 |
Note: The options for logical system and routing instance precede the topology statement with the then statement. |
- topology topology-name;
- [edit firewall family (inet | inet6) filter filter-name term term-name then],
- [edit firewall family (inet | inet6) filter filter-name term term-name then logical-system logical-system-name],
- [edit firewall family (inet | inet6) filter filter-name term term-name then logical-system logical-system-name routing-instance routing-instance-name],
- [edit firewall family (inet | inet6) filter filter-name term term-name then routing-instance routing-instance-name]
Statement introduced in JUNOS Release 9.0.
Configure a topology for filter-based forwarding for Multitopology Routing. The firewall filter you apply to the ingress interface is used to look up traffic against the configured topology, and, if a route matches the conditions you configure for the term, the route is accepted and added to the to the routing table for the specific topology.
There are multiple ways to configure a topology for filter-based forwarding, depending on the type of instance or logical system you want to specify for the forwarding class. See Options for more information.
|
Note: The options for logical system and routing instance precede the topology statement with the then statement. |
topology-name—Name of a topology against which you want to match traffic.
logical-system logical-system-name topology topology-name—For a nonmaster logical system, specify the name of the logical system and a topology name configured for a nonmaster logical system.
routing-instance routing-instance-name topology topology-name—For a nonmaster routing instance, specify the name of the routing instance and a topology name configured for a nonmaster routing instance.
logical-system logical-system-name routing-instance routing-instance-name topology topology-name—For a nonmaster routing instance configured within a nonmaster logical system, specify the name of the logical system, the name of the routing instance, and a topology name configured for a nonmaster routing instance within a nonmaster logical system.
See Configuring Filter-Based Forwarding for Multitopology Routing.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
JUNOS Policy Framework Configuration Guide
- topology topology-name;
- [edit logical-systems logical-system-name topologies family (inet | inet6)],
- [edit logical-systems logical-system-name routing-instances routing-instance-name topologies
family (inet | inet6)],
- [edit routing-instances routing-instance-name topologies family (inet | inet6)],
- [edit routing-options topologies family (inet | inet6)]
Statement introduced in JUNOS Release 9.0.
Configure the name of a topology configured to run Multitopology Routing.
topology-name—Name of the topology. Include a string value that describes the type of traffic, such as voice or video. For IPv4 multicast traffic, include ipv4-multicast as the name.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
- topology (default | ipv4-multicast | name) {
- topology-id number;
-
- spf-options {
- delay milliseconds;
- holddown milliseconds;
- rapid-runs number;
- }
- }
- [edit logical-systems logical-system-name protocols ospf],
- [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ospf],
- [edit protocols ospf],
- [edit routing-instances routing-instance-name protocols ospf]
Statement introduced in JUNOS Release 9.0.
Enable a topology for OSPF Multitopology Routing. You must first configure one or more topologies under the [edit routing-options] hierarchy level.
default—Name of the default topology. This topology is automatically created and all routes that correspond to it are automatically added to the inet.0 routing table. You can modify certain default parameters, such as for the shortest-path-first (SPF) algorithm.
ipv4-multicast—Name of the topology for IPv4 multicast traffic.
name—Name of a topology you configured under the [edit routing-options] hierarchy level to create a topology for a specific type of traffic, such a voice or video.
See Configuring Topologies and SPF Options for MT-OSPF.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
- topology (ipv4-multicast | name) {
- metric metric;
- }
- [edit logical-systems logical-system-name protocols ospf area area-id interface interface-name],
- [edit logical-systems logical-system-name routing-instances routing-instance-name protocols
ospf area area-id interface interface-name],
- [edit protocols ospf area area-id interface interface-name],
- [edit routing-instances routing-instance-name protocols ospf area area-id interface interface-name]
Statement introduced in JUNOS Release 9.0.
Configure interface-specific properties for MT-OSPF, including topology-specific metric values for an interface.
The default value of the topology metric is the same as the default metric value calculated by OSPF or the value configured for the OSPF metric.
ipv4-multicast—Name of the topology for IPv4 multicast traffic.
name—Name of a topology created under the [edit routing-options] hierarchy level.
metric metric—Cost of a route from an OSPF interface. You can specify a metric value for a topology that is different from the value specified for the interface.
See Configuring Interface Properties for MT-OSPF.
routing—To view this statement in the configuration.
routing-control—To add this statement to the configuration.
 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |