01-Fundamentals Configuration Guide

HomeSupportResource CenterSwitchesS12500X-AF SeriesS12500X-AF SeriesTechnical DocumentsConfigure & DeployConfiguration GuidesH3C S12500X-AF Switch Series Configuration Guides(R3606)-6W10001-Fundamentals Configuration Guide
10-Device management configuration
Title Size Download
10-Device management configuration 212.73 KB

Contents

Managing the device· 1

About device management 1

Device management restrictions and guidelines· 1

Device management tasks at a glance· 1

Configuring the device name· 2

Configuring the system time· 2

About the system time· 2

Restrictions and guidelines for configuring the system time· 2

System time configuration tasks at a glance· 2

Setting the system time at the CLI 3

Obtaining the UTC time through NTP· 3

Setting the time zone· 3

Setting the daylight saving time· 3

Enabling displaying the copyright statement 4

Configuring banners· 4

Disabling password recovery capability· 6

Disabling USB interfaces· 6

Setting the system operating mode· 6

Setting the TCAM operating mode· 7

Setting the port status detection timer 8

Monitoring CPU usage· 8

Monitoring CPU core usage· 9

Setting memory alarm thresholds· 10

Setting the temperature alarm thresholds· 12

Configuring hardware failure detection and protection· 13

About hardware failure detection and protection· 13

Specifying the actions to be taken for hardware failures· 13

Managing power supply· 13

About power supply management 13

Power supply management tasks at a glance· 13

Enabling power supply management 14

Specifying the number of redundant power supplies· 14

Verifying and diagnosing transceiver modules· 14

Verifying transceiver modules· 14

Diagnosing transceiver modules· 15

Specifying an ITU channel number for a transceiver module· 15

Scheduling a task· 16

About task scheduling· 16

Restrictions and guidelines for task scheduling· 16

Procedure· 16

Example: Scheduling a task· 17

Isolating switching fabric modules· 21

Suppressing removal interrupt signals from switching fabric modules· 21

Isolating a service module· 22

Rebooting the device· 22

About device reboot 22

Restrictions and guidelines for device reboot 22

Rebooting devices immediately at the CLI 22

Scheduling a device reboot 23

Restoring the factory-default configuration· 23

Display and maintenance commands for device management configuration· 24


Managing the device

About device management

This chapter describes how to configure basic device parameters and manage the device. You can perform the configuration tasks in this chapter in any order.

Device management restrictions and guidelines

After being powered on, a card takes some time to start up and complete configuration and data restoration and synchronization. Before configuring the card, use the display device and display system stable state commands to verify that the card is in Normal and Stable states. Failing to follow this rule might cause configuration failures and even device exceptions.

Device management tasks at a glance

All device management tasks are optional. You can perform any of the tasks in any order.

·     Configuring basic parameters

¡     Configuring the device name

¡     Configuring the system time

¡     Enabling displaying the copyright statement

¡     Configuring banners

·     Configuring security parameters

¡     Disabling password recovery capability

¡     Disabling USB interfaces

·     Adjusting device capacities

¡     Setting the system operating mode

¡     Setting the TCAM operating mode

¡     Setting the port status detection timer

·     Monitoring the device

¡     Monitoring CPU usage

¡     Monitoring CPU core usage

¡     Setting memory alarm thresholds

¡     Setting the temperature alarm thresholds

¡     Configuring hardware failure detection and protection

·     Managing resources

¡     Managing power supply

¡     Verifying and diagnosing transceiver modules

¡     Specifying an ITU channel number for a transceiver module

·     Maintaining the device

¡     Scheduling a task

¡     Isolating switching fabric modules

¡     Suppressing removal interrupt signals from switching fabric modules

¡     Isolating a service module

¡     Rebooting the device

¡     Restoring the factory-default configuration

Configuring the device name

About this task

A device name (also called hostname) identifies a device in a network and is used in CLI view prompts. For example, if the device name is Sysname, the user view prompt is <Sysname>.

Procedure

1.     Enter system view.

system-view

2.     Configure the device name.

sysname sysname

By default, the device name is H3C.

Configuring the system time

About the system time

Correct system time is essential to network management and communication. Configure the system time correctly before you run the device on the network.

The device can use one of the following methods to obtain the system time:

·     Uses the locally set system time, and then uses the clock signals generated by its built-in crystal oscillator to maintain the system time.

·     Periodically obtains the UTC time from an NTP source and uses the UTC time, time zone, and daylight saving time to calculate the system time. For more information about NTP, see Network Management and Monitoring Configuration Guide.

The system time calculated by using the UTC time from a time source is more precise.

Restrictions and guidelines for configuring the system time

After you configure the clock protocol none command, the clock datetime command determines the system time, whether or not the time zone or daylight saving time has been configured.

If you configure or change the time zone or daylight saving time after the device obtains the system time, the device recalculates the system time. To view the system time, use the display clock command.

System time configuration tasks at a glance

To configure the system time, perform the following tasks:

1.     Configuring the system time

Choose one of the following tasks:

¡     Setting the system time at the CLI

¡     Obtaining the UTC time through NTP

2.     (Optional.) Setting the time zone

Make sure each network device uses the time zone of the place where the device resides.

3.     (Optional.) Setting the daylight saving time

