Syslog of standby unit
Trying to figure out why i'm not seeing syslog messages coming from my standby unit of an active/passive pair of 4700 ACE Appliances.
ACE-4710-K9
Version A3(2.4)
I have syslog configured
failover is functioning
i see log messages sent (UDP514) to the syslog server from the primary
Standby logging is enabled.
However, i see no log messages being generated to the syslog.
Am I missing something in this scenario?
Thanks.
Bruce
Hi Bruce,
Did you try clear logging? If not, i would suggest to do the same.
Please do "show logging statistics" in affected contexts and see if the counters like "host" are increasing. Also, please do "show logging queue" and see the below counter's value:
switch/Admin# show logging queue
Logging Queue length limit : 80 msg(s), 8 msg(s) discarded.
Current 0 msg on queue, 5 msgs most on queue
By default, logging queue would be 80. If you see it is 0 please increase it.
Also, do "show resource usage" in affected and look at the counter's highlighted below:
switch/Admin# show resource usage
Allocation
Resource Current Peak Min Max Denied
Context: Admin
conc-connections 0 42 100 8000000 0
mgmt-connections 4 1630 100 100000 0
proxy-connections 0 42 0 1048572 0
xlates 0 0 0 1048572 0
bandwidth 616 338973 2500000 625000016 0
throughput 0 207796 1250000 500000016 0
mgmt-traffic rate 616 131177 1250000 125000000 0
connection rate 0 706 100 600000 0
ssl-connections rate 0 0 0 30000 0
mac-miss rate 0 1 0 2000 0
inspect-conn rate 0 0 0 240000 0
http-comp rate 0 0 0 786432000 0
to-cp-ipcp rate 0 534 0 5000 0
acl-memory 95136 97096 0 99579792 0
sticky 2 2 0 4194304 0
regexp 0 0 0 1048576 0
syslog buffer 0 29696 0 4194304 0
syslog rate 0 6 0 100000 0
If you see the last counter on right increasing then there is a resource problem. Also, do "show resource allocation" and see if you have any minimum resource guaranteed or not. Generally, if you don't any number in right-most column, you don't need to worry about resource crunch. But it is a good practice to have some minimum guaranteed to each context.
Coming to your question of sending logs from specific interface, i don't see any way of doing it. i guess it will send logs from the interface through which the syslog server is reachable. But you can always make the ACE to define the interface or hostname as a device-id to be included in the log messages it will send, even though the actual interface through which the log sent is different.
Regards,
Kanwal
Similar Messages
-
XML files dont copy to standby unit
Hi,
I have failover active/standby topology with two ASA (version 8.0.4), and Clientless SSL VPN configured.
I have created differents profiles, bookmarks and portal in this solution.
But when I try to see this files in the standby unit, I can't to see it. Why? I try it whit "write standby" but nothing... Any idea?
Best regardsThe write standby command replicates the configuation to the running configuration of the peer unit; it does not save the configuration to the startup configuration. To save the configuration changes to the startup configuration, use the copy running-config startup-config command on the same unit on which you entered the write standby command. The command will be replicated to the peer unit and the configuration saved to the startup configuration.
http://www.cisco.com/en/US/docs/security/asa/asa81/command/ref/uz.html#wp1567205 -
Replacement of primary unit failed! (ASA5510 active/standby)
Hi all,
I have an issue bringing up my RMA'd primary ASA unit.
So what happened so far:
1. primary unit failed
2. secondary took over and is now secondary - active (as per sh fail)
2. requested RMA at Cisco
3. got ASA and checked that Lic (SSL), OS (8.2.2) and ASDM are at the same level as the secondary
4. issued wr erase and reloaded
5. copied the following commands to the new (RMA) primary unit:
failover lan unit primary
failover lan interface Failover Ethernet3
failover interface ip Failover 172.x.x.9 255.255.255.248 standby 172.x.x.10
int eth3
no shut
failover
wr mem
6. installed primary unit into rack
7. plugged-in all cables (network, failover, console and power)
8. fired up the primary unit
9. expected that the unit shows:
Detected an Active mate
Beginning configuration replication from mate.
End configuration replication from mate.
10. but nothing happened on primary unit
So can anyone give me assistance on what is a valid and viable approach in replacing a failed primary unit? Is there a missing step that hinders me to successfully replicate the secondary - active config to the primary - standby unit.
I was looking for help on the net but unfortunately I was not able to find anything related to ASA55xx primary unit replacement with a clear guideline or step by step instructions.
Any comments or suggestions are appreciated, and might help others who are in the same situation.
Thanks,
NicoHi Varun,
Thanks for catching-up this thread.
Here you go:
sh run fail on secondary - active:
failover
failover lan unit secondary
failover lan interface Failover Ethernet0/3
failover key *****
failover link Failover Ethernet0/3
failover interface ip Failover 172.x.x.9 255.255.255.248 standby 172.x.x.10
sh fail hist on secondary - active:
asa1# sh fail hist
==========================================================================
From State To State Reason
==========================================================================
23:47:15 CEST Feb 19 2011
Not Detected Negotiation No Error
23:47:19 CEST Feb 19 2011
Negotiation Cold Standby Detected an Active mate
23:47:21 CEST Feb 19 2011
Cold Standby Sync Config Detected an Active mate
23:47:36 CEST Feb 19 2011
Sync Config Sync File System Detected an Active mate
23:47:36 CEST Feb 19 2011
Sync File System Bulk Sync Detected an Active mate
23:47:50 CEST Feb 19 2011
Bulk Sync Standby Ready Detected an Active mate
10:34:09 CEDT Sep 3 2011
Standby Ready Just Active HELLO not heard from mate
10:34:09 CEDT Sep 3 2011
Just Active Active Drain HELLO not heard from mate
10:34:09 CEDT Sep 3 2011
Active Drain Active Applying Config HELLO not heard from mate
10:34:09 CEDT Sep 3 2011
Active Applying Config Active Config Applied HELLO not heard from mate
10:34:09 CEDT Sep 3 2011
Active Config Applied Active HELLO not heard from mate
==========================================================================
sh fail on secondary - active
asa1# show fail
Failover On
Failover unit Secondary
Failover LAN Interface: Failover Ethernet0/3 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 2 of 110 maximum
Version: Ours 8.2(2), Mate 8.2(2)
Last Failover at: 10:34:09 CEDT Sep 3 2011
This host: Secondary - Active
Active time: 441832 (sec)
slot 0: ASA5510 hw/sw rev (2.0/8.2(2)) status (Up Sys)
Interface Outside (x.x.x.14): Normal (Waiting)
Interface Inside (x.x.x.11): Normal (Waiting)
slot 1: empty
Other host: Primary - Failed
Active time: 40497504 (sec)
slot 0: ASA5510 hw/sw rev (2.0/8.2(2)) status (Unknown/Unknown)
Interface Outside (x.x.x.15): Unknown
Interface Inside (x.x.x.12): Unknown
slot 1: empty
Stateful Failover Logical Update Statistics
Link : Failover Ethernet0/3 (up)
Stateful Obj xmit xerr rcv rerr
General 2250212 0 64800624 309
sys cmd 2250212 0 2249932 0
up time 0 0 0 0
RPC services 0 0 0 0
TCP conn 0 0 46402635 309
UDP conn 0 0 21248 0
ARP tbl 0 0 15921639 0
Xlate_Timeout 0 0 0 0
IPv6 ND tbl 0 0 0 0
VPN IKE upd 0 0 96977 0
VPN IPSEC upd 0 0 108174 0
VPN CTCP upd 0 0 19 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 17 203259096
Xmit Q: 0 1 2250212
show ver on secondary - active
asa1# sh ver
Cisco Adaptive Security Appliance Software Version 8.2(2)
Device Manager Version 6.2(5)53
Compiled on Mon 11-Jan-10 14:19 by builders
System image file is "disk0:/asa822-k8.bin"
Config file at boot was "startup-config"
asa1 up 200 days 12 hours
failover cluster up 1 year 108 days
Hardware: ASA5510, 256 MB RAM, CPU Pentium 4 Celeron 1600 MHz
Internal ATA Compact Flash, 256MB
Slot 1: ATA Compact Flash, 64MB
BIOS Flash M50FW080 @ 0xffe00000, 1024KB
Encryption hardware device : Cisco ASA-55x0 on-board accelerator (revision 0x0)
Boot microcode : CN1000-MC-BOOT-2.00
SSL/IKE microcode: CNLite-MC-SSLm-PLUS-2.03
IPSec microcode : CNlite-MC-IPSECm-MAIN-2.04
0: Ext: Ethernet0/0 : address is 0022.55cf.7420, irq 9
1: Ext: Ethernet0/1 : address is 0022.55cf.7421, irq 9
2: Ext: Ethernet0/2 : address is 0022.55cf.7422, irq 9
3: Ext: Ethernet0/3 : address is 0022.55cf.7423, irq 9
4: Ext: Management0/0 : address is 0022.55cf.741f, irq 11
5: Int: Not used : irq 11
6: Int: Not used : irq 5
Licensed features for this platform:
Maximum Physical Interfaces : Unlimited
Maximum VLANs : 100
Inside Hosts : Unlimited
Failover : Active/Active
VPN-DES : Enabled
VPN-3DES-AES : Enabled
Security Contexts : 2
GTP/GPRS : Disabled
SSL VPN Peers : 10
Total VPN Peers : 250
Shared License : Disabled
AnyConnect for Mobile : Disabled
AnyConnect for Cisco VPN Phone : Disabled
AnyConnect Essentials : Disabled
Advanced Endpoint Assessment : Disabled
UC Phone Proxy Sessions : 2
Total UC Proxy Sessions : 2
Botnet Traffic Filter : Disabled
This platform has an ASA 5510 Security Plus license.
Serial Number: xxx
Running Activation Key:xxxx
Configuration register is 0x1
Configuration last modified by enable_1 at 10:05:32.149 CEDT Fri Jul 15 2011 -
Syslog messages coming from Standyby ASA ?
I have a pair of ASA's in Active/Standby configuration. I noticed this morning that the secondary ASA is generating syslog messages when I dont think it should. Here is the logging configuration -
logging enable
logging timestamp
logging buffer-size 1048576
logging console informational
logging buffered informational
logging trap informational
logging history critical
logging asdm critical
logging mail critical
logging host inside 10.1.4.12
This is the interface that syslog should be coming out of on the primary ASA -
interface GigabitEthernet0/1
description 10.1.85.0/24 Internal Interface
nameif inside
security-level 100
ip address 10.1.85.31 255.255.255.0 standby 10.1.85.32
ospf retransmit-interval 1
ospf hello-interval 1
ospf dead-interval 3
Cisco Adaptive Security Appliance Software Version 8.2(3)
Device Manager Version 6.3(4)
I ran the packet capture wizard on the secondary ASA and saw no syslog traffic coming from it.
Anybody else seen this ?
RonRon
The message that you show us is part of what the ASA is doing to maintain state for all the VPN connections from the primary ASA. I see similar syslog messages from the standby unit in an ASA active/standby pair.
You say:"I wouldnt expect any messages to be coming from it since it isnt really doing anything." But the standby unit is really doing things. As a new session is established on the primary the secondary must process and retain that information. And when a session is discontinued on the primary then the standby must process that also and remove the session from the state table. If the standby were not busy doing these things then it would not be able to take over and process sessions correctly if the primary were to fail.
HTH
Rick -
Reboot ASA 8.4 (asdm 6.4) Active/Standby pair
Hi,
I manage a pair of ASAs (8.4 asdm 6.4) and am having trouble with traffic going thru a tunnel. It was recommended to me that perhaps a reboot is in order. I found the instructions at http://www.cisco.com/en/US/docs/security/asa/asa84/configuration/guide/admin_swconfig.html#wp1355970 (which I followed without actually upgrading the IOS, as all I wanted was both devices to reboot - one at at time without causing connection resets) but when I attempted it, the device that rebooted was always the same IP. My question is at step 3 "when standby unit has finished reloading and is in the Standby Ready state, force the active unit to fail over to the standby unit by entering the following command on the active unit.
active# no failover active
But there is a note "Use show failover command to verify that the standby unit is in the standby ready state" which I did.
This is the result of show failover from the 0.5 (primary) unit BEFORE issuing no failover active:
Last Failover at: 05:32:10 EST Feb 9 2012
This host: Primary - Active
Active time: 3732124 (sec)
slot 0: ASA5510 hw/sw rev (2.0/8.4(3)) status (Up Sys)
Interface management (192.168.200.249): No Link (Not-Monitored)
Interface outside (63.146.180.5): Normal (Monitored)
Interface inside (172.16.0.5): Normal (Monitored)
Interface DBDMZ (192.168.60.5): Normal (Monitored)
Interface WEBDMZ (192.168.50.5): Normal (Monitored)
slot 1: ASA-SSM-4GE hw/sw rev (1.0/1.0(0)10) status (Up)
Other host: Secondary - Standby Ready
Active time: 0 (sec)
slot 0: ASA5510 hw/sw rev (2.0/8.4(3)) status (Up Sys)
Interface management (0.0.0.0): Normal (Not-Monitored)
Interface outside (63.146.180.6): Normal (Monitored)
Interface inside (172.16.0.6): Normal (Monitored)
Interface DBDMZ (192.168.60.6): Normal (Monitored)
Interface WEBDMZ (192.168.50.6): Normal (Monitored)
slot 1: ASA-SSM-4GE hw/sw rev (1.0/1.0(0)10) status (Up)
So far so good. Then I entered (on the PRIMARY-ACTIVE unit) the command no failover active and I got the following:
NMEC-ASA5510-COLOVA# sho failover
Failover On
Failover unit Secondary
Failover LAN Interface: failover Ethernet0/0 (up)
Unit Poll frequency 500 milliseconds, holdtime 3 seconds
Interface Poll frequency 5 seconds, holdtime 25 seconds
Interface Policy 1
Monitored Interfaces 4 of 110 maximum
Version: Ours 8.4(3), Mate 8.4(3)
Last Failover at: 11:02:26 EDT Mar 23 2012
This host: Secondary - Active
Active time: 140 (sec)
slot 0: ASA5510 hw/sw rev (2.0/8.4(3)) status (Up Sys)
Interface management (192.168.200.249): No Link (Not-Monitored)
Interface outside (63.146.180.5): Normal (Monitored)
Interface inside (172.16.0.5): Normal (Monitored)
Interface DBDMZ (192.168.60.5): Normal (Monitored)
Interface WEBDMZ (192.168.50.5): Normal (Monitored)
slot 1: ASA-SSM-4GE hw/sw rev (1.0/1.0(0)10) status (Up)
Other host: Primary - Standby Ready
Active time: 3732178 (sec)
slot 0: ASA5510 hw/sw rev (2.0/8.4(3)) status (Up Sys)
Interface management (0.0.0.0): Normal (Not-Monitored)
Interface outside (63.146.180.6): Normal (Monitored)
Interface inside (172.16.0.6): Normal (Monitored)
Interface DBDMZ (192.168.60.6): Normal (Monitored)
Interface WEBDMZ (192.168.50.6): Normal (Monitored)
slot 1: ASA-SSM-4GE hw/sw rev (1.0/1.0(0)10) status (Up)
Thinking all was well, I now issued (from the same 172.16.0.5 unit) the reload command. Unfortunately my continuous pings to .0.5 and .0.6 show that 0.6 rebooted AGAIN!?!
Can someone tell me what I am doing wrong?
Thanks,
SueI guessed that might be the case, but am still unsure. The IP I was pinging was the inside LAN interface (Eth
LAN failover is configured using Eth0/0 (IPs 10.0.254.253 and .254) and State Failover with Eth0/1 (IPs 10.0.253.253 and .254) "Inside" is Gig1/1 with IP 172.16.0.5 (and .6 on the second unit) I would have expected either the LAN failover or the State failover IPs to change but not the LAN interface. But perhaps I've got it backwards. Thanks for your response. Patrick.
Sue -
Why do I see "FAILED" for probes on standby ACE?
Here there,
I am running a pair of ACE in redundancy mode for HA and have created multiple context.
here is my basic config for the serverfarm.
serverfarm host VPN_Farm
transparent
failaction purge
predictor leastconns
probe ICMP_Probe
rserver SVR_A
probe ICMP_Probe
inservice
rserver SVR_B
probe ICMP_Probe
inservice
So, on the active unit, I can see that the probes are running fine. However, if I do "show probe" on the standby unit, it appears that all my probes fail.
Result of "show probe" captured from Standby Unit.
probe : ICMP_Probe
type : ICMP
state : ACTIVE
port : 0 address : 0.0.0.0 addr type : -
interval : 15 pass intvl : 60 pass count : 3
fail count: 3 recv timeout: 10
------------------ probe results ------------------
associations ip-address port porttype probes failed passed health
------------ ---------------+-----+--------+--------+--------+--------+------
rserver : SVR_A
1.1.1.1 0 -- 109 109 0 FAILED
is it normal to see failed probe on the standby unit?
Thank you
Best RegardsHi Hyeon,
Some questions here.
Is this an ACE module or an ACE 4710? What version?
Are both ACEs peers connected to the same switch or how you got them setup? Can you describe a little bit your topology?
From the standby, Did you try to ping/telnet the servers?
Did you try to remove the probe and re-add it back? (get a #show tech-support before and after)
Is there any firewall or L3 device between the ACEs and the servers?
Do you use these servers for several contexts? Is the probe failing in all the contexts?
Jorge -
Active/Standby And failover link configuration mode
Hi everyone,
When config failover link of ASA in Active Standby mode.
When we config failover int say gi0/1
config t
int gi0/1
failover lan int gi0/1
Need to confirm we do this from interface config mode only or we can do this from global config also ????????
Whe we assign IP to this int we do that from global config mode ????
Regards
Mahesh
Message was edited by: mahesh parmar
Message was edited by: mahesh parmarHi,
Actually the ASA lets you insert a lot of command what ever mode you are under.
In the output you posted is a very important thing to notice
configure mode commands/options:
WORD Specify the interface name
As you can see, the output lists only one option and before that it mentions that this is a "configure mode" command
So even if you entered the command under the interface configuration mode, it would still be entered as a global/configure command mode.
Take the following thing for example
I want to check what configuration options I have with the command "failover"
So I enter the following to my ASA
ASA(config)# failover ?
configure mode commands/options:
interface Configure the IP address to be used for failover and/or
stateful update information
interface-policy Set the policy for failover due to interface failures
key Configure the failover shared secret or key
lan Specify the unit as primary or secondary or configure the
interface and vlan to be used for failover communication
mac Specify the virtual mac address for a dynamic interface
polltime Configure failover poll interval
timeout Specify the failover reconnect timeout value for
asymmetrically routed sessions
exec mode commands/options:
active Make this system to be the active unit of the failover pair
exec Execute command on the designated unit
reload-standby Force standby unit to reboot
reset Force a unit or failover group to an unfailed state
As you can see, the ASA tells us that there are different additional command parameters after the "failover" command that can be used. Some of them can be used either in Exec or Configuration mode.
- Jouni -
Fwsm - active/standby - "Vlan configuration mismatch between peers"
Hi,
A FWSM pair fall in to active active sittuation due to a vlan configuration mismatch. What would be the best way to synchronize configurations and return to the normal active/standbay? There is a new vlan on the primary fwsm and at present both are in active state.
Thank you in advance.
ZdravkoHi,
To my understanding the FWSMs (even though both active) have identical configurations?
Have you perhaps done so that on the core switch you have only issued the "firewall vlan-group only on the primary core device (to which the FWSM is attached) and not the secondary core device?
The only time I have witnessed the same situation is when configuring a new customer link and I have only configured the primary unit (and about to configure the same on the standby unit)
Hope it helps, not sure if the above was what you meant.
- Jouni -
HELP: WLC AP-SSO not working (standby unity in maintenance mode)
I have two WLC version 7.3.101.0 with the standby unit having HA-SKU. I have tested the AP-SSO functionality without any problem in lab with direct connection on RP port between two WLC. Once I brought them into data centre in separate location (latency is less than 10ms between the two DC), the standby unity always went into maintenance mode. The booting process on standby unit went to maintenance mode as shown below:
Management Gateway and Peer Redundancy Management interface are not reachable.
Entering maintenance mode...
I have checked on the core switches at 2 data centre that the two WLC RP ports are connected to same VLAN and it is spanned across MAN link (10GB and less than 10ms delay). The spanning tree on those ports are forwarding as well.
I have rebooted the second unit but no luck.
The interface between two DC is using MTU 9216 which I do not think would cause this issue.
Anyone has come across same or similar issue with me or know the solution? If you do, plz enlighten me.
ThanksThanks Leo and Scott for your feedback. I notice there are two newer software for WLC version 7.3.102.0 and 7.4.100.0.
Both of them seem to have many open caveats. In my wireless environment, I also use ISE, MSE and Prime Infrastructure and unfortunately WLC 7.4 does not support prime solution and MSE yet according to below compatibility matrix.
http://www.cisco.com/en/US/docs/wireless/controller/5500/tech_notes/Wireless_Software_Compatibility_Matrix.html
I think I only have choice to do minor upgrade to 7.3.102.0 at this moment (please correct me if I am wrong). This software was published on 30th Jan 2013 so I wonder if someone else has tried this and managed to get WLC AP-SSO setup working flawlessly where 2nd WLC unit is at different location?
Appreciate for more info and advise. -
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ørenProblem solved, initiated a failover after this it worked again!
-
Hi.
I am running VSS on 4506-E switch with Supervisor 7L-E. Currently running IOS on both switches is "cat4500e-universalk9.SPA.03.05.03.E.152-1.E3.bin" which is latest one. I have been asked to run "cat4500e-universalk9.SPA.03.04.03.SG.151-2.SG3.bin" so i think i need to degrade IOS.
Since switches are running in cluster so copying image will be pasted into active switch. Pls tell me how could i do copy this into standby also.
Pls tell me if IOS "cat4500e-universalk9.SPA.03.04.03.SG.151-2.SG3.bin" is stable for VSS.
Also let me know if this support SSH login.Once you copy the image into the active switch, you can copy it onto the standby unit by specifying the target as slavebootflash. e.g.:
copy bootflash:/cat4500e-universalk9.SPA.03.04.03.SG.151-2.SG3.bin slavebootflash:/
Once you have copied the image onto both supervisors, follow the procedure for upgrade / downgrade of a VSS described here.
I don't know personally of any stability issues with the 3.4(3) IOS-XE image - VSS or otherwise.
The "k9" in the image name indicates support for encryption which includes the ability to create an rsa key and configure ssh transport. -
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 -
Command to transfer traffic from active firewall to standby
Hi there,
I am looking for a command to divert traffic to stanby firewall even though active firewall is up. is there a command like that. PLZ help. Thanks in advance.Hi,
You can for example log to the standby unit and issue the command.
failover active
- Jouni -
Anyway to have Hot-Standby Root Bridge for Autonomous AP1242
Is there anyway to have or configure a Hot-Standby Root Bridge for Autonomous AP1242?
My purpose of hahving this is to have a more resilience in case the Active Root Bridge is faulty on the backhaul side.
In order to have more resilience backhaul for the backhaul bridging part, my thinking is to configure the Non Root bridges as WGB infrastructure mode and Root Bridges as AP.
Any suggestions are welcome :)When you set up the standby access point, you must enter the MAC address of the access point that the standby unit will monitor. Record the MAC address of the monitored access point before you configure the standby access point.
The standby access point also must duplicate several key settings on the monitored access point. These settings are:
⢠Primary SSID (as well as additional SSIDs configured on the monitored access point)
⢠Default IP Subnet Mask
⢠Default Gateway
⢠Data rates
⢠WEP settings
⢠Authentication types and authentication servers
Check the monitored access point and record these settings before you set up the standby access point.
I hope it may help you. -
CSS 11501 push new software from the production to a standby box
Is it possible to push/sync the new software image on the production CSS to a redundancy/standby CSS? e.i script play......
Thanksthis is not possible.
You have to install the software on the standby unit from a FTP server manually.
Gilles.
Maybe you are looking for
-
Open Sales Order Qantity / Value
Hello Experts, we need in BW the information of open order quantity (ooq) and open order value (oov) from our SD. In our opinion the ooq and oov have to be "open", until the delivery have status post good issue. But SAP-Standard is, after creating th
-
Compare DB objects between different schemas
Hi, I want to compare db objects beween 2 different schemas like QA and PROD. Please suggest me a tool that compares table definitions,stored procedures and other db objects between different schemas.
-
Resolution for the below error
Hi Gurus, facing the below error when trying to run/save/access IBots even though the BI Scheduler is up and running fine. Oracle BI Scheduler Error: [nQSError: 12008] Unable to connect to port 9705 on machine localhost. [nQSError: 12010] Communicati
-
I have a HTC Rhyme, and constantly get into the screen/message of "Sorry! Activity HTC Sense (in application HTC Sense) is not responding. Force close; Wait". After I clicked "Force close", a white screen of "HTC" came up and the phone was frozen for
-
Compression=all, data_only, [metadata_only],
hi gurus, i have seen one parameter: compression in oracle 11g r2. the values for this parameter are compression=all, data_only, [metadata_only] is this parameter will compression actual data also. how it can compress the actual data. could you pleas