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 1: Accessing the Switch 31
Using Simple Network Management Protocol
BLADE OS provides Simple Network Management Protocol (SNMP) version 1, version 2, and
version 3 support for access through any network management software, such as IBM Director or
HP-OpenView.
SNMP v1.0
To access the SNMP agent on the GbE2c, the read and write community strings on the SNMP
manager should be configured to match those on the switch. The default read community string on
the switch is public and the default write community string is private.
The read and write community strings on the switch can be changed using the following commands
on the CLI:
and
The SNMP manager should be able to reach the management interface or any one of the IP
interfaces on the switch.
For the SNMP manager to receive the SNMPv1 traps sent out by the SNMP agent on the switch,
configure the trap host on the switch with the following command:
SNMP v3.0
SNMPv3 is an enhanced version of the Simple Network Management Protocol, approved by the
Internet Engineering Steering Group in March, 2002. SNMP v3.0 contains additional security and
authentication features that provide data origin authentication, data integrity checks, timeliness
indicators and encryption to protect against threats such as masquerade, modification of
information, message stream modification and disclosure.
SNMPv3 ensures that the client can use SNMPv3 to query the MIBs, mainly for security.
To access the SNMP v3.0 menu, enter the following command in the CLI:
For more information on SNMP MIBs and the commands used to configure SNMP on the switch,
see the BLADE OS Command Reference.
>> # /cfg/sys/ssnmp/rcomm <SNMP read community string>
>> # /cfg/sys/ssnmp/wcomm <SNMP write community string>
>> # /cfg/sys/ssnmp/trsrc <1-128>
>> # /cfg/sys/ssnmp/snmpv3