01-Fundamentals Configuration Guide

HomeSupportConfigure & DeployConfiguration GuidesH3C MSR810 2600 3600 Routers Configuration Guides(V7)-R0707-6W30101-Fundamentals Configuration Guide
07-Software upgrade configuration
Title Size Download
07-Software upgrade configuration 128.50 KB

Upgrading software

About software upgrade

Software upgrade enables you to upgrade a software version, add new features, and fix software bugs. This chapter describes software types and release forms, compares software upgrade methods, and provides the procedures for upgrading software from the CLI.

Software types

The following software types are available:

·     BootWare image—Also called the Boot ROM image. This image contains a basic segment and an extended segment.

¡     The basic segment is the minimum code that bootstraps the system.

¡     The extended segment enables hardware initialization and provides system management menus. When the device cannot start up correctly, you can use the menus to load software and the startup configuration file or manage files.

Typically, the BootWare image is integrated into the Boot image to avoid software compatibility errors.

·     Comware image—Includes the following image subcategories:

¡     Boot image—A .bin file that contains the Linux operating system kernel. It provides process management, memory management, file system management, and the emergency shell.

¡     System image—A .bin file that contains the Comware kernel and standard features, including device management, interface management, configuration management, and routing.

¡     Feature image—A .bin file that contains advanced or customized software features. You can purchase feature images as needed.

¡     Patch image—A .bin file that is released for fixing bugs without rebooting the device. A patch image does not add or remove features.

Patch images have the following types:

-     Incremental patch images—Multiple incremental patch images can coexist on the device at the same time. A new patch image can cover all, part, or none of the functions provided by an old patch image.

-     Non-incremental patch images—Only one non-incremental patch image can coexist on the device. The device uninstalls the old non-incremental patch image before installing a new non-incremental patch image. A new non-incremental patch image covers all functions provided by an old non-incremental patch image.

An incremental patch image and a non-incremental patch image can coexist on the device.

Comware images that have been loaded are called current software images. Comware images specified to load at the next startup are called startup software images.

BootWare image, boot image, and system image are required for the device to operate.

Software release forms

Software images are released in one of the following forms:

·     Separate .bin files. You must verify compatibility between software images.

·     As a whole in one .ipe package file. The images in an .ipe package file are compatible. The system decompresses the file automatically, loads the .bin images and sets them as startup software images.

 

 

NOTE:

Software image file names use the model-comware version-image type-release format. This document uses boot.bin and system.bin as boot and system image file names.

 

Upgrade methods

Upgrade method

Software types

Remarks

Upgrading from the CLI by using the boot loader method

·     BootWare image

·     Comware images (excluding incremental patches)

This method is disruptive. You must reboot the entire device to complete the upgrade.

Performing an upgrade by using install commands

Comware images

This method installs new features or patches or upgrades the boot, system, or feature images.

Upgrading from the BootWare menu

·     BootWare image

·     Comware images

Use this method when the device cannot start up correctly.

To use this method, first connect to the console port and power cycle the device. Then, press Ctrl+B at prompt to access the BootWare menu.

For more information about upgrading software from the BootWare menu, see the release notes for the software version.

IMPORTANT IMPORTANT:

Use this method only when you do not have any other choice.

 

This chapter covers only upgrading software from the CLI by using the boot loader method.

Software image loading

Startup software images

To upgrade software, you must specify the upgrade files as the startup software images for the device to load at next startup. You can specify two lists of software images: one main and one backup. The device first loads the main startup software images. If the main startup software images are not available, the device loads the backup startup software images.

Image loading process at startup

At startup, the device performs the following operations after loading and initializing BootWare:

1.     Loads main images.

2.     If any main image does not exist or is invalid, loads the backup images.

3.     If any backup image does not exist or is invalid, checks the main or backup boot image.

4.     If the main or backup boot image exist and is valid, enters the emergency shell.

5.     If both the main and backup boot images do not exist or are invalid, the device cannot start up.

Handling the emergency shell process or image loading failure

After the device enters the emergency shell, connect to the console port and load a system image so you can access the Comware system. For more information about using the emergency shell, see "Using the emergency shell."

If the device fails to load the images, connect to the console port, power cycle the device, and use the BootWare menu to load new startup images.

