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
104 Chapter 4: VLANs BMD00113, September 2009
3. Add member ports for this PVLAN.
Note – If VLAN tagging is turned off for a port, and that port’s default VLAN (PVID) is different
than the VLAN to which the port is being added, you will be asked to confirm changing the PVID
to the current VLAN, as shown in the example.
4. Configure VLAN tagging for ports.
5. Enable the PVLAN.
>> VLAN 2 Protocol 1# add 1
Port 1 is an UNTAGGED port and its current PVID is 1.
Confirm changing PVID from 1 to 2 [y/n]: y
Current ports for VLAN 2: empty
Current ports for VLAN 1, Protocol 3: empty
Pending new ports for VLAN 2: 1
Pending new ports for VLAN 2, Protocol 1: 1
>> VLAN 2 Protocol 1# add 20
Port 20 is an UNTAGGED port and its current PVID is 1.
Confirm changing PVID from 1 to 2 [y/n]: y
Current ports for VLAN 2: empty
Current ports for VLAN 1, Protocol 2: empty
Pending new ports for VLAN 2: 1 20
Pending new ports for VLAN 2, Protocol 1: 1 20
>> VLAN 2 Protocol 1# /cfg/port 1/tag ena (Enable tagging on port)
Current VLAN tag support: disabled
New VLAN tag support: enabled
Port 1 changed to tagged.
>> Port 1# /cfg/l2/vlan 2/pvlan 1/tagpvl (Enable PVLAN tagging)
Enter port to be tagged: 1
Ena/Dis pvlan tag: ena
Current status: disabled
New status: enabled
WARN: Tagging status of Port 1 in VLAN 2 will be changed for
all protocols.
Confirm changing port's pvlan tagging status [y/n]: y
>> VLAN 2 Protocol 1# ena (Enable protocol-based VLAN)
Current status: disabled
New status: enabled
>> VLAN 2 Protocol 1# apply (Apply the configuration)
>> VLAN 2 Protocol 1# save (Save your changes)