Junos OS Features That Are Supported on Logical Systems

• Open Shortest Path First (OSPF), Intermediate System-to-Intermediate System (IS-IS), Routing Information Protocol (RIP), RIP next generation (RIPng), Border Gateway Protocol (BGP), Resource Reservation Protocol (RSVP), Label Distribution Protocol (LDP), static routes, and Internet Protocol version 4 (IPv4) and version 6 (IPv6).
• Multiprotocol Label Switching (MPLS) provider edge (PE) and core provider router functions, such as Layer 2 virtual private networks (VPNs), Layer 3 VPNs, circuit cross-connect (CCC), Layer 2 circuits, and virtual private LAN service (VPLS).
• Resource Reservation Protocol (RSVP) point-to-multipoint label-switched paths (LSPs).
• Multicast protocols, such as Protocol Independent Multicast (PIM), Distance Vector Multicast Routing Protocol (DVMRP), rendezvous point (RP), and source designated router (DR).
• All policy-related statements available at the [edit policy-options] hierarchy level.
• Most routing options statements available at the [edit routing-options] hierarchy level.
• Graceful Routing Engine switchover (GRES). Configure graceful Routing Engine switchover on the main router with the graceful-switchover statement at the [edit chassis redundancy] hierarchy level.
• Graceful restart. Include the graceful-restart statement at the [edit logical-systems logical-system-name routing-options] hierarchy level.
• You can assign most interface types to a logical system. For a list of unsupported PICs, see Logical Systems Operations and Restrictions.
• Flow aggregation in logical systems is supported starting in Junos OS Release 11.4. In the logical system, sampling based on the Routing Engine is not supported. Only PIC-based sampling is supported. Logical systems support only cflowd version 9. Currently, cflowd version 5 and cflowd version 8 are not supported in logical systems. Flow aggregation in logical systems is slightly different from flow aggregation on the main router in that when you configure flow aggregation in logical systems, the route-record statement is not required.
• Port mirroring, source class usage, destination class usage, unicast reverse-path forwarding, class of service, firewall filters, class-based forwarding, and policy-based accounting work with logical systems when you configure these features on the main router.
• The Simple Network Management Protocol (SNMP) has been extended to support logical systems and routing instances. A network management system receives instance-aware information in the following format:
  logical-system-name/routing-instance@community

  As a result, a network manager can gather statistics for a specific community within a routing instance within a logical system. The SNMP manager for a routing instance can request and manage SNMP data only for that routing instance and other routing instances in the same logical system. By default, the SNMP manager for the default routing instance in the main router (inet.0) can access SNMP data from all routing instances. To restrict that manager’s access to the default routing instance only, include the routing-instance-access statement at the [edit snmp] hierarchy level.

• Support for system logging at the [edit logical-system logical-system-name system syslog] hierarchy level is introduced in Junos OS Release 11.4.