Aruba Networking Comware 5960 Switch Series System Management Configuration Guide

Brand: Aruba

Model: Networking Comware 5960 Switch Series System Management

Type: Configuration Guide

This manual is also suitable for

HPE Networking Comware 5960 Switch Series

System Management Configuration Guide

Software

version: Release 9126P01 and later

Document version: 6W100-20230428

The information contained herein is subject to change without notice. The only warranties for Hewlett Packard

Enterprise products and services are set forth in the express warranty statements accompanying such

products and services. Nothing herein should be construed as constituting an additional warranty. Hewlett

Packard Enterprise shall not be liable for technical or editorial errors or omissions contained herein.

Confidential computer software. Valid license from Hewlett Packard Enterprise required for possession, use, or

copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software

Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s

standard commercial license.

Links to third-party websites take you outside the Hewlett Packard Enterprise website. Hewlett Packard

Enterprise has no control over and is not responsible for information outside the Hewlett Packard Enterprise

website.

Acknowledgments

Intel®, Itanium®, Pentium®, Intel Inside®, and the Intel Inside logo are trademarks of Intel Corporation in the

United States and other countries.

Microsoft® and Windows® are either registered trademarks or trademarks of Microsoft Corporation in the

United States and/or other countries.

Adobe® and Acrobat® are trademarks of Adobe Systems Incorporated.

Java and Oracle are registered trademarks of Oracle and/or its affiliates.

UNIX® is a registered trademark of The Open Group.

Contents

Performing basic device management ··························································· 4

Configuring the device name ····························································································································· 4

Configuring the system time······························································································································· 4

About the system time ································································································································ 4

Restrictions and guidelines for configuring the system time ······································································ 4

System time configuration tasks at a glance ······························································································ 4

Setting the system time at the CLI ············································································································· 5

Obtaining the UTC time through a time protocol ························································································ 5

Setting the time zone ································································································································· 5

Setting the daylight saving time ················································································································· 6

Displaying system time information············································································································ 6

Setting the system operating mode···················································································································· 6

Displaying copyright information ························································································································ 7

Enabling copyright statement display ········································································································· 7

Displaying detailed copyright information··································································································· 7

Configuring banners ··········································································································································· 7

Rebooting the device ········································································································································· 9

About device reboot ··································································································································· 9

Restrictions and guidelines for device reboot ···························································································· 9

Rebooting the device immediately at the CLI····························································································· 9

Restoring the factory-default configuration ······································································································ 10

Verifying device stability ··································································································································· 10

Hardening the device ··················································································· 11

Device hardening tasks at a glance ················································································································· 11

Disabling password recovery capability ··········································································································· 11

Disabling USB interfaces ································································································································· 11

Managing hardware resources ···································································· 12

Hardware resource management tasks at a glance························································································· 12

Monitoring CPU usage ····································································································································· 13

Configuring CPU usage alarm ················································································································· 13

Configuring CPU usage tracking ·············································································································· 14

Displaying CPU usage monitoring information························································································· 14

Monitoring memory usage································································································································ 15

Setting memory alarm thresholds ············································································································ 15

Displaying memory usage monitoring information ··················································································· 16

Monitoring resource usage······························································································································· 17

Configuring resource monitoring ·············································································································· 17

Displaying resource monitoring information ····························································································· 18

Monitoring device temperature························································································································· 18

Setting the temperature alarm thresholds ································································································ 18

Displaying device temperature information ······························································································ 19

Monitoring fans················································································································································· 19

Displaying fan information ························································································································ 19

Setting the port status detection timer ············································································································· 19

Verifying and diagnosing transceiver modules ································································································ 19

Verifying transceiver modules ·················································································································· 19

Diagnosing transceiver modules ·············································································································· 20

Managing 400-GE transceiver modules ··········································································································· 20

Enabling lanes on 400-GE transceiver modules ······················································································ 20

Setting the frequency for a transceiver optical channel ··········································································· 21

Setting the transmit power for a transceiver optical channel···································································· 21

