30 Oct. 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

N5860 and N8560 and NC8200 Series Switches CLI Reference Guide

28 Oct. 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

07 Jul. 2025 - Product overview N5860-48SC is ideal for all sizes data centers and cloud computer services. It is a ToR high density switch in a compact 1U form factor with full line rate 48 1/10GbE and 8 40/100GbE ports, combining advantages of zero packet loss, low latency, and non-blocking performance for lossless Ethernet. The layer 3 switch incorporates rich features incorporated, including industry-leading Broadcom chip, redundant hot-swappable AC and DC power supplies and fans, VXLAN, MLAG, PFC, ECN, RDMA, etc. for scalable and flexible data center leaf-spine designs. Product highlights Support Ansible, OpenFlow, NETCONF, etc. Configuration and Automation Tools Flexible 1/10/25/40/100GbE Interface Speeds, Support Stacking Support MLAG, BGP4/BGP4+, EVPN-VXLAN, REUP, GR, BFD Low-latency, Zero Packet Loss with PFC, ECN, RDMA over Converged Ethernet (RoCE) 1+1 Hot-Swappable AC or DC Power Supplies, 3+1 smart fans with Front-to-Back Airflow or Back-to-Front Airflow Support SPAN/RSPAN/ERSPAN and In-band Network Telemetry (INT) for Visibility Support ACL, RADIUS, TACACS+, DHCP Snooping, etc. for Security Support SNMP v1/v2c/v3, CLI, Telnet, SSH Platform details Platform benefits Software requirements Product specifications Quality certification At FS, our Quality Commitment lies in all aspects of processes, resources, and methods that enable us to build superior networks for our customers. Through a quality policy focusing on continuous improvement of products and services, we're able to achieve the highest levels of satisfaction for our customers. To that end, every FS employee is accountable for contributing to the value of the products and services we deliver. Figures 4 shows some of the authoritative certifications obtained by FS N5860-48SC Switch. Optics supported For details about the optical modules available, visit： N5860-48SC: TRANSCEIVERS DACS AND AOCS SUPPORTED ON N5860-48SC SWITCH Warranty, service and support FS N5860-48SC Switch enjoy 5 years limited warranty against defects in materials or workmanship. For moreinformation for FS Returns & Refunds policy, visit https://www.fs.com/policies/warranty.html or https://www.fs.com/policies/day_return_policy.html FS provides a personal account manager, free professional technical support, and 24/7 live customer serviceto each customer.support.html • Professional Lab: Test each product with the latest and advanced networking equipment. • Free Technical Support: Provide free & tailored solutions and services for your businesses. • 80% Same-day Shipping: Immediate shipping for in-stock items. • Fast Response: Direct and immediate assistance from an expert For more information, visit https://www.fs.com/service/fs_support.html Ordering information Additional information For more information about the N5860-48SC Switch, contact your account manager or visit https://www.fs.com/search_result?keyword=N5860 Document history

30 May. 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

FSOS 12.5(1)B0508S10 Software Image for N5860-48SC and N8560-48BC and N8560-64C and NC8200-4TD Switches

14 Abr. 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

FSOS 12.5(1)B0508S10 Release Notes for N5860-48SC and N8560-48BC and N8560-64C and NC8200-4TD Switches

