LMS4.2.4 failed Campus Manager inventory and UT with Nexus 5548UP switches
All Nexus 5548UP switches with attached 2248 FEX's are failed in Data colectection (CM part) if you check this at inventory => Collection status. All other inventory, Faultmanagement, CV ... is working with this type of devices.
As compared with LMS4.2 SDT one basic Campus Manager feature should be supported at LMS4.2 with all DC Switches:
Network Topology Layer 2 Services
So I cant understand the overal failed status for Data colectection for this devices.
as wrtiten in LMS4.2 SDT:
User Tracking (Nexus 1K, 4K, 5K and 7K with FEX), VLAN Management, VRF Lite, LANE Management
is not supported. Because there is a huge time diff between 4.2.0 and 4.2.5. Could we expect that Usertracking at NX5548UP with FEX will be working at LMS4.2.5?
If not, will this work with Prime Infrastructer 2.1 or later 2.2?
User Tracking (Nexus 7K without FEX and with FEX (for image version NX-OS 5.1(1) from LMS 4.2.3 version onwards for the OIDs 126.96.36.199.188.8.131.52.184.108.40.2062, 220.127.116.11.18.104.22.168.22.214.171.1247, 126.96.36.199.188.8.131.52.184.108.40.2062), Nexus 5k without FEX and with FEX (for device models Nexus5548P, Nexus5596UP, Nexus5548UP, Nexus5596T) - UT is supported for image version 6.0(2)N1(1) from LMS 4.2.3 version onwards for the OIDs 220.127.116.11.18.104.22.168.22.214.171.1248,126.96.36.199.188.8.131.52.184.108.40.2064, 220.127.116.11.18.104.22.168.22.214.171.1248,126.96.36.199.188.8.131.52.184.108.40.2065), Nexus 5010, Nexus 5020 without FEX and with FEX - UT is supported for image version 5.2(1)N1(4) from LMS 4.2.3 version onwards for the OIDs 220.127.116.11.18.104.22.168.22.214.171.1248, 126.96.36.199.188.8.131.52.184.108.40.2069)
Please check your device sysObjectID output and match if it is supported. Are you running min supported image or higher : 6.0(2)N1(1).
Some old version have known issues with n5k. The bugs CSCua19439 and CSCtx42727 need to be resolved for nexus5k device( as of now fixed for Nexus7k). Once the bugs are resolved ,then we can support user tracking for Nexus5K.
I will check for a good NXOS 6 version, because I dont want to degreese network stabability with giving a network management functionality by our Nexus specialists and propose the upgrage to the customer. If he will agree to the upgrade we will do this.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...