We use cisco dcnm to find out on which port / interface a server is connected to a FEX or the Nexus switches (9332PQ and 9372PX-E).
Unfortunately, the DCNM does not display this information (Cisco Prime does if the device is connected to a Nexus 93...
Cisco told us that the Nexus 9332PQ will not be supported by Cisco's Prime Infrastructure.
But it was no problem to buy licenses for the Nexus 93xx for Cisco Prime.....
Are there any other Nexus 9332PQ owners they want this to support by Cisco (...
We have the same issue at our customers WLAN.
WLC5520 with HA, Software 8.5.120.0, AP "AIR-AP2802I-E-K9" , since upgrade from 8.5.110.0 to 8.5.120.0 all the switch logs are full (WS-C2960XR-48LPD-I).
We disable the CDP as workaround.
Hi
I currently in fight with myself, I want to hear what you would prefer about the routing.
1 = N9K-C9372PX-E2 = N9K-C9372PX-E3 = N9K-C9372PX-E4 = N9K-C9372PX-E
5 = N9K-C9332PQ6 = N9K-C9332PQ
Nexus 1+2 should have 2 "back to back VPC" connections...
During upgrade of two Nexus 3548 from 9.6.0.2.A6.2 to 9.6.0.2.A6.5a we got the following output:
at006-core01# install all system n3500-uk9.6.0.2.A6.5a.bin kickstart n3500-uk9-kickstart.6.0.2.A6.5a.bin non-interruptiveInstaller is forced disruptive
...
Disable IP-Device tracking also solves this issue. Do this on uplink ports.
CAT9000: device-tracking attach-policy DT_trunk_policy
CAT:2960x: ip device tracking maximum 0
Booth on uplinks and AP ports only.
Same on C9200-24P with 17.06.04
In between IPv6 filter engaged, no changes, the one and only AP on this switch rebootet, but also in between, no changes. IPv6 filter only on user ports, not on uplink ports (23+24).
CPU utilization for five seconds...
Hi
You have to power-cycle the Switch, then it works fine (as workaround)
We currently have a TAC Case opened for this issue.
Cisco SR 684429477 for the 3560 POE issue
And we have this bug fixed with a firmware upgrade to 15.2(4)E6
Cisco Su...
