Preconfiguring Physical Interfaces

This module describes the preconfiguration of physical interfaces.

Preconfiguration is supported for these types of interfaces and controllers:

  • Gigabit Ethernet

  • 10-Gigabit Ethernet

  • 100-Gigabit Ethernet

  • Management Ethernet

Preconfiguration allows you to configure line cards before they are inserted into the router. When the cards are inserted, they are instantly configured. The preconfiguration information is created in a different system database tree, rather than with the regularly configured interfaces. That database tree is known as the preconfiguration directory on the route processor.

There may be some preconfiguration data that cannot be verified unless the line card is present, because the verifiers themselves run only on the line card. Such preconfiguration data is verified when the line card is inserted and the verifiers are initiated. A configuration is rejected if errors are found when the configuration is copied from the preconfiguration area to the active area.


Note

One Gigabit Ethernet interface is not supported. Only physical interfaces can be preconfigured.


Note

From Cisco IOS XR Release 6.3.2, a six-seconds delay is introduced in error propagation from the driver to DPA for the MACSec line card and Oldcastle platforms. As a result, the BER algorithm on these platforms knows the error with a delay of 6 seconds.

Physical Interface Preconfiguration Overview

Preconfiguration is the process of configuring interfaces before they are present in the system. Preconfigured interfaces are not verified or applied until the actual interface with the matching location (rack/slot/module) is inserted into the router. When the anticipated line card is inserted and the interfaces are created, the precreated configuration information is verified and, if successful, immediately applied to the running configuration of the router.


Note

When you plug the anticipated line card in, make sure to verify any preconfiguration with the appropriate show commands.

Use the show run command to see interfaces that are in the preconfigured state.


Note

We recommend filling out preconfiguration information in your site planning guide, so that you can compare that anticipated configuration with the actual preconfigured interfaces when that line card is installed and the interfaces are up.


Tip

Tip Use the commit best-effort command to save the preconfiguration to the running configuration file. The commit best-effort command merges the target configuration with the running configuration and commits only valid configuration (best effort). Some configuration might fail due to semantic errors, but the valid configuration still comes up.

Prerequisites for Preconfiguring Physical Interfaces

Before preconfiguring physical interfaces, ensure that this condition is met:

  • Preconfiguration drivers and files are installed. Although it may be possible to preconfigure physical interfaces without a preconfiguration driver installed, the preconfiguration files are required to set the interface definition file on the router that supplies the strings for valid interface names.

Benefits of Interface Preconfiguration

Preconfigurations reduce downtime when you add new cards to the system. With preconfiguration, the new cards can be instantly configured and actively running during cards bootup.

Another advantage of performing a preconfiguration is that during a cards replacement, when the cards is removed, you can still see the previous configuration and make modifications.

How to Preconfigure Physical Interfaces

This task describes only the most basic preconfiguration of an interface.

SUMMARY STEPS

  1. configure
  2. interface preconfigure type interface-path-id
  3. Use one of the following commands:
    • ipv4 address ip-address subnet-mask
    • ipv4 address ip-address/ prefix
  4. Configure additional interface parameters, as described in this manual in the configuration chapter that applies to the type of interface that you are configuring.
  5. end or commit best-effort
  6. show running-config

DETAILED STEPS

Step 1

configure

Example:


 RP/0/RP0/CPU0:router#configure

Enters global configuration mode.

Step 2

interface preconfigure type interface-path-id

Example:


RP/0/RP0/CPU0:router(config)# interface preconfigure HundredGigE 0/3/0/2

Enters interface preconfiguration mode for an interface, where type specifies the supported interface type that you want to configure and interface-path-id specifies the location where the interface will be located in rack/slot/module/port notation.

Step 3

Use one of the following commands:

  • ipv4 address ip-address subnet-mask
  • ipv4 address ip-address/ prefix

Example:


RP/0/RP0/CPU0:router(config-if-pre)# ipv4 address 192.168.1.2/31

Assigns an IP address and mask to the interface.

Step 4

Configure additional interface parameters, as described in this manual in the configuration chapter that applies to the type of interface that you are configuring.

Step 5

end or commit best-effort

Example:


RP/0/RP0/CPU0:router(config-if-pre)# end

or 


RP/0/RP0/CPU0:router(config-if-pre)# commit

Saves configuration changes.

  • When you issue the end command, the system prompts you to commit changes: 
Uncommitted changes found, commit them before exiting (yes/no/cancel)?

  • Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

  • Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

  • Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

  • Use the commit best-effort command to save the configuration changes to the running configuration file and remain within the configuration session. The commit best-effort command merges the target configuration with the running configuration and commits only valid changes (best effort). Some configuration changes might fail due to semantic errors.

Step 6

show running-config

Example:


RP/0/RP0/CPU0:router# show running-config

(Optional) Displays the configuration information currently running on the router.

Example

This example shows how to preconfigure a basic Ethernet interface: 


RP/0/RP0/CPU0:router# configure 
RP/0/RP0/CPU0:router(config)# interface preconfigure HundredGigE 0/0/1/0 
RP/0/RP0/CPU0:router(config-if)# ipv4 address 192.168.1.2/31 
RP/0/RP0/CPU0:router(config-if-pre)# commit

Information About Preconfiguring Physical Interfaces

