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 4: VLANs 89
The default configuration for the switch sets all ports (except the management port) as untagged
members of VLAN 1, and sets the PVID to 1. In the default configuration example, all incoming
packets are assigned to VLAN 1 by the default port VLAN identifier (PVID=1).
Use the following CLI commands to view PVIDs:
Use the following command to configure PVIDs:
Each port on the switch can belong to one or more VLANs, and each VLAN can have any number
of switch ports in its membership. Any port that belongs to multiple VLANs, however, must have
VLAN tagging enabled (see “VLAN Tagging” on page 90).
Any untagged frames (those with no VLAN specified) are set with the PVID of the sending port.
>> # /info/port
Port Tag MediaRMON Lrn Fld PVID NAME VLAN(s)
---- --- ---- --- --- ----- -------------- ----------------------------
1 n Auto d e e 1* Downlink1 1
2 n Auto d e e 1* Downlink2 1
3 n Auto d e e 1* Downlink3 1
4 n Auto d e e 1* Downlink4 1
5 n Auto d e e 1* Downlink5 1
6 n Auto d e e 1* Downlink6 1
7 n Auto d e e 1* Downlink7 1
8 n Auto d e e 1* Downlink8 1
9 n Auto d e e 1* Downlink9 1
10 n Auto d e e 1* Downlink10 1
11 n Auto d e e 1* Downlink11 1
12 n Auto d e e 1* Downlink12 1
13 n Auto d e e 1* Downlink13 1
14 n Auto d e e 1* Downlink14 1
15 n Auto d e e 1* Downlink15 1
16 n Auto d e e 1* Downlink16 1
17 n Auto d e e 1* Xconnect1 1
18 n Auto d e e 1* Xconnect2 1
19 n Auto d e e 4095 Mgmt 4095
20 n Auto d e e 1* Uplink1 1
21 n Auto d e e 1* Uplink2 1
22 n Auto d e e 1* Uplink3 1
23 n Auto d e e 1* Uplink4 1
24 n Auto d e e 1* Uplink5 1
* = PVID is tagged.
>> /cfg/port <port number>/pvid <PVID number>