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 101
Protocol-Based VLANs
Protocol-based VLANs (PVLANs) allow you to segment network traffic according to the network
protocols in use. Traffic for supported network protocols can be confined to a particular port-based
VLAN. You can give different priority levels to traffic generated by different network protocols.
With PVLAN, the switch classifies incoming packets by Ethernet protocol of the packets, not by the
configuration of the ingress port. When an untagged or priority-tagged frame arrives at an ingress
port, the protocol information carried in the frame is used to determine a VLAN to which the frame
belongs. If a frame’s protocol is not recognized as a pre-defined PVLAN type, the ingress port’s
PVID is assigned to the frame. When a tagged frame arrives, the VLAN ID in the frame’s tag is
used.
Each VLAN can contain up to eight different PVLANs. You can configure separate PVLANs on
different VLANs, with each PVLAN segmenting traffic for the same protocol type. For example,
you can configure PVLAN 1 on VLAN 2 to segment IPv4 traffic, and PVLAN 8 on VLAN 100 to
segment IPv4 traffic.
To define a PVLAN on a VLAN, configure a PVLAN number (1-8) and specify the frame type and
the Ethernet type of the PVLAN protocol. You must assign at least one port to the PVLAN before it
can function. Define the PVLAN frame type and Ethernet type as follows:
Frame type—consists of one of the following values:
Ether2 (Ethernet II)
SNAP (Subnetwork Access Protocol)
LLC (Logical Link Control)
Ethernet type—consists of a 4-digit (16 bit) hex value that defines the Ethernet type. You can
use common Ethernet protocol values, or define your own values. Following are examples of
common Ethernet protocol values:
IPv4 = 0800
IPv6 = 86dd
ARP = 0806