Vswitch upgrade troubleshooting instance (1)

Network administrators of various companies carefully select network devices and conduct repeated research between different vendors of the same level. After multiple comparisons, they can select the most cost-effective products. However, many network administrators may ignore this issue, that is, the future of network products. If a product cannot be used for a long time, the service provided by the manufacturer becomes especially important. Similarly, network technologies are constantly evolving, and network products must be scalable and scalable. Recently, I encountered a problem with upgrading the core device. The record is as follows:
I. Upgrade the environment
The reason for this is that the company's subordinate departments have applied for certain funds for network upgrades, so the department bought a new Cisco ipvst12009 switch a few days ago, and equipped with WS-X6548-GE-TX, CISCO launched a new 10 M, 100 M, M Adaptive 48-port RJ-45 Switching Module in last April. 6509 has a total of 9 slots, so you can plug in 9 modules, it is common to upgrade and add modules for core devices. However, because Cisco Software is always lagging behind hardware, IOS 12.2 (14) SX1, which is the standard configuration of ipvst3169, cannot support this module. This involves the upgrade problem. You need to upgrade ios of the 6509 switch. So I and the sub-department network administrator from the CISCO official website to support the new version of the WS-X6548-GE-TX module IOS preparation upgrade. I did not think that the lack of this simple upgrade caused two "quasi-Masters" to be connected and the problem emerged one after another.
2. There is no RJ-45 Interface
For this use of this WS-X6548-GE-TX module A total of 48 RJ-45 port, but the 6509 switch and no other with RJ-45 interface module. What should I do? After all, to upgrade IOS with Cisco's TFTP Server, the switch must be connected to a PC with a TFTP Server installed on the network. After some look, finally found that the super engine 720 on a RJ-45 interface, next to the words Link, the results of the network cable inserted a try, found that the indicator light is not on. The two of us thought there was hope. However, if the indicator light is not on, this interface cannot be used. However, this interface is the only hope. Otherwise, we can only transmit the 41MB IOS using xmodem, I am afraid the transmission time is prohibitive.
TIPS:
The speed of using XMODEM to transmit IOS is a headache. I used XMODEM to transmit a 2950 switch IOS, with a total capacity of about 2 MB. It took two hours. At this speed, it may take up to 30 hours for 41 MB.
Since the use of XMODEM transmission IOS is not realistic, but also from the super engine 720 above that RJ-45 interface. From the Internet to the relevant information, the original super engine 720 port2 has two modes: one is the RJ-45 interface, and one is SFP (a small form-factor pluggable) interface. The default setting is SFP, which must be changed to use the RJ-45 interface. Enter the following command to modify --
Router (config) # interface gigabitethemet 5/2
// Enter this interface to set
Router (config-if) # media-type rj45
// Change the mode to RJ45. The default value is SFP.
Router (config-if) # no shutdown
// Enable this interface
After running the command, the orange indicator turns green. Then, you can use the traditional TFTP method to upload the IOS file required for the upgrade to the switch. I thought that the next thing should be very easy. Who knows that we didn't stop it.
3. TFTP transmission protocol does not support 32 MB
Next, add the management address to the interface and back up the original IOS. In global mode of the Super Terminal, enter the following command:
Router # copy sup-rootflash: s72033-pk9sv-mz.122-14.SX1.bin tftp: // 192.168.1.1
The TFTP Server has a series of # font sizes and starts to transmit data. It thought everything was okay. Who knows the system prompts "timeout! Write error !".
Based on the information prompted by the system, I checked whether the network cable is disconnected or the disk space is insufficient. The answer is no. If the command is run again, the fault persists. To 6509, check that the size of the transmitted IOS is 32 MB, which is slightly smaller than the complete IOS32.1MB. Why is it impossible to transfer an extra 1 MB?
At first, I thought there was a problem with the TFTP software, and the version was too low. Download a third-party TFTP server from the Internet and try again. The TFTP Server of 3Com is found again. The effect is worse this time. It is disconnected when it is uploaded to 16 MB, and the system prompts that it is still time-out and write error. After careful analysis, we finally found the key to the problem. Two transfers, 32 MB at a time, 16 MB at a time, and even the number of bytes, are certainly not a problem with the transmission line. After checking the information, TFTP (Trivial File Transfer Protocol) supports transferring up to 32 MB files. So I searched for the Cisco Document and found 2nd solutions. I just needed to use FTP. Set up the FTP service on the PC and enter the following command:
Router # configure terminal
// Enter Switch configuration mode
Router (config) # ip ftp username
// Set the FTP access Username
Router (config) # ip ftp password
// Set the FTP logon Password
Touter (config) # end
// End and exit
Router # copy sup-bootflash: s72033-pk9sv-mz.122-14.SX1.bin ftp: [// [username [: password] @] 192.168.1.1]
// Execute the FTP transfer command, the transfer file is the s72033-pk9sv-mz.122-14.SX1.bin, the established FTP server address is 192.168.1.1.
After IOS is updated through FTP transmission, the file copy is normal. After several minutes, the system prompts "successful !". It seems that FTP is more powerful and flexible than TFTP, with fewer restrictions.