Not sure if anyone can help with this, but I added my Cisco Nexus 5k switches to UDT but I am not seeing any port details for any of the ports. I see all ports, but device data for each port is not showing up.
Hi Kurt,
UDT has sometimes issues with monitoring ports on Nexus devices (assuming you have virtual ports there too). could you briefly look and validate the compatibility in this KB: http://knowledgebase.solarwinds.com/kb/questions/3245/Cisco+Nexus+Switch+NX-OS+%28Network+Operating+System%29+Support and let me know? if you would be struggling with that, I'll organize short session with support or engineering team.
thanks,
Michal
The only items it is showing as not supported are below. I am running Version 7 on the NXOS on these 5k's.
15 lldpCacheTable NotSupported
16 lldpAddrCacheTable NotSupported
that's bit surprising as I can see many more OIDs not supported for 5K Nexus devices in version 6... Therefore, a call with Dev would be probably the best to double check the OIDs supported and to see if there is something we can do. Switching to email conversation to agree on the date/time...
Peter
I've had a case open with Solarwinds and Cisco development for our issue. UDT wasn't populating the mac/IPs for ALL ports, but only one or two vlans. After quite a bit of troubleshooting and research, we noticed this was specific to FEX ports off of our nexus. We were seeing only the ports that had vlans on the line cards in the nexus , but not in the FEX units because layer 2 ports in the FEX don't fill the vmMembershipSummaryTable. We verified this by assigning a line card port to a layer 2 vlan that wasn't populating and sure enough it started working, displaying mac and IP info on the ports in the FEX for that vlan. Remove that vlan from the line card, and the vlan info disappears from the vmMembershipSummaryTable and udt is unable to display it.
Here is the odd part, if you use Switchport mapper you are able to see all the devices (MAC address, IP address, VLAN,etc.) just fine, but with UDT you are not able to see that information.
I was all good with this thread until you mentioned Switchport mapper works when UDT does not.
Not super happy about that and contemplating worth at this point.
Do you guys have FEX units connected to your Nexus?
Yes. FEX connected to 5K.
Check out my thread - UDT not working on Nexus FEX units I've spent way too much time on this - Cisco's vmMembershipSummaryTable isn't being populated by the layer 2 ports on the FEX, because the port if index value is greater than 2048. Because the vmMembershipSummary Table isn't populated, UDT doesn't know to go grab the dot1dBasePortTable@vlanXXX. I've opened both cisco cases and sw cases and thats the problem. If you have a line card in your nexus, and you put a port in that line card in a layer 2 vlan access port, magically that vlan will appear in UDT for all ports in that vlan including the FEX ports.
So, if what I am getting you are saying. If I take one of my blades on the Nexus 7K, or rather a few ports and put them on the same VLANs as I have on the FEX ports, I will see the information on the 5K's when polling via UDT?
Kurt H wrote:So, if what I am getting you are saying. If I take one of my blades on the Nexus 7K, or rather a few ports and put them on the same VLANs as I have on the FEX ports, I will see the information on the 5K's when polling via UDT?
Kurt H wrote:
So here is what I did. I've got a line card in module 7 on my 7018, its a 1/10gig ethernet module (n7k-f248xp-25 specifically but it shouldn't matter). I put port 48 in vlan 10. I've got no other line cards set as layer 2 ports in vlan 10, BUT i do have a bunch of FEX ports in vlan 10. Once I put that line card port eth1/48 in switch port access vlan 10, udt was able to display all the MACs and IPs for vlan 10 on all ports on that switch, including the FEX ports. And I'm doing all this via the UDT compatibility checker (C:\Program Files (x86)\SolarWinds\Orion\UDT) as its a lot easier to "see" it working than kicking off a UDT polling job and waiting forever.
Go into the UDT compatibility checker, create a new session, plug in all your info - and then once it gets done polling the switch in the upper right hand corner dropdown labeled session data, you can see all the stuff UDT is polling. if you goto the vmMembershipSummaryTable you will see the vlan's that are showing from the switch. Then in that same drop down, you should see two other things dot1dBasePortTable@vlanXXX and dot1dTpFdbTable@vlanXXX. The "@vlanXXX" is being grabbed from the vmMembershipSummaryTable. In my case there was no dot1dBasePortTable@10, until I added the vlan 10 to the line card port eth7/48. I can post screenshots if it'll help or if wanted.
I add the VLANS to a few ports on another card. Do you have Nexus 5K units and the FEX are coming off the 5Ks, or do you have the FEX directly connected to your 7K?
My FEXs are directly connected to my nexus 7k. No 5k in play here. 7k with a bunch of 10gig F2 or M2 cards, trunked off to a gazillion FEX units.
Did you try running the UDT compatibility checker? The card has to be a line card that is going to have a port ifindex value between 0-2048, FEX ports ifindex is calculated completely differently.
it baffles me that automag928 got that response from SW support.
This is the core functionality we are paying for when purchasing UDT and continue paying maintenance; and the application needs to keep up with the technology - especially Cisco as it is foundational for SW applications. Why should we have to vote up a Feature Request for core functionality?
michal.hrncirik, can you comment on this and where/if this is on the roadmap?
njoylif - So I probably need to respond here, but am sort of waiting for something official. I was able to get some visibility to my issue and have been working with a great support guy whose working with the dev team. We are in the process of testing (not sure what to call it?) a potential fix for this. I rather not go into details because I'm not exactly sure what I can / should say but suffice to say they (Solarwinds) are definitely aware of the issue and are working to resolve it.
I was hoping that they are working on a resolution to the problem. I know I sent Tech Support a lot of captures, logs, etc.. Being that the Nexus 2k/5K is being used more and more, it would be nice for a simple fix.
Yes kurtrh, our product engineering team is working on this fix as highest priority at the moment.
automag928 - no harm done, no worries and thank you very much for your help with this fix!
I know the UDT team was working on that, I'll let UDT product owner Peter K. to respond where may the beta come with this.
has there been anyword on when UDT will support the Cisco Nexus 5K and 2k's?
