| |
|
Alert Type: | Updated * |
Bug Id: | CSCuq05010 | Title: | Nexus 3100: QSFP-40G-SR-BD V01 Generates TX-LOS after Multiple Reloads |
|
Status: | Open |
|
Severity: | 2 Severe |
Description: | Symptom:
Optical link does not come up after switch reload.
Conditions:
- QSFP-40G-SR-BD V01 (serial number up to and including AVM1813xxxx)
- Multiple reloads
Workaround:
Two workarounds are available on this platform:
- Reseat QSFP
- Reload switch
Further Problem Description:
This is an intermittent issue with a very low failure rate , field failure rate is less than 0.01%.
Issue is not seen in QSFP-40G-SR-BD V02.
Related bug for Nexus 7000: CSCuo76571
|
|
Last Modified: | 18-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U3(2.61) |
|
Known Fixed Releases: * | 6.0(2)A6(4.116), 6.0(2)A6(5), 6.0(2)U6(3.116), 6.0(2)U6(4) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv29193 | Title: | ECMP route installed with single NH in certain scenario |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
In certain conditions a prefix that is ECMP is installed with single NH
Conditions:
This is seen in the following conditions
ECMP table usage crosses and comes below maximum group usage (64)
There are 16 SVI over which ECMP adjacencies are learnt
These 16 SVI ride on a single physical link
All 16 SVI are flapped aggressively
Workaround:
Clear the entire v4 and v6 routing table
Further Problem Description:
|
|
Last Modified: | 24-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U6(1.72) |
|
Known Fixed Releases: * | 6.0(2)A6(3.74), 6.0(2)A6(4), 6.0(2)U3(7.106), 6.0(2)U3(8), 6.0(2)U3(9), 6.0(2)U6(1.74), 6.0(2)U6(2) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut32936 | Title: | PTP not sending Follow_up message on N3K |
|
Status: | Fixed |
|
Severity: | 2 Severe |
Description: | Symptom:
PTP Master is not forwarding ptp followup message when ptp sync interval -1,0,1
Conditions:
If ptp sync interval -1,0,1, ptp followup message was not forwarded.
Workaround:
N/A
Further Problem Description:
N/A
|
|
Last Modified: | 11-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U4(1) |
|
Known Fixed Releases: * | 6.0(2)A6(1.132), 6.0(2)A6(2), 6.0(2)U6(0.132), 6.0(2)U6(1), 7.0(3)I2(0.578), 7.0(3)I2(1), 7.0(3)IMK2(1), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1), 7.0(3)ITI2(1.36) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv08443 | Title: | Cisco Nexus 3000 VDC Authenticated Privilege Escalation Vulnerability |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
A vulnerability in Command Line Interface (CLI) parser of the Cisco Nexus Operating
System (NX-OS) devices could allow an authenticated, local attacker to perform a
privilege escalation at the CLI.
The vulnerability is due to improper input validation of special characters within
filenames. An attacker could exploit this vulnerability by authenticating at the local
shell and writing a file to disk with certain special characters. The attacker could then
use that file with other CLI commands to obtain an shell prompt at their current
privilege level. An exploit could allow the attacker to read/write files and perform
other privileged commands.
Conditions:
Device running with default configuration running an affected version of
software.
Workaround:
The user has to be authenticated so use care when distributing ''admin''
credentials to only trusted sources.
Further Problem Description:
Credit:
Cisco would like to thank Jens Krabbenhoeft for discovering and reporting this vulnerability.
PSIRT Evaluation:
The Cisco PSIRT has assigned this bug the following CVSS version 2 score. The Base and Temporal CVSS scores as of the time of evaluation are
4.3/4.1:
http://tools.cisco.com/security/center/cvssCalculator.x?vector=AV:L/AC:L/Au:S/C:P/I:P/A:P/E:F/RL:U/RC:C&version=2.0
CVE ID CVE-2015-4237 has been assigned to document this issue.
Additional information on Cisco's security vulnerability policy can be found at the following URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
|
|
Last Modified: | 10-SEP-2015 |
|
Known Affected Releases: | 7.2(0)ZZ(99.1) |
|
Known Fixed Releases: * | 6.0(2)A7(0.232), 6.0(2)A7(1), 6.0(2)U7(0.232), 6.0(2)U7(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuu99585 | Title: | Need to have configurable ECMP table size |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
This is not a bug but feature request. Currently we support 64 ECMP objects. This request is to make this number configurable.
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 10-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U6(1) |
|
Known Fixed Releases: * | 7.0(3)I2(1) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCun42549 | Title: | Service SSH (Weak MAC Algorithms) is enabled by default in N3K |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | <B>Symptom:</B>
The user needs the ability to configure the Secure Shell (SSH) ciphers on the N3K side and not just the client.
<B>Conditions:</B>
The device is configured for SSH remote access.
<B>Workaround:</B>
Configure the ciphers desired on the client side.
<B>Further Problem Description:</B>
None.
|
|
Last Modified: | 01-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U3(0.72) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut79980 | Title: | Copy to HTTP server outputs "Copy complete" when copy fails |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When copying a file from N3K to HTTP server, "Copy complete, now saving to disk (please wait)..." is displayed when the copy fails in some situations.
Conditions:
When copying a file from N3K to HTTP server, "Copy complete, now saving to disk (please wait)..." is displayed when the copy fails in some situations.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 11-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U5(1), 6.0(2)U6(1) |
|
Known Fixed Releases: * | 7.0(3)IMK2(1), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1), 7.0(3)ITI2(1.36), 8.3(0)CV(0.123) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut57959 | Title: | N3132: After breaking in port with pfc, pfc buffer remains on 10g ints |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
PFC resources remain allocated to unconfigured ports when port-breakin is applied on 10G interfaces to make it a 40G interface.
Conditions:
With PFC resources already allocated for 10G ports, if port-breakin is done on the 4x10G ports, PFC resources are freed only for the first port which became a 40G port, resources remain in use for the other 3x10G ports which got removed.
Workaround:
Explictly unconfigure PFC on the 4x10G ports before port-breakin is applied using "priority-flow-control mode off".
Further Problem Description:
Logs to see the issue:
//Break-in
N3132X-HL-6(config-if)# int e1/17/1
N3132X-HL-6(config-if)# speed 40000
N3132X-HL-6(config-if)# int e1/17
N3132X-HL-6(config-if)# no shut
N3132X-HL-6(config-if)# show platform software qd info pfc mmu-reservation
Total shared cells in hardware : 53854
PFC MMU buffer reservation percent : 32%
PFC MMU bufer reservation cells : 17233
Cells allocated for PFC ports : 7224
PFC enabled port bitmap : 65-68,72,76,80,84,88,92,103
LLFC enabled port bitmap :
Input queuing policy port bitmap :
Port MMU usage details
Port 1/64 : 0 Port 1/65 : 0 Port 1/66 : 264 Port 1/67 : 264 Port 1/68 : 264 Port 1/69 : 804
Port 1/70 : 0 Port 1/71 : 0 Port 1/72 : 0
Port 1/73 : 804 Port 1/74 : 0 Port 1/75 : 0
|
|
Last Modified: | 11-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U6(0.147), 7.0(3)I2(0.495) |
|
Known Fixed Releases: * | 7.0(3)I2(0.514), 7.0(3)I2(0.542), 7.0(3)I2(1), 7.0(3)IMK2(1), 7.0(3)IMK2(1.15), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1), 7.0(3)ITI2(1.36), 8.3(0)CV(0.123) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut02440 | Title: | When N3500 is GM, PTP Announce comes with utc_reasonable flag set to F |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When a Nexus 3500 is Grandmaster, the utc_reasonable flag in the ptp announce message is set to false.
In a design with an active and standby GM clocks. In case of active GM failure, Nexus may become GM for a short while till the standby takes over. Because Nexus doesn't set the utc_reasonable flag, the clock on the slave ptp devices will jump by utc_offset (35 sec).
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 11-SEP-2015 |
|
Known Affected Releases: | 6.0(2)A1(1c), 6.0(2)A4(4) |
|
Known Fixed Releases: * | 6.0(2)A4(5.47), 6.0(2)A4(6), 6.0(2)A6(1.127), 6.0(2)A6(2), 6.0(2)U4(4.47), 6.0(2)U4(5), 6.0(2)U6(0.127), 6.0(2)U6(1), 7.0(3)I2(0.569), 7.0(3)I2(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv67133 | Title: | Interface config wipeout failed on defaulting tunnel interface with desc |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When a tunnel interface, which has description configured, is defaulted using "default interface tunnel " command, it will fail.
"show run interface tunnel " would still show description configured.
Conditions:
Applicable for Tunnel interface and description must have been configured
Workaround:
Go to interface config mode for the same tunnel interface and do "no description" manually for work around
Further Problem Description:
|
|
Last Modified: | 11-SEP-2015 |
|
Known Affected Releases: | 7.0(3)I2(0.530) |
|
Known Fixed Releases: * | 7.0(3)I2(0.539), 7.0(3)I2(1), 7.0(3)IMK2(1), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1), 7.0(3)ITI2(1.36) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuw10287 | Title: | Filter option for local SPAN is not working |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
Filter option for local span not working. Filter gets applied on a different monitor session.
switch# sh hardware internal libsdk mtc span sess-entry-mask-reg
SPAN_SESS_ENTRY_MASK_CFG:
SESS SESS SESS SESS SESS SESS SESS SESS
0 1 2 3 4 5 6 7
F F F F F F F F
I I I I I I I I I I I I I I I I
L N E L N E L N E L N E L N E L N E L N E L N E
T G G T G G T G G T G G T G G T G G T G G T G G NOTES
----- ----- ----- ----- ----- ----- ----- ----- ----- -----------------
ENTRY 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 INVERTED ALREADY
MASK 0 1 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Ingress bit is set to 1 for Monitor session 0 and Filter bit is set to 1 for Monitor session 1.
Conditions:
Local Span
Workaround:
None
Further Problem Description:
Filter option on ERSPAN was fixed in the defect#CSCus87538
|
|
Last Modified: | 13-SEP-2015 |
|
Known Affected Releases: | 6.0(2)A6(4.108) |
|
Known Fixed Releases: * | 6.0(2)A7(0.235), 6.0(2)A7(1), 6.0(2)U7(0.235), 6.0(2)U7(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv95538 | Title: | N3K AFM memory leak in libglib-2.0.so.0.1600.3 |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
AFM service hap reset due to a memory leak
Conditions:
This has been seen on N3K platform running 6.0(2)A6(3) code.
show platform afm mem-stats detail
154 [r-xp]/lib/libc-2.8.so 10151 10153 985546 1220292
157 [r-xp]/lib/libglib-2.0.so.0.1600.3 210512 210684 63038322 63079362
--------------------------------------------------------------------------------
Total bytes: 64320620 (62813k)
--------------------------------------------------------------------------------
Total bytes: 455700 (445k)
--------------------------------------------------------------------------------
Grand total bytes: 89982801 (87873k)
LHC-JPM-EMM-ASN-P01# show process memory | i afm
3691 241053696 565047718 1400832 287354880 58527744 fff86900/ffffffff afm
Workaround:
Not Known
Further Problem Description:
|
|
Last Modified: | 29-SEP-2015 |
|
Known Affected Releases: | 6.0(2)A4(5) |
|
Known Fixed Releases: * | 6.0(2)A7(0.255), 6.0(2)A7(1), 6.0(2)U7(0.255), 6.0(2)U7(1) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus81590 | Title: | n3500 interface byte counter is inaccurate |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
The input packet counters and input byte counters are not sync.
Conditions:
When frames ingressing to a port.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 18-SEP-2015 |
|
Known Affected Releases: | 6.0(2)A4(3) |
|
Known Fixed Releases: * | 6.0(2)A6(2.58), 6.0(2)A6(3), 6.0(2)A6(3.77), 6.0(2)A6(3.95), 6.0(2)A6(4), 6.0(2)U6(1.58), 6.0(2)U6(1.77), 6.0(2)U6(1.95), 6.0(2)U6(4) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv24760 | Title: | Service "fs-daemon" (PID 4259) hasn't caught signal 6 (core will be save |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
fs-daemon process may restart unexpectedly.
Conditions:
unknown
Workaround:
Unknown
Further Problem Description:
|
|
Last Modified: | 18-SEP-2015 |
|
Known Affected Releases: | 5.0(3)U3(1) |
|
Known Fixed Releases: * | 6.0(2)A6(4.113), 6.0(2)A6(5), 6.0(2)U6(2.113), 6.0(2)U6(4) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv68669 | Title: | Slow-receiver feature cannot be applied on 1G interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When applying "slow-receiver" on a 1G port generates the following error message:
"Multicast slow receiver configuration is supported only on 1G ports"
Conditions:
Applying hardware profile multicast slow-receiver port on a 1G interface
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 18-SEP-2015 |
|
Known Affected Releases: | 6.0(2)A6(3.68) |
|
Known Fixed Releases: * | 6.0(2)A6(3.101), 6.0(2)A6(4), 6.0(2)U6(1.101), 6.0(2)U6(4) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv71673 | Title: | QoS: Disallow unsupported priority levels 2 and 3 in pmap config |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: * | Symptom:
T+ based Nexus 3000 switch allows to configure priority level 2 and 3 in queuing policy, but functionality of priority level 1 is supported. While applying the policy it throws an error when priority level 2 and 3 configured.
Conditions:
On T+ based Nexus 3000 switch allows to configure priority level 2 and 3 in queuing policy map.
Workaround:
Further Problem Description:
|
|
Last Modified: | 24-SEP-2015 |
|
Known Affected Releases: | 7.0(3)I2(0.541) |
|
Known Fixed Releases: * | 7.0(3)I2(1.17), 7.0(3)I2(2) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw31286 | Title: | FR:Repave:QI:"no negotiate auto" removed & "speed 10000" added under PO |
|
Status: | Terminated |
|
Severity: | 3 Moderate |
Description: | Symptom:
When fast-reload is performed with ascii config, if the configuration contains port-channels with 10G members, after fast-reload, the port-channel speed becomes "speed 10000" instead of "speed auto". This does not have any functional impact
Conditions:
Only when fast-reload is performed with ASCII configuration (repave)
Workaround:
None required
Further Problem Description:
|
|
Last Modified: | 24-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U6(3.114) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCun19114 | Title: | port channel members flapping on peer reload in VPC on MTC and Trident |
|
Status: * | Terminated |
|
Severity: | 3 Moderate |
Description: * | Symptom:
PO members in the VPC PO(goes to suspend momentarilywhile comming up after reload of the secondary VPC switch)
Conditions:
VPC secondary reload
Workaround:
No work around required. Comes up on its own. Also traffic will continue to flow through the primary during this short period while secondary VPC is comming up.
Configure "lacp suspend-individual" on PO member links to avoid getting into STP dispute state due to PO members transitioning to I-state during bring up. This workaround was tested on 6.0(2)U6(1) CCO image
Further Problem Description:
|
|
Last Modified: | 07-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U3(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCuv75209 | Title: | Nexus 3064T detects non-existent SFP on 40G interface |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When configuring "hardware profile portmode 48x10G+4x40G" and reloading N3k, unknown SFP might be detected on 40G interfaces though SFP is not inserted.
The unknown SFP's serial number is always "AVP1525S301".
At that time, "show interface transceiver" may show the following output;
Ethernet1/xx
transceiver is present
type is 40Gbase-SR
name is CISCO-AVAGO
part number is AFBR-79E4Z-CS1
revision is 02
serial number is AVP1525S301
nominal bitrate is 10300 MBit/sec
Link length supported for 50/125um OM3 fiber is 100 m
Link length supported for 50/125um OM2 fiber is 30 m
cisco id is --
cisco extended id number is 16
OR
Ethernet1/xx
transceiver is present
type is QSFP-40G-SR4
name is UNKNOWN
part number is
revision is
serial number is
nominal bitrate is 10300 MBit/sec
Link length supported for 50/125um OM3 fiber is 100 m
Link length supported for 50/125um OM2 fiber is 30 m
cisco id is --
cisco extended id number is 16
Conditions:
Nexus - 3064T
NXOS - 6.0(2)U3(7), 6.0(2)U4(3), 6.0(2)U5(1), 6.0(2)U6(1)
Workaround:
By Installing QSFP+ in the affected port then reseating it again, correct SFP information will be shown.
Further Problem Description:
|
|
Last Modified: | 29-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U5(1), 6.0(2)U6(1) |
|
Known Fixed Releases: * | 6.0(2)U6(3.126), 6.0(2)U6(4) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw14219 | Title: | Icaria : route-map changed after upgrade to Camden |
|
Status: | Fixed |
|
Severity: | 3 Moderate |
Description: | Symptom:
When upgrading from U6(2) or U6(3) to Camden, "set ip/ipv6 next-hop unchanged" will be changed to "set ip/ipv6 precedence routine" after upgrading to Camden
Conditions:
When upgrading from U6(2) or U6(3) to Camden, "set ip/ipv6 next-hop unchanged" will be changed to "set ip/ipv6 precedence routine" after upgrading to Camden
Workaround:
None. After upgrading to Camden the configuration will need to be changed
Further Problem Description:
|
|
Last Modified: | 25-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U6(2.111) |
|
Known Fixed Releases: | 6.0(2)A6(4.112), 6.0(2)A6(5), 6.0(2)U6(2.112), 6.0(2)U6(4) |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut60707 | Title: | I/O errors due to Journal corruption causes RO mount |
|
Status: | Open |
|
Severity: | 3 Moderate |
Description: | Symptom:
I/O Errors due to Journal corruption causes eUSB to remount as RO
Conditions:
Journal corruption.
Workaround:
reload the device If the issue reoccurs RMA
Further Problem Description:
RO mount is expected behavior by the fs as a damage control by continous I/O write attempt.
|
|
Last Modified: | 26-SEP-2015 |
|
Known Affected Releases: * | 6.0(2)U2(4.92.4Z), 6.0(2)U6(4) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw40964 | Title: | GRE tunnel terminating on N3K drops OSPF packets with ttl not 1 in hw |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Establishing an OSPF neighbor over a tunnel interface terminating on a Nexus 3100 switch will fail if the sending device is transmitting the OSPF packets with a TTL value greater than 1.
These OSPF packets will be dropped in hardware and not sent to the cpu for further processing.
Conditions:
The GRE tunnel must be terminating on the Nexus 3100 switch, and the GRE payload must be an ip OSPF packet with the TTL set to a value other than 1.
Workaround:
This configuration will work on other Cisco devices, however, RFC 2328 - OSPF Version 2 states the following:
Use of IP multicast. Some OSPF messages are multicast, when
sent over broadcast networks. Two distinct IP multicast
addresses are used. Packets sent to these multicast addresses
should never be forwarded; they are meant to travel a single hop
only. To ensure that these packets will not travel multiple
hops, their IP TTL must be set to 1.
The only workaround is to correct the OSPF implementation on the sending device.
Further Problem Description:
|
|
Last Modified: | 25-SEP-2015 |
|
Known Affected Releases: | 7.0(3)I2(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw40970 | Title: | GRE tunnel terminating on N3K drops OSPF packets with ttl not 1 in hw |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Establishing an OSPF neighbor over a tunnel interface terminating on a Nexus 3100 switch will fail if the sending device is transmitting the OSPF packets with a TTL value greater than 1.
These OSPF packets will be dropped in hardware and not sent to the cpu for further processing.
Conditions:
The GRE tunnel must be terminating on the Nexus 3100 switch, and the GRE payload must be an ip OSPF packet with the TTL set to a value other than 1.
Workaround:
This configuration will work on other Cisco devices, however, RFC 2328 - OSPF Version 2 states the following:
Use of IP multicast. Some OSPF messages are multicast, when
sent over broadcast networks. Two distinct IP multicast
addresses are used. Packets sent to these multicast addresses
should never be forwarded; they are meant to travel a single hop
only. To ensure that these packets will not travel multiple
hops, their IP TTL must be set to 1.
The only workaround is to correct the OSPF implementation on the sending device.
Further Problem Description:
|
|
Last Modified: | 25-SEP-2015 |
|
Known Affected Releases: | 7.0(3)I2(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCut79953 | Title: | Copy to HTTP server returns HTML response from HTTP server to cli |
|
Status: | Fixed |
|
Severity: | 4 Minor |
Description: | Symptom:
When copying a file from N3K to HTTP server, the N3K outputs to the cli the HTML response from the HTTP server. This is no ideal for the user to see.
Conditions:
When copying a file from N3K to HTTP server, the N3K outputs to the cli the HTML response from the HTTP server. This is no ideal for the user to see.
Workaround:
None
Further Problem Description:
|
|
Last Modified: | 11-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U5(1), 6.0(2)U6(1) |
|
Known Fixed Releases: * | 7.0(3)IMK2(1), 7.0(3)IMK2(1.65), 7.0(3)ITI2(1), 7.0(3)ITI2(1.36), 8.3(0)CV(0.123) |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw21603 | Title: | ip tftp source-interface vrf does not change vrf for tftp copy |
|
Status: | Open |
|
Severity: | 4 Minor |
Description: | Symptom:
Configuring ip tftp source-interface mgmt0 vrf management does not change the default vrf from default to management when issuing the copy tftp: bootflash: command
Conditions:
Workaround:
add the keyword 'vrf management ' to the copy command
Further Problem Description:
|
|
Last Modified: | 13-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U5(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | New |
Bug Id: | CSCuw07773 | Title: | Document Update N3k QoS 3548 No-Drop |
|
Status: | Open |
|
Severity: | 5 Cosmetic |
Description: | Symptom:
When applying the following policy-map the following error message is displayed.
N3k(config-sys-qos)# service-policy type network-qos MY-POLICY
ERROR: Unable to perform the action due to incompatiblity: Module 1 returned status "Not all cos values can be mapped to no-drop classes
Conditions:
This error message is encountered when attempting to configure a no drop QoS policy to a QoS group other than group 1.
Workaround:
Only qos-group 1 can be configured as a no drop class.
Further Problem Description:
This is a defect to get a document updated for the Nexus 3548.
http://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus3548/sw/qos/602_A1_1/b_N3548_QoS_Config_602_A11/b_N3548_QoS_Config_602_A11_chapter_0100.htm
|
|
Last Modified: | 02-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U6(1) |
|
Known Fixed Releases: | |
|
|
| |
| |
|
Alert Type: | Updated * |
Bug Id: | CSCus01626 | Title: | Need ERSPAN support for PFC frames |
|
Status: | Fixed |
|
Severity: | 6 Enhancement |
Description: | Symptom:
Enhancement request to be able to ERSPAN PFC frames rx on a port
Conditions:
Workaround:
Further Problem Description:
|
|
Last Modified: | 06-SEP-2015 |
|
Known Affected Releases: | 6.0(2)U5(1), 6.0(2)U6(1) |
|
Known Fixed Releases: * | 6.0(2)A6(2.26), 6.0(2)A6(3), 6.0(2)U6(1.26), 6.0(2)U6(2), 7.0(3)I2(0.354), 7.0(3)I2(1), 7.0(3)ITI2(1), 7.0(3)ITI2(1.36), 8.3(0)CV(0.72) |
|
|
| |
2013 Cisco and/or its affiliates. All rights reserved. 
没有评论:
发表评论