Configuration Example: Converged Access Management through Prime Infrastructure with SNMP v2 and v3

The Converged Access Management through Prime Infrastructure with SNMP v2 and v3 document describes how to add Converged Access (Cisco Catalyst 3850 Series and Cisco Catalyst 3650 Series Switches) to Prime Infrastructure with Simple Network Management Protocol (SNMP) v2 and v3.


Note

For more information on the commands used in this section, refer to Command Lookup Tool (Registered customers only).

Prerequisites

We recommend that you have knowledge on the following topics:

  • Converged Access Cisco IOS Version 3.3.2 or later.

  • Prime Infrastructure Version 2.0 or later.

Supported Platforms and Releases

  • Cisco Catalyst 3850 Series Switch

  • Cisco Catalyst 3650 Series Switch


Note
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Configuring Converged Access Management

Configuring SNMP v2 on a Switch using CLI

To configure SNMP v2, use the following commands: 


Device# configure terminal

Device(config)# snmp-server community V2Community RW

Configuring SNMP v2 on a Switch using GUI

Perform the following steps to configure SNMP v2:

    Step 1   From the GUI, navigate to Configuration > Controller > Management > SNMP > Communities > New
    Figure 1. Configuring SNMP V2



    Step 2   Enter the details as shown in the following figure.
    Figure 2. Configuring SNMP V2



    Configuring SNMP v3 on a Switch using CLI

    To configure SNMP v3, use the following commands: 


    Device# configure terminal

Device(config)# snmp-server group V3Group v3 auth read V3Read write V3Write

Device(config)# snmp-server user V3User V3Group v3 auth sha Password1 priv aes 128 Password1

Device(config)# snmp-server view V3Read iso included

Device(config)# snmp-server view V3Write iso included

Device(config)# snmp-server host 198.51.100.170 version 3 auth V3User

Device(config)# snmp-server enable traps

    Configuring on Prime Infrastructure

    Perform the following tasks to configure SNMP v2 and SNMP v3 on Prime Infrastructure:


    Note
    Use the Lifecycle view.

      Step 1   Navigate to Operate > Device Work Center > Add Device.
      Figure 3. Add Device



      Step 2   Add the SNMP V2 configuration details as shown in the following figure:
      Figure 4. SNMP V2 Configuration Details



      Step 3   Enter the SNMP v3 details as shown in the following figure:
      Figure 5. SNMP V3 Configuration Details



      Note    If Telnet or Secure Shell parameters are not entered, Prime Infrastructure will not collect inventory from the switch.

      Verifying Converged Access Management Configuration

      Verifying SNMP v2 Configuration on a Switch

      To verify SNMP v2 configuration on the switch, use the following commands: 


      Device# show snmp community

Community name: V2Community
Community Index: V2Community
Community SecurityName: V2Community
storage-type: nonvolatile active

      Verifying SNMP v3 Configuration on a Switch

      To verify SNMP v3 configuration on a switch, use the following commands: 


      Device# show snmp user
 
User name: V3User
Engine ID: 80000009030068BC0C5A8F80
storage-type: nonvolatile        active
Authentication Protocol: SHA
Privacy Protocol: AES128
Group-name: V3Group
 
Device# show snmp group
groupname: V3Group                          security model:v3 auth
contextname: <no context specified>         storage-type: nonvolatile
readview : V3Read                           writeview: V3Write                 
notifyview: <no notifyview specified>
row status: active

      Verifying Configuration on Prime Infrastructure

      The following figure verifies the configuration on Prime Infrastructure:
      Figure 6. Verifying Prime Infrastructure Configuration



      Troubleshooting Converged Access Management Configuration Issues

      There is currently no specific troubleshooting information available for this configuration.