Getting started

About this guide

This guide describes system concepts and provides configuration examples to provision Input/Output modules (IOMs), XMA Control Modules (XCMs), also referred to as cards, Media Dependent Adapters (MDAs), XRS Media Adapters (XMAs), and ports.

Note: Unless otherwise indicated, this guide uses classic CLI command syntax and configuration examples.

This guide is organized into functional chapters and provides concepts and descriptions of the implementation flow, as well as Command Line Interface (CLI) syntax and command usage.

The topics and commands described in this document apply to the:

  • 7450 ESS

  • 7750 SR

  • 7950 XRS

  • Virtualized Service Router

For a list of unsupported features by platform and chassis, see the SR OS R22.x.Rx Software Release Notes, part number 3HE 18412 000 x TQZZA.

Command outputs shown in this guide are examples only; actual displays may differ depending on supported functionality and user configuration.

Note:

The SR OS CLI trees and command descriptions can be found in the following guides:

  • 7450 ESS, 7750 SR, 7950 XRS, and VSR Classic CLI Command Reference Guide

  • 7450 ESS, 7750 SR, 7950 XRS, and VSR Clear, Monitor, Show, and Tools Command Reference Guide (for both MD-CLI and Classic CLI)

  • 7450 ESS, 7750 SR, 7950 XRS, and VSR MD-CLI Command Reference Guide

Note:

This guide generically covers Release 22.x.Rx content and may contain some content that will be released in later maintenance loads. See the SR OS R22.x.Rx Software Release Notes, part number 3HE 18412 000 x TQZZA for information about features supported in each load of the Release 22.x.Rx software.

Interface configuration process

Configuration process lists the tasks necessary to configure IOMs and XCMs (also referred to as cards), MDAs and XMAs, and ports.

Note: For consistency across platforms, XMAs are modeled in the SR OS (CLI and SNMP) as MDAs.

Unless specified otherwise:

  • the term ‟card” is used generically to refer to both IOMs and XCMs

  • the term ‟MDA” is used generically to refer to both MDAs and XMAs

Table 1. Configuration process
Area Task Section

Provisioning

Chassis slots and cards

Chassis slots and card slots

MDAs

MDA-a, MDA-aXP, MDA, MDA-e, and MDA-s modules

Ports

Ports

Interface Configuration

MTU Configuration

MTU configuration guidelines

Configure fabric speed

Setting fabric speed

Preprovisioning

Preprovisioning guidelines

Configure cards and MDAs

Configuring cards and MDAs

Configure ports

Configuring ports

Service management

Service management tasks

Conventions

This section describes the general conventions used in this guide.

Precautionary and information messages

The following are information symbols used in the documentation.

DANGER: Danger warns that the described activity or situation may result in serious personal injury or death. An electric shock hazard could exist. Before you begin work on this equipment, be aware of hazards involving electrical circuitry, be familiar with networking environments, and implement accident prevention procedures.
WARNING: Warning indicates that the described activity or situation may, or will, cause equipment damage, serious performance problems, or loss of data.
Caution: Caution indicates that the described activity or situation may reduce your component or system performance.
Note: Note provides additional operational information.
Tip: Tip provides suggestions for use or best practices.

Options or substeps in procedures and sequential workflows

Options in a procedure or a sequential workflow are indicated by a bulleted list. In the following example, at step 1, the user must perform the described action. At step 2, the user must perform one of the listed options to complete the step.

Options in a procedure

  1. User must perform this step.
  2. This step offers three options. User must perform one option to complete this step.
    • This is one option.
    • This is another option.
    • This is yet another option.

Substeps in a procedure or a sequential workflow are indicated by letters. In the following example, at step 1, the user must perform the described action. At step 2, the user must perform two substeps (a. and b.) to complete the step.

Substeps in a procedure

  1. User must perform this step.
  2. User must perform all substeps to complete this action.
    1. This is one substep.
    2. This is another substep.