HP 5500 Ei 5500 Si Switch Series Configuration Guide
Have a look at the manual HP 5500 Ei 5500 Si Switch Series Configuration Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 1114 HP manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
![Page 2366
65
Step Command Remarks
2. Configure a target host. snmp-agent
target-host trap
address udp-domain { ip-address |
ipv6 ipv6-address } [ udp-port
port-number ] [ dscp dscp-value ]
[ vpn-instance vpn-instance-name ]
params securityname
security-string [ v1 | v2c | v3
[ authentication | privacy ] ] If the trap destination is a host, the
ip-address
argument must be the IP
address of the host.
Only the HP 5500 EI switches
support the vpn-instance keyword.
3. Configure...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2365.png "Page 2366
65
Step Command Remarks
2. Configure a target host. snmp-agent
target-host trap
address udp-domain { ip-address |
ipv6 ipv6-address } [ udp-port
port-number ] [ dscp dscp-value ]
[ vpn-instance vpn-instance-name ]
params securityname
security-string [ v1 | v2c | v3
[ authentication | privacy ] ] If the trap destination is a host, the
ip-address
argument must be the IP
address of the host.
Only the HP 5500 EI switches
support the vpn-instance keyword.
3. Configure...")
![Page 2367
66
Task Command Remarks
Display basic information about
the trap queue. display snmp-agent trap queue
[ | { begin |
exclude | include } regular-expression ] Available in any view
Display the modules that can send
traps and their trap status (enable
or disable). display snmp-agent trap-list
[ | { begin |
exclude | include } regular-expression ] Available in any view
Display SNMPv3 user information. display snmp-agent usm-user
[ engineid
engineid | username user-name | group...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2366.png "Page 2367
66
Task Command Remarks
Display basic information about
the trap queue. display snmp-agent trap queue
[ | { begin |
exclude | include } regular-expression ] Available in any view
Display the modules that can send
traps and their trap status (enable
or disable). display snmp-agent trap-list
[ | { begin |
exclude | include } regular-expression ] Available in any view
Display SNMPv3 user information. display snmp-agent usm-user
[ engineid
engineid | username user-name | group...")
![Page 2368
67
# Enable SNMP traps, set the NMS at 1.1.1.2 as an SNMP trap destination, and use public as the
community name. (To make sure the NMS can receive traps, specify the same SNMP version in the
snmp-agent target-host command as is configured on the NMS.)
[Agent] snmp-agent trap enable
[Agent] snmp-agent target-host trap address udp-domain 1.1.1.2 params securityname
public v1
[Agent] quit
2. Configure the SNMP NMS:
# Configure the SNMP version for the NMS as v1 or v2c, create a read-only...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2367.png "Page 2368
67
# Enable SNMP traps, set the NMS at 1.1.1.2 as an SNMP trap destination, and use public as the
community name. (To make sure the NMS can receive traps, specify the same SNMP version in the
snmp-agent target-host command as is configured on the NMS.)
[Agent] snmp-agent trap enable
[Agent] snmp-agent target-host trap address udp-domain 1.1.1.2 params securityname
public v1
[Agent] quit
2. Configure the SNMP NMS:
# Configure the SNMP version for the NMS as v1 or v2c, create a read-only...")
![Page 2369
68
Figure 26 Network diagram
Configuration procedure
1. Configure the agent:
# Configure the IP address of the agent and make sure the agent and the NMS can reach each
other. (Details not shown.)
# Assign the NMS read and write access to the objects under the snmp node (OID
1.3.6.1.2.1.11), and deny its access to any other MIB object.
system-view
[Agent] undo snmp-agent mib-view ViewDefault
[Agent] snmp-agent mib-view included test snmp
[Agent] snmp-agent group v3 managev3group...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2368.png "Page 2369
68
Figure 26 Network diagram
Configuration procedure
1. Configure the agent:
# Configure the IP address of the agent and make sure the agent and the NMS can reach each
other. (Details not shown.)
# Assign the NMS read and write access to the objects under the snmp node (OID
1.3.6.1.2.1.11), and deny its access to any other MIB object.
system-view
[Agent] undo snmp-agent mib-view ViewDefault
[Agent] snmp-agent mib-view included test snmp
[Agent] snmp-agent group v3 managev3group...")
![Page 2371
70
# Enable displaying log messages on the configuration terminal. (This function is enabled by default.
Skip this step if you are using the default.)
terminal monitor
terminal logging
# Enable the information center to output system info rmation with severity level equal to or higher than
informational to the console port.
system-view
[Agent] info-center source snmp channel console log level informational \
# Enable logging GET and SET operations.
[Agent] snmp-agent log all
# Verify the...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2370.png "Page 2371
70
# Enable displaying log messages on the configuration terminal. (This function is enabled by default.
Skip this step if you are using the default.)
terminal monitor
terminal logging
# Enable the information center to output system info rmation with severity level equal to or higher than
informational to the console port.
system-view
[Agent] info-center source snmp channel console log level informational \
# Enable logging GET and SET operations.
[Agent] snmp-agent log all
# Verify the...")
![Page 2376
75
Step Command Remarks
3. Create an entry in the
alarm table or private
alarm table.
• Create an entry in the alarm table:
rmon alarm entry -number alarm -variable
sampling -interval { absolute | delta }
rising-threshold threshold -value1 event -entry1
falling-threshold threshold -value2 event -entry2
[ owner text ]
• Create an entry in the private alarm table:
rmon prialarm entry-number prialarm-formula
prialarm-des sampling-interval { absolute |
changeratio | delta }...](http://img.usermanuals.tech/thumb/36/58909/w64_hp-5500-ei-5500-si-switch-series-configuration-guide-2375.png "Page 2376
75
Step Command Remarks
3. Create an entry in the
alarm table or private
alarm table.
• Create an entry in the alarm table:
rmon alarm entry -number alarm -variable
sampling -interval { absolute | delta }
rising-threshold threshold -value1 event -entry1
falling-threshold threshold -value2 event -entry2
[ owner text ]
• Create an entry in the private alarm table:
rmon prialarm entry-number prialarm-formula
prialarm-des sampling-interval { absolute |
changeratio | delta }...")
70 # Enable displaying log messages on the configuration terminal. (This function is enabled by default. Skip this step if you are using the default.) terminal monitor terminal logging # Enable the information center to output system info rmation with severity level equal to or higher than informational to the console port. system-view [Agent] info-center source snmp channel console log level informational \ # Enable logging GET and SET operations. [Agent] snmp-agent log all # Verify the configuration: Use the NMS to get a MIB variable from the agent. The following is a sample log message displayed on the configuration terminal: %Jan 1 02:49:40:566 2011 Sysname SNMP/6/GET: seqNO = srcIP = op = node = value= Use the NMS to set a MIB variable on the agent. Th e following is a sample log message displayed on the configuration terminal: %Jan 1 02:59:42:576 2011 Sysname SNMP/6/SET: seqNO = srcIP = op = errorIndex = errorStatus = node = value = Table 6 SNMP log message field description Field Descri ption Jan 1 02:49:40:566 2011 Time when the SNMP log was generated. seqNO Serial number automatically assigned to the SNMP log, starting from 0. srcIP IP address of the NMS. op SNMP operation type (GET or SET). node MIB node name and OID of the node instance. erroIndex Error index, with 0 meaning no error. errorStatus Error status, with noError meaning no error. value Value set by the SET operation. This field is null for a GET operation. If the value is a character string that has invisible characters or characters beyond the ASCII range 0 to 127, the string is displayed in hexadecimal format, for example, value = [hex]. The information center can output system event messag es to several destinations, including the terminal and the log buffer. In this example, SNMP log messages are output to the terminal. To configure other message destinations, see Configuring the information center .
71 Configuring RMON This chapter describes how to configure RMON. Overview Remote Monitoring (RMON) is an enhancement to SNMP for remote device management and traffic monitoring. An RMON monitor, typically the RMON agent embedded in a network device, periodically or continuously collects traffic statistics for the network attached to a port, and when a statistic crosses a threshold, logs the crossing event and sends a trap to the management station. RMON uses SNMP traps to notify NMSs of exceptional conditions. RMON SNMP traps report various events, including traffic events such as broadcast tr affic threshold exceeded. In contrast, SNMP standard traps report device operating st atus changes such as link up, link down, and module failure. RMON enables proactive monitoring and management of remote network devices and subnets. The managed device can automatically send a trap when a statistic crosses an alarm threshold, and the NMS does not need to constantly poll MIB variables and compare the results. As a result, network traffic is reduced. Working mechanism RMON monitors typically take one of the following forms: • Dedicated RMON probes . NMSs can obtain management information from RMON probes directly and control network resources. In this approach, NMSs can obtain all RMON MIB information. • RMON agents embedded in network devices . NMSs exchange data with RMON agents by using basic SNMP operations to gather network management information. Because this approach is resource intensive, most RMON agent implementation s provide only four groups of MIB information: alarm, event, history, and statistics. HP devices provide the embedded RMON agent function. You can configure your device to collect and report traffic statistics, error statistics, and performance statistics. RMON groups Among the RFC 2819 defined RMON groups, HP implements the statistics group, history group, event group, and alarm group supported by the public MIB. HP also implements a private alarm group, which enhances the standard alarm group. Ethernet statistics group The statistics group defines that the system collects traf fic statistics on interfaces (only Ethernet interfaces are supported) and saves the statistics in the Ethernet statistics table (ethernetStatsTable). The interface traffic statistics include network collisions, CRC alig nment errors, undersize/oversize packets, broadcasts, multicasts, bytes received, and packets received. After you create a statistics entry for an interface, the statistics group starts to colle ct traffic statistics on the interface. The statistics in the Ethernet statistics table are cumulative sums.
72 History group The history group defines that the system periodically collects traffic statistics on interfaces and saves the statistics in the history record table (ethernetHistory Table). The statistics include bandwidth utilization, number of error packets, and total number of packets. The history statistics table record traffic statistics collected for each sampling interval. The sampling interval is user-configurable. Event group The event group defines event indexes and controls the generation and notifications of the events triggered by the alarms defined in the alarm group and the private alarm group. The events can be handled in one of the following ways: • Log—Logs event information (including event name an d description) in the event log table of the RMON MIB, so the management device can get the logs through the SNMP Get operation. • Trap —Sends a trap to notify an NMS of the event. • Log-Trap—Logs event information in the event log table and sends a trap to the NMS. • None —No action. Alarm group The RMON alarm group monitors alarm variables, such as the count of incoming packets (etherStatsPkts) on an interface. After you define an alarm entry, the system gets the value of the monitored alarm variable at the specified interval. If the value of the monitored variable is greater than or equal to the rising threshold, a rising event is triggered. If the value of the monitored variable is smaller than or equal to the falling threshold, a falling event is triggered. The event is then handled as defined in the event group. If an alarm entry crosses a threshold multiple times in succession, the RMON agent generates an alarm event only for the first crossing. For example, if the value of a sampled alarm variable crosses the rising threshold multiple times before it crosses the falling threshold, only the first crossing triggers a rising alarm event, as shown in Figure 28. Figure 28 Rising and falling alarm events
73 Private alarm group The private alarm group calculates the values of alarm variables and compares the results with the defined threshold for a more comprehensive alarming function. The system handles the private alarm entry (as defined by the user) in the following ways: • Periodically samples the prialarm variables defined in the prialarm formula. • Calculates the sampled values based on the prialarm formula. • Compares the result with the defined threshold an d generates an appropriate event if the threshold value is reached. If a private alarm entry crosses a threshold multiple times in succession, the RMON agent generates an alarm event only for the first crossing. For example, if the value of a sampled alarm variable crosses the rising threshold multiple times before it crosses the falling threshold, only the first crossing triggers a rising alarm event. If the count result of the private alar m group overpasses the same threshold multiple times, only the first one can cause an alarm event. In other words, the rising alarm and falling alarm are alternate. Configuring the RMON statistics function The RMON statistics function can be implemented by either the Ethernet statistics group or the history group, but the objects of the statistics are different, as follows: • A statistics object of the Ethernet statistics group is a variable defined in the Ethernet statistics table, and the recorded content is a cumulative sum of the variable from the time the statistics entry is created to the current time. For more information, see Configuring the RMON Ethernet statistics fu nction . • A statistics object of the history group is the vari able defined in the history record table, and the recorded content is a cumulative sum of the variable in each period. For more information, see Configuring the RMON history statistics function . Configuring the RMON Ethernet statistics function Step Command Remarks 1. Enter system view. system-view N/A 2. Enter Layer 2 Ethernet interface view or Layer 3 Ethernet interface view. interface interface-type interface-number You can configure an Ethernet port as a Layer 3 Ethernet port only on the HP 5500 EI switch. 3. Create an entry in the RMON statistics table. rmon statistics entry -number [ owner text ] N/A You can create one statistics entry per interface and up to 100 statistics entries on the device. When the number of statistics entries exceed s 100, you cannot add new entries. Configuring the RMON history statistics function Follow these guidelines when you configure the RMON history statistics function: • The entry-number for an RMON history control entry must be globally unique. If an entry number has been used on one interface, it cannot be used on another.
74
• You can configure multiple history control entries for one interface, but must make sure their entry
numbers and sampling intervals are different.
• On the HP 5500 SI switch, up to 100 histor y entries can be created. On the HP 5500 EI switch, up
to 1000 history entries can be created.
• You can successfully create a history control entry, even if the specified bucket size exceeds the
history table size supported by the device. However, the effective bucket size will be the actual value
supported by the device.
To configure the RMON history statistics function:
Step Command Remarks
1. Enter system view.
system-view N/A
2. Enter Layer 2 Ethernet
interface view or Layer 3
Ethernet interface view. interface
interface-type
interface-number You can configure an Ethernet port as
a Layer 3 Ethernet port only on the HP
5500 EI switch.
3. Create an entry in the
RMON history control
table. rmon history
entry -number buckets
number interval sampling -interval
[ owner text ] N/A
Configuring the RMON alarm function
Follow these guidelines when you configure the RMON alarm function:
• To send traps to the NMS when an alarm is trig gered, configure the SNMP agent as described in
Configuring SNMP be
fore configuring the RMON alarm function.
• If the alarm variable is a MIB variable defined in the history group or the Ethernet statistics group,
make sure the RMON Ethernet statistics function or the RMON history statistics function is
configured on the monitored Ethernet interface. Ot herwise, even if you can create the alarm entry,
no alarm event can be triggered.
• You cannot create a new event, alarm, or privat e alarm entry that has the same set of parameters
as an existing entry. For parameters to be compared for duplication, see Tabl e 7.
• A
fter the maximum number of entries is reached, no new entry can be created. For the table entry
limits, see Tabl e 7.
T
o configure the RMON alarm function:
Step Command Remarks
1. Enter system view.
system-view N/A
2.
Create an event entry in
the event table. rmon event
entry-number [ description string ] { log |
log-trap log-trapcommunity | none | trap
trap- community } [ owner text ] N/A
75
Step Command Remarks
3. Create an entry in the
alarm table or private
alarm table.
• Create an entry in the alarm table:
rmon alarm entry -number alarm -variable
sampling -interval { absolute | delta }
rising-threshold threshold -value1 event -entry1
falling-threshold threshold -value2 event -entry2
[ owner text ]
• Create an entry in the private alarm table:
rmon prialarm entry-number prialarm-formula
prialarm-des sampling-interval { absolute |
changeratio | delta } rising-threshold
threshold-value1 event-entry1 falling-threshold
threshold-value2 event-entry2 entrytype { forever |
cycle cycle -period } [ owner text ] Use at least one
command.
Table 7
RMON configuration restrictions
Entry Parameters to be compared Maximum number of
entries
Event Event description (
description string), event type ( log, trap ,
logtrap or none) and community name (trap-community or
log-trapcommunity ) 60
Alarm Alarm variable (
alarm-variable), sampling interval
(sampling-interval), sampling type ( absolute or delta), rising
threshold ( threshold-value1 ) and falling threshold
(threshold-value2 ) 60
Prialarm Alarm variable formula (
alarm-variable), sampling interval
(sampling-interval), sampling type ( absolute, changeratio or
delta ), rising threshold ( threshold-value1) and falling
threshold ( threshold-value2 ) 50
Displaying and maintaining RMON
Task Command Remarks
Display RMON statistics.
display rmon statistics
[ interface-type
interface-number ] [ | { begin | exclude |
include } regular-expression ] Available in any view
Display the RMON history
control entry and history
sampling information. display rmon history
[ interface-type
interface-number ] [ | { begin | exclude |
include } regular-expression ] Available in any view
Display RMON alarm
configuration. display rmon alarm
[ entry-number ] [ | { begin |
exclude | include } regular-expression ] Available in any view
Display RMON private alarm
configuration. display rmon prialarm
[ entry-number ] [ |
{ begin | exclude | include } regular-expression ]
Available in any view
Display RMON events
configuration. display rmon event
[ entry-number ] [ | { begin |
exclude | include } regular-expression ] Available in any view
Display log information for
event entries. display rmon eventlog
[ entry-number ] [ | { begin
| exclude | include } regular-expression ] Available in any view
76 Ethernet statistics group configuration example Network requirements Configure the RMON statistics group on the RMON agent in Figure 29 to gather cumulative traffic statistics for GigabitEthernet 1/0/1. Figure 29 Network diagram Configuration procedure # Configure the RMON statistics group on the RMON agent to gather statistics for GigabitEthernet 1/0/1. system-view [Sysname] interface gigabitethernet 1/0/1 [Sysname-GigabitEthernet1/0/1] rmon statistics 1 owner user1 # Display statistics collected by the RMON agent for GigabitEthernet 1/0/1. display rmon statistics gigabitethernet 1/0/1 EtherStatsEntry 1 owned by user1-rmon is VALID. Interface : GigabitEthernet1/0/1 etherStatsOctets : 21657 , etherStatsPkts : 307 etherStatsBroadcastPkts : 56 , etherStatsMulticastPkts : 34 etherStatsUndersizePkts : 0 , etherStatsOversizePkts : 0 etherStatsFragments : 0 , etherStatsJabbers : 0 etherStatsCRCAlignErrors : 0 , etherStatsCollisions : 0 etherStatsDropEvents (insufficient resources): 0 Packets received according to length: 64 : 235 , 65-127 : 67 , 128-255 : 4 256-511: 1 , 512-1023: 0 , 1024-1518: 0 # On the configuration terminal, get the traffic statistics through SNMP. (Details not shown.) History group configuration example Network requirements Configure the RMON history group on the RMON agent in Figure 30 to gather periodical traffic statistics for GigabitEthernet 1/0/1 every one minute.
77
Figure 30 Network diagram
Configuration procedure
# Configure the RMON history group on the RMON agent to gather traffic statistics every one minute for
GigabitEthernet 1/0/1. Retain up to eight records for the interface in the history statistics table.
system-view
[Sysname] interface gigabitethernet 1/0/1
[Sysname-GigabitEthernet1/0/1] rmon history 1 buckets 8 interval 60 owne\
r user1
# Display the history data collected for GigabitEthernet 1/0/1.
[Sysname-GigabitEthernet1/0/1] display rmon history
HistoryControlEntry 2 owned by null is VALID
Samples interface : GigabitEthernet1/0/1
Sampling interval : 10(sec) with 8 buckets max
Sampled values of record 1 :
dropevents : 0 , octets : 834
packets : 8 , broadcast packets : 1
multicast packets : 6 , CRC alignment errors : 0
undersize packets : 0 , oversize packets : 0
fragments : 0 , jabbers : 0
collisions : 0 , utilization : 0
Sampled values of record 2 :
dropevents : 0 , octets : 962
packets : 10 , broadcast packets : 3
multicast packets : 6 , CRC alignment errors : 0
undersize packets : 0 , oversize packets : 0
fragments : 0 , jabbers : 0
collisions : 0 , utilization : 0
Sampled values of record 3 :
dropevents : 0 , octets : 830
packets : 8 , broadcast packets : 0
multicast packets : 6 , CRC alignment errors : 0
undersize packets : 0 , oversize packets : 0
fragments : 0 , jabbers : 0
collisions : 0 , utilization : 0
Sampled values of record 4 :
dropevents : 0 , octets : 933
packets : 8 , broadcast packets : 0
multicast packets : 7 , CRC alignment errors : 0
undersize packets : 0 , oversize packets : 0
78
fragments : 0 , jabbers : 0
collisions : 0 , utilization : 0
Sampled values of record 5 :
dropevents : 0 , octets : 898
packets : 9 , broadcast packets : 2
multicast packets : 6 , CRC alignment errors : 0
undersize packets : 0 , oversize packets : 0
fragments : 0 , jabbers : 0
collisions : 0 , utilization : 0
Sampled values of record 6 :
dropevents : 0 , octets : 898
packets : 9 , broadcast packets : 2
multicast packets : 6 , CRC alignment errors : 0
undersize packets : 0 , oversize packets : 0
fragments : 0 , jabbers : 0
collisions : 0 , utilization : 0
Sampled values of record 7 :
dropevents : 0 , octets : 766
packets : 7 , broadcast packets : 0
multicast packets : 6 , CRC alignment errors : 0
undersize packets : 0 , oversize packets : 0
fragments : 0 , jabbers : 0
collisions : 0 , utilization : 0
Sampled values of record 8 :
dropevents : 0 , octets : 1154
packets : 13 , broadcast packets : 1
multicast packets : 6 , CRC alignment errors : 0
undersize packets : 0 , oversize packets : 0
fragments : 0 , jabbers : 0
collisions : 0 , utilization : 0
# On the configuration terminal, get the traffic statistics through SNMP. (Details not shown.)
Alarm group configuration example
Network requirements
Configure the RMON alarm group on the RMON agent in Figure 31 to send alarms in traps when the
five-second incoming traffic statistic on GigabitEthernet 1/0/1 crosses the rising threshold or drops
below the falling threshold.
79 Figure 31 Network diagram Configuration procedure # Configure the SNMP agent with the same SNMP settings as the NMS at 1.1.1.2. This example uses SNMPv1, read community public, and write community private. system-view [Sysname] snmp-agent [Sysname] snmp-agent community read public [Sysname] snmp-agent community write private [Sysname] snmp-agent sys-info version v1 [Sysname] snmp-agent trap enable [Sysname] snmp-agent target-host trap address udp-domain 1.1.1.2 params \ securityname public # Configure the RMON statistics group to gather traffic statistics for GigabitEthernet 1/0/1. [Sysname] interface gigabitethernet 1/0/1 [Sysname-GigabitEthernet1/0/1] rmon statistics 1 owner user1 [Sysname-GigabitEthernet1/0/1] quit # Create an RMON event entry and an RMON alar m entry so the RMON agent sends traps when the delta sampling value of node 1.3.6.1.2.1.16.1.1.1.4.1 exceeds 100 or drops below 50. [Sysname] rmon event 1 trap public owner user1 [Sysname] rmon alarm 1 1.3.6.1.2.1.16.1.1.1.4.1 5 delta rising-threshold\ 100 1 falling-threshold 50 1 # Display the RMON alarm entry configuration. display rmon alarm 1 AlarmEntry 1 owned by null is Valid. Samples type : delta Variable formula : 1.3.6.1.2.1.16.1.1.1.4.1 Sampling interval : 5(sec) Rising threshold : 100(linked with event 1) Falling threshold : 50(linked with event 2) When startup enables : risingOrFallingAlarm Latest value : 0 # Display statistics for GigabitEthernet 1/0/1. display rmon statistics gigabitethernet 1/0/1 EtherStatsEntry 1 owned by user1-rmon is VALID. Interface : GigabitEthernet1/0/1 etherStatsOctets : 57329 , etherStatsPkts : 455 etherStatsBroadcastPkts : 53 , etherStatsMulticastPkts : 353