Home » HP Manuals » Repeaters & Transceivers » HP GbE2c » Manual Viewer

HP GbE2c HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Gu - Page 110

OSPF implementation in GbE2c software, Configurable parameters, Defining areas

UPC - 808736802215

Add to My Manuals
Save this manual to your list of manuals

Page 110 highlights

OSPF implementation in GbE2c software The GbE2c Ethernet Blade Switch supports a single instance of OSPF and up to 4 K routes on the network. The following sections describe OSPF implementation in GbE2c software: • Configurable Parameters • Defining Areas • Interface Cost • Electing the Designated Router and Backup • Summarizing Routes • Default Routes • Virtual Links • Router ID • Authentication Configurable parameters In GbE2c software, OSPF parameters can be configured through the Command Line Interface (CLI), Browser-Based Interface (BBI) for GbE2c Ethernet Blade Switches, or through SNMP. For more information, see "Accessing the Switch." The CLI supports the following parameters: interface output cost, interface priority, dead and hello intervals, retransmission interval, and interface transit delay. OSPF traps-Traps produce messages upon certain events or error conditions, such as missing a hello, failing a neighbor, or recalculating the SPF. In addition to the above parameters, you can also specify the following: Link-State Database size-The size of the external LSA database can be specified to help manage the memory resources on the switch. • Shortest Path First (SPF) interval-Time interval between successive calculations of the shortest path tree using the Dijkstra's algorithm. • Stub area metric-A stub area can be configured to send a numeric metric value such that all routes received via that stub area carry the configured metric to potentially influence routing decisions. • Default routes-Default routes with weight metrics can be manually injected into transit areas. This helps establish a preferred route when multiple routing devices exist between two areas. It also helps route traffic to external networks. Defining areas If you are configuring multiple areas in your OSPF domain, one of the areas must be designated as area 0, known as the backbone. The backbone is the central OSPF area and is usually physically connected to all other areas. The areas inject routing information into the backbone which, in turn, disseminates the information into other areas. Since the backbone connects the areas in your network, it must be a contiguous area. If the backbone is partitioned (possibly as a result of joining separate OSPF networks), parts of the AS will be unreachable, and you will need to configure virtual links to reconnect the partitioned areas (see "Virtual Links"). Up to three OSPF areas can be connected to the GbE2c Ethernet Blade Switch. To configure an area, the OSPF number must be defined and then attached to a network interface on the switch. The full process is explained in the following sections. An OSPF area is defined by assigning two pieces of information-an area index and an area ID. The command to define an OSPF area is as follows: >> # /cfg/l3/ospf/aindex /areaid NOTE: The aindex option above is an arbitrary index used only on the switch and does not represent the actual OSPF area number. The actual OSPF area number is defined in the areaid portion of the command as explained in the following sections. OSPF 110