Make sure each network device uses the daylight saving time parameters of the place where the device resides.

Setting the system time at the CLI

1.     Enter system view.

system-view

2.     Configure the device to use the local system time.

clock protocol none

By default, the device uses NTP to obtain the UTC time.

If you execute this command multiple times, the most recent configuration takes effect.

3.     Return to user view.

quit

4.     Set the local system time.

clock datetime time date

By default, the factory-default system time is used.

Obtaining the UTC time through NTP

1.     Enter system view.

system-view

2.     Specify NTP for obtaining the UTC time.

clock protocol ntp mdc mdc-id

By default, the device uses NTP to obtain the UTC time.

If you execute this command multiple times, the most recent configuration takes effect.

3.     Configure time protocol parameters.

For more information about NTP configuration, see Network Management and Monitoring Configuration Guide.

Setting the time zone

1.     Enter system view.

system-view

2.     Set the time zone.

clock timezone zone-name { add | minus } zone-offset

By default, the system uses the UTC time zone.

Setting the daylight saving time

1.     Enter system view.

system-view

2.     Set the daylight saving time.

clock summer-time name start-time start-date end-time end-date add-time

By default, the daylight saving time is not set.

Enabling displaying the copyright statement

About this task

This feature enables the device to display the copyright statement in the following situations:

·     When a Telnet or SSH user logs in.

·     When a console user quits user view. This is because the device automatically tries to restart the user session.

If you disable displaying the copyright statement, the device does not display the copyright statement in any situations.

Procedure

1.     Enter system view.

system-view

2.     Enable displaying the copyright statement.

copyright-info enable

By default, displaying the copyright statement is enabled.

Configuring banners

About this task

Banners are messages that the system displays when a user logs in.

The system supports the following banners:

·     Legal banner—Appears after the copyright statement. To continue login, the user must enter Y or press Enter. To quit the process, the user must enter N. Y and N are case insensitive.

·     Message of the Day (MOTD) banner—Appears after the legal banner and before the login banner.

·     Login banner—Appears only when password or scheme authentication is configured.

·     Shell banner—Appears before the user enters user view.

The system displays the banners in the following order: legal banner, MOTD banner, login banner, and shell banner.

Banner input methods

You can configure a banner by using one of the following methods:

·     Input the entire command line in a single line.

The banner cannot contain carriage returns. The entire command line, including the command keywords, the banner, and the delimiters, can have a maximum of 511 characters. The delimiters for the banner can be any printable character but must be the same. You cannot press Enter before you input the end delimiter.

For example, you can configure the shell banner "Have a nice day." as follows:

<System> system-view

[System] header shell %Have a nice day.%

·     Input the command line in multiple lines.

The banner can contain carriage returns. A carriage return is counted as two characters.

To input a banner configuration command line in multiple lines, use one of the following methods:

¡     Press Enter after the final command keyword, type the banner, and end the final line with the delimiter character %. The banner plus the delimiter can have a maximum of 1999 characters.

For example, you can configure the banner "Have a nice day." as follows:

<System> system-view

[System] header shell

Please input banner content, and quit with the character '%'.

Have a nice day.%

¡     After you type the final command keyword, type any printable character as the start delimiter for the banner and press Enter. Then, type the banner and end the final line with the same delimiter. The banner plus the end delimiter can have a maximum of 1999 characters.

For example, you can configure the banner "Have a nice day." as follows:

<System> system-view

[System] header shell A

Please input banner content, and quit with the character 'A'.

Have a nice day.A

¡     After you type the final command keyword, type the start delimiter and part of the banner. Make sure the final character of the final string is different from the start delimiter. Then, press Enter, type the rest of the banner, and end the final line with the same delimiter. The banner plus the start and end delimiters can have a maximum of 2002 characters.

For example, you can configure the banner "Have a nice day." as follows:

<System> system-view

[System] header shell AHave a nice day.

Please input banner content, and quit with the character 'A'.

A

Procedure

1.     Enter system view.

system-view

2.     Configure one or more banners:

¡     Configure the legal banner.

header legal text

¡     Configure the MOTD banner.

header motd text

¡     Configure the login banner.

header login text

¡     Configure the shell banner.

header shell text

By default, no banner is configured.

 

Disabling password recovery capability

About this task

Password recovery capability controls console user access to the device configuration and SDRAM from BootWare menus. For more information about BootWare menus, see the release notes.

If password recovery capability is enabled, a console user can access the device configuration without authentication to configure a new password.

If password recovery capability is disabled, console users must restore the factory-default configuration before they can configure new passwords. Restoring the factory-default configuration deletes the next-startup configuration files.

To enhance system security, disable password recovery capability.

Restrictions and guidelines

To access the device configuration without authentication, you must connect to the active MPU and access the BootWare menu while the MPU is starting up.

Procedure

1.     Enter system view.

system-view

2.     Disable password recovery capability.

undo password-recovery enable

By default, password recovery capability is enabled.

Disabling USB interfaces

About this task

You can use USB interfaces to upload or download files. By default, all USB interfaces are enabled. You can disable USB interfaces as needed.

Prerequisites

Before using this command, use the umount command to unmount all USB partitions. For more information about this command, see Fundamentals Command Reference.

Procedure

1.     Enter system view.

system-view

2.     Disable USB interfaces.

usb disable

