Connect Connector to Cisco AireOS Wireless Controller

Configure and Test Connectivity Between a Connector and AireOS Controller

Before you begin

  • Deploy a connector OVA and activate it using a token from Cisco Spaces.

  • Ensure that the IP address of a Cisco AireOS Wireless Controller is reachable from the Cisco Spaces: Connector.


Restriction

  • In the context of CSCvk38081, we recommend that you do not add connector on the same subnet as the dynamic interface of the AireOS controller. However, if you cannot follow this recommendation, you can add the AireOS controller to connector and configure all the SNMP queries to the IP address of the dynamic interface of the controller.

  • We also recommend that you do not add connector on the same subnet as the service port of the AireOS controller. However, if you cannot follow this recommendation, you can add the AireOS controller to connector and configure all the SNMP queries to the IP address of the service port of the controller.

  • This restriction is a result of a limitation in the AireOS controller. While SNMP queries are usually made to the management IP address, the SNMP response packets are returned with a source IP address field that is configured with the IP address of the dynamic interface or source port.

Procedure

Step 1

Log in to Cisco Spaces.

Note

 

The Cisco Spaces URL is region-dependent.

Step 2

In the Cisco Spaces dashboard, choose Setup > Wireless Networks.

Step 3

Expand the Connect via Spaces Connector area using the respective drop-down arrow to display a list of steps.

Step 4

To test the connectivity from the Connector to an existing AireOS controller, click View Controllers in the Step 3 area, and do the following steps:

  1. Click the pencil icon to edit an AireOS controller.

  2. Choose an active Connector from the Connector drop-down list to enable the Test Connectivity button.

  3. Go to this step to test the connectivity to an existing AireOS controller.

Step 5

To add a new AireOS controller, click Add Controllers from the Step 3 area.

Figure 1. Add a New AireOS controller

Step 6

From the Connector drop-down list, choose a Connector.

Step 7

Enter the Controller IP address and Controller Name, and from the Controller Type drop-down list, choose WLC (AireOS) to connect to an AireOS controller.

Step 8

From the Controller SNMP Version drop-down list, choose the SNMP version of the AireOS controller.

  • If you choose the SNMP version as v2C, specify the SNMP read-write community.
  • If you choose the SNMP version as v3, specify the SNMP v3 version username, password, and authentication protocol credentials. Ensure that SNMP v3 has read-write permissions in the AireOS controller.

Note

 

Both SNMP v2c and SNMP v3 must have read-write permission in the AireOS controller to register the Connector certificate in the AireOS controller. The Connector doesn't support SNMP v1.

Figure 2. Add a New AireOS controller

Step 9

Click Test Connectivity . Connector issues ping and SNMP commands to check the connectivity to Cisco Spaces using the credentials provided.

Note

 
Test Connectivity is enabled only when an active Connector is chosen.
Table 1. Error Description

Status of PING

Status of SNMP Test

Displayed Test Connectivity Message

SUCCESSFUL

SUCCESSFUL

 Connectivity test is successful

SUCCESSFUL

FAILED

Ping test is successful, but SNMP test failed. Check the following:

Ping test to the AireOS controller is successful, but SNMP test has failed. Check the following:

  • If you are using v2c SNMP, check if the community strings are valid.

  • If you are using v3 SNMP, check if the credentials are correct.

  • Check if v2c or v3 mode is enabled in the controller.

FAILED

FAILED

Both ping and SSH test to the AireOS controller have failed. Check the following:

  • Is there IP connectivity between a Connector and a controller?

  • Is SSH enabled on the AireOS controller?

  • Is the SSH port 22 of the AireOS controller reachable from the Connector?

  • Have you provided accurate SSH credentials?

  • Is AAA enabled with local authentication?

  • Are you using an interface that is not the wireless management interface for NMSP and SSH connectivity?

Step 10

Click Save, and then click Close.

You can see the new Catalyst 9800 controller in the Controller Channel area of the Connector GUI. The Catalyst 9800 controller that is connected successfully to the Connector appears as Active. It takes approximately five minutes for the wireless controller to change to the Active state. Refresh your window to view the status change. The added Catalyst 9800 controller is also listed in the Controller Channel area of the Connector.
Figure 3. Details of the Catalyst 9800 controller

What to do next

You can import the added Catalyst 9800 controller to the Cisco Spaces location hierarchy.