How to Build a Feeder Trunk between an MGX 8250 and an MGX 8850 [Cisco MGX 8800 Series Switches]

Document ID: 42609

Introduction
Prerequisites
      Conventions
      Requirements
      Components Used
Configure
      Network Diagram
      Configuring the MGX 8250
      Configuring the MGX 8850
Verify
Troubleshoot
NetPro Discussion Forums - Featured Conversations
Related Information

Introduction

This document provides a sample configuration to build a feeder trunk between a Cisco MGX 8250 switch and an MGX 8850 switch.

Prerequisites

Conventions

For more information on document conventions, refer to Cisco Technical Tips Conventions.

Requirements

Before you attempt this configuration, you should be knowledgeable of the MGX 8850 and the MGX 8250 (also known as MGX 8850 Release1).

Components Used

The information in this document is based on the software and hardware versions below.

MGX 8250 with a Processor Switch Module-1 (PXM1)—MGX 8850 Release 1
MGX 8850 with PXM-45 (Release 2) and Multiservice Switch Broadband ATM Switching Module (AXSM) cards

The information presented in this document was created from devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your are in a live network, ensure that you understand the potential impact of any command before you use it.

Configure

In this section, you are presented with the information to configure a feeder trunk between a Cisco MGX 8250 switch and an MGX 8850 switch.

Note: To find additional information on the commands used in this document, use the Command Lookup Tool ( registered customers only) .

Network Diagram

This document uses the network setup shown in the diagram below.

Configuring the MGX 8250

Complete these steps to configure the MGX 8250:

Use the addln command to add a line on the PXM back card.
```
mgx8250.1.7.PXM.a > addln -ds3 7.1
```

Use the dsplns and dspln commands to verify appropriate statistics for the added line:

mgx8250.1.7.PXM.a > dsplns -ds3 7 
Line Type           Status/Coding   Length        Criteria    AIScBitsChek 
---- -------------- --------------- ------------- ----------- ------------ 
1    dsx3CbitParity Ena / dsx3B3ZS  lessThan225   fBits3Of8   Check C-bits 
2    dsx3CbitParity Dis / dsx3B3ZS  lessThan225   fBits3Of8   Check C-bits 

mgx8250.1.7.PXM.a > dspln -ds3 7.1 
LineNum: 1 
LineType: dsx3CbitParity 
LineCoding: dsx3B3ZS 
LineLength: lessThan225 
LineOOFCriteria: fBits3Of8 
LineAIScBitsCheck: Check C-bits 
LineLoopbackCommand: NoLoop 
LineRcvFEACValidation: 4 out of 5 FEAC codes 
LineXmtFEACCode: SendNoCode 
FarEndLoopbkLineNum: 0 
LineEnable: Enabled 
LinePayloadScramble: Enabled

Use the upif command to enable the interface:

mgx8250.1.7.PXM.a > upif 
Syntax: upif "if_num line_num pct_bw min_vpi max_vpi" 
Interface Number -- a number 1..32 
Line Number -- a number 1..4 
Percent of Line Bandwidth -- a number 0..100 
Minimum VPI Value -- a number 0..4095 
Maximum VPI Value -- a number 0..4095 

mgx8250.1.7.PXM.a > upif 1 1 100 0 4095

Use the dspif command to verify that you enabled the interface:

mgx8250.1.7.PXM.a > dspif 1 

ifNum Status Line ingrPctBw egrPctBw minVpi maxVpi maxRatePct 
----- ------ ---- --------- -------- ------ ------ ---------- 
1     Ena    1    100       100      0      4095   100

Use the cnfswfunc command to configure the MGX 8250 node as a feeder:

Mgx8250.1.7.PXM.a > cnfswfunc 
Syntax: -vsvd <enable(yes)/disable(no)> 
-ndtype <routing/fdr> 
  
mgx8250.1.7.PXM.a > cnfswfunc -ndtype fdr

