Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?


topology (Protocols BGP)


Hierarchy Level


Enable a topology for BGP multitopology routing. You must first configure one or more topologies under the [edit routing-options] hierarchy level.

Apply the community tags to identify the application topologies by configuring a routing topology name and BGP community value.

In Junos OS, multitopology support for BGP is based on the community value in a BGP route. This configuration determines the association between a topology and one or more community values and populates the topology routing tables. Arriving BGP updates that have a matching community value are replicated in the associated topology routing table. You decide which BGP community values are associated with a given topology.

For example, you can create a configuration that causes BGP updates that are received with community value target:40:40 to be added into topology routing table voice.inet.0 (in addition to the default routing table inet.0). Likewise, you configuration can specify that updates that are received with community value target:50:50 are added into topology routing table video.inet.0 (in addition to the default routing table inet.0).



Name of a topology you configured at the [edit routing-options] hierarchy level to create a topology for a specific type of traffic, such as voice or video.


Configure the community to identify the multitopology routes. BGP uses the target community identifier to install the routes it learns in the appropriate multitopology routing tables.

  • Syntax: target identifier—Configure the destination to which the route is going.

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 9.0.