Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Logical Systems Operations and Restrictions

• You can configure a maximum of 15 logical systems plus the master logical system on a routing device. When a configuration session is in use, users who are tied to the same logical system cannot commit configuration changes.
• The routing device has only one running configuration database, which contains configuration information for the main routing device and all associated logical systems. When configuring a logical system, a user has his own candidate configuration database, which does not become part of the running configuration database until the user issues the commit command.
• Configuring the out-of-band management interface, such as em0 or fxp0, in a logical system is not supported.
• Some high availability features are not supported on logical systems. These features include non-stop routing (NSR), non-stop bridging (NSB), and unified in-service software upgrade (unified ISSU). Graceful restart is supported. For a logical system, include the graceful-restart statement at the [edit logical-systems logical-system-name routing-options] hierarchy level.
• The following guidelines describe how firewall filters affect the main routing device, logical systems, and virtual routers. The "default loopback interface" refers to lo0.0 (associated with the default routing table), the “loopback interface in a logical system” refers to lo0.n configured in the logical system, and the “loopback interface in the virtual router” refers to lo0.n configured in the virtual router.

  If you configure Filter A on the default loopback interface in the main routing device but do not configure a filter on the loopback interface in a logical system, the logical system does not use a filter.

  If you configure Filter A on the default loopback interface in the main routing device but do not configure a loopback interface in a logical system, the logical system uses Filter A.

  If you configure Filter A on the default loopback interface on the main routing device and Filter B on the loopback interface in a logical system, the logical system uses Filter B. In a special case of this rule, when you also configure a routing instance of type virtual-router on the logical system, the following rules apply:

  • If you configure Filter C on the loopback interface in the virtual router, traffic belonging to the virtual router uses Filter C.
  • If you do not configure a filter on the loopback interface in the virtual router, traffic belonging to the virtual router does not use a filter.
  • If you do not configure a loopback interface in the virtual router, traffic belonging to the virtual router uses Filter A.
• If a logical system experiences an interruption of its routing protocol process (rpd), the core dump output is placed in /var/tmp/ in a file called rpd_logical-system-name.core-tarball.number.tgz. Likewise, if you issue the restart routing command in a logical system, only the routing protocol process (rpd) for the logical system is restarted.
• If you configure trace options for a logical system, the output log file is stored in the following location: /var/log/logical-system-name. To monitor a log file within a logical system, issue the monitor start logical-system-name/filename command.
• The following PICs are not supported with logical systems: Adaptive Services, Multiservices, ES, Monitoring Services, and Monitoring Services II.
• Generalized MPLS (GMPLS), IP Security (IPsec), and sampling are not supported.
• Ethernet VPN (EVPN) is not supported on logical systems (even if it is available in the CLI, the commit check will fail).
• Class of service (CoS) on a logical tunnel (lt) or virtual loopback tunnel (vt) interface in a logical system is not supported.
• You cannot include the vrf-table-label statement on multiple logical systems if the core-facing interfaces are channelized or configured with multiple logical interfaces (Frame Relay DLCIs or Ethernet VLANs).
• The master administrator must configure global interface properties and physical interface properties at the [edit interfaces] hierarchy level. Logical system administrators can only configure and verify configurations for the logical systems to which they are assigned.
• You can configure only Frame Relay interface encapsulation on a logical tunnel interface (lt-) when it is configured with an IPv6 address.
• IPv6 tunneling is not supported with point-to-multipoint label-switched paths (LSPs) configured on logical systems.
• IGMP snooping is not supported.
• BGP MVPNs, and draft-rosen multicast VPNs, are not supported in logical systems (even though the configuration statements may be configurable under the logical-systems hierarchy).
• If you configure virtual private LAN service (VPLS) for a logical system, the no-tunnel-services statement is visible but not supported on DPC cards.
• In a VPLS multihoming scenario in which a logical tunnel interface (lt-) is used for connecting the dual-home VPLS, Junos OS creates a unique static MAC address for every logical tunnel interface configured. This MAC address is not flushed when a CCC down event occurs on the link and when traffic is switched from the primary link to the backup link (or the reverse). As a result, any traffic that is destined for hosts behind the logical tunnel MAC address does not take the new path.