UCCX Active / Standby server

Hello,
We have UCCX HA pair. I am trying to find out the current active and standby server. How can I do this? How do I know which of the 2 server is Active and Standby. Also, which server should be active? Should Publisher be Active? or Subscriber be active?
Thank You,

It doesn't matter which server is active. Both will work. I try to keep my publisher the active (master) server as this is what the CAD clients are configured to connect to first.
To find out which one is currently the master, log in to Cisco Unified CCX Serviceability (from drop down menu in top right of appadmin), select tools --> control centre. Select your node, if the CCX Engine has a blue box with an M - it is currently the master. If it is an S, it is currently the slave.
Brian

Similar Messages

CSS active/standby server loadbalancing

Hello All
I have client that want to use the CSS to loadbalance only to thier active server and if that server fails then send requests to the standby server.
I have told them that using the CSS to acomplish this is not the best use of it functionallity but they want to do it anyway. Does anybody know how this can be done.
I know the CSS will send keepalives to the particular service to ensure it is available and was wondering if I could use these to detect the primary server failure and then start sending traffic to the secondary.
I do not want to loadbalance to both servers I only want to forward traffic to the secondary server if the primary fails.
Regards
Paul Le Grange

Hi,
you can accomplish this by using a sorryserver.
configure you content rule, add your active service using "add service server1" and add you standby service (which will be only used when the active service goes down) using "primarySorryServer server2".
See the config guide for more info: http://www.ciscopress.info/en/US/docs/app_ntwk_services/data_center_app_services/css11500series/v7.40/configuration/content_lb/guide/contrule.html#wp1038009
HTH,
Dario

UCCX 8.0 SNMP notification to report failover from active to the standby server?

Does any know the UCCX 8.0 SNMP notification to report failover from active to the standby server? (The specific notification.)
ftp://ftp.cisco.com/pub/mibs/v2/CISCO-VOICE-APPS-MIB.my
I see this in the MIB.
cvaModuleStart NOTIFICATION-TYPE
OBJECTS   { cvaAlarmSeverity, cvaModuleName }
STATUS    current
DESCRIPTION
        "A cvaModuleStart notification signifies that an
        application module or subsystem has successfully
        started and transitioned into in-service state.
        This notification is working in conjunction with
        the cvaModuleStop notification to notify the start
        and stop status of a particular application module."
::= {ciscoVoiceAppsMIBNotifications 1}

Attached are two files:
cad-ecc-viewer.html
This is a template HTML document which dictates how the pop up will look and what data fields are available.
cad-ecc-viewer.vbs
This is the Windows Scripting Host file which you run from a CDA workflow, and you pass it the values of the call data, it then launches an instance of IE and loads the above template.
By default the code is setup to use the following data from the call, but can be modified to work with more, less, or different data:
Customer Name
Customer Status (like Premium, or Platinum)
Customer Number (like an account number)
Customer Phone Number
So when you specify the VBS file to run in CDA you need to pass those variables in that order.
The CDA should expect the VBS file on the root of C:\ by default, and the VBS file expects the HTML Template on the root of C:\ also.
I have only tested this on UCCX 7x and IE 8x. Use the code as a guide to your own solution, that suites your business requirements.
EDIT: I see that this does not work on my Win7/IE9 system, so I will spend some time updating the code for Win7/IE9 and I'll let you know how it goes.
Anthony Holloway
Please use the star ratings to help drive great content to the top of searches.

ASA 5520 VPN load balancing with Active/Standby failover on 2 devices only...

/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-qformat:yes;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:10.0pt;
mso-para-margin-left:0in;
line-height:115%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-fareast-font-family:"Times New Roman";
mso-fareast-theme-font:minor-fareast;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
This topic has been beat to death, but I did not see a real answer. Here is configuration:
1) 2 x ASA 5520, running 8.2
2) Both ASA are in same outside and inside interface broadcast domains – common Ethernet on interfaces
3) Both ASA are running single context but are active/standby failovers of each other. There are no more ASA’s in the equation. Just these 2. NOTE: this is not a Active/Active failover configuration. This is simply a 1-context active/standby configuration.
4) I want to share VPN load among two devices and retain active/standby failover functionality. Can I use VPN load balancing feature?
This sounds trivial, but I cannot find a clear answer (without testing this); and many people are confusing the issue. Here are some examples of confusion. These do not apply to my scenario.
Active/Active failover is understood to mean only two ASA running multi-contexts. Context 1 is active on ASA1 Context 2 is active on ASA2. They are sharing failover information. Active/Active does not mean two independently configured ASA devices, which do not share failover communication, but do VPN load balancing. It is clear that this latter scenario will work and that both ASA are active, but they are not in the Active/Active configuration definition. Some people are calling VPN load balancing on two unique ASA’s “active/active”, but it is not
The other confusing thing I have seen is that VPN config guide for VPN load balancing mentions configuring separate IP address pools on the VPN devices, so that clients on ASA1 do not have IP address overlap with clients on ASA2. When you configure ip address pool on active ASA1, this gets replicated to standby ASA2. In other words, you cannot have two unique IP address pools on a ASA Active/Standby cluster. I guess I could draw addresses from external DHCP server, and then do some kind of routing. Perhaps this will work?
In any case, any experts out there that can answer question? TIA!

