Cisco Systems MGX 8230 Sequence of Configuration Tasks, Rules for Adding Connections

6-2

Cisco MGX 8230 Edge Concentrator Installation and Configuration

Release 1.1.31, Part Number 78-11215-03 Rev. B0, May 2001

Chapter6 Card and Service Configuration

Sequence of Configuration Tasks

logical interface are available to any controller o n a first- co m e , first- s er ved basi s. If necessary, you can

modify the resources for a cont r ol ler a t the card level and logical port level. Por t -level r eso ur ce

modification follows card-level modificatio n, s o th e avail ab le po rt- level re sou r ces d ep en d o n wh et h er

and how much you change the card-level resource partitioning. You do not have to change the resource

partitioning for the car d befo re chan gin g re sour ce pa rt itio ni ng fo r a port .

The current network control application is Portable AutoRoute (PAR). Planning considerations should

include the possibility of m o di fyin g th e partitioning of resources for th e in te rface. For example, the

MGX 8230 has the capaci ty t o s u p po r t a C isco Multiprotocol Label S w it ch in g (M P LS ) c ontroller or a

Private Network to Network Interface (PNNI) controller.

Note There is no need to partition MGX 8230 service module resources i n th is release of the MGX 8230

BPX feeder.

Sequence of Configuration Tasks

In a new MGX 8230, the common appro ach i s t o c onfi gu re the sa me asp ect for all card s at on ce—adding

logical ports, for example. In con trast, the likely sequence for inst alling a new or replacement card is to

begin with the card-level features and c on ti nue until you have added every connection. Th e co m mo n

tasks for a new MGX 8230 are:

1. Activate physical lines.

2. Optionally configure the line if default parameters are not appropriate.

3. Create the logical ports then mo di fy a s needed the logical ports.

4. Optionally configure resource partiti ons for a l ogical port if the de fault partit ionin g does not su pport

the intended operation of the port . (With th is re le ase of MGX 8230 BPX feeder, there is no need to

partition resources.)

5. Add connections, then modify as needed individual connections.

Rules for Adding Connections

This section describes the rul es f o r a ddi ng local connections, three-seg m en t c on n ect io ns, and

management connections. The MGX 8230 can support

•Local-only, digital access cross-connect (DAX) c onn ect ions

•Three-segment connections across an ATM or Frame Relay network

As a preface to the steps for ad di ng c on n ect io ns, this section describes the ap p lic ab le rules for these

connections. Although the ru les in clu d e r ef er en c e s to C LI syntax, they also apply to th e Cisco WAN

Manager application.

A DAX con is a connection whose endpoin ts for the entire connection exist on the same MGX 8230. The

following apply to the MGX 8230:

1. On a feeder, a DAX con can exist betwee n differen t service modules or within the s ame service

module.