Cisco WISM2 HA problem

Mohamed Sayed · ‎08-17-2014

hi all

i have two cisco WISM2 in two 6500 configured as VSS

after I configured the HA from GUI, the two controllers rebooted together and i connect console to the primary one when it reach to starting the redundancy

it fail and appear to me

Dropping ARP packet since IP conflict is detected

and then the secondary controller is down and unreachable

please advice how can i solve this issue

thanks in advance

Sandeep Choudhary · ‎08-17-2014

You have a duplicate IP address in your network. You must find it out.

There is no otherway.

Regards

Mohamed Sayed · ‎08-18-2014

hi Sandeep Choudhary

thanks alot i found it and passed this step

but now I an stuck in other point, after configured the HA and while the two wisms reloading I found this log on the console of secondary wism:

Starting Redundancy: Starting Peer Search Timer of 120 seconds

Cannot open the file /mnt/application/ha/InheritedApCount.txt

Redundancy Link is down. Entering maintenance mode to avoid network conflict.

Entering maintenance mode...

ok

my IOS is 7.4.121

please advice ?

thanks in advance

Sandeep Choudhary · ‎08-18-2014

Hi,

1. is the cable connected and is the link LED active? What is the output from “show interfaces”?

2. Did you tried to reboot both WLC at same time??

Workaround:

Configure HA once again and reboot primary and after primary comes up then reboot secondary.(do not reboot at same time)

Regards

Dont forget to rate helpful posts

Mohamed Sayed · ‎08-19-2014

Hi Sandeep Choudhary,

1- the two wisms, each one in core 6500 and the physical connection between the two WISMs is the VSL link which of the VSS

does I need another physical link ?

2- i rebooted them at the same time and also i tried to reboot the primary controller first and after it come back up i rebooted the secondary but also failed ?

i would like to tell you something, the primary wism is activated permanent with 100 AP licesne and the secondary controller is activated with the evaluation license (1500 AP) which will be expired after time period, does this cause a problem in the HA ?

thanks in advance

Sandeep Choudhary · ‎08-20-2014

Hi,

1. To achieve HA between two Cisco WiSM2 platforms, the controllers should be deployed on a single chassis or on multiple chassis using a virtual switching system (VSS) and extending a redundancy VLAN between the multiple chassis.

2.Why you activated the evaluation license on WISM2 ? Noramally if you configured with HA and primary wlc is down then the HA-WLC automatically share the configuration and the license for 90 days from the main WLC.

Regards

Mohamed Sayed · ‎08-21-2014

Hi Sandeep Choudhary ,

I didnot activate the evaluation license I found it activated

does this cause this problem of HA failure ?

I tried what you told me but the issue is still exist

now I have Cisco WLC1 is active and WLC2 is mantanence mode

kindly find the logs of WLC during the reboot to activate HA as long as show redundancy summary from the two controllers:

*****************************************************************************

init started: BusyBox v1.6.0 (2010-05-13 17:50:10 EDT) multi-call binary

starting pid 889, tty '': '/etc/init.d/rcS'
Enable memory base + limit on PLX for Octeon0 for BAR0+BAR1
Enable memory base + limit on PLX for Octeon1 for BAR0+BAR1
Change BAR2 setting for Octeon0
Change BAR2 setting for Octeon1
Set PLX switch prefetchable window to access BAR2 on Octeon0
Set PLX switch prefetchable window to access BAR2 on Octeon1
Set PLX switch MPS settings .............!!!!!!!
Detecting Hardware ...
set smp_affinity for irq 48
003f
Freeing __tmp_linux_reserved ...
Allocating named block ...
DP from CGE5.0 ...
Freeing __tmp_linux_reserved ...
Allocating named block ...
DP from CGE5.0 ...

starting pid 1184, tty '/dev/ttyS0': '/usr/bin/gettyOrMwar'
Setting up ZVM
Exporting LD_LIBRARY_PATH

Cryptographic library self-test....passed!

XML config selected
Validating XML configuration
Read HA Config before validation
octeon_device_init: found 2 DPs
readCPUConfigData: cardid 0x6080001
Cisco is a trademark of Cisco Systems, Inc.
Software Copyright Cisco Systems, Inc. All rights reserved.

Cisco AireOS Version 7.4.121.0
Firmware Version FPGA 1.6, Env 0.0, USB console 2.2
Initializing OS Services: ok
Initializing Serial Services: ok
Initializing Network Services: ok
Initializing Licensing Services: ok

License daemon start initialization.....

