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

OSPF, OSPF overview, Types of OSPF areas

Page 107 highlights

OSPF GbE2c software supports the Open Shortest Path First (OSPF) routing protocol. The GbE2c implementation conforms to the OSPF version 2 specifications detailed in Internet RFC 1583. The following sections discuss OSPF support for the GbE2c Ethernet Blade Switch: • OSPF Overview: This section provides information on OSPF concepts, such as types of OSPF areas, types of routing devices, neighbors, adjacencies, link state database, authentication, and internal versus external routing. • OSPF Implementation in GbE2c Software. This section describes how OSPF is implemented in GbE2c software, such as configuration parameters, electing the designated router, summarizing routes, defining route maps and so forth. • OSPF Configuration Examples. This section provides step-by-step instructions on configuring different configuration examples: • Creating a simple OSPF domain • Creating virtual links • Summarizing routes NOTE: OSPF is available only on the GbE2c Layer 2/3 Ethernet Blade Switch. OSPF overview OSPF is designed for routing traffic within a single IP domain called an Autonomous System (AS). The AS can be divided into smaller logical units known as areas. All routing devices maintain link information in their own Link State Database (LSDB). The LSDB for all routing devices within an area is identical but is not exchanged between different areas. Only routing updates are exchanged between areas, thereby significantly reducing the overhead for maintaining routing information on a large, dynamic network. The following sections describe key OSPF concepts. Types of OSPF areas An AS can be broken into logical units known as areas. In any AS with multiple areas, one area must be designated as area 0, known as the backbone. The backbone acts as the central OSPF area. All other areas in the AS must be connected to the backbone. Areas inject summary routing information into the backbone, which then distributes it to other areas as needed. OSPF defines the following types of areas: • Stub Area-an area that is connected to only one other area. External route information is not distributed into stub areas. • Not-So-Stubby-Area (NSSA)-similar to a stub area with additional capabilities. External routes from outside the AS can be advertised within the NSSA but are not distributed into other areas. • Transit Area-an area that allows area summary information to be exchanged between routing devices. The backbone (area 0), any area that contains a virtual link to connect two areas, and any area that is not a stub area or an NSSA are considered transit areas OSPF 107

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165

OSPF 107
OSPF
GbE2c software supports the Open Shortest Path First (OSPF) routing protocol. The GbE2c implementation conforms
to the OSPF version 2 specifications detailed in Internet RFC 1583. The following sections discuss OSPF support for
the GbE2c Ethernet Blade Switch:
OSPF Overview: This section provides information on OSPF concepts, such as types of OSPF areas, types of
routing devices, neighbors, adjacencies, link state database, authentication, and internal versus external
routing.
OSPF Implementation in GbE2c Software. This section describes how OSPF is implemented in GbE2c software,
such as configuration parameters, electing the designated router, summarizing routes, defining route maps and
so forth.
OSPF Configuration Examples. This section provides step-by-step instructions on configuring different
configuration examples:
Creating a simple OSPF domain
Creating virtual links
Summarizing routes
NOTE:
OSPF is available only on the GbE2c Layer 2/3 Ethernet Blade Switch.
OSPF overview
OSPF is designed for routing traffic within a single IP domain called an Autonomous System (AS). The AS can be
divided into smaller logical units known as
areas
.
All routing devices maintain link information in their own Link State Database (LSDB). The LSDB for all routing devices
within an area is identical but is not exchanged between different areas. Only routing updates are exchanged
between areas, thereby significantly reducing the overhead for maintaining routing information on a large, dynamic
network.
The following sections describe key OSPF concepts.
Types of OSPF areas
An AS can be broken into logical units known as
areas
. In any AS with multiple areas, one area must be designated
as area 0, known as the
backbone
. The backbone acts as the central OSPF area. All other areas in the AS must be
connected to the backbone. Areas inject summary routing information into the backbone, which then distributes it to
other areas as needed.
OSPF defines the following types of areas:
Stub Area—an area that is connected to only one other area. External route information is not distributed into
stub areas.
Not-So-Stubby-Area (NSSA)—similar to a stub area with additional capabilities. External routes from outside the
AS can be advertised within the NSSA but are not distributed into other areas.
Transit Area—an area that allows area summary information to be exchanged between routing devices. The
backbone (area 0), any area that contains a virtual link to connect two areas, and any area that is not a stub
area or an NSSA are considered transit areas