14 Abr. 2025 - FSOS 12.5(1)B0508S10 Release Notes for N5860-48SC and N8560-48BC and N8560-64C and NC8200-4TD Switches Version Information Version Number N8560_FSOS 12.5(1)B0508S10 Products N5860-48SC、N8560-48BC、N8560-64C、NC8200-4TD Version Type Official Version Applicable Customers Data Center Customers Release Date 2025-01-22 Baseline Version N8560_FSOS 12.5(1)B0508 Use the show version command to view the version number, an example is as follows: FS#show version detail System description : FS Data Center Switch(N5860-48SC) By FS.COM Inc System start time : 2025-01-07 06:01:00 System uptime : 0:01:28:17 System hardware version : 2.00 System software version : N5860_FSOS 12.5(1)B0508S10 System patch number : NA System software number : M21382301012025 System serial number : 1234943260073 System boot version : 1.3.44(Master) 1.3.44(Slave) System rboot version : 1.2.13 System core version : 5.4.241-Cavium-Octeon+ System cpu partition : 3 Module information: Slot 0 : N5860-48SC System uptime : 0:01:28:17 Hardware version : 2.00 Boot version : 1.3.44(Master) 1.3.44(Slave) Rboot version : 1.2.13 Software version : N5860_FSOS 12.5(1)B0508S10 Software number : M21382301012025 Serial number : 1234943260073 FS#show version detail System description : FS Data Center Switch(N8560-64C) By FS.COM Inc System start time : 2025-01-07 14:52:59 System uptime : 0:00:36:32 System hardware version : 1.00 System software version : N8560_FSOS 12.5(1)B0508S10 System patch number : NA System software number : M21382301012025 System serial number : G1MS20N00006B System boot version : 1.3.36(Master) 1.3.36(Slave) System rboot version : 1.2.15 System core version : 5.4.241-Cavium-Octeon+ System cpu partition : 3 Module information: Slot 0 : N8560-64C System uptime : 0:00:36:32 Hardware version : 1.00 Boot version : 1.3.36(Master) 1.3.36(Slave) Rboot version : 1.2.15 Software version : N8560_FSOS 12.5(1)B0508S10 Software number : M21382301012025 Serial number : G1MS20N00006B FS#show version detail System description : FS Data Center Switch(NC8200-4TD) By FS.COM Inc System start time : 2025-01-07 15:11:14 System uptime : 0:00:18:57 System hardware version : 1.00 System software version : NC8200_FSOS 12.5(1)B0508S10 System patch number : NA System software number : M21382301012025 System serial number : G1M80B7000321 System boot version : 1.3.45(Master) 1.3.45(Slave) System rboot version : 1.2.15 System core version : 5.4.241-Cavium-Octeon+ System cpu partition : 3 Module information: Slot 0 : NC8200-4TD System uptime : 0:00:18:57 Cpu 0: Hardware version : 1.00 Boot version : 1.3.45(Master) 1.3.45(Slave) Rboot version : 1.2.15 Software version : NC8200_FSOS 12.5(1)B0508S10 Software number : M21382301012025 Serial number : G1M80B7000321 Release History Release Date Version Type 2023-08-11 N8560_FSOS 12.5(1)B0505 Initial Official Release 2023-08-11 N8560_FSOS 12.5(1)B0506 Official Release 2024-05-13 N8560_FSOS 12.5(1)B0508 Official Release New Features Feature Module Requirement Source (Optional) Feature Description First Supported Version BFD NA Supports BFD over MLAG functionality N8560_FSOS 12.5(1)B0508 FRR NA Supports ISIS ECMP FRR functionality N8560_FSOS 12.5(1)B0508 Local QoS value marking functionality NA Marks local QoS values at the ingress using MQC, allowing modifications such as DSCP marking, rate limiting, filtering, and statistics at the egress based on ingress information. N8560_FSOS 12.5(1)B0506 ACL NA Adds support for matching ACL and printing packet features to CLI at ingress/egress. N8560_FSOS 12.5(1)B0506 Fault Isolation NA The FSUI component monitors the file system for read-only status and will reset the device for self-healing. N8560_FSOS 12.5(1)B0506 Storm suppression NA Supports storm control violation actions for multicast and broadcast PPS (packets per second) on violation ports. N8560_FSOS 12.5(1)B0506 PBR v6 NA Supports policy-based routing to specify the next hop across VRFs. N8560_FSOS 12.5(1)B0506 Sloved Problems 12.5(1)B0508S10 Issue ID Problem Description Fixed Version 1154843 Resolve the issue where bulk creation of full-capacity ECMP groups (the current available ECMP group resource size can be viewed using show route-res usage all) and continuous shutdown/no shutdown of ECMP member ports lead to continuous ECMP group resource allocation, which may result in high SDA memory usage. N8560_FSOS 12.5(1)B0508S10 1290111 Resolve the issue where shutting down the MLAG downstream port and hitting the VXLAN MAC exit causes unicast traffic of the shutdown VAP to fail forwarding. N8560_FSOS 12.5(1)B0508S10 1290112 Resolve the issue where changes in the ECMP routing exit or enabling/disabling elastic hashing causes ECMP route disruption. N8560_FSOS 12.5(1)B0508S10 1290116 Resolve the issue where upgrading business process function patches may occasionally fail to uninstall the patch, resulting in the error message "Remove package error!" due to the temporary creation of a thread that exits. N8560_FSOS 12.5(1)B0508S10 1197591 Resolve the issue where authentication fails when using the ED25519 public key algorithm for SSH. N8560_FSOS 12.5(1)B0508S10 12.5(1)B0508 Issue ID Problem Description Fixed Version 1154843 Resolve the issue where NETCONF fails to transcode when the device contains illegal characters. In this case, NETCONF skips transcoding and sends the data directly to the controller, which causes a disconnection and reconnection. N8560_FSOS 12.5(1)B0508 1109939 Supports enabling and disabling the gRPC server functionality through configuration commands. N8560_FSOS 12.5(1)B0508 1126197 Resolve the occasional BFD protocol flapping issue in VXLAN scenarios when there is a high volume of VXLAN broadcast traffic. N8560_FSOS 12.5(1)B0508 12.5(1)B0506 Issue ID Problem Description Fixed Version 1040164 Unable to view PS information - TIPC link down, and syslog does not print any logs. N8560_FSOS 12.5(1)B0506 1039712 The order of the clock timezone configuration in the show running-config is inconsistent after upgrading from 11X to 12X. N8560_FSOS 12.5(1)B0506 1018363 The DHCPv6 client obtains an IPv6 address with a 64-bit prefix from the server. If the gateway prefix is not 64 bits, the device generates a default route. This can cause communication issues across different subnets. N8560_FSOS 12.5(1)B0506 1017825 At the customer's site, the integration of Arista multi-level MLAG and VSTP does not support configuring the revision. Otherwise, it may cause the two devices to send BPDU packets with different cost values. N8560_FSOS 12.5(1)B0506 1036352 Under PBR traffic, the statistics from show ip pbr statistics / show ipv6 pbr statistics command return 0. N8560_FSOS 12.5(1)B0506 Known Issues Bug ID Issue Description Workaround First Detected Version 1050908 In the ZAM zero-configuration startup scenario, if the customer's script contains issues (unable to correctly configure "no ip address"), the lease on the DHCP server may remain after a reboot. The issue can be resolved by correctly revising the script. N8560_FSOS 12.5(1)B0508 1108966 On devices with the patch already installed, performing the ZAM process will not allow the installation of a new patch without first uninstalling the old patch. The ZAM process should be performed after uninstalling the patch. N8560_FSOS 12.5(1)B0508 1103759 When using Checkpoint to back up and rollback configurations, if several of the 6 configured IPFIX entries are deleted and then restored, the order of the restored configuration may differ from the original. There is no workaround, and only the order is different. N8560_FSOS 12.5(1)B0508 1037893 When integrating with a partner's IPSec algorithm, some algorithms may fail to establish encryption and decryption interoperability. The command/configuration manual has listed the IPSec encryption algorithms that are supported for integration with the partner. N8560_FSOS 12.5(1)B0508 1051233 In a high-capacity BGP environment, when the BGP message rate exceeds the default CPP threshold (3000 pps), CPP packet loss occurs, leading to BGP instability. In a high-capacity BGP scenario, increasing the BGP CPP threshold can help avoid this issue. It is recommended to set it to the maximum value. N8560_FSOS 12.5(1)B0508 1096015 In an MLAG+VSTP scenario, restarting the MSTP process may cause temporary packet loss. - N8560_FSOS 12.5(1)B0508 1042361 When using Checkpoint to back up configurations and perform a rollback to restore a Layer 2 port to a Layer 3 port, the configuration may fail to restore. The configuration that was not restored will prompt the user, requiring manual restoration. N8560_FSOS 12.5(1)B0508 1090243 During the one-click VSU upgrade process using the upgrade auto command, if the standby unit is rebooting and the syslog shows "VSU-5-DTM_AUTO_UPGRADE: Upgrading the system, wait a moment please," manually executing a new upgrade command will cause the one-click upgrade to fail. When the upgrade auto command is used to perform a one-click VSU upgrade, and the standby unit is still in the reboot process, with the VSU upgrade not yet complete and log messages indicating the upgrade is still in progress, do not execute a new upgrade command. N8560_FSOS 12.5(1)B0508 1138568 When the FP resources are at full capacity, enabling the VXLAN-QoS feature while exceeding the FP capacity limit will generate a syslog message. The configuration will not roll back. After exceeding the capacity limit, a syslog message will be printed, indicating the need to delete some FP rules. The configuration will not roll back automatically. N8560_FSOS 12.5(1)B0508 1108385 In a full capacity scenario, the idle FP reserved slice resources cannot be used by the ACL. When the TCAM resources are full, delete other unused configurations to release resources. N8560_FSOS 12.5(1)B0508 1048968 When using TFTP to transfer and specify the USB path, if the USB drive is removed, the configuration will not roll back. Continuing the transfer at this point will fail. When using TFTP with the USB path, if the USB drive is removed, you will need to re-specify the TFTP path. N8560_FSOS 12.5(1)B0508 1162266 When two devices are grouped in MLAG with a non-direct VAP, executing vap shut/no shut and pl shut/no shut will cause a brief burst of multiple packets on the devices. It is not recommended to configure a non-direct VAP. N8560_FSOS 12.5(1)B0508 1135051 In 11.x, the default load balancing mode is src-dst-mac, while in 12.x, it is the enhanced load balancing mode. If the enhanced load balancing is configured in 11.x and the system is upgraded to 12.x, the show running-config command will not display the enhanced load balancing configuration (as the default configuration will not be shown). - N8560_FSOS 12.5(1)B0508 1077447 The GTSM feature is not supported for Link-local neighbors, although the command is still present. In this version, the configuration for GTSM will be disabled. If there was a previous configuration for GTSM on Link-local neighbors, it will be lost after the upgrade, but the functionality will not be affected. - N8560_FSOS 12.5(1)B0508 1039201 [11.X to 12.X Upgrade/Downgrade] In the 11.X upgrade, the configuration order for MTU forwarding 9000 has changed. The implementation in 12.x is more reasonable. N8560_FSOS 12.5(1)B0506 1039202 [11.X to 12.X Upgrade/Downgrade] In the 11.X upgrade, the configuration order related to AAA has changed. In 11.x, the RADIUS server group is attached to the PARSE_ADD_CFG_TOP_CMD node in the CLI, and the global server configuration is attached to the PARSE_ADD_CFG_CMD node. Commands under the TOP node are applied first, so during configuration loading, the server group configuration is applied before the global server configuration. In practice, the configuration under the server group depends on the global server configuration. If the server group is configured before the global server, a log will prompt that the global server must be configured. This causes a warning log during boot-time configuration loading. Once the global server is configured, the functionality works as expected. In the initial version of 12.x, the server group is attached to the PARSE_ADD_CFG_CMD node, and the global server configuration is attached to the PARSE_ADD_CFG_TOP_CMD node. This resolves the boot-time warning log issue. There is no functional difference, and the implementation in 12.x is more reasonable. N8560_FSOS 12.5(1)B0506 1036119 [11.X to 12.X Upgrade/Downgrade] After upgrading from 11.X, the default Layer 3 MTU under an interface equals the link-layer MTU. When the link-layer MTU is modified, the default Layer 3 MTU changes accordingly. When mtu 4000, ip mtu 4000, and ipv6 mtu 4000 are configured simultaneously under an interface, the show running-config output differs between 11.X and 12.X. - N8560_FSOS 12.5(1)B0506 981320 The device does not support link-local addresses other than FE80:0:0:0. - N8560_FSOS 12.5(1)B0506 Unsupported Line Cards The NC8200-4TD does not support the NC8200-16 module. 964728 After three consecutive login failures, the account will be automatically locked, and the IP will be prevented from logging in again for 10 minutes. Do not exceed three consecutive failures, or wait 10 minutes after a failure. N8560_FSOS 12.5(1)B0505 920024 Changes in default behavior for management protocols: Telnet is disabled by default. SNMP is disabled by default; when enabled, SNMPv3 is supported by default (SNMPv1 and SNMPv2 are not supported by default and need to be manually enabled). Password strings are encrypted by default. Strong password check is enabled by default. - N8560_FSOS 12.5(1)B0505 Default Behavior Change Changes in default behavior after upgrading from 11.X to 12.X: QOS configuration: qos-queue compatible enable //12.X's default value depends on whether the capability is 0 to 7 or 1 to 8. AAA configuration: aaa slave-login allow //12.X's backup login functionality has changed. The console port on the backup device now logs into the primary device. This command is now obsolete. Disable visualization: no visual path detection enable //12.X does not support PFV. Key encryption: service password-encryption // Security policy: This configuration will be displayed whether it is explicitly set or not. Disable telnet login service: no enable service telnet-server // Telnet is disabled by default, as per network device security policies. - N8560_FSOS 12.5(1)B0505 916174 The CPP command output order in 11.X follows the configuration order, while in 12.X, it follows dictionary order, resulting in inconsistent sorting. External Interface Change Notice: The current CPP configuration display in 12.X is an optimization over 11.X, and no workaround is needed. N8560_FSOS 12.5(1)B0505 837022 By default, the dh_group_exchange_sha1 key exchange algorithm is not supported. The algorithm can be supported by configuring it with the ip ssh-server key-exchange dh_group_exchange_sha1 command. However, this algorithm does not comply with national standards and is not recommended for use. N8560_FSOS 12.5(1)B0505 916400 In 12.X, the libproxy-cli module commands from 11.X have been split into different modules. As a result, it is not possible to guarantee the same command order across modules as in 11.X. External Interface Change Notice, involving command scope: EFMP: config ecmp cluster enable LSM: 1）config mtu forwarding <64-9216> 2）interface posit-lamp enable TCPIP: config arp-passby optimization enable dcn_app_intf: interface transceiver xxx ptm_cli: 1）interface mac-loopback 2）interface mac-loopback remove-itag N8560_FSOS 12.5(1)B0505 909474 The value range for BGP commands has been changed to align with BFD. If a user upgrades from 11.X to 12.X, it may result in configuration loss. External Interface Change Notice. N8560_FSOS 12.5(1)B0505 847744 When the device is configured with TCAM mode, downgrading from 12.X to 11.X requires the device to restart once for the TCAM mode to take effect. An additional restart will make it effective. N8560_FSOS 12.5(1)B0505 845454 After the SDK upgrade, FP does not support matching the packet fragment ID. External Interface Change Notice: [Product Difference] Due to the limitation of SDK 6.5.18 after the upgrade, IFA and IPID are not supported, and FP does not support matching the packet fragment ID. N8560_FSOS 12.5(1)B0505 853495 CPP Protocol Difference – SDN Protocol Compatibility Issues Between 11.X and 12.X Upgrades/Downgrades 11xSdn Sdn_of_fetch Sdn_of_copy Sdn_of_trap12X merged into trap display N8560_FSOS 12.5(1)B0505 853344 CPP Protocol Difference – BFD Protocol Compatibility Issues Between 11.X and 12.X Upgrades/Downgrades In 11.X, show cpu protect displays bfd, micro-bfd, and micro-bfd-v6; in 12.X, it only displays bfd. N8560_FSOS 12.5(1)B0505 853497 CPP Protocol Differences: MPLS Compatibility Between 11.X and 12.X [Product Difference] 12.x introduces a separate IPv6 type due to chip-level distinction (e.g., JR). 11.x JR-based devices also differentiate between IPv4 and IPv6. N8560_FSOS 12.5(1)B0505 918437 [Product Difference] When upgrading directly from 11.x to 12.x, static MAC configurations for VXLAN become disordered. - N8560_FSOS 12.5(1)B0505 Compatibility Notes Hardware Support Notes The following are the hardware models and version numbers supported by this version. Hardware Type Hardware Model Hardware Version Number Description (Optional) Switch N8560-48BC 1.x Host Switch NC8200-4TD 1.x Host Switch N5860-48SC 1.x Host Switch N8560-64C 1.x Host Expansion Card NC8200-8C 1.x Expansion Card Expansion Card NC8200-24BC 1.x Expansion Card Power Supply GW-CRPS550N2C 1.x The AC power supply model for N8560-48BC and N5860-48SC. Power Supply U1A-D10550-DRB-Z 1.x The DC power supply model for N8560-48BC and N5860-48SC. Power Supply U1D-D10800-DRB 1.x The DC 800W power supply model for the N8560-48BC, N5860-48SC, and N8560-64C. Power Supply GW-CRPS550N2RC 1.x The AC power supply model for the N5860-48BC and N5860-48SC, Front-to-Back. Power Supply GW-CRPS800N2C 1.x NC8200-4TD、N8560-64C 800W Fan AFM-NC4TD-FB 1.x NC8200-4TD Front-to-Back airflow fan module. Fan AFM-N48SC-FB 1.x, Fan model for N5860-48SC and N8560-48BC, Front-to-Back Fan M1EFAN IV-R 1.x Fan model for N5860-48SC、N5860-48BC, Back-to-Front Fan AFM-N64C-FB 1.x Fan model for N8560-64C, Front-to-Back Upgrade Instructions Upgrade File File Name N8560_FSOS12.5(1)B0508S10_install.bin File Description System Installation Package (For 12.x Upgrade Only) File Size 148,390,603 bytes Applicable Products N8560-48BC、NC8200-4TD、N5860-48SC、N8560-64C MD5 Value f38ab7ca39444710348b1d0eb13c7135 Software Version N8560_FSOS 12.5(1)B0508S10 Upgrade Requirements (Upgrade Notes) 5.2.1. Pre-upgrade Checks Perform the following checks before upgrading to help prevent upgrade failures: If service interruptions are allowed during the upgrade, it is recommended to stop any unrelated services to improve the reliability of the upgrade. Check memory and CPU utilization. Avoid upgrading when CPU utilization is high (e.g., above 80%) or memory usage is high (e.g., above 70%). Upgrading under such conditions may lead to system instability, resulting in transmission or upgrade failures. Prepare a rollback package. If you need to prevent issues such as system malfunctions (e.g., trial versions) after the upgrade, and the selected upgrade method does not support rollback, you should prepare the upgrade package of the previous version in advance. Check the validity of the upgrade package. Compare the actual MD5 of the current upgrade package with the one listed in the release notes, or verify if the upgrade package type matches the device that is being upgraded. The installation package dedicated to upgrading from 11.x, (upgrade_from_11.x)N8560_FSOS12.5(1)B0508_install.bin, will cause a restart during the upgrade process. After the restart, the device will begin automatically upgrading to 12.x. During this process, ensure there is no power interruption or restart, and refrain from performing any other operations until the device automatically restarts and enters the 12.x CLI interface. During the upgrade or downgrade process, please pay close attention to the output prompts. If any failure occurs, save the log information and contact our technical support. During the upgrade or downgrade process, you may encounter prompts indicating that a restart is not allowed. If such prompts appear, please do not power off, reset the system, or unplug any modules. During the upgrade or downgrade process, please pay close attention to the output prompt information. If a failure occurs, save the log information and contact our technical support. During the upgrade or downgrade process, you may encounter prompts indicating that a restart is not allowed. If such a prompt appears, do not power off, reset the system, or remove/insert any modules. During the upgrade process, ensure that you do not power off, restart, or perform any other actions until the system automatically reboots to the 12.X CLI interface (estimated time: around 1h 30mins, depending on the actual situation). Failure to do so may result in upgrade failure or device malfunction. Before downgrading from 12.x to 11.x, if the device has a configured password, please remove the password or delete the configuration before downgrading. Otherwise, issues may occur after downgrading (as 11.x and 12.x handle password parsing differently), such as missing username configurations. After upgrading from 11.x to 12.x, the order of some configurations may change. During the downgrade process, ensure that the system is not powered off or rebooted, and avoid making any other operations. Once the version update is complete, enter the CLI interface. Do not perform any write operations while the system is in the intermediate version. After the upgrade or downgrade is complete, please run the "show version" command to check the current device version and confirm the success of the upgrade. 5.2.2. Upgrade Operation Instructions Upgrade via USB Drive Insert the USB drive into the device and use the upgrade command to complete the installation package upgrade. An example of the upgrade process is as follows: Hostname# upgrade usb0: /xxx/hulkos.bin Installation Package Local Upgrade Steps Under the condition that the network communication between the device and the PC is normal, use the copy oob_tftp command to transfer the installation package to the device, and then use the upgrade command to complete the installation package upgrade. Assuming the PC's address is 1.1.1.3, the upgrade example is as follows: FS# config FS(config)# interface mgmt 0 FS(config-if-Mgmt 0)# ip address 1.1.1.1/24 FS(i config-if-Mgmt 0)# end FS# copy oob_tftp://1.1.1.3/hulkos.bin flash:hulkos.bin FS# upgrade flash:hulkos.bin Network Upgrade Steps for Installation Package Ensure network connectivity between the device and the PC. Use the upgrade download oob_tftp command to complete the upgrade. Assuming the PC's IP address is 1.1.1.3, an upgrade example is as follows: FS# config FS(config)# interface mgmt 0 FS(config-if-Mgmt 0)# ip address 1.1.1.1/24 FS(config-if-Mgmt 0)# end FS# upgrade download oob_tftp://1.1.1.3/ hulkos.bin Upgrade Steps Under rboot Mode First, press Ctrl + C during bootup to enter rboot. Then, in the rboot menu, select Tftp utilities -> Upgrade main program to proceed with the upgrade. Connect the PC to the device’s MGMT port, set the device’s management IP address to 1.1.1.2. Assuming the PC’s address is 1.1.1.3, an upgrade example is as follows: ====== Rboot Menu (Ctrl+Z to upper level) ====== TOP menu items. ************************************************ 0. Tftp utilities. 1. X/Y/ZModem utilities. 2. Run main. 3. SetMac utilities. 4. Scattered utilities. ************************************************ Press a key to run the command: 0 ====== Rboot Menu (Ctrl+Z to upper level) ====== Tftp utilities. ************************************************ 0. Upgrade uboot/bios program. 1. Upgrade rboot program. 2. Upgrade main program. 3. Upgrade the entire device by distribute package. 4. Burn the total FlashROM by this downloaded file. ************************************************ Press a key to run the command: 2 Plz enter the Local IP [192.168.64.31]:1.1.1.2 Plz enter the Remote IP [192.168.64.1]:1.1.1.3 Plz enter the Filename [fsos.bin]:fsos.bin If the upgrade file is already stored locally, select X/Y/ZModem utilities -> Local utilities -> Upgrade main program in the rboot menu and enter the file path to proceed with the upgrade. ====== Rboot Menu (Ctrl+Z to upper level) ====== TOP menu items. ************************************************ 0. Tftp utilities. 1. X/Y/ZModem utilities. 2. Run main. 3. SetMac utilities. 4. Scattered utilities. ************************************************ Press a key to run the command: 1 ====== Rboot Menu (Ctrl+Z to upper level) ====== X/Y/ZModem utilities. ************************************************ 0. XModem utilities. 1. YModem utilities. 2. ZModem utilities. 3. Local utilities. ************************************************ Press a key to run the command: 3 ====== Rboot Menu (Ctrl+Z to upper level) ====== Local utilities. ************************************************ 0. Upgrade uboot program. 1. Upgrade rboot program. 2. Upgrade main program. 3. Upgrade the entire device by distribute package. 4. Burn the total FlashROM by this downloaded file. ************************************************ Press a key to run the command: 2 Plz enter the Filepath [fsos.bin]:/xxx/fsos.bin 5.2.3. Post-Upgrade Checklist After the upgrade, check the following system status items to verify whether the upgrade was successful: Verify upgrade success. In rboot, the upgrade status can be determined by checking the logs during the upgrade process. Plz enter the Filepath [fsos.bin]: /xxx/fsos.bin Checking file, keep power on and wait please ... Determined to upgrade? [Y/N]: y Rootfs found: rootfs.sqsh Uboot found: Rboot found: Extract package.... Mount rootfs file system ... Install rootfs files to Flash ... !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Install main success. Upgrade main(or uboot/rboot) finish. Success (or upgrade nothing due to version is same). For upgrades performed using the upgrade command, you can determine if the upgrade was successful by checking the logs during the upgrade process and using the show upgrade status command. FS#upgrade flash: fsos.bin < The terminal is locked by upgrade module > Upgrade start !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!10% < you can press Ctrl+C to unlock terminal > !!!!!!!!!!!!100% Upgrade success [Slot 0] Device type : N8560-48BC Status : success < The terminal is unlocked by upgrade module > FS#show upgrade status upgrade global status: INIT [Slot 0] Device type : N8560-48BC Status : success Verify New Version You can check the system's displayed version and upgrade status by using the show upgrade history and show upgrade status commands. The upgrade history can confirm the success of the upgrade by checking the upgrade time and package name. FS# show upgrade status upgrade global status: INIT [Slot 0] Device type : N8560-48BC Status : ready FS#show upgrade history Upgrade History Information: Time : 2000-01-04 18:38:37 Method : LOCAL Package Name : fsos-factory.bin Package Type : MAIN Time : 2019-09-25 10:35:04 Method : LOCAL Package Name : fsos.bin Package Type : MAIN Package Type: MAIN FS# show version detail …Refer to the version information in Chapter 1.… Supporting Documents Document Name Document Description Release Notes for N8560 Series Switch FSOS 12.5(1)B0508S10 Version This document (i.e., this article) provides a detailed introduction to the N8560_FSOS 12.5(1)B0508S10 version, including: version information, hardware support, feature support, known issues, version change logs, and upgrade instructions.

14 Abr. 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

24 Ene. 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

22 Ene. 2025 - For details, please click the attachment icon below to view or download for a good reading experience or resources.

12 Sep. 2024 - For details, please click the attachment icon below to view or download for a good reading experience or resources.