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
30 Chapter 1: Accessing the Switch BMD00113, September 2009
User Accounts
By default, remote users must log in with a user name and password to access the switch. The
default user accounts are listed in Table 2:
For information on configuring users or restricting remote access, see “Securing Access to the
Switch” on page 41.
Table 2 Default User Access Levels
Account
Password
Description and Tasks Performed
user user User interaction with the switch is completely passive; nothing can be
changed on the switch. Users may display information that has no security
or privacy implications, such as switch statistics and current operational
state information.
oper Operators can only effect temporary changes on the switch. These changes
are lost when the switch is rebooted/reset. Operators have access to the
switch management features used for daily switch operations. Because any
changes an operator makes are undone by a reset of the switch, operators
cannot severely impact switch operation, but do have access to the
Maintenance menu. By default, the operator account is disabled and has no
password.
admin admin Administrators are the only ones that can make permanent changes to the
switch configuration-changes that are persistent across a reboot/reset of the
switch. Administrators can access switch functions to configure and
troubleshoot problems on the switch level. Because administrators can also
make temporary (operator-level) changes as well, they must be aware of
the interactions between temporary and permanent changes.