By default, all USB interfaces are enabled.

Setting the system operating mode

About this task

The device can operate in one of the following modes:

·     bridgee—Enhanced Layer 2 mode. It does not support VXLAN or ERSPAN.

·     standard—Standard mode. This mode supports VXLAN and ERSPAN. Typically, this mode is used.

Supported features and feature specifications vary by system operating mode.

Restrictions and guidelines

Change to the operating mode takes effect after a system reboot.

Procedure

1.     Enter system view.

system-view

2.     Set the system operating mode.

system-working-mode { bridgee | standard }

By default, the device operates in standard mode.

Setting the TCAM operating mode

About this task

The ternary content addressable memory (TCAM) provides an extended memory space for the device to store entries such as ARP, ACL, and routing entries. The TCAM operating mode determines the types of entries that the TCAM stores.

Table 1 describes the TCAM operating modes and the supported entry types.

Table 1 TCAM operating modes and supported entry types

TCAM operating mode

FE card

ACL mode

Stores IPv4 ACLs.

IPv6 mode

Stores ARP entries, ND entries, IPv4 routing entries, and IPv6 routing entries.

Mixed mode

Stores ARP entries, ND entries, IPv4 routing entries, and IPv6 routing entries.

Normal mode

Does not store any entries.

Routing mode

Stores ARP entries, ND entries, IPv4 routing entries, and IPv6 routing entries.

Procedure

1.     Enter system view.

system-view

2.     Set the TCAM operating mode.

hardware-resource tcam { routing | normal | acl | ipv6| mix }

By default, the TCAM operating mode is routing.

The LSXM1CGQ36HB1 card supports only the mixed mode.

3.     Save the running configuration to the next-startup configuration file.

save

To avoid configuration loss, use the save command to save the running configuration before a reboot. For more information about the save command, see Fundamentals Command Reference.

4.     Return to user view.

quit

5.     Delete the .mdb next-startup configuration file.

delete

For more information about the delete command, see Fundamentals Command Reference.

6.     Reboot the device.

reboot

Setting the port status detection timer

About this task

The device starts a port status detection timer when a port is shut down by a protocol. Once the timer expires, the device brings up the port so the port status reflects the port's physical status.

Procedure

1.     Enter system view.

system-view

2.     Set the port status detection timer.

shutdown-interval time

The default setting is 30 seconds.

Monitoring CPU usage

About this task

To monitor CPU usage, the device performs the following operations:

·     Samples CPU usage at 1-minute intervals, and compares the samples with CPU usage thresholds to identify the CPU usage status and send alarms or notifications accordingly.

·     Samples and saves CPU usage at a configurable interval if CPU usage tracking is enabled. You can use the display cpu-usage history command to display the historical CPU usage statistics in a coordinate system.

The device supports the following CPU usage thresholds:

·     Minor threshold—If the CPU usage increases above the minor threshold but is less than or equal to the severe threshold, the CPU usage enters minor alarm state. The device sends minor alarms periodically until the CPU usage increases above the severe threshold or the minor alarm is removed.

·     Severe threshold—If the CPU usage increases above the severe threshold, the CPU usage enters severe alarm state. The device sends severe alarms periodically until the severe alarm is removed.

·     Recovery threshold—If the CPU usage decreases below the recovery threshold, the CPU usage enters recovered state. The device sends a recovery notification.

CPU usage alarms and notifications can be sent to NETCONF, SNMP, and the information center to be encapsulated as NETCONF events, SNMP traps and informs, and log messages. For more information, see NETCONF, SNMP, and information center in Network Management and Monitoring Configuration Guide.

Figure 1 CPU alarms and alarm-removed notifications

Procedure

1.     Enter system view.

system-view

2.     Set the CPU usage thresholds.

monitor cpu-usage threshold cpu-threshold [ minor-threshold minor-threshold recovery-threshold recovery-threshold ] [ slot slot-number [ cpu cpu-number ] ]

By default, the severe CPU usage alarm threshold is 99%, and the minor CPU usage alarm threshold is 79%.

3.     Set the CPU usage alarm resending intervals.

monitor resend cpu-usage { minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]

By default, the minor CPU usage alarm resending interval and severe CPU usage alarm resending interval are 300 seconds and 60 seconds, respectively.

4.     Set the sampling interval for CPU usage tracking.

monitor cpu-usage interval interval [ slot slot-number [ cpu cpu-number ] ]

By default, the sampling interval for CPU usage tracking is 1 minute.

5.     Enable CPU usage tracking.

monitor cpu-usage enable [ slot slot-number [ cpu cpu-number ] ]

By default, CPU usage tracking is enabled.

Monitoring CPU core usage

About this task

The device samples CPU core usage at 5-second intervals and calculates the average value during each CPU core usage statistics interval. If the value during an interval is greater than a CPU core usage threshold, the device issues an alarm and logs the event.

Restrictions and guidelines

As a best practice, set the CPU core usage statistics interval to a multiple of 5. If you do not do so, the effective statistics interval is the biggest multiple of 5 that is smaller than the setting. For example, if you set this statistics interval to 12 seconds, the effective statistics interval is 10 seconds.

Procedure

1.     Enter system view.

system-view

2.     Set CPU core usage statistics intervals.

monitor cpu-usage statistics-interval interval slot slot-number cpu cpu-number core core-id-list