Restrictions and guidelines: Software upgrade

As a best practice, store the startup images in a fixed storage medium. If you store the startup images in a hot swappable storage medium, do not remove the hot swappable storage medium during the startup process.

Upgrading device software by using the boot loader method (in standalone mode)

Prerequisites

1.     Use the display version command to verify the current BootWare image version and startup software version.

2.     Use the release notes for the upgrade software version to evaluate the upgrade impact on your network and verify the following items:

¡     Software and hardware compatibility.

¡     Version and size of the upgrade software.

¡     Compatibility of the upgrade software with the current BootWare image and startup software image.

3.     Use the release notes to verify whether the software images require a license. If licenses are required, register and activate licenses for each license-based software image. For more information about licensing, see "Managing licenses."

4.     Use the dir command to verify that the device has sufficient storage space for the upgrade images. If the storage space is not sufficient, delete unused files by using the delete command. For more information, see "Managing file systems."

5.     Use FTP or TFTP to transfer the upgrade image file to the root directory of a file system. For more information about FTP and TFTP, see "Configuring FTP" or "Configuring TFTP." For more information about file systems, see "Managing file systems."

Specifying startup images and completing the upgrade

Perform the following steps in user view:

1.     Specify main or backup startup images.

¡     Use an .ipe file:

boot-loader file ipe-filename { backup | main }

¡     Use .bin files:

boot-loader file boot filename system filename [ feature filename&<1-30> ] { backup | main }

2.     Save the running configuration.

save

This step ensures that any configuration you have made can survive a reboot.

3.     Reboot the device.

reboot

4.     (Optional.) Verify the software image settings.

display boot-loader

Verify that the current software images are the same as the startup software images.

Upgrading device software by using the boot loader method (in IRF mode)

Prerequisites

1.     Use the display version command to verify the current BootWare image version and startup software version.

2.     Use the release notes for the upgrade software version to evaluate the upgrade impact on your network and verify the following items:

¡     Software and hardware compatibility.

¡     Version and size of the upgrade software.

¡     Compatibility of the upgrade software with the current BootWare image and startup software image.

3.     Use the release notes to verify whether the software images require a license. If licenses are required, register and activate licenses for each license-based software image. For more information about licensing, see "Managing licenses."

4.     Use the dir command to verify that all IRF member devices have sufficient storage space for the upgrade images. If the storage space is not sufficient, delete unused files by using the delete command. For more information, see "Managing file systems."

5.     Use FTP or TFTP to transfer the upgrade image file to the root directory of a file system. For more information about FTP and TFTP, see "Configuring FTP" or "Configuring TFTP." For more information about file systems, see "Managing file systems."

Specifying startup images and completing the upgrade

Perform the following steps in user view:

1.     Specify main or backup startup images for all member devices.

¡     Use an .ipe file:

boot-loader file ipe-filename { all | slot slot-number } { backup | main }

¡     Use .bin files:

boot-loader file boot filename system filename [ feature filename&<1-30> ] { all | slot slot-number } { backup | main }

As a best practice in a multichassis IRF fabric, specify the all keyword for the command. If you use the slot slot-number option to upgrade member devices one by one, version inconsistencies occur among the member devices during the upgrade.

2.     Save the running configuration.

save

This step ensures that any configuration you have made can survive a reboot.

3.     Reboot the IRF fabric.

reboot

4.     (Optional.) Verify the software image settings.

display boot-loader [ slot slot-number ]

Verify that the current software images are the same as the startup software images.

Upgrading device software by using install commands

Upgrade tasks at a glance

1.     (Optional.) Decompressing an .ipe file

2.     Installing or upgrading software images

3.     (Optional.) Deactivating software images

4.     (Optional.) Verifying software images

5.     Committing software changes

6.     (Optional.) Deleting inactive software images

Decompressing an .ipe file

1.     (Optional.) Identify images that are included in the .ipe file.

display install ipe-info

2.     Decompress the .ipe file.

install add ipe-filename filesystem

Installing or upgrading software images

About installing or upgrading software images

You can install a new feature or patch image, or upgrade an existing boot, system, or feature image.

The device requires a boot image and a system image to operate correctly. You can uninstall only feature and patch images.

