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

Command Reference

S7700 and S9700 V200R011C10

This document describes all the configuration commands of the device, including the command function, syntax, parameters, views, default level, usage guidelines, examples, and related commands.

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).
Device Management Compatible Commands

Device Management Compatible Commands

display autosave config (upgrade-compatible command)

Function

The display autosave config command displays the configuration about the autosave function, including the status of the autosave function, time for autosave check, threshold of the CPU usage, and interval during which configurations are not changed.

Format

display autosave config

Parameters

None

Views

All views

Default Level

3: Management level

Usage Guidelines

After the autosave function is configured, you can run the display autosave config command to check whether the configured parameters are correct. You can also run this command to check whether the parameters about the autosave function are properly configured when autosave cannot function normally. If not, run the set save-configuration command to adjust the parameters to restore the normal state of the autosave function.

Example

# Display the configuration about the autosave function.

<HUAWEI> display autosave config
Auto save function status: enable
Auto save checking interval: 60 minutes
The threshold of the CPU usage: 50%
The interval of the configuration not changing: 30 minutes
Table 19-1  Description of the display autosave config command output

Item

Description

Auto save function status

Indicates the status of the autosave function:

  • Enable
  • Disable

Auto save checking interval

Indicates the time for autosave check.

The threshold of the CPU usage

Indicates the threshold of the CPU usage during the autosave operation.

The interval of the configuration not changing

Indicates the interval during which system configurations are not changed.

display fault-management (upgrade-compatible command)

Function

The display fault-management command displays the contents of an alarm message, active alarm message, or event.

Format

display fault-management { alarm | active-alarm | event } [ sequence-number sequence-number ]

Parameters

Parameter Description Value
alarm Displays information about alarms. -
active-alarm Displays information about active alarms. -
event Displays information about events. -
sequence-number sequence-number Specifies the number of an alarm message, active alarm message, or event. The value is an integer ranging from 0 to 2147483647. When the value is 0, information about all alarm messages, active messages, or events is displayed.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

This command helps you obtain the contents of all alarm messages or one alarm message on a device.

Example

# Display the contents of active alarm messages in the system.

<HUAWEI> display fault-management active-alarm
A/B/C/D/E/F/G/H/I/J                                                             
A=Sequence, B=RootKindFlag(Independent|RootCause|nonRootCause)                  
C=Generating time, D=Clearing time                                              
E=ID, F=Name, G=Level, H=State                                                  
I=Description information for locating(Para info, Reason info)                  
J=RootCause alarm sequence(Only for nonRootCause alarm)                         
                                                                                
  1/Independent/2013-03-27 16:36:46/-/0xff0c201c/hwStorageUtilizationRisingAlarm
