Options

Active unit and PDM warning replication message

zillahzillah Member Posts: 42 ■■□□□□□□□□
I have got two PIXs, Primary and Secondary

Primary (192.168.100.1) is Standby
Secondary (192.168.100.2) is Active

When I try to access the PDM from primary (Standby) I could not, but I was able to access PDM for Secondary (Active)

Secondary’s PDM Tools --> Command Line Interface --> config terminal,,,,I received this error message
Result of firewall command: "config ter"
 
**** WARNING *** 
	Configuration Replication is NOT performed from Standby unit to Active unit.
	Configurations are no longer synchronized.

1- In the above message why it says Standby unit ?, while I have issued the command (config terminal ) within Active unit, not Standby unit

2- How can I find user privilege level from within PDM ?


PIX# show failover
Failover On
Cable status: Normal
Reconnect timeout 0:00:00
Poll frequency 15 seconds
Last Failover at: 00:53:35 UTC Sat Nov 11 2006

This host: Secondary - Active
Active time: 4705650 (sec)
Interface outside (10.1.1.130): Normal (Waiting)
Interface inside (192.168.100.1): Normal
!
!
!
Other host: Primary - Standby
Active time: 15838095 (sec)
Interface outside (192.168.105.2): Normal (Waiting)
Interface inside (192.168.100.2): Normal



This is the backup configuration (not current one):
PIX# show failover
Failover On
Cable status: Normal
Reconnect timeout 0:00:00
Poll frequency 15 seconds
Last Failover at: 02:46:02 UTC Mon Oct 4 1993
This host: Primary - Active
Active time: 15931095 (sec)
Interface outside (10.1.1.130): Normal (Waiting)
Interface inside (192.168.100.1): Normal


Other host: Secondary - Standby
Active time: 4761990 (sec)
Interface outside (192.168.105.2): Normal (Waiting)
Interface inside (192.168.100.2): Normal

Stateful Failover Logical Update Statistics
Link : Unconfigured.[/b]

Comments

  • Options
    AhriakinAhriakin Member Posts: 1,799 ■■■■■■■■□□
    Sorry don't have time to spend on this but quickly: The Command Line from within the PDM is always in config mode, you don't enter any extra commands to get there. Best thing to do to discover the privilege is do SH CURPRIV from the command line tool.
    We responded to the Year 2000 issue with "Y2K" solutions...isn't this the kind of thinking that got us into trouble in the first place?
Sign In or Register to comment.