Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Routing and Interfaces for Master Logical Systems

 

Logical systems enables you to configure the interfaces, routing instances and the routing protocol. The master logical system administrator can display or clear the routing protocol parameters for all logical systems whereas the administrator for the user logical system can display or clear the protocol parameters for their own logical system. For more information, see the following topics:

Understanding Logical Systems Interfaces and Routing Instances

Logical interfaces on the device are allocated among the user logical systems by the master administrator. The user logical system administrator configures the attributes of the interfaces, including IP addresses, and assigns them to routing instances and zones.

A routing instance is a collection of routing tables, interfaces, and routing protocol parameters. There can be multiple routing tables for a single routing instance—for example, unicast IPv4, unicast IPv6, and multicast IPv4 routing tables can exist in a single routing instance. Routing protocol parameters and options control the information in the routing tables.

Interfaces and routing instances can be configured in the master logical system and in user logical systems. Configuring an interface or routing instance in a logical system is the same as configuring an interface or routing instance on a device that is not configured for logical systems. Any routing instance created within a logical system is only applicable to that logical system.

The default routing instance, master, refers to the main inet.0 routing table in the logical system. The master routing instance is reserved and cannot be specified as a routing instance. Routes are installed in the master routing instance by default, unless a routing instance is specified. Configure global routing options and protocols for the master routing instance by including statements at the [edit protocols] and [edit routing-options] hierarchy levels in the logical system.

You can configure only virtual router routing instance type in a user logical system. Only one virtual private LAN service (VPLS) routing instance type can be configured on the device and it must be in the interconnect logical system.

The user logical system administrator can configure and view all attributes for an interface or routing instance in a user logical system. All attributes of an interface or routing instance in a user logical system are also visible to the master administrator.

Multicast is a “one source, many destinations” method of traffic distribution, which means the destinations needing to receive the information from a particular source receive the traffic stream. The master and user logical system administrators can configure a logical system to support multicast applications. The same multicast configurations to configure a device as a node in a multicast network can be used in a logical system.

Example: Configuring Interfaces, Routing Instances, and Static Routes for the Master and Interconnect Logical Systems and Logical Tunnel Interfaces for the User Logical Systems (Master Administrators Only)

This topic covers configuration of interfaces, static routes, and routing instances for the master and interconnect logical systems. It also covers configuration of logical tunnel interfaces for user logical systems.

Requirements

The example uses an SRX5600 device running Junos operating system (Junos OS) with logical systems.

Before you begin:

Overview

This scenario shows how to configure interfaces for the logical systems on the device, including an interconnect logical system.

  • For the interconnect logical system, the example configures logical tunnel interfaces lt-0/0/0.0, lt-0/0/0.2, lt-0/0/0.4, and lt-0/0/0.6. The example configures a routing instance called vr-ic and assigns the interfaces to it.

    Because the interconnect logical system acts as a virtual switch, it is configured as a virtual private LAN service (VPLS) routing instance type. The interconnect logical system’s lt-0/0/0 interfaces are configured with ethernet-vpls as the encapsulation type. The corresponding peer lt-0/0/0 interfaces in the master and user logical systems are configured with Ethernet as the encapsulation type.

    • lt-0/0/0.0 connects to lt-0/0/0.1 on the root logical system.

    • lt-0/0/0.2 connects to lt-0/0/0.3 on the ls-product-design logical system.

    • lt-0/0/0.4 connects to lt-0/0/0.5 on the ls-marketing-dept logical system.

    • lt-0/0/0.6 connects to lt-0/0/0.7 on the ls-accounting-dept logical system.

  • For the master logical system, called root-logical-system, the example configures ge-0/0/4.0 and assigns it to the vr1-root routing instance. The example configures lt-0/0/0.1 to connect to lt-0/0/0.0 on the interconnect logical system and assigns it to the vr1-root routing instance. The example configures static routes to allow for communication with other logical systems and assigns them to the vr1-root routing instance.

  • For the ls-product-design logical system, the example configures lt-0/0/0.3 to connect to lt-0/0/0.2 on the interconnect logical system.

  • For the ls-marketing-dept logical system, the example configures lt-0/0/0.5 to connect to lt-0/0/0.4 on the interconnect logical system.

  • For the ls-accounting-dept logical system, the example configures lt-0/0/0.7 to connect to lt-0/0/0.6 on the interconnect logical system.

Figure 1 shows the topology for this deployment including virtual routers and their interfaces for all logical systems.

Figure 1: Configuring Logical Tunnel Interfaces, Logical Interfaces, and Virtual Routers
Configuring Logical Tunnel Interfaces,
Logical Interfaces, and Virtual Routers

Configuration

This topic explains how to configure interfaces for logical systems.

Configuring Logical Tunnel Interfaces and a Routing Instance for the Interconnect Logical System

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide.

To configure the interconnect system lt-0/0/0 interfaces and routing instances:

  1. Configure the lt-0/0/0 interfaces.
  2. Configure the routing instance for the interconnect logical system and add its lt-0/0/0 interfaces to it.

Results

From configuration mode, confirm your configuration by entering the show logical-systems interconnect-logical-system command. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring Interfaces, a Routing Instance, and Static Routes for the Master Logical System

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

To configure the master logical system interfaces:

  1. Configure the master (root) logical and lt-0/0/0.1 interfaces.
  2. Configure the interfaces for other logical systems to support VLAN tagging.
  3. Configure a routing instance for the master logical system, assign its interfaces to it, and configure static routes for it.

Results

From configuration mode, confirm your configuration by entering the show interfaces and show routing-instances commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Configuring Logical Tunnel Interfaces for the User Logical Systems

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode.

  1. Configure the lt-0/0/0 interface for the first user logical system:
  2. Configure the lt-0/0/0 interface for the second user logical system.
  3. Configure the lt-0/0/0 interface for the third user logical system.

Results

From configuration mode, confirm your configuration by entering the show logical-systems ls-product-design interfaces lt-0/0/0, show logical-systems ls-marketing-dept interfaces lt-0/0/0 , and show logical-systems ls-accounting-dept interfaces lt-0/0/0 commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

If you are done configuring the device, enter commit from configuration mode.

Verification

To confirm that the configuration is working properly, perform these tasks:

Verifying That the Static Routes Configured for the Master Administrator Are Correct

Purpose

Verify if you can send data from the master logical system to the other logical systems.

Action

From operational mode, use the ping command.

Example: Configuring OSPF Routing Protocol for the Master Logical Systems

This example shows how to configure OSPF for the master logical system.

Requirements

Before you begin:

Overview

In this example, you configure OSPF for the master logical system, called root-logical-system, shown in Example: Creating User Logical Systems, Their Administrators, Their Users, and an Interconnect Logical System.

This example enables OSPF routing on the ge-0/0/4.0 and lt-0/0/0.1 interfaces in the master logical system. You configure the following routing policies to export routes from the Junos OS routing table into OSPF in the vr1-root routing instance:

  • ospf-redist-direct—Routes learned from directly connected interfaces.

  • ospf-redist-static—Static routes.

  • ospf-to-ospf—Routes learned from OSPF.

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Step-by-Step Procedure

The following example requires you to navigate various levels in the configuration hierarchy. For instructions on how to do that, see Using the CLI Editor in Configuration Mode in the Junos OS CLI User Guide.

To configure OSPF for the master logical system:

  1. Log in to the master logical system as the master administrator and enter configuration mode.
  2. Create routing policies that accept routes.
  3. Apply the routing policies to routes exported from the Junos OS routing table into OSPF.
  4. Enable OSPF on the logical interfaces.

Results

From configuration mode, confirm your configuration by entering the show policy-options and show routing-instances commands. If the output does not display the intended configuration, repeat the configuration instructions in this example to correct it.

For brevity, this show command output includes only the configuration that is relevant to this example. Any other configuration on the system has been replaced with ellipses (...).

If you are done configuring the device, enter commit from configuration mode.

Verification

Confirm that the configuration is working properly.

Verifying OSPF Interfaces

Purpose

Verify OSPF-enabled interfaces.

Action

From the CLI, enter the show ospf interface instance vr1-root command.

admin@host> show ospf interface instance vr1-root

Verifying OSPF Neighbors

Purpose

Verify OSPF neighbors.

Action

From the CLI, enter the show ospf neighbor instance vr1-root command.

admin@host> show ospf neighbor instance vr1-root

Verifying OSPF Routes

Purpose

Verify OSPF routes.

Action

From the CLI, enter the show ospf route instance vr1-root command.

admin@host> show ospf route instance vr1-root