cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
456
Views
0
Helpful
4
Replies

cannot access 4402 controller management IP

gflorescu
Level 1
Level 1

I just purchased a wireless controller 4402 and I'm new to using a controller.

I booted it up and I setup the ip address information on it. (management IP, service port IP, AP-management IP).

I'm able to access the device from the CLI thru a serial cable and also if I'm plugged in with a laptop thru the service port.

I am not able to ping or access the device via its management IP address or its service port IP address from any PC on the network.

I tried different settings on the switch port (i.e. trunk, access).

4 Replies 4

dennischolmes
Level 7
Level 7

Did you place both the management address and the service port address in the same network? This will cause failure as the service port must be out of band.

weterry
Level 4
Level 4

Did you set a vlan for your management interface?

Your management vlan should be 0 if the native vlan (or access vlan) is the vlan for the management interface.

Leo Laohoo
Hall of Fame
Hall of Fame

Taken from Cisco 440X Series Wireless LAN Controllers Deployment Guide

Management Interface

The Management interface is the default interface for in-band management of theWLC and connectivity to enterprise services such as AAA servers. The Management interface is the only consistently "pingable" in-band interface IP address on the WLC.

Service-Port Interface

The service port interface must have an IP address on a different subnet from the Management, AP Manager, and any dynamic interfaces. The service port can get an IP address via DHCP or it can be assigned a static IP address, but a default-gateway cannot be assigned to the Service-port interface. The Service-port is typically

reserved for out-of-band management in the event of a network failure. It is also the only port that is active when the controller is in boot mode.

Hope this helps. Please rate when applicable.

Well, it was all kind of weird because I am able to access it now from a different VLAN without a problem and I didn't change anything.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Review Cisco Networking products for a $25 gift card