Setting a power mode for 400-GE transceiver modules ·········································································· 22

Configuring pre-cursor, post-cursor, and amplitude ················································································· 22

Displaying 400-GE transceiver module information ················································································· 23

Resetting 400-GE transceiver modules ··································································································· 23

Specifying a diagnostic selector for a transceiver module ······················································· 23

Enabling loopback testing on a transceiver module lane ················································································· 24

Specifying the signal mode and PRBS pattern for a transceiver module lane ················································· 24

Configuring transceiver monitoring ·················································································································· 25

Displaying device hardware information ·········································································································· 25

Displaying device hardware electronic label information ················································································· 25

Displaying device hardware alarm information ································································································ 25

Monitoring and maintaining processes ························································· 26

About monitoring and maintaining processes ·································································································· 26

Process monitoring and maintenance tasks at a glance ·················································································· 26

Monitoring and maintaining user processes and kernel threads ······································································ 26

About monitoring and maintaining user processes and kernel threads ··················································· 26

Displaying memory usage of processes ·································································································· 27

Displaying CPU usage of processes ········································································································ 27

Monitoring process status ························································································································ 27

Monitoring and maintaining user processes ···································································································· 27

About monitoring and maintaining user processes ·················································································· 27

Configuring core dump ····························································································································· 27

Locating user process memory usage exceptions ··················································································· 28

Displaying log information for user processes ························································································· 28

Displaying context information for process exceptions ············································································ 28

Clearing context information for process exceptions ··············································································· 28

Monitoring and maintaining kernel threads ······································································································ 29

About monitoring and maintaining kernel threads ···················································································· 29

Detecting kernel thread deadloops ·········································································································· 29

Detecting kernel thread starvation ··········································································································· 30

Displaying kernel thread exception information ······················································································· 30

Displaying kernel thread reboot information····························································································· 31

Clearing kernel thread exception information ··························································································· 31

Clearing kernel thread reboot information ································································································ 31

Configuring the information center ······························································· 32

About the information center ···························································································································· 32

Log types ·················································································································································· 32

Log levels ················································································································································· 32

Log destinations ······································································································································· 33

Default output rules for logs ····················································································································· 33

Default output rules for diagnostic logs ···································································································· 33

Default output rules for security logs ········································································································ 33

Default output rules for hidden logs ········································································································· 34

Default output rules for trace logs ············································································································ 34

Log formats and field descriptions ··········································································································· 34

Information center tasks at a glance ················································································································ 37

Managing standard system logs ·············································································································· 37

Managing hidden logs ······························································································································ 38

Managing security logs ···························································································································· 38

Managing diagnostic logs ························································································································· 38

Managing trace logs ································································································································· 39

Enabling the information center ······················································································································· 39

Outputting logs to various destinations ············································································································ 39

Displaying the log output filters ················································································································ 39

Outputting logs to the console·················································································································· 39

Outputting logs to the monitor terminal ···································································································· 40

Outputting logs to log hosts ······················································································································ 41

Outputting logs to the log buffer ··············································································································· 41

Saving logs to the log file ························································································································· 42

Setting the minimum storage period ················································································································ 43

About setting the minimum storage period······························································································· 43

Procedure ················································································································································· 44

Enabling synchronous information output ········································································································ 44

Configuring log suppression····························································································································· 44

iii

Enabling duplicate log suppression·········································································································· 44

Configuring log suppression for a module ································································································ 46

Disabling an interface from generating link up or link down logs ····························································· 47

Enabling SNMP notifications for system logs··································································································· 47

Configuring security logs ·································································································································· 48

Saving security logs to the security log file ······························································································ 48

Managing the security log file ··················································································································· 48

Displaying security log information··········································································································· 49

Configuring diagnostic logs ······························································································································ 49

Saving diagnostic logs to the diagnostic log file ······················································································· 49

Displaying diagnostic log file information ································································································· 50

Setting the maximum size of the trace log file·································································································· 50

Displaying the information center configuration ······························································································· 51

Displaying and clearing log buffer information ································································································· 51

Displaying log file information ·························································································································· 51