Software image installation and upgrade methods

Use one of the following methods to activate software images:

·     Slot by slot—Activate all the images on one slot, and then move to the next slot.

·     Image by image—Activate one image on all slots before activating another image. Before using this method, read the release notes to make sure the upgrade images are compatible with the current images. If the upgrade images are not compatible with the current images, the upgrade might fail.

Restrictions and guidelines

(In IRF mode.) To install an image, you must begin with the master device. To upgrade an image, you must begin with a subordinate device.

The activate operation only updates the current software image list. For the image changes to take effect after a reboot, you must perform a commit operation to update the main startup image list.

Installing or upgrading boot, system, and feature images

To activate boot, system, and feature images, execute the following commands in user view:

1.     Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful installation or upgrade, you must make sure the system is stable before you proceed to the next step.

2.     Activate images.

In standalone mode:

install activate { boot filename | system filename | feature filename&<1-30> }

In IRF mode:

install activate { boot filename | system filename | feature filename&<1-30> } * slot slot-number

Installing patch images

To activate patch images, execute the following commands in user view:

1.     Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful installation, you must make sure the system is stable before you proceed to the next step.

2.     Activate patch images.

In standalone mode:

install activate patch filename

You can specify only one patch image file for this command at a time. However, you can execute this command multiple times to install multiple patch image files.

In IRF mode:

install activate patch filename { all | slot slot-number }

You can specify only one patch image file for this command at a time. However, you can execute this command multiple times to install multiple patch image files.

The install activate patch filename all command installs the specified patch images on all hardware and the images can survive a reboot. You do not need to execute the install commit command for the installation.

Deactivating software images

Restrictions and guidelines

You can deactivate only feature and patch images.

The deactivate operation only removes images from the current software image list. For the image changes to take effect after a reboot, you must perform a commit operation to remove the images from the main startup image list.

Deactivated images are still stored on the storage medium. To permanently delete the images, execute the install remove command. For more information, see "Deleting inactive software images."

Deactivating feature images

To deactivate feature images, execute the following commands in user view:

1.     Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful deactivate operation, you must make sure the system is stable before you proceed to the next step.

2.     Deactivate feature images.

In standalone mode:

install deactivate feature filename&<1-30>

In IRF mode:

install deactivate feature filename&<1-30> slot slot-number

Deactivating patch images

To deactivate patch images, execute the following commands in user view:

1.     Verify that the system is stable.

display system stable state

The system is stable if the System State field displays Stable. For a successful deactivate operation, you must make sure the system is stable before you proceed to the next step.

2.     Deactivate patch images.

In standalone mode:

install deactivate patch filename

You can specify only one patch image file for this command at a time. However, you can execute this command multiple times to deactivate multiple patch image files.

In IRF mode:

install deactivate patch filename { all | slot slot-number }

You can specify only one patch image file for this command at a time. However, you can execute this command multiple times to deactivate multiple patch image files.

The install deactivate patch filename all command deactivates the specified patch images on all hardware and the image changes can survive a reboot. You do not need to execute the install commit command for the deactivation.

Committing software changes

About committing software changes

When you activate or deactivate images for an incremental upgrade, or activate or deactivate patch images, the main startup image list does not update with the changes. The software changes are lost at reboot. For the changes to take effect after a reboot, you must commit the changes.

Procedure

To commit software changes, execute the following command in user view:

install commit

Verifying software images

About software image verification

Perform this task to verify the following items:

·     Integrity—Verify that the boot, system, and feature images are integral.

·     Consistency—Verify that the same active images are running across the entire system.

·     Software commit status—Verify that the active images are committed as needed.

Procedure

To verify software images, execute the following commands in user view:

1.     Verify software images.

install verify

2.     Activate or deactivate images as required.

install { activate | deactivate }

3.     Commit the software changes.

install commit

Deleting inactive software images

About deleting inactive software images

After completing an upgrade, you can use this task to delete old image files permanently.

Restrictions and guidelines

This task deletes image files permanently.

Procedure

To delete inactive software image files, execute the following command in user view:

In standalone mode:

install remove { filename | inactive }

In IRF mode:

install remove [ slot slot-number ] { filename | inactive }

