CSS Box to Box - Redundancy

Unanswered Question
Apr 28th, 2008

We have two CSS running in box to box redundancy in two-arm (router mode) on code 8.10.40. Master is running with ip redundancy master (causing it to always be master if it is up and running).

We had a need to reload a previous configuration. To do this I copied the configuration to startup-config under running boot-file. I then ran command copy start run (on the master). After doing so, we lost all VIPs, although servers on second arm of CSS were accesible as well as the interface on the same network as the VIPs.

There is a 6509 switch between our CSS and the Firewall (firewall's are running in same mode - box to box). Firewall team saw traffic destined for the VIPs leave their interface, but we never saw it hit the CSS. I think that we had an ARP issue, but nobody can attest to this 100%. We had to reboot both CSS's to get VIPs to respond properly.

What would be the normal expectations in this scenario?

What is best practice to reload a configuration?

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
Gilles Dufour Tue, 04/29/2008 - 05:17

the copy start run does not erase the running config. So, it tries to add whatever config you had in startup on top of the running config.

Personally I would have simply done a reload once the config was in startup.

Gilles.

Actions

This Discussion