TechLibrary

Navigation Back up to About Overview

Network Services Mode Overview

You can configure network services modes on MX Series 3D Universal Edge Routers and on T4000 Core Routers with Type 5 FPCs.

  • MX Series 3D Universal Edge Routers can be configured to run in IP Network Services mode, Enhanced IP Network Services mode, Ethernet Network Services mode, or Enhanced Ethernet Network Services mode. Each network services mode defines how the chassis recognizes and uses certain modules.

    You can use either Enhanced IP Network Services mode or Enhanced Ethernet Network Services mode to improve the scaling and performance specific to filters in a subscriber access network that uses statically configured subscriber interfaces. For more information about using enhanced network services modes with firewall filters, see Firewall Filters and Enhanced Network Services Mode Overview.

    Note: You can configure only the Ethernet Network Services mode or Enhanced Ethernet Network Services mode, if your router chassis contains an MPC module that is not of the -IR-B type or the -R-B type.

  • T4000 Core Routers with Type 5 FPCs can be configured to run in Enhanced Network Service mode to enable improved virtual private LAN service (VPLS) MAC address learning. For more information about using Enhanced Network Service mode for T4000 Core Routers with Type 5 FPCs, see enhanced-mode.

When configuring chassis network services on the MX Series 3D Universal Edge routers, keep the following considerations in mind:

  • You must configure a router chassis that has only MPC-3D-16XGE-SFPP modules installed for Ethernet Network Services mode or Enhanced Ethernet Network Services mode. If the router chassis has both MPC-3D-16XGE-SFPP and MPC-3D-16XGE-SFPP-R-B modules installed, only Ethernet Network Services mode or Enhanced Ethernet Network Services mode can be configured on the chassis.
  • You can configure a router chassis with only MPC-3D-16XGE-SFPP-R-B modules installed for any network services mode. However, this configuration requires installing the appropriate license if you want to use IP Network Services mode or Enhanced IP Network Services mode. The licenses for these services are paper licenses.
  • You can configure a router chassis with only MPC4E-3D-2CGE8XGE-IR-B, MPC4E-3D-32XGE-IR-B, MPC4E-3D-2CGE8XGE-R-B, or MPC4E-3D-32XGE-R-B modules installed for any network services mode.

    Note: The -IR-B type is applicable only for MPC4E modules.

Note: If Dense Port Concentrators (DPCs) in Ethernet Network Services mode or Enhanced Ethernet Network Services mode are up and running, you cannot configure the system for IP Network Services mode. You must first disable any Ethernet Network Services mode DPCs before switching to IP Network Services mode.

Note: Starting from Junos OS Release 13.3, you can configure the network services mode—Enhanced IP Network Services mode and Enhanced Ethernet Network Services mode—on MX240, MX480 and MX960 routers with an SCBE2 with the enhanced-ip option or the enhanced-ethernet option at the [edit chassis network-services] hierarchy level.

Table 1 explains the different module functions when you configure the MX Series 3D Universal Edge router chassis for different network services modes.

Table 1: Network Services Mode Functions

Configuration Upon Boot or Configuration Change

Module Function

IP Network Services mode (default; upon boot)

All modules except DPCE-X and DPCE-X-Q modules are powered on.

Starting with Junos OS Release 14.1, a router with Enhanced Ethernet Services DPCs (DPCE-X) and Enhanced Queuing Ethernet Services DPCs (DPCE-X-Q) modules is powered on by default. The default network services mode is IP Network Services mode if you do not configure a services mode on DPCE-X or DPCE-X-Q modules. Until Junos OS Release 13.3, all modules except DPCE-X and DPCE-X-Q modules are powered on, and DPCE-X or DPCE-X-Q modules are powered off by default.

Ethernet Network Services mode (upon boot)

All modules are powered on. However, operating in Ethernet Network Services mode restricts certain BGP protocol functions and does not support Layer 3 VPN, unicast RPF, and source and destination class usage (SCU and DCU) functions. In addition, the number of externally configured filter terms is restricted to 64K.