By default, the CPU core usage statistics interval is 60 seconds.

3.     Set CPU core alarm resending intervals.

monitor resend cpu-usage core-interval { minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]

By default, the resending intervals for severe CPU core usage alarms and minor CPU core usage alarms are all 300 seconds.

Setting memory alarm thresholds

About this task

To monitor memory usage, the device performs the following operations:

·     Samples memory usage at 1-minute intervals, and compares the sample with the memory usage threshold. If the sample is greater, the device sends a trap.

·     Monitors the amount of free memory space in real time. If the amount of free memory space reaches a free-memory threshold, the system generates an alarm notification and sends it to affected service modules or processes. If the amount of free memory space drops below a free-memory threshold, the system generates an alarm-removed notification and sends it to affected service modules or processes.

For slots that support low memory, the system monitors only the amount of free low-memory space. You can use the display memory command to display memory usage information. If the LowMem field is displayed for a slot, the slot supports low memory.

As shown in Table 2 and Figure 2, the system supports the following free-memory thresholds:

·     Normal state threshold.

·     Minor alarm threshold.

·     Severe alarm threshold.

·     Critical alarm threshold.

Table 2 Memory alarm notifications and memory alarm-removed notifications

Notification

Triggering condition

Remarks

Minor alarm notification

The amount of free memory space decreases below the minor alarm threshold.

After generating and sending a minor alarm notification, the system does not generate and send any additional minor alarm notifications until the minor alarm is removed.

Severe alarm notification

The amount of free memory space decreases below the severe alarm threshold.

After generating and sending a severe alarm notification, the system does not generate and send any additional severe alarm notifications until the severe alarm is removed.

Critical alarm notification

The amount of free memory space decreases below the critical alarm threshold.

After generating and sending a critical alarm notification, the system does not generate and send any additional critical alarm notifications until the critical alarm is removed.

Critical alarm-removed notification

The amount of free memory space increases above the severe alarm threshold.

N/A

Severe alarm-removed notification

The amount of free memory space increases above the minor alarm threshold.

N/A

Minor alarm-removed notification

The amount of free memory space increases above the normal state threshold.

N/A

 

Figure 2 Memory alarm notifications and alarm-removed notifications

 

 

Procedure

1.     Enter system view.

system-view

2.     Set the memory usage threshold.

memory-threshold [ slot slot-number [ cpu cpu-number ] ] usage memory-threshold

By default, the memory usage threshold is 100%.

3.     Set the memory usage alarm resending interval.

memory-threshold [ slot slot-number [ cpu cpu-number ] ] usage resend-intervel interval-value

By default, the memory usage alarm resending interval is 5 minutes.

4.     Set the free-memory thresholds.

memory-threshold [ slot slot-number [ cpu cpu-number ] ] [ ratio ] minor minor-value severe severe-value critical critical-value normal normal-value [ early-warning early-warning-value secure secure-value ]

The default settings are as follows:

¡     Minor alarm threshold—256 MB.

¡     Severe alarm threshold—192 MB.

¡     Critical alarm threshold—128 MB.

¡     Normal state threshold—320 MB.

5.     Set memory depletion alarm resending intervals.

monitor resend memory-threshold { critical-interval critical-interval | early-warning-interval early-warning-interval | minor-interval minor-interval | severe-interval severe-interval } * [ slot slot-number [ cpu cpu-number ] ]

The following are the default settings:

¡     Early warning resending interval—1 hour.

¡     Minor alarm resending interval—12 hours.

¡     Severe alarm resending interval—3 hours.

¡     Critical alarm resending interval—1 hour.

Setting the temperature alarm thresholds

About this task

The device monitors its temperature based on the following thresholds:

·     Low-temperature threshold.

·     High-temperature warning threshold.

·     High-temperature alarming threshold.

When the device temperature drops below the low-temperature threshold or reaches the high-temperature warning or alarming threshold, the device performs the following operations:

·     Sends log messages and traps.

·     Sets LEDs on the device panel.

Restrictions and guidelines

The high-temperature alarming threshold must be higher than the high-temperature warning threshold, and the high-temperature warning threshold must be higher than the low-temperature threshold.

Procedure

1.     Enter system view.

system-view

2.     Configure the temperature alarm thresholds.

temperature-limit slot slot-number { hotspot | inflow } sensor-number lowlimit warninglimit [ alarmlimit ]

The defaults vary by temperature sensor model. To view the defaults, execute the undo temperature-limit and display environment commands in turn.

Configuring hardware failure detection and protection

About hardware failure detection and protection

The device can automatically detect hardware failures on components, cards, and the forwarding plane, and take actions in response.

Specifying the actions to be taken for hardware failures

About this task

The device can take the following actions in response to hardware failures:

·     isolate—Performs the following tasks as appropriate to reduce impact from the failures:

¡     Shuts down the relevant ports.

¡     Prohibits loading software for the relevant cards.

¡     Isolates the relevant cards.

¡     Powers off the relevant cards.

·     reset—Restarts the relevant components or cards to recover from failures.

·     warning—Sends traps to report the failures.

Procedure

1.     Enter system view.

system-view

2.     Specify the action to be taken in response to a type of hardware failures.

hardware-failure-detection { board | chip | forwarding } { off | isolate | reset | warning }