License daemon running.....
Starting Statistics Service: ok
Starting ARP Services: ok
Starting Trap Manager: ok
Starting Network Interface Management Services: ok
Starting System Services: ok
Starting FIPS Features: ok : Not enabled
Starting Fastpath Hardware Acceleration: ok
Starting Fastpath Console redirect : ok
Starting Fastpath DP Heartbeat : ok
Fastpath CPU0.00: Starting Fastpath Application. SDK-1.8.0, build 269. Flags-[DUTY CYCLE] : ok

Fastpath CPU0.00: Initializing last packet received queue. Num of cores(12)

Fastpath CPU0.00: Init MBUF size: 1856, Subsequent MBUF size: 2040

Fastpath CPU0.00: Core 0 Initialization and FIPS self-test: ok

Fastpath CPU0.00: Initializing Timer...

Fastpath CPU0.00: Initializing Timer...done.

Fastpath CPU0.00: Initializing Timer...

Fastpath CPU0.00: Initializing NBAR AGING Timer...done.

Fastpath CPU0.01: Core 1 Initialization and FIPS self-test: ok

Fastpath CPU0.02: Core 2 Initialization and FIPS self-test: ok

Fastpath CPU0.03: Core 3 Initialization and FIPS self-test: ok

Fastpath CPU0.04: Core 4 Initialization and FIPS self-test: ok

Fastpath CPU0.05: Core 5 Initialization and FIPS self-test: ok

Fastpath CPU0.06: Core 6 Initialization and FIPS self-test: ok

Fastpath CPU0.07: Core 7 Initialization and FIPS self-test: ok

Fastpath CPU0.08: Core 8 Initialization and FIPS self-test: ok

Fastpath CPU0.09: Core 9 Initialization and FIPS self-test: ok

Fastpath CPU0.10: Core 10 Initialization and FIPS self-test: ok

Fastpath CPU0.11: Core 11 Initialization and FIPS self-test: ok

Fastpath CPU0.00: Received instruction to get link status

Starting Fastpath Console redirect : ok
Starting Fastpath DP Heartbeat : ok
Fastpath CPU1.00: Starting Fastpath Application. SDK-1.8.0, build 269. Flags-[DUTY CYCLE] : ok

Fastpath CPU1.00: Initializing last packet received queue. Num of cores(12)

Fastpath CPU1.00: Init MBUF size: 1856, Subsequent MBUF size: 2040

Fastpath CPU1.00: Core 0 Initialization and FIPS self-test: ok

Fastpath CPU1.00: Initializing Timer...

Fastpath CPU1.00: Initializing Timer...done.

Fastpath CPU1.00: Initializing Timer...

Fastpath CPU1.00: Initializing NBAR AGING Timer...done.

Fastpath CPU1.01: Core 1 Initialization and FIPS self-test: ok

Fastpath CPU1.02: Core 2 Initialization and FIPS self-test: ok

Fastpath CPU1.03: Core 3 Initialization and FIPS self-test: ok

Fastpath CPU1.00: Received instruction to get link status

Fastpath CPU1.04: Core 4 Initialization and FIPS self-test: ok

Fastpath CPU1.05: Core 5 Initialization and FIPS self-test: ok

Fastpath CPU1.06: Core 6 Initialization and FIPS self-test: ok

Fastpath CPU1.07: Core 7 Initialization and FIPS self-test: ok

Fastpath CPU1.08: Core 8 Initialization and FIPS self-test: ok

Fastpath CPU1.09: Core 9 Initialization and FIPS self-test: ok

Fastpath CPU1.10: Core 10 Initialization and FIPS self-test: ok

Fastpath CPU1.11: Core 11 Initialization and FIPS self-test: ok

Starting Switching Services: ok
Starting QoS Services: ok
Starting Policy Manager: ok
Starting Data Transport Link Layer: ok
Starting Access Control List Services: ok
Starting System Interfaces: ok
Starting Client Troubleshooting Service: ok
Starting Management Frame Protection: ok
Starting Certificate Database: ok
Starting VPN Services: ok
Starting Licensing Services: ok
Starting Redundancy: Starting Peer Search Timer of 120 seconds
Cannot open the file /mnt/application/ha/InheritedApCount.txt
Cannot open the file /mnt/application/ha/InheritedApCount.txt
Redundancy Link is down. Entering maintenance mode to avoid network conflict.
Entering maintenance mode...
ok
Starting LWAPP: ok
Starting CAPWAP: ok
Starting LOCP: ok
Starting Security Services: ok
Starting Policy Manager: ok
Starting Authentication Engine: ok
Starting Mobility Management: ok
Starting AVC Services: ok
Starting Virtual AP Services: ok
Starting AireWave Director: ok
Starting Network Time Services: ok
Starting Cisco Discovery Protocol: ok
Starting Broadcast Services: ok
Starting Logging Services: ok
Starting DHCP Server: ok
Starting IDS Signature Manager: ok
Starting RFID Tag Tracking: ok
Starting RF Profiles: ok
Starting WLAN Control Protocol (WCP): ok
Starting Mesh Services: ok
Starting TSM: ok
Starting CIDS Services: ok
Starting Ethernet-over-IP: ok
Starting DTLS server: enabled in CAPWAP
Starting CleanAir: ok
Starting WIPS: ok
Starting SSHPM LSC PROV LIST: ok
Starting RRC Services: ok
Starting SXP Services: ok
Starting Alarm Services: ok
Starting FMC HS: ok
Starting IPv6 Services: ok
Starting Config Sync Manager : ok
Starting Hotspot Services: ok
Starting PMIP Services: ok
Starting Portal Server Services: ok
Starting mDNS Services: ok
Starting Management Services:
Web Server: CLI: ok
Secure Web: ok
License Agent: ok

