No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Configuration Guide - Basic Configuration

S7700 and S9700 V200R010C00

This document describes methods to use command line interface and to log in to the device, file operations, and system startup configurations.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Configuring the Commander

Configuring the Commander

Configuring Basic Commander Functions

Context

To implement EasyDeploy using the Commander, you must configure a device on a network as the Commander.

NOTE:

For unified device management, specify only one device as the Commander on a networking running EasyDeploy.

Procedure

  1. Run the system-view command to enter the system view.
  2. Run the easy-operation commander ip-address ip-address [ udp-port udp-port ] command to configure the Commander IP address.

    The specified IP address must exist on the network.

  3. Run the easy-operation commander enable command to enable the Commander function.

    By default, the Commander function is disabled.

Configuring File Server Information

Context

File server information includes the IP address of the file server from which clients obtain files, user names, and passwords.

The files clients need to download are saved on the file server. After obtaining information about files to be downloaded, clients download specific files from the file server specified by the Commander based on the obtained file information.

Procedure

  1. Run the system-view command to enter the system view.
  2. Run the easy-operation command to enter the Easy-Operation view.
  3. Perform any of the following steps based on the file server type:

    • Run the tftp-server ip-address command to assign an IP address to the TFTP server.

    • Run the ftp-server ip-address [ username username [ password password ] ] command to assign an IP address to the FTP server and configure a user name and password.

    • Run the sftp-server ip-address [ username username [ password password ] ] command to assign an IP address to the SFTP server and configure a user name and password.

      If the file server is an SFTP or FTP server and has a user name and password configured, configure the user name and password on the Commander.

      Only information about one file server can be configured. If you run this command multiple times, only the latest configuration takes effect.

      NOTE:

      Using an SFTP server is recommended. FTP and TFTP protocols are less secure than SFTP.

(Optional) Configuring Network Topology Collection

Context

Network topology collection is provided by the Commander using the Neighbor Discovery Protocol (NDP) and Network Topology Discovery Protocol (NTDP). When this function is enabled on the Commander to deploy unconfigured devices, users do not need to manually collect such information as device's MAC address or ESN. After unconfigured devices are powered on and started, the Commander automatically collects device information and assigns client IDs to devices to bind device information with devices.