Ethernet Network Services mode provides support for only Layer 2.5 functions.

Enhanced IP Network Services mode (upon boot)

Only MPCs, MS-MPCs, and MS-DPCs are powered on.

Note: Only Multiservices DPCs (MS-DPCs) and MS-MPCs are powered on with the enhanced network services mode options. No other DPCs function with the enhanced network services mode options.

Enhanced Ethernet Network Services mode (upon boot)

Only MPCs, MS-MPCs, and MS-DPCs are powered on. All restrictions for operating in Ethernet Network Services mode apply.

Note: Only Multiservices DPCs (MS-DPCs) and MS-MPCs are powered on with the enhanced network services mode options. No other DPCs function with the enhanced network services mode options.

Change from IP Network Services mode to Ethernet Network Services mode

DPCE-X and DPCE-X-Q modules are powered on; no reboot is required. No impact to MPCs or MS-DPCs.

Change from Ethernet Network Services mode to IP Network Services mode

Invalid modification; no commit occurs; a warning message indicating any FPCs (along with their slot location) must be offline before switching to other network services; no impact to MPCs or MS-DPCs.

Change from Enhanced IP Network Services mode to Enhanced Ethernet Network Services mode

No reboot is required; no impact to MPCs or MS-DPCs.

Change from IP Network Services mode to Enhanced IP Network Services mode

Reboot required.

Change from Ethernet Network Services mode to Enhanced Ethernet Network Services mode

Reboot required.

The details of Layer 2.5 support for Ethernet Network Services mode are shown in Restrictions on Junos OS Ethernet Network Services Mode and Enhanced Ethernet Network Services Mode Features for MX Series Routers.

Network Services on SCBE2

The following scenarios are to be noted when you are using an MX Series router with an SCBE2:

  • You must configure the set chassis network-services (enhanced-ip | enhanced-ethernet) configuration command and reboot the router to bring up the FPCs on the router. However, after the router reboot the MS DPC, the MX FPC, and the ADPC are powered off.
  • All the FPCs and DPCs in the router are powered off when you reboot the router without configuring either the enhanced-ip option or the enhanced-ethernet option at the [edit chassis network-services] hierarchy level.
  • You must reboot the router when you configure or delete the enhanced-ip option or the enhanced-ethernet option at the [edit chassis network-services] hierarchy level. The following warning message is displayed when the enhanced-ip or the enhanced-ethernet configuration commands are configured or deleted at the [edit chassis network-services] hierarchy level, which prompts you to reboot the router.
    'chassis'
    WARNING: Chassis configuration for network services has been changed. A
    system reboot is mandatory. Please reboot the system NOW. Continuing without
    a reboot might result in unexpected system behavior.
    commit complete
  • Starting with Junos OS Release 14.2, if you configure or remove the enhanced-ip option or the enhanced-ethernet option at the [edit chassis network-services] hierarchy level on one of the Routing Engines on a router that contains dual Routing Engines, you must perform a commit synchronization of the settings between the two Routing Engines by entering the commit synchronize command at the [edit system] hierarchy level. In addition, you must reboot all of the Routing Engines on the router when the enhanced IP network services mode is changed to avoid unexpected system behavior.

Note: Dynamic multicast replication mode is supported on SCBE2. Static multicast replication mode is not supported on SCBE2.

Note: If a route’s next-hop is an unicast next-hop via IRB and the corresponding MAC address is learned over a LSI, the IRB will derive the L2 info from the indirect next-hop for the LSI. If you configure the load- balance per -packet policy statement, the indirect next-hop of the LSI will point to an unilist. The unilist will have all the member links to load balance the packets towards the MPLS cloud. The enhanced-ip option needs to be configured to enable the unicast next-hop for IRB to use the unilist as the L2-forwards next-hop and load balance the packets.

Published: 2015-01-26