When purchasing network equipment, network administrators of each company carefully select and study it repeatedly among different manufacturers of the same level, and after multiple comparisons, they select the best cost-effective product. However, there is one thing that many network administrators may ignore, that is, the future of network products. If a product cannot be used all the time, there will definitely be problems. After the problem occurs, the manufacturer's service becomes particularly important. Similarly, network technology is constantly developing and advancing, and network products must also have certain upgradeability and scalability. Recently, the author has encountered the problem of upgrading core equipment, and the records are as follows:
1. Upgrade the environment:
The reason for this is that the company's subordinate departments applied for a certain amount of expenses for network upgrades. Therefore, the department bought a new Cisco Catalyst6509 switch a few days ago and was equipped with WS-X6548-GE-TX, a 10M, 100M, and 1000M adaptive 48-port RJ-45 switch module that Cisco launched in April last year. 6509 has 9 slots in total, so 9 modules can be inserted. It is common to add modules to upgrade core equipment. However, since Cisco's software launch always lags behind the hardware, the 12.2 (14) SX1 version of the IOS that has been equipped with the standard configuration of Catalyst6509 switch cannot support this module. This involves the upgrade issue, and it is necessary to upgrade the IOS of the 6509 switch. So my sub-department network administrator and I found a new version of IOS that supports the WS-X6548-GE-TX module from the official CISCO website to prepare for upgrade. Unexpectedly, this simple upgrade work lacked trouble for us two "quasi-economic experts" and problems arose one after another.
2. No RJ-45 interface
The WS-X6548-GE-TX module used this time has a total of 48 RJ-45 ports, but the 6509 switch does not have other modules with RJ-45 interfaces. What should I do? After all, to upgrade IOS with Cisco's TFTP Server, you must connect the switch to a PC with TFTP Server on the network. After some searching, I finally found that there was an RJ-45-shaped interface on the Super Engine 720, with the words Link written next to it. As a result, I used it to plug it in the network cable and found that the indicator lights were not on. Originally, we thought there was hope, but the indicator light did not light up, which means that the interface could not be used. However, because this interface is the only hope, otherwise we can only use xmodem to transmit 41MB of IOS, and the transmission time may be discouraged.
Tips:
Using XMODEM to transmit IOS is very troublesome. The author once used XMODEM to transmit the IOS of a 2950 switch, with a total capacity of only about 2MB, which took two hours. At this speed, 41MB can take at least 30 hours.
Since it is not realistic to use XMODEM to transmit IOS, we must start with the RJ-45-like interface on the Super Engine 720. From searching online, it turns out that there are two modes for port2 on the super engine 720: one is the RJ-45 interface, and the other is the SFP (a small form-factor pluggable) interface. The default setting is SFP, and to use the RJ-45 interface, you must change the settings. Enter the following command to modify—
Router(config)#interface gigabitethemet 5/2
//Enter this interface to set
Router(config-if)#media-type rj45
//Modify the mode to RJ45, default is SFP
Router(config-if)#no shutdown
//Enable this interface
After executing the command, I found that the orange indicator light finally turned green. Next, you can use the traditional TFTP method to pass the IOS files required for the upgrade to the switch. I thought the next thing should be easy, but who knew that the obstacles did not stop there.
3. TFTP transmission protocol does not support 32 megabytes
Next, assign the interface with the management address and back up the original IOS. Enter the command in HyperTerminal Global Mode:
Router#copy sup-rootflash: s72033-pk9sv-mz.122-14. tftp://192.168.1.1
A series of # font sizes appeared in TFTP Server and began to transmit data. I thought everything was OK. Who knew that when the transmission was about to be completed, the system prompted: "timeout! Write error!"
According to the system prompts, I checked whether the network cable was broken and whether the disk space was insufficient. The answer was no. The failure of executing the transmission command again remains. The size of the transferred IOS is 32MB on 6509, which is slightly smaller than the full IOS32.1MB. Why can't the extra 0.1MB be transmitted?
At first I thought it was because of the problem with the TFTP software and the version was too low. I downloaded a third-party TFTP server from the Internet and tried it, but the result was still the same. I found 3Com's TFTP Server, and the effect was even worse this time. It was disconnected when it reached 16MB. The system prompted that it was still timeout and write errors. After careful analysis, I finally found the key to the problem. The two transmissions are exactly 32MB and the other is exactly 16MB. The number of hyphens is not bad, so it is definitely not a problem with the transmission line. After searching for information, it turned out that the TFTP (Trivial File Transfer Protocol) ordinary file transfer protocol supports the maximum transfer of 32MB files. So I found Cisco Documents again, searched for a while, and found the second solution, just use FTP. So build the FTP service on your PC and type the following command:
Router# configure terminal
//Enter switch configuration mode
Router(config)# ip ftp username username
//Set the FTP access username
Router(config)# ip ftp password password
//Set the password for logging in to FTP
Touter(config)# end
//End, Exit
Router#copy sup-bootflash: s72033-pk9sv-mz.122-14. ftp:[//[username[:password]@]192.168.1.1]
//Execute the FTP transmission command, the transmission file is s72033-pk9sv-mz.122-14. The established FTP server address is 192.168.1.1.
After updating IOS with FTP transfer, the file copying is very normal. After waiting for a few minutes, the system prompts "successful!". It seems that FTP is more powerful and flexible than TFTP, and has much fewer restrictions.
Fourth, protocol error
After successfully backing up the IOS to FTP, it is your turn to upload the new IOS for upgrade. Enter the 6509 configuration mode and use the following commands to operate:
Router# configure terminal
//Enter configuration mode
Router(config)#ip ftp username username
//Set up users who log in to FTP
Router(config)#ip ftp password password
//Set the password for logging in to FTP
Router(config)#end
//Exit settings
Router# copy ftp:[[//[username[:password]@192.168.1.1] / s72033-jk9o3sv-mz.] sup-bootflash:
//Copy the new version of s72033-jk9o3sv-mz. to this switch.
I thought it was done easily, but this time the system prompted "Protocol error!". Protocol error? Try again, there is no problem with downloading, and uploading still prompts a protocol error. After analysis, I suspect that the problem may be on FTP Server. My FTP Server is made with Server-U, a third-party software. Could it be caused by compatibility issues? So I changed it to Microsoft Windows 2000's own FTP component in IIS to build an FTP server. There is no problem with trying to download and upload again, and no longer prompts for a protocol error. The screen shows Loading…. A few seconds later, another prompt message appeared: "There is insufficient Flash space".
Five, there is insufficient Flash space
After the FLASH space insufficient information appeared, I specifically checked the hardware configuration of the 6509 core device. The default Flash standard configuration of 6509 is 64MB, the standard IOS size is 32.1MB, and the 12.2 (17a) SX version to be upgraded is 40.6MB, so it seems that insufficient space is inevitable. However, this problem is relatively easy to solve. Delete the original IOS in Flash and upload it. So enter the command:
Router#delete sup-bootflash:s72033-pk9sv-mz.122-14.
Then pass it again. The prompt message is still insufficient space! At this time, I have deleted the switch's IOS. If the power is accidentally dropped or restarted, the switch will not be able to get up. In the management interface, use the show command to see that the IOS file is gone, but the space is still more than 30 megabytes, which means that the flash has not been cleared. At this time, I remembered that I had to restart the switch after deleting the file before it could take effect, but now it is absolutely impossible to restart. what to do? I searched for useful information on Cisco's website and finally found a command squeeze, which completely cleared the deleted files, just like clearing the recycling bin. run:
Router#squeeze sup-bootflash: Then use the SHOW command to check it out and found that Flash has been completely cleared and the available space is 64MB. At this time, use FTP to upload, and in a few minutes you will see the success message prompted on the screen. Reload it and use the show flash command to see that the IOS version has become 12.2 (17a) SX. Plug in the new module WS-X6548-GE-TX and try it. Everything is OK and the new module can run normally.
Summary of experience:
I originally thought that the work that was easy to complete was full of twists and turns, but it seemed that the upgrade of high-end products was also very complicated, and many links that were not paid attention to would have problems of one kind or another. This troubleshooting made me understand a truth. The technology has no end, and it is best to go to the official website to query when encountering problems. Also, you must think twice before doing things. If you take it for granted after deleting FLASH, the switch will not be able to start, and the consequences will be very serious. Please stop thinking for 30 seconds before the operation can often reduce many unnecessary losses.
1. Upgrade the environment:
The reason for this is that the company's subordinate departments applied for a certain amount of expenses for network upgrades. Therefore, the department bought a new Cisco Catalyst6509 switch a few days ago and was equipped with WS-X6548-GE-TX, a 10M, 100M, and 1000M adaptive 48-port RJ-45 switch module that Cisco launched in April last year. 6509 has 9 slots in total, so 9 modules can be inserted. It is common to add modules to upgrade core equipment. However, since Cisco's software launch always lags behind the hardware, the 12.2 (14) SX1 version of the IOS that has been equipped with the standard configuration of Catalyst6509 switch cannot support this module. This involves the upgrade issue, and it is necessary to upgrade the IOS of the 6509 switch. So my sub-department network administrator and I found a new version of IOS that supports the WS-X6548-GE-TX module from the official CISCO website to prepare for upgrade. Unexpectedly, this simple upgrade work lacked trouble for us two "quasi-economic experts" and problems arose one after another.
2. No RJ-45 interface
The WS-X6548-GE-TX module used this time has a total of 48 RJ-45 ports, but the 6509 switch does not have other modules with RJ-45 interfaces. What should I do? After all, to upgrade IOS with Cisco's TFTP Server, you must connect the switch to a PC with TFTP Server on the network. After some searching, I finally found that there was an RJ-45-shaped interface on the Super Engine 720, with the words Link written next to it. As a result, I used it to plug it in the network cable and found that the indicator lights were not on. Originally, we thought there was hope, but the indicator light did not light up, which means that the interface could not be used. However, because this interface is the only hope, otherwise we can only use xmodem to transmit 41MB of IOS, and the transmission time may be discouraged.
Tips:
Using XMODEM to transmit IOS is very troublesome. The author once used XMODEM to transmit the IOS of a 2950 switch, with a total capacity of only about 2MB, which took two hours. At this speed, 41MB can take at least 30 hours.
Since it is not realistic to use XMODEM to transmit IOS, we must start with the RJ-45-like interface on the Super Engine 720. From searching online, it turns out that there are two modes for port2 on the super engine 720: one is the RJ-45 interface, and the other is the SFP (a small form-factor pluggable) interface. The default setting is SFP, and to use the RJ-45 interface, you must change the settings. Enter the following command to modify—
Router(config)#interface gigabitethemet 5/2
//Enter this interface to set
Router(config-if)#media-type rj45
//Modify the mode to RJ45, default is SFP
Router(config-if)#no shutdown
//Enable this interface
After executing the command, I found that the orange indicator light finally turned green. Next, you can use the traditional TFTP method to pass the IOS files required for the upgrade to the switch. I thought the next thing should be easy, but who knew that the obstacles did not stop there.
3. TFTP transmission protocol does not support 32 megabytes
Next, assign the interface with the management address and back up the original IOS. Enter the command in HyperTerminal Global Mode:
Router#copy sup-rootflash: s72033-pk9sv-mz.122-14. tftp://192.168.1.1
A series of # font sizes appeared in TFTP Server and began to transmit data. I thought everything was OK. Who knew that when the transmission was about to be completed, the system prompted: "timeout! Write error!"
According to the system prompts, I checked whether the network cable was broken and whether the disk space was insufficient. The answer was no. The failure of executing the transmission command again remains. The size of the transferred IOS is 32MB on 6509, which is slightly smaller than the full IOS32.1MB. Why can't the extra 0.1MB be transmitted?
At first I thought it was because of the problem with the TFTP software and the version was too low. I downloaded a third-party TFTP server from the Internet and tried it, but the result was still the same. I found 3Com's TFTP Server, and the effect was even worse this time. It was disconnected when it reached 16MB. The system prompted that it was still timeout and write errors. After careful analysis, I finally found the key to the problem. The two transmissions are exactly 32MB and the other is exactly 16MB. The number of hyphens is not bad, so it is definitely not a problem with the transmission line. After searching for information, it turned out that the TFTP (Trivial File Transfer Protocol) ordinary file transfer protocol supports the maximum transfer of 32MB files. So I found Cisco Documents again, searched for a while, and found the second solution, just use FTP. So build the FTP service on your PC and type the following command:
Router# configure terminal
//Enter switch configuration mode
Router(config)# ip ftp username username
//Set the FTP access username
Router(config)# ip ftp password password
//Set the password for logging in to FTP
Touter(config)# end
//End, Exit
Router#copy sup-bootflash: s72033-pk9sv-mz.122-14. ftp:[//[username[:password]@]192.168.1.1]
//Execute the FTP transmission command, the transmission file is s72033-pk9sv-mz.122-14. The established FTP server address is 192.168.1.1.
After updating IOS with FTP transfer, the file copying is very normal. After waiting for a few minutes, the system prompts "successful!". It seems that FTP is more powerful and flexible than TFTP, and has much fewer restrictions.
Fourth, protocol error
After successfully backing up the IOS to FTP, it is your turn to upload the new IOS for upgrade. Enter the 6509 configuration mode and use the following commands to operate:
Router# configure terminal
//Enter configuration mode
Router(config)#ip ftp username username
//Set up users who log in to FTP
[1][2] Next page
Article entry: csh Editor in charge: csh
Router(config)#ip ftp password password
//Set the password for logging in to FTP
Router(config)#end
//Exit settings
Router# copy ftp:[[//[username[:password]@192.168.1.1] / s72033-jk9o3sv-mz.] sup-bootflash:
//Copy the new version of s72033-jk9o3sv-mz. to this switch.
I thought it was done easily, but this time the system prompted "Protocol error!". Protocol error? Try again, there is no problem with downloading, and uploading still prompts a protocol error. After analysis, I suspect that the problem may be on FTP Server. My FTP Server is made with Server-U, a third-party software. Could it be caused by compatibility issues? So I changed it to Microsoft Windows 2000's own FTP component in IIS to build an FTP server. There is no problem with trying to download and upload again, and no longer prompts for a protocol error. The screen shows Loading…. A few seconds later, another prompt message appeared: "There is insufficient Flash space".
Five, there is insufficient Flash space
After the FLASH space insufficient information appeared, I specifically checked the hardware configuration of the 6509 core device. The default Flash standard configuration of 6509 is 64MB, the standard IOS size is 32.1MB, and the 12.2 (17a) SX version to be upgraded is 40.6MB, so it seems that insufficient space is inevitable. However, this problem is relatively easy to solve. Delete the original IOS in Flash and upload it. So enter the command:
Router#delete sup-bootflash:s72033-pk9sv-mz.122-14.
Then pass it again. The prompt message is still insufficient space! At this time, I have deleted the switch's IOS. If the power is accidentally dropped or restarted, the switch will not be able to get up. In the management interface, use the show command to see that the IOS file is gone, but the space is still more than 30 megabytes, which means that the flash has not been cleared. At this time, I remembered that I had to restart the switch after deleting the file before it could take effect, but now it is absolutely impossible to restart. what to do? I searched for useful information on Cisco's website and finally found a command squeeze, which completely cleared the deleted files, just like clearing the recycling bin. run:
Router#squeeze sup-bootflash: Then use the SHOW command to check it out and found that Flash has been completely cleared and the available space is 64MB. At this time, use FTP to upload, and in a few minutes you will see the success message prompted on the screen. Reload it and use the show flash command to see that the IOS version has become 12.2 (17a) SX. Plug in the new module WS-X6548-GE-TX and try it. Everything is OK and the new module can run normally.
Summary of experience:
I originally thought that the work that was easy to complete was full of twists and turns, but it seemed that the upgrade of high-end products was also very complicated, and many links that were not paid attention to would have problems of one kind or another. This troubleshooting made me understand a truth. The technology has no end, and it is best to go to the official website to query when encountering problems. Also, you must think twice before doing things. If you take it for granted after deleting FLASH, the switch will not be able to start, and the consequences will be very serious. Please stop thinking for 30 seconds before the operation can often reduce many unnecessary losses.
Previous page [1][2]
Article entry: csh Editor in charge: csh