IPv4 issues - Multinetting

EtherNation_Use — Wed, 08 Jan 2014 05:50:00 GMT

Create Date: Jan 4 2012 4:26PM

I have a Summit stack with a series of VLAN's configured, one of which is our main for all of our base systems.

I have attached to this VLAN a series of multinetted address ranges.

VLAN DATA TAG 2
VLAN IP: 10.0.0.3 (10.0.0.0/24)
MULTINET #1: 172.16.51.1 (172.16.51.0/24)
MULTINET #2: 172.16.52.1 (172.16.52.0/24)
MULTINET #2: 172.16.53.1 (172.16.53.0/24)

I can access all systems on this VLAN on the primary, and any of the multinetted ip addresses.

However we have recently added in a HDS SAN and have connected the management controller ports to the stack. I can ping/snmp/http/https etc.. the controller from the switch stack itself, and any other mutlinetted address, however we cannot access the controller from the primary subnet (10.0.0.0/24).

I've confirmed and reconfigured the ports to be on the DATA VLAN as untagged (conf data add port 1:13 untagged) however we are unable to get any data to the controller from the native subnet.

We have an open ticket with the TAC and are awaiting feedback, but I thought I'd trow this out to see if anyone else had seen this issue before and had a solution.

* Slot-1 Stack.2 # ping vr "VR-Default" 172.16.52.251 from 10.0.0.3
Ping(ICMP) 172.16.52.251: 4 packets, 8 data bytes, interval 1 second(s).
--- 172.16.52.251 ping statistics ---
4 packets transmitted, 0 packets received, 100% loss
round-trip min/avg/max = 0/0/0 ms

* Slot-1 Stack.3 # ping vr "VR-Default" 172.16.52.251 from 172.16.51.1
Ping(ICMP) 172.16.52.251: 4 packets, 8 data bytes, interval 1 second(s).
16 bytes from 172.16.52.251: icmp_seq=0 ttl=64 time=8.109 ms
16 bytes from 172.16.52.251: icmp_seq=1 ttl=64 time=1.921 ms
16 bytes from 172.16.52.251: icmp_seq=2 ttl=64 time=2.250 ms
16 bytes from 172.16.52.251: icmp_seq=3 ttl=64 time=8.097 ms
--- 172.16.52.251 ping statistics ---
4 packets transmitted, 4 packets received, 0% loss
round-trip min/avg/max = 1/5/8 ms

* Slot-1 Stack.4 # ping vr "VR-Default" 172.16.52.251 from 172.16.52.1
Ping(ICMP) 172.16.52.251: 4 packets, 8 data bytes, interval 1 second(s).
16 bytes from 172.16.52.251: icmp_seq=0 ttl=64 time=6.643 ms
16 bytes from 172.16.52.251: icmp_seq=1 ttl=64 time=8.331 ms
16 bytes from 172.16.52.251: icmp_seq=2 ttl=64 time=1.124 ms
16 bytes from 172.16.52.251: icmp_seq=3 ttl=64 time=1.323 ms
--- 172.16.52.251 ping statistics ---
4 packets transmitted, 4 packets received, 0% loss
round-trip min/avg/max = 1/4/8 ms

(from Francis_McPhail)

RE: IPv4 issues - Multinetting

EtherNation_Use — Wed, 08 Jan 2014 05:50:00 GMT

Create Date: Jan 11 2012 6:38AM

Hello,

To me, it looks like the problem is caused by your SAN having no reverse path back to your primary subnet.

Do you use the summitstack as a router between these subnets?

And does your SAN have a route to the 10.0.0.0/24 network? (e.g. configured with multinetting as well, or does it use the summitstack as default gateway?)

If you're using the summitstack "10.0.0.3" as default gateway, If so, you will just need to enable ip forwarding on your "DATA" VLAN.

Otherwise, you can enable ip forwarding, and add a static route to the primary subnet, inside your SAN network configuration, e.g.

code:

ip route add 10.0.0.0/24 gw 172.16.52.1 dev eth0

(from Kenneth_Oestrup)

topic RE: IPv4 issues - Multinetting in ExtremeSwitching (EXOS/Switch Engine)

IPv4 issues - Multinetting

RE: IPv4 issues - Multinetting