Home » Dell Manuals » Hubs & Switches » Dell PowerConnect Brocade M6505 » Manual Viewer

Dell PowerConnect Brocade M6505 Brocade 7.1.0 Fabric Watch Administrator's Gui - Page 98

System monitoring using the sysMonitor command, Using the nosave command

View all Dell PowerConnect Brocade M6505 manuals

Add to My Manuals
Save this manual to your list of manuals

Page 98 highlights

8 System monitoring using the sysMonitor command System monitoring using the sysMonitor command Use the sysMonitor command to configure temperature and system resource settings at the chassis level. For detailed information about the sysMonitor command, refer to the Fabric OS Command Reference Manual. The following operations are supported by the sysMonitor command: • Configure thresholds for Fabric Watch event monitoring and reporting for the environment and resource classes. Environment thresholds enable temperature monitoring, and resource thresholds enable monitoring of flash memory. Configuration changes are saved persistently to non-volatile storage, but the changes do not take effect until you execute --apply. The --apply option allows you to toggle between default settings and your own saved custom configuration and to apply actions and thresholds separately. • Configure memory or CPU usage parameters on the switch or display memory or CPU usage. Configuration options include setting usage thresholds which, if exceeded, trigger a set of specified Fabric Watch alerts. You can set up the system monitor to poll at certain intervals and specify the number of retries required before Fabric Watch takes action. Configuring thresholds for CPU and memory does not follow the transaction model of the typical Fabric Watch command. The --apply and --cancel options are not valid in this context. When the system crosses any of the limits, SNMP, RASlog, e-mail (or all) messages are generated. Flash and temperature configuration are at the chassis level. To execute this command, you must have chassis-level permission in a virtual fabric (VF) environment. NOTE Spikes in memory and CPU utilization are normal during the firmware download process and you may see threshold warning messages while the process is running. After the firmware download process has completed, memory and CPU utilization should return to normal. System monitoring is disabled by default. You must run both the --config -mem and the --config -cpu commands to enable both memory and CPU system monitoring. Using the nosave command The nosave command prevents the configuration changes from being saved persistently. This option allows you to make and view changes without overwriting the saved configuration. CAUTION When you use --config with the --nosave option and the switch reboots, your changes are lost. 78 53-1002752-01 Fabric Watch Administrator's Guide

