BLADE OS™ Application Guide HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Version 5.1 Advanced Functionality Software
Table Of Contents
- Contents
- Figures
- Tables
- Preface
- Part 1: Basic Switching
- Accessing the Switch
- The Management Network
- Local Management Using the Console Port
- The Command Line Interface
- Remote Management Access
- Client IP Address Agents
- Securing Access to the Switch
- Setting Allowable Source IP Address Ranges
- RADIUS Authentication and Authorization
- TACACS+ Authentication
- LDAP Authentication and Authorization
- Secure Shell and Secure Copy
- Configuring SSH/SCP Features on the Switch
- Configuring the SCP Administrator Password
- Using SSH and SCP Client Commands
- SSH and SCP Encryption of Management Messages
- Generating RSA Host and Server Keys for SSH Access
- SSH/SCP Integration with Radius Authentication
- SSH/SCP Integration with TACACS+ Authentication
- End User Access Control
- Ports and Trunking
- Port-Based Network Access Control
- VLANs
- Spanning Tree Protocol
- RSTP and MSTP
- Link Layer Discovery Protocol
- Quality of Service
- Accessing the Switch
- Part 2: IP Routing
- Basic IP Routing
- Routing Information Protocol
- IGMP
- OSPF
- OSPF Overview
- OSPF Implementation in BLADE OS
- OSPF Configuration Examples
- Remote Monitoring
- Part 3: High Availability Fundamentals
- High Availability
- Layer 2 Failover
- Server Link Failure Detection
- VRRP Overview
- Failover Methods
- BLADE OS Extensions to VRRP
- Virtual Router Deployment Considerations
- High Availability Configurations
- High Availability
- Part 4: Appendices
- Index
BLADE OS 5.1 Application Guide
BMD00113, September 2009 Chapter 13: Remote Monitoring 219
RMON Group 2—History
The RMON History Group allows you to sample and archive Ethernet statistics for a specific
interface during a specific time interval.
Note – RMON port statistics must be enabled for the port before an RMON history group can
monitor the port.
Data is stored in buckets, which store data gathered during discreet sampling intervals. At each
configured interval, the history instance takes a sample of the current Ethernet statistics, and places
them into a bucket. History data buckets reside in dynamic memory. When the switch is re-booted,
the buckets are emptied.
Requested buckets (/cfg/rmon/hist <x>/rbnum) are the number of buckets, or data slots,
requested by the user for each History Group. Granted buckets
(/info/rmon/hist <x>/gbnum) are the number of buckets granted by the system, based on
the amount of system memory available. The system grants a maximum of 50 buckets.
Use an SNMP browser to view History samples.
History MIB Objects
The type of data that can be sampled must be of an ifIndex object type, as described in RFC1213
and RFC1573. The most common data type for the history sample is as follows:
1.3.6.1.2.1.2.2.1.1.x -mgmt.interfaces.ifTable.ifIndex.interface
The last digit (x) represents the interface on which to monitor, which corresponds to the port
number. History sampling is done per port, by utilizing the interface number to specify the port
number.
RMON History Example
This example configuration creates an RMON History Group to monitor port 20. It takes a data
sample every two minutes, and places the data into one of the 30 requested buckets. After 30
samples are gathered, the new samples overwrite the previous samples, beginning with the first
bucket.