Active/Standby issue.

Hi.
I've got a pair of ASA5510, who recently experienced a power failure.
The "cluster" got back up and working again.
But I'm experiencing a weird issue.
If i try to edit a bookmark a get the following:
ERROR: % Command not executed because 'show import' command is running
Actually quite a problem, since i can't make changes to bookmarks atm.
Also looking like this.
Tried to reboot the Standby unit, no effect.
Anyone experienced this before?
Thanks.
Regards,
Søren

Problem solved, initiated a failover after this it worked again!

Similar Messages

ASA 8.4 Active/Standby issue

Hi,
Have configured Active/Standby and configuration has been copied fine from one device to other.
All interfaces that have been auto created (to match the original device) are showing IP addresses correctly (UP,UP)
The ASA are connected via 2 switches using trunk ports and status is UP for both trunk ports (I have connected to the same ports as in original device)
Though it was going to work when the configuration transfer was completed and the same interfaces connected. Let me know if you can suggest why interfaces on the standby ASA when active become (UP, UP) with correct IP Addresses but no traffic passes except on the failover interface.
Thanks

in fact this is the problem that even after entering command "no failover active" on the Active ASA and therefore the second ASA becomes the Active one - still no traffic works except between the interfaces of the Failover between the two ASA's. So the second ASA is yes becoming Active but it seems that no device is able to communicate with it even if all its interfaces match the primary one.
Attached is a diagram of the setup.
(Update seems that isakmp site to site link is not coming up now - other than that internal communication is working from the ASA on failover)

Issues with IPSEC on active standby ASA 5545-X

We have two 500 meg layer 2 links with ethernet presentation. Each end of these links connected to the outside interface of an ASA firewall in active standby. So four firewalls total.
When I configure an IPsec between them and failover one end, the tunnel fails over correctly. When I failover back to the primary, it stalls until manually cleare in the ASDM or cli.
I dont really understand why it works at all rather than just the first time so would appreciate some assistance. Is some sort of tracking required? I've attached a diagram which I hope helps.
Running asa912-smp-k8.bin and asdm-713.bin

GurjitSra
Correct. In order to reload IPS without triggering failover you'll need to remove IPS inspection from policy-maps so that failover will not track IPS status.
Johan.

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

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

E71-1 - No inbox/notification in active standby

In the past days I have tried to configure any kind of information about my primary email account for the active standby/home screen. The email account works fine (imap-idle account), receiving emails works fine, but other than the @-symbol in the top-right corner (when new emails are available) no information about the inbox or any indication about new emails are displayed on the home screen.
In the mode-config I selected the email account to be displayed on the home screen, and no matter what option I choose in the email notification 1 details (headers only, headers with popup, headers with unread etc.) nothing at all is shown. I have seen screen shots where at least a bubble notification is shown (for new emails) and also at least a link with the account name. The way it is now I have a really hard time keeping track of my (new) emails, because I really have to open my inbox every time to be sure.
I have tried every imaginable configuration detail, the manual is no help at all, and I didn't find any information in any forums about this problem. Is this a software bug? Has anybody experienced this? Is there a solution?

I've been experiencing the same issue where that active standby plugin wouldnt show a notification. But I *THINK* I have it figured out from the clues in this discussion. This post is to benefit any other people googling for the solution. To my knowledge, this method will enable you to have the single line email notication on your Active Standby aka homescreen (where your calendar and meetings show up) in the format of Gmail (6). I believe the catch is you need to have less than 999 emails in your inbox. As a workaround you need to archive all extra emails in your Gmail inbox. A disclaimer: I am not 100% on this, so I will give you as much detail to replicate my scenario where it works, so adjust it for your own situation
I went through various deletes of my Gmail account in the Email settings area of the NATIVE messaging app (where text messages are).
If you look at Messaging --> Options --> Settings --> Other
There is a setting called "Number of saved msgs." I figured out the maximum of this to be 999. In my opinion this setting is talked about saved SENT messages (the setting above it is called "Save sent messages" Yes/No). Set this number to 999.
I assumed this 999 number of messages to be the limit for all emails out of a hunch. I went into my Gmail account on the web and pretty much archived a lot of emails except the recent ones. Archiving your emails does not delete them, but rather stores them outside of the inbox and are still searchable within Gmail. I made sure the number of emails in my inbox were under 900.
Next, I followed the steps we all know to put in a Gmail account via IMAP via the setup email wizard and some minor tweaking in the settings dialogs (Messaging --> Options --> Settings --> Email --> Gmail --> Connections Settings --> Both Incoming e-mail and Outgoing e-mail sections) using the guide: Symbian S60 - Gmail Help
It might also be worth it to set your "Access point in use" for both incoming and outgoing servers.
Under
Messaging --> Options --> Settings --> Email --> Gmail --> User Settings --> New e-mail alerts should be ON
Under
Messaging --> Options --> Settings --> Email --> Gmail --> Retrieval Settings --> there are no necessary changes (the next section will override settings related to retrieval amount and cause ALL emails to be retrieved.). Note that putting folder subscriptions may put you over the 999 limit. I don't know if the 999 limit applies to each folder or to ALL emails as a whole. If you do put folder subscriptions, the next section setting will automatically also override the # of emails from folders retrieved to be ALL as well. Experiment at your own risk.
Under
Messaging --> Options --> Settings --> Email --> Gmail --> Automatic Retrieval:
Email notifications -- Disabled (you can only have one or the other and email retrieval is more important than this unknown and ill defined setting)
Email retrieval -- Enabled or "only in home network" (more options will appear now regarding scheduling. Pick your frequency according to how long you want your battery to last and how important your emails are). If you choose "only in home network" I am inclined to believe that it will only use the access point you described earlier in "Connection Settings"
Out of this menu,
Under
Messaging --> Options --> Settings --> Email
Make sure your default mailbox is Gmail
If you go into Modes (Modes--> Home screen apps --> Enabled apps) at this point and try to put the "Email 1 notification" as active, and go into "Email 1 notification's " settings, and try to set your mailbox to Gmail, it will tell you to connect first. So lets do that and hope it works
So go to Messaging --> Gmail --> Options --> Connect and watch it retrieve headers of your emails from Gmail. Make sure that theres 1 or 2 *NEW* emails before downloading for testing out the Active Standby plugin's temperment.
Go into Modes while it is retrieving the headers of your emails
Modes --> Home screen apps --> Enabled Apps --> and select "Email 1 notification"
Go back into
Modes --> Home screen apps --> Go into the new "Email 1 Notification" setting there
Mailbox: Gmail
Preview: You have a choice of three
Header only -- shows your mailbox's name and # of unread mails on homescreen -- eg: Gmail (3)
Header and popup -- show the header described above in 1 line, plus when you hover over it, a preview of your emails in a bubble that includes Sender, Subject, and Date. To me, this is the most useful
Header and unread -- Shows the header described above in 1 line, and in a 2nd line shows the most recent unread email's Sender, subject, and date
Assuming you've put a audio tone for email alerts in Profiles --> Whichever profile --> Customize --> Email alert tone
Then once you head back to your home screen and once the email retrieval finishes, you should hear a audio sound, and see Gmail (3).
Good luck

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

Active/Standby ASA 5520 + SSM-10=Failures

Greetings,
We have two ASA5520s, both at 7.2(2) running in active/standby failover. Each of the ASA's have an AIP-SSM-10 in them running 6.0(3)E1. The configuration is in promiscuous mode assign to global policy, all traffic.
The primary will be running fine until it transitions to the secondary with a message: Module in slot slot experienced a data channel communication failure, data channel is DOWN. When I go to the SSM it will not let us in by ASDM, I can telnet and it will allow us to log in, shows the disclaimer info but never gives a cli prompt. The secondary will be running for a while, then it exhibits the same behavior and its SSM become unresponsive. The ASA transition again regardless if the SSM is back online or not. If it is it operates normally.
If it were 1 SSM I'd say it was the problem but both of them are doing it which leads me to consider configuration or is there something else I am missing somewhere.
We want to put these SSM-10's inline but not with there current instability.
Any suggestion at this point would be most helpfull.
Jim Collin
Maui Land and Pineapple Company Inc.
[email protected]

I've got the exact same problem. I opened a TAC case and was told too much traffic was being redirected to the AIP module, overflowing a queue, causing the failure. We were using the modules for a couple of months before we began experiencing this issue. It got so bad I had to completely disable redirection to the module. We're not inspecting ESMTP traffic, but I'm going to try disabling protocol inspection entirely and apply the service-policy to see if it could be one of the other defaults that is the culprit. That makes more sense to me than volume because our traffic volume didn't changed considerably. Need approval so it may be awhile.

FWSM move from Active/Standby to Active/active

Hi there,
we have some FWSM installed in 6500 with many contexts in them. They are at the moment configured as Active/Standby and in production. But we have noticed that whenever a backup is run which goes through some of the contexts, the FWSM start counting errors which was already determined to be an oversubscription issue. So, while we wait for the new ASA 5585X to arrive and finally replace them, we want to mitigate the issue by configuring the FWSM as Active/Active and move the contexts for backup traffic to the other box (keeping the production contexts in the other one).
My question is, can this be done without impacting the production traffic? Or as soon as we enable the active/active by the configuration of the groups and assignments of the contexts, the traffic will be impacted and we will produce an outage to the network?
Thanks in advance for your help.
Regards,
Paula

So no answers?
Just one to update why had problem here: we need to to pull changes from Physical StandBy, because of performance reasons we cannot afford to reload every table with full refresh, we only want to get changes. At first I thought that it will be easy just create materialized view log and do basic replication, but in Physical StandBy we cant do it

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

E50 Active standby plugins

Hy.
I have an Nokia E50.
When i enter to the Active Standby Plug-ins apper No Data.
Where can i find some plug-ins to download?

24-Jan-2008 09:14 AM
cristian05 wrote:
Hy.
I have an Nokia E50.
When i enter to the Active Standby Plug-ins apper No Data.
Where can i find some plug-ins to download?
Hi - Did you ever solve this as I have the same issue?
Regards
Simon

