topic Prime Infrastructure "Current Associated Clients" No Data Availa in Network Management

Prime Infrastructure "Current Associated Clients" No Data Available

wshuffman — Fri, 16 Aug 2013 13:58:30 GMT

We have prime infrastructure 1.3 and the "Current Associated Clients" always shows No Data Available. Any suggestions as to what would cause this?

Prime Infrastructure "Current Associated Clients" No Data Availa

jordanperks — Fri, 16 Aug 2013 17:40:03 GMT

SNMP credentials in Prime match the credentials set in the controllers?

Prime Infrastructure "Current Associated Clients" No Data Availa

wshuffman — Mon, 19 Aug 2013 12:24:25 GMT

Yes everyting else works, and the credentials match between Prime and the Controllers.

Prime Infrastructure "Current Associated Clients" No Data Availa

wshuffman — Mon, 16 Sep 2013 17:57:18 GMT

Incase anyone else has the issue it is a known bug in Prime 1.3. The resolve is to upgrade to 2.x.

Prime Infrastructure "Current Associated Clients" No Data Availa

r-klein — Mon, 27 Jan 2014 13:34:10 GMT

Hi,

i have the same Problem with the actual Version of Prime 2.x.

But the Problem is only when using SNMP V3, all other Data of the Switch i see correctly.

When i changed back to SNMP V1 the "Current Associated Clients" will work also.

I have turnd on the debug for snmp packets, so i see that the switch will send the Data correctly.

regards

Prime Infrastructure "Current Associated Clients" No Data Availa

Vinod Arya — Mon, 27 Jan 2014 13:37:14 GMT

End host Tracking needs the Bridge mib data, i.e, the Mac addr table/Cam table entry from device to show end hosts. With the error it is clear that LMS is not able to poll the bridge mib.

Bridge MIB is not as simple as directly polling device for data. It needs SNMP string indexing, which means it has to include @ sign after community to poll each vlan for mac addr's.

For example, the Catalyst switch includes one instance of the standard BRIDGE-MIB for each Virtual LAN in the switch. If the read-only community string is "public" and the read-write community string is "private", one could use "public@25" to read the BRIDGE-MIB for VLAN 25 and use "private@33" to read and write the BRIDGE-MIB for VLAN 33. If just "public" or "private" is used, the BRIDGE-MIB for VLAN 1 is accessed.

This is different when SNMP v3 is used. You have to configure snmp context than, as SNMP string indexing doesn't work on SNMP v3.

If you are using snmp v3, please check the following doc to see how contexts are created :

http://www.cisco.com/en/US/docs/switches/datacenter/sw/4_2/nx-os/system_management/configuration/guide/sm_9snmp.html#wp1070467

If using SNMP v1/v2c please manually poll the device by adding @ on community string and see it works.

-Thanks

Vinod

**Rating Encourages contributors, and its really free. **