Техническая
Current location:Home > Новости > Техническая

Related news

Contact us

  • Business Phone :0086-13538247228
  • Worktime :9:00-18:00(Beijing time)
  • Address :
  • How to upgrade N3K software version Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.x

    By 14,01,2022

    Information About Software Images

    Cisco Nexus 3000 Series switches are shipped with the Cisco NX-OS software preinstalled on the switches. Before upgrading or downgrading from an existing image, you should read through the information in this document to understand the guidelines, prerequisites, and procedures for upgrading the software. For updated information about the Cisco NX-OS software for the Cisco Nexus 3000 Series switch, see the Cisco Nexus 3000 Series Release Notes.

    The Cisco NX-OS software consists of one NXOS software image. The image filename begins with "nxos" [beginning with Cisco NX-OS Release 7.0(3)I2(1) and later releases]. Only this image is required to load the Cisco NX-OS operating system. This image runs on all the Cisco Nexus 3000 and Nexus 3100 Series switches. Using fast-reload after the BIOS upgrade or using install all commands are the only supported methods of upgrading to Release 7.0(3)I2(1) and later releases.

    Note

    Starting with Release 7.0(3)I2(1) and later releases, there is a single image for booting the Cisco Nexus 3000 Series platforms. The kickstart and system images are not required anymore. The single image binary now boots up on both Cisco Nexus 3000 and 3100 Series platforms and Cisco Nexus 9000 Series platforms. Due to single image binary, the following commands are updated: -

    • boot nxos single_image_binary

    • fast-reload nxos single_image_binary

    • install all nxos single_image_binary


    Caution

    The fast-reload to Release 7.0(3)I2(1) is supported only from Release 6.0(2)U6(3a) or later releases, after the BIOS has been upgraded. Using fast-reload from Release 6.0(2)U6(3a) to Release 7.0(3)I2(1) without upgrading the BIOS will result in the switch not booting up.


    Caution

    If the switch was ordered new with 7.0(3)I2.x code or has had init system performed while running 7.0(3)I2.x code, an install all downgrade to 6.0(2)U6.x code will result in the device being stuck in the loader prompt with no access to the files on bootflash.


    Supported Hardware

    Cisco Nexus 3000 and 3100 Series switches are shipped with the Cisco NX-OS software preinstalled. Cisco NX-OS upgrades and downgrades are supported on the hardware listed in the following sections:

    Cisco Nexus 3000 Series Switches

    • Cisco Nexus 3016 switches

    • Cisco Nexus 3048 switches

    • Cisco Nexus 3064 switches

    Cisco Nexus 3100 Series Switches

    • Cisco Nexus 3132Q and 3132Q-XL switches

    • Cisco Nexus 3172 switches

    Note

    For software upgrade and downgrade information for Cisco Nexus 3000 Series switches that operate in N9K mode, see the Cisco Nexus 9000 Series NX-OS Software Upgrade and Downgrade Guide.


    About ISSU

    Beginning with Cisco NX-OS Release 7.0(3)I3(1), you can perform an in-service software upgrade (ISSU), also known as a non-disruptive upgrade. An ISSU allows you to upgrade the device software while the switch continues to forward traffic. An ISSU reduces or eliminates the downtime typically caused by software upgrades.

    ISSU Prerequisites

    Follow the guidelines in the "Guidelines and Limitations for ISSU" section to ensure that the ISSU works smoothly.

    Make sure that the network is stable and no changes are made while the ISSU is in progress.

    Ensure feature compatibility between the current running release and the target release.

    Make sure that interfaces are not in a spanning-tree designated forwarding state. Also, make sure that bridge assurance is not configured on any interface. The vPC peer-link is an exception to these requirements.

    Verify that the current STP topology is consistent with the ISSU requirements. Use the show spanning-tree issu-impact command to display the STP configuration and whether or not there are potential STP issues.

    Use the show lacp issu-impact command to display if a port or a peer switch is configured in the rate fast mode. The ISSU process is aborted if the system has any LACP fast timers configured.

    Guidelines and Limitations for ISSU

    The following is a list of important guidelines and limitations for ISSU:

    • An ISSU can be performed only from a Cisco NX-OS 7.0(3)I3(1) or a later image to a later image.

    • Beginning with Cisco NX-OS Release 7.0(3)I4(1), you can perform an ISSU for VXLAN.

    • ISSUs for segment routing are supported on Cisco Nexus 3000 series switches from Cisco NX-OS Release 7.0(3)I4(1) onwards.

    • ISSUs are supported on the following platforms:

      • Cisco Nexus 3172PQ, 3172TQ, 3172PQ-XL, and 3172TQ-XL switches

      • Cisco Nexus 3132Q, 3132Q-X, and 3132Q-XL switches

      • Cisco Nexus 3064, 3064-X, and 3064-T switches

      • Cisco Nexus 3048 switches

      • Cisco Nexus 3016 switches

    • Beginning with Cisco NX-OS Release 7.0(3)I5(1), Cisco Nexus 3000 series platforms with 16 GB of memory or higher support enhanced ISSU. The upgrade will be disruptive.

    • Beginning with Cisco NX-OS Release 7.0(3)I7(3), the minimum free bootflash space that is required to perform an ISSU is as follows:

      • For compact image: 200 MB

      • For non-compact image: 300 MB

    • For Cisco NX-OS Release 7.0(3)I7(1) and Cisco NX-OS Release 7.0(3)I7(2), the minimum free bootflash space that is required to perform ISSU is 550 MB.

    • Cisco Nexus 3048, 3064, 3132, and 3172 switches with a model number that does not end in -XL must run a compact NX-OS software image due to limited bootflash space. This compact image can be created using the NX-OS Compact Image procedure; alternatively, a compact NX-OS software image can be downloaded directly from Cisco's Software Download website. This requirement does not apply to any other model of Nexus 3000 or 3100 series switch.

      • The MD5/SHA512 checksum published on Cisco's Software Download website for a compact NX-OS software image may not match the MD5/SHA512 checksum of a compact image created through the NX-OS Compact Image procedure.

    Configuring Enhanced ISSU

    Beginning with Cisco NX-OS Release 7.0(3)I5(1), you can enable or disable enhanced (LXC) ISSU.

    Note

    After you upgrade to Cisco NX-OS Release 7.0(3)I5(1) from an earlier release, you can enable enhanced ISSU for use with future upgrades.


    Procedure

      Command or Action Purpose
    Step 1

    configure terminal

    Example:

    switch# configure terminal switch(config#)

    Enters global configuration mode.

    Step 2

    [noboot mode lxc

    Example:

    switch(config)# boot mode lxc Using LXC boot mode

    Example:

    switch(config)# no boot mode lxc Using normal native boot mode

    Enables or disables enhanced (LXC) ISSU.

    Step 3

    (Optional) show boot mode

    Example:

    switch(config)# show boot mode LXC boot mode is enabled

    Example:

    switch(config)# show boot mode LXC boot mode is disabled
    (Optional)

    Shows whether enhanced (LXC) ISSU is enabled or disabled.

    Step 4

    copy running-config startup-config

    Example:

    switch(config)# copy running-config startup-config

    Saves the running configuration to the startup configuration.

    Step 5

    reload

    Example:

    switch(config)# reload This command will reboot the system. (y/n)?  [n] Y
    loader>

    Последняя статья :How to upgrade N3K software version Cisco Nexus 3000 Series NX-OS Software Upgrade and Downgrade Guide, Release 7.x

    Следующая статья :About MikroTik

    Обратный список