abstract-hop
Syntax
abstract-hop abstract-hop-name { constituent-list constituent-list-name (include-any-list | include-all-list | exclude-all-list | exclude-any-list); operators (AND | OR); }
Hierarchy Level
[edit logical-systems logical-systems-name protocols mpls] [edit protocols mpls]
Description
Define router clusters or groups, similar to the sequence of real-hop constraints (strict or loose), as a sequence of abstract hops for setting up a label-switched path (LSP).
An abstract hop is a logical combination of the existing traffic engineering constraints, such as administrative groups, extended administrative groups, and Shared Risk Link Groups (SRLGs), along with the ordering property of real hops. As a result, when a sequence of abstract hops is used in a path constraint, ordering is achieved among the groups of routers that meet a logical combination of link or node attributes called constituent attributes. A path can use a combination of real and abstract hops as constraints.
Options
abstract-hop-name | Name of the abstract hop that is a logical combination of the existing traffic engineering constraints, such as administrative groups, extended administrative groups, and SRLGs, along with the ordering property of real hops. |
constituent-list constituent-list-name | Name of the predefined constituent list to be included in defining the abstract hop. A constituent list enables you to define a set of constituent attributes that is identified with a user-defined name. |
include-any-list | Satisfy any one of the attributes specified in the constituent list. |
include-all-list | Satisfy all of the attributes specified in the constituent list. |
exclude-all-list | Satisfy none of the attributes specified in the constituent list. |
exclude-any-list | Fail to satisfy any one of the attributes specified in the constituent list. |
operators | Specify the operation between constituent lists when more than one constituent list is included in the abstract hop definition. |
AND | Satisfy all the constituent lists referenced in the abstract hop definition for the attached node to be a member of the abstract hop. |
OR | Satisy at least one of the constituent lists referenced in the abstract hop definition for the attached node to be a member of the abstract hop. |
Required Privilege Level
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 17.1.