Upgrading firmware

About firmware upgrade

Perform this task to upgrade firmware for components that do not run Comware and cannot be upgraded when you upgrade Comware. Examples of these components include complex programmable logical devices (CPLDs), field programmable gate arrays (FPGAs), and 3G modems.

Restrictions and guidelines

After you upgrade firmware for a component, you must power cycle the card where the component resides for the upgrade to take effect.

You can power cycle a card by using one of the following methods:

·     Power cycle the device that holds the card.

·     Remove and reinstall the card.

·     Power cycle the card from the CLI:

¡     power-supply off

¡     power-supply on

Support for these methods depends on the card model.

Procedure

To upgrade firmware, execute the following command in user view:

In standalone mode:

firmware update [ subslot subslot-number ]  { cpld cpld-number | fpga fpga-number | module module-number } file filename

In IRF mode:

firmware update slot slot-number [ subslot subslot-number ] { cpld cpld-number | fpga fpga-number | module module-number } file filename

Display and maintenance commands for software images

(In standalone mode.) Execute display commands in any view and execute reset commands in user view.

 

Task

Command

Display current software images and startup software images.

display boot-loader

Display active software images.

display install active [ verbose ]

Display backup startup software images.

display install backup [ verbose ]

Display main startup software images.

display install committed [ verbose ]

Display inactive software images in the root directories of file systems.

display install inactive [ verbose ]

Display the software images included in an .ipe file.

display install ipe-info ipe-filename

Display ongoing activate, deactivate, and rollback operations.

display install job

Display log entries for upgrades that used install commands.

display install log [ log-id ] [ verbose ]

Display software image file information.

display install package { filename | all } [ verbose ]

Display rollback point information.

display install rollback [ point-id ]

Display the software image file that includes a specific component or file.

display install which { component name | file filename }

Display the upgrade methods.

display version comp-matrix file { boot filename | system filename | feature filename&<1-30> } *

display version comp-matrix file ipe ipe-filename

Clear log entries for upgrades that used install commands.

reset install log-history oldest log-number

Clear rollback points.

reset install rollback oldest point-id

(In IRF mode.) Execute display commands in any view and reset commands in user view.

 

Task

Command

Display current software images and startup software images.

display boot-loader [ slot slot-number ]

Display active software images.

display install active [ slot slot-number ] [ verbose ]

Display backup startup software images.

display install backup [ slot slot-number ] [ verbose ]

Display main startup software images.

display install committed [ slot slot-number ] [ verbose ]

Display inactive software images in the root directories of file systems.

display install inactive [ slot slot-number ] [ verbose ]

Display the software images included in an .ipe file.

display install ipe-info ipe-filename

Display ongoing activate, deactivate, and rollback operations.

display install job

Display log entries for upgrades that used install commands.

display install log [ log-id ] [ verbose ]

Display software image file information.

display install package { filename | all } [ verbose ]

Display rollback point information.

display install rollback [ point-id ]

Display the software image file that includes a specific component or file.

display install which { component name | file filename } [ slot slot-number ]

Display the upgrade methods.

display version comp-matrix file { boot filename | system filename | feature filename&<1-30> } *

display version comp-matrix file ipe ipe-filename

Clear log entries for upgrades that used install commands.

reset install log-history oldest log-number

Clear rollback points.

reset install rollback oldest point-id

Software upgrade examples

Example: Upgrading device software (in standalone mode)

Network configuration

As shown in Figure 1, use the file startup-a2105.ipe to upgrade software images for the device.

Figure 1 Network diagram

 

Procedure

# Configure IP addresses and routes. Make sure the device and the TFTP server can reach each other. (Details not shown.)

# Configure TFTP settings on both the device and the TFTP server. (Details not shown.)

# Display information about the current software images.

<Sysname> display version

# Back up the current software images.

<Sysname> copy boot.bin boot_backup.bin

<Sysname> copy system.bin system_backup.bin

# Specify boot_backup.bin and system_backup.bin as the backup startup image files.

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin backup

# Use TFTP to download the startup-a2105.ipe image file from the TFTP server to the root directory of the flash memory.

<Sysname> tftp 2.2.2.2 get startup-a2105.ipe

