Good advice below re: failover...hehe.
I always make a term emu capture and a tftp backup. The tftp file will let
you get back up and moving much quicker.
tv
----- Original Message -----
From: "Velasquez Venegas Jaime Omar" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[email protected]>
Sent: Friday, August 29, 2008 1:50 PM
Subject: Re: [c-nsp] FWSM module replacement
Always it's handy to have a backup of all your current configuration
files (i.e system config and all of the other contexts).If something
unexpected comes up it's fairly easy to replace a blank configuration
file.
-----Mensaje original-----
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] En nombre de Ge Moua
Enviado el: Friday, August 29, 2008 8:27 AM
Para: 'Brett Clausenhauf'; [email protected]
Asunto: Re: [c-nsp] FWSM module replacement
Be careful here (as I've made this mistake already):
* Set the good fwsm to 'primary - active'
* before you bring up the fail-over link, set the replacement to
'secondary
- standby'
* as soon as you bring up the fail-over link the sync happens
automatically
* you can changet to unit desgination after this
* be carefule not to bring the replacement unit online in 'primary -
active', otherwise the a blank config will be syced between them (this
is bad, & I've done this before).
Good luck.
Regards,
Ge Moua | Email: [EMAIL PROTECTED]
Network Design Engineer
University of Minnesota | Networking & Telecommunications Services
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brett
Clausenhauf
Sent: Friday, August 29, 2008 3:37 AM
To: [email protected]
Subject: [c-nsp] FWSM module replacement
Hi Guys,
Shortly I need to replace a FWSM module in a 6500. It is paired with
another FWSM module which is now the active module.
Looking at this below url it seems to be a straight forward process to
replace the module & to get the configuration sync'ed.
http://www.cisco.com/en/US/docs/security/fwsm/fwsm22/configuration/guide
/upg
rade.html#wp1036343
One thing is not clear though. The module that died is usually the
primary module, whilst the current active module is in standby.. If I
issue the command "Failover" in step 5 after I define the replacement
module with all the basic failover variables including the unique
variable of *fail lan unit Primary will this cause it to override the
configuration in the
currently active FWSM with that of the newly installed FWSM? I presume
not, although I am not 100 percent sure here.*
**
Regards,
Brad
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
_______________________________________________
cisco-nsp mailing list [email protected]
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/
