The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
◦
Introduction
This document provides information about the currently supported network applications for the Nexus® 3550-T Programmable Network Platform. The product plan is to create and release new 3550 Series platform applications. The new network application releases will be communicated in the quarterly Cisco New Product Introduction (NPI) as they are released.
Note: The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product.
Date |
Description |
July 13, 2023 |
Release 10.2(3v) became available. |
The list of new features for the Cisco Nexus 3550-T switch, Release 10.2(3v) is here.
Product Impact |
Feature |
Description |
Base Functionality |
Dynamic NAT |
Dynamic Network Address Translation (NAT) translates a group of real IP addresses into mapped IP addresses that are routable on a destination network. For details, see the Configuring Static and Dynamic NAT Translation chapter in the Cisco Nexus 3550-T NX-OS Interfaces Configuration Guide, Release 10.2(x). |
Support for 1G |
All 48 ports of the 3550-T chassis support speeds of 1G and 10G. For the supported optics, see the TMG Matrix. For details, see the Cisco Nexus 3550-T Hardware Installation Guide. |
|
Multicast Support Enhancements |
Cisco Nexus 3550-T trunk ports support single configured PIM-enabled VLAN with Layer 3 egress multicast capability. For details, see the Multicast Configuration Overview chapter in the Cisco Nexus 3550-T NX-OS Multicast Configuration Guide, Release 10.2(x). |
|
Support for UTC Offset Correction in HPT |
High Precision Timestamping (HPT) now supports Coordinated Universal Time (UTC) offset correction. For details, see the Configuring High Precision Timestamping chapter in the Cisco Nexus 3550-T NX-OS System Management Configuration Guide, Release 10.2(x). |
|
Performance and Scalability |
Scale Enhancements |
Scale enhancements for this release are: · Increased Unicast / Multicast Scalability · Increased Port Channel Scalability For details, see the Cisco Nexus 3550-T NX-OS Verified Scalability Guide, Release 10.2(3v). |
New Hardware Features
No new hardware was introduced for release 10.2(3v).
Open Issues
Click the bug ID to access the Bug Search tool and see additional information about the bug.
Bug ID |
Description |
Headline: Router-on-stick configuration L3 Unicast getting dropped. Symptoms: L3 Unicast traffic may get dropped in a corner-case scenario. Conditions: Traffic Ingresses and is expected to Egress out of the same L2 trunk Port-Channel interface after getting routed between SVIs. Workaround: None |
|
Headline: N35-T-48X to N9K-C93180YC-FX Connections: Observing extra reset with reload on multiple links. Symptom: An extra interface reset is reported on a few interfaces on N35-T-48X post reload. Conditions:
● At least one interface on N35-T-48X is connected to a N9K-C93180YC-FX.
● N35-T-48X is reloaded.
● An extra reset may be seen on the interface(s) connected to N9K-C93180YC-FX.
Workaround: None |
|
Headline: TypeError: unsupported operand type while collecting show tech detail. Symptom: A python script error may be seen on executing 'show tech-support detail'. The command continues to collect all the required logs from the system. Conditions: 'show tech-support details' command is executed. Workaround: None. |
Resolved Issues
Click the bug ID to access the Bug Search tool and see additional information about the bug.
Bug ID |
Description |
Headline: Exablaze: L3 Routing across the ULL network in the Colo is unstable due to Mac out-of-sync issue. Symptom: Host to gateway (SVI IP) ping stops working after certain triggers Conditions:
● Presence of a STP blocked port.
● Triggers - Switch reload, STP root port failover.
Workaround: Issue the 'clear mac address-table dynamic' command |
|
Headline: N3550-T static NAT does not translate TCP flow. Symptom: TCP flow times out. Conditions: TCP flows is going via N3550-T doing static NAT. Workaround: N/A |
|
Headline: Dynamic Nat Entries replicated when shutting L3backup Links in same quad leading to table exhaustion. Symptom: Primary link flap (shut/no shut) with NAT or ACL can cause NAT/ACL HW table exhaustion. Conditions:
● Multiple backup l3 links configured with ACL or NAT and the rules are in the order of hundreds.
● L3 Back up Links are configured on the same quad.
Workaround:
● Flap the L3 interfaces on which the ACL/NAT is configured.
(or)
● Unconfigure and configure ACL/NAT back on the L3 interface.
|
Known Issues
Click the bug ID to access the Bug Search tool and see additional information about the bug.
Bug ID |
Description |
Headline: SFP 1gig mgmt interface didnt come up. Symptom: Link does not come up when connected to the 1GbE SFP management port. Management connectivity is not established. Conditions: Any supported transceiver connected to the 1GbE SFP management port. Workaround: None. Use RJ45 port for management connectivity on N3550-T. |
|
Headline: Unknown Multicast packets are not flooded to ports on same vlan. Symptom: Multicast packets received when "no ip igmp snooping" is configured are not flooded in the VLAN. Conditions: "no ip igmp snooping” configured on VLAN. Workaround: None |
|
|
Headline: When attempting to reach max. scale, some entries (100) missing in Hardware for L3 Unicast. Symptom: Layer 3 Unicast Traffic drop observed after device reload and route entries for those flows are missing in hardware. Conditions: The issue is specific to hardware scale boundary scenarios and will be observed only if the IP table utilization in hardware is above 90%. Workaround: None |
Headline: Exablaze to n9k cloudscale (N9K-C93180YC-FX, N9K-C93180YC-EX TOR) switch 1gig link is not coming up. Symptom: Link not coming up when Nexus 3550-T switch is connected to a Nexus 9000 switch with 1G optics and interoperability scenario does not work. Conditions: The issue is seen only with the following pre-conditions:
● Nexus 3550-T device connected to Nexus 9000 (or other 3rd-party device)
● The connection between those devices is thru 1G optics
Workaround: The workaround is to disable auto-neg (no negotiation auto) and configure speed manually on Nexus 9000 switch connected to Nexus 3550-T device to get the 1G connection between those UP & running. |
Optics
To determine which transceivers and cables are supported by a switch, see the Transceiver Module (TMG) Compatibility Matrix. To see the transceiver specifications and installation information, see the Install and Upgrade Guides.
Cisco Network Insights for Data Center
Cisco NX-OS Release 10.2(3v) supports the Cisco Network Insights on Cisco Nexus 3550-T platform switches. For more information, see the Cisco Network Insights documentation.
Upgrade and Downgrade
To perform a software upgrade to release 10.2(3v), follow the instructions in the Cisco Nexus 3550-T Software Upgrade and Installation Guide, Release 10.2(3v).
Documentation Feedback
To provide technical feedback on this document, or to report an error or omission, send your comments to nexus3k-docfeedback@cisco.com. We appreciate your feedback.
Legal Information
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2023 Cisco Systems, Inc. All rights reserved.