| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw78727 | Title: | Nexus 6000 crash due to "fwm hap reset" |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
Nexus 6000 crash in "fwm hap reset"
Conditions:
Errors: "fwm_add_mac_move_notif: mac regist db is empty!"
Log: "restore pss - fwm pss: vlan does not exist"
The crash might occur after following scenario of double step ISSU:
1. Create some VLANs on NX-OS 6.0(2)N2(4)
2. ISSU from 6.0(2)N2(4) to 7.0(6)N1(1)
3. After upgrade to 7.0(6)N1(1) delete some of these VLANs
4. ISSU from 7.0(6)N1(1) to 7.0(7)N1(1)
5. Crash just after the ISSU
Workaround:
Before triggering a ISSU from 7.0(6)N1(1) to 7.0(7)N1(1), if some VLANs were deleted in 7.0(6)N1(1) then you will not see the VLAN in running config but you can see the VLAN in PSS "show platform fwm info pss runtime_vlan".
Recreate all the VLANs before the ISSU, so the running config and PSS are in sync. After system is moved to 7.0(7)N1(1) VLANs can be deleted safely.
Further Problem Description:
|
|
Last Modified: | 17-DEC-2015 |
|
Known Affected Releases: | 7.0(7)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu37102 | Title: | N5K kernel Panic on AIPC driver causing crash |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | A Nexus 5K/6K could reload due to a kernel panic
Symptom:
Conditions:
This has been seen on Nexus running 7.1(1)N1(1) and 7.0(6)N1(1)
Workaround:
Software fix is currently available in NX-OS 7.1(2)N1(1).
A debug plugin based workaround also exists. Please contact TAC to obtain the workaround.
Further Problem Description:
|
|
Last Modified: | 27-DEC-2015 |
|
Known Affected Releases: * | 6.0(2)N2(7), 7.1(1)N1(1), 7.3(0)N1(0.104) |
|
Known Fixed Releases: | 7.0(6)N1(1.4), 7.0(6)N1(2s), 7.0(7)N1(0.65), 7.0(7)N1(1), 7.0(7)ZN(0.141), 7.1(2)N1(0.575), 7.1(2)N1(1), 7.1(2)ZN(0.36), 7.2(1)N1(0.246), 7.2(1)N1(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq81648 | Title: | N5K: Po configured as fex-fabric does not work as normal VPC trunk port |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
On a Nexus 5K switch if we configure ports as a fex-fabric port-channel, and then configure the prots as regular VPC trunk port the links stop passing traffic.
Conditions:
Sequence of events
a) The physical interface needs to be configured as part of a fex-fabric port channel.
b) Configure the port-channel as a regular VPC trunk interface
Workaround:
The workaround is to use a different port-channel interface ID when configuring the VPC trunk port. For example, if you were using port-channel 2 as a fex-fabric interface, and want to use the same physical ports for creating a regular VPC, use port-channel 10.
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 5.2(1)N1(8a), 7.0(3)N1(0.99) |
|
Known Fixed Releases: * | 7.1(3)N1(0.647), 7.1(3)N1(1), 7.1(3)ZN(0.55), 7.2(2)N1(0.357), 7.2(2)N1(1), 7.2(2)ZN(0.41) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux66903 | Title: | L3Nor48fexScale: stp hap reset upon fp uplinks & peer-link shut together |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: * | Symptom:
Shutdown FP POs and Peer-Link PO together will result in stp hap reset. Seems to be a scale issue.
Conditions:
Need to shut all the POs together.
Workaround:
Shut the POs one after the other and issue will not be seen.
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 7.3(0)N1(0.245) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux60390 | Title: | L3 Norcal 48 fex scale: Fex configured mod dont show up after poweroff |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:`show module` failed to show up module after poweroff and no poweroff module
Conditions:Observed this issue on Nexus 6000 switch having vPC+ configuration and 24 fexes configured on the breakout ports of the same module. On vPC primary, it is found that `show module` failed to show up module after `poweroff module` and `no poweroff module`.
Workaround:1. First, shut down NIF port-channels configured for Fexes in the module being powered-off
2. Wait for Fexes to go to offline state
3. Run `poweroff module` and `no poweroff module`
|
|
Last Modified: | 21-DEC-2015 |
|
Known Affected Releases: | 7.3(0)N1(0.238) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut49092 | Title: | [comm:ethpm] WARNING: possible memory leak is detected on pers queue |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Switch will be throwing continuous errors about ethpm leak as
"2015 Mar 20 23:45:06 SPINE11 %$ VDC-1 %$ Mar 20 23:45:06 %KERN-2-SYSTEM_MSG: [29216.124753] [sap 175][pid 3942][comm:ethpm] WARNING: possible memory leak is detected on pers queue (len=3122,bytes=32760206) - kernel"
Conditions:
Issue is seen after a write erase, reload,copy bootflash:config to running config.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 28-DEC-2015 |
|
Known Affected Releases: | 7.0(6)N1(0.258) |
|
Known Fixed Releases: * | 7.2(2)N1(0.360), 7.2(2)N1(1), 7.2(2)ZN(0.44), 7.3(0)N1(0.208), 7.3(0)N1(1), 7.3(0)ZN(0.188) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw60905 | Title: | KOkomo158(FP): DHCP DISCOVERs in same vlan do not cause MAC learn in FWM |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
Multiple DISCOVERs in same vlan do not co-exist.
Conditions:
After the first DISCOVER causes auto-config, subsequent DISCOVERs do not cause MAC learn in FWM.
Workaround:
Further Problem Description:
|
|
Last Modified: | 15-DEC-2015 |
|
Known Affected Releases: | 7.3(0)N1(0.158) |
|
Known Fixed Releases: * | 7.3(0)N1(0.237), 7.3(0)N1(1), 7.3(0)ZN(0.214) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw09852 | Title: | BFD not sent over FP core ports on 56128 |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
BFD neighborship will fail to come online when built on SVIs over fabricpath. Can successfully build BFD neighbors over the peer-link, but neighbors with other switches will fail to come online.
Conditions:
Nexus 56128 switch, running fabricpath and BFD on the SVI of a fabricpath enabled vlan
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 12-DEC-2015 |
|
Known Affected Releases: | 7.1(1)N1(1), 7.2(0)N1(1) |
|
Known Fixed Releases: * | 7.1(3)ZN(0.126), 7.1(4)N1(0.691), 7.1(4)N1(1), 7.2(2)N1(0.334), 7.2(2)N1(1), 7.2(2)ZN(0.10), 7.3(0)IZN(0.7), 7.3(0)N1(0.184), 7.3(0)N1(1), 7.3(0)ZN(0.166) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu22403 | Title: | N5K/6K Cosmetic Message: Mac registration with L2FM failed for mac... |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
In a Nexus 5K/6K running NX-OS 7.0(6)N1(1), following messages can be seen
5596A# show logg logfile | inc L2FM
2015 May 6 13:04:55 5596A %ADJMGR-3-MAC_REG_FAILED: adjmgr [3568] Mac registration with L2FM failed for mac 0022.55e9.b53f, iod Vlan15, phy iod: Ethernet115/1/38
2015 May 6 13:07:21 5596A %ADJMGR-3-MAC_REG_FAILED: adjmgr [3568] Mac registration with L2FM failed for mac 0000.0c07.ac0f, iod Vlan15, phy iod: Vlan15
2015 May 6 13:10:04 5596A %ADJMGR-3-MAC_REG_FAILED: adjmgr [3568] Mac registration with L2FM failed for mac 002a.6a1f.2341, iod Vlan15, phy iod: Ethernet130/1/48
2015 May 6 13:11:43 5596A %ADJMGR-3-MAC_REG_FAILED: adjmgr [3568] Mac registration with L2FM failed for mac 547f.ee7e.1441, iod Vlan15, phy iod: Vlan15
5596A#
Conditions:
Seen when the switch sees ARP request packets.
Workaround:
These messages are cosmetic. To suppress them configure 'logging level adjmgr 2'.
Further Problem Description:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 7.0(6)N1(0.272), 7.1(0)N1(0.401), 7.2(0)N1(1) |
|
Known Fixed Releases: * | 7.0(7)N1(0.291), 7.0(7)N1(1), 7.0(7)ZN(0.186), 7.1(3)N1(0.612), 7.1(3)N1(1), 7.1(3)ZN(0.17), 7.2(2)N1(0.357), 7.2(2)N1(1), 7.2(2)ZN(0.41) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux64958 | Title: | Documentation-Netflow missing BGP ASN and next hop IP detail |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:Documentation update is required to mention the restriction software imposes currently for Netflow collection of BGP ASN and next hop IP details.
Enhancement CSCuw66497 is currently pending for development for FIB to assist Netflow collection.
Conditions:Netflow collection of BGP ASN and next hop IP details.
Workaround:None. This is a documentation bug to outline the restrictions on config guides and release notes.
More Info:
|
|
Last Modified: | 24-DEC-2015 |
|
Known Affected Releases: | 7.0(1)N1(1), 7.1(1)N1(1), 7.2(1)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuv12279 | Title: | tiburon fex speed change on port causes flap on remaining ports on asic |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Ports on fex flap when one port is connected, flapped or speed is changed.
Conditions:
Speed change on a tiburon fex port
Workaround:
none, though increasing link debounce time may help for some servers.
Further Problem Description:
|
|
Last Modified: | 23-DEC-2015 |
|
Known Affected Releases: | 7.0(3)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux46284 | Title: | N5600 VXLAN Configuration Guide Missing Overlay Port Limitation |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: * | Symptom:
This is a documentation bug being filed to add the following limitation to the Nexus 5600 VXLAN Configuration Guide:
A non VNI enabled vlan with an SVI in the same VRF as the underlay interfaces is considered an overlay port. If this vlan is then allowed on a FEX HIF, vxlan encapsulated traffic will egress this port. In order to overcome this, these non VNI enabled vlan's should be configured in a VRF that is separate from that of the VRF that the underlay interfaces belong to.
Conditions:
The following Configuration guide is missing the above limitation:
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus5600/sw/layer2/7x/b_5600_Layer2_Config_7x/b_5600_Layer2_Config_7x_chapter_010010.html#concept_E41C6339B7414189B061E76F1BBBFB25
Workaround:
Further Problem Description:
|
|
Last Modified: | 14-DEC-2015 |
|
Known Affected Releases: | 7.2(1)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw91721 | Title: | KK158: arp is resolved but ping is not working with VRRPv2 |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
ARP is resolved for hsrp VIP but, ping for hsrp VIP from standby is not working
Conditions:
vPC+ pair where HSRP is configured and vmac is not installed on the standby.
Workaround:
Flap the HSRP group or the SVI on which hsrp is configured
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 7.3(0)N1(0.158) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv96234 | Title: | match datalink mac destination-address use field id 57 for ingress flow |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
"match datalink mac destination-address" use PostDestinationMacAddress for ingress flow
Conditions:
- configure flow record for ingress source/destination mac.
- nx-os use field id 56 (sourceMacAddress) for source mac
- nx-os use field id 57 (PostDestinationMacAddress) for destination mac.
- nx-os shoud use field id 80 (destinationMacAddress).
http://www.cisco.com/c/en/us/td/docs/routers/access/ISRG2/AVC/api/guide/AVC_Metric_Definition_Guide/avc_app_exported_fields.html
Workaround:
none
Further Problem Description:
This behavior seen on N7K.
- 7.2(1)D1(1)
- 6.2(12)
|
|
Last Modified: | 10-DEC-2015 |
|
Known Affected Releases: | 7.0(3)N1(1), 7.2(0)N1(1) |
|
Known Fixed Releases: * | 7.2(2)N1(0.346), 7.2(2)N1(1), 7.2(2)ZN(0.29), 7.3(0)N1(0.140), 7.3(0)N1(1), 7.3(0)ZN(0.128) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCux47933 | Title: | FEX2348 EVPC: HIF PO seconds of traffic drops after NIF failure |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
Traffic drop for up to 10-20 seconds for dual-homed FEX host ports when FEX fabric interfaces to one N5k switch are disconnected or that N5k switch is reloaded
Conditions:
FEX 2348UPQ Active/Active with enhanced VPC (port-channels on FEX Host ports)
Workaround:
Configure standalone FEX host ports (remove the enhanced VPC port-channel)
Further Problem Description:
|
|
Last Modified: | 09-DEC-2015 |
|
Known Affected Releases: | 7.1(3)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCus37334 | Title: | N56k: global FCF mac as src fcns fames for vfc's with bind mac-address |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
- N56k sends a name server PLOGI_ACC using vsan global FCF mac instead of interface MAC. ethanalyzer can be used to capture the mac address used.
- host's affected will not have access to their storage.
- host's affected will not have fcns "fc4-types", "symbolic-port-name" and "symbolic-node-name" registered with the name server.
------------------------
VSAN:10 FCID:0xd30060
------------------------
port-wwn (vendor) :50:01:99:93:ed:2a:10:0c
[A-D-bc1atrabl09-hba1]
node-wwn :50:01:99:93:ed:2a:10:0d
class :3
node-ip-addr :0.0.0.0
ipa :00 00 00 00 1e 00 01 30
fc4-types:fc4_features : ---->
symbolic-port-name : ---->
symbolic-node-name : ---->
port-type :N
port-ip-addr :0.0.0.0
fabric-port-wwn :21:30:8c:60:4f:25:81:7f
hard-addr :0x000000
permanent-port-wwn (vendor) :50:01:99:93:ed:2a:10:0c
connected interface :vfc305
switch name (IP address) :RF_NEXUS1_SR1 (10.200.99.211)
- the following errors are shown under
"`show platform software fcoe_mgr event-history errors`"
356) Event:E_DEBUG, length:80, at 971774 usecs after Thu Dec 18 18:49:06 2014
[102] fcoe_mgr_fill_get_fcoe_info(2822): vfc301 eth_ifindex is invalid, skipping
Conditions:
all of the following must apply for the issue to be a hit on this bug.
- Nexus 5600 or 6000 only "N55k is not affected".
- software code 7.x.
- vfc's are configured to using "bind mac-address":
interface vfc301
bind mac-address 0019.993E.D302
switchport trunk allowed vsan 10
switchport description FCoE-to-Blade
no shutdown
Workaround:
configure the following:
- remove the vfc interfaces with bind mac-address.
- use one vfc interface that is bind to the physical interface.
- enable NPIV on the switch.
feature npiv
interface vfc 1
bind interface port-channel 1
switchport trunk allowed vsan 10
switchport description FCoE-to-Blade
no shutdown
with this setup, instead of using multiple vfc interfaces each one that is bound to a MAC. we will use on interface, and all the host's will login through that one vfc which is allowed through NPIV.
Further Problem Description:
|
|
Last Modified: | 08-DEC-2015 |
|
Known Affected Releases: | 7.0(5)N1(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCux34522 | Title: * | %VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on vsh. |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: | Symptom:
Logs may appear while nobody is accessing the device :
%VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on console
%VSHD-5-VSHD_SYSLOG_CONFIG_I: Configured from vty by admin on vsh
Conditions:
Cosmetic - triggered by internal processes. May happen during bootup, interface flap, system switchover or other conditions.
Workaround:
none
Further Problem Description:
|
|
Last Modified: | 02-DEC-2015 |
|
Known Affected Releases: | 7.1(3)N1(0.619) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw66497 | Title: | Netflow missing BGP ASN and next hop IP details |
|
Status: | Open |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Nexus5600/6000 Series switches unable to collect BGP SRC/DST ASN and next hop IP details for the flow.
These fields are populated through FIB table which currently is not supporting this collection for these platforms.
Conditions:
Netflow Export configured on the switch to collect BGP ASN and next hop IP detail for the flow.
Workaround:
None. Development team will work to enhance FIB to support Netflow collection.
Further Problem Description:
|
|
Last Modified: | 22-DEC-2015 |
|
Known Affected Releases: | 7.1(1)N1(1), 7.3(0)N1(0.94) |
|
Known Fixed Releases: | |
|
|
| |
:
2015 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论