Section	Page
HP GbE2c Ethernet Blade Switch for c-Class BladeSystem Application Guide	1
Notice	2
Contents	3
Accessing the switch	8
Introduction	8
Additional references	8
Typographical conventions	9
Management Network	9
Connecting through the console port	10
Connecting through Telnet	10
Connecting through Secure Shell	10
Using the command line interfaces	10
Configuring an IP interface	11
Using the Browser-based Interface	11
Using Simple Network Management Protocol	12
SNMP v1.0	12
SNMP v3.0	12
Default configuration	12
User configuration	13
View based configurations	14
CLI user equivalent	14
CLI oper equivalent	14
Configuring SNMP trap hosts	15
SNMPv1 trap host	15
SNMPv2 trap host configuration	16
SNMPv3 trap host configuration	16
Secure access to the switch	17
Setting allowable source IP address ranges	17
Configuring an IP address range for the management network	17
RADIUS authentication and authorization	18
How RADIUS authentication works	18
Configuring RADIUS on the switch (CLI example)	18
Configuring RADIUS on the switch (BBI example)	19
RADIUS authentication features	20
User accounts for RADIUS users	21
RADIUS attributes for user privileges	21
TACACS+ authentication	21
How TACACS+ authentication works	22
TACACS+ authentication features	22
Authorization	22
Accounting	23
Configuring TACACS+ authentication on the switch (CLI example)	23
Configuring TACACS+ authentication on the switch (BBI example)	24
Secure Shell and Secure Copy	25
Configuring SSH and SCP features (CLI example)	26
Using SSH and SCP client commands	27
SSH and SCP encryption of management messages	28
Generating RSA host and server keys for SSH access	28
SSH/SCP integration with RADIUS and TACACS+ authentication	28
User access control	29
Setting up user IDs	29
Ports and trunking	30
Introduction	30
Ports on the switch	30
Port trunk groups	31
Statistical load distribution	31
Built-in fault tolerance	31
Before you configure trunks	31
Trunk group configuration rules	31
Port trunking example	32
Configuring trunk groups (CLI example)	33
Configuring trunk groups (BBI example)	34
Configurable Trunk Hash algorithm	36
Link Aggregation Control Protocol	37
Configuring LACP	38
Port-based Network Access and traffic control	39
Port-based Network Access control	39
Extensible authentication protocol over LAN	39
802.1x authentication process	39
EAPoL Message Exchange	40
802.1x port states	41
Supported RADIUS attributes	41
EAPoL configuration guidelines	42
Port-based traffic control	42
Configuring port-based traffic control	42
VLANs	43
Introduction	43
Overview	43
VLANs and port VLAN ID numbers	43
VLAN numbers	43
Viewing VLANs	43
PVID numbers	43
Viewing and configuring PVIDs	44
Port information	44
Port configuration	44
VLAN tagging	44
VLANs and IP interfaces	47
VLAN topologies and design considerations	47
VLAN configuration rules	47
Multiple VLANS with tagging	47
Configuring the example network	49
Configuring ports and VLANs on Switch 1 (CLI example)	49
Configuring ports and VLANs on Switch 2 (CLI example)	50
Configuring ports and VLANs on Switch 1 (BBI example)	51
FDB static entries	54
Trunking support for FDB static entries	54
Configuring a static FDB entry	54
Spanning Tree Protocol	55
Introduction	55
Overview	55
Bridge Protocol Data Units	55
Determining the path for forwarding BPDUs	55
Bridge priority	55
Port priority	55
Port path cost	56
Spanning Tree Group configuration guidelines	56
Default Spanning Tree configuration	56
Adding a VLAN to a Spanning Tree Group	56
Creating a VLAN	56
Rules for VLAN tagged ports	56
Adding and removing ports from STGs	57
Assigning cost to ports and trunk groups	57
Multiple Spanning Trees	57
Why do we need Multiple Spanning Trees?	57
VLAN participation in Spanning Tree Groups	58
Configuring Multiple Spanning Tree Groups	58
Configuring Switch 1 (CLI example)	59
Configuring Switch 2 (CLI example)	59
Configuring Switch 1 (BBI example)	59
Port Fast Forwarding	60
Configuring Port Fast Forwarding	61
Fast Uplink Convergence	61
Configuration guidelines	61
Configuring Fast Uplink Convergence	61
RSTP and MSTP	62
Introduction	62
Rapid Spanning Tree Protocol	62
Port state changes	62
Port type and link type	62
Edge port	62
Link type	63
RSTP configuration guidelines	63
RSTP configuration example	63
Configuring Rapid Spanning Tree (CLI example)	63
Configuring Rapid Spanning Tree Protocol (BBI example)	63
Multiple Spanning Tree Protocol	65
MSTP region	65
Common Internal Spanning Tree	65
MSTP configuration guidelines	65
MSTP configuration example	65
Configuring Multiple Spanning Tree Protocol (CLI example)	65
Configuring Multiple Spanning Tree Protocol (BBI example)	66
Quality of Service	70
Introduction	70
Overview	70
Using ACL filters	71
Summary of packet classifiers	71
Summary of ACL actions	72
Understanding ACL precedence	72
Using ACL Groups	74
ACL Metering and Re-marking	74
Metering	74
Re-marking	75
Viewing ACL statistics	75
ACL configuration examples	75
Configure Access Control Lists (CLI example)	75
Configure Access Control Lists and Groups (BBI example 1)	76
Using DSCP values to provide QoS	80
Differentiated Services concepts	80
Per Hop Behavior	80
QoS levels	81
Using 802.1p priorities to provide QoS	81
802.1p configuration (CLI example)	82
802.1p configuration (BBI example)	83
Queuing and scheduling	86
Basic IP routing	87
IP routing benefits	87
Routing between IP subnets	87
Example of subnet routing	89
Using VLANs to segregate broadcast domains	91
Dynamic Host Configuration Protocol	92
DHCP relay agent	92
DHCP relay agent configuration	93
Routing Information Protocol	94
Distance vector protocol	94
Stability	94
Routing updates	94
RIPv1	94
RIPv2	94
RIPv2 in RIPv1 compatibility mode	95
RIP Features	95
Poison	95
Triggered updates	95
Multicast	95
Default	95
Metric	95
Authentication	95
RIP configuration example	96
IGMP Snooping	97
Introduction	97
Overview	97
FastLeave	97
IGMP Filtering	98
Configuring the range	98
Configuring the action	98
Static multicast router	98
IGMP Snooping configuration example	98
Configuring IGMP Snooping (CLI example)	98
Configuring IGMP Filtering (CLI example)	99
Configuring a Static Mrouter (CLI example)	100
Configuring IGMP Snooping (BBI example)	100
Configuring IGMP Filtering (BBI example)	102
Configuring a Static Multicast Router (BBI example)	105
OSPF	107
OSPF overview	107
Types of OSPF areas	107
Types of OSPF routing devices	108
Neighbors and adjacencies	109
Link-State Database	109
Shortest Path First Tree	109
Internal versus external routing	109
OSPF implementation in GbE2c software	110
Configurable parameters	110
Defining areas	110
Assigning the area index	111
Using the area ID to assign the OSPF area number	111
Attaching an area to a network	111
Interface cost	112
Electing the designated router and backup	112
Summarizing routes	112
Default routes	112
Virtual links	113
Router ID	114
Authentication	114
Host routes for load balancing	115
OSPF features not supported in this release	116
OSPF configuration examples	116
Example 1: Simple OSPF domain (CLI example)	116
Example 1: Simple OSPF domain (BBI example)	117
Example 2: Virtual links	124
Configuring OSPF for a virtual link on Switch A	124
Configuring OSPF for a virtual link on Switch B	126
Other Virtual Link Options	127
Example 3: Summarizing routes	127
Verifying OSPF configuration	128
Remote monitoring	129
Introduction	129
Overview	129
RMON group 1—statistics	129
Configuring RMON Statistics (CLI example)	129
Configuring RMON Statistics (BBI example)	130
RMON group 2—history	132
History MIB objects	132
RMON group 3—alarms	134
Alarm MIB objects	134
RMON group 9—events	138
Configuring RMON Events (CLI example)	138
Configuring RMON Events (BBI example 1)	139
High availability	140
Introduction	140
Uplink Failure Detection	140
Failure Detection Pair	141
Spanning Tree Protocol with UFD	141
Configuration guidelines	141
Monitoring Uplink Failure Detection	141
Configuring Uplink Failure Detection	142
Configuring UFD on Switch 1 (CLI example)	142
Configuring UFD on Switch 2 (CLI example)	142
Configuring Uplink Failure Detection (BBI example)	143
VRRP overview	145
VRRP components	145
Virtual router	145
Virtual router MAC address	145
Owners and renters	145
Master and backup virtual router	145
Virtual Interface Router	145
VRRP operation	146
Selecting the master VRRP router	146
Failover methods	146
Active-Active redundancy	147
GbE2c extensions to VRRP	147
Tracking VRRP router priority	147
Virtual router deployment considerations	147
Assigning VRRP virtual router ID	148
Configuring the switch for tracking	148
High availability configurations	148
Active-Active configuration	148
Task 1: Configure Switch A	149
Task 2: Configure Switch B	150
Task 1: Configure Switch A (BBI example)	151
Troubleshooting tools	159
Introduction	159
Port Mirroring	159
Configuring Port Mirroring (CLI example)	160
Configuring Port Mirroring (BBI example)	161
Other network troubleshooting techniques	162
Console and Syslog messages	162
Ping	162
Trace route	163
Statistics and state information	163
Customer support tools	163

