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 103
PVLAN Configuration Guidelines
Consider the following guidelines when you configure protocol-based VLANs:
Each port can support up to 16 VLAN protocols.
The GbE2c can support up to 16 protocols simultaneously.
Each PVLAN must have at least one port assigned before it can be activated.
The same port within a port-based VLAN can belong to multiple PVLANs.
An untagged port can be a member of multiple PVLANs.
A port cannot be a member of different VLANs with the same protocol association.
Configuring PVLANs
Follow this procedure to configure a Protocol-based VLAN (PVLAN).
1. Create a VLAN and define the protocol type(s) supported by the VLAN.
2. Configure the priority value for the protocol.
>> /cfg/l2/vlan 2 (Select VLAN 2)
>> VLAN 2# ena (enable VLAN 2)
Current status: disabled
New status: enabled
>> VLAN 2# pvlan
Enter protocol number [1-8]: 1 (Select a protocol number)
>> VLAN 2 Protocol 1# pty
Current FrameType: empty; EtherType: empty
Enter new frame type(Ether2/SNAP/LLC): ether2 (Define the frame type)
Enter new Ether type: 0800 (Define the Ethernet type)
New pending FrameType: Ether2; EtherType: 0800
>> VLAN 2 Protocol 1# prio 1 (Configure the priority value)