Use the dspswfunc command to verify that the node type is set to feeder:

mgx8250.1.7.PXM.a > dspswfunc 

1. ABR VSVD(enable(yes)/disable(no): NO 
2. Node Type(routing(routing)/Feeder(fdr): FDR

Use the cnfifastrk command to configure the trunk:
```
mgx8250.1.7.PXM.a > cnfifastrk 7.1 ftrk
```

Use the dsptrks command to verify that your trunk is configured and clear:

mgx8250.1.7.PXM.a > dsptrks 
TRK Current Alarm Status Other End 

7.1 CLEAR --

Configuring the MGX 8850

Complete these steps to configure the MGX 8850:

Use the upln command to add a line on the AXSM card:

mgx8850.12.AXSM.a > upln 
Err: Too few arguments. 
Syntax: upln "<bay.line>" 
Line Number -- format bay.line <bay:1-upper,2-lower, line:1 - 8> 

mgx8850.12.AXSM.a > upln 1.3

Use the dspatmln and dsplns commands to verify appropriate statistics for the added line:

mgx8850.12.AXSM.a > dspatmln 1.3
LineNum HCScoset PayloadScramble NullCellHdr NullCellPayload 
------- --------- --------------- ----------- --------------- 
1.3 Enable Enable 00000000 6a 
  
mgx8850.12.AXSM.a > dsplns 
Line Line    Line        Line        Length   OOF AIS  Alarm 
Num  State   Type        Lpbk        (meters) Criteria cBitsCheck State 
---- ------- ----------- ----------- ------   -------- ---------- ----- 
1.1  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.2  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.3  Up      ds3cbitadm  NoLoop      0        3Of8Bits Check      Critical 

1.4  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.5  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.6  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.7  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear

Use the cnfln command to clear a critical alarm with the help of the change in line type, if a line is not free of alarms:

mgx8850.12.AXSM.a > cnfln 
Syntax for ds3 line: 
=== to configure ds3 line === 
--- to configure T3 line --- 
cnfln "-ds3 <bay.line> -len <LineLength> -clk <clockSource> 
-lt <LineType> -oof <OOFCriteria> 
-cb <AIScBitsCheck> -rfeac <RcvFEACValidation>" 

mgx8850.12.AXSM.a > cnfln -ds3 1.3 -lt 2

Use the dsplns command to verify that the lines are free of alarms:

mgx8850.12.AXSM.a > dsplns 
Line Line    Line        Line        Length   OOF AIS  Alarm 
Num  State   Type        Lpbk        (meters) Criteria cBitsCheck State 
---- ------- ----------- ----------- ------   -------- ---------- ----- 
1.1  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.2  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.3  Up      ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.4  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.5  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.6  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear 
1.7  Down    ds3cbitadm  NoLoop      0        3Of8Bits Check      Clear

Use the addport command to add a port on the AXSM:

mgx8850.12.AXSM.a > addport 
Syntax: addport "<ifNum> <bay.line> <guaranteedRate> <maxRate> <sctID> <ifType> 
[vpi]" 
If Number -- number between 1 and 60 
Line Number -- format bay.line 
Guaranteed virtual int. Rate -- rates in cells/sec: 
Max virtual int. Rate -- for OC48:between 50 and 5651320 
for OC12:between 50 and 1412830 
for OC3:between 50 and 353207 
for T3:between 50 and 96000(PLCP),104268(ADM) 
for E3:between 50 and 80000 
SctID -- Port SCT Id between 0 and 255, for default file use 0 
IfType -- 1: uni 2: nni 3: vnni 
vpiNum -- vpi between 1 and 4095: 
used for configuring interface as virtual trunk 

mgx8850.12.AXSM.a > addport 13 1.3 100000 100000 0 1

Use the dspports command to verify your added port on the AXSM:

mgx8850.12.AXSM.a > dspports
ifNum Line Admin Oper. Guaranteed Maximum   SCT Id ifType  VPI   
           State State Rate       Rate     (D:dflt        (VNNI 
                                            used)          only)
----- ---- ----- ----- ---------- --------- ------ ------ ------ 
   13  1.3    Up    Up     100000   100000  0       UNI     0

Use the addpart command to add the partition for the port:

mgx8850.12.AXSM.a > addpart 

Syntax: addpart/addrscprtn "ifNum partId cntlrId egrminbw egrmaxbw ingminbw 
ingmaxbw minVpi maxVpi minVci maxVci minConns maxConns" 
If Number -- number between 1 and 60 
Partition Number -- Partition Identifier between 1 and 5 
Controller Number -- Controller Identifier between 1 and 20 
Egr guaranteed % Bandwidth -- units:0.0001% of interface bandwidth 
Egr max % Bandwidth -- units:0.0001% of interface bandwidth 
Ing guaranteed % Bandwidth -- units:0.0001% of interface bandwidth 
Ing max % Bandwidth -- units:0.0001% of interface bandwidth 
Minimum VPI Value -- number between 0 and 4095(0..255 for UNI interface 
Maximum VPI Value -- number between 0 and 4095(0..255 for UNI interface 
Minimum VCI Value -- number between 1 and 65535 
Maximum VCI Value -- number between 1 and 65535 
Guaranteed #conns -- between 0 and max #conns in portgroup,see dspcd for portgroup info 
Max. #conns -- between 0 and max #conns in portgroup,see dspcd for portgroup info 
  

mgx8850.12.AXSM.a > addpart 13 1 2 1000000 1000000 1000000 1000000 0 255 35 65535 2000 8000

Use the dsppart command to verify the added partition:

mgx8850.12.AXSM.a > dsppart 13 1 
Interface Number : 13 
Partition Id : 1 Number of SPVC: 0 
Controller Id : 2 Number of SPVP: 0 
egr Guaranteed bw(.0001percent): 1000000 Number of SVC : 0 
egr Maximum bw(.0001percent) : 1000000 
ing Guaranteed bw(.0001percent): 1000000 
ing Maximum bw(.0001percent) : 1000000 
min vpi : 0 
max vpi : 255 
min vci : 35 
max vci : 65535 
guaranteed connections : 2000 
maximum connections : 8000

Use the addcontroller command to add a controller on the PXM, if it is not already added:

Mgx8850.7.PXM.a > addcontroller 
ERR: Syntax: addcontroller <cntrlrId> i <cntrlrType> <slot> [cntrlrName] 
addcontroller <cntrlrId> x <cntrlrType> <slot> <bay> <line> 
<vpi> <vci> [cntrlrName] 
cntrlrId - [1-20]; i - internal; x - external; 
cntrlrIds 1..3 are reserved for PAR, PNNI and LSC respectively. 
cntrlrtype - 1:PAR, 2:PNNI, 3:LSC; slot - [1-16]; bay - [1-2]; 
line - card dependent; vpi - [1-255]; vci - [1-65536]; 
cntrlrName - optional 
  

mgx8850.7.PXM.a > addcontroller 2 i 2 7 PNNI

Use the dspcontrollers command to verify the added controller:

mgx8850.7.PXM.a > dspcontrollers 
mgx8850 System Rev: 02.01 Oct. 14, 2002 12:38:49 GMT 
MGX8850 Node Alarm: CRITICAL 
Number of Controllers: 1 
Controller Name: PNNI 
Controller Id: 2 
Controller Location: Internal 
Controller Type: PNNI 
Controller Logical Slot: 7 
Controller Bay Number: 0 
Controller Line Number: 0 
Controller VPI: 0 
Controller VCI: 0 
Controller In Alarm: NO 
Controller Error:

Use the dsppnports command to verify the port signaling:

mgx8850.7.PXM.a > dsppnports 

Type <CR> to continue, Q<CR> to stop: 
DSPPNPORTSPer-port status summary 

PortId LogicalId IF status Admin status ILMI state #Conns 

7.35 17251107 up up NotApplicable 0 

7.36 17251108 up up NotApplicable 0 

7.37 17251109 up up NotApplicable 0 

7.38 17251110 up up NotApplicable 0 

12:1.3:13 17569805 auto config up Disable 0 
  

mgx8850.7.PXM.a > dsppnportsig 12:1.3:13 

provisioned IF-type: uni version: uni3.1 <---by default 
sigType: private side: network 
addrPlan: aesa 
VpiVciAllocator: n/a HopCounterGen: n/a 
PassAlongCapab: n/a 
sigVpi: 0 sigVci: 5 
rccVpi: n/a rccVci: n/a

Note: The default port signaling is uni3.1; however, if you want to add the feeder trunk, you should reconfigure the port signaling.

Use the cnfpnportsig command to enable IP communications between the switch and feeder.

Note: The port must be down before you use the cnfpnportsig command. If the port is not down, use the dnpnport command to bring the port down.
```
mgx8850.7.PXM.a > cnfpnportsig 12:1.3:13 -cntlvc ip 
```
Use the uppnport command to bring the configured port up, and use the dsppnportsig command to verify the port signaling:
```
mgx8850.7.PXM.a > uppnport 12:1.3:13 

mgx8850.7.PXM.a > dsppnportsig 12:1.3:13 

type: ip 
sigVpi: 3 sigVci: 8
```
Use the addfdr command to add the feeder:
```
mgx8850.12.AXSM.a > addfdr 13
```
Note: The Interim Link Management Interface (ILMI) must be disabled on the port in order to add the feeder. By default, the ILMI is disabled. Use the dspilmi command to verify the ILMI status:
```
mgx8850.12.AXSM.a > dspilmi 13 1 

Sig. rsrc Ilmi  Sig  Sig  Ilmi S:Keepalive  T:conPoll  K:conPoll 
Port Part State Vpi  Vci  Trap Interval     Interval   InactiveFactor 
---- ---- ----  ---- ---- ---  ------------ ---------- ---------- 
13   1    Off   0    16   On   1             5         4
```
Note: If the ILMI is enabled, you receive an error message when you use the addfdr command.You must use the dnilmi command to disable the ILMI first:
```
mgx8850.12.AXSM.a > addfdr 13 
ERR: ILMI is enabled so LMI can't be added 

mgx8850.12.AXSM.a > dnilmi 13 1 

mgx8850.12.AXSM.a > addfdr 13
```
Note: The addfdr command is blocked if connections have been defined on the interface. You must delete the connections if connections have been defined.

Use the dspfdrs command to verify the added feeder:

mgx8850.12.AXSM.a > dspfdrs 
IF Remote Remote Rmt Rmt LMI LMI LMI 
No. Name IP Slot Port Admin Oper Alarms 
--- ------- ------------ ----- ----- ----- ---- ------ 
13 mgx8250 10.170.200.137 7 1 Up Up Clear

Use the dsptrks command to verify the configuration on the MGX 8250 side:
```
Mgx8250.1.7.PXM.a > dsptrks 
TRK Current Alarm Status Other End 

7.1 CLEAR mgx8850
```
You have added the feeder trunk successfully.

Verify

There is currently no verification procedure available for this configuration.

Troubleshoot

There is currently no specific troubleshooting information available for this configuration.

NetPro Discussion Forums - Featured Conversations

Networking Professionals Connection is a forum for networking professionals to share questions, suggestions, and information about networking solutions, products, and technologies. The featured links are some of the most recent conversations available in this technology.

NetPro Discussion Forums - Featured Conversations for WAN

Network Infrastructure: WAN, Routing, and Switching

Related Information

Updated: Apr 30, 2009

Document ID: 42609

Hierarchical Navigation

Cisco MGX 8800 Series Switches