Wow, some good info posted here (both questions and some answers). I'm in a similar situation with a couple of vpn load-balanced pairs... my goal was to get active-standby failover up and running in each pair- then I ran into this thread and saw the first post about the unique IP addr pools (and obviously we can't have unique pools in an active-standby failover rig where the complete config is replicated). So it would seem that these two features are indeed mutually exclusive. Real nice initial post to call this out.
Now I'm wondering if the ASA could actually handle a single addr pool in an active-standby fo rig- *if* the code supported the exchange of addr pool status between the fo members (so they each would know what addrs have been farmed out from this single pool)? Can I get some feedback from folks on this? If this is viable, then I suppose we could submit a feature request to Cisco... not that this would necessarily be supported anytime soon, but it might be worth a try. And I'm also assuming we might need a vip on the inside int as well (not just on the outside), to properly flip the traffic on both sides if the failover occurs (note we're not currently doing this).
Finally, if a member fails in a std load-balanced vpn pair (w/o fo disabled), the remaining member must take over traffic hitting the vip addr (full time)... can someone tell me how this works? And when this pair is working normally (with both members up), do the two systems coordinate who owns the vip at any time to load-balance the traffic? Is this basically how their load-balancing scheme works?
Anyway, pretty cool thread... would really appreciate it if folks could give some feedback on some of the above.
Thanks much,
Mike

Standby server - WAIT_FOR_GAP error

Hi,
I have a Oracle Dataguard 10.2 running on Windows and found a WAIT_FOR_GAP error on the standby server.
--> alert log of standby
Sun Jan 30 20:00:04 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
MRP0 started with pid=18, OS id=2452
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 3 processes
Sun Jan 30 20:00:13 2011
Waiting for all non-current ORLs to be archived...
Clearing online redo logfile 10 E:\ORACLE\A30\ORIGLOGA\LOG_G10_M1.DBF
Clearing online log 10 of thread 1 sequence number 17848
Sun Jan 30 20:00:13 2011
Errors in file z:\oracle\a30\saptrace\background\a30_mrp0_2452.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 10 thread 1: 'E:\ORACLE\A30\ORIGLOGA\LOG_G10_M1.DBF'
Clearing online redo logfile 10 complete
Media Recovery Log L:\ORACLE\A30\ORAARCH\A30ARCH\ARC17856_0681431456.001
Sun Jan 30 20:00:13 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Sun Jan 30 20:00:33 2011
Media Recovery Waiting for thread 1 sequence 17857
Sun Jan 30 20:51:19 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[636]: Assigned to RFS process 4976
RFS[636]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
Sun Jan 30 20:51:20 2011
Fetching gap sequence in thread 1, gap sequence 17857-17863
Sun Jan 30 20:51:20 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[637]: Assigned to RFS process 4012
RFS[637]: Identified database type as 'physical standby'
Sun Jan 30 20:52:20 2011
RFS[637]: Archived Log: 'L:\ORACLE\A30\ORAARCH\A30ARCH\ARC17864_0681431456.001'
Sun Jan 30 20:56:34 2011
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 17857-17863
DBID 3371425568 branch 681431456
FAL[client]: All defined FAL servers have been attempted.
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Sun Jan 30 22:00:44 2011
RFS[636]: Archived Log: 'L:\ORACLE\A30\ORAARCH\A30ARCH\ARC17865_0681431456.001'
Primary database is in MAXIMUM PERFORMANCE mode
SQL> select process,sequence#,status from v$managed_standby;
PROCESS    SEQUENCE# STATUS
ARCH               0 CONNECTED
ARCH               0 CONNECTED
MRP0           17857 WAIT_FOR_GAP
RFS                0 IDLE
RFS                0 IDLE
RFS                0 IDLE
SQL> select * from v$archive_gap;
   THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
         1         17857          17863
SQL> select sequence#,applied from v$archived_log order by sequence#;
SEQUENCE# APP
     17855 YES
     17856 YES <--- Gap here
     17864 NO
     17865 NO
     17866 NO
     17867 NO
     17868 NO
     17869 NO
     17870 NO
     17871 NO
     17872 NO
SEQUENCE# APP
     17873 NO
     17874 NO
     17875 NO
     17876 NO
     17877 NO
     17878 NO
     17879 NO <--- Gap here
     17889 NO
     17890 NO
     17891 NO
     17892 NO
SEQUENCE# APP
     18067 NO
     18068 NO
     18069 NO
     18070 NO
     18071 NO
     18072 NO
4032 rows selected.
--> alert log of primary
Sun Jan 30 20:00:03 2011
Incremental checkpoint up to RBA [0x45c8.1f6c6.0], current log tail at RBA [0x45c8.1f7f5.0]
Sun Jan 30 20:05:04 2011
ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
Sun Jan 30 20:30:11 2011
Incremental checkpoint up to RBA [0x45c8.201e2.0], current log tail at RBA [0x45c8.20215.0]
Sun Jan 30 20:51:12 2011
Destination LOG_ARCHIVE_DEST_2 is UNSYNCHRONIZED
LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
LNSb started with pid=50, OS id=1792
Sun Jan 30 20:51:19 2011
Destination LOG_ARCHIVE_DEST_2 no longer supports SYNCHRONIZATION
Beginning log switch checkpoint up to RBA [0x45c9.2.10], SCN: 276988485
Sun Jan 30 20:51:20 2011
Thread 1 advanced to log sequence 17865 (LGWR switch)
Current log# 17 seq# 17865 mem# 0: F:\ORACLE\A30\ORIGLOGB\LOG_G17_M1.DBF
Current log# 17 seq# 17865 mem# 1: E:\ORACLE\A30\MIRRLOGB\LOG_G17_M2.DBF
Sun Jan 30 20:51:20 2011
ARC1: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
Sun Jan 30 20:51:25 2011
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
Sun Jan 30 20:56:35 2011
Completed checkpoint up to RBA [0x45c9.2.10], SCN: 276988485

Hi,
I've seen that, if the following message persists for a long time, then it is an ERROR.
FAL[client]: Failed to request gap sequence GAP - thread 1 sequence 17857-17863 DBID 3371425568 branch 681431456 FAL[client]: All defined FAL servers have been attempted.
The possibility is that log shipping of 17857 is stuck. It is not stuck because of any network disconnect, as it is in the case you mentioned. It is probably due to the following.
The parameter LOG_ARCHIVE_DEST_1 on standby is set as L:\ORACLE\A30\ORAARCH\A30ARCH\ARC and STANDBY_ARCHIVE_DEST is also set to L:\ORACLE\A30\ORAARCH\A30ARCH\ARC. When a GAP is identified, standby database tries to pull the missing files FROM PRIMARY, and the in turn when you enable standby destination on primary (log_archive_dest_state_2 = enabled), it starts shipping logfiles on its OWN.
When such a situation occurs in a system when archived logs are generated at a high rate, it can happen that the file which standby is trying to pull is being pushed/already pushed by primary database. Then a conflict arise, and standby deletes the file and tries to pull it again...this may go on in a loop. (because the locations are SAME).
When i had this issue, I maintained different locations for LOG_ARCHIVE_DEST_1 and STANDBY_ARCHIVE_DEST on standby database. After this is done, you will find that the logs shipped by primary are written in STANDBY_ARCHIVE_DEST. The file written in this location will be used by the standby database only when you do a managed recovery. If you are doing a manual recovery by issuing the command RECOVER STANDBY DATABASE; then, the stanbdby database will check if the file exists in LOG_ARCHIVE_DEST_1.
The point is, when there is BIG gap, then you have the option of doing the following procedure.
1. On the primary database keep LOG_ARCHIVE DESTSTATE_2 = enable
2. On the standby ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL.
3. Copy the missing archive logs sequence from the primary to standby's LOG_ARCHIVE_DEST_1 and perform manual recovery on standby untill the gap is over.
4. issue the command ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT to start managed recovery. ( This will use the files present in STANDBY_ARCHIVE_DEST ).
Hope the above procedure helps.
Note: If the GAP is not that big and you see that last applied log is advancing, then conflict is not there...standby will automatically fill the GAP. But it is advised to maintain different location for the parameters i mentioned.
Regards,
Anish
Edited by: Mohammed Anish on Feb 10, 2011 6:48 AM

About stateful active/standby failover

Hello guys.
I have two ASA's, same model and hardware. Asa have configured stateful active/standby failover by someone, few years ago. It was working normally until recently and no one have changed this configuration. Then Secondary unit is failed. Ping between 2 interfaces is ok. Please help me to resolve this problem.
on Primary site
interface Management0/0
description STATE Failover Interface
management-only
interface GigabitEthernet1/1
description LAN Failover Interface
failover
failover lan unit primary
failover lan interface failover GigabitEthernet1/1
failover link state Management0/0
failover interface ip failover 172.16.1.1 255.255.255.0 standby 172.16.1.2
failover interface ip state 172.16.0.1 255.255.255.0 standby 172.16.0.2
on Secondary site
interface Management0/0
description STATE Failover Interface
management-only
interface GigabitEthernet1/1
description LAN Failover Interface
output of show failover on PRIMARY
show run failover
failover
failover lan unit primary
failover lan interface failover GigabitEthernet1/1
failover link state Management0/0
failover interface ip failover 172.16.1.1 255.255.255.0 standby 172.16.1.2
failover interface ip state 172.16.0.1 255.255.255.0 standby 172.16.0.2
F1# show failover
Failover On
Failover unit Primary
Failover LAN Interface: failover GigabitEthernet1/1 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 5 of 256 maximum
Version: Ours 8.2(2), Mate 8.2(2)
Last Failover at: 08:03:11 ULAST Jan 1 2003
        This host: Primary - Active
                Active time: 5755203 (sec)
                slot 0: ASA5550 hw/sw rev (2.0/8.2(2)) status (Up Sys)
                  Interface Backup2 (10.2.5.1): Normal (Waiting)
                  Interface Internet (202.131.225.90): No Link (Waiting)
                  Interface Backup1 (10.3.5.1): Normal (Waiting)
                  Interface Server (192.168.227.1): Normal (Waiting)
                  Interface Bank (10.20.1.1): Normal (Waiting)
                slot 1: ASA-SSM-4GE-INC hw/sw rev (1.0/1.0(0)10) status (Up)
      Other host: Secondary - Failed
                Active time: 0 (sec)
                slot 0: ASA5550 hw/sw rev (2.0/8.2(2)) status (Up Sys)
                  Interface Backup2 (0.0.0.0): No Link (Waiting)
                  Interface Internet (0.0.0.0): No Link (Waiting)
                  Interface Backup1 (0.0.0.0): Normal (Waiting)
                  Interface Server (0.0.0.0): Normal (Waiting)
                  Interface Bank (0.0.0.0): Normal (Waiting)
                slot 1: ASA-SSM-4GE-INC hw/sw rev (1.0/1.0(0)10) status (Up)
Stateful Failover Logical Update Statistics
        Link : state Management0/0 (up)
        Stateful Obj    xmit       xerr       rcv        rerr
        General         76184539   0          767513     6
        sys cmd         767328     0          767326     1
        up time         0          0          0          0
        RPC services    0          0          0          0
        TCP conn        25878669   0          11         5
        UDP conn        40545710   0          40         0
        ARP tbl         8987688    0          136        0
        Xlate_Timeout   0          0          0          0
        IPv6 ND tbl     0          0          0          0
        VPN IKE upd     1140       0          0          0
        VPN IPSEC upd   4004       0          0          0
        VPN CTCP upd    0          0          0          0
        VPN SDI upd     0          0          0          0
        VPN DHCP upd    0          0          0          0
        SIP Session     0          0          0          0
        Logical Update Queue Information
                        Cur     Max     Total
        Recv Q:         0       7       6522961
        Xmit Q:         0       34      106685671
output of show failover on SECONDARY
F1# show failover
Failover On
Failover unit Secondary
Failover LAN Interface: failover GigabitEthernet1/1 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 5 of 256 maximum
Version: Ours 8.2(2), Mate 8.2(2)
Last Failover at: 03:36:23 ULAST Dec 15 2013
       This host: Secondary - Failed
                Active time: 0 (sec)
                slot 0: ASA5550 hw/sw rev (2.0/8.2(2)) status (Up Sys)
                  Interface Backup2 (0.0.0.0): No Link (Waiting)
                  Interface Internet (0.0.0.0): No Link (Waiting)
                  Interface Backup1 (0.0.0.0): Normal (Waiting)
                  Interface Server (0.0.0.0): Normal (Waiting)
                  Interface Bank (0.0.0.0): Normal (Waiting)
                slot 1: ASA-SSM-4GE-INC hw/sw rev (1.0/1.0(0)10) status (Up)
        Other host: Primary - Active
                Active time: 5743217 (sec)
                slot 0: ASA5550 hw/sw rev (2.0/8.2(2)) status (Up Sys)
                  Interface Backup2 (10.2.5.1): Normal (Waiting)
                  Interface Internet (202.131.225.90): No Link (Waiting)
                  Interface Backup1 (10.3.5.1): Normal (Waiting)
                  Interface Server (192.168.227.1): Normal (Waiting)
                  Interface Bank (10.20.1.1): Normal (Waiting)
                slot 1: ASA-SSM-4GE-INC hw/sw rev (1.0/1.0(0)10) status (Up)
Stateful Failover Logical Update Statistics
        Link : state Management0/0 (up)
        Stateful Obj    xmit       xerr       rcv        rerr
        General         765518     0          35843181   874
        sys cmd         765518     0          765516     0
        up time         0          0          0          0
        RPC services    0          0          0          0
        TCP conn        0          0          12671303   80
        UDP conn        0          0          13432853   133
        ARP tbl         0          0          8968384    661
        Xlate_Timeout   0          0          0          0
        IPv6 ND tbl     0          0          0          0
        VPN IKE upd     0          0          1137       0
        VPN IPSEC upd   0          0          3988       0
        VPN CTCP upd    0          0          0          0
        VPN SDI upd     0          0          0          0
        VPN DHCP upd    0          0          0          0
        SIP Session     0          0          0          0
        Logical Update Queue Information
                        Cur     Max     Total
        Recv Q:         0       9       72011189
        Xmit Q:         0       1       765518

- ping is ok between 172.16.1.1 and 172.16.1.2, 172.16.0.1 and 172.16.0.2
- ASA that shows as failed the ASA that didn't use to be the primary , it used to be secondary.
- Yes, i logged via console on both ASAs and checked status of the ASAs. Primary is active and Secondary is failed.
- I have changed cable. Primary ASA indicates below as soon as cable changed.
Beginning configuration replication: Sending to mate.
End Configuration Replication to mate
Then output of SHOW FAILOVER on PRIMARY ASA :
F1# show failover
Failover On
Failover unit Primary
Failover LAN Interface: failover GigabitEthernet1/1 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 5 of 256 maximum
Version: Ours 8.2(2), Mate 8.2(2)
Last Failover at: 08:03:11 ULAST Jan 1 2003
        This host: Primary - Active
                Active time: 5812656 (sec)
                slot 0: ASA5550 hw/sw rev (2.0/8.2(2)) status (Up Sys)
                  Interface Backup2 (10.2.5.1): Normal (Waiting)
                  Interface Internet (202.131.225.90): No Link (Waiting)
                  Interface Backup1 (10.3.5.1): Normal (Waiting)
                  Interface Server (192.168.227.1): Normal (Waiting)
                  Interface Bank (10.20.1.1): Normal (Waiting)
                slot 1: ASA-SSM-4GE-INC hw/sw rev (1.0/1.0(0)10) status (Up)
       Other host: Secondary - Standby Ready
                Active time: 9 (sec)
                slot 0: ASA5550 hw/sw rev (2.0/8.2(2)) status (Up Sys)
                  Interface Backup2 (0.0.0.0): No Link (Waiting)
                  Interface Internet (0.0.0.0): No Link (Waiting)
                  Interface Backup1 (0.0.0.0): Normal (Waiting)
                  Interface Server (0.0.0.0): Normal (Waiting)
                  Interface Bank (0.0.0.0): Normal (Waiting)
                slot 1: ASA-SSM-4GE-INC hw/sw rev (1.0/1.0(0)10) status (Up)
Stateful Failover Logical Update Statistics
        Link : state Management0/0 (up)
        Stateful Obj    xmit       xerr       rcv        rerr
        General         76940782   0          775168     6
        sys cmd         774983     0          774981     1
        up time         0          0          0          0
        RPC services    0          0          0          0
        TCP conn        26125140   0          11         5
        UDP conn        40971274   0          40         0
        ARP tbl         9064174    0          136        0
        Xlate_Timeout   0          0          0          0
        IPv6 ND tbl     0          0          0          0
        VPN IKE upd     1155       0          0          0
        VPN IPSEC upd   4056       0          0          0
        VPN CTCP upd    0          0          0          0
        VPN SDI upd     0          0          0          0
        VPN DHCP upd    0          0          0          0
        SIP Session     0          0          0          0
        Logical Update Queue Information
                        Cur     Max     Total
        Recv Q:         0       7       6588043
        Xmit Q:         0       34      107757911
But few seconds later Secondary ASA become FAILED.
And i also did FAILOVER RESET command. After this command, secondary ASA became Standby Ready then few seconds later it became Failed again. Why does it become Failed again ?

Cisco ASA Active standby failover problem

We have configured ASA Active standby failover with ASA5505 . When primary unit power off, secondary unit became active. when primary unit power on, then primary unit is becoming active again. i think for active standby setup there is no preemption. The real issue is when primary ASA became active after power on all the external connectivity getting down. Please see the below config,
ASA01# show run
ASA01# show running-config
: Saved
ASA Version 8.2(5)
hostname ASA01
enable password PVSASRJovmamnVkD encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
name 192.168.1.1 MPLS_Router description MPLS_Router
name 192.168.2.1 SCADA_Router description SCADA_Router
interface Ethernet0/0
switchport access vlan 2
interface Ethernet0/1
interface Ethernet0/2
switchport access vlan 2
interface Ethernet0/3
interface Ethernet0/4
switchport access vlan 3
interface Ethernet0/5
interface Ethernet0/6
interface Ethernet0/7
interface Vlan1
nameif inside
security-level 100
ip address 192.168.3.8 255.255.255.0 standby 192.168.3.9
interface Vlan2
nameif outside
security-level 0
ip address 192.168.1.8 255.255.255.0 standby 192.168.1.9
interface Vlan3
description LAN Failover Interface
ftp mode passive
clock timezone AST 3
access-list inside_access_in extended permit icmp any any
access-list inside_access_in extended permit ip any any
access-list inside_access_in extended permit ip any host MPLS_Router
access-list outside_access_in extended permit icmp any any
access-list outside_access_in extended permit ip any any
access-list outside_access_in extended permit ip any 192.168.2.0 255.255.255.0
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
failover
failover lan unit primary
failover lan interface FAILOVER Vlan3
failover key *****
failover interface ip FAILOVER 10.1.1.1 255.255.255.0 standby 10.1.1.2
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0
access-group inside_access_in in interface inside
access-group outside_access_in in interface outside
route-map Route_Out permit 1
match ip address inside_access_in outside_access_in
match interface inside
route outside 0.0.0.0 0.0.0.0 MPLS_Router 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 192.168.1.0 255.255.255.0 inside
http 192.168.2.0 255.255.255.0 inside
http authentication-certificate inside
http authentication-certificate outside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec security-association lifetime seconds 28800
crypto ipsec security-association lifetime kilobytes 4608000
telnet 192.168.2.0 255.255.255.0 inside
telnet 192.168.1.0 255.255.255.0 outside
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
username admin password eY/fQXw7Ure8Qrz7 encrypted
prompt hostname context
no call-home reporting anonymous
call-home
profile CiscoTAC-1
no active
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination address email [email protected]
destination transport-method http
subscribe-to-alert-group diagnostic
subscribe-to-alert-group environment
subscribe-to-alert-group inventory periodic monthly
subscribe-to-alert-group configuration periodic monthly
subscribe-to-alert-group telemetry periodic daily
Cryptochecksum:1a8e46a787aa78502ffd881ab62d1c31
: end

I suggest removing the failover configuration on both units and then re-add them, and then test.
Primary
failover lan interface FAILOVER Vlan3
failover interface ip FAILOVER 10.1.1.1 255.255.255.0 standby 10.1.1.2
failover lan unit primary
failover key KEY
failover
Secondary
failover lan interface FAILOVER Vlan3
failover interface ip FAILOVER 10.1.1.1 255.255.255.0 standby 10.1.1.2
failover lan unit secondary
failover key KEY
failover
Please remember to select a correct answer and rate helpful posts

Best practice for ASA Active/Standby failover

Hi,
I have configured a pair of Cisco ASA in Active/ Standby mode (see attached). What can be done to allow traffic to go from R1 to R2 via ASA2 when ASA1 inside or outside interface is down?
Currently this happens only when ASA1 is down (shutdown). Is there any recommended best practice for such network redundancy? Thanks in advanced!

Hi Vibhor,
I test ping from R1 to R2 and ping drop when I shutdown either inside (g1) or outside (g0) interface of the Active ASA. Below is the ASA 'show' failover' and 'show run',
ASSA1# conf t
ASSA1(config)# int g1
ASSA1(config-if)# shut
ASSA1(config-if)# show failover
Failover On
Failover unit Primary
Failover LAN Interface: FAILOVER GigabitEthernet2 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 3 of 60 maximum
Version: Ours 8.4(2), Mate 8.4(2)
Last Failover at: 14:20:00 SGT Nov 18 2014
This host: Primary - Active
Active time: 7862 (sec)
Interface outside (100.100.100.1): Normal (Monitored)
Interface inside (192.168.1.1): Link Down (Monitored)
Interface mgmt (10.101.50.100): Normal (Waiting)
Other host: Secondary - Standby Ready
Active time: 0 (sec)
Interface outside (100.100.100.2): Normal (Monitored)
Interface inside (192.168.1.2): Link Down (Monitored)
Interface mgmt (0.0.0.0): Normal (Waiting)
Stateful Failover Logical Update Statistics
Link : FAILOVER GigabitEthernet2 (up)
Stateful Obj xmit xerr rcv rerr
General 1053 0 1045 0
sys cmd 1045 0 1045 0
up time 0 0 0 0
RPC services 0 0 0 0
TCP conn 0 0 0 0
UDP conn 0 0 0 0
ARP tbl 2 0 0 0
Xlate_Timeout 0 0 0 0
IPv6 ND tbl 0 0 0 0
VPN IKEv1 SA 0 0 0 0
VPN IKEv1 P2 0 0 0 0
VPN IKEv2 SA 0 0 0 0
VPN IKEv2 P2 0 0 0 0
VPN CTCP upd 0 0 0 0
VPN SDI upd 0 0 0 0
VPN DHCP upd 0 0 0 0
SIP Session 0 0 0 0
Route Session 5 0 0 0
User-Identity 1 0 0 0
Logical Update Queue Information
Cur Max Total
Recv Q: 0 9 1045
Xmit Q: 0 30 10226
ASSA1(config-if)#
ASSA1# sh run
: Saved
ASA Version 8.4(2)
hostname ASSA1
enable password 2KFQnbNIdI.2KYOU encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
interface GigabitEthernet0
nameif outside
security-level 0
ip address 100.100.100.1 255.255.255.0 standby 100.100.100.2
ospf message-digest-key 20 md5 *****
ospf authentication message-digest
interface GigabitEthernet1
nameif inside
security-level 100
ip address 192.168.1.1 255.255.255.0 standby 192.168.1.2
ospf message-digest-key 20 md5 *****
ospf authentication message-digest
interface GigabitEthernet2
description LAN/STATE Failover Interface
interface GigabitEthernet3
shutdown
no nameif
no security-level
no ip address
interface GigabitEthernet4
nameif mgmt
security-level 0
ip address 10.101.50.100 255.255.255.0
interface GigabitEthernet5
shutdown
no nameif
no security-level
no ip address
ftp mode passive
clock timezone SGT 8
access-list OUTSIDE_ACCESS_IN extended permit icmp any any
pager lines 24
logging timestamp
logging console debugging
logging monitor debugging
mtu outside 1500
mtu inside 1500
mtu mgmt 1500
failover
failover lan unit primary
failover lan interface FAILOVER GigabitEthernet2
failover link FAILOVER GigabitEthernet2
failover interface ip FAILOVER 192.168.99.1 255.255.255.0 standby 192.168.99.2
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-715-100.bin
no asdm history enable
arp timeout 14400
access-group OUTSIDE_ACCESS_IN in interface outside
router ospf 10
network 100.100.100.0 255.255.255.0 area 1
network 192.168.1.0 255.255.255.0 area 0
area 0 authentication message-digest
area 1 authentication message-digest
log-adj-changes
default-information originate always
route outside 0.0.0.0 0.0.0.0 100.100.100.254 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
user-identity default-domain LOCAL
aaa authentication ssh console LOCAL
http server enable
http 10.101.50.0 255.255.255.0 mgmt
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
telnet timeout 5
ssh 10.101.50.0 255.255.255.0 mgmt
ssh timeout 5
console timeout 0
tls-proxy maximum-session 10000
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
webvpn
username cisco password 3USUcOPFUiMCO4Jk encrypted
prompt hostname context
no call-home reporting anonymous
call-home
profile CiscoTAC-1
no active
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination address email [email protected]
destination transport-method http
subscribe-to-alert-group diagnostic
subscribe-to-alert-group environment
subscribe-to-alert-group inventory periodic monthly
subscribe-to-alert-group configuration periodic monthly
subscribe-to-alert-group telemetry periodic daily
crashinfo save disable
Cryptochecksum:fafd8a885033aeac12a2f682260f57e9
: end
ASSA1#

Stop/start in PGW active/standby mode

Hi all
My VOIP Network has 2 PGW in active/standby mode. But when we add more telco, the state of ss7path is OOS. i must stop/start the PGW and ss7path is IS status.
Now PGW is running services. it processing many call with other telco.
i have question need to support.
When we stop/start PGW,has PGW disconnected all call or not?
Thank for supporting
PhaiLQ

If you restart the service on active pgw, calls are disconnected. If you don't want out of services you must pass the control to the standby server first.
From mml console of active server use the command:
rtrv-ne    to check the status, the output is:
    MGC-01 - Media Gateway Controller 2010-09-07 16:53:42.655 MEST
M RTRV
   "Type:MGC"
   "Hardware platform:sun4u sparc SUNW,Sun-Fire-V240"
   "Vendor:"Cisco Systems, Inc.""
   "Location:MGC-01 - Media Gateway Controller"
   "Version:"9.6(1)""
   "Platform State:ACTIVE"
sw-over::confirm to swich control to standby server
now restart the service
/etc/init.d/CiscoMGC stop
/etc/init.d/CiscoMGC start
P.S. If I remember the right way, the OOS (out of service) state of new ss7 path can be set in IS (in service) via mml command line without service restart.
set- your ss7 path ::IS   use tab for help
Regards.

Active Standby Pair Clustering.

Hi Chris, I had created ActiveStandby Pair as follows:
Server 1 => DSN: TTCluster1
Server 2 => DSN: TTCluster2.
Then I created ActiveStandby Pair in Server1, Started RepAgent and then Duplicated the DSN on Server 2 with name TTCluster 2. It worked fine.
Now to access it from the client server mode, I created Client DSN on Client machine using Virtual IP. (Using Linux Cluster Manager).
But inthis case I had to create two client DSN. TTCluster1Client and TTCluster2client. Since Application can connect to only one DSN and shifting to other while failover is very difficult.
So I am trying following model now, Let me know your views on this.
Server 1 and Server 2, both will have same DSN name "TTCluster".
Client Machin will have only one DSN "TTClusterClient" using VIP.
When the Server1 failes, Server 2 will take over and there is no need of shifting client DSN. Application will be routed to Server 2 after switch over.
Step1: created server DSN "TTCluster" on Server 1 and Server 2.
Step2: created user 'ttcluster' on Server 1 and Server 2.
Step3: Create DataStore TTCluster on Server 1. (By connecting to TTCluster).
Step4: Create Cache Groups (AWT) on Server1.
Step5: Started Cache Agent on Server1.
Step6: Created ActiveStandby Pair on Server1 as follows:
CREATE ACTIVE STANDBY PAIR
TTCluster ON "wabtectimesten.patni.com",
TTCluster ON "wabtectimesten2.patni.com"
RETURN TWOSAFE
STORE TTCluster PORT 20000 TIMEOUT 120;
Step8: executed ttrepstateset('ACTIVE') on server1.
Step9: Started Replication Agent on Server1.
Step10: Duplicated DataStore on Server2.
Issues:
Server2 is not coming up as Standby. The log on Server1 shows following messages:
15:19:33.83 Warn: REP: 8671: TTCLUSTER:receiver.c(1723): TT16060: Failed to read data from the network. select() timed out
15:19:37.09 Err : REP: 8671: TTCLUSTER:receiver.c(3428): TT16142: Failed to retrieve peer information. No peers found
15:19:37.09 Err : REP: 8671: TTCLUSTER:transmitter.c(5523): TT16229: Transmitter thread failure due to lack of state consistency at subscriber store _ORACLE
Question:
While creating replication scheme I have mentioned.
STORE TTCluster PORT 20000 TIMEOUT 120;
I need to define the timeout for both DataStores. How will I do that?
The above timeout will be applicable for which datastore??
Can you please let me know if I am going in the right direction???

Hi Tanweer,
When designing a monitoring scheme for TimesTen one has to bear a few things in mind (though not all will be relevant in every case):
1. There could be multiple 'instances' of TimesTen installed on a machine. Each instance is completely independent and must be monitoried separately.
2. Each instance has a 'main daemon' (timestend) that is the instance master supervisor. If this daemon is running and healthy then the 'instance' is considered to be 'up' and 'healthy'.
3. Each instance can manage multiple datastores. Each datastore is independent from the others and so each datastore must be monitored separately.
4. Each datastore may be using replication and/or cache connect. If so, these must also be monitored as well as the datastore since it is perfectly possible e.g. for the datastore to be healthy but for replication to be 'down'.
Depending on your requirements, your monitoring mechanism must 'model' this structure and relationships...
- If the instance main daemon is not running, or is not responding, then the entire instance is 'down' and all datastores managed by the instance should also be considered as 'down'
- If a datastore goes down (e.g. call invalidate), other stores in the instance are not affected and neither is the main daemon for the instance. They will continue to operate normally.
- A datastore may be healthy in itself but maybe replication or cache connect for the datastore is not healthy. Do you then consider the datastore as down? That depends on your applications requirements!
Hopefully this helps to clarify the interrelationship of components. Crashing a datastore by calling 'invalidate' does not crash the daemon (if it does then that is a bug!).
For monitoring the instance (main daemon) there are a few options:
1. ps -ef | grep timestend. This can detect if the daemon process is running but not if it is healthy...
2. Connect to a datastore. Every connect/disconnect request is processed via the main daemon so if the daemon is not healthy this will result in some error (usually a 'cannot communicate with the daemon' error). However, connect/disconnect are relatively expensive so you don't want to do this too often.
3. Have a monitoring process that maintains an open connection to the instance level datastore (DSN=TT_<instancename>). Periodically (as often as required within reason) it can execute the built in procedure ttDataStoreStatus() passing it the pathname of the instaance datastore checkpoint files (obtainable from the built in procedure ttConfiguration). This procedure communicates with the main daemon so will either return success (meaning daemon is okay) or an error (daemon is in big trouble).
If you have to do the test from a script then I would suggest that (2) is best but if you can do it from a continually running monitoring process then (3) is better.
For monitoring a datastore the best way to ascertain overall health is as follows:
1. Have a dummy table in the datastore. And as part of the check update a row in th dummy and commit the transaction. If this returns success then this shows that the datastore is up and able to service update requests (which means it is also okay for read requests).
2. You should also monitor the available space in the datastore and warn someone or something if the free space gets too low. You can query space allocation, current usage and high watermark usage from the SYS.MONITOR table. You can also configure TimesTen to generate SNMP traps and/or return warnings to applications if space usage exceeds some configured threshold. The objective is to take proactive action to prevent the datastore becoming full since that will require more disruptive corrective action.
For monitoring replication you should periodically:
1. Check that the datastore's repagent is running (you can do this using ttDatastoreStatus)
2. Check the status of each replication peer by calling ttReplicationStatus and checking the values of pstate (should be 'start') logs (if this value increases over time then the peer is in some kind of trouble) and lastMsg (if there is no message from the peer for a long time then it may be in some kind of trouble).
3. Sometimes an easier way is to have a dummy table set up for synchronous replication and do an update+commit for a row in that table. if replicatioin is working the commit will return within a few ms at most. If you get a timeout error returned that tells you that replication is in trouble,
To monitor cache connect is not so easy at present.
For AWT cache groups, the same monitoring as is used for replication is okay).
For SWT cache groups, if the sync to Oracle is not working every commit will get an error (so that's kind of obvious).
For AUTOREFRESH cache groups it's a bit harder. There is currenyly no supported way to determine when the last successful autorefresh occurred. I am hoping this capability will be added in a future release.
Sorry if that is a bit long winded - I hope it helps...
Chris

Unable to start Active Standby

Hi ,
I have setup the physical standby database on 11g as per the active standby setup.The physical standby is up and RFS is fetching the archive logs and appling to the standby database.When i try to open the standby database in active mode its not showing any errror converting the database to recover mode.
(1) SQL> alter database open read only;
Database altered.
SQL> alter database recover managed standby database cancel;
Database altered.
SQL> alter database open read only;
Database altered.
SQL> select count(*) from tab;
COUNT(*)
4364
SQL> RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE disconnect;
Media recovery complete.
SQL> select count(*) from tab;
select count(*) from tab
ERROR at line 1:
ORA-01219: database not open: queries allowed on fixed tables/views only
SQL> select PROCESs,SEQUENCE#,BLOCK#,BLOCKS ,STATUS from v$managed_standby
PROCESS SEQUENCE# BLOCK# BLOCKS STATUS
ARCH 46 1 497 CLOSING
ARCH 55 81921 1232 CLOSING
ARCH 52 18433 1401 CLOSING
ARCH 54 92161 1493 CLOSING
ARCH 50 1 1 CLOSING
RFS 56 158 1 IDLE
RFS 0 0 0 IDLE
RFS 0 0 0 IDLE
RFS 0 0 0 IDLE
RFS 0 0 0 IDLE
MRP0 56 125 102400 APPLYING_LOG
11 rows selected.
SQL>
Can anyone share their views as i am not sure where i had done wrong.I have verified everythign but could not find .
Thanks in advance
Regards,
Hussain

To enable active dataguard the correct sequence of statements is (see the documentation http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/manage_ps.htm#i1017111 ):
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL;
ALTER DATABASE OPEN;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE USING CURRENT LOGFILE DISCONNECT;
This has to be done only once, later simply start the standby database with 'startup' instead of 'startup mount'.
Note: you must not say 'alter database open read-only', that's the old (pre 11g) behaviour,which does not allow redo applying while the database is open for queries.
Werner

Router HSRP Active/Standby question

Hello,
Can I use following command to setup HSRP Active/Standby mode for both router ?
Router A:
ip address 10.10.228.202 255.255.255.248
standby 3 ip 10.10.228.201
standby 3 preempt
Router B:
ip address 10.10.228.203 255.255.255.248
standby 3 ip 10.10.228.201
standby 3 preempt
standby 3 track 1 decrement 10
standby 3 track 2 decrement 10
Thanks

Wilson,
we don't know what objects you're tracking, so it's a little bit difficult to answer the question.
You use the default priorities on both routers (100), so, as long as track objects 1 and 2 are up, Router B will be the active router, because it has the higher IP address.
If track object 1 or 2 goes down, Router B's priority will be reduced to 90 (or 80 if both are down at the same time), so Router A will become active, because preemption is enabled.
If the track object(s) change to up, Router B will take over again, because it also has preemtion enabled.
Correction:
Preemption only comes into play when the local priority is higher than the priority of the current active router. In your examle, the priorities on RA and RB have the same values. The IP addresses serve as a tie breaker only in the initial phase, the preemption feature doesn't consider the IP addresses later on.
Consequence: Router A continues beeing the active router.
HTH
Rolf

Ask timesten 11.2 Using Oracle Clusterware to Manage Active Standby Pair

Using Oracle Clusterware to Manage Active Standby Pairs
http://download.oracle.com/docs/cd/E13085_01/doc/timesten.1121/e13072/cluster.htm#CCHCFAAD
What is that mean ?
I have to use Share Storage for... Oracle Clusterware?
I think right?... or wrong ?
Can I have VIP on Master node, and then master down... standby will active with VIP, right ?

A TimesTen A/S pair is a replicated configuation where a pair of TimesTen datastores, usually located on different machines, act in many ways as a single unit. The active master can process both queries and DML (insert/update/delete) while the standby master can only process queries (think of this as a little like Active Dataguard). Applications that run on the same machine as one of the TT datastores can connect to it via the very high performance 'direct mode' while applications running on other machines can access the datastores in client/server mode. There is a clearly defined procedure for failing over if the active master fails (which involves promoting the standby master to active) and for recovering a failed store back to the correct role. Direct mode applications must failover with the datastore whereas for client/server applications the connection(s) need to be failed over. The basic A/S pair replication mechanism has been available since TimesTen 6.0. The replication configuration is defined via special SQL syntax and monitoring and management (failover control etc.) is performed by way of built-in procedure calls. However, in TT 6.0 and 7.0 the actual monitoring and management of the A/S pair, including failover, is left for the user to implement themselvses or via some custom integration with an external cluster manager.
TimesTen 11g adds two major new capabilities:
1. Automatic client connection failover for client/server connections. Think of this as very similar to Oracle DB TAF and FAN. This does not require VIPs or Clusterware since it is implemented completely within TimesTen. However it works very well when used in onjunction with Clusterware.
2. A deep integration between TimesTen and Oracle Clusterware. All aspects of Timesten A/S pair definition, deployment, management and recovery are handled by Clusterware. There is just a single configuration file and a single TimesTen utility (ttCWAdmin) involved. Of course you need a properly configured Clusterware setup first which will require some form of shared storage (for OCR and voting disks) but TT storage (checkpoint and log files) does not need to be on shared storage. Setting up TT for use with Clusterware is very quick and easy (maybe 30 minutes the first time you do it and much quicker thereafter once you know what you are doing). From then on Clusterware will manage all aspects of failover and recovery completely automatically. VIPs are not required but can be used if desired e.g. for application failover purposes. Clusterware can also manage the failover of direct mode applications. Also, you can define automated backup cycles and spare nodes that can be used if a node suffers some permanent failure. The Clusterware integration offers very rich functionality but also very fast failover (typically just a few seconds in my testing).
Hope that helps clarify.
Chris

Ace 4710 active/standby SNMP config

We have 2 x Ace 4710 deployed in Active/Standby config. Since the configuration mode is disabled on the Standby unit, how can we configure the SNMP settings (such as location etc.) on the standby unit different from the active unit?
The 2 devices are in physically separated data centers so the SNMP location settings need to be set differently on both units. The standby unit does not allow any configuration.

Comments inline:
Since this is the admin context, we would better not do this. As i understand correctly, this will turn off the config sync on the 2 units and we may end up with some issues.
KM - Correct, you need to manually manage the configurations of both devices.
Also, if at a later stage, we sync the configs again in the admin context, it will overwrite the different config on the standby unit with that from the active unit?
KM - Correct, the device with the lower priority will be overwritten when config-sync is re-enabled. This is one of the reasons you need to be careful in the Admin context. For example: Ff the lower priority device has contexts defined that the primary does not, they would be removed when you re-enablethis command.
Since my requirement is just the SNMP location config, I do not think i should go for this; rather i can have some descriptive location setting identifying the 2 units in cluster mode...
KM - This would be more ideal than disabling config sync. You could also put both locations like this:
snmp-server location "San Jose, CA & Seattle, WA"
Regards
Kris

What is best conection string for application to connect to active standby

I have setup a primary db and an active standby database on two servers in different city.
Now for people to test it, what is the best tnsnames strings I should provide to them?
Plus how do I test it?
Thanks in advance.

Hello;
What you are looking at Transparent Application Failover for Data Guard. ( Way cool idea if you decide to use it )
Example
ernie =
(DESCRIPTION =
    (ADDRESS_LIST =
       (ADDRESS = (PROTOCOL = TCP)(HOST = Primary.server.com)(PORT = 1521))
       (ADDRESS = (PROTOCOL = TCP)(HOST = Standby.server.com)(PORT = 1521))
       (CONNECT_DATA =
       (SERVICE_NAME = ernie)
)The DBMS_SERVICE.CREATE_SERVICE will let create an alias for database which can be used on both servers so the end user never sees a failover.
The rough outline is
1. Create the service
BEGIN
   DBMS_SERVICE.CREATE_SERVICE('ernie','ernie');
END;
/2. Start the service
BEGIN
   DBMS_SERVICE.START_SERVICE('ernie');
END;
/3. default parameters can now be set for 'ernie'.
BEGIN
   DBMS_SERVICE.MODIFY_SERVICE
   ('ernie',
   FAILOVER_METHOD => 'BASIC',
   FAILOVER_TYPE => 'SELECT',
   FAILOVER_RETRIES => 200,
   FAILOVER_DELAY => 1);
END;
/4. Finally a database STARTUP trigger should be created to ensures that this service is only offered if the database is primary.
CREATE TRIGGER CHECK_ERNIE_START AFTER STARTUP ON DATABASE
DECLARE
V_ROLE VARCHAR(30);
BEGIN
SELECT DATABASE_ROLE INTO V_ROLE FROM V$DATABASE;
IF V_ROLE = 'PRIMARY' THEN
DBMS_SERVICE.START_SERVICE('ernie');
ELSE
DBMS_SERVICE.STOP_SERVICE('ernie');
END IF;
END;
/A complete document is available here :
http://uhesse.wordpress.com/2009/08/19/connect-time-failover-transparent-application-failover-for-data-guard/
Best Regards
mseberg

UCCX Active / Standby server

Similar Messages

Maybe you are looking for