Search this Blog

Tuesday, November 27, 2012

What are the steps to upgrade IOS for VSS 6509 switches?

We have 2 6509 switches configured with VSS. We would like to enable SSH but it is not available existing IOS which is "s72033-ipbase-mz.122-33.SXI3.bin". SSH available in "s72033-ipbasek9-mz.122-33.SXI10".

Please advise step by step procedure for upgrade the IOS with VSS configured switches.


Here are the steps to upgrade IOS for VSS 6509 
1.  Copy the IOS from the TFTP to the active blade supervisor card:  copy tftp:///IOS.bin sup-bootflash:
2.  Copy the IOS from the TFTP to the secondary blade supervisor card:  copy tftp:///IOS.bin slavesup-bootflash:
3.  Go to enable mode and change the bootstring/boot variable.
NOTE:  In this step, what we've done is specify that the chassis boot the NEW IOS and also specify that the chassis boot the old or existing IOS in case the first one fails.

conf t
NO boot system flash sup-bootdisk:OLD_IOS.bin
boot system flash sup-bootdisk:NEW_IOS.bin
boot system flash sup-bootdisk:OLD_IOS.bin
end
copy run start
reboot

Please click here for Cisco IOS In-Service Software Upgrade procedures from Cisco. 


Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

Sunday, November 18, 2012

Wake on LAN across a corporate environment


How do you setup wol in an environment where there are about 8 sites all connected on a private MPLS.
Each site has 20 - 50 PC's on it. We have been asked to configure the Cisco equipment to allow from a single place the ability to wake any PC at any office. We have looked at various documents on the Cisco website, but we are still not quite sure.

- start on the router connecting the subnet where the WoL source is located.
- determine what protocol port number is to be used for WoL.
- configure an ip forward-protocol to match that protocol port.
- configure an ip helper-address for every remote subnet which needs to receive WoL. (this is the most tedious of the steps since you need one per remote subnet)
- then on each remote router where WoL will be received configure an ip directed-broadcast on each interface where clients are connected that will receive WoL.

Depending on how concerned you are with security issues you may want to make use of the optional capability to configure an access list to control the directed broadcast to limit it to WoL.

In summary
- you need an ip forward-protocol statement to match the protocol port that will be used for WoL (frequently it is port 6 but depending on the server it might be something different).
- you need an ip helper-address configured on the source subnet for each destination subnet to forward the WoL as a broadcast to the remote subnet.
- you need an ip directed-broadcast on each remote subnet to permit forwarding of the WoL packet onto the subnet as a broadcast.


Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.
 
/* Google Analytics begin ----------------------------------------------- */ /* Google Analytics end ----------------------------------------------- */