By default, the system takes the action of warning in response to hardware failures.

Managing power supply

About power supply management

Power supplies might have problems such as overload overcurrent, overvoltage, overtemperature, and short circuit. Some power supplies use a hardware protection measure, for example, powering off the device, to protect the entire device from being damaged. The hardware protection measure helps protect the device but causes service outage. The power supply management feature can minimize service outage while protecting the device against overload problems.

The power supply management feature constantly monitors the available power and the system loads. If a potential power supply overload problem is found, this feature takes protective measures immediately to remove requirements for power supply hardware protection. Examples of protective measures include sending a notification, starting redundant power supplies, and powering off certain interface cards.

Power supply management tasks at a glance

To manage power supply, perform the following tasks:

1.     Enabling power supply management

2.     (Optional.) Specifying the number of redundant power supplies

To avoid overload problems, you can install redundant power supplies.

Enabling power supply management

1.     Enter system view.

system-view

2.     Enable power supply management.

power-supply policy enable

By default, power supply management is disabled.

Specifying the number of redundant power supplies

About this task

To avoid overload problems, you can install redundant power supplies. For example, if the device requires a minimum of N power supplies to operate correctly, you can install M power supplies (M > N). The M power supplies operate in load balance mode. When a power supply fails, the load is rebalanced among the other power supplies.

After you specify the number of redundant power supplies, the device compares the maximum power consumption of a newly added card with the remaining power.

·     If the remaining power is sufficient for the card, the device powers on the card.

·     If the power is insufficient, the device does not power on the card. You can add power supplies or scale the number of redundant power supplies down.

Restrictions and guidelines

This feature takes effect only if power supply management is enabled.

Procedure

1.     Enter system view.

system-view

2.     Specify the number of redundant power supplies.

power-supply policy redundant module-count

By default, the number of redundant power supplies is 0.

Verifying and diagnosing transceiver modules

Verifying transceiver modules

About this task

You can use one of the following methods to verify the genuineness of a transceiver module:

·     Display the key parameters of a transceiver module, including its transceiver type, connector type, central wavelength of the transmit laser, transfer distance, and vendor name.

·     Display its electronic label. The electronic label is a profile of the transceiver module and contains the permanent configuration, including the serial number, manufacturing date, and vendor name. The data was written to the transceiver module or the device's storage component during debugging or testing of the transceiver module or device.

The device regularly checks transceiver modules for their vendor names. If a transceiver module does not have a vendor name or the vendor name is not H3C, the device repeatedly outputs traps and log messages. For information about logging rules, see Network Management and Monitoring Configuration Guide.

Procedure

To verify transceiver modules, execute the following commands in any view:

·     Display the key parameters of transceiver modules.

display transceiver interface [ interface-type interface-number ]

·     Display the electrical label information of transceiver modules.

display transceiver manuinfo interface [ interface-type interface-number ]

Diagnosing transceiver modules

About this task

The device provides the alarm and digital diagnosis functions for transceiver modules. When a transceiver module fails or is not operating correctly, you can perform the following tasks:

·     Check the alarms that exist on the transceiver module to identify the fault source.

·     Examine the key parameters monitored by the digital diagnosis function, including the temperature, voltage, laser bias current, TX power, and RX power.

Procedure

To diagnose transceiver modules, execute the following commands in any view:

·     Display transceiver alarms.

display transceiver alarm interface [ interface-type interface-number ]

·     Display the current values of the digital diagnosis parameters on transceiver modules.

display transceiver diagnosis interface [ interface-type interface-number ]

Specifying an ITU channel number for a transceiver module

About this task

ITU numbers and identifies fiber signals by wavelength and frequency. A transceiver module sends signals of a specific wavelength and frequency based on the specified ITU channel number.

This feature is required in dense wavelength division multiplexing scenarios.

Restrictions and guidelines

This feature is supported only on the SFP-XG-LH80-Tunable transceiver module.

Procedure

1.     Enter system view.

system-view

2.     Enter Ethernet interface view.

interface interface-type interface-number

3.     Specify an ITU channel number.

itu-channel channel-number

By default, the ITU channel number is 1.

Scheduling a task

About task scheduling

You can schedule the device to automatically execute a command or a set of commands without administrative interference.

You can configure a periodic schedule or a non-periodic schedule. A non-periodic schedule is not saved to the configuration file and is lost when the device reboots. A periodic schedule is saved to the startup configuration file and is automatically executed periodically.

Restrictions and guidelines for task scheduling

·     To assign a command (command A) to a job, you must first assign the job the command or commands for entering the view of command A.

·     Make sure all commands in a schedule are compliant to the command syntax. The system does not check the syntax when you assign a command to a job.

·     A schedule cannot contain any one of these commands: telnet, ftp, ssh2, and monitor process.

·     A schedule does not support user interaction. If a command requires a yes or no answer, the system always assumes that a Y or Yes is entered. If a command requires a character string input, the system assumes that either the default character string (if any) or a null string is entered.

·     A schedule is executed in the background, and no output (except for logs, traps, and debug information) is displayed for the schedule.

Procedure

1.     Enter system view.

system-view

2.     Create a job.

scheduler job job-name

3.     Assign a command to the job.

command id command

By default, no command is assigned to a job.

