Dell PowerConnect 6248 Configuration Guide - Page 175

Routed Access Scenario, NSF and Routed Access

Get Dell PowerConnect 6248 PDF manuals and user guides View all Dell PowerConnect 6248 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 175 highlights

Routed Access Scenario Figure 9-5 shows a stack of three units serving as an access router for a set of hosts. Two LAGs connect the stack to two aggregation routers. Each LAG is a member of a VLAN routing interface. The stack has OSPF and PIM adjacencies with each of the aggregation routers. The top unit in the stack is the management unit. Figure 9-5. NSF and Routed Access ` LAG1 ` Access Router LAG2 Aggregation Routers If the management unit fails, its link to the aggregation router is removed from the LAG. When the control plane restarts, both routing interfaces come back up by virtue of the LAGs coming up. OSPF sends grace LSAs to inform its OSPF neighbors (the aggregation routers) that it is going through a graceful restart. NOTE: The graceful restart feature for OSPF is disabled by default. To enable OSPF to perform a graceful restart for all planned and unplanned warm restart events, use the nsf command in Router OSPF Config mode: console#configure console(config)#router ospf console(config-router)#nsf The grace LSAs reach the neighbors before they drop their adjacencies with the access router. PIM starts sending hello messages to its neighbors on the aggregation routers using a new generation ID to prompt the neighbors to quickly resend multicast routing information. PIM neighbors recognize the new generation ID and immediately relay the group state back to the restarting router. IGMP sends queries to relearn the hosts' interest in multicast groups. IGMP tells PIM the group membership, and PIM sends JOIN messages upstream. The control plane updates the driver with checkpointed unicast routes. The forwarding plane reconciles L3 hardware tables. The OSPF graceful restart finishes, and the control plane deletes any stale unicast routes not relearned at this point. The forwarding plane reconciles L3 multicast hardware tables. Throughout the process, the hosts continue to receive their multicast streams, possibly with a short interruption as the top aggregation router learns that one it its LAG members is down. The hosts see no more than a 50 ms interruption in unicast connectivity. Utility 175

  • 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
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
Utility
175
Routed Access Scenario
Figure 9-5 shows a stack of three units serving as an access router for a set of hosts. Two LAGs connect
the stack to two aggregation routers. Each LAG is a member of a VLAN routing interface. The stack has
OSPF and PIM adjacencies with each of the aggregation routers. The top unit in the stack is the
management unit.
Figure 9-5.
NSF and Routed Access
If the management unit fails, its link to the aggregation router is removed from the LAG. When the
control plane restarts, both routing interfaces come back up by virtue of the LAGs coming up. OSPF
sends grace LSAs to inform its OSPF neighbors (the aggregation routers) that it is going through a
graceful restart.
NOTE:
The graceful restart feature for OSPF is disabled by default. To enable OSPF to perform a graceful restart
for all planned and unplanned warm restart events, use the
nsf
command in Router OSPF Config mode:
console#configure
console(config)#router ospf
console(config-router)#nsf
The grace LSAs reach the neighbors before they drop their adjacencies with the access router. PIM starts
sending hello messages to its neighbors on the aggregation routers using a new generation ID to prompt
the neighbors to quickly resend multicast routing information. PIM neighbors recognize the new
generation ID and immediately relay the group state back to the restarting router. IGMP sends queries to
relearn the hosts' interest in multicast groups. IGMP tells PIM the group membership, and PIM sends
JOIN messages upstream. The control plane updates the driver with checkpointed unicast routes. The
forwarding plane reconciles L3 hardware tables.
The OSPF graceful restart finishes, and the control plane deletes any stale unicast routes not relearned at
this point. The forwarding plane reconciles L3 multicast hardware tables. Throughout the process, the
hosts continue to receive their multicast streams, possibly with a short interruption as the top
aggregation router learns that one it its LAG members is down. The hosts see no more than a 50 ms
interruption in unicast connectivity.
`
`
LAG1
LAG2
Access Router
Aggregation Routers