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 3: Port-Based Network Access Control 85
Port-Based Traffic Control
Port-based traffic control prevents switch ports from being disrupted by LAN storms. A LAN storm
occurs when data packets flood the LAN, which can cause the network to become congested and
slow down. Errors in the protocol-stack implementation or in the network configuration can cause a
LAN storm.
You can enable port-based traffic control separately for each of the following traffic types:
Broadcast—packets with destination MAC address ff:ff:ff:ff:ff:ff
Multicast—packets that have MAC addresses with the least significant bit of their first octet set
to one
Destination Lookup Failed (DLF)—packets with unknown destination MAC address, that are
treated like broadcast packets
With Port-based Traffic Control enabled, the port monitors incoming traffic of each type noted
above. If the traffic exceeds a configured threshold, the port blocks traffic that exceeds the threshold
until the traffic flow falls back within the threshold.
The GbE2c supports separate traffic-control thresholds for broadcast, multicast, and DLF traffic.
The traffic threshold is measured in number of frames per second.
Note – All ports that belong to a trunk must have the same traffic-control settings.
Configuring Port-Based Traffic Control
To configure a port for traffic control, perform the following steps:
1. Configure the traffic-control threshold and enable traffic control.
2. To disable a traffic-control threshold, use the following command:
3. Apply and save the configuration.
Main# /cfg/port 2
>> Port 2# brate 150000 (Set broadcast threshold)
>> Port 2# mrate 150000 (Set multicast threshold)
>> Port 2# drate 150000 (Set DLF threshold)
>> Port 2# mrate dis (Disable multicast threshold)
>> Port 2# apply (Apply the port configurations)
>> Port 2# save (Save the port configurations)