HP 6125XLG R2306-HP 6125XLG Blade Switch FCoE Configuration Guide - Page 62

Static routes, FSPF routes, Basic concepts

Get HP 6125XLG PDF manuals and user guides View all HP 6125XLG manuals
Add to My Manuals
Save this manual to your list of manuals

Page 62 highlights

• When an FCF switch assigns FC addresses to the directly connected N_Ports, the FCF switch also adds the direct routes of these addresses to the routing table. In such a direct route, the destination address is an assigned FC address, the mask is 0xFFFFFF, and the outgoing interface is the VFC interface connected to the N_Port. Static routes Static routes are manually configured by the administrator. After you configure a static route, an FC frame to the specified destination is forwarded along the path specified by the administrator. In a simple network, static routes are enough for implementing network connectivity. By correctly setting and using static routes, you can improve network performance and guarantee bandwidth for critical network applications. However, the static routes cannot automatically adapt to network topology changes. When the network fails or the network topology changes, the routes might fail to be reachable, and the network is interrupted. In this case, you must manually modify the static routes. Static routes support equal-cost routes. When you configure multiple equal-cost static routes to the same destination but with different outgoing interfaces, equal-cost routes are generated. FSPF routes As a route selection protocol based on link states, FSPF can automatically calculate the best path between any two switches in a fabric. FSPF has the following characteristics: • Can be used for any topology. • Supports equal-cost routes. • Performs topology calculations on a per-VSAN basis. • Runs only on E_Ports and provides a loop-free topology. • Provides a topology database on each switch to track the state of all links. • Uses the Dijkstra algorithm to calculate routes. • Provides fast convergence in the event of topology changes. Basic concepts • LSDB The link state database (LSDB) is used to store global topology information for switches and link state information of all switches in link state records (LSRs). • LSR An LSR describes information about all link states between a switch and its directly connected switches. Each LSR generated by a switch is called an LSR instance. LSRs generated by all switches comprise the LSDB. An LSR contains one or more pieces of link state information, including the following: { LSR hold time. { Domain ID of the switch advertising the LSR. { LSR instance number. Every time an LSR is updated, the instance number increments by 1. 56

  • 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
56
•
When an FCF switch assigns FC addresses to the directly connected N_Ports, the FCF switch also
adds the direct routes of these addresses to the routing table. In such a direct route, the destination
address is an assigned FC address, the mask is 0xFFFFFF, and the outgoing interface is the VFC
interface connected to the N_Port.
Static routes
Static routes are manually configured by the administrator. After you configure a static route, an FC frame
to the specified destination is forwarded along the path specified by the administrator.
In a simple network, static routes are enough for implementing network connectivity. By correctly setting
and using static routes, you can improve network performance and guarantee bandwidth for critical
network applications.
However, the static routes cannot automatically adapt to network topology changes. When the network
fails or the network topology changes, the routes might fail to be reachable, and the network is
interrupted. In this case, you must manually modify the static routes.
Static routes support equal-cost routes. When you configure multiple equal-cost static routes to the same
destination but with different outgoing interfaces, equal-cost routes are generated.
FSPF routes
As a route selection protocol based on link states, FSPF can automatically calculate the best path
between any two switches in a fabric.
FSPF has the following characteristics:
•
Can be used for any topology.
•
Supports equal-cost routes.
•
Performs topology calculations on a per-VSAN basis.
•
Runs only on E_Ports and provides a loop-free topology.
•
Provides a topology database on each switch to track the state of all links.
•
Uses the Dijkstra algorithm to calculate routes.
•
Provides fast convergence in the event of topology changes.
Basic concepts
•
LSDB
The link state database (LSDB) is used to store global topology information for switches and link
state information of all switches in link state records (LSRs).
•
LSR
An LSR describes information about all link states between a switch and its directly connected
switches.
Each LSR generated by a switch is called an LSR instance. LSRs generated by all switches comprise
the LSDB. An LSR contains one or more pieces of link state information, including the following:
{
LSR hold time.
{
Domain ID of the switch advertising the LSR.
{
LSR instance number. Every time an LSR is updated, the instance number increments by 1.