I've installed a Cisco Prime infrastructure 2.0 and it's working perfectly except for Nexus 7k : I canot see the wired client connected (useful for traking) while it's working fine on many other devices. The devices are managed with an inventoy collection completed (No data vailable in Device Details/ clients / current associated wired clients).
I heard that the full netflow is not supported on the 7ks. You shouldnt have issues if you purchased a specific module for the Nexus that enables full Netflow. Im not sure what that module is currently.
Issue with Nexus can be if SNMP V3 is configured. You should have snmp context configured on device, which would help getting end hosts clients being discovered.
-Thanks
Vinod
**Rating Encourages contributors, and its really free. **
I have a ticket open with TAC on this, they are saying this is supposed to work in PI 2.0, but have yet to come with resolution. I have tried using SNMPv2 and SNMP v3 with no success.
Nexus 7k and 5K in LMS 3.2.1. “When adding the Nexus devices to DCR, provide the “netadmin SNMP RO credential”. When other SNMP RO credential is provided, user tracking will not collect end host data. The Nexus device should be running NXOS 5.1(1), 5.1(3) or later. 5.1(2) is not supported.
Configure the device to map community with context using the below command: snmp-server context vrf, snmp-server mib community-map context
Please let us know what the progress is of the TAC case. I'm very interested.
Kind Regards
Ad
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
