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
BMD00113, September 2009 253
APPENDIX A
Troubleshooting
BLADE OS provides two main methods for monitoring HP GbE2c Ethernet Blade Switch (GbE2c)
network traffic, as well as a varietry of traditional network troubleshooting tools:
sFlow—Statistical flow monitoring for high-speed data ports.
Port Mirroring—Complete port data capture.
Other tools such as ping, traceroute, etc.
sFlow
The GbE2c supports sFlow technology for monitoring traffic in data networks. The switch includes
an embedded sFlow agent which can be configured to sample network traffic and provide
continuous monitoring information to a central sFlow analyzer.
Note – The switch is responsible only for forwarding sFlow information. A separate sFlow
analyzer is required elsewhere on the network in order to interpret sFlow data.
sFlow Statistical Counters
The GbE2c can be configured to send network statistics to an sFlow analyzer at regular intervals.
For each port, a polling interval of 5 to 60 seconds can be configured.
At the end of each configured polling interval, the GbE2c reports general port statistics (as found in
the output of the /stats/port <x>/if command) and port Ethernet statistics (as found in the
output of the /stats/port <x>/ether command).