You can assign multiple commands to a job. A command with a smaller ID is executed first.

4.     Exit to system view.

quit

5.     Create a schedule.

scheduler schedule schedule-name

6.     Assign a job to the schedule.

job job-name

By default, no job is assigned to a schedule.

You can assign multiple jobs to a schedule. The jobs will be executed concurrently.

7.     Assign user roles to the schedule.

user-role role-name

By default, a schedule has the user role of the schedule creator.

You can assign a maximum of 64 user roles to a schedule. A command in a schedule can be executed if it is permitted by one or more user roles of the schedule.

8.     Specify the execution time for the schedule.

Choose one option as needed:

¡     Execute the schedule at specific points of time.

time at time date

time once at time [ month-date month-day | week-day week-day&<1-7> ]

¡     Execute the schedule after a period of time.

time once delay time

¡     Execute the schedule at the specified time on every specified day in a month or week.

time repeating at time [ month-date [ month-day | last ] | week-day week-day&<1-7> ]

¡     Execute the schedule at intervals from the specified time on.

time repeating [ at time [date ] ] interval interval

By default, no execution time is specified for a schedule.

The time commands overwrite each other. The most recently configured command takes effect.

9.     (Optional.) Set the schedule log file size limit.

scheduler logfile size value

By default, the schedule log file size limit is 16 KB.

The schedule log file stores log messages for execution results of commands in jobs. After the limit is reached, the system deletes the oldest log messages to store the new log messages. If the remaining space of the log file is not enough for a single log message, the system truncates the message and does not store the extra part.

Example: Scheduling a task

Network configuration

As shown in Figure 3, two interfaces of the device are connected to users.

To save energy, configure the device to perform the following operations:

·     Enable the interfaces at 8:00 a.m. every Monday through Friday.

·     Disable the interfaces at 18:00 every Monday through Friday.

Figure 3 Network diagram

Procedure

# Enter system view.

<Sysname> system-view

# Configure a job for disabling interface HundredGigE 1/0/1.

[Sysname] scheduler job shutdown-HundredGigE1/0/1

[Sysname-job-shutdown-HundredGigE1/0/1] command 1 system-view

[Sysname-job-shutdown-HundredGigE1/0/1] command 2 interface hundredgige 1/0/1

[Sysname-job-shutdown-HundredGigE1/0/1] command 3 shutdown

[Sysname-job-shutdown-HundredGigE1/0/1] quit

# Configure a job for enabling interface HundredGigE 1/0/1.

[Sysname] scheduler job start-HundredGigE1/0/1

[Sysname-job-start-HundredGigE1/0/1] command 1 system-view

[Sysname-job-start-HundredGigE1/0/1] command 2 interface hundredgige 1/0/1

[Sysname-job-start-HundredGigE1/0/1] command 3 undo shutdown

[Sysname-job-start-HundredGigE1/0/1] quit

# Configure a job for disabling interface HundredGigE 1/0/2.

[Sysname] scheduler job shutdown-HundredGigE1/0/2

[Sysname-job-shutdown-HundredGigE1/0/2] command 1 system-view

[Sysname-job-shutdown-HundredGigE1/0/2] command 2 interface hundredgige 1/0/2

[Sysname-job-shutdown-HundredGigE1/0/2] command 3 shutdown

[Sysname-job-shutdown-HundredGigE1/0/2] quit

# Configure a job for enabling interface HundredGigE 1/0/2.

[Sysname] scheduler job start-HundredGigE1/0/2

[Sysname-job-start-HundredGigE1/0/2] command 1 system-view

[Sysname-job-start-HundredGigE1/0/2] command 2 interface hundredgige 1/0/2

[Sysname-job-start-HundredGigE1/0/2] command 3 undo shutdown

[Sysname-job-start-HundredGigE1/0/2] quit

# Configure a periodic schedule for enabling the interfaces at 8:00 a.m. every Monday through Friday.

[Sysname] scheduler schedule START-pc1/pc2

[Sysname-schedule-START-pc1/pc2] job start-HundredGigE1/0/1

[Sysname-schedule-START-pc1/pc2] job start-HundredGigE1/0/2

[Sysname-schedule-START-pc1/pc2] time repeating at 8:00 week-day mon tue wed thu fri

[Sysname-schedule-START-pc1/pc2] quit

# Configure a periodic schedule for disabling the interfaces at 18:00 every Monday through Friday.

[Sysname] scheduler schedule STOP-pc1/pc2

[Sysname-schedule-STOP-pc1/pc2] job shutdown-HundredGigE1/0/1

[Sysname-schedule-STOP-pc1/pc2] job shutdown-HundredGigE1/0/2

[Sysname-schedule-STOP-pc1/pc2] time repeating at 18:00 week-day mon tue wed thu fri

[Sysname-schedule-STOP-pc1/pc2] quit

Verifying the configuration

# Display the configuration information of all jobs.

[Sysname] display scheduler job

Job name: shutdown-HundredGigE1/0/1

 system-view

 interface hundredgige 1/0/1

 shutdown

 

Job name: shutdown-HundredGigE1/0/2

 system-view

 interface hundredgige 1/0/2

 shutdown

 

Job name: start-HundredGigE1/0/1

 system-view

 interface hundredgige 1/0/1

 undo shutdown

 

Job name: start-HundredGigE1/0/2

 system-view

 interface hundredgige 1/0/2

 undo shutdown

# Display the schedule information.

[Sysname] display scheduler schedule

Schedule name        : START-pc1/pc2

Schedule type        : Run on every Mon Tue Wed Thu Fri at 08:00:00

Start time           : Wed Sep 28 08:00:00 2011

Last execution time  : Wed Sep 28 08:00:00 2011

Last completion time : Wed Sep 28 08:00:03 2011

Execution counts     : 1

-----------------------------------------------------------------------

Job name                                          Last execution status

start-HundredGigE1/0/1                                 Successful

start-HundredGigE1/0/2                                 Successful

 

Schedule name        : STOP-pc1/pc2

Schedule type        : Run on every Mon Tue Wed Thu Fri at 18:00:00

Start time           : Wed Sep 28 18:00:00 2011

Last execution time  : Wed Sep 28 18:00:00 2011

Last completion time : Wed Sep 28 18:00:01 2011

Execution counts     : 1

-----------------------------------------------------------------------

Job name                                          Last execution status

shutdown-HundredGigE1/0/1                              Successful

shutdown-HundredGigE1/0/2                              Successful

# Display schedule log information.

[Sysname] display scheduler logfile

Job name        : start-HundredGigE1/0/1

Schedule name   : START-pc1/pc2

Execution time  : Wed Sep 28 08:00:00 2011

Completion time : Wed Sep 28 08:00:02 2011

--------------------------------- Job output -----------------------------------

<Sysname>system-view

System View: return to User View with Ctrl+Z.

[Sysname]interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1]undo shutdown

 

Job name        : start-HundredGigE1/0/2

Schedule name   : START-pc1/pc2

Execution time  : Wed Sep 28 08:00:00 2011

Completion time : Wed Sep 28 08:00:02 2011

--------------------------------- Job output -----------------------------------

<Sysname>system-view

System View: return to User View with Ctrl+Z.

[Sysname]interface hundredgige 1/0/2

[Sysname-HundredGigE1/0/2]undo shutdown

 

Job name        : shutdown-HundredGigE1/0/1

Schedule name   : STOP-pc1/pc2

Execution time  : Wed Sep 28 18:00:00 2011

Completion time : Wed Sep 28 18:00:01 2011

--------------------------------- Job output -----------------------------------

<Sysname>system-view

System View: return to User View with Ctrl+Z.

[Sysname]interface hundredgige 1/0/1

[Sysname-HundredGigE1/0/1]shutdown

 

Job name        : shutdown-HundredGigE1/0/2

Schedule name   : STOP-pc1/pc2

Execution time  : Wed Sep 28 18:00:00 2011

Completion time : Wed Sep 28 18:00:01 2011

--------------------------------- Job output -----------------------------------

<Sysname>system-view

System View: return to User View with Ctrl+Z.

[Sysname]interface hundredgige 1/0/2

[Sysname-HundredGigE1/0/2]shutdown

Isolating switching fabric modules

About this task

Isolating a switching fabric module isolates the module from the data plane. An isolated switching fabric module continues to communicate with the MPU, and can forward traffic immediately after the isolation is canceled. The isolation does not affect protocol packet parsing and protocol calculation on the control plane.

Restrictions and guidelines

CAUTION

CAUTION:

·     Do not isolate the only switching fabric module of the device.

·     Do not reboot the device when a switching fabric module is isolated.

 

Isolate a switching fabric module only if required. If the device has multiple switching fabric modules, isolating a switching fabric module or channel decreases the forwarding bandwidth and reduces the forwarding performance.

You can isolate switching fabric modules to identify whether switching fabric modules can forward traffic correctly.

Before replacing a switching fabric module, you can isolate the module to prevent packet loss.

To use an isolated switching fabric module or channel, use the undo switch-fabric isolate command to cancel the isolation.

Procedure

1.     Enter system view.

system-view

2.     Isolate a switching fabric module or channel.

switch-fabric isolate slot slot-number [ channel channel-number ]

By default, a switching fabric module is not isolated and can forward traffic.

Suppressing removal interrupt signals from switching fabric modules

About this task

Typically, removing a switching fabric module triggers one removal interrupt signal. Upon receiving the signal, the system switches traffic on the switching fabric module to other switching fabric modules to ensure service continuity. Upon hardware failure or signal interference, however, removal interrupt signals might be frequently triggered. To prevent the interrupt signals from affecting system operation, use this feature to suppress the interrupt signals.

Restrictions and guidelines

Suppressing removal interrupt signals from switching fabric modules might result in packet loss and service outage.

Procedure

1.     Enter system view.

system-view

2.     Suppress removal interrupt signals from switching fabric modules.

switch-fabric removal-signal-suppression

By default, removal interrupt signals from switching fabric modules are not suppressed.

Isolating a service module

About this task

When a service module fails, you can use this feature to isolate it to prevent it from affecting traffic forwarding. An isolated service module does not receive traffic.

Restrictions and guidelines

A service module reboot cancels the isolation of the service module.

To display service module operating status, execute the display device command. An isolated service module is in Offline state.

Procedure

1.     Enter system view.

system-view

2.     Isolate a service module.

switch-linecard isolate slot slot-number

Rebooting the device

 

About device reboot

The following device reboot methods are available:

·     Schedule a reboot at the CLI, so the device automatically reboots at the specified time or after the specified period of time.

·     Immediately reboot the device at the CLI.

During the reboot process, the device performs the following operations:

a.     Resets all of its chips.

b.     Uses the BootWare to verify the startup software package, decompress the package, and load the images.

c.     Initializes the system.

·     Power off and then power on the device. This method might cause data loss, and is the least-preferred method.

Using the CLI, you can reboot the device from a remote host.

Restrictions and guidelines for device reboot

A device reboot might result in a service outage.

For data security, the device does not reboot while it is performing file operations.

Rebooting devices immediately at the CLI

Prerequisites

Perform the following steps in any view:

1.     Verify that the next-startup configuration file is correctly specified.

display startup

For more information about the display startup command, see Fundamentals Command Reference.

2.     Verify that the startup image files are correctly specified.

display boot-loader

If one main startup image file is damaged or does not exist, you must specify another main startup image file before rebooting the device.

For more information about the display boot-loader command, see Fundamentals Command Reference.

3.     Save the running configuration to the next-startup configuration file.

save

To avoid configuration loss, save the running configuration before a reboot.

For more information about the save command, see Fundamentals Command Reference.

Procedure

To reboot the device immediately at the CLI, execute one of the following commands in user view:

reboot [ slot slot-number ] [ force ]

Scheduling a device reboot

Restrictions and guidelines

The device supports only one device reboot schedule. If you execute the scheduler reboot command multiple times, the most recent configuration takes effect.

Procedure

To schedule a reboot, execute one of the following commands in user view:

·     scheduler reboot at time [ date ]

·     scheduler reboot delay time

By default, no device reboot time is specified.

Restoring the factory-default configuration

About this task

If you want to use the device in a different scenario or you cannot troubleshoot the device by using other methods, use this task to restore the factory-default configuration.

This task does not delete license files.

Restrictions and guidelines

This task is disruptive.

Procedure

1.     Execute the following command in user view to restore the factory-default configuration for the device:

restore factory-default

2.     Reboot the device.

reboot

When the command prompts you to choose whether to save the running configuration, enter N. If you choose to save the running configuration, the device loads the saved configuration at startup.

Display and maintenance commands for device management configuration

Execute display commands in any view. Execute the reset scheduler logfile command in user view. Execute the reset version-update-record command in system view.

 

Task

Command

Display device alarm information.

display alarm [ slot slot-number ]

Display the system time, date, time zone, and daylight saving time.

display clock

Display the copyright statement.

display copyright

Display CPU usage statistics.

display cpu-usage [ summary ] [ slot slot-number [ cpu cpu-number [ core { core-number| all } ] ] ]

display cpu-usage [ control-plane ] [ summary ] [ slot slot-number [ cpu cpu-number ]

Display CPU usage monitoring settings.

display cpu-usage configuration [ slot slot-number [ cpu cpu-number ] ]

Display the historical CPU usage statistics in a coordinate system.

display cpu-usage history [ job job-id ] [ slot slot-number [ cpu cpu-number ] ]

Display device information.

display device [ flash | usb ] [ slot slot-number | verbose ]

Display electronic label information for the device.

display device manuinfo [ slot slot-number ]

Display electronic label information for the backplane.

display device manuinfo chassis-only

Display electronic label information for a fan tray.

display device manuinfo fan fan-id

Display electronic label information for a power supply.

display device manuinfo power power-id

Display or save operating information for features and hardware modules.

display diagnostic-information [ hardware | infrastructure | l2 | l3 | service ] [ key-info ] [ filename ]

Display device temperature information.

display environment [ slot slot-number ]

Display fan tray operating status information.

display fan [ fan-id ]

Display hardware failure detection and fix information.

display hardware-failure-detection

Display hardware resource operating mode information.

display hardware-resource [ tcam ]

Display CPU and memory usage.

display health [ slot slot-number [ cpu cpu-number ] ]

Display memory usage statistics.

display memory [ summary ] [ slot slot-number [ cpu cpu-number ] ]

Display memory alarm thresholds and statistics.

display memory-threshold [ slot slot-number [ cpu cpu-number ] ]

Display power supply information.

display power [ power-id | verbose ]

Display job configuration information.

display scheduler job [ job-name ]

Display job execution log information.

display scheduler logfile

Display the automatic reboot schedule.

display scheduler reboot

Display schedule information.

display scheduler schedule [ schedule-name ]

Display system stability and status information.

display system stable state [ summary ]

Display system working mode information.

display system-working-mode

Display transceiver alarms.

display transceiver alarm interface [ interface-type interface-number ]

Display the current values of the digital diagnosis parameters on transceiver modules.

display transceiver diagnosis interface [ interface-type interface-number ]

Display the key parameters of transceiver modules.

display transceiver interface [ interface-type interface-number ]

Display ITU channel information for transceiver modules.

display transceiver itu-channel interface [ interface-type interface-number [ supported-channel ] ]

Display electronic label information for transceiver modules.

display transceiver manuinfo interface [ interface-type interface-number ]

Display system version information.

display version

Display startup software image upgrade records.

display version-update-record

Clear job execution log information.

reset scheduler logfile

Clear startup software image upgrade records.

reset version-update-record

 

  • 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
新华三官网