The most recent content from our members.
This is related to my post in the UDT forums - UDT not working on Nexus FEX units Currently Cisco Nexus FEX layer 2 access ports are not populating the vmMembershipSummaryTable because the port ifindex is above the limit of 2048. Because the vmMembershipSummaryTable is not populated, UDT does not know which vlans to grab…
Other then the interface poll, Does NPM support FEX Modules? Like they do for switch stacks?
I've run into an issue with UDT polling Nexus FEX ports. Basic background - the majority of my network over the last few years has migrated from Cat6500s to Nexus 7018s, with FEX 2248s. I've had users come to me and tell me they aren't seeing MACs and IPs for devices on the Nexus switches. I started doing some exploring…
I've got a problem with Nexus FEX ports throwing bogus Tx/Rx utilization amounts. I don't have this problem with ports native to the Nexus cores, only on the FEX ports. I've verified that port speed is detected correctly and that the devices/interfaces have 64-bit counters enabled. There are no similarities of devices…
It looks like you're new here. Sign in or register to get started.