FWSM Active/Standby in VSS mode

hello,
i do have two 6500 in VSS mode , and one FWSM module on each 6500, i want to configure these modules as Active/Standby, how do i start , should i follow this (not in VSS mode):
http://www.cisco.com/en/US/docs/security/fwsm/fwsm32/configuration/guide/fail_f.html
or are there other things should i do to make it work,
thanks

up!

Apple iPad 6.1.2 10B147 - Active Sync Issues Remain

Hi,
Please correct me ASAP if I am posting this in the wrong area of the discussion forum.
I have a batch of Apple iPad devices that are now connecting to our Exchange 2003 system using Apple iPad iOS 6.1.2 10B147 devices. It would seem that these devices may have the 6.1 Active Sync issue again even though this version was meant to fix the issue.
A couple of users have reported this morning reoccuring calender cancellations, we have also had excessive log growth on Exchange 2007 platform.
Here is the reported "Device Agent" from Active Sync logs:
Apple-iPad3C6/1002.147
Apple-iPad2C7/1002.147
Apple-iPad2C7/1002.147
Apple-iPad3C6/1002.147
Apple-iPad2C7/1002.147
Apple-iPad3C6/1002.147
Here is the reported Device iOS
DeviceOS
iOS 6.1.2 10B147
Does anyone know if Apple has this as a reported bug yet on their fixed version? If not is there an official Apple bug submission process that should be followed?
Regards
Ben Paddick

Hi waddock,
I think that for the most part, iOS 6.1.2 resolved the recurring calendar bug and the significant battery drain issues. With that said, I have had a couple cases of devices still experiencing the battery drain but not the calendar bug. Quick fix is to remove the Exchange mailbox(es) from the device and re-add it. If there are any existing accounts that use Exchange ActiveSync (I think Hotmail and legacy GoogleSync), I just remove and add them back to just in case.
I suggest checking here for periodic updates on what's going on with EAS (Exchange ActiveSync) and 3rd party devices like Apple:
http://support.microsoft.com/kb/2563324
I assume you're an on-premise environment, so to mitigate short-term, you may want to think about blocking certain devices on certain operating systems using your Device Access Settings in Exchange for mobile devices.
For feedback for Apple, you can do it a couple ways. This is the internet facing site:
http://www.apple.com/feedback/
Or you can create an Apple Developer account (or Apple IT program if you have an enterprise agreement with them) and start submitting feedback during your testing (i.e. beta versions of iOS):
https://developer.apple.com/
Hopefully this helps!

N81 How to Show calender at active standby

Hi, i just bought a N81, but i just cant seem to get the phone to show the calender details for the day at the active standby mode(the main page). I can do it previously on my 6280.
Anyone can help?

12-Jun-2008 11:42 AM
psychomania wrote:
Pass, it reads to me like they want to change the active standby shortcuts and can't find which application to use in the phone.
It reads like that to me too.
Grayburn @ www.nokiausers.net & www.dailymobile.se....come say Hello!!!
If you appreciate ANY help from a member,then show it by clicking on the Blue Star button, cheers

SAP HR Active Sync Issue

Hi,
I encountered SAP HR Active Sync issue: The IDM seems can't receive the IDOC but SAP side says the data already passed to port OK.
I enabled the verbose mode of the Active Sync logs and it is repeating:
2009-06-04T17:07:08.750+0800: IDOCs of message type HRMD_A will be processed.
2009-06-04T17:07:08.750+0800: {jco.server.gwhost=10.153.3.20, jco.server.progid=IDMRFC, jco.server.gwserv=sapgw01, jco.server.trace=1, jco.server.unicode=1}
2009-06-04T17:07:08.750+0800: Started IDocServer (IDMRFC)
2009-06-04T17:07:08.750+0800: Done initializing SAPHRActiveSync resource adapter.
2009-06-04T17:07:08.750+0800: SARunner: loop 0
2009-06-04T17:07:08.812+0800: Started, paused until Thu Jun 04 17:07:08 GMT+08:00 2009
2009-06-04T17:07:13.812+0800: Pause completed
2009-06-04T17:07:13.843+0800: Polling
2009-06-04T17:07:13.843+0800: Poll complete.
2009-06-04T17:07:13.843+0800: SARunner: loop 1
SAP side transaction WE02 shows the IDOC:
IDoc sent to SAP system or external program: Data passed to port OK
SAP HR Active Sync resource reference says:
1. Enter transaction code PFAL.
2. Insert the Object Type P for person objects.
3. Enter an Employee's ID for the Object ID or select a range of employees.
4. Click Execute.
5. Ensure that the status is set to passed to port okay.
6. The IDoc has been created. Check the Active Sync adapter log file to verify that
an update was received.
Now why I can't see the IDOC logs in the active sync adaptor log file?
Thanks!

Hi Wushilin,
Did you ever find a solution to this?
Thanks

Active/Standby issue.

Similar Messages

Maybe you are looking for