Match case Limit results 1 per page

OSPF 110

OSPF implementation in GbE2c software

The GbE2c Ethernet Blade Switch supports a single instance of OSPF and up to 4 K routes on the network. The follow-

ing sections describe OSPF implementation in GbE2c software:

•

Configurable Parameters

•

Defining Areas

•

Interface Cost

•

Electing the Designated Router and Backup

•

Summarizing Routes

•

Default Routes

•

Virtual Links

•

Router ID

•

Authentication

Configurable parameters

In GbE2c software, OSPF parameters can be configured through the Command Line Interface (CLI), Browser-Based

Interface (BBI) for GbE2c Ethernet Blade Switches, or through SNMP. For more information, see “Accessing the

Switch.”

The CLI supports the following parameters: interface output cost, interface priority, dead and hello intervals,

retransmission interval, and interface transit delay.

OSPF traps—Traps produce messages upon certain events or error conditions, such as missing a hello, failing a

neighbor, or recalculating the SPF.

In addition to the above parameters, you can also specify the following:

Link-State Database size—The size of the external LSA database can be specified to help manage the memory

resources on the switch.

•

Shortest Path First (SPF) interval—Time interval between successive calculations of the shortest path tree using the

Dijkstra’s algorithm.

•

Stub area metric—A stub area can be configured to send a numeric metric value such that all routes received

via that stub area carry the configured metric to potentially influence routing decisions.

•

Default routes—Default routes with weight metrics can be manually injected into transit areas. This helps

establish a preferred route when multiple routing devices exist between two areas. It also helps route traffic to

external networks.

Defining areas

If you are configuring multiple areas in your OSPF domain, one of the areas must be designated as area 0, known as

the

backbone

. The backbone is the central OSPF area and is usually physically connected to all other areas. The

areas inject routing information into the backbone which, in turn, disseminates the information into other areas.

Since the backbone connects the areas in your network, it must be a contiguous area. If the backbone is partitioned

(possibly as a result of joining separate OSPF networks), parts of the AS will be unreachable, and you will need to

configure

virtual links

to reconnect the partitioned areas (see “Virtual Links”).

Up to three OSPF areas can be connected to the GbE2c Ethernet Blade Switch. To configure an area, the OSPF

number must be defined and then attached to a network interface on the switch. The full process is explained in the

following sections.

An OSPF area is defined by assigning

two

pieces of information—an

area index

and an

area ID

. The command to

define an OSPF area is as follows:

>> # /cfg/l3/ospf/aindex <

area index

>/areaid <

n.n.n.n

NOTE:

The

aindex

option above is an arbitrary index used only on the switch and does not represent the

actual OSPF area number. The actual OSPF area number is defined in the

areaid

portion of the command as

explained in the following sections.