Using Advanced Settings and Operations

Managing SNMP

Simple Network Management Protocol Version 2 (SNMPv2) is a protocol for network management. It is used for collecting information from, and configuring and managing all the devices in the network.

To enable SNMPv2 Access, choose Enabled from the SNMPv2 Access drop-down list. Otherwise, choose Disabled. The default is Disabled.

To configure an SNMP community with read-only privileges, in the Read-Only Community field, enter a name for the community. The default is Public.

To configure an SNMP community with read-write privileges, in the Read-Write Community field, enter a name for the community. The default is Private.

To enable the SNMP Trap Receiver tool that receives, logs, and displays SNMP traps sent from network devices, choose Enabled from the SNMP Trap drop-down list. The default is Disabled.

To connect to an SNMP server, specify the IP address of the server in the SNMP Server IP field.

Setting Up System Message Logging

The System Message Logging feature logs the system events to a remote server called a Syslog server. Each system event triggers a Syslog message containing the details of that event.

If the System Message Logging feature is enabled, the controller sends a syslog message to the syslog server configured on the controller.

Before You Begin

Set up a Syslog server in your network before starting with the following procedure.

    Step 1   Choose Advanced > Logging.

    The Logging Setup window appears.

    Step 2   From the Syslog Logging drop-down list, choose Enabled. The default is Disabled.

    The System Message Logging feature is enabled.

    Step 3   In the Syslog Server IP field, enter the IPv4 address of the server to which the syslog messages are to be sent.
    Step 4   Set the severity level for filtering syslog messages to the syslog server. From the Logging Level drop-down list, set the severity level by choosing one of the following (given in the order of severity):
    • Emergencies (Highest severity)
    • Alerts
    • Critical
    • Errors (Default)
    • Warnings
    • Notifications
    • Informational
    • Debugging (Lowest severity)

    After a syslog level is set, only messages with a severity equal to or more than the set level are sent to the syslog server.

    Step 5   To set the facility for outgoing syslog messages to the syslog servers, choose one of the following options from the Syslog Facility drop-down list:
    • Kernel = Facility level 0
    • User Process = Facility level 1
    • Mail = Facility level 2
    • System Daemons = Facility level 3
    • Authorization System = Facility level 4
    • Syslog = Facility level 5 (default value)
    • Line Printer = Facility level 6
    • USENET = Facility level 7
    • Unix-to-Unix Copy = Facility level 8
    • Cron = Facility level 9
    • FTP Daemon = Facility level 11
    • System Use 12 = Facility level 12
    • System Use 13 = Facility level 13
    • System Use 14 = Facility level 14
    • System Use 15 = Facility level 15
    • Local Use 0 = Facility level 16
    • Local Use 1 = Facility level 17
    • Local Use 2 = Facility level 18
    • Local Use 3 = Facility level 19
    • Local Use 4 = Facility level 20
    • Local Use 5 = Facility level 21
    • Local Use 6 = Facility level 22
    • Local Use 7 = Facility level 23
    • Authorization System (Private) = Facility level 24
    Step 6   Click Apply.

    Resetting the Mobility Express Controller

    This operation can be performed only by Admin users.

    To reset your Cisco Mobility Express wireless LAN controller to its default factory-shipped parameters:
    1. Choose Advanced > Reset to Factory Default.

      This opens the RESET MOBILITY EXPRESS CONTROLLER TO FACTORY DEFAULT window.

    2. Click Continue to:

      • Erase the Cisco Mobility Express controller configuration parameters to their factory default values and reboot the Cisco Mobility Express wireless LAN controller.

      • Reset and reboot the master AP to it's default factory-shipped configuration.

    After the Mobility Express Controller reboots, proceed to Starting the Initial Configuration Wizard.

    Rebooting the Mobility Express Controller

    At any time, you can reboot the controller by choosing Management > Software Update, and then clicking Restart.

    Saving Controller Configuration

    Access points have two kinds of memory, the active, but volatile, RAM, and the nonvolatile RAM (NVRAM). During normal operation, the current configuration of the Cisco Mobility Express controller resides on the RAM of the master AP. During a reboot, the volatile RAM is completely erased, but the data on the NVRAM is retained.

    At any time, you can save the Cisco Mobility Express controller's configuration from the RAM to the NVRAM of the master AP. This ensures that in the event of a reboot, the controller can restart with the last saved configuration.

    To save the controller's current configuration from the RAM to the NVRAM, click Save Configuration at the top-right corner of the Cisco Mobility Express web interface, and then click Ok.

    Upon successful saving of the configuration, a message conveying the same is displayed.