topic I believe you hitting below in Wireless

Web GUI not accessible once an AP boots up

Cormac Champion — Mon, 05 Jul 2021 12:15:39 GMT

I don't know what is going on, but once any Lightweight AP connected to the 2504 controller boots up, the GUI is no longer accessible from a PC on the same subnet as the Management Interface. It's still pingable. I've no Access Lists in place

The SSID's are working at this point

Pls provide us "show sysinfo"

Rasika Nayanajith — Tue, 21 Jun 2016 01:20:54 GMT

Pls provide us "show sysinfo" & "show interface detailed management" output from your WLC

HTH

Rasika

Product Version..............

Cormac Champion — Tue, 21 Jun 2016 07:23:13 GMT

Product Version.................................. 8.2.100.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. PIC 16.0

Build Type....................................... DATA + WPS

System Name...................................... TEST_SYSTEM
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
IP Address....................................... 10.10.5.253
IPv6 Address..................................... ::
Last Reset....................................... Power on reset
System Up Time................................... 0 days 0 hrs 4 mins 4 secs
System Timezone Location......................... (GMT +1:00) Amsterdam, Berlin, Rome, Vienna

--More-- or (q)uit
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180

Configured Country............................... ES - Spain
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +20 C
External Temperature............................. +23 C
Fan Status....................................... 3800 rpm

State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 3
Number of Active Clients......................... 0

Burned-in MAC Address............................ CC:D8:C1:41:1A:20
Maximum number of APs supported.................. 75
System Nas-Id....................................
WLC MIC Certificate Types........................ SHA1/SHA2

(Cisco Controller) >show interface detailed management

Interface Name................................... management
MAC Address...................................... cc:d8:c1:41:1a:20
IP Address....................................... 10.10.5.253
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 10.10.5.254
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
Link Local IPv6 Address.......................... fe80::ced8:c1ff:fe41:1a20/64
STATE ........................................... REACHABLE
Primary IPv6 Address............................. ::/128
STATE ........................................... NONE
Primary IPv6 Gateway............................. ::
Primary IPv6 Gateway Mac Address................. 00:00:00:00:00:00
STATE ........................................... INCOMPLETE
VLAN............................................. untagged
Quarantine-vlan.................................. 0
Active Physical Port............................. 1
Primary Physical Port............................ 1
Backup Physical Port............................. Unconfigured
DHCP Proxy Mode.................................. Global
Primary DHCP Server.............................. 10.10.5.254

--More-- or (q)uit
Secondary DHCP Server............................ Unconfigured
DHCP Option 82................................... Disabled
DHCP Option 82 bridge mode insertion............. Disabled
IPv4 ACL......................................... Unconfigured
IPv6 ACL......................................... Unconfigured
mDNS Profile Name................................ Unconfigured
AP Manager....................................... Yes
Guest Interface.................................. No
L2 Multicast..................................... Enabled

I believe you hitting below

Rasika Nayanajith — Tue, 21 Jun 2016 08:08:03 GMT

I believe you hitting below issue. Enable LAG on your WLC & test this again.

http://www.cisco.com/c/en/us/td/docs/wireless/controller/release/notes/crn82.html

Guidelines and Limitations

After upgrading to Release 8.2, the Cisco WLC might lose all IPv4 connectivity. The Cisco WLC can no longer service incoming SSH/Web sessions and is unable to ping other IPv4 stations. However, the default router is able to ping the Cisco WLC’s management interface.

Every 10 seconds, a message similar to the following is sent to the msglog:

*dtlArpTask: Jan 06 23:50:37.312: %OSAPI-4-GW_ADD_FAILED: osapi_net.c:1032 Unable to add the gateway 192.168.145.1. System command returned failure. Errorcode:256

This occurs in the following conditions:

a. LAG is not configured.

b. The management interface is untagged and is mapped to one physical port.

c. When an untagged dynamic interface is added and mapped to port 2, the default route for the management interface is lost.

The workaround is to configure all interfaces with VLANs.

You can track this issue via CSCux75436.

HTH

Rasika

*** Pls rate all useful responses ***

Aaaarrrgggghhh

Cormac Champion — Tue, 21 Jun 2016 20:10:27 GMT

Aaaarrrgggghhh

I have changed the Management Interface to Vlan 1 but when I do, I can no longer ping it from my Laptop, which is directly connected to port 1. Have I mis-understood as to what is required to be done ? Does Management need to be in a vlan other than Vlan 1 ?

I've changed the other interfaces onto another port too so the Management interface is on it's own port - but still not pingable

You need to configure LAG,

Rasika Nayanajith — Tue, 21 Jun 2016 20:10:28 GMT

You need to configure LAG, see below

http://www.cisco.com/c/en/us/support/docs/wireless/2500-series-wireless-controllers/113034-2500-deploy-guide-00.html#anc24

HTH

Rasika

*** Pls rate all useful responses ***

Got it sorted with Management

Cormac Champion — Tue, 21 Jun 2016 20:12:23 GMT

Got it sorted with Management in Vlan 0 on Port 1 and all other Interfaces with whatever Vlans, on Port 2