# Specify startup-a2105.ipe as the main startup image file.

<Sysname> boot-loader file flash:/startup-a2105.ipe main

# Verify the startup image settings.

<Sysname> display boot-loader

# Reboot the device to complete the upgrade.

<Sysname> reboot

Verifying the configuration

# Verify that the device is running the correct software.

<Sysname> display version

Example: Upgrading device software (in IRF mode)

Network configuration

As shown in Figure 2, use the file startup-a2105.ipe to upgrade software images for the IRF fabric.

Figure 2 Network diagram

 

Procedure

# Configure IP addresses and routes. Make sure the device and the TFTP server can reach each other. (Details not shown.)

# Configure TFTP settings on both the device and the TFTP server. (Details not shown.)

# Display information about the current software images.

<Sysname> display version

# Back up the current software images.

<Sysname> copy boot.bin boot_backup.bin

<Sysname> copy system.bin system_backup.bin

# Specify boot_backup.bin and system_backup.bin as the backup startup image files for all IRF member devices.

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin slot 1 backup

<Sysname> boot-loader file boot flash:/boot_backup.bin system flash:/system_backup.bin slot 2 backup

# Use TFTP to download the startup-a2105.ipe image file from the TFTP server to the root directory of the flash memory on the master device.

<Sysname> tftp 2.2.2.2 get startup-a2105.ipe

# Specify startup-a2105.ipe as the main startup image file for all IRF member devices.

<Sysname> boot-loader file flash:/startup-a2105.ipe slot 1 main

<Sysname> boot-loader file flash:/startup-a2105.ipe slot 2 main

# Verify the startup image settings.

<Sysname> display boot-loader

# Reboot the device to complete the upgrade.

<Sysname> reboot

Verifying the configuration

# Verify that the device is running the correct software.

<Sysname> display version

Example: Upgrading a feature by using install commands (in standalone mode)

Upgrade requirements

On the device shown in Figure 3, upgrade the Feature1 feature from T0001015 to T0001016. The two versions are compatible.

Figure 3 Network diagram

 

Upgrade procedure

 

# Download the .ipe file that contains the T0001016 Feature1 feature image from the TFTP server.

<Sysname> tftp 2.2.2.2 get feature1-t0001016.ipe

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100   256  100  256     0     0    764      0 --:--:-- --:--:-- --:--:--   810

Writing file...Done.

# Decompress the .ipe file.

<Sysname> install add flash:/feature1-t0001016.ipe flash:

Verifying the file flash:/feature1-t0001016.ipe on the device...Done.

Decompressing file feature1-t0001016.bin to flash:/feature1-t0001016.bin.......................Done.

# Display active software images.

<Sysname> display install active

Active packages on the device:

  flash:/boot-t0001015.bin

  flash:/system-t0001015.bin

  flash:/feature1-t0001015.bin

# Identify the recommended upgrade method and possible impact of the upgrade.

<Sysname> install activate feature flash:/feature1-t0001016.bin test

Verifying the file flash:/feature1-t0001016.bin on the device...Done.

Upgrade summary according to following table:

 

flash:/feature1-t0001016.bin

  Running Version             New Version

  Test 0001015                Test 0001016

 

Upgrade Way: Service Upgrade

 

Influenced service according to following table on the device:

  flash:/feature1-t0001016.bin

         Feature1

The output shows that a service upgrade is recommended and the Feature1 module will be rebooted during the upgrade process.

# Activate the new Feature1 image to upgrade the Feature1 feature.

<Sysname> install activate feature flash:/feature1-t0001016.bin

Verifying the file flash:/feature1-t0001016.bin on the device...Done.

Upgrade summary according to following table:

 

flash:/feature1-t0001016.bin

  Running Version             New Version

  Test 0001015                Test 0001016

 

Upgrade Way: Service Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait...Done.

# Verify that the new Feature1 image has been activated.

<Sysname> display install active

Active packages on the device:

  flash:/boot-t0001015.bin

  flash:/system-t0001015.bin

  flash:/feature1-t0001016.bin

# Commit the software changes.

<Sysname> install commit

This operation will take several minutes, please wait...........................Done.

Example: Upgrading a feature by using install commands (in IRF mode)

Upgrade requirements

