DescriptionSNMP stopped working after the controller upgrade.
ScopeKB ARTICLE TYPE:
Troubleshooting
RELATED PRODUCTS:
controller
RELATED SOFTWARE VERSIONS:
N/A
KEYWORDS: controller, SNMP,
CIL
SolutionSNMP stopped working after the
upgrade. From the controller the SNMP server responds for the SNMP as
Destination Port
Unreachable.
STEP
1:Double check if the SNMP agent in the controller is
be properly configured for the
following:
1. The read and write community strings must be configured
before the Web UI can be used to view and update any of the components
of the controller.
2. The trap manager must be
configured correctly so that traps are sent to the correct SNMP
manager.
3. The contact and location information should also be
correctly configured so that the SNMP manager can access this
information and know who to contact in case of
problems
STEP
2: Verify the status of the SNMP from the CIL of the controller
to know if the status of the SNMP is "running" or "stopped”
using the following
command:
wlan-controller# snmp status
STEP
3: If the SNMP configuration was set correct and if
the SNMP status is showing as “stopped”, enable it
with the command snmp
start:
controller# snmp
start
STEP
4: Verify the status of the SNMP from the CLI of the
controller using the syntax #snmp status. It should show the status as
"running"
RESOLUTION: Check the
status of the SNMP after upgrading the controller. If it says as
"stopped" starting the SNMP service will address the
issue.
ROOT
CAUSE:
The default setting of
SNMP is disabled. After the upgrade, the SNMP service gets disabled as
the status of the SNMP is not updated in the running config of the
controller. The config has only the SNMP server, the trap and the
community string information. So you have to start the SNMP service
after the upgrade.
