End-of-Sale and End-of-Life Announcement for the Cisco Nexus 3000 Releases 5.0.(3)Ux(x) and 6.0.(2)U1(x)
Available Languages
EOL10513
Cisco announces the end-of-sale and end-of-life dates for the Cisco Nexus 3000 Releases 5.0.(3)Ux(x) and 6.0.(2)U1(x). The last day to order the affected product(s) is October 30, 2016. Customers with active service contracts will continue to receive support from the Cisco Technical Assistance Center (TAC) as shown in Table 1 of the EoL bulletin. Table 1 describes the end-of-life milestones, definitions, and dates for the affected product(s). Table 2 lists the product part numbers affected by this announcement. For customers with active and paid service and support contracts, support will be available under the terms and conditions of customers' service contract.
Table 1. End-of-Life Milestones and Dates for the Cisco Nexus 3000 Releases 5.0.(3)Ux(x) and 6.0.(2)U1(x)
| Milestone |
Definition |
Date |
| End-of-Life Announcement Date |
The date the document that announces the end-of-sale and end-of-life of a product is distributed to the general public. |
October 31, 2015 |
| End-of-Sale Date |
The last date to order the product through Cisco point-of-sale mechanisms. The product is no longer for sale after this date. |
October 30, 2016 |
| Last Ship Date: |
The last-possible ship date that can be requested of Cisco and/or its contract manufacturers. Actual ship date is dependent on lead time. |
January 29, 2017 |
| End of SW Maintenance Releases Date: |
The last date that Cisco Engineering may release any final software maintenance releases or bug fixes. After this date, Cisco Engineering will no longer develop, repair, maintain, or test the product software. |
October 30, 2017 |
| End of New Service Attachment Date: |
For equipment and software that is not covered by a service-and-support contract, this is the last date to order a new service-and-support contract or add the equipment and/or software to an existing service-and-support contract. |
October 30, 2017 |
| End of Service Contract Renewal Date: |
The last date to extend or renew a service contract for the product. |
January 28, 2021 |
| Last Date of Support: |
The last date to receive applicable service and support for the product as entitled by active service contracts or by warranty terms and conditions. After this date, all support services for the product are unavailable, and the product becomes obsolete. |
October 31, 2021 |
Table 2. Product Part Numbers Affected by This Announcement
| End-of-Sale Product Part Number |
Product Description |
Replacement Product Part Number |
Replacement Product Description |
Additional Information |
| N3KUK9-503U2.2B |
NX-OS Release 5.0(3)U2(2b) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2B |
NX-OS Release 5.0(3)U2(2b) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2B= |
NX-OS Release 5.0(3)U2(2b) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2B= |
NX-OS Release 5.0(3)U2(2b) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2C |
NX-OS Release 5.0(3)U2(2c) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2C |
NX-OS Release 5.0(3)U2(2c) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2C= |
NX-OS Release 5.0(3)U2(2c) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2C= |
NX-OS Release 5.0(3)U2(2c) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2D |
NX-OS Release 5.0(3)U2(2d) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2D |
NX-OS Release 5.0(3)U2(2d) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2D= |
NX-OS Release 5.0(3)U2(2d) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U2.2D= |
NX-OS Release 5.0(3)U2(2d) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.1 |
NX-OS Release 5.0(3)U3(1) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.1 |
NX-OS Release 5.0(3)U3(1) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.1= |
NX-OS Release 5.0(3)U3(1) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.1= |
NX-OS Release 5.0(3)U3(1) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.2 |
NX-OS Release 5.0(3)U3(2) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.2 |
NX-OS Release 5.0(3)U3(2) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.2= |
NX-OS Release 5.0(3)U3(2) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.2= |
NX-OS Release 5.0(3)U3(2) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.2A |
NX-OS Release 5.0(3)U3(2a) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.2A |
NX-OS Release 5.0(3)U3(2a) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.2B |
NX-OS Release 5.0(3)U3(2b) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U3.2B |
NX-OS Release 5.0(3)U3(2b) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U4.1 |
NX-OS Release 5.0(3)U4(1) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U4.1 |
NX-OS Release 5.0(3)U4(1) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U4.1= |
NX-OS Release 5.0(3)U4(1) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U4.1= |
NX-OS Release 5.0(3)U4(1) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1 |
NX-OS Release 5.0(3)U5(1) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1 |
NX-OS Release 5.0(3)U5(1) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1= |
NX-OS Release 5.0(3)U5(1) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1= |
NX-OS Release 5.0(3)U5(1) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1A |
NX-OS Release 5.0(3)U5(1a) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1A |
NX-OS Release 5.0(3)U5(1a) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1A= |
NX-OS Release 5.0(3)U5(1a) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1A= |
NX-OS Release 5.0(3)U5(1a) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1B |
NX-OS Release 5.0(3)U5(1b) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1B |
NX-OS Release 5.0(3)U5(1b) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1B= |
NX-OS Release 5.0(3)U5(1b) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1B= |
NX-OS Release 5.0(3)U5(1b) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1C |
NX-OS Release 5.0(3)U5(1c) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1C |
NX-OS Release 5.0(3)U5(1c) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1C= |
NX-OS Release 5.0(3)U5(1c) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1C= |
NX-OS Release 5.0(3)U5(1c) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1D |
NX-OS Release 5.0(3)U5(1d) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1D |
NX-OS Release 5.0(3)U5(1d) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1D= |
NX-OS Release 5.0(3)U5(1d) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1D= |
NX-OS Release 5.0(3)U5(1d) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1E |
NX-OS Release 5.0(3)U5(1e) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1E |
NX-OS Release 5.0(3)U5(1e) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1E= |
NX-OS Release 5.0(3)U5(1e) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1E= |
NX-OS Release 5.0(3)U5(1e) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1F |
NX-OS Release 5.0(3)U5(1f) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1F |
NX-OS Release 5.0(3)U5(1f) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1F= |
NX-OS Release 5.0(3)U5(1f) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1F= |
NX-OS Release 5.0(3)U5(1f) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1G |
NX-OS Release 5.0(3)U5(1g) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1G |
NX-OS Release 5.0(3)U5(1g) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1G= |
NX-OS Release 5.0(3)U5(1g) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1G= |
NX-OS Release 5.0(3)U5(1g) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1H |
NX-OS Release 5.0(3)U5(1h) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1H |
NX-OS Release 5.0(3)U5(1h) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1I |
NX-OS Release 5.0(3)U5(1i) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1I |
NX-OS Release 5.0(3)U5(1i) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1I= |
NX-OS Release 5.0(3)U5(1i) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1I= |
NX-OS Release 5.0(3)U5(1i) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1J |
NX-OS Release 5.0(3)U5(1j) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1J |
NX-OS Release 5.0(3)U5(1j) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1J= |
NX-OS Release 5.0(3)U5(1j) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-503U5.1J= |
NX-OS Release 5.0(3)U5(1j) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.1 |
NX-OS Release 6.0(2)U1(1) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.1 |
NX-OS Release 6.0(2)U1(1) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.1= |
NX-OS Release 6.0(2)U1(1) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.1= |
NX-OS Release 6.0(2)U1(1) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.1A |
NX-OS Release 6.0(2)U1(1a) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.1A |
NX-OS Release 6.0(2)U1(1a) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.1A= |
NX-OS Release 6.0(2)U1(1a) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.1A= |
NX-OS Release 6.0(2)U1(1a) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.2 |
NX-OS Release 6.0(2)U1(2) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.2 |
NX-OS Release 6.0(2)U1(2) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.2= |
NX-OS Release 6.0(2)U1(2) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.2= |
NX-OS Release 6.0(2)U1(2) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.3 |
NX-OS Release 6.0(2)U1(3) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.3 |
NX-OS Release 6.0(2)U1(3) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.3= |
NX-OS Release 6.0(2)U1(3) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.3= |
NX-OS Release 6.0(2)U1(3) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.4 |
NX-OS Release 6.0(2)U1(4) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.4 |
NX-OS Release 6.0(2)U1(4) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.4= |
NX-OS Release 6.0(2)U1(4) |
N3KUK9-602U3.8 |
NX-OS Release 6.0(2)U3(8) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
| N3KUK9-602U1.4= |
NX-OS Release 6.0(2)U1(4) |
N3KUK9-602U5.2 |
NX-OS Release 6.0(2)U5(2) |
N3000 customers upgrade to 6.0(2)U3(8). N3100 customers upgrade to 6.0(2)U5(2) |
Product Migration Options
Cisco Nexus 3000 customers are encouraged to migrate to the Cisco Nexus 6.0(2)U3(8) release. Cisco Nexus 3100 customers are encouraged to migrate to Release 6.0(2)U5(2). Information about these products can be found at: http://www.cisco.com/c/en/us/support/switches/nexus-3000-series-switches/products-release-notes-list.html.
Customers may be able to use the Cisco Technology Migration Program (TMP) where applicable to trade-in eligible products and receive credit toward the purchase of new Cisco equipment. For more information about Cisco TMP, customers should work with their Cisco Partner or Cisco account team. Cisco Partners can find additional TMP information on Partner Central at http://www.cisco.com/web/partners/incentives_and_promotions/tmp.html.
Customers may be able to continue to purchase the Cisco Nexus 3000 Releases 5.0.(3)Ux(x) and 6.0.(2)U1(x) through the Cisco Certified Refurbished Equipment program. Refurbished units may be available in limited supply for sale in certain countries on a first-come, first-served basis until the Last Date of Support has been reached. For information about the Cisco Certified Refurbished Equipment program, go to: http://www.cisco.com/go/eos.
Service prices for Cisco products are subject to change after the product End-of-Sale date.
The Cisco Takeback and Recycle program helps businesses dispose properly of surplus products that have reached their end of useful life. The program is open to all business users of Cisco equipment and its associated brands and subsidiaries. For more information, go to: http://www.cisco.com/web/about/ac227/ac228/ac231/about_cisco_takeback_recycling.html.
For More Information
For more Information about the Cisco Nexus 3000 Release 6.0(2)U3(8) or 6.0(2)U5(2) , visit http://www.cisco.com/c/en/us/support/switches/nexus-3000-series-switches/products-release-notes-list.html, or contact your local account representative.
To request information about the Cisco Nexus 3000 Release 6.0(2)U3(8) or 6.0(2)U5(2), send an e-mail to ask-nexus3000-pm@cisco.com.
For more information about the Cisco End-of-Life Policy, go to: http://www.cisco.com/en/US/products/products_end-of-life_policy.html.
For more information about the Cisco Product Warranties, go to: http://www.cisco.com/en/US/products/prod_warranties_listing.html.
To subscribe to receive end-of-life/end-of-sale information, go to: http://www.cisco.com/cisco/support/notifications.html.
Subscribe for RSS Notifications for End-of-Life and End-of-Sale Notices
To subscribe to the End-of-Life and End-of-Sale RSS Feed, insert the following URL into your RSS application: http://www.cisco.com/web/feeds/products/end_of_life_rss.xml.
Any authorized translation issued by Cisco Systems or affiliates of this end-of-life Product Bulletin is intended to help customers understand the content described in the English version. This translation is the result of a commercially reasonable effort; however, if there are discrepancies between the English version and the translated document, please refer to the English version, which is considered authoritative.
Feedback