Information center configuration examples ······································································································ 51

Example: Outputting logs to the console·································································································· 51

Example: Outputting logs to a UNIX log host ··························································································· 52

Example: Outputting logs to a Linux log host ··························································································· 53

Document conventions and icons ································································ 55

Conventions ····················································································································································· 55

Network topology icons ···································································································································· 56

Support and other resources ······································································· 57

Accessing Hewlett Packard Enterprise Support······························································································· 57

Accessing updates ··········································································································································· 57

Websites ·················································································································································· 58

Customer self repair ································································································································· 58

Remote support ········································································································································ 58

Documentation feedback ························································································································· 58

Index ············································································································ 60

Performing basic device management

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 HPE.

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 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

The system time configured by using the clock datetime command takes effect immediately.

The time zone or daylight saving time, whether configured or not, are not taken into account.

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.

You can configure the device to use both methods to obtain the system time. For time consistency,

however, configure the device to use only one of the methods to obtain the system time. If you

configure the device to use both methods, the device uses the manually set system time or the

periodically obtained UTC time, whichever is obtained later.

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 a time protocol

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.

4. (Optional.) Displaying system time information

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 the NTP time source.

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 system time is the factory-default time.

CAUTION:

This command changes the

system time, which affects execution of system time-related

features

(for example, scheduled tasks) and collaborative operations of the device with other

devices (for example, log reporting and statistics collection).

Before executing this command,

make sure you fully understand its impact on your live network.

Obtaining the UTC time through a time protocol

1. Enter system view.

system-view

2. Specify the system time source.

clock protocol { ntp }

By default, the device uses the NTP time source.

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.

Displaying system time information

To display system time information, execute the following command in any view:

display clock

This command displays the system time, date, time zone, and daylight saving time.

Setting the system operating mode

About this task

The device can operate in one of the following modes:

•

advance—Advanced mode.

•

standard—Standard mode.

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{ advance | standard }

By default, the device operates in standard mode.

Displaying the system working mode

To display system working mode information, execute the following command in any view:

display system-working-mode

Displaying copyright information

Enabling copyright statement display

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 dial-in user quits user view. This is because the device automatically tries to

restart the user session.

Figure 1 shows the copyright statement.

If you disable displaying the copyright statement, the device does not display the copyright statement

in any situations.

Figure 1 Copyright statement at the login page

Procedure

1. Enter system view.

system-view

2. Enable copyright statement display.

By default, copyright statement display is enabled.

Displaying detailed copyright information

To display detailed copyright information, execute the following command in any view:

display copyright

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.

•

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

banner.

•

Shell banner—Appears for a user when the user accesses 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'.

Procedure

1. Enter system view.

system-view

2. Configure the legal banner.

header legal text

3. Configure the MOTD banner.

header motd text

4. Configure the login banner.

header login text

5. Configure the shell banner.

header shell text

Rebooting the device

About device reboot

The following device reboot methods are available:

•

Immediately reboot the device at the CLI.

This method allows you to reboot the device remotely.

•

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

least-preferred method.

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 the device 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 ]

CAUTION:

•

A device reboot might result in service interruption.

Before configuring this command, make sure

you fully understand its impact on your live network.

•

Use the force keyword to reboot the device only when the system is faulty or fails to start up

normally. A forced device reboots might cause file system damage. Before using the force

keyword to reboot the device, make sure you understand its impact.

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 .bin files, or reserved directories customized for a product.

Restrictions and guidelines

CAUTION:

This

feature will automatically restore the factory defaults for the device. Before us

ing this command,

make sure you fully understand its impact on your live network.

Procedure

Execute the following command in user view to restore the factory-default configuration for the

device:

restore factory-default

Verifying device stability

About this task

The device startup process takes some time. If the values of the status fields do not change to

Stable, use this feature to identify the devices that are not in Stable state.

Restrictions and guidelines

As a best practice, execute this command multiple times to identify whether the system is operating

stably.

Procedure

To display system stability and status information, execute the following command in any view:

display system stable state

