Re: Intermittent EE failure initiated by SAVRSTOBJ - V6R1

Another Enterprise Extender tip.
AnyNet does not care if the data sent back to the source system is routed
back from the same IP you sent to.
Enterprise Extender DOES.

If your SystemA has an Enterprise Extender controller to SystemB at an IP
address of say 12.100.200.15
BUT SystemB routes outbound traffic over a different route so that SystemA
sees the data coming back from say 12.100.200.95 then you will have
problems.
One of the symptoms can be that if you are on SystemB you can always
originate a connection (say STRPASTHR over Enterprise Extender) back to
SystemA. But System A can only originate a STR{ASTHR connection to System
B within a short time period (a minute or two) of when System B initiated a
connection to SystemA (or maintains an active connection) - if you follow
me.

In other words, if the location of the remote SystemB has multiple Public
WAN IP addresses for Internet traffic, make sure the one SystemA has
defined for the Enterprise Extender controller is the same Public IP that
routes traffic back from SystemB.



And yes, check all Enterprise Extender PTFs here:
V5
http://www-01.ibm.com/support/docview.wss?uid=nas8N1017409

V6

http://www-01.ibm.com/support/docview.wss?uid=nas8N1013733

V7
http://www-01.ibm.com/support/docview.wss?uid=nas8N1012511


Neil Palmer, Waterloo, Ontario, Canada


(This account not monitored for personal mail,
remove the last two letters before @ for that)


________________________________
From: Evan Harris <auctionitis@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Thursday, October 17, 2013 2:01:20 PM
Subject: Re: Intermittent EE failure initiated by SAVRSTOBJ - V6R1


Keep in mind you are running over the network, so don't rule out network
issues.

Make sure the required ports are open in your firewalls, especially the
12000 thru 12004 UDP ports


On Fri, Oct 18, 2013 at 4:20 AM, Steinmetz, Paul <PSteinmetz@xxxxxxxxxx

wrote:

Since migrating from ANYNET to EE
SAVRSTOBJ from LPAR A to LPAR B results in failure, intermittently
Strpasthr from A to B also fails.
Strpasthr from B to A works.

On B, Object Connect retries for 2 hours, before reporting the error.
ObjectConnect internal error, function code F5, return code BF.

On A, error occurs, 30 minutes earlier.
CPF3808 Diagnostic 30 10/17/13 04:21:46.431277
QSRSVDEQ QSYS 0388 QSREVTHD QSYS 03FD
Message . . . . : Save file

OBCSAVF

in QTEMP not complete.
Cause . . . . . : An error occurred
during the save operation. Recovery . .
. : Do not use the save file for
restoring because the restore operation
may not end normally. See message
CPF389C for corrective action.
CPF389C Escape 30 10/17/13 04:21:46.431538
QSREVTHD QSYS 0568 QSVRSINT QSR 00DC
Message . . . . : ObjectConnect
internal error, function code F4, return
code BF.
Cause . . . . . : An error

occurred

during an ObjectConnect communications
request. Recovery . . . : Try
the request again. See the Backup and
Recovery - Basic book, SC41-4304
for an explanation of the codes. If the
problem persists, report the
problem using the Analyze Problem (ANZPRB)
command.


It appears the "timers" are different on A and B,
LPAR A tries for 90 minutes.
LPAR B tries for 120 minutes.

Sometimes, the issue resolves itself, no interaction done.
Other times, varying off/on EE controller on A that points to B "appears"
to resolve the issue.

Open PMR with IBM, nothing yet.

Could it be a configuration issue.

Anyone experience similar issue?


Thank You
_____
Paul Steinmetz
IBM i Systems Administrator

Pencor Services, Inc.
462 Delaware Ave
Palmerton Pa 18071

610-826-9117 work
610-826-9188 fax
610-349-0913 cell
610-377-6012 home

psteinmetz@xxxxxxxxxx<mailto:psteinmetz@xxxxxxxxxx>
http://www.pencor.com/

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

--

Regards
Evan Harris

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.