I have a complex question, maybe not. We recently move half of our servers to a data Center, we are connected Via a layer two link. At HQ we have two Nexus 7k, and at the DC two Nexus 5k. all our routing is located at HQ at the moment. Currently the Nexus 5k’s are working on layer2. The problem we are having is that when VLan 100 is sending data to Vlan 200 it all travels from the DC to HQ then routes back to the DC. And to make thing even more fun Vlan 100 and 200 are in both locations, and need to talk as well. I believe I have found a solution via Packet Tracer, but that’s in theory.
What I believe I can do is set the same IP address on the vlan’s at the DC as they are at HQ, and turn on routing.
Until you have Gateway IP address on your HQ Nexus7K switches , all traffic from your DC will come to HQ for communicating between VLAN.
If you create SVI with new IP address from same VLAN segment on DC Nexus 5K switch and enable routing , you need to modify gateway IP address for DC server pointing SVI IP address of NEXUS 5k . HQ Server Gateway IP address can be left as its .
With this way you can achieve inter-vlan communication .
Link between HQ & DC should be made as trunk allowing VLAN 100 & VLAN 200 .
I just want to make sure I understand before i try to suggest implementing this.
SVI @ HQ will stay the same, as well as the GW on the servers @ HQ
I need to add a SVI for the Vlans that I need routed at the DC, and I cant use the same IP as HQ SVI because of duplicate IP Address on the network? so I will use a new address on the network and turn on routing on the 5K. Change the GW on the servers on the DC side to the new GW.
After this is done the servers on both sides will be able to to each other on both sides, as well talk between Vlans on each side.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...