Troubleshooting

If the system is not in stable state, you can use other commands to identify the faulty components.

For example:

•

Use the display device command to identify the device operating status.

•

Use the display system internal process state command in probe view to display

service operating status.

Hardening the device

Device hardening tasks at a glance

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

•

Disabling password recovery capability

•

Disabling USB interfaces

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

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.

Managing hardware resources

This chapter describes routine device hardware resource management tasks, including monitoring

CPU and memory usage, displaying power supply and fan operating status, and configuring basic

device operating parameters.

Hardware resource management tasks at a

glance

All hardware resource management tasks are optional. You can perform any of the tasks in any

order.

•

Monitoring CPU usage

 Configuring CPU usage alarm

 Configuring CPU usage tracking

 Displaying CPU usage monitoring information

•

Monitoring memory usage

 Setting memory alarm thresholds

 Displaying memory usage monitoring information

•

Monitoring resource usage

 Configuring resource monitoring

 Displaying resource monitoring information

•

Monitoring device temperature

 Setting the temperature alarm thresholds

 Displaying device temperature information

•

Monitoring fans

Displaying fan information

•

Setting the port status detection timer

•

Verifying and diagnosing transceiver modules

 Verifying transceiver modules

 Diagnosing transceiver modules

•

Managing 400-GE transceiver modules

 Enabling lanes on 400-GE transceiver modules

 Setting the frequency for a transceiver optical channel

 Setting the transmit power for a transceiver optical channel

 Setting a power mode for 400-GE transceiver modules

 Configuring pre-cursor, post-cursor, and amplitude

 Displaying 400-GE transceiver module information

 Resetting 400-GE transceiver modules

•

Specifying a diagnostic selector for a transceiver module

•

Enabling loopback testing on a transceiver module lane

•

Specifying the signal mode and PRBS pattern for a transceiver module lane

•

Configuring transceiver monitoring

•

Displaying device hardware information

•

Displaying device hardware electronic label information

•

Displaying device hardware alarm information

Monitoring CPU usage

Configuring CPU usage alarm

About this task

The device 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.

The device supports the following CPU usage thresholds:

•

Minor threshold—If the CPU usage increases to or above the minor threshold but is less than

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 about NETCONF and SNMP, see Network Management and Monitoring Configuration

Guide. For more information about information center, see "Configuring the information center."

Figure 2 CPU alarms and alarm-removed notifications

Procedure

1. Enter system view.

system-view

2. Set the CPU usage alarm thresholds.

monitor cpu-usage threshold severe-threshold [ minor-threshold

minor-threshold recovery-threshold recovery-threshold ] [ slot

slot-number [ cpu cpu-number ] ]

Severe CPU usage

alarm threshold

Severe alarm removed

Time

CPU usage

Minor CPU usage

alarm threshold

Entering minor

alarm state

Entering severe alarm state

CPU usage

recovery threshold

Minor alarm removed

By default, the CPU usage alarm threshold is 99%.

CAUTION:

you set the severe CPU usage alarm threshold to a too low value, the device will reach the

threshold easily. Normal service processing will be affected.

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.

Configuring CPU usage tracking

About this task

After you enable CPU usage tracking, the system samples CPU usage at intervals and saves

the samples to a buffer. You can use the display cpu-usage history command to view

the recent CPU usage.

Procedure

1. Enter system view.

system-view

2. 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.

3. Enable CPU usage tracking.

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

By default, CPU usage tracking is enabled.

Displaying CPU usage monitoring information

Perform display tasks in any view.

•

Display CPU usage monitoring settings.

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

•

Display the current CPU usage statistics.

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

cpu-number ] [ core { core-number | all } ] ]

•

Display the historical CPU usage statistics in a coordinate system.

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

cpu-number ] ]

Monitoring memory usage

Setting memory alarm thresholds

About this task

To ensure correct operation and improve memory efficiency, the system monitors the amount of free

memory space in real time. If the amount of free memory space reaches the minor, severe, or critical

alarm threshold, the system issues an alarm to affected service modules and processes.

