01-20-2016 03:49 AM - edited 07-05-2021 04:30 AM
I probably posted in the wrong forum so ill try here!
I am having a problem whereby after configuring the WLC via gui, it was recommended i set a static Ip on my router which i have done.
I set the subnet at 255.255.255.0, however, on the router it is different.
The default gateway i set as the router IP address.
However, after the WLC rebooted, i cannot get access to it at all, and thats using the ip address that is set as the management IP and the one the router issued automatically.
With that in mind, I have tried to do a reset on the front of the unit, but i still cannot gain access.
I think the router has assigned an IP of .93 and i had set the interface at .95 before plugging it into the switch.
EDIT: i have now assigned a static ip for the wlc at .95 which is what the management interface was set to on the router and i get "not connected to internet".
Is there another way to back to factory defaults with the IP 192.168.1.1?
01-20-2016 06:24 AM
Anyone?
Kinda stuck here with no wifi.
Im running the default firmware that came preinstalled but i got two quick start guides in the box...
7.6.120.0 and 8.0.110.0 (which is the one i used) so im not sure what i am running.
Build date for the wlc is 07/2015
EDIT: i have now managed to SSH into the controller using the static IP address, but im not sure where to go from there.
I still cannot connect directly via ip address on browser.
01-20-2016 06:37 AM
Some info...
Interface Name Port Vlan Id IP Address Type Ap Mgr Guest
-------------------------------- ---- -------- --------------- ------- ------ -----
management 1 untagged 192.168.2.95 Static Yes No
virtual N/A N/A 192.0.2.1 Static No No
(Cisco Controller) >show interface detailed management
Interface Name................................... management
MAC Address...................................... 80:e8:6f:01:59:c0
IP Address....................................... 192.168.2.95
IP Netmask....................................... 255.255.255.0
IP Gateway....................................... 192.168.2.1
External NAT IP State............................ Disabled
External NAT IP Address.......................... 0.0.0.0
Link Local IPv6 Address.......................... fe80::82e8:6fff:fe01:59c0/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.............................. Unconfigured
--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
(Cisco Controller) >
01-20-2016 06:55 AM
Manufacturer's Name.............................. Cisco Systems Inc.
Product Name..................................... Cisco Controller
Product Version.................................. 8.1.102.0
Bootloader Version............................... 1.0.20
Field Recovery Image Version..................... 7.6.101.1
Firmware Version................................. PIC 20.0
Build Type....................................... DATA + WPS
System Name...................................... Cisco
System Location..................................
System Contact...................................
System ObjectID.................................. 1.3.6.1.4.1.9.1.1279
IP Address....................................... 192.168.2.95
IPv6 Address..................................... ::
Last Reset....................................... Power on reset
System Up Time................................... 0 days 0 hrs 22 mins 12 secs
System Timezone Location......................... (GMT) London, Lisbon, Dublin, Edinburgh
System Stats Realtime Interval................... 5
System Stats Normal Interval..................... 180
--More-- or (q)uit
Configured Country............................... GB - United Kingdom
Operating Environment............................ Commercial (0 to 40 C)
Internal Temp Alarm Limits....................... 0 to 65 C
Internal Temperature............................. +33 C
External Temperature............................. +37 C
Fan Status....................................... 3200 rpm
State of 802.11b Network......................... Enabled
State of 802.11a Network......................... Enabled
Number of WLANs.................................. 1
Number of Active Clients......................... 0
Burned-in MAC Address............................ 80:E8:6F:01:59:C0
Maximum number of APs supported.................. 75
System Nas-Id.................................... Cisco
WLC MIC Certificate Types........................ SHA1/SHA2
01-20-2016 07:15 AM
Well, for one reason or another and after searching the forums, it turns out that webmode must be enabled via CLI.
That wasn't in the instructions!
01-20-2016 11:58 AM
The webmode is enabled by default. You need to make sure that the subnet mask is correct and that the ip address you used on the WLC is not being used by another device.
You can connect to port 1 with your laptop and assign 192.168.2.20 255.255.255.0 and you should be able to ping and access the controller.
-Scott
*** Please rate helpful posts ***
01-20-2016 12:22 PM
Thanks Scott,
Yes, i must admit I thought there shouldn't have been an issue, but after i enabled it via the CLI it sprung into life!
So, basically, all ok and up and running, although i can't seem to access any of the wired devices via wireless devices now, eg, printer, music system etc.
Ill start another thread.
:)
01-20-2016 10:58 AM
Moving post to the appropriate community
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide