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 8: Quality of Service 141
Summary of ACL Actions
Actions determine how the traffic is treated. The GbE2c QoS actions include the following:
Pass or Drop
Re-mark a new DiffServ Code Point (DSCP)
Re-mark the 802.1p field
Set the COS queue
ACL Order of Precedence
When multiple ACLs are assigned to a port, the order in which the ACLs are applied to port traffic
(or whether they are applied at all) depends on the following factors:
The precedence group in which the ACL resides;
The ACL number;
Whether a prior ACL in the precedence group is also matched;
And whether the ACL action is compatible with preceding ACLs.
ACLs are divided into Precedence Groups, as shown in the following table. Each Precedence Group
provides a different set of packet classifiers for the ACLs within the Precedence Group.
Table 19 ACI Precedence Groups
Precedence Group Member ACLs Supported Packet Classifiers Priority Level
Precedence Group 1 ACL 1 – ACL 127 Destination MAC address
Source IP address
TCP source port
TCP destination port
Packet format
Highest
Precedence Group 2 ACL 128 – ACL 254 Destination MAC address
Destination IP address
Ethernet type
VLAN ID
802.1p
Packet format