You can use the display memory command to display memory usage information.

As shown in the following table and figure, the system supports the following free-memory

thresholds:

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

•

Normal state threshold.

•

Minor alarm threshold.

•

Severe alarm threshold.

•

Critical alarm threshold.

Table 1 Memory alarm notifications and memory alarm-removed notifications

Notification

Triggering condition

Remarks

Minor alarm notification The amount of free memory

space decreases to or 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 to or 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 to or 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 3 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 free-memory thresholds.

memory-threshold [ slot slot-number [ cpu cpu-number ] ] [ ratio ] minor

minor-value severe severe-value critical critical-value normal

normal-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.

Displaying memory usage monitoring information

Perform display tasks in any view.

•

Display memory usage information.

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

•

Display memory alarm thresholds and statistics.

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

Minor

Critical

Free memory space

Severe

Normal

Minor alarm-removed

Severe alarm-removed

Time

Minor

alarm

Severe alarm

Critical alarm

Critical alarm-removed

Monitoring resource usage

Configuring resource monitoring

About this task

The resource monitoring feature enables the device to monitor the available amounts of types of

resources, for example, the space for ARP entries. The device samples the available amounts

periodically and compares the samples with resource depletion thresholds to identify the resource

depletion status.

The device supports a minor resource depletion threshold and a severe resource depletion threshold

for each supported resource type.

•

If the available amount is equal to or less than the minor resource depletion threshold but

greater than the severe resource depletion threshold, the resource type is in minor alarm state.

•

If the available amount is equal to or less than the severe resource depletion threshold, the

resource type is in severe alarm state.

•

If the available amount increases above the minor resource depletion threshold, the resource

type is in recovered state.

When a resource type enters severe alarm state, the device issues a severe alarm. If the resource

type stays in severe alarm state, the device resends severe alarms periodically.

When a resource type enters minor alarm state, the device issues a minor alarm. If the resource type

stays in minor alarm state or changes from severe alarm state to minor alarm state, the device

identifies whether resending of minor resource depletion alarms is enabled. If the feature is disabled,

the device does not issue additional minor alarms. If the feature is enabled, the device resends minor

alarms periodically.

Resource depletion alarms 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 about NETCONF and SNMP, see Network Management and Monitoring Configuration

Guide. For more information about information center, see "Configuring the information center."

Figure 4 Resource depletion alarms and alarm-removed notifications

Procedure

1. Enter system view.

system-view

Severe alarm-removed

Severe resource

depletion threshold

Time

Available amount

Minor resource

depletion threshold

Entering

minor alarm

state

Entering severe

alarm state

Minor alarm-removed

2. Set resource depletion thresholds.

resource-monitor resource resource-name slot slot-number cpu

cpu-number by-percent minor-threshold minor-threshold

severe-threshold severe-threshold

The default varies by resource type. Use the display resource-monitor command to

display the resource depletion thresholds.

3. Specify destinations for resource depletion alarms.

resource-monitor output { netconf-event | snmp-notification | syslog }

By default, resource depletion alarms are sent to NETCONF, SNMP, and the information

center.

4. Enable resending of minor resource depletion alarms.

resource-monitor minor resend enable

By default, resending of minor resource depletion alarms is enabled.

Displaying resource monitoring information

To display resource monitoring information, execute the following command in any view:

display resource-monitor [ resource resource-name ] [ slot slot-number

[ cpu cpu-number ] ]

Monitoring device temperature

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.

Procedure

1. Enter system view.

system-view

2. Configure the temperature alarm thresholds.

temperature-limit slot slot-number hotspot 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.

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.

Page is loading ...

Aruba Networking Comware 5960 Switch Series System Management Configuration Guide

Brand: Aruba

Model: Networking Comware 5960 Switch Series System Management

Type: Configuration Guide

This manual is also suitable for

Download PDF

report

Aruba Networking Comware 5960 Switch Series System Management Configuration Guide

This manual is also suitable for

Aruba Networking Comware 5960 Switch Series System Management Configuration Guide

Related papers

Other documents