Summary of two Cisco S4500 switch configurations

The following are all the problems you will encounter when working through CCIE RS LAB EXAM.

The switchover between the two switches is very simple, the configuration is very simple, but from the beginning of this cut to the final completion, I calculated the time, about two hours, I personally feel that the efficiency is too bad, in fact, should be half Completed within an hour, so special summaries.

The time specified at that time was to change the equipment from 18 o'clock. The original equipment of the customer was an old S4506 switch.

You can see that the engine is a relatively old four-generation engine. There are only two boards on it. I believe many people can see that it is an old GBIC interface, and the fiber is single mode in yellow.

The model of the device that is being replaced now is

From this above, we can see a lot of information, the first is 0X2101, I found out in the summary, I did not update to 0X2102 in the end. Did not pay attention at the time:

This later discovered that it was a very big mistake. It is very likely that it will cause a fallback, but the luck at the time was not bad, and there was no retreat.

Let's take a look at the customer's old configuration:

The following configurations are deleted. The main configuration is as follows:

Cisco_4506#show run

Building configuration...

interface GigabitEthernet3/1

 switchport trunk encapsulation dot1q

 switchport mode trunk

!

interface GigabitEthernet3/2

switchport trunk encapsulation dotlq

switchport mode trunk

!

interface GigabitEthernet5/1

 switchport trunk encapsulation dot1q

switchport mode trunk

!

interface GigabitEthernet5/2

switchport trunk encapsulation dot1q

switchport mode trunk

interface GigabitEthernet5/3

switchport trunk encapsulation dot1q

switchport mode trunk

interface Vlan1

ip address 192.168.0.2 255.255.255.0

interface Vlan10

ip address 192.168.1.1 255.255.255.0

interface Vlan20

ip address 192.168.2.1 255.255.255.0

 interface Vlan30

ip address 192.168.3.1 255.255.255.0

 interface Vlan40

ip address 192.168.4.1 255.255.255.0

interface Vlan50

ip address 192.168.5.1 255.255.255.0

interface Vlan60

ip address 192.168.6.1 255.255.255.0

interface Vlan70

ip address 192.168.7.1 255.255.255.0

ip access-group 101 out

interface Vlan80

ip address 192.168.8.1 255.255.255.0

ip route 0.0.0.0 0.0.0.0 192.168.0.1 

ip http server ip http port 7777 

ip http access-class 1 

ip http authentication local

access-list 1 permit 192.168.1.1 

access-list 1 permit 192.168.0.2 access-list 1 permit 192.168.1.232

access-list 100 deny ip 192.168.0.0 0.0.255.255 192.168.7.0 0.0.0.255 access-list 100 permit ip any any

access-list 101 deny ip 192.168.1.0 0.0.0.255 host 192.168.7.92

access-list 101 deny ip 192.168.2.0 0.0.0.255 host 192.168.7.92

access-list 101 deny ip 192.168.3.0 0.0.0.255 host 192.168.7.92

access-list 101 deny ip 192.168.4.0 0.0.0.255 host 192.168.7.92

access-list 101 deny ip 192.168.5.0 0.0.0.255 host 192.168.7.92

access-list 101 permit ip any any

Obviously, the configuration is simple and simple. At the time of configuration, when all the configurations were imported into the new switch, the VLANs could not communicate with each other. I was surprised at the time. This is the default, why not here. I remember to manually open the command IP ROUTING. When I hit this command, I remembered that this is the engine of SUP7, and the license is LANBASE. It may not support routing. Because by default, this engine does not buy a license is a Layer 2 switch.

If I follow my own ideas, things will not be configured here, and the cutover work will end here. But this is not the case, but it can be done. In the second layer license, even in the case of lanbase, you can play static routes and support Layer 3 functions. Of course, if it is really not supported, I have written it before, you can use the RTU license, the order will not be repeated in this way.

Here to see the configuration of the new device with the cutover completed:

As can be seen from the figure, the box is the 4507R chassis. Support for dual engines, currently only one engine is configured. WS-X45-SUP7L-E, here again, this engine is usually licensed to send ip base when it is bought, that is, it supports OSPF. But this time did not send, everyone must pay attention when configuring, this time can be configured successfully, there is no fallback, it is because the customer's configuration is too simple, it is not worth mentioning, so it is successful, this is also entirely luck .

The above is my feeling of when I exam CISCO CCIE LAB and CISCO CCIE written exam. Hope you guys for your own dream to fight! Fighting!