Behalf Of Jeff Wojciechowski
Sent: Thursday, June 11, 2009 4:24 PM
To: Ryan West
Cc: cisco-nsp@puck.nether.net
Subject: Re: [c-nsp] ASA 5510 Configuration Replication Failure
Ryan -
Solved... for now at least...
Still using straight thru cable for synch interface I upgraded to 8.21 - based
on the
Ryan -
Solved... for now at least...
Still using straight thru cable for synch interface I upgraded to 8.21 - based
on the following bug IDs:
CSCsu88174
CSCsw98373
CSCsy21727
CSCsz63217
For the record the sh run | inc fail:
failover lan unit primary
failover lan interface failover Ethernet0/3
g a crossover or does it connect to
a switch?
-ryan
-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Jeff Wojciechowski
Sent: Thursday, June 11, 2009 12:38 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] ASA 5510 Configurati
.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Jeff Wojciechowski
Sent: Thursday, June 11, 2009 12:38 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] ASA 5510 Configuration Replication Failure
Dearest List:
We are building a new active/standby ASA cluster with 5510's and
Subject: [c-nsp] ASA 5510 Configuration Replication Failure
To: "cisco-nsp@puck.nether.net"
Date: Thursday, June 11, 2009, 9:37 AM
Dearest List:
We are building a new active/standby ASA cluster with 5510's and the initial
config synch went just fine.
However, when we changed the
using a crossover or does it connect to
a switch?
-ryan
-Original Message-
From: cisco-nsp-boun...@puck.nether.net
[mailto:cisco-nsp-boun...@puck.nether.net] On Behalf Of Jeff Wojciechowski
Sent: Thursday, June 11, 2009 12:38 PM
To: cisco-nsp@puck.nether.net
Subject: [c-nsp] ASA 5510
nal Message-
> From: cisco-nsp-boun...@puck.nether.net [mailto:cisco-nsp-
> boun...@puck.nether.net] On Behalf Of Jeff Wojciechowski
> Sent: Thursday, June 11, 2009 12:38 PM
> To: cisco-nsp@puck.nether.net
> Subject: [c-nsp] ASA 5510 Configuration Replication Failure
>
> D
Dearest List:
We are building a new active/standby ASA cluster with 5510's and the initial
config synch went just fine.
However, when we changed the hostname on the primary unit and did a 'write
standby' I got the following:
VaultASA(config)# wr stan
Building configuration...
[OK]
VaultASA(con