Section	Page
Contents	5
Tables	11
Figures	13
About This Document	15
In this chapter	15
How this document is organized	15
Supported hardware and software	16
Deprecated hardware platform support	16
What’s new in this document	16
New information	17
Changed information	17
Removed information	17
Document conventions	17
Text formatting	17
Notes, cautions, and warnings	18
Key terms	18
Additional information	19
Other industry resources	19
Getting technical help	19
Document feedback	20
Fabric Watch	21
In this chapter	21
Fabric health	21
Fabric Watch overview	22
Role-based access control	22
Fabric Watch licensing	22
Reasons to customize Fabric Watch settings	23
Event behavior configuration	23
Alert configuration	23
Time base configuration	24
Threshold and action configuration	24
Monitoring	24
Post-processing of messages	24
Class, area, and element hierarchy	25
Switch monitoring components	25
Fabric events monitoring	25
Performance monitoring	25
Security monitoring	26
SFP monitoring	26
Port monitoring	26
System resource monitoring	27
Switch policies	28
Logical switch support	28
Threshold monitoring using SNMP tables	28
MIB capability configuration parameters	29
Fabric Watch event settings	29
Fabric Watch notification types	29
E-mail alert	29
SNMP traps	30
RASlog (switch event)	30
Locked port log	31
Fabric Watch audit messages	31
Data values	31
Fabric Watch support in Access Gateway mode	32
Fabric Watch Thresholds	33
In this chapter	33
Threshold values	33
In-between buffer values	34
Threshold triggers	34
Above event trigger	35
Below event trigger	35
Audit and RASlog messages	35
Time bases	36
Time base set to none	36
Time base set to other than none	36
Fabric Watch alarm behavior	37
Fabric Watch Threshold Components	39
In this chapter	39
Fabric Watch classes, areas, and elements	39
Classes	39
Class areas	39
Elements	40
Fabric Watch Activation	43
In this chapter	43
Interfaces for activating Fabric Watch	43
Activating Fabric Watch using a Telnet session	43
Activating Fabric Watch using SNMP	44
Activating Fabric Watch using Web Tools	48
Fabric Watch Configuration	49
In this chapter	49
Fabric Watch configuration tasks	49
Setting Fabric Watch custom and default values	51
E-mail notification configuration	51
Showing e-mail configuration information	51
Disabling an e-mail alert	52
Enabling an e-mail alert	52
Sending a test e-mail message	53
Setting recipient e-mail address for e-mail alert	53
Setting the relay host IP address	53
Displaying the relay host configuration	54
Removing the relay host configuration	54
Notification configuration	54
Configuring alarm notifications	54
Fabric, Security, SFP, and Performance Monitoring	57
In this chapter	57
Fabric monitoring guidelines and default settings	57
Fabric class areas	57
Fabric monitoring setting guidelines	58
Fabric class default settings	59
Security monitoring guidelines and default settings	60
Security class areas	60
Security monitoring default settings	61
SFP monitoring guidelines and default settings	63
SFP class areas	63
SFP monitoring default settings	64
Performance monitoring guidelines and default settings	65
Performance Monitor class areas	65
Performance monitoring setting guidelines	65
Performance Monitor class default settings	65
thConfig command	66
thConfig command examples	68
16 Gbps and QSFP monitoring	68
Recommended settings for Fabric, SFP, Performance, Security classes	72
Port Monitoring	75
In this chapter	75
Port class areas	75
Port class guidelines and default settings	76
Physical port setting guidelines	77
Port class default settings	77
Port configuration	78
Custom port settings	78
Using the nosave command	79
portThConfig command procedures	79
Port type: physical port	79
E_Port subclass setting guidelines	81
E_Port class default settings	82
FOP_Port and FCU_Port subclass setting guidelines	84
FOP_Port and FCU_Port subclass default settings	85
VE_Port class default settings	88
Port type: E_Port, FOP_Port, or FCU_Port	88
Setting the port persistence time	89
Port fencing	89
Port fencing configuration	90
Port fencing configuration using BNA	91
Recommended port configuration settings	92
System Monitoring	95
In this chapter	95
Environment monitoring	95
Environment class area	95
Environment monitoring setting guidelines	96
Environment class default settings	96
Resource class settings	97
Resource class area	97
Resource class setting guidelines	97
Resource class default settings	97
System monitoring using the sysMonitor command	98
Using the nosave command	98
Examples of the sysMonitor command	99
Environment class settings	99
Resource class settings	99
CPU and memory	100
Examples of the CPU and memory commands	100
Recommended environment and resource monitoring settings	101
Switch monitoring	101
Switch status policy planning	102
FRU monitoring	104
FRU class areas	104
Configuring FRUs	104
Specifying triggers for FRU alarms	105
Recommended FRU settings	106
Fabric Watch Configuration Using Web Tools	107
In this chapter	107
Fabric Watch Configuration Using Web Tools	107
Opening the Fabric Watch window	107
System Monitoring using Web Tools	108
Fabric Watch threshold configuration using Web Tools	109
Configuring alarms for FRUs using Web Tools	112
Configuring alarm filters using Web Tools	112
Fabric Watch alarm information	113
E-mail notification using Web Tools	114
Fabric Watch Reports	117
In this chapter	117
Fabric Watch reports	117
Switch Availability Monitor report	118
Generating a Switch Availability Monitor report	118
Switch Health report	119
Generating a Switch Health report	119
Switch Status Policy report	120
Generating a Switch Status Policy report	120
Port Detail report	121
Generating a Port Detail report	121

Match case Limit results 1 per page

53-1002752-01

Fabric Watch Administrator’s Guide

System monitoring using the sysMonitor command

Use the

sysMonitor

command to configure temperature and system resource settings at the

chassis level. For detailed information about the

sysMonitor

command, refer to the

Fabric OS

Command Reference Manual

The following operations are supported by the

sysMonitor

command:

•

Configure thresholds for Fabric Watch event monitoring and reporting for the environment and

resource classes. Environment thresholds enable temperature monitoring, and resource

thresholds enable monitoring of flash memory.

Configuration changes are saved persistently to non-volatile storage, but the changes do not

take effect until you execute --

apply

. The --

apply

option allows you to toggle between default

settings and your own saved custom configuration and to apply actions and thresholds

separately.

•

Configure memory or CPU usage parameters on the switch or display memory or CPU usage.

Configuration options include setting usage thresholds which, if exceeded, trigger a set of

specified Fabric Watch alerts. You can set up the system monitor to poll at certain intervals and

specify the number of retries required before Fabric Watch takes action. Configuring

thresholds for CPU and memory does not follow the transaction model of the typical Fabric

Watch command. The --

apply

and --

cancel

options are not valid in this context.

When the system crosses any of the limits, SNMP, RASlog, e-mail (or all) messages are generated.

Flash and temperature configuration are at the chassis level. To execute this command, you must

have chassis-level permission in a virtual fabric (VF) environment.

NOTE

Spikes in memory and CPU utilization are normal during the firmware download process and you

may see threshold warning messages while the process is running. After the firmware download

process has completed, memory and CPU utilization should return to normal.

System monitoring is disabled by default. You must run both the

--config -mem

and the

--config -cpu

commands to enable both memory and CPU system monitoring.

Using the nosave command

The

nosave

command prevents the configuration changes from being saved persistently. This

option allows you to make and view changes without overwriting the saved configuration.

CAUTION

When you use --config with the --nosave option and the switch reboots, your changes are lost.