SNASW DLSw+ on same router configuration

[a.mountouris]

Hello,

there is a problem we have encountered during a test having snasw and dlsw on the same router. The network environment is like the following:

(end user PC.ETH)--(7204B)--/DLSW/--(7204A)----(OSA.ETH>MainFrame)

End user has PCOM emulator for 3270 data stream interpretation. DLSw is between the two 7204. 7204A has also snasw enabled and we have achieved connection to the mainframe with both ways: HPR/IP and pure SNA (sna on osa too).

When we set at end user PC as destination address the MAC address of the OSA everything is ok.

But when we try to put a VDLC port definition on 7204A and use the virtual mac of this VDLC port as destination, the session is not coming up.

Any ideas? Any working example of having dlsw, snasw and vdlc interface on same router?

Regards, Apostolos.

[rclousto]

There are a few things to check, let's narrow down what's not coming active and then figure out why it's not.

Does the link from the PCOM box to snasw on 7204A come up? On 7204A, "sh snasw link" should show an active link with a link name like $I000001 on the VDLC port active.

In "show snasw link" you should also be seeing your link configured to the mainframe as active.

Do you have CP-CP sessions from 7204A to the mainframe? "show snasw sess" should show 2 CPSVCMG mode sessions to the mainframe. Do you have a CPSVRMGR session up as well? This should be driven up when the downstream link comes up and indicates it wants an SSCP-PU session.

I assume the DLSw peer connection is active else it wouldn't work when you use the OSA address, right?

Regards,

Bob

[a.mountouris]

Hello Bob,

and many thanks for the reply. The problem was in the definitions inside the PCOM emulator. It was wrongly defined the adjacent CP name, it was defined the SSCP of the VTAM but it needs to be the CP name of the cisco router.

We performed another test with blanks in the definition of adjacent CP name and it worked also (I assume dynamicaly found out that adjacent CP is the router).

Anyway, all work fine now, HPR/IP to Mainframe and DLSw+ for downstream PUs. The VDLC also works fine.

Regards, Apostolos.

[rclousto]

Hello Apostolos,

I'm glad to hear that you were able to resolve the problem. I recommend leaving the adjacent CP name blank. APPN nodes will always send their CP name on the XID exchange. This way if you have to change the adjacent node later, or decide to build in redundancy (two SNASw/DLSw routers with the same MAC address so that either can answer) it will work with no modification to the PCOM emulator.