As shown in Figure 4, the IRF fabric has two members.

Upgrade the Feature1 feature from T0001015 to T0001016. The two versions are compatible.

Figure 4 Network diagram

Upgrade procedure

 

# Download the .ipe file that contains the T0001016 Feature1 feature image from the TFTP server.

<Sysname> tftp 2.2.2.2 get feature1-t0001016.ipe

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100   256  100  256     0     0    764      0 --:--:-- --:--:-- --:--:--   810

Writing file...Done.

# Decompress the .ipe file.

<Sysname> install add flash:/feature1-t0001016.ipe flash:

Verifying the file flash:/feature1-t0001016.ipe on slot 1...Done.

Decompressing file feature1-t0001016.bin to flash:/feature1-t0001016.bin.......................Done.

# Display active software images.

<Sysname> display install active

Active packages on slot 1:

  flash:/boot-t0001015.bin

  flash:/system-t0001015.bin

  flash:/feature1-t0001015.bin

Active packages on slot 2:

  flash:/boot-t0001015.bin

  flash:/system-t0001015.bin

  flash:/feature1-t0001015.bin

# Identify the recommended upgrade methods and possible impact of the upgrade.

<Sysname> install activate feature flash:/feature1-t0001016.bin slot 2 test

Copying file flash:/feature1-t0001016.bin to slot2#flash:/feature1-t0001016.bin......Done.

Verifying the file flash:/feature1-t0001016.bin on slot 2...Done.

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

  Running Version             New Version

  Test 0001015                Test 0001016

  Slot                        Upgrade Way

  2                           Service Upgrade

Influenced service according to following table on slot 2:

  flash:/feature1-t0001016.bin

         Feature1

<Sysname> install activate feature flash:/feature1-t0001016.bin slot 1 test

Verifying the file flash:/feature1-t0001016.bin on slot 1...Done.

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

  Running Version             New Version

  Test 0001015                Test 0001016

  Slot                        Upgrade Way

  1                           Service Upgrade

Influenced service according to following table on slot 1:

  flash:/feature1-t0001016.bin

         Feature1

The output shows that both members need a service upgrade and the Feature1 module will be rebooted during the upgrade.

# Activate the new Feature1 image to upgrade the Feature1 feature.

<Sysname> install activate feature flash:/feature1-t0001016.bin slot 2

Verifying the file flash:/feature1-t0001016.bin on slot 1...Done.

flash:/feature1-t0001016.bin already exists on slot 2.

Overwrite it?[Y/N]:y

Copying file flash:/feature1-t0001016.bin to slot2#flash:/feature1-t0001016.bin......Done.

Verifying the file flash:/feature1-t0001016.bin on slot 2...Done.

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

  Running Version             New Version

  Test 0001015                Test 0001016

  Slot                        Upgrade Way

  2                           Service Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait...Done.

<Sysname> install activate feature flash:/feature1-t0001016.bin slot 1

Verifying the file flash:/feature1-t0001016.bin on slot 1...Done.

Upgrade summary according to following table:

flash:/feature1-t0001016.bin

  Running Version             New Version

  Test 0001015                Test 0001016

  Slot                        Upgrade Way

  1                           Service Upgrade

Upgrading software images to compatible versions. Continue? [Y/N]:y

This operation might take several minutes, please wait...Done.

# Display active software images.

<Sysname> display install active

Active packages on slot 1:

  flash:/boot-t0001015.bin

  flash:/system-t0001015.bin

  flash:/feature1-t0001016.bin

Active packages on slot 2:

  flash:/boot-t0001015.bin

  flash:/system-t0001015.bin

  flash:/feature1-t0001016.bin

# Commit the software changes.

<Sysname> install commit

This operation will take several minutes, please wait...........................Done.

  • Cloud & AI
  • InterConnect
  • Intelligent Computing
  • Security
  • SMB Products
  • Intelligent Terminal Products
  • Product Support Services
  • Technical Service Solutions
All Services
  • Resource Center
  • Policy
  • Online Help
All Support
  • Become a Partner
  • Partner Resources
  • Partner Business Management
All Partners
  • Profile
  • News & Events
  • Online Exhibition Center
  • Contact Us
All About Us
新华三官网