Showing results for 
Search instead for 
Did you mean: 

Really challenging route issue for me today


Today I had to turn up a few T1's for a Windstream MPLS that we are pushing voice over. All Windstream voice runs over 172.16.X.0/24 private networks, so the diagram is basically the HQ which holds the network. The destination subnet is

There is a voicemail server that has two NICs one on the network with no gateway and a NIC on network (Data) with a gateway of (HSRP VIP of 5k's). The two Links connected from the Nexus 5k's to the Verizon MPLS router are peering iBGP with Verizon and learning different 10.X.X.X networks from corporate private MPLS. I have verified that BGP is not learning any through networks from the corporate network. The route table only shows 2 networks being learned in that subnet area and they are and

So I have interface vlan 30 on each Nexus, and at first I entered static routes into each Nexus that states to get to networks to use as the gateway. After this from the Nexus, either one, I would do a ping and traceroute to using the source of for Nexus 1 and for Nexus 2. The ping failed, and the traceroute showed the traffic going out the layer 3 links connected to the Verizon MPLS router. No clue why. The route table shows me all my 10.X.X.X networks being learned via BGP, shows me the statics that I entered for the 172.16 networks and a default route that points to, which is the ASA to the internet.

So my fix for this, because I was clueless as to what was going on and why, was I created a VRF and called it windstream, associated it with Interface vlan 30 and entered all the static routes into that VRF. Now when I try to ping and source it from VRF Windstream I can get to my destination. Now the issue was the Voice mail server that was dual homed had a gateway of which is Interface Vlan 2 and it could not ping anything or Now I understand why it cant reach, but why cant it ping The Nexus holds both SVI's so shouldn't it just route? Of does the SVI for vlan 30 being in its own VRF isolate it? To fix this for now I just put a persistant route into Voicemail Windows server route table that points it to to get to anything 172.16.

So why was the original configuration pushing traffic to the verizon MPLS router where it was not learning this network, and therefore if static routes didnt exist, it would have atleast gone to the default route which would have taken it to the ASA and dropped the traffic. With the static routes entered into the routing table with all the BGP networks learned, shouldn't the Nexus have know to push that traffic back to the Windstream Router to get to those networks?

Did I miss something?

Frequent Contributor

Really challenging route issue for me today


Please post some output about the HSRP running on Vlan 30 and Vlan 2.

Also try get rid of any VRF as you don't need it in this scenario. Finall, ping 172.16.6.x source


Really challenging route issue for me today

I eliminated the VRF for all these 172.16.x.x subnets, but now I think I am routing over the peerlink. Everything works right now with the way I have it, but the issue is the traffic goes up the N5k's then back down to get to the router that leads to the other subnets over the MPLS cloud. And honestly I don't know if I am routing over the peerlink or not. I need to figure it out.


Really challenging route issue for me today

Can you delete the VRF and add the statics back into the global routing table, then share

show ip route

show ip route

Can you share show ip bgp summary from both Nexus, along with show ip bgp and show vpc.



CreatePlease to create content
Content for Community-Ad
July's Community Spotlight Awards