Cisco6506vss connection problem with Cisco4507vss

Cisco's VSS is really a very good technology for the project, but when configuring VSS it's important to be aware of whether the engine, board, iOS are all supported, and the different versions of iOS, it's best to refer to the appropriate configuration guide. Of course, I feel the most important is to make sure that the VSS work principle to understand, technology is not to the book to knock command line, but the real grasp of technology.

Back to the point:

Customer Main Plant original two cisco6506, and do the VSS, factory area in order to ensure network redundancy, decided to use two cisco4507 do VSS and 6506 connected, before doing VSS, I downloaded the cat4500e-universal on the Internet. Spa.03.04.05.sg.151-2.sg5.bin, and found the configuration manual on the official website.

At about 5:30 in the evening, I and colleagues at the scene, the first two 4507 of the system to do a backup and upgrade to ensure consistency of the system, and then refer to the configuration manual for the two 4507 VSS, after finished using switch convert mode virtual to switch the system to VSS mode, Through the show command to find two switches in the active state, one in the standby state, two 4507 of the VSS configuration is complete. But at the same time the problem comes up! In the ping test found that the factory area and the main plant directly connected to the link is not working!!!

Check the interface status, Normal! Detect link status, normal! But why not?

Since we are using the Ipbase version of the VSS feature, we also suspect that the feature is not fully open and has some limitations. So decided to find another iOS test, and then found Cat4500e-universal. Spa.03.07.00.e.152-3.e.bin, re-upgrade, found that different iOS, some of the commands are indeed different, even the VSS commands are slightly different. Configure VSS again, and check that VSS is working properly after the configuration is complete, but the same problem recurs! Why?

Using show Arp view, found that the switch can not learn the MAC address of the end, we switch the switch to standalone mode, ping to the end, found out!! Using show ARP to discover the Mac that learned to end this time, why? At this time my colleague and I have been somewhat confused, think of the internet vibe of the picture of the fragile worship equipment, can't help laughing! We switched 4507 again to VSS mode, and then the phone to let our boss remote to the factory area of 6506, check found that 6506 normal operation is not a problem.

Can't learn the mac!!! The boss proposed: since cannot learn, then you are there to use ARPA binding to try. Perhaps God really do not want to toss us in the middle of the night, so when tied to the MAC found that the boss told us the main factory Mac is the same as our Mac!!! MY god!!! The problem is found!

Due to the configuration of VSS, we are mainly configured to:

1. Virtual domain

2. Switch number

3. Switch priority

4. Virtual link

5. Dual-active Check

Only MAC address is the default, that is, mac-address use-virtual, viewing the document can be found, if using use-virtual, then:

Assigns the router MAC address from a reserved pool of domain-based addresses.

That is, the system from the reserved MAC address selected as a VSS to use the Mac, at this time it is not difficult to find, do VSS, the system will always choose from the reserved address of the first to use as a VSS Mac, so that our two ends of the same Mac, the factory area to learn the factory area of the Mac, It eventually leads to the problem.

Re-configure a MAC address through the mac-address command, ping the test again, and finally found the long-lost "!!!!! "At this point, the problem is solved!"

*********************************************************************************************************

After thinking about it, we found that in the process of debugging we have also logged into the plant area of the equipment, but because the link is through, we do not care about what the Mac is, but switch to VSS mode after the two ends are not, we have no way to log on to the remote, want to see the Mac when the Mac can not see Seems to have entered a dead loop! But the most surprising to us is that MAC address, even every time from the first start to choose to use! You can't use the default configuration every time you configure it!

*********************************************************************************************************

Finally repeat one sentence: Technology is not scripted, technology is a comprehensive grasp of the need!

This article is from the "Xunil" blog, make sure to keep this source http://136464.blog.51cto.com/126464/1610359

Cisco6506vss connection problem with Cisco4507vss