(WiSM-slot22-1)

Enter User Name (or 'Recover-Config' this one-time only to reset configuration to factory defaults)

User: admin

Password:*********

User:

User:admin

Password:*********

(WiSM-slot22-1) >

(WiSM-slot22-1) >show redundancy summary

Redundancy Mode = SSO ENABLED

Local State = MAINTENANCE

Peer State = UNKNOWN - Communication Down

Unit = Secondary - HA SKU

Unit ID = 6C:20:56:2B:E6:60

Redundancy State = Non Redundant

Mobility MAC = 6C:20:56:2B:E6:60

Maintenance Mode = Enabled

Maintenance cause= Negotiation Timeout

Redundancy Management IP Address................. 172.10.0.9

Peer Redundancy Management IP Address............ 172.10.0.11

Redundancy Port IP Address....................... 169.254.0.9

Peer Redundancy Port IP Address.................. 169.254.0.11

(WiSM-slot22-1) >

(WiSM-slot22-1) >sh

******************************************************************
(WLC1) >show redundancy summary
Redundancy Mode = SSO ENABLED
Local State = ACTIVE
Peer State = UNKNOWN - Communication Down
Unit = Primary
Unit ID = 6C:20:56:2B:E5:A0
Redundancy State = Non Redundant
Mobility MAC = 6C:20:56:2B:E5:A0

Redundancy Management IP Address................. 172.10.0.10
Peer Redundancy Management IP Address............ 172.10.0.12
Redundancy Port IP Address....................... 169.254.0.10
Peer Redundancy Port IP Address.................. 169.254.0.12

***********************************************************************************

these are the coreVSS configuration of wism:

wism service-vlan 170
wism redundancy-vlan 169
wism switch 1 module 6 controller 1 allowed-vlan 1-999
wism switch 2 module 6 controller 1 allowed-vlan 1-999
wism switch 1 module 6 controller 1 native-vlan 500
wism switch 2 module 6 controller 1 native-vlan 500
wism switch 1 module 6 controller 1 qos trust dscp
wism switch 2 module 6 controller 1 qos trust dscp

please advice

thanks in advance

Sandeep Choudhary · ‎08-21-2014

Can you please tell me which license you have on both WLCs.

Primary with enough AP license and secondary with HA-SKU or ??

alos check this link: http://www.my80211.com/storage/online-pdf-downloads/high-availability-dg-00.pdf

REgards

Mohamed Sayed · ‎08-21-2014

hi Sandeep Choudhary

for the primary

(WLC1) >show license feature

Feature name Enforcement Evaluation Clear Allowed Enabled
base-ap-count yes yes yes yes
data_encryption yes no yes no
high_availability yes no yes no

(WLC1) >show license capacity

Licensed Feature Max Count Current Count Remaining Count
-----------------------------------------------------------------------
AP Count 100 30 70

***************************************************************

for the secondary:

(WiSM-slot22-1) >show license feature

This command is Not allowed on a HA-SKU Controller

(WiSM-slot22-1) >show license capacity

Licensed Feature Max Count Current Count Remaining Count
-----------------------------------------------------------------------
AP Count 1000 0 1000

(WiSM-slot22-1) >

thanks in advance

Sandeep Choudhary · ‎08-21-2014

IP address and License looks ok.

But there must be something wrong because WLC is in Maintanence mode.

Can you check the whole config again.

Sup720 and Wireless Services Module 2 (WiSM2) Basic Communication

http://me2learn.wordpress.com/2014/08/10/sup720-and-wireless-services-module-2-wism2-basic-communication/

Configure two WiSM2 for HA

http://me2learn.wordpress.com/

Regards

Dont forget to rate helpful posts