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
258 Appendix A: Troubleshooting BMD00113, September 2009
Other Network Troubleshooting Techniques
Other network troubleshooting techniques include the following.
Console and Syslog Messages
When a switch experiences a problem, review the console and Syslog messages. The switch
displays these informative messages when state changes and system problems occur. Syslog
messages can be viewed by using the following command:
/info/sys/log
For more information on interpreting syslog messages, see the BLADE OS 5.1 Command Reference.
Ping
To verify station-to-station connectivity across the network, execute the following command:
ping <host name>|<IP address> [<number of tries> [<msec delay>]]
The IP address is the hostname or IP address of the device. The number of tries (optional) is the
number of attempts (1-32). Msec delay (optional) is the number of milliseconds between attempts.
Trace Route
To identify the route used for station-to-station connectivity across the network, execute the
following command:
traceroute <host name>|<IP address> [<max-hops> [<msec delay>]]
The IP address is the hostname or IP address of the target station. Max-hops (optional) is the
maximum distance to trace (1-16 devices). Msec delay (optional) is the number of milliseconds to
wait for the response.
Statistics and State Information
The switch keeps track of a large number of statistics and many of these are error condition
counters. The statistics and state information can be very useful when troubleshooting a LAN or
Real Server problem. For more information about available statistics, see one of the following:
“Viewing Statistics” chapter of the BLADE OS 5.1 Browser-Based Interface Quick Guide, or
“Statistics Menu” chapter of the BLADE OS 5.1 Command Reference or ISCLI Reference