/Major/Start/OID 1.3.6.1.4.1.2011.5.25.129.2.6.1 Storage utilization exceeded th
e pre-alarm threshold.(Index=137887753, BaseUsagePhyIndex=0, UsageType=5, UsageI
ndex=0, Severity=4, ProbableCause=151, EventType=4, PhysicalName="MPU Board 2/14
", RelativeResource="", UsageValue=92, UsageUnit=1, UsageThreshold=90)          
  3/Independent/2013-03-27 16:36:47/-/0xff0c2004/hwEntityReset/Warning/Start/OID
 1.3.6.1.4.1.2011.5.25.129.2.1.5 Physical entity is reset. (Index=137363465, Sev
erity=6, ProbableCause=153, EventType=4, ContainedIn=137363461, PhysicalName=LPU
 Board 2/12, RelativeResource=, ReasonDescription=Power off for board type missm
atch)                                                                           
  4/Independent/2013-03-27 16:36:47/-/0x41932001/hwLldpEnabled/Warning/Start/OID
: 1.3.6.1.4.1.2011.5.25.134.2.1 Global LLDP is enabled.                         
  5/Independent/2013-03-27 16:36:47/-/0xff0c2004/hwEntityReset/Warning/Start/OID
 1.3.6.1.4.1.2011.5.25.129.2.1.5 Physical entity is reset. (Index=136577033, Sev
erity=6, ProbableCause=153, EventType=4, ContainedIn=136577029, PhysicalName=LPU
 Board 2/9, RelativeResource=, ReasonDescription=Power off for board type missma
tch)                                                                            
  17/Independent/2013-03-28 11:06:07/-/0x418c2001/hwGtlNearDeadline/Major/Start/
OID 1.3.6.1.4.1.2011.5.25.142.2.3 License feature All is near deadline, remain t
ime is 21 days.                                                                 
  18/Independent/2013-03-29 11:06:07/-/0x418c2001/hwGtlNearDeadline/Major/Start/
OID 1.3.6.1.4.1.2011.5.25.142.2.3 License feature All is near deadline, remain t
ime is 20 days.                                                                 
  19/Independent/2013-03-30 11:06:07/-/0x418c2001/hwGtlNearDeadline/Major/Start/
OID 1.3.6.1.4.1.2011.5.25.142.2.3 License feature All is near deadline, remain t
ime is 19 days.                                                                 
  20/Independent/2013-03-31 11:06:08/-/0x418c2001/hwGtlNearDeadline/Major/Start/
OID 1.3.6.1.4.1.2011.5.25.142.2.3 License feature All is near deadline, remain t
ime is 18 days.   

display fault-management alarm information (upgrade-compatible command)

Function

The display fault-management alarm information command displays registration information about an alarm message.

Format

display fault-management alarm information [ alarm-name ]

Parameters

Parameter Description Value
alarm-name Specifies the name of an alarm message. The value is a case-sensitive string of 1 to 256 characters without spaces.

Views

All views

Default Level

1: Monitoring level

Usage Guidelines

None

Example

# Check registration information about the alarm message named linkUp.

<HUAWEI> display fault-management alarm information linkUp
**********************************                                              
  AlarmName: linkUp                                                             
  AlarmType: Resume Alarm                                                       
  AlarmLevel: Cleared                                                           
  Suppress Period: NA                                                           
  CauseAlarmName: linkDown                                                      
  Match VB Name: ifIndex                                                        
**********************************
Table 19-2  Description of the display fault-management alarm information command output

Item

Description

AlarmName

Name of an alarm message

AlarmType

Type of an alarm

AlarmLevel

Level of an alarm

Suppress Period

Suppress period of an alarm

CauseAlarmName

Name of the corresponding root alarm

Match VB Name

Contents of the matching rule set for the alarm messages

dual-active detect mode direct (upgrade-compatible command)

Function

The dual-active detect mode direct command enables DAD in direct mode on a specified interface.

By default, DAD is disabled on an interface in a CSS.

Format

dual-active detect mode direct

Parameters

None

Views

Ethernet interface view, GE interface view, XGE interface view, 40GE interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

DAD in direct mode applies to a CSS containing two DAD-supporting member switches.

Prerequisites

The CSS containing two member switches is running properly, and DAD in relay mode is not configured for the CSS.

Precautions

Disabling DAD in direct mode on an interface restores the forwarding function on the interface. If a loop exists on the network, a broadcast store occurs.

It is replaced by the mad detect mode direct command.

Example

# Configure DAD in direct mode on GigabitEthernet1/1/0/1.

<HUAWEI> system-view
[HUAWEI] interface gigabitethernet 1/1/0/1
[HUAWEI-GigabitEthernet1/1/0/1] dual-active detect mode direct
Warning: This command will block the port, and no other configuration running on this port is recommended. Continue?[Y/N]:y

dual-active detect mode relay (upgrade-compatible command)

Function

The dual-active detect mode relay command enables DAD in relay mode on a specified interface.

By default, DAD is disabled on an interface in a CSS.

Format

dual-active detect mode relay

Parameters

None

Views

Eth-Trunk interface view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

You can configure DAD in relay mode only when a CSS containing two member switches is configure with an inter-chassis Eth-Trunk and a proxy device supports the relay function.

Prerequisites

The CSS containing two member switches is running properly, and DAD in direct mode is not configured for the CSS.

Precautions

It is replaced by the mad detect mode relay command.

Example

# Configure DAD in relay mode on Eth-Trunk 10.

<HUAWEI> system-view
[HUAWEI] interface eth-trunk 10
[HUAWEI-Eth-Trunk10] dual-active detect mode relay

dual-active exclude (upgrade-compatible command)

Function

The dual-active exclude command excludes specified interfaces of a CSS from shutdown.

By default, only physical member ports are excluded from shutdown.

Format

dual-active exclude interface { interface-type interface-number1 [ to interface-type interface-number2 ] } &<1-10>

Parameters

Parameter Description Value
interface { interface-type interface-number1 [ to interface-type interface-number2 ] }
Specifies the type and number of an interface:
  • interface-type specifies the type of the interface.

  • interface-number1 specifies the number of the first interface.

  • interface-number2 specifies the number of the second interface.

The value of interface-number2 must be larger than that of interface-number1.

Views

System view

Default Level

2: Configuration level

Usage Guidelines

This command is available to aid upgrade compatibility. It can be run when it is entered in full.

After the upgrade, it is replaced by the mad exclude command.

dual-active relay (upgrade-compatible command)

Function

The dual-active relay command enables the relay function on a specified interface of a proxy device.

By default, the relay function is disabled on an interface.

Format

dual-active relay

Parameters

None

Views

Eth-Trunk interface view

Default Level

2: Configuration level

Usage Guidelines

In DAD in relay mode, you need to use the dual-active relay command to configure the relay function on a specified Eth-Trunk interface of a proxy device. Member interfaces of the Eth-Trunk interface forward DAD packets to each other so that member switches can exchange DAD packets.

It is replaced by the mad relay command.

Example

# Enable the relay function on Eth-Trunk 10 of a proxy device.

<HUAWEI> system-view
[HUAWEI] interface eth-trunk 10
[HUAWEI-Eth-Trunk10] dual-active relay

dual-active restore (upgrade-compatible command)

Function

The dual-active restore command restores the blocked interfaces of the standby switch that enters the Recovery state after its CSS splits.

Format

dual-active restore

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenario

After a CSS splits, if the active switch fails, you can restore the blocked interfaces of the standby switch that enters the Recovery state to make the standby switch to take over the active role.

Precautions

When the active switch is working properly, do not use this command. Otherwise, DAD detects a dual-active scenario again and blocks all service interfaces, causing interface status flapping.

It is replaced by the mad restore command.

Example

# Restore all the blocked interfaces of the standby switch that enters the Recovery state after its CSS splits.

<HUAWEI> system-view
[HUAWEI] dual-active restore

fault-management alarm (upgrade-compatible command)

Function

The fault-management alarm command configures the type or level of an alarm message or event.

The undo fault-management alarm command cancels the type or level of an alarm message or event.

Format

fault-management alarm alarm-name level alarm-level

undo fault-management alarm alarm-name [ level ]

Parameters

Parameter Description Value
alarm alarm-name Specifies the name of an alarm message or event. The value is a case-sensitive string of 1 to 64 characters without spaces.
level alarm-level Specifies the level of an alarm message or event. Mappings between alarm levels and severity levels:
  1. Critical: Indicates that a service affecting condition has occurred and an immediate corrective action is required. Such a severity can be reported. For example, when a managed object becomes totally out of service, its capability must be restored.
  2. Major: Indicates that a service affecting condition has developed and an urgent corrective action is required. Such a severity can be reported. For example, when there is a severe degradation in the capability of a managed object, its full capability must be restored.
  3. Minor: Indicates the existence of a non-service affecting fault condition and that corrective action should be taken in order to prevent a more serious (for example, service affecting) fault. Such a severity can be reported. For example, when the detected alarm condition is not currently degrading the capacity of the managed object.
  4. Warning: Indicates the detection of a potential or impending service affecting fault, before any significant effects have been felt. Action should be taken to further diagnose (if necessary) and correct the problem in order to prevent it from becoming a more serious service affecting fault.
  5. Indeterminate: Indicates that the severity level cannot be determined.
  6. Cleared: Indicates the clearing of one or more previously reported alarms. This alarm clears all alarms for this managed object that have the same Alarm type, Probable cause and Specific problems (if given). Multiple associated notifications may be cleared by using the Correlated notifications parameter.
The value is a character string. In the X.733 standard, according to the severity level and emergency level, alarm messages are classified into six levels. The more serious event an alarm message indicates, the smaller alarm-level is. Critical indicates the alarm severity 1; whereas Cleared indicates the alarm severity 6.

Views

System view

Default Level

3: Management level

Usage Guidelines

Alarm messages can be classified into root alarm messages and resume-alarm messages. All the alarms are saved on the device.

Events can be classified into critical events and events. Critical events are saved on a device and can be obtained by the NMS. Events are not saved on a device.

The fault-management alarm command can be used to promote or degrade the level of an alarm message according to the severity level and emergency level of the alarm message.

Example

# Set the alarm severity of the alarm message named hwCfgManEventlog to major respectively.

<HUAWEI> system-view
[HUAWEI] fault-management alarm hwCfgManEventlog level major

poe max-power (upgrade-compatible command)

Function

The poe max-power command sets the maximum output power of an interface.

By default, the maximum output power of an interface is 37000 mW.

Format

poe max-power port-max-power

Parameters

Parameter

Description

Value

port-max-power

Specifies the maximum output power of an interface.

The value is an integer that ranges from 0 to 37000, in mW.

Views

GE interface view, port group view

Default Level

2: Configuration level

Usage Guidelines

Usage Scenarios

The PD negotiation power may be different from the power required by some non-standard PDs or PDs that cannot be classified. You can run the poe max-power command to set the maximum output power of the interface, which prevents power overload for PDs and saves energy.

Generally, the maximum power required by a standard PD is 30000 mW. To be compatible with more PDs, the device provides a maximum interface power of 37000 mW. Therefore the reserved power is 7000 mW.

Prerequisites

The PoE function has been enabled on the interface using the poe enable command.

Example

# Set the maximum output power on GigabitEthernet5/0/0 to 20000 mW.
<HUAWEI> system-view
[HUAWEI] interface gigabitEthernet 5/0/0
[HUAWEI-GigabitEthernet5/0/0] poe max-power 20000

reset fault-management (upgrade-compatible command)

Function

The reset fault-management command clears all alarm messages.

Format

reset fault-management { active-alarm | event } [ sequence-number sequence-number ]

Parameters

Parameter Description Value
active-alarm Clears information about active alarms. -
event Clears event information. -
sequence-number sequence-number Specifies the number of an alarm message. The value is an integer ranging from 0 to 2147483647. If the value is 0, it indicates that all alarm messages are cleared.

Views

System view

Default Level

3: Management level

Usage Guidelines

If sequence-number is not specified, the system clears all the alarm messages on the device.

After this command is run, all alarm messages on a device are cleared and cannot be restored.

Example

# Clear all active alarm messages.

<HUAWEI> system-view
[HUAWEI] reset fault-management active-alarm

username password (upgrade-compatible command)

Function

The username password command configures the user name and password for logging in to the PM server.

By default, no user name and password for logging in to the PM server are configured.

Format

username user-name password simple password

Parameters

Parameter Description Value
username user-name Specifies a user name for logging in to the PM server. The password is a string of 1 to 255 case-sensitive characters, spaces and question marks not supported.
password password Specifies a password for logging in to the PM server. The password is a string of 1 to 128 case-sensitive characters, spaces and question marks not supported. After the password is configured, a 32-bit to 200-bit encrypted password will be displayed in the configuration file.
simple Specifies that the password is in plaintext. -

Views

PM server view

Default Level

2: Configuration level

Usage Guidelines

This command is available to aid upgrade compatibility. It can only be run during the configuration restoration phase of the upgrade.

This command is saved in simple text after it is configured, which brings security risks. Saving the command configuration in ciphertext is recommended.

snmp-agent trap enable basetrap (upgrade-compatible command)

Function

The snmp-agent trap enable basetrap command enables the trap function of basetrap.

The undo snmp-agent trap enable basetrap command disables the trap function of basetrap.

Format

snmp-agent trap enable basetrap

undo snmp-agent trap enable basetrap

Parameters

None

Views

System view

Default Level

2: Configuration level

Usage Guidelines

This is an upgrade compatible command. It can only be executed during configuration restoration after an upgrade and cannot be executed manually.

ntp-service authentication-keyid (upgrade-compatible command)

Function

The ntp-service authentication-keyid command sets NTP authentication key.

The undo ntp-service authentication-keyid command removes NTP authentication key.

By default, no authentication key is set.

Format

ntp-service authentication-keyid key-id authentication-mode { md5 | hmac-sha256 } plain password-plain

undo ntp-service authentication-keyid key-id

Parameters

Parameter Description Value
key-id Indicates the key number. Key ID is an integer and ranges from 1 to 4294967295.
authentication-mode md5 Indicates MD5 authentication mode. -
authentication-mode hmac-sha256 Indicates HMAC-SHA256 authentication mode. -
plain password-plain

Indicates that the configured password is displayed in plain text, and specifies the password.

NOTICE:

If plain is selected, the password is saved in the configuration file in plain text. This brings security risks.

The password is a string of 1 to 255 case-sensitive characters without spaces.

Views

System view

Default Level

2: Management level

Usage Guidelines

Usage Scenario

On a network that requires high security, the NTP authentication must be enabled. You can configure password authentication between client and server, which guarantee the client only to synchronize with server successfully authenticated, and improve network security. If the NTP authentication function is enabled, a reliable key should be configured at the same time. Keys configured on the client and the server must be identical.

NOTE:

In NTP symmetric peer mode, the symmetric active peer functions as a client and the symmetric passive peer functions as a server.

Follow-up Procedure

You can configure multiple keys for each device. After the NTP authentication key is configured, you need to set the key to reliable using the ntp-service reliable authentication-keyid command. If you do not set the key to reliable, the NTP key does not take effect.

Precautions

To ensure security, you are advised to use the HMAC-SHA256 algorithm, which is more secure, for NTP authentication.

You can configure a maximum of 1024 keys for each device.

If the NTP authentication key is a reliable key, it automatically becomes unreliable when you delete the key. You do not need to run the undo ntp-service reliable authentication-keyid command.

Example

# Set authentication text to abc in HMAC-SHA256 authentication with plain option.

<HUAWEI> system-view
[HUAWEI] ntp-service authentication-keyid 10 authentication-mode hmac-sha256 plain abc 
Translation
Download
Updated: 2019-10-18

Document ID: EDOC1000178288

Views: 34272

Downloads: 109

Average rating:
This Document Applies to these Products

Related Version

Related Documents

Share
Previous Next