ITEM: AG5149L
CP-CP session won't start
Question:
Desc:
Harry has configured 2 riscs on a token ring as APPN network
nodes. When he starts the link station, it becomes active
but the CP-CP sessions don't start.
Resp:
Made sure he has both sides saying they support cp sessions.
The network names on the two are different, but the bind
request contains the correct fq cp names. The sense code
in the unbind which is sent from the other side is 084b0000
Requested Resources Not Available.
Don't know what is going wrong here. Will research and call
him back. 703-759-8498.
Response:
Called and left a message that we were able to start a link station
between two network nodes and had no problem with the CP-CP sessions
starting. We configured a calling link on one side and let the
dynamic listening link station answer on the other. We has to stop
and restart sna but after that the link started fine and both
CP-CP sessions started.
Verify that you have the CPSVCMG mode and nothing has been changed
in that profile.
Response:
Told Harry that we had gotten this to work in our lab. I had Harry
try to start this link station from the other machine and we traced
it. This time we got a different sense code 0891 0006 and it looked
that there was positive BIND then an unbind. The sense code means:
Invalid Network ID: The sender has deactivated CP-CP sessions with
the adjacent nonnative CP because neither CP contains border node
support (ie., neither sets byte 9, bit 7, to 1 in the CP
Capabilities GDS variable that it sends).
I have the traces and profiles. One of the machines is at level
1.3.94.10 and the other is at 1.3.95.20.
Will call Harry back when I get more info on this. There were no
hits in AUSTEXT.
Response:
Found out that we get this sense code because the RISC does not
provide border node support.
"According to the base APPN architecture, network nodes within
an APPN network must share the same NETID (as opposed to end
nodes, which may have a NETID different from their adjacent
node's NETID). " -- p.151 APPN Architecture and Products
Implementation Tutorial, GG24-3669-01
"...an APPN network node can have CP-CP sessions with other network
nodes only if they all use the same network ID. The solution to
the multi-network connectivity requirement is a border node." --
p.32 3174 APPN Implementation Guide, GG24-3702-00
Border node support is required for APPN Network Nodes that
need CP-CP sessions with a APPN Network Node with a different
Network ID. Harry was using two different Network Ids. We
reproduced this in our lab by using different network ids.
I am including the summary trace here for reference:
333 TokenRing 10005AB18666 -----------------XID(3)----------------->
334 TokenRing 10005AB1C735 \<----------------XID(3)------------------
335 TokenRing 10005AB18666 -----------------SABME------------------>
336 TokenRing 10005AB1C735 \<------------------UA--------------------
337 TokenRing 10005AB18666 -------------------RR------------------->
338 TokenRing 10005AB1C735 \<------------------RR--------------------
340 TokenRing 10005AB18666 00200 ----------------BIND rq----------------->
341 TokenRing 10005AB1C735 00002 \<--------------BIND +rsp-----------------
342 TokenRing 10005AB18666 -------------------RR------------------->
344 TokenRing 10005AB18666 00200 ---------FMH5,CPCapabilities rq--------->
345 TokenRing 10005AB1C735 00002 \<--------IPM solicited(1) +rsp-----------
346 TokenRing 10005AB18666 -------------------RR------------------->
347 TokenRing 10005AB1C735 00002 \<----------CPCapabilities rq-------------
348 TokenRing 10005AB18666 -------------------RR------------------->
350 TokenRing 10005AB18666 00200 ---------IPM solicited(1) +rsp---------->
351 TokenRing 10005AB1C735 10200 \<---------------BIND rq------------------
352 TokenRing 10005AB18666 -------------------RR------------------->
354 TokenRing 10005AB18666 00200 ---------------UNBIND rq---------------->
355 TokenRing 10005AB1C735 00002 \<-------------UNBIND +rsp----------------
356 TokenRing 10005AB18666 -------------------RR------------------->
358 TokenRing 10005AB18666 10002 ---------------BIND +rsp---------------->
359 TokenRing 10005AB1C735 10200 \<--------FMH5,CPCapabilities rq----------
360 TokenRing 10005AB18666 -------------------RR------------------->
362 TokenRing 10005AB18666 10002 ---------IPM solicited(1) +rsp---------->
364 TokenRing 10005AB18666 10002 -----------CPCapabilities rq------------>
365 TokenRing 10005AB1C735 10200 \<--------IPM solicited(1) +rsp-----------
366 TokenRing 10005AB18666 -------------------RR------------------->
368 TokenRing 10005AB18666 10002 ---------------UNBIND rq---------------->
369 TokenRing 10005AB1C735 10200 \<-------------UNBIND +rsp----------------
370 TokenRing 10005AB18666 -------------------RR------------------->
425 TokenRing 10005AB1C735 \<------------------RR--------------------
426 TokenRing 10005AB18666 -------------------RR------------------->
Response:
Support Line: CP-CP session won't start ITEM: AG5149L
Dated: March 1995 Category: N/A
This HTML file was generated 99/06/24~13:30:27
Comments or suggestions?
Contact us