We have two data centers with a pair of Nexus 7000 in each of them. We use OTV to extend the existing VLANs below to serve across site traffic.
We found that 10, 16, 40 and 42 are going through the first Nexus while 17 and 41 are going through the second one, which is exactly what the Cisco document described that "VLANs are split as odd and even VLAN IDs on each edge device". But, the load is not well balanced!
So my questions...is there any way we can redistribute the vlans so that they are evenly allocated between the two Nexus? How can we assign a particular VLAN to a specific Nexus?
I found your posting while I was looking for something related to the even/odd split. As far as I know, at this date the behaviour is fixed, and depends on the system id of the switches. The lower system id gets the even numbered VLANs and the higher system id gets the odd numbered VLANs.
However, I did hear at Cisco Live! this year that it is planned for a future release to be able to allocate specific VLANs to specific AEDs in the same sort of way that you allocate VLANs to MST instances. That will be great, because if you are using MST, it will make it easier to keep the spanning-tree root in correspondence with the AED.
I think it will still be on a per-VLAN basis, that is, you will not be able to load-share a single VLAN between AEDs. So if you have a VLAN that carries much more traffic than the rest put together, you will still have the imbalance.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...