NCS-57B1-6D24-SYS and NCS-57B1-5DSE-SYS have the following port-mapping characteristics:

  • All ports use QSFP-DD; however, the first 24 ports are 100G, and the last few ports (six for non-SE and five for SE) are 400G.

  • The two port types available are "400G Direct" port and "Quad Port Group".

  • Each port type supports one or more speeds and breakout modes, such as 400G/4x100G/2x100G/8x50G/100G/4x25G/40G/4x10G/10G.


Note

For specific transceiver support check the optics compatibility matrix.

400G Direct Ports

Ports 24-29 for non-SE and ports 24-28 for SE are 400G direct ports, which support 400G individually.

Table 1. Possible Optics and Breakout for 400G Direct Ports

Optics

Breakout

QSFP-DD 400G

4x100G, 8x50G

QSFP56 200G

2x100G, 4x50G

QSFP28-DD 2x100G

2x(4x25G)

QSFP28 100G

4x25G

QSFP+ 40G

4x10G

Configuration Examples

The following are some configuration examples. All possible combinations are not listed here.

Router(config)#controller optics 0/0/0/n breakout 4x100

Result: Hu0/0/0/n/0-3

Router(config)#controller optics 0/0/0/n breakout 8x50

Result: Fi0/0/0/n/0-7

Router(config)#controller optics 0/0/0/n breakout 2x100

Result: Hu0/0/0/n/0-1

Router(config)#controller optics 0/0/0/n breakout 4x25

Result: TF0/0/0/n/0-3

Router(config)#controller optics 0/0/0/n breakout 4x10

Result: Te0/0/0/n/0-3

Quad Port Groups

Quad port groups have the following characteristics:

  • There are six quad port groups of 4 QSFP-DD: (0,3), (4-7), (8-11), (12-15), (16-19), and (20-23).

  • Each group shares 400G.

  • Each port supports any combination of 40G/100G optics by default for a total of 400G per group.

  • Each group has two port pairs, for example (0,1) and (2,3) for group (0,3).

  • Breakout is only supported on the even (top) port of a port pair. The odd (bottom) port is automatically disabled. The odd port should be empty.

  • QSA is supported only on 100G QSFP-DD ports, not on 400G QSFP-DD ports.

  • Only 10G SFP+ optics are supported. There is no support for 1G.

  • Linear optics not supported.

  • For combinations with other optics type, see Quad Port Group table below, and consider 10G as one of the 40G optics.

  • 4x25G breakout cannot co-exist with 40G or 4x10G breakout in the same port group.

Table 2. Possible Optics and Breakout for Quad Port Groups

Port N

Port N+1

Port N+2

Port N+3

100G or 40G

100G or 40G

100G or 40G

100G or 40G

4x10G

Disabled

4x10G

Disabled

4x10G

Disabled

100G or 40G

100G or 40G

100G or 40G

100G or 40G

4x10G

Disabled

4x25G

Disabled

4x25G

Disabled

4x25G

Disabled

100G

100G

100G

100G

4x25G

Disabled

Configuration Examples

The following are some configuration examples. All possible combinations are not listed here.

  1. Quad Port Group in 4x10G breakout mode 

    Router(config)#hw-module port-range n n+1 location 0/RP0/CPU0 mode 4x10

    Results:

    • Te0/0/0/n/0-3: Port n+1 will be automatically disabled.

    • Fo0/0/0/n+2~n+3 or Hu0/0/0/n+2~n+3 Ports n+2 and n+3 by default will be either 40G or 100G.

    • For breakout in port n+2, a new breakout configuration is needed for port range n+2 n+3, as only top port n+2 supports breakout (bottom port n+3 is disabled) and cannot have a mix of 4x10G and 4x25G in the same port group.

  2. Quad Port Group in 4x25G breakout mode

    Router(config)#hw-module port-range n n+1 location 0/RP0/CPU0 mode 4x25

    Results (TF0/0/0/n/0-3 or Hu0/0/0/n+2~n+3):

    • Ports n+2 and n+3 can only be 100G.

    • For breakout in port n+2, a new breakout configuration is needed for port range n+2 n+3, as only top port n+2 supports breakout (bottom port n+3 is disabled) and cannot have a mix of 4x10G and 4x25G in the same port group.

To preconfigure interfaces, you must understand these concepts:

Use of the Interface Preconfigure Command

Interfaces that are not yet present in the system can be preconfigured with the interface preconfigure command in global configuration mode.

The interface preconfigure command places the router in interface configuration mode. Users should be able to add any possible interface commands. The verifiers registered for the preconfigured interfaces verify the configuration. The preconfiguration is complete when the user enters the end command, or any matching exit or global configuration mode command.


Note

It is possible that some configurations cannot be verified until the line card is inserted.

Do not enter the no shutdown command for new preconfigured interfaces, because the no form of this command removes the existing configuration, and there is no existing configuration.

Users are expected to provide names during preconfiguration that will match the name of the interface that will be created. If the interface names do not match, the preconfiguration cannot be applied when the interface is created. The interface names must begin with the interface type that is supported by the router and for which drivers have been installed. However, the slot, port, subinterface number, and channel interface number information cannot be validated.


Note

Specifying an interface name that already exists and is configured (or an abbreviated name like Hu0/3/0/0) is not permitted.