Procedure
  1. Enable NDP.
    1. Run the system-view command to enter the system view.

    2. Run the ndp enable command to enable NDP globally.

      By default, NDP is disabled globally.

    3. (Optional) Run the ndp enable interface { interface-type interface-number [ to interface-type interface-number ] }&<1-10> command to enable NDP on interfaces.

      By default, NDP is enabled on an interface.

    4. (Optional) Run the ndp timer aging aging-time command to configure an aging time for NDP packets.

      By default, the aging time of the NDP packets on the receiving switch is 180 seconds. The aging time of the NDP packets must be larger than the interval for sending NDP packets.

    5. (Optional) Run the ndp timer hello interval command to set the interval for sending NDP packets.

      By default, the interval for sending NDP packets is 60 seconds. The interval for sending NDP packets must be smaller than the aging time of the NDP packets.

    6. (Optional) Run the ndp trunk-member enable command to enable trunk member interface-based NDP.

      By default, trunk member interface-based NDP is disabled.

      If links are established between devices through trunk interfaces, the system discovers neighbors and displays NTDP topology information based on the trunk interfaces. To obtain link information about trunk member interfaces, run this command to enable trunk member interface-based NDP for the system to discover neighbors and query topology information about the trunk member interfaces from the NMS.

  2. Enable NTDP.
    1. Run the ntdp enable command to enable NTDP globally.

      By default, NTDP is disabled globally.

    2. (Optional) Enable NTDP on an interface.

      1. Run the interface range { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10> command to enter the interface group view.

      2. Run the ntdp enable command to enable NTDP on an interface.

        By default, NTDP is enabled on an interface.

      3. Run the quit command to return to the system view.

    3. (Optional) Run the ntdp hop max-hop-value command to set the maximum number of hops for collecting topology information using NTDP.

      By default, the maximum number of hops for collecting topology information using NTDP is 8. When the maximum number of hops is set to a large value, large memory space is occupied on the topology collection device.

    4. (Optional) Run the ntdp timer hop-delay hop-delay-time command to set the delay for the first interface to forward NTDP topology request packets.

      By default, the delay for the first interface to forward NTDP topology request packets is 200 milliseconds.

    5. (Optional) Run the ntdp timer port-delay port-delay-time command to set the delay for the other interfaces to forward NTDP topology request packets.

      By default, the delay for other interfaces to forward NTDP topology request packets is 20 milliseconds.

    6. Run the ntdp timer interval command to set the interval for collecting topology information.

      By default, the interval for collecting topology information using NTDP is 0, which indicates that topology information is not periodically collected.

      NOTE:

      The Commander collects network topology information at an interval of 5 minutes; therefore, you are advised to set the interval for collecting topology information using NTDP to less than 5 minutes.

    7. (Optional) Run the ntdp explore command in the user view to collect topology information manually.

      You can run this command to collect network topology information at any time.

  3. Configure a cluster management VLAN.
    1. Run the system-view command to enter the system view.

    2. Run the cluster enable command to enable the cluster function.

      By default, the cluster function is disabled.

    3. Run the cluster command to enter the cluster view.

    4. Run the mngvlanid vlanid command to configure a cluster management VLAN.

      By default, the cluster management VLAN is VLAN 1. However, VLAN 1 is not recommended as the cluster management VLAN. You are advised to change the cluster management VLAN to a different VLAN.

      NOTE:

      The cluster management VLAN must be the same as the VLAN to which the Commander's interfaces connected to clients.

  4. Configure Commander topology collection.
    1. Run the system-view command to enter the system view.

    2. Run the easy-operation command to enter the Easy-Operation view.

    3. Run the topology enable command to enable the Commander to collect network topology information.

      By default, the Commander cannot collect network topology information.

    4. (Optional) Run the topology save command to save the currently collected network topology information.

    5. (Optional) Run the client auto-join enable command to enable clients to automatically join the management domain of the Commander.

      By default, clients do not automatically join the management domain of the Commander.

      After a client automatically joins the management domain of the Commander, the Commander automatically learns client information and assigns the minimum ID not in use to the client. If the auto-join function is not enabled, the Commander does not assign IDs to clients, and you must run the client [ client-id ] { mac-address mac-address | esn esn } command to assign IDs to clients.

Example

Run the display easy-operation topology command to view network topology information collected by the Commander after clients are enabled to automatically join the management domain of the Commander.

<HUAWEI> display easy-operation topology
<-->:normal device         <??>:lost device
Total topology node number: 3
------------------------------------------------------------------------------
[HUAWEI: 4CB1-6C8F-0447](Commander)
|-(GE1/0/8)<-->(GE0/0/38)[HUAWEI: 0200-2326-1007](Client 1)
| |-(GE1/0/16)<-->(GE0/0/16)[HUAWEI: 0200-0000-0001](Client 2)

The command output shows that IDs are assigned to clients within the management domain of the Commander. If the auto-join function is not enabled, client IDs are not displayed.

Configuring Information About Files to Be Downloaded

Context

Information about files to be downloaded by clients includes the configuration file name, system software package name and version number, and patch file name. The network administrator can specify the type of files to be downloaded based on actual requirements.

When deploying unconfigured devices, you can specify file information for each device or specify the same file information for a group of devices with the same attribute. The system preferentially matches the rule of a single client. If no matching rule is found, the system then matches the rule of a group. If still no matching rule is found or a rule is matched but no file information is specified in the rule, the system uses the default file information.

Procedure

Perform the following steps based on the network planning.

Configure file information for a client.

  1. Run the system-view command to enter the system view.

  2. Run the easy-operation command to enter the Easy-Operation view.

  3. In the following two situations, you need to manually bind device information with devices. In other situations, go to the next step.

    • Unconfigured devices are deployed without using the network topology collection function:

      Run the client [ client-id ] { mac-address mac-address | esn esn } command to define a matching rule for the client. The client can be uniquely identified by a MAC address or an ESN.

      If client-id is not specified, the system assigns the smallest unused ID to the client.

    • Unconfigured devices are deployed using the network topology collection function, but client auto-join is disabled:

      Run the client [ client-id ] mac-address mac-address command to define a matching rule based on the client's MAC address.

  4. Run the client client-id { system-software file-name [ version ] | patch file-name | configuration-file file-name | web-file file-name | { custom-file file-name } &<1-3> }* command to configure information about files to be downloaded.

Configure file information for a client group.

  1. Run the system-view command to enter the system view.

  2. Run the easy-operation command to enter the Easy-Operation view.

  3. Perform either of the following steps based on the group type:

    • Configure a matching rule for a built-in group.

      1. Run the group build-in device-type command to create a built-in group and enter the group view.

    • Configure a matching rule for a customized group.

      1. Run the group custom { mac-address | esn | ip-address | model | device-type } group-name command to create a customized group and enter the group view.

      2. Run the match { mac-address mac-address [ mac-mask | mac-mask-length ] | esn esn | ip-address ip-address [ ip-mask | ip-mask-length ] | model model | device-type device-type } command to define the matching rule for the customized group.

    NOTE:
    • A maximum of 256 groups can be created and a maximum of 256 matching rules can be defined for the groups on the Commander. For groups created based on MAC addresses, IP addresses, or ESNs, multiple matching rules can be defined. For groups created based on device types and models, only one matching rule can be defined for each group.
    • If multiple types of groups are configured, the clients match the groups in the following sequence: MAC address > ESN > IP address > device model > device type in the customized group > device type in the built-in group.
    • If a client matches multiple groups of the same type, the groups are selected in alphabetical order of their names.
  4. Perform the following steps based on your requirements to specify the files to be downloaded:

    • Run the system-software file-name version command to specify the system software package name and version number.

    • Run the patch file-name command to specify the patch file name.

    • Run the configuration-file file-name command to specify the configuration file name.

    • Run the web-file file-name command to specify the web page file name.

    • Run the { custom-file file-name } &<1-3> command to specify the user-defined file name. A maximum of three user-defined files can be specified.

Configure default file information.

  1. Run the system-view command to enter the system view.

  2. Run the easy-operation command to enter the Easy-Operation view.

  3. Perform the following steps based on your requirements to specify the files to be downloaded:

    • Run the system-software file-name version command to specify the system software package name and version number.

    • Run the patch file-name command to specify the patch file name.

    • Run the configuration-file file-name command to specify the configuration file name.

    • Run the web-file file-name command to specify the web page file name.

    • Run the { custom-file file-name } &<1-3> command to specify the user-defined file name. A maximum of three user-defined files can be specified.

Configuring an Activation Policy for Downloaded Files

Context

When configuring an activation policy, you can configure a file activation time and a file activation mode.
  • Configuring a file activation time involves two values:
    • Specific time to activate files

      Clients will activate files at a specified time.

    • Delay time before activating files

      Clients activate downloaded files after a certain delay. The maximum delay can be 24 hours.

  • Configuring a file activation mode involves choosing between two modes:
    • Non-reset mode

      By default, a client activates downloaded files without resetting. However, if a system software package (*.cc) is downloaded, the client resets to activate downloaded files regardless of whether the reset mode is configured. If no system software package is downloaded, the client activates the downloaded files as follows:

      • The patch file is automatically activated.
      • The configuration file is reversely compiled, and commands are saved in the client one by one. The client will use the configuration for next startup. If any command configuration fails during configuration recovery, the client resets to activate the configuration file.
      • The web page file must be activated manually.
    • Reset mode

      A client will use the downloaded system software package, patch file, and configuration file for the next startup. The web page file must be activated manually after the client resets.

      • If a hot patch needs to be downloaded, you can use the default file activation mode (non-reset). If a cold patch needs to be downloaded, set the file activation mode to reset.

      • If the client uses the non-reset mode to activate a configuration file but some commands in the configuration file cannot be restored, the client automatically uses the reset mode to activate the configuration file.

      • If some clients have downstream clients attached in cascading networking, it is recommended that you configure the global file activation delay time on the Commander. If an upstream client restarts or updates the configuration immediately after downloading required files, the downstream clients connected to this client are disconnected from the Commander or file server. As a result, the EasyDeploy process fails on the downstream clients. The file activation delay time avoids this problem.

        Set an appropriate delay time based on the size of files to be downloaded, to ensure that all the downstream clients can complete file downloading within this delay time.

Clients select an appropriate activation policy based on the downloaded file information.

  • If you configure a group for clients when configuring the file information, the file activation mode and time configured in the group take effect for the matching clients. If no file activation mode or time is configured in the group, the global file activation mode and time configured on the Commander take effect. If no global file activation mode or time is configured on the Commander, the default file activation mode and time are used.
  • If you specify a specific client when configuring the file information or retain the default file information, the global file activation mode and time configured on the Commander take effect. If no global file activation mode or time is configured, the default file activation mode and time are used.
Procedure

Configure a file activation policy in the group view.

  1. Run the system-view command to enter the system view.

  2. Run the easy-operation command to enter the Easy-Operation view.

  3. Run either of the following commands depending on your situation:

    To enter the built-in group view, run the group build-in device-type command.

    To enter the customized group view, run the group custom { mac-address | esn | ip-address | model | device-type } group-name command.

  4. Run the activate-file { reload | { in time | delay delay-time } } * command to configure an activation policy for the group.

Configure a global file activation policy.

  1. Run the system-view command to enter the system view.

  2. Run the easy-operation command to enter the Easy-Operation view.

  3. Run the activate-file { reload | { in time | delay delay-time } }* command to configure a global activation policy.

(Optional) Enabling Clients to Automatically Clear Storage Space

Context

If storage space on a client is insufficient, the client cannot download system software. If this function is enabled, the client automatically deletes non-startup files if the storage space is insufficient.

NOTE:

Startup system software, including the running system software and the system software specified for next startup, will not be deleted when a client clears storage space.

This function is invalid for some types of file servers. If the file server is a TFTP server, this function does not take effect because the TFTP server does not return file size to clients. If an FTP or SFTP server does not support the function of returning file size, this function does not take effect. When an S switch serves as an FTP or a TFTP file server, the switch does not support the function of returning file size.

Procedure

  1. Run the system-view command to enter the system view.
  2. Run the easy-operation command to enter the Easy-Operation view.
  3. Run the client auto-clear enable command to enable the client to automatically clear storage space.

    By default, a client does not automatically clear storage space.

(Optional) Enabling Automatic Configuration File Backup

Context

After automatic configuration file backup is enabled, the configuration file of a client is automatically backed up to the file server for use in a faulty device replacement scenario. After a faulty client is replaced by a new client, the new client needs to obtain the latest configuration file of the faulty client to minimize impact on service.

Procedure

  1. Run the system-view command to enter the system view.
  2. Run the easy-operation command to enter the Easy-Operation view.
  3. Run the backup configuration interval interval [ duplicate ] command to set the interval and mode of automatic configuration file backup.

    By default, the configuration file is not backed up automatically.

Translation
Download
Updated: 2019-08-21

Document ID: EDOC1000141895

Views: 62116

Downloads: 221

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next