Extreme Networks BlackDiamond 6800 MPLS Guide de l'utilisateur Page 87

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 176
  • Table des matières
  • DEPANNAGE
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 86
MPLS Module Installation and User Guide 5-13
RSVP Features
configured metric that is less than, or equal to, the interior gateway protocol (IGP)
metric. In both cases, a TE /32 route to the egress LER is installed in the route table of
the ingress LER for all of the best equal-cost RSVP-TE paths. Traffic is distributed across
up to four TE /32 routes based on a MAC and IP address hash algorithms. If one of the
LSPs fail, the traffic is redistributed across the remaining active LSPs. In this example,
no LSP secondary paths are required.
Ping Health Checking
After an LSP has been established, the egress LSR may be optionally pinged to
determine end-to-end path connectivity. If a ping response is not received within [2 *
ping-interval – 1] seconds, the LSP is considered unavailable. You can specify how
frequently an ICMP echo request is transmitted to the egress LSR IP address on the
established LSP.
Improving LSP Scaling
You can improve LSP scaling by configuring the following RSVP-TE parameters:
refresh-time
The refresh-time specifies the interval for sending refresh path messages. RSVP
refresh messages provide soft state link-level keep-alive information for previously
established paths and enable the switch to detect when an LSP is no longer active.
RSVP sessions are torn down if an RSVP refresh message is not received from a
neighbor within [(keep-multiplier + 0.5) * 1.5 * refresh-time] seconds. The
valid-refresh-time may be set to any value between zero to 60 seconds. The default
setting is 30 seconds. Configuring a longer refresh time reduces both switch and
network overhead.
summary-refresh-time
The summary-refresh-time, specified in tenths of a second, indicates the time interval
for sending summary refresh RSVP messages. The summary-refresh-time must be
less than the configured refresh-time. The default summary-refresh-time is zero,
indicating that no summary refresh RSVP messages are sent. The
summary-refresh-time value may be set to any value between zero to 100 (or 10
seconds). If configured, the bundled and summary refresh RSVP messages are only
sent to RSVP-TE peers supporting RSVP refresh reduction.
bundle-time
The bundle-time, specified in tenths of a second, indicates the maximum amount of
time a transmit buffer is held so that multiple RSVP messages can be bundled into a
single PDU. The default bundle-time is zero, indicating that RSVP message bundling
Vue de la page 86
1 2 ... 82 83 84 85 86 87 88 89 90 91 92 ... 175 176

Commentaires sur ces manuels

Pas de commentaire