I asked this on the Spiceworks forum as well, but I thought that I'd ask here as well:
I've been working on setting up routing between two switching stacks with little success. I've spent 9 hours on this so far.
The first stack is an Avaya ERS stack. The second is a Cisco 3750x stack. Both are licensed for L3 and do inter-vlan routing well. This Cisco stack will be going to our DC and is currently connected via a 1GB ethernet cable in the same rack.
The Avaya infrastructure is pre-existing with the exception of the routing port mentioned below. The Cisco infrastructure is a new setup.
The Cisco end has a port enabled as a router port with the IP 10.48.35.49/30
The Avaya end has a similar port enabled as a "brouter" in their lingo. (a port in it's own vlan) with an IP
of 10.48.35.50/30
Site (A)vaya has VLAN 1 with an IP of 192.168.1.250 and VLAN 10 with an IP of 192.168.10.250 as well as VLAN 50 (192.168.50.250) to which a inside port of a firewall is connected. Avaya's default route of 0.0.0.0 is the firewall inside 192.168.50.100 (functioning fine)
Site (C)isco has VLAN 2 (192.168.2.254) and VLAN 20 (192.168.20.254)
Neither VLAN is defined on the opposite site.
A host in site A can ping it's local 10.48.35.50 with a sub 1ms response time and no packet loss, however when it pings anything on the (C)isco side 10.48.35.49, the latency gets above 1ms, more like 12-18ms with about 8% packet loss. Pinging the far VLANs 2 and 20 IPs is successful with similar latency, however pinging of hosts connected to those VLANs is unsuccessful.
The hosts in site C can ping it's local 10.48.35.49 Pinging the far VLANs 1 and 10 IPs is successful pinging of VLAN IPs as well as the hosts connected to those VLANs is unsuccessful.
The weird thing is, when I tracert from a host in VLAN 2 (192.168.2.25) from site C to a host in site A on VLAN 10 (192.168.10.2), the first hop is the router interface facing the firewall 192.168.50.250, then the target.
Do I have a routing loop issue? I'm not all that familiar with Avaya systems.
Ciisco stack:
Gateway of last resort is 192.168.51.251 to network 0.0.0.0
S* 0.0.0.0/0 [1/0] via 192.168.51.251
10.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
C 10.48.35.48/30 is directly connected, GigabitEthernet2/0/20
L 10.48.35.49/32 is directly connected, GigabitEthernet2/0/20
S 192.168.1.0/24 [1/0] via 10.48.35.50
192.168.51.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.51.248/29 is directly connected, Vlan51
L 192.168.51.254/32 is directly connected, Vlan51
S 192.168.10.0/24 [1/0] via 10.48.35.50
S 192.168.10.0/24 is directly connected
is directly connected, GigabitEthernet2/0/20
192.168.2.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.2.0/24 is directly connected, Vlan2
L 192.168.2.254/32 is directly connected, Vlan2
192.168.20.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.20.0/24 is directly connected, Vlan20
L 192.168.20.254/32 is directly connected, Vlan20
Avaya stack:
DST MASK NEXT COST VLAN PORT PROT TYPE PRF
0.0.0.0 0.0.0.0 192.168.50.1 5 50 T#4 S IB 5
10.48.35.48 255.255.255.252 10.48.35.50 1 4094 ---- C DB 0
192.168.1.0 255.255.255.0 192.168.1.250 1 1 ---- C DB 0
192.168.10.0 255.255.255.0 192.168.10.250 1 10 ---- C DB 0
192.168.50.0 255.255.255.0 192.168.50.250 1 50 ---- C DB 0
192.168.2.0 255.255.255.0 10.48.35.49 1 4094 3/10 S IB 5
192.168.20.0 255.255.255.0 10.48.35.49 1 4094 3/10 S IB 5
The Avaya "brouter" port is in VLAN 4094, port 3/10, directly connected to the routing port on the Cisco stack.
It seems like when the packet reaches the Cisco port, there's no destination VLAN tag applied or it doesn't know where to send it.
Inter-VLAN traffic within either stack works fine. A host on the Cisco stack of 192.168.2.2 can reach 192.168.20.25 and the internet via 51.251.
Thank you!
Brad
Thanks,
Brad
