Can we bind secondary IP segment on CIP connection

[lliwai]

Does anyone know whether we can bind secondary IP segment on CIP connection ?

CIP card using is CX-CIP2-ECA2 (CIP2 controller (2 IBM Channel)) in Cisco 7513 router with RSP4 running IOS version 12.1(9)

[hadbou]

CSNA supports:

Communication between a channel-attached mainframe that runs virtual telecommunications access method (VTAM) and a LAN/WAN-attached Physical Unit (PU) 2.0 SNA node.

Communication between a channel-attached mainframe that runs VTAM and a LAN/WAN-attached PU 2.1 SNA node.

Communication between a channel-attached mainframe that runs VTAM and a LAN/WAN-attached PU 5/4 SNA node. WAN attachment is restricted to RSRB and DLSw+.

Communication between two channel-attached mainframes that run VTAM to the same CIP card, or different CIP cards, in a 7000 router. The two VTAMs can be configured as PU5s or PU 2.1 nodes. External communications adapter (XCA) major nodes do not provide network boundary function. Therefore, the remote connection must be to an NCP, a PU4, if the CIP is configured as an SNI link.

[dmccullo]

Hi Wai,

If I understand the question, the answer is yes. The only caveat I find is to code "ip route-cache same-interface". Apparently there are no samples online, so it should look something like this -

interface Channel3/0

bandwidth 98304

ip address 172.22.0.1 255.255.255.0 secondary

ip address 172.22.100.1 255.255.255.0 secondary <---

ip address 172.22.101.1 255.255.255.0 secondary <---

ip address 172.20.75.33 255.255.255.248

no keepalive

claw C141 00 172.20.75.34 MVS4 CIP2 TCPIP TCPIP

claw C131 00 172.20.75.37 MVS3 CIP2 TCPIP TCPIP

claw C861 00 172.20.75.38 MVS6 CIP2 TCPIP TCPIP

claw C811 00 172.20.75.36 MVS1 CIP2 TCPIP TCPIP

claw C121 00 172.20.75.35 MVS2 CIP2 TCPIP TCPIP

claw C851 00 172.22.0.51 MVS5 CIP2 TCPIP TCPIP

claw C851 02 172.22.0.50 MVS5 CIP2 TCPIP TCPIP

claw Cxxx 02 172.22.100.50 MVSx CIP2 TCPIP TCPIP <---

claw Cxxx 02 172.22.101.50 MVSx CIP2 TCPIP TCPIP <---

Hope that helps,

Dan

[lliwai]

Hi Dan,

Thanks for your info.

Must the IP address we assign to the interface be in the same subnetwork as the hosts with which we wish to communicate ?

Such that when we add a new secondary IP subnet in the interface, we need to add the corresponding new claw statemnet with the Host ip address with the same subnet with the new secondary IP address ?

Thks

Li