ADSP Polling

J Jasyn Voshell 3 years 5 months ago
4 3 0

Attached are the requirements for integration between WiNG 5.2 and ADSP system.  Following these guidelines you should be able to minimize challenges with SNMP integration between WiNG 5.2 and ADSP.

WiNG v5.2.x with Air Defense Services Platform 8.1.3b2 & 9.0 Integration Configuration Best Practices

 

Required Firmware Versions:

WiNG v5

5.2.11 or newer
5.3.1 or newer

ADSP

ADSP 8.1.3 -11b2 or ADSP 8.1.3-11e1

ADSP 9.0 or newer

Recommended Configurations:

Following are the required configurations for WING and ADSP integration

ADSP Communication Profile Settings

1)      SNMP timeout – Increase the timeout value 10 seconds (9999ms). The larger the timeout, the more reliable the system operation will be.

 

ADSP Polling Profile Settings

2)      Data Poll Interval – 

a)       Status poll interval -- 30 minutes or more.

b)      Data Collection interval -- 60 minutes or more. .

ADSP Polling

3)      In a network topology where there are controllers in the network, the polling should be set up only on the RFS Controllers, and not directly to the Access Points . It is only necessary to poll the controller as it  has all required information for the network.  Configure ADSP  to poll only the controllers, and not the APs.

 

AP and Controller Firmware Versions

4)      Only identical versions of firmware are supported for AP adoption.  Deployed systems where the controller is running a different firmware version from the AP is not a supported configuration.    Integration between WiNG and ADSP would also not be supported in this type of deployment.  Ensure deployments have identical versions of Controller and AP firmware.

Please Register or Login to post a reply

3 Replies

D Denis Dionne

Thx for the clarification. I will do.

D Denis Dionne

Hi, I read your recommendations and I tried to find where I can restrict the polling to the RFS. I don't find where. Please guide me on this. Denis Dionne

J Jared Ebel

ADSP will perform scheduled polling of each infrastructure device that was added through direct SNMP discovery or by import file.  To properly import a controller managed WLAN, you should only be performing the initial SNMP discovery on the WLAN controller.  APs which the controller manages will be imported via discovery of the controller.  By doing this, ADSP will poll only the controller on subsequent data collection or status polls. If a controller managed WLAN was imported to ADSP using a broad SNMP discovery of an IP subnet or subnets to discover all devices individually (controllers and APs), then the devices will need to be removed from the system and re-imported using the method described above. Jared Ebel

CONTACT
Can’t find what you’re looking for?