Brocade Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide (Supporting R05.6.00) - Manual (Page 116)

92 Multi-Service IronWare Multiprotocol Label Switch (MPLS) Configuration Guide
53-1003031-02
Configuring MPLS
1
Brocade(config-mpls)# policy
Brocade(config-mpls-policy)# retry-time 45
Syntax: [no] retry-time seconds
Setting the retry limit
When the ingress LER fails to connect to the egress LER in a signaled LSP, the ingress LER tries
indefinitely to make the connection unless the user sets a limit for these connection attempts. After
this limit is exceeded, the ingress LER stops trying to connect to the egress LER over the primary
path.
When a secondary path is configured for the LSP, it is immediately activated after the primary path
fails. After the secondary path is activated, the ingress LER continues to try to connect to the
egress LER over the primary path either up to the configured retry limit or indefinitely when no retry
limit is set. When a connection over the primary path can be established, the secondary path is
deactivated, and traffic for the LSP is again sent over the primary path.
To set the number of connection attempts to 20.
Brocade(config-mpls)# policy
Brocade(config-mpls-policy)# retry-limit 20
Syntax: [no] retry-limit number
Once the connection is established, the retry counter is reset to zero. In the example above, when
an LSP needs to be established again, the ingress LER makes 20 attempts to establish a
connection to the egress LER.
Establishing administrative group names
Administrative groups, also known as resource classes or link colors, allows the user to assign
MPLS-enabled interfaces to various classes. When a device calculates the path for an LSP, it can
take into account the administrative group to which a interface belongs; the user can specify which
administrative groups the device can include or exclude when making its calculation.
Up to 32 administrative groups can be configured on the device. The user can see an
administrative group either by its name or its number. Before the user can see an administrative
group by its name, the user must specify a name for the group at the MPLS policy level and
associate the name with that administrative group’s number.
For example, the following commands establish three administrative group names.
Brocade(config-mpls)# policy
Brocade(config-mpls-policy)# admin-group gold 30
Brocade(config-mpls-policy)# admin-group silver 20
Brocade(config-mpls-policy)# admin-group bronze 10
Syntax: [no] admin-group name / number