Preprovisioning guidelines

The 7210 SAS platforms have a console port to connect terminals to the device. The Ethernet management port is supported.

Configure parameters from a system console connected to a console port, using Telnet to access the device remotely or SSH to open a secure shell connection.

Predefining entities

On 7210 SAS platforms, where cards/MDAs are not auto-provisioned, to initialize a card, the chassis slot, line card type, and MDA type must match the preprovisioned parameters. In this context, preprovisioning means to configure the entity type (such as the line card type, MDA type, port, and interface) that is planned for a chassis slot, line card, or MDA. Preprovisioned entities can be installed but not enabled or the slots can be configured but remain empty until populated. Provisioning means that the preprovisioned entity is installed and enabled.

You can:

  • provision the chassis to accept specific IMM cards on the 7210 SAS-R6 and 7210 SAS-R12

  • preprovision ports and interfaces after the line card and MDA types are specified.

  • install line cards in slots with no preconfiguration parameters specified. When the card is installed, the card and MDA types must be specified. This is required on 7210 SAS chassis-based platforms (7210 SAS-R6 and 7210 SAS-R12). On 7210 SAS platforms that do not support any removable cards or MDAs, the cards are preprovisioned for fixed ports.

  • install a line card in a slot provisioned for a different card type (the card will not initialize). The existing card and MDA configuration must be deleted and replaced with the current information. This is required on 7210 SAS chassis-based platforms (7210 SAS-R6 and 7210 SAS-R12). On 7210 SAS platforms that do not support any removable cards or MDAs, the MDAs are preprovisioned for all fixed ports.

Preprovisioning a port

On 7210 SAS chassis-based platforms (7210 SAS-R6 and 7210 SAS-R12), before a port can be configured, the slot must be preprovisioned with an allowed card type or the MDA must be preprovisioned with an allowed MDA type.

Some recommendations to configure a port include:

  • Ethernet

    • Configure an access port for customer facing traffic on which services are configured.

      An encapsulation type may be specified to distinguish services on the port or channel. Encapsulation types are not required for network ports.

      To configure an Ethernet access port, see Ethernet access port.

    • Configure a network port to participate in the service provider transport or infrastructure network.

      To configure an Ethernet network port, see Ethernet network port.

      Accounting policies can only be associated with network ports and Service Access Points (SAPs). Accounting policies are configured in the config>log>accounting-policy context.

When ports are preprovisioned, Link Aggregation Groups (LAGs) can be configured to increase the bandwidth available between two nodes. All physical links in a specific LAG combine to form one logical connection. A LAG also provides redundancy in case one or more links that participate in the LAG fail. For command syntax, see Configuring LAG parameters.