01-07-2011 08:43 AM
We've just received a new CSS and would like to configure a redundancy between this one and the legacy CSS. The legacy CSS is running IOS 8.2 - can we just bring the new CSS to this IOS level and then do a fail-over from the legacy CSS to the new one to sync them up?
Thanks..
Solved! Go to Solution.
01-12-2011 07:46 AM
Yes, you can load last CSS sw image on the new CSS and then sync them.
Please be aware that on the CSS, for every redundancy type, the configuration synchronization is always invoked manually through the execution of a script.
Before being able to run the sync script it is necessary to have configured an “app session”
#app
#app session
After setting up the app session you just invoke the script from the master CSS, for instance:
#script play commit_vip_redundancy "arguments"
In theory it is able to trigger the failover for every VR on his own but is better to be already in the correct mastership condition.
An additional remark, by default circuit and interface config is not synced.
Check this link for more details:
01-16-2011 02:52 PM
A couple of other notes about CSS redundancy (and upgrading).
CSS software has a built-in ftp server. In some case this makes it easier to upload the software image (not an IOS image but rather an ADI file or Arrowpoint Distribution Image - an artifact of the company that Cisco bought to establish this line of equipment) since you can simply "ftp put" the file onto the css.
Once you have a redundant pair set up, be careful to check when logging in that you are on the master (show redundancy will give you this and other information). They run as an active/standby pair and only on the active (master) unit will services show as active. This can be alarming if, for instance, you log into the unit that is in standby state and "show service xxx"" and see your service as down.
Hope this helps. Please rate helpful posts.
01-12-2011 07:46 AM
Yes, you can load last CSS sw image on the new CSS and then sync them.
Please be aware that on the CSS, for every redundancy type, the configuration synchronization is always invoked manually through the execution of a script.
Before being able to run the sync script it is necessary to have configured an “app session”
#app
#app session
After setting up the app session you just invoke the script from the master CSS, for instance:
#script play commit_vip_redundancy "arguments"
In theory it is able to trigger the failover for every VR on his own but is better to be already in the correct mastership condition.
An additional remark, by default circuit and interface config is not synced.
Check this link for more details:
01-16-2011 02:52 PM
A couple of other notes about CSS redundancy (and upgrading).
CSS software has a built-in ftp server. In some case this makes it easier to upload the software image (not an IOS image but rather an ADI file or Arrowpoint Distribution Image - an artifact of the company that Cisco bought to establish this line of equipment) since you can simply "ftp put" the file onto the css.
Once you have a redundant pair set up, be careful to check when logging in that you are on the master (show redundancy will give you this and other information). They run as an active/standby pair and only on the active (master) unit will services show as active. This can be alarming if, for instance, you log into the unit that is in standby state and "show service xxx"" and see your service as down.
Hope this helps. Please rate helpful posts.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide