Cisco 12816 Router Configuration Guide

Cisco 12000 Series Router SIP and SPA

Software Configuration Guide (Cisco IOS)

December 10, 2008

Americas Headquarters

Cisco Systems, Inc.

170 West Tasman Drive

San Jose, CA 95134-1706

USA http://www.cisco.com

800 553-NETS (6387)

Text Part Number: OL-8832-01, Rev. C9

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL

STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT

WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT

SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE

OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH

ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT

LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF

DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,

WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO

OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,

WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO

OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To

You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems,

Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing,

FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace,

MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet,

Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS)

Copyright © 2008 Cisco Systems, Inc. All rights reserved.

C O N T E N T S

Preface

xv

Document Change History

xv

Objectives

xvii

Organization

xviii

Related Documentation

xix

Cisco 12000 Series Router Documentation

xix

Cisco IOS Software Publications

xx

Cisco IOS Release 12.0 S Software Publications

xx

Document Conventions

xx

Obtaining Documentation and Submitting a Service Request

xxi

xxi

Shared Port Adapters

Using Cisco IOS Software

1-1

Accessing the CLI Using a Router Console

1-1

Accessing the CLI Using a Directly-Connected Console

1-1

Accessing the CLI from a Remote Console Using Telnet

1-3

Accessing the CLI From a Remote Console Using a Modem

1-4

Using Keyboard Shortcuts

1-4

Using the History Buffer to Recall Commands

1-5

Understanding Command Modes

1-5

Getting Help

1-7

Example: How to Find Command Options

1-7

Using the no and default Forms of Commands

1-10

Saving Configuration Changes

1-11

Filtering Output from the show and more Commands

1-11

Finding Support Information for Platforms and Cisco IOS Software Images

1-12

Using Cisco Feature Navigator

1-12

Using Software Advisor

1-12

Using Software Release Notes

1-12

SIP and SPA Product Overview

2-1

Introduction to SIPs and SPAs

2-1

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS)

Release 12.0(33)S, OL-8832-01, Rev. C9 iii

Contents iv

SPA Interface Processors

2-1

Shared Port Adapters

2-2

SFP and XFP Optics Modules

2-3

SIP and SPA Compatibility

2-5

Overview of the Cisco 12000 Series Router SIPs

3-1

Release History

3-1

Supported Features

3-2

Cisco 12000 SIP-401, Cisco 12000 SIP-501, Cisco 12000 SIP-600, and Cisco 12000 SIP-601

Features

3-2

Cisco 12000 SIP-400 Features

3-4

Key Features

3-4

Supported MIBs

3-6

Displaying the SPA Hardware Type

3-9

Example of the show gsr Command

3-10

Gigabit Ethernet Shared Port Adapters

Overview of the Gigabit Ethernet SPAs

4-1

Release History

4-1

Supported Features

4-2

Gigabit Ethernet SPA Features

4-2

Supported MIBs

4-3

SPA Architecture

4-4

Path of a Packet in the Ingress Direction

4-4

Path of a Packet in the Egress Direction

4-4


4-4

Example of the show interfaces Command

4-5

Configuring the Fast Ethernet and Gigabit Ethernet SPAs

5-1

Configuration Tasks

5-1

Required Configuration Tasks

5-2

Specifying the Interface Address

5-4

Modifying the MAC Address on the Interface

5-5

Gathering MAC Address Accounting Statistics

5-6

Configuring HSRP

5-6

Modifying the Interface MTU Size

5-7

Configuring the Encapsulation Type

5-9

Configuring Autonegotiation on an Interface

5-9

Configuring a Subinterface on a VLAN

5-10


Release 12.0(33)S, OL-8832-01, Rev. C9

Contents

Configuring Flow Control Support on the Link

5-11

Saving the Configuration

5-12

Shutting Down and Restarting an Interface on a SPA

5-12

Verifying the Interface Configuration

5-12

Verifying Per-Port Interface Status

5-13

Configuration Examples

5-14

Basic Interface Configuration Example

5-14

MAC Address Configuration Example

5-15

MTU Configuration Example

5-15

VLAN Configuration Example

5-16

Configuring Dense Wavelength Division Multiplexing Controllers on Cisco IOS Software

5-16

Contents

5-17

Prerequisites for Configuring DWDM Controller Interfaces

5-17

Information About the DWDM Controllers

5-17

How to Configure DWDM Controllers

5-18

Configuring the Optical Parameters

5-18

Configuring G.709 Parameters

5-20

Examples

5-21

Additional References

5-21

Standards

5-22

MIBs

5-22

RFCs

5-22

Technical Assistance

5-22

Troubleshooting the Gigabit Ethernet SPA

6-1

General Troubleshooting Information

6-1

Using show Commands

6-2

Performing Basic Interface Troubleshooting

6-2

Verifying the Interface is Up

6-4

Verifying the Line Protocol is Up

6-5

Verifying Output Hang Status

6-5

Verifying the CRC Counter

6-5

Verifying Late Collisions

6-5

Verifying the Carrier Signal

6-5

Understanding SPA Automatic Recovery

6-6

When Automatic Recovery Occurs

6-6

If Automatic Recovery Fails

6-6

Configuring the Interface for Internal Loopback

6-7

Configuring the Interface for Internal Loopback

6-7


Release 12.0(33)S, OL-8832-01, Rev. C9 v

Contents vi

Configuring the Interface for External Loopback

6-7

Verifying Loopback Status

6-7

Using the Cisco IOS Event Tracer to Troubleshoot Problems

6-8

Preparing for Online Insertion and Removal of a SPA

6-8

Cleaning Optics

6-8

Command Summary for Gigabit Ethernet SPAs

7-1

Serial Shared Port Adapters

Overview of the Serial SPAs

8-1

Release History

8-1

Supported Features

8-1

SIP-400 Features

8-2

SPA Features

8-2

Restrictions

8-4

Supported MIBs

8-4


8-5

Example of the show interface Command

8-6

Configuring the 2-Port and 4-Port Channelized T3 SPA

9-1

Configuration Tasks

9-1


9-2

Specifying the Interface Address on a SPA

9-7

Optional Configurations

9-8


9-18


9-18


9-18


9-20

DSU Configuration Example

9-21

MDL Configuration Example

9-21

Encapsulation Configuration Example

9-21

Framing - Unchannelized Mode Configuration Example

9-22

Facility Data Link Configuration Example

9-22

Scrambling Configuration Example

9-22

Configuring the 2-Port and 4-Port T3/E3 SPAs

10-1

Configuration Tasks

10-1


10-2


10-7


Release 12.0(33)S, OL-8832-01, Rev. C9

Contents


10-8


10-18


10-18


10-18


10-20

DSU Configuration Example

10-21

MDL Configuration Example

10-21


10-21

Framing - Unchannelized Mode Configuration Example

10-22


10-22

Scrambling Configuration Example

10-22

Configuring the 8-Port Channelized T1/E1 SPA

11-1

Configuration Tasks

11-1


11-1


11-6


11-6


11-17


11-18


11-18


11-18

Framing and Encapsulation Configuration Example

11-19

CRC Configuration Example

11-19


11-20

MLPPP Configuration Example

11-20

MFR Configuration Example

11-21

Invert Data on the T1/E1 Interface Example

11-22

Configuring the 1-Port Channelized OC-3/STM-1 SPA

12-1

Configuration Tasks

12-1


12-1

Selection of Physical Port and Controller configuration

12-2


12-12


12-21


12-21


12-21

Command Summary for Serial SPAs

13-1

Packet over SONET Shared Port Adapters


Release 12.0(33)S, OL-8832-01, Rev. C9 vii

Contents viii

Overview of the POS SPAs

14-1

Release History

14-1

POS Technology Overview

14-2

Supported Features

14-3

SONET/SDH Compliance Features

14-3

SONET/SDH Error, Alarm, and Performance Monitoring Features

14-4

SONET/SDH Synchronization Features

14-4

WAN Protocol Features

14-5

Network Management Features

14-5

Restrictions

14-5

Supported MIBs

14-7

SPA Architecture

14-8

1-Port OC-192c/STM-64 POS/RPR XFP SPA Architecture

14-8

1-Port OC-192c/STM-64 POS/RPR SPA and 1-Port OC-192c/STM-64 POS/RPR XFP SPA

Architecture

14-9

2-Port OC-48c/STM-16 POS SPA Architecture

14-11


14-12

Example of the show interfaces Command

14-12

Example of the show diags Command

14-13

Example of the show controllers Command

14-14

Configuring the POS SPAs

15-1

Configuration Tasks

15-1


15-2


15-3

Modifying the Interface MTU Size

15-4

Modifying the POS Framing

15-5

Modifying the Keepalive Interval

15-7

Modifying the CRC Size

15-7

Modifying the Clock Source

15-8

Modifying SONET Payload Scrambling

15-9

Configuring the Encapsulation Type

15-10

Configuring APS

15-11

Configuring POS Alarm Trigger Delays

15-12

Configuring SDCC

15-15

Configuring Dynamic Packet Transport Features

15-16


15-22

Shutting Down and Restarting an Interface on a SPA

15-22


15-22


Release 12.0(33)S, OL-8832-01, Rev. C9

Contents


15-23

Monitoring Per-Port Interface Statistics

15-23


15-24

Basic Interface Configuration Example

15-25

MTU Configuration Example

15-25

POS Framing Configuration Example

15-26

Keepalive Configuration Example

15-26

CRC Configuration Example

15-26

Clock Source Configuration Example

15-27

SONET Payload Scrambling Configuration Example

15-27


15-27

APS Configuration Example

15-27

POS Alarm Trigger Delays Configuration Example

15-29

SDCC Configuration Example

15-29

SRP Configuration Example

15-29

Command Summary for the POS SPAs

16-1

Field-Programmable Devices

Upgrading Field-Programmable Devices

17-1

Release History

17-1

FPD Quick Upgrade

17-2

FPD Quick Upgrade Before Upgrading your Cisco IOS Release (Recommended)

17-2

FPD Quick Upgrade After Upgrading your Cisco IOS Release

17-2

Overview of FPD Images and Packages

17-3

Upgrading FPD Images

17-3

Migrating to a Newer Cisco IOS Release

17-3

Upgrading FPD Images in a Production System

17-5

Optional FPD Procedures

17-6

FPD Image Upgrade Examples

17-12

Troubleshooting Problems with FPD Image Upgrades

17-14

Power Failure or Removal of a SPA During an FPD Image Upgrade

17-14

Command Summary for FPDs

18-1

SIP and SPA Command Reference

19-1

G L O S S A R Y

I

N D E X

Release 12.0(33)S, OL-8832-01, Rev. C9

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS) ix

Contents x


Release 12.0(33)S, OL-8832-01, Rev. C9

Figure 2-1

Figure 2-2

Figure 5-1

Figure 5-2

Figure 14-1

Figure 14-2

Figure 14-3

Figure 15-1

F I G U R E S

Single-height and Double-height SPA Sizes

2

Horizontal and Vertical Chassis Slot Orientation for SPAs

2

Slot, Subslot, and Port Locations for the Cisco 10-port Gigabit Ethernet SPA and the 1-Port 10-Gigabit Ethernet

SPA.

5

OTN Optical Channel Structure 17

1-Port OC-192c/STM-64 POS/RPR XFP SPA Architecture 8

1-Port OC-192c/STM-64 POS/RPR XFP SPA Architecture 9

2-Port OC-48c/STM-16 POS SPA Architecture 11

Basic APS Configuration 28

Release 12.0(33)S, OL-8832-01, Rev. C9

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS) xi

Figures xii


Release 12.0(33)S, OL-8832-01, Rev. C9

T A B L E S

Table 14-1

Table 14-2

Table 16-1

Table 17-1

Table 18-1

Table 19-1

Table 19-2

Table 19-3

Table 19-4

Table 19-5

Table 19-6

Table 19-7

Table 19-8

Table 19-9

Table 1

Table 1-1

Table 1-2

Table 1-3

Table 1-4

Table 2-1

Table 2-2

Table 2-3

Table 3-1

Table 4-1

Table 4-2

Table 5-1

Table 6-1

Table 7-1

Table 8-1

Table 13-1

Document Change History Table xv

Keyboard Shortcuts

5

History Substitution Commands

5

Accessing and Exiting Command Modes

6

How to Find Command Options

8

SFP Modules

3

SPA Optics Compatibility

3

SIP and SPA Compatibility on the Cisco 12000 Series Router

5

SPA Hardware Descriptions in show Commands

10

Release History for Ethernet SPAs

1


5

Slot and Port Locations for the Gigabit Ethernet SPAs

5

Basic Interface Troubleshooting Steps

3

Command Summary

1


5

Command Summary

1

POS Feature Compatibility and Restrictions by SIP and SPA Combination

6


12

Command Summary for POS SPAs

1

FPD Release History

1

FPD Command Summary

1

Interface Type Keywords

41 show controllers pos Field Descriptions

73 show controllers pos pm Field Descriptions

76 show controllers pos pm Field Descriptions

78 show controllers serial Field Descriptions

84 show diag (AIC) Field Descriptions

92 show diag (AIM-VPN) Field Descriptions

94 show diag subslot Field Descriptions

94

Operational Status Field Descriptions

103


Release 12.0(33)S, OL-8832-01, Rev. C9 xiii

Tables

Table 19-10

Table 19-11

Table 19-12

Table 19-13

Table 19-14

Table 19-15

Table 19-16

Table 19-17

Table 19-18

Table 19-19

Table 19-20

Table 19-21

Table 19-22

Table 19-23

Table 19-24

Table 19-25

Table 19-26

Table 19-27

Table 28

show interface sdcc

Field Descriptions 109

show interfaces pos

Field Descriptions 116 show interfaces serial Field Descriptions—Synchronous Serial Interface 123 show interfaces serial Field Descriptions—PA-2JT2 Serial Interface 126

show interfaces serial

Field Descriptions—PA-E3 127 show interfaces serial Field Descriptions—PA-T3 128


Field Descriptions—CT3IP 129


Field Descriptions—Frame Relay Interface Queueing and Fragmentation 132 show interfaces serial Field Descriptions—ANSI LMI 134 show interfaces serial Field Descriptions—LAPB 134 show interfaces serial Field Descriptions—PPP Encapsulation 135 show interfaces serial Field Descriptions—SDLC Enabled 136

SDLC Secondary Interface Descriptions 136

SDLLC Parameter Descriptions 137 show interfaces serial Field Descriptions—X.25 Enabled 138


Field Descriptions—Accounting 140 show interfaces serial Field Descriptions—Cisco AS5800 140

T3/E3 SPA—Command Field Descriptions 141

Relationship Between duplex and speed Commands 155 xiv


Release 12.0(33)S, OL-8832-01, Rev. C9

Preface

Revised: Release 12.0(33)S, OL-8832-01, Rev. C9

This preface describes the objectives and organization of this document and explains how to find additional information on related products and services. This preface contains the following sections:

•

•

•

•

•

Document Change History, page xv

Objectives, page xvii

Organization, page xviii

Related Documentation, page xix

Document Conventions, page xx

Document Change History

Table 1 provides a list of the changes to this document.

Table 1 Document Change History Table

Release No.

12.0(31)S

12.0(31)S2

Revision

Release

12.0(31)S

Release

12.0(31)S2

Date

April 26, 2005

Change Summary

Initial release and 1st publication. Provides Cisco IOS commands and configuration procedures for the following SPAs installed in a

Cisco 12000 SIP-400 or a Cisco 12000 SIP-600:

• 1-Port 10-Gigabit Ethernet SPA

•

•

•

•

5-Port 10 Gigabit Ethernet SPA

10-Port Gigabit Ethernet SPA

2-Port and 4-Port Clear Channel T3/E3 SPA

2-Port and 4-Port Channelized T3 SPA

•

•

1-Port OC-192c/STM-64 POS/RPR SPA

September 22, 2005 Support for the following hardware by the Cisco 12000 SIP-600 was introduced on the Cisco 12000 series router:

2-Port OC-48c/STM-16 POS SPA

Release 12.0(33)S, OL-8832-01, Rev. C9

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS) xv

Preface

Release No.

12.0(32)S

Table 1

Revision

Release

12.0(32)S

12.0(32)SY Release

12.0(32)SY

Document Change History Table (continued)

Date

January 20, 2006

June 26, 2006

Change Summary

Support for the following SPA interface processor (SIP) hardware was introduced on the Cisco 12000 series routers:

•

•

•

Cisco 12000 SIP-401

Cisco 12000 SIP-501

Cisco 12000 SIP-601

Support for the following SPAs with the SIP 401/501/601 was introduced on Cisco 12000 series routers:


•

•

8-Port FastEthernet SPA


Support for the following hardware by the Cisco 12000 SIP-601 was introduced on the Cisco 12000 series router:

• 1-Port OC-192c/STM-64 POS/RPR SPA

• 1-Port OC-192c/STM-64 POS/RPR XFP SPA

Support for the following hardware by the Cisco 12000 SIP-501 and

Cisco 12000 SIP-601 was introduced on the Cisco 12000 series router:

•

•


Support for the following hardware by the Cisco 12000 SIP-401,

Cisco 12000 SIP-501 and Cisco 12000 SIP-601 was introduced on the Cisco 12000 series router:

8-Port Fast Ethernet SPA (SPA-8X1FE-TX-V2)

•

•

•

•

•

1-Port 10-Gigabit Ethernet SPA (SPA-1X10GE-L-V2)

2-Port Gigabit Ethernet SPA (SPA-2X1GE-V2)

5-Port Gigabit Ethernet SPA (SPA-5x1GE-V2)

10-Port Gigabit Ethernet SPA (SPA-10X1GE-V2)

•

•

•

2-Port OC-3c/STM-1 and OC-12c/STM-4 POS SPA




• 8-Port OC-3c/STM-1 POS SPA



• 1-Port OC-48c/STM-16 POS SPA xvi


Release 12.0(33)S, OL-8832-01, Rev. C9

Preface

Release No.

12.0(32)SY6

Table 1

Revision

Release

12.0(32)SY6

12.0(33)S

12.0(33)S2

Release

12.0(33)S

Release

12.0(33)S2

Document Change History Table (continued)

Date

May 7, 2008

April 26, 2007

Change Summary

Added a starting and ending <time-interval> argument for the command show controllers pos on a Cisco 12000 series router or on a POS Shared Port Adapter.

Command output displays the POS interface details for each of the time-intervals between the specified range. Command output changes applicable for Cisco 12000 series router or for a POS

Shared Port Adapter.

Support for the following hardware by the Cisco 12000 SIP-600 and the Cisco 12000 SIP-601 was introduced on the Cisco 12000 series router:

•

•

1-Port 10-Gigabit Ethernet SPA [WAN-PHY]

(SPA-1X10GE-WL-V2)

1-Port 10-Gigabit Ethernet DWDM SPA

(SPA-1X10GE-L-ITUC)


Cisco 12000 SIP-501 and Cisco 12000 SIP-601 was introduced on the Cisco 12000 series router:

• 8-Port Gigabit Ethernet SPA (SPA-8X1GE-V2)




Information specific to BERT configuration for the following SPAs was introduced:

• 2-Port and 4-Port Channelized T3 SPA

•

•

8-Port Channelized T1/E1 SPA

1-Port Channelized OC-3/STM-1 SPA

November 10, 2008 Added following flowcontrol commands supported on Cisco IOS

Release 12.0(33)S2 on Cisco 12000 series router for Engine 5

SIP-401/501/600/601 line card and applicable on GE or FE SPA interfaces:

• show interfaces flowcontrol

•

• flowcontrol bidirectional no flowcontrol bidirectional

Objectives

This document describes the configuration and troubleshooting of SPA interface processors (SIPs) and shared port adapters (SPAs) that are supported on a Cisco 12000 Series Router.

Release 12.0(33)S, OL-8832-01, Rev. C9

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS) xvii

Preface

Organization

This document contains the following chapters:

Chapter

Part 1

Title

Shared Port Adapters

Chapter 1 Using Cisco IOS Software

Chapter 2 SIP and SPA Product Overview

Description

Covers IOS Software and SIP and SPA overview.

Provides an introduction to accessing the command-line interface (CLI) and using the Cisco

IOS Software and related tools.

Provides an introduction to modular services cards

(SIPs) and shared port adapters (SPAs).

Chapter 3

Chapter 7

Overview of the Cisco 12000

Series Router SIPs

Command Summary for Gigabit

Ethernet SPAs

Provides an overview of the release history, and feature and Management Information Base (MIB) support for the SIPs supported on the Cisco 12000

Series Routers.

Covers Gigabit Ethernet SPA Configuration.

Part 2

Chapter 4

Gigabit Ethernet Shared Port

Adapters

Overview of the Gigabit Ethernet

SPAs

Chapter 5 Configuring the Fast Ethernet and

Gigabit Ethernet SPAs

Chapter 6 Troubleshooting the

Gigabit Ethernet SPA

Provides an overview of the release history, and feature and Management Information Base (MIB) support for the Gigabit Ethernet SPAs on the Cisco

12000 series router.

Describes how to configure the Gigabit Ethernet

SPAs on the Cisco 12000 Series Router.

This chapter describes techniques that you can use to troubleshoot the operation of your GigabitEthernet

SPAs.

Provides an alphabetical list of the most significant commands that are needed to configure, monitor, and maintain the Fast Ethernet and Gigabit Ethernet shared port adapter (SPA) cards.

Part 3

Chapter 8

Serial Shared Port Adapters

Overview of the Serial SPAs

Covers Serial SPAs.

Provides an overview of the release history, features, and MIBs for the 2 and 4-Port T3/E3 SPA and the 2 or 4-Port CT3 SPA.

Chapter 9 Configuring the 2-Port and 4-Port

Channelized T3 SPA

Provides information about configuring the 2-Port and 4-Port Channelized T3 Shared Port Adapters

(SPAs) on the Cisco 12000 series routers.

Chapter 10 Configuring the 2-Port and 4-Port

T3/E3 SPAs

Provides information about configuring the 2-Port and 4-Port T3/E3 Shared Port Adapters (SPAs) on the

Cisco 12000 Series routers.

Chapter 13 Command Summary for Serial

SPAs

Part 4 Packet over SONET Shared Port

Adapters

Provides an alphabetical list of some of the related commands to configure, monitor, and maintain Serial

SPAs.

Covers POS SPAs.

xviii


Release 12.0(33)S, OL-8832-01, Rev. C9

Preface

Chapter Title

Chapter 14 Chapter 14, “Overview of the POS

SPAs”

Description

Provides an overview of the release history, and feature and Management Information Base (MIB) support for the Packet over SONET (POS) SPAs on the Cisco 12000 Series Router.

Chapter 15 Configuring the POS SPAs

Chapter 16

Part 5

Command Summary for the POS

SPAs

Field-Programmable Devices

Chapter 17 Upgrading Field-Programmable

Devices

Provides information about configuring the Packet over SONET (POS) SPAs on the Cisco 12000

SIP-600 series routers.

Provides an alphabetical list of some of the related commands to configure, monitor, and maintain POS

SPAs.

Covers FPDs.

Provides information about upgrading the

Field-Programmable Gate Array (FPGA) on the

Cisco 12000 Series Router.

Chapter 18 Command Summary for FPDs

Provides an alphabetical list of some of the related commands to configure, monitor, and upgrade FPD images for SPAs on the Cisco 12000 Series Router.

Chapter 19 SIP and SPA Command Reference

Describes Cisco IOS software command reference information including syntax, usage guidelines, and examples for all new and modified commands for

SPAs on a Cisco 12000 Series Router.

Related Documentation

This section refers you to other documentation that also might be useful as you configure your

Cisco 12000 Series Router. The documentation listed below is available online.

• Cisco 12000 Series Router SIP and SPA Hardware Installation Guide

•

•

•

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS)

Cross-Platform Release Notes for Cisco IOS Release 12.0 S

Regulatory Compliance and Safety Information for Cisco 12000 Series Routerss

Cisco 12000 Series Router Documentation

As you configure SIPs and SPAs on your Cisco 12000 Series Router, you should also refer to the following companion publication for important hardware installation information:

• Cisco 12000 Series Router SIP and SPA Hardware Installation Guide

Some of the other Cisco 12000 Series Router publications might be useful to you as you configure your

Cisco 12000 Series Router. The following URL provides a wide range of documentation for the various

Cisco 12000 Series Routers and their accompanying field replaceable units (FRUs): http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/

Several other publications are also related to the Cisco 12000 Series Router. For a complete reference of related documentation, refer to the various roadmap documents located at the following URL:

Release 12.0(33)S, OL-8832-01, Rev. C9

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS) xix

Preface http://www.cisco.com/univercd/cc/td/doc/product/core/cis12000/roadmap/

Cisco IOS Software Publications

Your router, switch, or gateway and the Cisco IOS software running on it contain extensive features. You can find documentation for Cisco IOS software features at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/

Cisco IOS Release 12.0 S Software Publications

Documentation for Cisco IOS Release 12.0 S, including release notes and system error messages, can be found at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/

Document Conventions

Within the SIP and SPA software configuration guides, the term router is generally used to refer to a variety of Cisco products (for example, routers, access servers, and switches). Routers, access servers, and other networking devices that support Cisco IOS software are shown interchangeably within examples. These products are used only for illustrative purposes; that is, an example that shows one product does not necessarily indicate that other products are not supported.

This documentation uses the following conventions:

Convention

^ or Ctrl string

Convention bold italics

[x]

|

[x | y]

{x | y}

Description

The ^ and Ctrl symbols represent the Control key. For example, the key combination ^D or Ctrl-D means hold down the Control key while you press the D key. Keys are indicated in capital letters but are not case sensitive.

A string is a nonquoted set of characters shown in italics. For example, when setting an SNMP community string to public , do not use quotation marks around the string or the string will include the quotation marks.

Command syntax descriptions use the following conventions:

Description

Bold text indicates commands and keywords that you enter literally as shown.

Italic text indicates arguments for which you supply values.

Square brackets enclose an optional element (keyword or argument).

A vertical line indicates a choice within an optional or required set of keywords or arguments.

Square brackets enclosing keywords or arguments separated by a vertical line indicate an optional choice.

Braces enclosing keywords or arguments separated by a vertical line indicate a required choice.

xx


Release 12.0(33)S, OL-8832-01, Rev. C9

Preface

Convention

[x {y | z}]

Convention screen bold screen

< >

!

[ ]

Nested sets of square brackets or braces indicate optional or required choices within optional or required elements. For example:

Description

Braces and a vertical line within square brackets indicate a required choice within an optional element.

Examples use the following conventions:

Description

Examples of information displayed on the screen are set in Courier font.

Examples of text that you must enter are set in Courier bold font.

Angle brackets enclose text that is not printed to the screen, such as passwords.

An exclamation point at the beginning of a line indicates a comment line. (Exclamation points are also displayed by the Cisco IOS software for certain processes.)

Square brackets enclose default responses to system prompts.

The following conventions are used to attract the attention of the reader:

Caution Means reader be careful . In this situation, you might do something that could result in equipment damage or loss of data.

Note Means reader take note . Notes contain helpful suggestions or references to materials not contained in this manual.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation , which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Release 12.0(33)S, OL-8832-01, Rev. C9

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS) xxi

Preface xxii


Release 12.0(33)S, OL-8832-01, Rev. C9

P A R T 1


Using Cisco IOS Software

C H A P T E R

1

This chapter provides useful information as you prepare to configure a shared port adapter (SPA) using the Cisco IOS software. It includes the following sections:

•

•

•

•

•

•

•

•

•

Accessing the CLI Using a Router Console, page 1-1

Using Keyboard Shortcuts, page 1-4

Using the History Buffer to Recall Commands, page 1-5

Understanding Command Modes, page 1-5

Getting Help, page 1-7

Using the no and default Forms of Commands, page 1-10

Saving Configuration Changes, page 1-11

Filtering Output from the show and more Commands, page 1-11

Finding Support Information for Platforms and Cisco IOS Software Images, page 1-12

Accessing the CLI Using a Router Console

This section describes how to access the command-line interface (CLI) using a directly-connected console or by using Telnet to obtain a remote console:

•

Accessing the CLI Using a Directly-Connected Console, page 1-1

•

•

Accessing the CLI from a Remote Console Using Telnet, page 1-3

Accessing the CLI From a Remote Console Using a Modem, page 1-4

For more detailed information about configuring and accessing a router through various services, refer to the Cisco IOS Terminal Services Configuration Guide and Cisco IOS Terminal Services Command

Reference publications.

For more information about making the console cable connections, refer to the Cisco 12000 Series

Router SIP and SPA Hardware Installation Guide .

Accessing the CLI Using a Directly-Connected Console

This section describes how to connect to the console port on the router and use the console interface to access the CLI.


1-1 Release 12.0(33)S, OL-8832-01, Rev. C9

Chapter 1 Using Cisco IOS Software


Connecting to the Console Port

Before you can use the console interface on the router using a terminal or PC, perform the following steps:

Step 1 Configure your terminal emulation software with the following settings:

•

•

•

•

9600 bits per second (bps)

8 data bits

No parity

2 stop bits

Note These are the default serial communication parameters on the router. For information about how to change those defaults to meet the requirements of your terminal or host, refer to the Cisco IOS Terminal

Services Configuration Guide .

Step 2 Connect a terminal or PC to the console port using a rollover cable.

To make this connection, attach one end of an RJ-45 to RJ-45 rollover cable to the router console port.

Attach the other end of the cable to an ASCII terminal or a PC running terminal emulation software. The

ASCII terminal or PC port might require an RJ-45-to-DB-9 or an RJ-45-to-DB-25 adapter.

Using the Console Interface

To access the CLI using the console interface, complete the following steps:

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

After you attach the terminal hardware to the console port on the router (and have configured your terminal emulation software with the proper settings), the following prompt appears:

Press Return for Console prompt

Press Return to enter user EXEC configuration mode. The following prompt appears:

Router>

From user EXEC configuration mode, enter the enable command as shown in the following example:

Router> enable

At the password prompt, enter your system’s password. The following example shows entry of the password called “enablepass”:

Password: < enablepass >

When the enable password is accepted, the privileged EXEC configuration mode prompt appears:

Router#

You now have access to the CLI in privileged EXEC configuration mode and you can enter the necessary commands to complete your desired tasks.

To exit the console session, enter the quit command as shown in the following example:

Router# quit

1-2


Release 12.0(33)S, OL-8832-01, Rev. C9



Accessing the CLI from a Remote Console Using Telnet

This section describes how to connect to the console interface on a router using Telnet to access the CLI.

Preparing to Connect to the Router Console Using Telnet

Before you can access the router remotely using Telnet from a TCP/IP network, you need to configure the router to support virtual terminal lines (vtys) using the line vty global configuration command. You also should configure the vty lines to require login and specify a password.

Note To prevent disabling login on the line, be careful that you specify a password with the password command when you configure the login line configuration command. If you are using authentication, authorization, and accounting (AAA), you should configure the login authentication line configuration command. To prevent disabling login on the line for AAA authentication when you configure a list with the login authentication command, then you must also configure that list using the aaa authentication login global configuration command. For more information about AAA services, refer to the Cisco IOS

Security Configuration Guide and Cisco IOS Security Command Reference publications.

In addition, before you can make a Telnet connection to the router you must have a valid host name for the router, or have an IP address configured on the router. For more information about requirements for connecting to the router using Telnet, information about customizing your Telnet services, and using

Telnet key sequences, refer to the Cisco IOS Terminal Services Configuration Guide.

Using Telnet to Access a Console Interface

To access a console interface using Telnet, complete the following steps:

Step 1 From your terminal or PC, enter one of the following commands:

•

• connect host [ port ] [ keyword telnet host [ port ] [ keyword ]

] where host is the router host name or an IP address, port is a decimal port number (23 is the default), and keyword is a supported keyword. For more information, refer to the Cisco IOS Terminal Services

Command Reference .

Note If you are using an access server, then you also will need to specify a valid port number with the host name or IP address, such as telnet 172.20.52.40 2003 .

The following example shows the telnet command to connect to the router named Router: unix_host% telnet Router

Trying 172.20.52.40...

Connected to 172.20.52.40.

Escape character is '^]'.

unix_host% connect

Release 12.0(33)S, OL-8832-01, Rev. C9


1-3


Using Keyboard Shortcuts

Step 2 At the password prompt, enter your login password. The following example shows entry of the password called “mypass”:

User Access Verification

Password: < mypass >

Note If no password has been configured, press Return .

Step 3

Step 4

Step 5

Step 6

From user EXEC configuration mode, enter the enable command as shown in the following example:

Router> enable

When the enable password is accepted, the privileged EXEC configuration mode prompt appears:

Router#

You now have access to the CLI in privileged EXEC configuration mode and you can enter the necessary commands to complete your desired tasks.

To exit the Telnet session, use the exit or logout command as shown in the following example:

Router# logout

Accessing the CLI From a Remote Console Using a Modem

To access the router remotely using a modem through an asynchronous connection, you need to configure the AUX port and attach a modem to it.

For more information about making a modem connection using the AUX port on the Cisco 12000 Series

Router, refer to the Cisco 12000 Series Router SIP and SPA Hardware Installation Guide .

For detailed guidelines on making a connection to the router using a modem, and using reverse Telnet, refer to Configuring a Modem on the AUX Port for EXEC Dialin Connectivity located at the following

URL: http://www.cisco.com/warp/public/471/mod-aux-exec.html

Using Keyboard Shortcuts

Commands are not case sensitive. You can abbreviate commands and parameters if the abbreviations contain enough letters to be different from any other currently available commands or parameters. You can scroll through the last 20 commands stored in the history buffer, and enter or edit the command at the prompt.

1-4


Release 12.0(33)S, OL-8832-01, Rev. C9


Using the History Buffer to Recall Commands

Table 1-1 lists the keyboard shortcuts for entering and editing commands.

Table 1-1 Keyboard Shortcuts

Keystrokes

Press Ctrl-B or press the left arrow key

1

Press Ctrl-F or press the right arrow key

1

Press Ctrl-A

Press Ctrl-E

Press Esc B

Press Esc F

Purpose

Move the cursor back one character

Move the cursor forward one character

Move the cursor to the beginning of the command line

Move the cursor to the end of the command line

Move the cursor back one word

Move the cursor forward one word

1.

The arrow keys function only on ANSI-compatible terminals such as VT100s.

Using the History Buffer to Recall Commands

The history buffer stores the last 20 commands you entered. History substitution allows you to access these commands without retyping them, by using special abbreviated commands.

Table 1-2 lists the history substitution commands.

Table 1-2 History Substitution Commands

Command

Ctrl-P or the up arrow key.

1

Ctrl-N or the down arrow key.

Router# show history

1

Purpose

Recall commands in the history buffer, beginning with the most recent command. Repeat the key sequence to recall successively older commands.

Return to more recent commands in the history buffer after recalling commands with Ctrl-P or the up arrow key. Repeat the key sequence to recall successively more recent commands.

While in EXEC mode, list the last several commands you have just entered.

1.

The arrow keys function only on ANSI-compatible terminals such as VT100s.

Understanding Command Modes

You use the CLI to access Cisco IOS software. Because the CLI is divided into many different modes, the commands available to you at any given time depend on the mode that you are currently in. Entering a question mark ( ?

) at the CLI prompt allows you to obtain a list of commands available for each command mode.

When you log in to the CLI, you are in user EXEC mode. User EXEC mode contains only a limited subset of commands. To have access to all commands, you must enter privileged EXEC mode, normally by using a password. From privileged EXEC mode you can issue any EXEC command—user or

Release 12.0(33)S, OL-8832-01, Rev. C9


1-5


Understanding Command Modes privileged mode—or you can enter global configuration mode. Most EXEC commands are one-time commands. For example, show commands show important status information, and clear commands clear counters or interfaces. The EXEC commands are not saved when the software reboots.

Configuration modes allow you to make changes to the running configuration. If you later save the running configuration to the startup configuration, these changed commands are stored when the software is rebooted. To enter specific configuration modes, you must start at global configuration mode.

From global configuration mode, you can enter interface configuration mode and a variety of other modes, such as protocol-specific modes.

ROM monitor mode is a separate mode used when the Cisco IOS software cannot load properly. If a valid software image is not found when the software boots or if the configuration file is corrupted at startup, the software might enter ROM monitor mode.

Table 1-3

describes how to access and exit various common command modes of the Cisco IOS software.

It also shows examples of the prompts displayed for each mode.

Accessing and Exiting Command Modes Table 1-3

Command

Mode

User EXEC

Privileged

EXEC

Global configuration

Interface configuration

Access Method

Log in.

Prompt

Router>

From user EXEC mode, use the enable EXEC command.

From privileged EXEC mode, use the configure terminal privileged

EXEC command.

Router#

Router(config)#

From global configuration mode, specify an interface using an interface command.

Router(config-if)#

ROM monitor From privileged EXEC mode, use the reload

EXEC command. Press the Break key during the first 60 seconds while the system is booting.

>

Exit Method

Use the logout

To return to user EXEC mode, use the command.

command.

configuration mode, use the exit or disable end

To return to privileged EXEC mode from global

command.

To return to global configuration mode, use the command.

To return to privileged EXEC mode, use the command.

To exit ROM monitor mode, use the command.

end continue exit

For more information on command modes, refer to the “Using the Command-Line Interface” chapter in the Cisco IOS Configuration Fundamentals and Network Management Configuration Guide .

1-6


Release 12.0(33)S, OL-8832-01, Rev. C9


Getting Help

Getting Help

Entering a question mark ( ?

) at the CLI prompt displays a list of commands available for each command mode. You can also get a list of keywords and arguments associated with any command by using the context-sensitive help feature.

To get help specific to a command mode, a command, a keyword, or an argument, use one of the following commands:

Command help abbreviated-command-entry ?

abbreviated-command-entry < Tab >

?

command ?

Purpose

Provides a brief description of the help system in any command mode.

Provides a list of commands that begin with a particular character string. (No space between command and question mark.)

Completes a partial command name.

Lists all commands available for a particular command mode.

Lists the keywords or arguments that you must enter next on the command line.

(Space between command and question mark.)

Example: How to Find Command Options

This section provides an example of how to display syntax for a command. The syntax can consist of optional or required keywords and arguments. To display keywords and arguments for a command, enter a question mark ( ?

) at the configuration prompt or after entering part of a command followed by a space.

The Cisco IOS software displays a list and brief description of available keywords and arguments. For example, if you were in global configuration mode and wanted to see all the keywords or arguments for the arap command, you would type arap ?

.

The <cr> symbol in command help output stands for “carriage return.” On older keyboards, the carriage return key is the Return key. On most modern keyboards, the carriage return key is the Enter key. The

<cr> symbol at the end of command help output indicates that you have the option to press Enter to complete the command and that the arguments and keywords in the list preceding the <cr> symbol are optional. The <cr> symbol by itself indicates that no more arguments or keywords are available and that you must press Enter to complete the command.

Table 1-4 shows examples of how you can use the

question mark ( ?

) to assist you in entering commands.

The table steps you through configuring an IP address on a serial interface on a Cisco 7206 router that is running Cisco IOS Release 12.0(3).

Release 12.0(33)S, OL-8832-01, Rev. C9


1-7


Getting Help

Table 1-4 How to Find Command Options

Command

Router> enable

Password: <password>

Router#

Router# configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

Router(config)#

Router(config)# interface serial ?

<0-6> Serial interface number

Router(config)# interface serial 4 ?

/

Router(config)# interface serial 4/ ?

<0-3> Serial interface number

Router(config)# interface serial 4/0 ?

<cr>

Router(config)# interface serial 4/0

Router(config-if)#

Comment

Enter the enable command and password to access privileged EXEC commands. You are in privileged EXEC mode when the prompt changes to

Router#

.

Enter the configure terminal privileged

EXEC command to enter global configuration mode. You are in global configuration mode when the prompt changes to

Router(config)#

.

Enter interface configuration mode by specifying the serial interface that you want to configure using the interface serial global configuration command.

Enter ? to display what you must enter next on the command line. In this example, you must enter the serial interface slot number and port number, separated by a forward slash.

When the <cr> symbol is displayed, you can press Enter to complete the command.

You are in interface configuration mode when the prompt changes to

Router(config-if)#.

1-8


Release 12.0(33)S, OL-8832-01, Rev. C9


Getting Help

Table 1-4 How to Find Command Options (continued)

Command

Router(config-if)# ?

Interface configuration commands:

.

.

.

ip Interface Internet Protocol config commands

keepalive Enable keepalive

lan-name LAN Name command

llc2 LLC2 Interface Subcommands

load-interval Specify interval for load calculation for an

interface

locaddr-priority Assign a priority group

logging Configure logging for interface

loopback Configure internal loopback on an interface

mac-address Manually set interface MAC address

mls mls router sub/interface commands

mpoa MPOA interface configuration commands

mtu Set the interface Maximum Transmission Unit (MTU)

netbios Use a defined NETBIOS access list or enable

name-caching

no Negate a command or set its defaults

nrzi-encoding Enable use of NRZI encoding

ntp Configure NTP

.

.

.

Router(config-if)#

Router(config-if)# ip ?

Interface IP configuration subcommands:

access-group Specify access control for packets

accounting Enable IP accounting on this interface

address Set the IP address of an interface

authentication authentication subcommands

bandwidth-percent Set EIGRP bandwidth limit

broadcast-address Set the broadcast address of an interface

cgmp Enable/disable CGMP

directed-broadcast Enable forwarding of directed broadcasts

dvmrp DVMRP interface commands

hello-interval Configures IP-EIGRP hello interval

helper-address Specify a destination address for UDP broadcasts

hold-time Configures IP-EIGRP hold time

.

.

.

Router(config-if)# ip

Comment

Enter ? to display a list of all the interface configuration commands available for the serial interface. This example shows only some of the available interface configuration commands.

Enter the command that you want to configure for the interface. This example uses the ip command.

Enter ? to display what you must enter next on the command line. This example shows only some of the available interface IP configuration commands.

Release 12.0(33)S, OL-8832-01, Rev. C9


1-9


Using the no and default Forms of Commands

Table 1-4 How to Find Command Options (continued)

Command

Router(config-if)# ip address ?

A.B.C.D IP address

negotiated IP Address negotiated over PPP

Router(config-if)# ip address

Router(config-if)# ip address 172.16.0.1 ?

A.B.C.D IP subnet mask

Router(config-if)# ip address 172.16.0.1

Router(config-if)# ip address 172.16.0.1 255.255.255.0 ?

secondary Make this IP address a secondary address

<cr>

Router(config-if)# ip address 172.16.0.1 255.255.255.0


Router(config-if)#

Comment

Enter the command that you want to configure for the interface. This example uses the ip address command.

Enter ? to display what you must enter next on the command line. In this example, you must enter an IP address or the negotiated keyword.

A carriage return (<cr>) is not displayed; therefore, you must enter additional keywords or arguments to complete the command.

Enter the keyword or argument that you want to use. This example uses the

172.16.0.1 IP address.

Enter ?

to display what you must enter next on the command line. In this example, you must enter an IP subnet mask.

A <cr> is not displayed; therefore, you must enter additional keywords or arguments to complete the command.

Enter the IP subnet mask. This example uses the 255.255.255.0 IP subnet mask.

Enter ?

to display what you must enter next on the command line. In this example, you can enter the secondary keyword, or you can press Enter .

A <cr> is displayed; you can press

Enter to complete the command, or you can enter another keyword.

In this example, Enter is pressed to complete the command.

Using the no and default Forms of Commands

Almost every configuration command has a no form. In general, use the no form to disable a function.

Use the command without the no keyword to reenable a disabled function or to enable a function that is disabled by default. For example, IP routing is enabled by default. To disable IP routing, use the no ip routing command; to reenable IP routing, use the ip routing command. The Cisco IOS software command reference publications provide the complete syntax for the configuration commands and describe what the no form of a command does.

Configuration commands can also have a default form, which returns the command settings to the default values. Most commands are disabled by default, so in such cases using the default form has the same result as using the no form of the command. However, some commands are enabled by default and

1-10


Release 12.0(33)S, OL-8832-01, Rev. C9


Saving Configuration Changes have variables set to certain default values. In these cases, the default form of the command enables the command and sets the variables to their default values. The Cisco IOS software command reference publications describe the effect of the default form of a command if the command functions differently than the no form.

Saving Configuration Changes

Use the copy system:running-config nvram:startup-config command to save your configuration changes to the startup configuration so that the changes will not be lost if the software reloads or a power outage occurs. For example:

Router# copy system:running-config nvram:startup-config

Building configuration...

It might take a minute or two to save the configuration. After the configuration has been saved, the following output appears:

[OK]

Router#

On most platforms, this task saves the configuration to NVRAM. On the Class A Flash file system platforms, this task saves the configuration to the location specified by the CONFIG_FILE environment variable. The CONFIG_FILE variable defaults to NVRAM.

Filtering Output from the show and more Commands

You can search and filter the output of show and more commands. This functionality is useful if you need to sort through large amounts of output or if you want to exclude output that you need not see.

To use this functionality, enter a show or more command followed by the “pipe” character (|); one of the keywords begin , include , or exclude ; and a regular expression on which you want to search or filter (the expression is case-sensitive): command | { begin | include | exclude } regular-expression

The output matches certain lines of information in the configuration file. The following example illustrates how to use output modifiers with the show interface command when you want the output to include only lines in which the expression “protocol” appears:

Router# show interface | include protocol

FastEthernet0/0 is up, line protocol is up

Serial4/0 is up, line protocol is up


Serial4/2 is administratively down, line protocol is down

Serial4/3 is administratively down, line protocol is down

For more information on the search and filter functionality, refer to the “Using the Command-Line

Interface” chapter in the Cisco IOS Configuration Fundamentals and Network Management

Configuration Guide .

Release 12.0(33)S, OL-8832-01, Rev. C9


1-11


Finding Support Information for Platforms and Cisco IOS Software Images

Finding Support Information for Platforms and Cisco IOS

Software Images

Cisco IOS software is packaged in feature sets consisting of software images that support specific platforms. The feature sets available for a specific platform depend on which Cisco IOS software images are included in a release. To identify the set of software images available in a specific release or to find out if a feature is available in a given Cisco IOS software image, you can use Cisco Feature Navigator or the software release notes.

Using Cisco Feature Navigator

Use Cisco Feature Navigator to find information about platform support and Cisco IOS software image support. Access Cisco Feature Navigator at http://tools.cisco.com/ITDIT/CFN/jsp/index.jsp

. You must have an account on Cisco.com. If you do not have an account or have forgotten your username or password, click Cancel at the login dialog box and follow the instructions that appear.

Using Software Advisor

To see if a feature is supported by a Cisco IOS release, to locate the software document for that feature, or to check the minimum software requirements of Cisco IOS software with the hardware installed on your router, Cisco maintains the Software Advisor tool on Cisco.com at http://www.cisco.com/cgi-bin/Support/CompNav/Index.pl

You must be a registered user on Cisco.com to access this tool.

Using Software Release Notes

Cisco IOS software releases include release notes that provide the following information:

• Platform support information

•

•

Memory recommendations

New feature information

• Open and resolved severity 1 and 2 caveats for all platforms

Release notes are intended to be release-specific for the most current release, and the information provided in these documents may not be cumulative in providing information about features that first appeared in previous releases. Refer to Cisco Feature Navigator for cumulative feature information.

1-12


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

2

SIP and SPA Product Overview

This chapter provides an introduction to modular services cards (SIPs) and shared port adapters (SPAs).

It includes the following sections:

•

•

Introduction to SIPs and SPAs, page 2-1

SPA Optics Compatibility, page 2-3

•

SIP and SPA Compatibility, page 2-5

For more hardware details for the specific SIP and SPAs that are supported on the Cisco 12000 series router, refer to the companion publication, Cisco 12000 Series Router SIP and SPA Hardware

Installation Guide .

Introduction to SIPs and SPAs

SIPs and SPAs are a new carrier card and port adapter architecture to increase modularity, flexibility, and density across Cisco Systems routers for network connectivity. This section describes the SIPs and SPAs and provides some guidelines for their use.

SPA Interface Processors

The following list describes some of the general characteristics of a SIP:

• A SIP is a carrier card that inserts into a router slot like a line card. It provides no network connectivity on its own.

•

•

A SIP can contain two or more subslots, which are used to house one or more SPAs. The SPA provides interface ports for network connectivity.

During normal operation the SIP should reside in the router fully populated either with functional

SPAs in all subslots, or with a blank filler panel inserted in any empty subslots.

• SIPs support online insertion and removal (OIR) while SPAs are inserted in their subslots.

Release 12.0(33)S, OL-8832-01, Rev. C9


2-1

Chapter 2 SIP and SPA Product Overview



The following list describes some of the general characteristics of a SPA:

•

•

A SPA is a modular type of port adapter that inserts into a subslot of a compatible SIP carrier card to provide network connectivity and increased interface port density. A SIP can hold one or more

SPAs, depending on the SIP type.

SPAs are available in the following sizes, as shown in

Figure 2-1 and Figure 2-2

:

–

–

Single-height SPA—Inserts into a single SIP subslot.

Double-height SPA—Inserts into two single, vertically aligned SIP subslots.

Figure 2-1 Single-height and Double-height SPA Sizes

Front of SIP

Single-height SPA

Double-height SPA

Figure 2-2 Horizontal and Vertical Chassis Slot Orientation for SPAs

Front of SIP, horizontal chassis slots Vertical slot orientation

SPA 0

SPA 2

SPA 1

SPA 3

SPA 0

Double-height SPA

SPA 1

SPA 3

SPA 0

SPA 2

SPA 1

Double-height SPA

•

•

•

Each SPA provides a certain number of connectors, or ports, that are the interfaces to one or more networks. These interfaces can be individually configured within the Cisco IOS command-line interface (CLI).

Either a blank filler panel or a functional SPA should reside in every subslot of an SIP during normal operation.

SPAs support online insertion and removal (OIR). They can be inserted or removed independently from the SIP. OIR of a SIP with installed SPAs is also supported.

2-2


Release 12.0(33)S, OL-8832-01, Rev. C9



SFP and XFP Optics Modules

For more detailed information about the SFP and XFP optics modules, please refer to the applicable SPA section in the Cisco 12000 Series Router SIP and SPA Hardware Installation Guide .

Table 2-1 shows the SFP modules and their descriptions.

Table 2-1 SFP Modules

SPA




1-Port 10-Gigabit Ethernet SPA





SFP Module

Product Number SFP Module

SFP-GE-S

SFP-GE-L

SFP-GE-Z

XFP-10GLR

XFP-10GER

SFP-GE-S

SFP-GE-L

SFP-GE-Z

Short wavelength

(1000BASE-SX)

Long wavelength/long haul

(1000BASE-LX/LH)

Extended distance

(1000BASE-ZX)

XFP-10GLR-OC192SR

XFP-10GER-OC192IR

Short wavelength

(1000BASE-SX)

Long wavelength/long haul

(1000BASE-LX/LH)

Extended distance

(1000BASE-ZX)

Description

Contains a Class 1 laser of 850 nm for

1000BASE-SX (short wavelength) applications.


1000BASE-LX/LH (long wavelength) applications.


1000BASE-ZX (extended wavelength) applications.






1000BASE-SX (short wavelength) applications.





SPA Optics Compatibility

Table 2-2 shows the types of optics modules that have been qualified for use with a SPA:

Table 2-2 SPA Optics Compatibility

SPA

2-Port T3/E3 Serial SPA

4-Port Clear Channel T3/E3 SPA

2-Port Channelized T3 SPA


Qualified Optics Modules

None.

None.

None.

None.

Release 12.0(33)S, OL-8832-01, Rev. C9


2-3



Table 2-2 SPA Optics Compatibility (continued)

SPA











XFP-10GLR-OC192SR

XFP-10GER-OC192IR

XFP-10GLR-OC192SR

XFP-10GER-OC192IR

SFP-GE-S

SFP-GE-L

SFP-GE-Z

SFP-GE-S

SFP-GE-L

SFP-GE-Z

SFP-GE-S

SFP-GE-L

SFP-GE-Z

SFP-GE-S

SFP-GE-L

SFP-GE-Z

None.

SFP-OC48-SR OC48/STM16c SFP, Short Reach

SFP-OC48-IR1 OC48/ STM16c SFP, Intermediate

Reach

SFP-OC48-LR2 OC48/STM16c SFP, Long Reach

(80km)



Reach


(80km)

2-4


Release 12.0(33)S, OL-8832-01, Rev. C9


SIP and SPA Compatibility

Table 2-2 SPA Optics Compatibility (continued)

SPA

2-Port and 4-Port OC-48c/STM-16 POS SPA

2-Port, 4-Port, and 8-Port OC-3c/STM-1 and

OC-12c/STM-4 POS SPA




Reach


(80km)

SFP-OC3-SR OC3c/STM1 SFP, Short Reach

SFP-OC3-IR1 OC3c/STM1 SFP, Intermediate

Reach

SFP-OC3-LR2 OC3c/STM1 SFP, Long Reach

(80km)

SFP-OC12-SR OC12c/STM4 SFP, Short Reach

SFP-OC12-IR1 OC12c/STM4 SFP, Intermediate

Reach

SFP-OC12-LR2 OC12c/STM4 SFP, Long Reach

(80km)


Table 2-3 shows the SIPs that are supported in the Cisco 12000 Series Router and the SPAs that each SIP

supports:

Table 2-3

SPA





8-Port Fast Ethernet SPA









SIP and SPA Compatibility on the Cisco 12000 Series Router

SIP Type

2.5G ISE

SIP 400

X

10G

SIP 600

X

X

X

2.5G

SIP 401

X

X

X

X

X

SIP Type

5G

SIP 501

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

10G

SIP 601

X

X

X

X

X

X

X

Release 12.0(33)S, OL-8832-01, Rev. C9


2-5



Table 2-3

SPA



2-Port OC-3c/STM-1 and

OC-12c/STM-4 POS SPA, 4-Port

OC-3c/STM-1 and OC-12c/STM-4 POS

SPA, 8-Port OC-3c/STM-1 POS SPA


SIP and SPA Compatibility on the Cisco 12000 Series Router (continued)

SIP Type

2.5G ISE

SIP 400

10G

SIP 600

X

X

2.5G

SIP 401

X

SIP Type

5G

SIP 501

X

X

X

10G

SIP 601

X

X

X

X X

2-6


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

3

Overview of the Cisco 12000 Series Router SIPs

This chapter provides an overview of the release history, and feature and Management Information Base

(MIB) support for the SIPs supported on the Cisco 12000 Series Routers.

This chapter includes the following sections:

•

Release History, page 3-1

•

•

•

Supported Features, page 3-2

Supported MIBs, page 3-6

Displaying the SPA Hardware Type, page 3-9

Release History

Release

Cisco IOS Release

12.0(31)S

Modification


•

•

Cisco 12000 SIP-400

Cisco 12000 SIP-600

Release 12.0(33)S, OL-8832-01, Rev. C9


3-1

Chapter 3 Overview of the Cisco 12000 Series Router SIPs

Supported Features

Cisco IOS Release

12.0(32)S

Cisco IOS Release

12.0(33)S


• Cisco 12000 SIP-401

• Cisco 12000 SIP-501

• Cisco 12000 SIP-601

Support for the following hardware by the Cisco 12000 SIP-600 and the


•

•

1-Port 10-Gigabit Ethernet SPA [WAN-PHY] (SPA-1X10GE-WL-V2)

1-Port 10-Gigabit Ethernet DWDM SPA (SPA-1X10GE-L-ITUC)


• 8-Port Gigabit Ethernet SPA (SPA-8X1GE-V2)




Information specific to BERT configuration for the following SPAs was introduced:

• 2-Port and 4-Port Channelized T3 SPA

•

•




This section provides a list of some of the primary features supported by the SIP hardware and software.

Cisco 12000 SIP-401, Cisco 12000 SIP-501, Cisco 12000 SIP-600, and Cisco 12000

SIP-601 Features

The Cisco 12000 SIP-401, Cisco 12000 SIP-501, Cisco 12000 SIP-600, and Cisco 12000 SIP-601 provide a common 10 Gbps forwarding and queuing engine responsible for packet classification, forwarding, queuing, and accounting without compromising performance. The Cisco 12000 SIP-401,

Cisco 12000 SIP-501, Cisco 12000 SIP-600, and Cisco 12000 SIP-601 have two forwarding engines, one for ingress and one for egress. This allows the user to implement different features and QoS policies for the ingress and egress interfaces. The multicast replication is done by the egress forwarding engine, hence a very scalable multicast with built-in QoS.

The Modular Physical Layer Interface Module (PLIM) front end hosts up to 2 SPAs. Each SPA has a dedicated 10 Gbps interface to the SPA controller. The SPA controller uses a fair bandwidth allocation algorithm to share available and excess bandwidth between the 2 SPAs. The oversubscribed SPA does not cause any packet-drop on the nonoversubscribed SPA, and any unused bandwidth from one SPA is used by the other SPA.

The Cisco 12000 SIP-401, Cisco 12000 SIP-501, Cisco 12000 SIP-600, and Cisco 12000 SIP-601 support any combination of the following pluggable SPAs and Layer 2 encapsulations:


3-2 Release 12.0(33)S, OL-8832-01, Rev. C9



•

•

•

•

•

•

•

Concatenated OC-192 and OC-48

Gigabit Ethernet and 10 Gigabit Ethernet Interfaces

Point to Point Protocol (PPP)

High Level Data Link Control (HDLC)

Frame Relay

Dynamic Packet Transport (DPT)

Resilient Packet Ring (RPR)

• 802.17

• VLANs

The SPA controller adapts the user traffic flowing between the SPA interfaces for the Layer 3 forwarding engine. The SPA controller has two levels of priority queuing with Deficit Round Robin (DRR) and

Strict Priority Servicing. Strict Priority Servicing protects higher-priority packets by dropping lower priority packets first, in an oversubscribed configuration (persistent incoming traffic rate of 20 Gbps.)

The Cisco 12000 SIP-401, Cisco 12000 SIP-501, Cisco 12000 SIP-600, and Cisco 12000 SIP-601 provide the following key features:

• Dynamic allocation of 4096 input-shaped queues to any interface, subinterface, Frame Relay connection, VLAN.

• Ingress Queuing:

– 2048 unicast Modified DRR (MDRR) queues

–

–

16 high priority queues

8 multicast queues

•

•

•

– 2 fabric priority queues

Egress Queuing:

–

–

8192 Modified DRR (MDRR) queues dynamically shared across 4096 interfaces;

Hierarchical shaping (interface, queue)

High number of IPv4, IPv6, Multiprotocol Label Switching (MPLS), and MPLS VKPN unicast and multicast routes: Up to 1M IPv4/MPLS routes and up to 512,000 IPv6 prefixes.

Per-VLAN/source-destination MAC address filtering, trunking, accounting, QoS, match VLAN

QoS, Hot Standby Router Protocol (HSRP)/Virtual Router Redundancy Protocol (VRRP) hierarchical rate limiting and policing, dynamic queuing, and traffic shaping.

•

•

•

•

Input and output full NetFlow Version 8 in hardware.

Input and output Sampled NetFlow, Versions 5, 8, and 9 in hardware.

Building Integrated Timing Supply (BITS)

Online Insertion Removal (OIR) of SPAs; OIR of one SPA does not effect the traffic on other SPA interfaces.

•

•

Multi-router Automatic Protection Switching (MR-APS)

Layer 2 VPNs over MPLS (Any transport over MPLS (AToM)) and Over IP Layer 2 Tunneling

Protocol Version 3 (L2TPv3)

The Cisco 12000 SIP-401, Cisco 12000 SIP-501, and Cisco 12000 SIP-601 provide the following key features not available on the Cisco 12000 SIP-400 and Cisco 12000 SIP-600:

• Finer control over power supply voltages


Release 12.0(33)S, OL-8832-01, Rev. C9 3-3



The 12.0(32)S release allows you to specify the percentage of voltage increase. If you don’t specify a percentage, the value used is the default percentage, which is 5%.

The output is enhanced to show nominal supply voltage, percentage margin, and actual read-back voltage, to validate that the expected values were written and actually applied successfully.

Note High speed SPAs are only supported in bay 0 and 1 in routers with the Cisco 12000 SIP-401,

Cisco 12000 SIP-501, or Cisco 12000 SIP-601 SIP installed.

Cisco 12000 SIP-400 Features

The Cisco 12000 SIP-400 is a 2.5 Gbps IP Services Engine (ISE) SIP that hosts SPAs used for applications that require a high level of performance, scalable physical and logical connections, and high-touch QoS and security features. The Cisco 12000 SIP-400 enhances and scales functionality with benefits previously available on the 2.5 G ISE line card, allowing carriers to offer services such as VoIP,

MPLS VPN, Internet Access, and Low-speed Leased Line Aggregation (DS3, E3, CT3, n x T1, and n x

DS0).

The Cisco 12000 SIP-400 provides a common 10 Gbps forwarding and queuing engine that handles packet classification, forwarding, queuing, and accounting without compromising performance. The forwarding engine, based on the 12000 Series ISE technology, features a unique edge-optimized, programmable adaptive network processor that combines the hardware performance of

Application-Specific Integrated Circuits (ASICs) with the flexibility of software.

The Modular Physical Layer Interface Module (PLIM) front end hosts up to 4 SPAs. Each SPA has a dedicated 2.5 Gbps interface to the SPA controller. The Cisco 12000 SIP-400 supports any combination of the following pluggable SPAs and Layer 2 encapsulation:

•

•

T3

E3

•

•

CT3

PPP/HDLC/FR

MLPPP •

• MLFR

The SPA controller adapts the traffic flowing between the SPA interfaces for the Layer 3 forwarding engine. The SPA controller has two levels of priority queuing with Deficit Round Robin (DRR) and

Strict Priority Servicing. Strict Priority Servicing protects high priority traffic.

Key Features

The Cisco 12000 SIP-400 provides the following key features and benefits:

• QoS

•

•

•

Provider Edge

Security

Accounting

• High Availability

3-4


Release 12.0(33)S, OL-8832-01, Rev. C9



QoS

Traffic Shaping

Traffic Shaping offers additional value to service providers that want to build tiered service models. With traffic shaping, the Cisco 12000 SIP-400 can absorb bursts of traffic in both the ingress and egress directions. The Cisco 12000 SIP-400 supports up to 2048 input shaped queues and up to 1024 output shaped queues dynamically allocated to any interface or subinterface. Traffic can be shaped down to

64 kbps.

Traffic Rate Limiting and Marking

Traffic Rate Limiting and Marking, using Committed Access Rate (CAR) or Modular QoS CLI (MQC), allows service providers to control access to internal network resources. These features can be used to protect against Denial of Service (DoS) attacks or to deliver tiered services.

Traffic Prioritization through MDRR with Low Latency Queuing (LLQ)

Traffic Prioritization through MDRR with Low Latency Queuing (LLQ) offers class-based packet queuing that controls the packet dequeuing process to assure transit latency for differentiated flows. The

Cisco 12000 SIP-400 supports the following queues:

• 2048 unicast MDRR queues

•

•

•

16 high priority queues

1 multicast queue in the ingress direction

4096 MDRR queues dynamically shared across 1024 interfaces in the egress direction

Congestion Control through WRED and Query Management

Congestion Control through WRED and Query Management allows selective discard of low-priority flows before dropping packets from higher-priority flows.

Provider Edge

The Cisco 12000 SIP-400 provides the following comprehensive MPLS capabilities that support the development of service-optimized networks and can accelerate migration from circuit-based networks to packet-based networks:

• Layer 2 VPNs over MPLS (any transport over MPLS) and over IP (L2TPv3)

•

•

•

•

•

•

Layer 3 VPNs over MPLS and over IP, Multicast VPNs

Multilink Point-to-point Protocol (MLPPP)

Multilink Frame Relay (MLFR)

Link Fragmentation And Interleaving (LFI) over Frame Relay

IPv6 Unicast/Multicast

6PE

Release 12.0(33)S, OL-8832-01, Rev. C9


3-5


Supported MIBs

Security

Access Control Lists (ACLs) and Unicast Reverse Packet Check (uRPF) provide security and access control by checking and filtering unwanted packets on specific interfaces. With ACLs, filtering can be done on source and destination IP addresses, transport protocols, and input and output interfaces.

Accounting

ISE accounting tools provide data for end-customer billing and network utilization monitoring. The

Cisco 12000 SIP-400 provides the following accounting tools:

• Input and output Full Netflow v8 in Hardware

•

•

Input and output Sampled NetFlow v5/v8/v9 in Hardware

BGP Policy accounting per interface, protocol, or Class of Service account

High Availability

The Cisco 12000 SIP-400 supports Online Insertion Removal (OIR) of SPAs; OIR of one SPA does not effect the traffic on other SPA interfaces.

The Cisco 12000 SIP-400 also supports Layer 3 NSF/SSO.

Supported MIBs

•

•

•

•

•

•

The following MIBs are supported in Cisco IOS Release 12.0(33)S for the Cisco 12000 SIP-600 on a

Cisco 12000 series router:

• IPv6 MIB

•

•

ICMPv6 MIB

IPv6 TCP MIB

IPv6 UDP MIB

SNMP v1, v2c, v3 (RFC 1157, 1901-07)

•

•

•

MIB II, including interface extensions (RFC 1213, 2011-13, 2233)

Cisco GSR Manager

CiscoView ifIndex persistence

•

•

•

•

•

64-bit counters

APS Extensions MIB

ATM CON MIB

ATM Forum Address MIB

ATM Forum MIB

ATM MIB

BGP-4 MIB

CAR MIB

3-6


Release 12.0(33)S, OL-8832-01, Rev. C9


Supported MIBs

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

Cisco AAL5 MIB

Cisco APS MIB

Cisco ATM Extensions MIB

Cisco BGP Policy Accounting MIB

Cisco Bulk File MIB

Cisco CAR MIB

Cisco CDP MIB

Cisco Class-Based QoS MIB) aka MQC MIB)

Cisco Config Copy MIB

Cisco Config Man MIB

Cisco Enhanced MemPool MIB

Cisco EnvMon MIB

Cisco Flash MIB

Cisco Frame Relay MIB

Cisco FRU MIB

Cisco FTP Client MIB

Cisco HSRP Extensions MIB

Cisco HSRP MIB

Cisco IETF ATM2 PVCTRAP MIB

Cisco Image MIB

Cisco IP Statistics MIB

Cisco IP Mroute MIB

Cisco MDRR MIB

Cisco Memory Pool MIN

Cisco Optical Monitoring MIB

Cisco PIM MIB

Cisco Ping MIB

Cisco Process MIB

Cisco Queue MIB

Cisco RTT Monitor MIB (SAA)

Cisco SRP MIB

Cisco Syslog MIB

Cisco TCP MIB

Cisco VLAN IFTABLE Relationship MIB

Cisco WRED MIB

DPT MIB

DS1/E1 MIB

DS3/E3 MIB


Release 12.0(33)S, OL-8832-01, Rev. C9 3-7

Supported MIBs

3-8

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

Entity MIB

Entity II MIB

Ethernet MIB

Ethernet RMON MIB

Ether-like MIB

Event MIB

Expression MIB

Fabric MIB

Frame Relay MIB (IETF)

Frame Relay DTE MIB

HSRP MIB

IF MIB

IF MIB for VLANs

IGMP MIB

Interfaces MIB

Int-Serv MIB

Int-Serv Guaranteed MIB

IP Mroute MIB

MPLS MIB

MPLS LDP MIB

MPLS LSR MIB

MPLS-TE MIB

MPLS-TE Topo MIB

MPLS-VPN MIB

MPLS-DE-TE MIB

MQC MIB

MSDP MIB

Old Cisco Chassis MIB

Old Cisco CPU MIB

Old Cisco Interfaces MIB

Old Cisco IP MIB

Old Cisco Memory MIB

Old Cisco System MIB

Old Cisco TCP MIB

Old Cisco TS MIB

OSPFv2 MIB

PIM MIB

PSA Microcode MIB



Release 12.0(33)S, OL-8832-01, Rev. C9


Displaying the SPA Hardware Type

•

•

•

•

•

•

•

RFC1213 MIB

RFC1253 MIB

RFC1315 MIB

RFC1406 MIB

RFC1407 MIB

RFC1398 MIB

RFC1595 MIB

•

•

RMON MIB

RS232C MIB

RSVP MIB •

•

•

•

SNMP Framework MIB

SNMP Target MIB

SNMP USM MIB

SNMP VACM MIB •

•

•

•

SNMPv2 MIB

SNMP v3 MIB

SONET/SDH MIB

SONET Traps •

•

•

•

Syslog Trap Alert on DLCI loss

TCP MIB

UDP MIB

WRED MIB •

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use Cisco

MIB Locator found at the following URL: http://www.cisco.com/go/mibs

If Cisco MIB Locator does not support the MIB information that you need, you can also obtain a list of supported MIBs and download MIBs from the Cisco MIBs page at the following URL: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

To access Cisco MIB Locator, you must have an account on Cisco.com. If you have forgotten or lost your account information, send a blank e-mail to [email protected]. An automatic check will verify that your e-mail address is registered with Cisco.com. If the check is successful, account details with a new random password will be e-mailed to you. Qualified users can establish an account on Cisco.com by following the directions found at this URL: http://www.cisco.com/register


To verify the SPA hardware type that is installed in your Cisco 12000 Series Router, you can use the show gsr command.

Release 12.0(33)S, OL-8832-01, Rev. C9


3-9



Table 3-1

shows the hardware description that appears in the show command output for each type of SPA that is supported on the Cisco 12000 Series Router.

Table 3-1 SPA Hardware Descriptions in show Commands

SPA








4-Port Channelized T3 to DS0 SPA









2-Port OC48-POS/RPR SPA

2-Port and 4-Port OC-48c/STM-16 POS SPA

2-Port OC-3c/STM-1 and OC-12c/STM-4 POS

SPA


SPA


SPA



Description in show gsr Command

SPA-2XT3/E3

SPA-4XT3/E3

SPA-1XCOC3

SPA-8XCT1/E1

SPA-2XT3/E3

SPA-4XT3/E3

SPA-2XCT3/DS0

SPA-4XCT3/DS0

SPA-8XFE, SPA-8x1FE-TX-V2

SPA-2XGE, SPA-2X1GE-V2

SPA-5XGE, SPA-5x1GE-V2

SPA-8X1GE-V2

SPA-1XTENGE-XFP, SPA-1X10GE-L-V2,

SPA-1X10GE-WL-V2

SPA-1X10GE-L-ITUC

SPA-10XGE-XFP, SPA-10X1GE-V2

SPA-OC192POS

SPA-2XOC48POS

SPA-4XOC48-POS/RPR

SPA-2XOC12-POS

SPA-4XOC12-POS

SPA-8XOC12-POS

SPA-4XOC3-POS

SPA-8XOC3-POS

Example of the show gsr Command

The following example shows output from the show gsr command on a Cisco 12000 Series Router with a Cisco 12000 SIP-400 installed in slot 1 and a Cisco 12000 SIP-600 installed in slot 3:

Router# show gsr hdm-193#show gsr

Slot 0 type = ISE 2.5G SPA Interface Card

state = IOS RUN Line Card Enabled

subslot 0/0: SPA-4XT3/E3 (0x40B), status is ok



3-10 Release 12.0(33)S, OL-8832-01, Rev. C9




subslot 0/3: SPA-2XCT3/DS0 (0x43C), status is ok




subslot 1/1: SPA-2XT3/E3 (0x40C), status is ok











subslot 3/0: SPA-4XT3/E3 (0x40B), status is out of service


subslot 3/2: Empty

subslot 3/3: Empty



subslot 4/0: Empty

subslot 4/1: Empty

subslot 4/2: Empty

subslot 4/3: Empty

Slot 9 type = Performance Route Processor

state = ACTV RP IOS Running ACTIVE

Slot 16 type = Clock Scheduler Card(10) OC-192

state = Card Powered

Slot 17 type = Clock Scheduler Card(10) OC-192

state = Card Powered PRIMARY CLOCK

Slot 18 type = Switch Fabric Card(10) OC-192










Slot 24 type = Alarm Module(10)




Slot 29 type = Blower Module(16)


Release 12.0(33)S, OL-8832-01, Rev. C9


3-11



3-12


Release 12.0(33)S, OL-8832-01, Rev. C9

P A R T 2

Gigabit Ethernet Shared Port Adapters

C H A P T E R

4

Overview of the Gigabit Ethernet SPAs


(MIB) support for the Gigabit Ethernet SPAs on the Cisco 12000 series router.


•


•

•

•

•



SPA Architecture, page 4-4


Release History

Table 4-1 provides the release and modification history for Ethernet SPA-related features and

enhancements on the Cisco 12000 series router.

Table 4-1 Release History for Ethernet SPAs

Release Modification

Cisco IOS Release

12.0(31)S

Support for the following SPAs was introduced on Cisco 12000 series routers:


Cisco IOS Release

12.0(32)S

• 5-Port Gigabit Ethernet SPA

• 10-Port Gigabit Ethernet SPA


•

•

•




Release 12.0(33)S, OL-8832-01, Rev. C9


4-1

Chapter 4 Overview of the Gigabit Ethernet SPAs


Cisco IOS Release

12.0(32)SY

Cisco IOS Release

12.0(33)S

Cisco IOS Release

12.0(33)S2


• 1-Port 10-Gigabit Ethernet SPA Version 2

•

•

8-Port FastEthernet SPA Version 2

2-Port Gigabit Ethernet SPA Version 2

•

•

5-Port Gigabit Ethernet SPA Version 2

• 10-Port Gigabit Ethernet SPA Version 2

Support for the following hardware by the Cisco 12000 SIP-600 and the


1-Port 10-Gigabit Ethernet SPA [WAN-PHY] Version 2

• 1-Port 10-Gigabit Ethernet DWDM SPA


Cisco 12000 SIP-501 and Cisco 12000 SIP-601 was introduced on the


• 8-Port Gigabit Ethernet SPA Version 2

Added following commands supported on Cisco IOS Release 12.0(33)S2 on Cisco 12000 series router for Engine 5 SIP-401/501/600/601 line card and applicable on GE or FE SPA interfaces:

• show interfaces flowcontrol

•

• flowcontrol bidirectional no flowcontrol bidirectional


This section provides a list of some of the primary features supported with the Gigabit Ethernet SPAs.

Gigabit Ethernet SPA Features

The following is a list of some of the significant hardware and software features supported by the Gigabit

Ethernet SPAs on the Cisco 12000 series routers:

• Auto negotiation

•

•

•

•

•

Full-duplex operation

802.1Q VLAN termination

Jumbo frames support (9188 bytes)

Support for command-line interface (CLI) controlled OIR

•

•

802.3x flow control

Up to 4K VLAN per SPA

Up to 5K Mac Accounting Entries per SPA (Source Mac Accounting on the ingress and Destination

Mac Accounting on the egress)

4-2


Release 12.0(33)S, OL-8832-01, Rev. C9


Supported MIBs

•

•

•

•

•

•

•

•

Up to 2K MAC address entries for destination MAC address filtering per SPA, and up to 1K MAC address filtering entries per port

Per port byte and packet counters for policy drops, oversubscription drops, CRC error drops, packet sizes, Unicast, multicast, and broadcast packets

Per VLAN byte and packet counters for policy drops, oversubscription drops, Unicast, multicast, and broadcast packets

Per-port byte counters for good bytes and dropped bytes

Ethernet over Multi-protocol Label Switching (EoMPLS)

Quality of service (QoS)

Hot Standby Router Protocol (HSRP)

Virtual Router Redundancy Protocol (VRRP)

Supported MIBs

The following MIBs are supported by the Gigabit Ethernet SPAs on the Cisco 12000 series routers:

•

•

•

•

•

•

•

•

•

•

Entity-MIB (RFC 2737)

Cisco-entity-asset-MIB

Cisco-entity-field-replaceable unit (FRU)-control-MIB

Cisco-entity-alarm-MIB

Cisco-entity-sensor-MIB

IF-MIB

Etherlike-MIB (RFC 2665)

Remote Monitoring (RMON)-MIB (RFC 1757)

Cisco-class-based-QoS-MIB

MPLS-related MIBs

• Ethernet MIB/RMON

To locate and download MIBs for selected platforms, Cisco IOS releases, and feature sets, use

Cisco MIB Locator found at the following URL: http://tools.cisco.com/ITDIT/MIBS/servlet/index



Release 12.0(33)S, OL-8832-01, Rev. C9


4-3


SPA Architecture


This section provides an overview of the architecture of the Gigabit Ethernet SPAs and describes the path of a packet in the ingress and egress directions. Some of these areas of the architecture are referenced in the SPA software and can be helpful to understand when troubleshooting or interpreting some of the SPA

CLI and show command output.

Every incoming and outgoing packet on the Gigabit Ethernet SPAs goes through the physical (PHY) SFP optics, Media Access Control (MAC), and ASIC devices.

Path of a Packet in the Ingress Direction

The following steps describe the path of an ingress packet through the Gigabit Ethernet SPAs:

1.

2.

The PHY SFP optics device receives incoming frames on a per-port basis from one of the laser optic interface connectors.

The PHY laser optics device processes the frame and sends it over the XAUI path to the MAC device.

3.

4.

The MAC device receives the frame, strips the CRCs, and sends the packet via the SPI 4.2 bus to the

ASIC.

The ASIC takes the packet from the MAC devices and classifies the ethernet information. CAM lookups based on etype, port, VLAN, and source and destination address information determine whether the packet is dropped or forwarded to the SPA interface. If the packet is forwarded to the

SPA interface, an 8-byte SHIM header that is used for additional downstream packet processing is prepended to the packet.

Path of a Packet in the Egress Direction

The following steps describe the path of an egress packet from the SIP through the Gigabit Ethernet SPA:

1.

The packet is sent to the ASIC using the SPI 4.2 Bus. The packets are received with layer 2 and layer

3 headers in addition to the packet data.

2.

3.

The ASIC uses port number, destination MAC address, destination address type, and VLAN ID to perform parallel CAM lookups. If the packet is forwarded, it is forwarded via the SPI 4.2 Bus to the

MAC device.

The MAC device forwards the packets to the PHY laser optic interface, which transmits the packet.


To verify the SPA hardware type that is installed in your Cisco 12000 series router, you can use the show interfaces command. For more information about these commands, see

Chapter 19, “SIP and SPA

Command Reference.”

4-4


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 4-2 shows the hardware description that appears in the

show command output for each type of

Gigabit Ethernet SPA that is supported on Cisco 12000 series routers.


SPA




Description in show interfaces and show controllers commands

Hardware is GigMac 1 Port 10 GigabitEthernet

Hardware is FiveGigE

Hardware is TenGigE

Example of the show interfaces Command

The following example shows output from the show interfaces fastethernet command on a Cisco 12000 series router with a 1-Port 10-Gigabit Ethernet SPA installed in slot 3:

Router# show interfaces gigabitethernet 3/0/0

GigabitEthernet3/0/0 is up, line protocol is up

Hardware is GigMac 1 Port 10 GigabitEthernet , address is 0008.7db3.8dfe (bia )

Internet address is 10.0.0.2/24

.

.

MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec, rely 255/255, load 1/255

Encapsulation ARPA, loopback not set

.

Release 12.0(33)S, OL-8832-01, Rev. C9


4-5



4-6


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

5

Configuring the Fast Ethernet and Gigabit

Ethernet SPAs

This chapter provides information about configuring the Cisco 1-port 10 Gigabit Ethernet SPA, 5-Port

Gigabit Ethernet SPA, 8-Port Gigabit Ethernet SPA, 8-Port Fast Ethernet SPA,and Cisco 10-port Gigabit

Ethernet SPA on Cisco 12000 series routers. It includes the following sections:

•

Configuration Tasks, page 5-1

•

•

Verifying the Interface Configuration, page 5-12

Configuration Examples, page 5-14

For information about managing your system images and configuration files, refer to the Cisco IOS

Configuration Fundamentals Configuration Guide, Release 12.0 and Cisco IOS Configuration

Fundamentals Command Reference, Release 12.0 publications.

For more information about the commands used in this chapter, first see


Command Reference,”

which documents new and modified commands . Also refer to the related

Cisco IOS Release 12.0 software command reference and master index publications. For more information about accessing these publications, see the “Related Documentation” section on page xix .

Configuration Tasks

This section describes how to configure the Cisco 1-port 10 Gigabit Ethernet SPA, the 1-Port 10-Gigabit

Ethernet DWDM SPA, the 2-Port Gigabit Ethernet SPA, the 5-Port Gigabit Ethernet SPA, the 8-Port

Gigabit Ethernet SPA, the 8-Port Fast Ethernet SPA, and the Cisco 10-port Gigabit Ethernet SPA. This section also includes information about verifying the configuration.

This section includes the following topics:

•

Required Configuration Tasks, page 5-2

•

•

•

•

Specifying the Interface Address, page 5-4

Modifying the MAC Address on the Interface, page 5-5

Modifying the Interface MTU Size, page 5-7

Configuring the Encapsulation Type, page 5-9

•

•

•

Configuring Autonegotiation on an Interface, page 5-9

Configuring a Subinterface on a VLAN, page 5-10

Configuring Flow Control Support on the Link, page 5-11

Release 12.0(33)S, OL-8832-01, Rev. C9


5-1

Chapter 5 Configuring the Fast Ethernet and Gigabit Ethernet SPAs


•

•

Saving the Configuration, page 5-12

Shutting Down and Restarting an Interface on a SPA, page 5-12

Required Configuration Tasks

This section lists the required configuration steps to configure the Gigabit Ethernet SPAs. Some of the required configuration commands implement default values that might be appropriate for your network.

If the default value is correct for your network, then you do not need to configure the command. These commands are indicated by “(As Required)” in the purpose column.

Required Configuration Tasks for the Fast Ethernet SPA

To configure the 8-Port Fast Ethernet SPA, complete the following steps:

Step 1

Step 2

Command


Router(config)# interface fastethernet slot / subslot / port [ .

subinterface-number ]

Step 3 Router(config-if)# ip address ip-address mask

[ secondary ]

Step 4

Step 5

Step 6

Step 7

Router(config-if)# duplex { full | half }

Router(config-if)# speed { 10 | 100 }

Router(config-if)# mtu bytes

Router(config-if)# no shutdown

Purpose

Enters global configuration mode.

Specifies the Fast Ethernet interface to configure, where:

• slot / subslot / port —Specifies the location of the interface. See the

“Specifying the Interface

Address” section on page 5-4

.

• .

subinterface-number —(Optional) Specifies a secondary interface (subinterface) number.

Sets a primary or secondary IP address for an interface, where:

•

• ip-address —Specifies the IP address for the interface.

mask —Specifies the mask for the associated

IP subnet.

• secondary —(Optional) Specifies that the configured address is a secondary IP address.

If this keyword is omitted, the configured address is the primary IP address.

(As Required) Configures the duplex operation on an interface.

The default is full .

(As Required) Configures the speed of an interface

(Mbps).

(As Required) Specifies the maximum packet size for an interface, where:

• bytes— Specifies the maximum number of bytes for a packet. The default is 1500 bytes.

Enables the interface.

5-2


Release 12.0(33)S, OL-8832-01, Rev. C9



Required Configuration Tasks for the Gigabit Ethernet SPA

To configure the Cisco 1-port 10 Gigabit Ethernet SPA, the 1-Port 10-Gigabit Ethernet DWDM SPA, the

2-Port Gigabit Ethernet SPA, the 5-Port Gigabit Ethernet SPA, the 8-Port Gigabit Ethernet SPA, or the

Cisco 10-port Gigabit Ethernet SPA, complete the following steps:

Step 1

Step 2

Command


Router(config)# interface gigabitethernet slot / subslot / port [ .

subinterface-number ] or

Router(config)# interface tengigabitethernet slot / subslot / port [ .


Step 3 Router(config-if)# ip address ip-address mask

[ secondary ]

Step 4

Step 5

Router(config)# ip accounting mac-address

{ input | output }


Purpose


Specifies the Gigabit Ethernet or Ten Gigabit

Ethernet interface to configure, where:



Address” section on page 5-4 .

• .

subinterface-number —(Optional) Specifies a secondary interface (subinterface) number.

For IPv4:

Sets a primary or secondary IP address for an interface that is using IPv4, where:


•

• mask —Specifies the mask for the associated

IP subnet.

secondary —(Optional) Specifies that the configured address is a secondary IP address.


(Optional) Enables MAC address accounting.

MAC address accounting provides accounting information for IP traffic based on the source and destination MAC addresses of the LAN interfaces, where:

• input —specifies MAC address accounting for traffic entering the interface.

• output —specifies MAC address accounting for traffic leaving the interface.

(As Required) Specifies the maximum packet size for an interface, where:

• bytes— Specifies the maximum number of bytes for a packet.

The default is 1500 bytes.

Release 12.0(33)S, OL-8832-01, Rev. C9


5-3



Step 6

Command

Router(config-if)# standby [ group-number ] ip

[ ip-address [ secondary ]]

Step 7 Router(config-if)# no shutdown

Purpose

(Required for HSRP Configuration Only) Creates

(or enables) the HSRP group using its number and virtual IP address.

•

•

(Optional) group-number —The group number on the interface for which HSRP is being enabled. The range is 0 to 255; the default is 0.

If there is only one HSRP group, you do not need to enter a group number.

(Optional on all but one interface if configuring HSRP) ip-address —The virtual

IP address of the hot standby router interface.

You must enter the virtual IP address for at least one of the interfaces; it can be learned on the other interfaces.

• (Optional) secondary —The IP address is a secondary hot standby router interface. If neither router is designated as a secondary or standby router and no priorities are set, the primary IP addresses are compared and the higher IP address is the active router, with the next highest as the standby router.

This command enables HSRP but does not configure it further. For additional information on configuring HSRP, see the “ Configuring Hot

Standby Routing Protocol ” section of the Cisco

IOS Release 12.2 IP Configuration Guide .


Specifying the Interface Address

The interface address format when using SPAs is slot / subslot / port :

•

•

• slot

SPA is installed. subslot —Specifies the secondary slot on the MSC where the SPA that you want to select is installed.

port

–

—Specifies the slot number in the Cisco 12000 series router in which the SIP that contains the

—Specifies the interface number that you want to select on the SPA:

For the Cisco 1-port 10 Gigabit Ethernet SPA, 0 is the only option.

–

–

For the 2-Port Gigabit Ethernet SPA, 0 or 1 are the options.

For the 5-Port Gigabit Ethernet SPA, 0 through 4 are the options.

–

–

For the 8-Port Fast Ethernet SPA, 0 through 7 are the options.

For the 8-Port Gigabit Ethernet SPA, 0 through 7 are the options.

– For the Cisco 10-port Gigabit Ethernet SPA, 0 through 9 are the options.

5-4


Release 12.0(33)S, OL-8832-01, Rev. C9



Figure 5-1

shows the slot, subslot, and interface port locations of the Cisco 10-port Gigabit Ethernet SPA on a Cisco 12000 series router.

Figure 5-1 Slot, Subslot, and Port Locations for the Cisco 10-port Gigabit Ethernet SPA and the

1-Port 10-Gigabit Ethernet SPA.

ALARM A

ALARM B

A

B

MINO

R

MA JOR

CRITIC

AL

MBUS

A B

CSC

0 1 0

SFC

1 2 3 4

FAIL

ENABLE

1

0

ACTIVE

CARRIER

RX PKT

0

ACTIVE

CAR

1

ACTIVE

CARRIER

RX PKT

1

AC

TIVE

CARRIER

RX PKT

2

ACTIVE

CARRIER

RX PKT

2

ACTIVE

CARRIER

RX PKT

3

ACTIVE

CARRIER

RX PKT

3

ACTIVE

CARRIER

RX PKT

CTIVE/LINK

ST

AT

U

S

AC

TIV

CA

RR

IE

RX

P

E

KT

R

EJ

EC

T

SLO

T-0

SLO

T-1

LINK

DATA

LINK

DATA

SIG

AC

T

SIG

AC

T

EC

T

SLO

T-0

SLO

T-1

LINK

DATA

LINK

DATA

SIG

AC

T

SIG

AC

T

2

3

Table 5-1

2

3

Call Out Number

1

Slot and Port Locations for the Gigabit Ethernet SPAs

Description

Slot 3

Subslot 0, Port 3/0/0

Subslot 1, Ports 3/1/0 to 3/1/9

For more information about the installation of cards on the Cisco 12000 router, refer to the Cisco 12000

SIP and SPA Hardware Installation Guide .

Modifying the MAC Address on the Interface

The Fast Ethernet and Gigabit Ethernet SPAs use a default MAC address for each port that is derived from the base address that is stored in the electrically erasable programmable read-only memory

(EEPROM) on the backplane of the Cisco 12000 series router.

Release 12.0(33)S, OL-8832-01, Rev. C9


5-5



To modify the default MAC address of an interface to some user-defined address, use the following command in interface configuration mode:

Command

Router(config-if)# mac-address ieee-address

Purpose

Modifies the default MAC address of an interface to some user-defined address, where:

• ieee-address— Specifies the 48-bit Institute of

Electrical and Electronics Engineers (IEEE) MAC address written as a dotted triple of four-digit hexadecimal numbers ( xxxx.yyyy.zzzz

).

To return to the default MAC address on the interface, use the no form of the command.

Verifying the MAC Address

To verify the MAC address of an interface, use the show interfaces gigabitethernet privileged EXEC command and observe the value shown in the “address is” field.

The following example shows that the MAC address is 0008.7db3.8dfe for interface 0 on the SPA installed in slot 3 of the Cisco 12000 series router:



Hardware is GigMac 1 Port 10 GigabitEthernet, address is 0008.7db3.8dfe

(bia )


.

.



.

Gathering MAC Address Accounting Statistics

The ip accounting mac-address [ input | output ] command can be entered to enable MAC Address

Accounting on an interface.

After enabling MAC Address Accounting, MAC address statistics can be gathered by entering the show interface mac command.

Configuring HSRP

Hot Standby Router Protocol (HSRP) is available for Fast Ethernet and Gigabit Ethernet SPAs. HSRP provides high network availability because it routes IP traffic from hosts without relying on the availability of any single router. HSRP is used in a group of routers for selecting an active router and a standby router. (An active router is the router of choice for routing packets; a standby router is a router that takes over the routing duties when an active router fails, or when preset conditions are met).

HSRP is enabled on an interface by entering the standby [ group-number ] ip [ ip-address [ secondary ]] command. The standby command is also used to configure various HSRP elements. This document does not discuss more complex HSRP configurations. For additional information on configuring HSRP, see the Configuring Hot Standby Routing Protocol section of the Cisco IOS Release 12.2 IP Configuration

Guide .


5-6 Release 12.0(33)S, OL-8832-01, Rev. C9



In the following HSRP configuration, standby group 2 on GigabitEthernet port 2/1/0 is configured at a priority of 110 and is also configured to have a preemptive delay should a switchover to this port occur.

Router(config)# interface GigabitEthernet 2/1/0

Router(config-if)# standby 2 ip 120.12.1.200

Router(config-if)# standby 2 priority 110

Router(config-if)# standby 2 preempt

Modifying the Interface MTU Size

The Cisco IOS software supports three different types of configurable maximum transmission unit

(MTU) options at different levels of the protocol stack:

•

•

•

Interface MTU—Checked by the SPA on traffic coming in from the network. Different interface types support different interface MTU sizes and defaults. The interface MTU defines the maximum packet size allowable (in bytes) for an interface before drops occur. If the frame is smaller than the interface MTU size, but is not smaller than the minimum frame size for the interface type (such as

64 bytes for Ethernet), then the frame continues to process.

IP MTU—Can be configured on a subinterface and is used by the Cisco IOS software to determine whether fragmentation of a packet takes place. If an IP packet exceeds the IP MTU size, then the packet is fragmented.

Tag or Multiprotocol Label Switching (MPLS) MTU—Can be configured on a subinterface and allows up to six different labels, or tag headers, to be attached to a packet. The maximum number of labels is dependent on your Cisco IOS software release.

Different encapsulation methods and the number of MPLS MTU labels add additional overhead to a packet. For example, Subnetwork Access Protocol (SNAP) encapsulation adds an 8-byte header, dot1q encapsulation adds a 2-byte header, and each MPLS label adds a 4-byte header ( n labels x 4 bytes).

For the Fast Ethernet and Gigabit Ethernet SPAs on the Cisco 12000 series router, the default MTU size is 1500 bytes. The maximum configurable MTU is 9216 bytes. The SPA automatically adds an additional

38 bytes to the configured MTU size to accommodate some of the additional overhead.

Interface MTU Configuration Guidelines

When configuring the interface MTU size on a Fast Ethernet or Gigabit Ethernet SPA on a Cisco 12000 series router, consider the following guidelines:

• The default interface MTU size accommodates a 1500-byte packet, plus 38 additional bytes to cover the following additional overhead:

–

–

Layer 2 header—14 bytes

SNAP header—8 bytes

–

–

Dot1q header—4 bytes

2 MPLS labels—8 bytes

– CRC—4 bytes

Note Depending on your Cisco IOS software release, a certain maximum number of MPLS labels are supported. If you need to support more than two MPLS labels, then you should increase the default interface MTU size on the SPA interface.

Release 12.0(33)S, OL-8832-01, Rev. C9


5-7



•

•

If you are using MPLS, be sure that the mpls mtu command is configured for a value less than or equal to the interface MTU.

If you are using MPLS labels, then you should increase the default interface MTU size to accommodate the number of MPLS labels. Each MPLS label adds 4 bytes of overhead to a packet.

Interface MTU Configuration Task

To modify the MTU size on an interface, use the following command in interface configuration mode:

Command


Purpose

Configures the maximum packet size for an interface, where:



To return to the default MTU size, use the no form of the command.

Verifying the MTU Size

To verify the MTU size for an interface, use the show interfaces fastethernet or show interfaces gigabitethernet , or show interfaces tengigabitethernet privileged EXEC command and observe the value shown in the “MTU” field.

The following example shows an MTU size of 1500 bytes for interface port 0 (the first port) on the

Gigabit Ethernet SPA installed in the top subslot (0) of the MSC that is located in slot 3 of the Cisco

12000 series router:



Hardware is GigMac 1 Port 10 GigabitEthernet, address is 0008.7db3.8dfe (bia )


MTU 1500 bytes , BW 10000000 Kbit, DLY 10 usec, rely 255/255, load 1/255


Keepalive set (10 sec)

Full Duplex, 10000Mbps, link type is autonegotiation, media type is T

output flow-control is on, input flow-control is on

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:01, output 00:00:01, output hang never

Last clearing of "show interface" counters never

Queueing strategy: fifo

Output queue 0/40, 0 drops; input queue 0/75, 0 drops

Available Bandwidth 10000000 kilobits/sec

30 second input rate 0 bits/sec, 0 packets/sec

30 second output rate 0 bits/sec, 0 packets/sec

11 packets input, 1154 bytes, 0 no buffer

Received 1 broadcasts, 0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

0 watchdog, 0 multicast, 0 pause input

67 packets output, 20951 bytes, 0 underruns

0 output errors, 0 collisions, 1 interface resets

0 babbles, 0 late collision, 0 deferred

0 lost carrier, 0 no carrier, 0 pause output

0 output buffer failures, 0 output buffers swapped out

5-8


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring the Encapsulation Type

By default, the interfaces on the Cisco 1-port 10 Gigabit Ethernet SPA, 5-Port Gigabit Ethernet

SPA,8-Port Fast Ethernet SPA, and Cisco 10-port Gigabit Ethernet SPA support Advanced Research

Projects Agency (ARPA) encapsulation. They do not support configuration of service access point (SAP) or SNAP encapsulation for transmission of frames; however, the interfaces will properly receive frames that use SAP and SNAP encapsulation.

The only other encapsulation supported by the SPA interfaces is IEEE 802.1Q encapsulation for virtual

LANs (VLANs).

Configuring Autonegotiation on an Interface

Ethernet interfaces use a connection-setup algorithm called autonegotiation. Autonegotiation allows the local and remote devices to configure compatible settings for communication over the link. Using autonegotiation, each device advertises its transmission capabilities and then agrees upon the settings to be used for the link.

For the Fast Ethernet and Gigabit Ethernet interfaces on the Cisco 12000 series router, flow control is autonegotiated when autonegotiation is enabled. For the 10 Gigabit Ethernet interfaces, autonegotiation is not an option.

The following guidelines should be followed regarding autonegotiation:

•

•

•

If autonegotiation is disabled on one end of a link, it has to be disabled on the other end of the link.

If one end of a link has autonegotiation disabled while the other end of the link does not, the link will not come up properly on both ends.

Flow control is enabled by default.

Flow control will be on if autonegotiation is disabled on both ends of the link.

Disabling Autonegotiation

Autonegotiation is automatically enabled. During autonegotiation, advertisement for flow control is advertised. If the Fast Ethernet or Gigabit Ethernet interface is connected to a link that has autonegotiation disabled, autonegotiation should either be re-enabled on the other end of the link or disabled on the Fast Ethernet or Gigabit Ethernet SPA. Both ends of the link will not come up properly if only one end of the link has disabled autonegotiation.

To disable autonegotiation on a Fast Ethernet or Gigabit Ethernet interface, use the following command in interface configuration mode:

Command

Router(config-if)# no negotiation auto

Purpose

Disables autonegotiation on Gigabit Ethernet SPA interfaces. No advertisement of flow control occurs.

Enabling Autonegotiation

Autonegotiation is automatically enabled. During autonegotiation, advertisement and configuration of flow control occurs. To re-enable autonegotiation on a Fast Ethernet or Gigabit Ethernet interface, use the following command in interface configuration mode:

Release 12.0(33)S, OL-8832-01, Rev. C9


5-9



Command

Router(config-if)# negotiation auto

Purpose

Enables autonegotiation on Gigabit Ethernet SPA interfaces. Advertisement of flow control occurs.

Configuring a Subinterface on a VLAN

You can configure subinterfaces on the Cisco 1-port 10 Gigabit Ethernet SPA, 5-Port Gigabit Ethernet

SPA, 8-Port Fast Ethernet SPA, and Cisco 10-port Gigabit Ethernet SPA on a VLAN using IEEE 802.1Q encapsulation.

Note The Cisco 10-port Gigabit Ethernet SPA does not support Inter-Switch Link (ISL) encapsulation.

To configure a SPA subinterface on a VLAN, use the following commands beginning in interface configuration mode:

Step 1

Step 2

Step 3

Command

Router(config)# interface fastethernet slot / subslot / port .

subinterface-number or

Router(config)# interface gigabitethernet slot / subslot / port .

subinterface-number or

Purpose

Specifies the Fast Ethernet, Gigabit Ethernet, or Ten

Gigabit Ethernet interface to configure, where:

•


“Specifying the Interface Address” section on page 5-4

.

.

subinterface-number —Specifies a secondary interface (subinterface) number.

Router(config)# interface tengigabitethernet slot / subslot / port .

subinterface-number

Router(config-subif)# dot1q vlan-id encapsulation

Router(config-if)# ip address ip-address mask [ secondary ]

Defines the encapsulation format as IEEE 802.1Q

(“dot1q”), where vlan-id is the number of the VLAN

(1–4095).


•

•


mask —Specifies the mask for the associated IP subnet.

secondary —(Optional) Specifies that the configured address is a secondary IP address. If this keyword is omitted, the configured address is the primary IP address.

Verifying Subinterface Configuration on a VLAN

To verify the configuration of a subinterface and its status on the VLAN, use the show vlans privileged

EXEC command.

5-10


Release 12.0(33)S, OL-8832-01, Rev. C9



The following example shows the status of subinterface number 1 on port 0 on the SPA in VLAN number

200:

Router# show vlans

VLAN ID:200 (IEEE 802.1Q Encapsulation)

Protocols Configured: Received: Transmitted:

IP 0 14

VLAN trunk interfaces for VLAN ID 200:

GigabitEthernet4/1/0.1 (200)

IP:12.200.21.21

Total 0 packets, 0 bytes input

Total 2 packets, 120 bytes output

Configuring Flow Control Support on the Link

Flow control is turned on or off based on the result of the autonegotiation. For information on this process, see

“Configuring Autonegotiation on an Interface” section on page 5-9 .

Verifying Flow Control Status

To verify flow control status on a Fast Ethernet or Gigabit Ethernet interface on a SPA, use the show interfaces fastethernet , show interfaces gigabitethernet ,or show interfaces tengigabitethernet privileged EXEC command and view the “output flow-control is” and “ input flow-control is” output lines to see if input and output flow control is on or off. The “pause input” and “pause output” counters of the output of this command can be used to view the number of pause frames sent or received by the interface.

The following example shows that zero pause frames have been transmitted and received by the MAC device for interface port 3 (the fourth port) on the SPA located in subslot 0 of the MSC that is installed in slot 3 of the Cisco 12000 series router:



Hardware is GigabitEthernet, address is 0008.7db3.8e01 (bia 0008.7db3.8e01)





Full Duplex, 1000Mbps, link type is autonegotiation, media type is T output flow-control is on, input flow-control is on












0 watchdog, 0 multicast, 0 pause input



Release 12.0(33)S, OL-8832-01, Rev. C9


5-11


Verifying the Interface Configuration


0 lost carrier, 0 no carrier, 0 pause output


Saving the Configuration

To save your running configuration to nonvolatile random-access memory (NVRAM), use the following command in privileged EXEC configuration mode:

Command

Router# copy running-config startup-config

Purpose

Writes the new configuration to NVRAM.

For more information about managing configuration files, refer to the Cisco IOS Configuration

Fundamentals Configuration Guide, Release 12.0 and Cisco IOS Configuration Fundamentals

Command Reference, Release 12.0 publications.

Shutting Down and Restarting an Interface on a SPA

You can shut down and restart any of the interface ports on a SPA independently of each other. Shutting down an interface stops traffic and enters the interface into an “administratively down” state.

If you are preparing for an OIR of a SPA, it is not necessary to independently shut down each of the interfaces prior to deactivation of the SPA. The hw-module subslot shutdown command automatically stops traffic on the interfaces and deactivates them along with the SPA in preparation for OIR.

In similar fashion, you do not need to independently restart any interfaces on a SPA after OIR of a SPA or MSC.

To shut down an interface on a SPA, use the following command in interface configuration mode:

Command

Router(config-if)# shutdown

Purpose

Disables an interface.

To restart an interface on a SPA, use the following command in interface configuration mode:

Command


Purpose

Restarts a disabled interface.


Besides using the show running-configuration command to display your router configuration settings, you can use the show interfaces gigabitethernet command to get detailed information on a per-port basis for your Cisco 1-port 10 Gigabit Ethernet SPA, Cisco 1-Port 10-Gigabit Ethernet DWDM SPA,

5-Port Gigabit Ethernet SPA, and Cisco 10-port Gigabit Ethernet SPA. For the 8-Port Fast Ethernet SPA, show interfaces fastethernet can be entered to gather detailed per-port information.

5-12


Release 12.0(33)S, OL-8832-01, Rev. C9



Verifying Per-Port Interface Status

To find detailed interface information on a per-port basis for the Fast Ethernet or Gigabit Ethernet SPAs, use the show interfaces fastethernet , show interfaces gigabitethernet ,or show interfaces tengigabitethernet command. For a description of the command output, see


Command Reference.”

The following example provides sample output for interface port 0 on the Gigabit Ethernet SPA located in the top subslot (0) of the MSC that is installed in slot 3 of the Cisco 12000 series router:








Full Duplex, 10000Mbps, link type is autonegotiation, media type is T



















The following example provides sample output for interface port 0 on the Fast Ethernet SPA located in the top subslot (0) of the SIP that is installed in slot 7 of the Cisco 12000 series router:

Router# show interfaces fastethernet 7/0/0

FastEthernet7/0/0 is administratively down, line protocol is down

Hardware is FastEthernet, address is 0000.001c.a400 (bia 0000.001c.a400)




Full Duplex, 100Mbps, link type is autonegotiation, media type is 100BaseTx

output flow-control is unsupported, input flow-control is unsupported


Last input never, output never, output hang never





5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 0 bits/sec, 0 packets/sec






Transmitted 0 broadcasts



Release 12.0(33)S, OL-8832-01, Rev. C9 5-13


Configuration Examples





This section includes the following configuration examples:

•

Basic Interface Configuration Example, page 5-14

•

MAC Address Configuration Example, page 5-15

•

•

MTU Configuration Example, page 5-15

VLAN Configuration Example, page 5-16

Basic Interface Configuration Example

The following example shows how to enter global configuration mode to specify the interface that you want to configure, configure an IP address for the interface, and save the configuration. This example configures interface port 1 on the SPA that is located in subslot 0 of the MSC, that is installed in slot 3 of the Cisco 12000 series router:

!Enter global configuration mode

!

Router# configure terminal


!

! Specify the interface address

!

Router(config)# interface gigabitethernet 3/0/1

!

! Configure an IP address

!

Router(config-if)# ip address 192.168.50.1 255.255.255.0

!

! Start the interface

!

Router(config-if)# no shut

!

! Save the configuration to NVRAM

!

Router(config-if)# exit

Router# copy running-config startup-config

The following example shows the same configuration on a port, but with an IPv6 address:


!


5-14


Release 12.0(33)S, OL-8832-01, Rev. C9




!

!Enable IPv6 Routing

!

Router(config)#

!


!


!


!

Router(config-if)# ipv6 address 2001:10::1/64

Router(config-if)# ipv6 address FEC0:11:1001:11::1/64

!

! Start the interface

!

Router(config-if)# no shut

!


!



MAC Address Configuration Example

The following example changes the default MAC address on the interface to 1111.2222.3333:


!



!


!


!

! Modify the MAC address

!

Router(config-if)# mac-address 1111.2222.3333

MTU Configuration Example

The following example sets the interface MTU to 9216 bytes:

Note The SPA automatically adds an additional 36 bytes to the configured interface MTU size.


!


Release 12.0(33)S, OL-8832-01, Rev. C9


5-15


Configuring Dense Wavelength Division Multiplexing Controllers on Cisco IOS Software


!


!


!

! Configure the interface MTU

!

Router(config-if)# mtu 9216

VLAN Configuration Example

The following example creates subinterface number 268 on SPA interface port 2 (the third port), and configures the subinterface on the VLAN with ID number 269 using IEEE 802.1Q encapsulation:

Note The SPA does not support ISL encapsulation.


!



!


!

Router(config)# interface gigabitethernet 3/0/1.268

!

! Configure dot1q encapsulation and specify the VLAN ID

!

Router(config-subif)# encapsulation dot1q 268

Configuring Dense Wavelength Division Multiplexing

Controllers on Cisco IOS Software

This module describes the configuration of dense wavelength division multiplexing (DWDM) controller on routers supporting Cisco IOS software. DWDM is an optical technology that is used to increase bandwidth over existing fiber-optic backbones. DWDM can be configured on 1-Port 10-Gigabit Ethernet

DWDM SPA.

Feature History for Configuring DWDM Controller Interfaces

Release

Release 12.0(33)s

Modification

This feature was introduced on the Cisco 12000 Series Router.

Support was added for the 1-Port 10-Gigabit Ethernet DWDM SPA

(SPA-1X10GE-L-ITUC).

5-16


Release 12.0(33)S, OL-8832-01, Rev. C9


Contents

Contents

•

•

•

•

Prerequisites for Configuring DWDM Controller Interfaces, page 5-17

Information About the DWDM Controllers, page 5-17

How to Configure DWDM Controllers, page 5-18

Additional References, page 5-21

Prerequisites for Configuring DWDM Controller Interfaces

Before configuring a DWDM controller, be sure that the following tasks and conditions are met:

• You must be in a user group associated with a task group that includes the proper task IDs for

DWDM commands.

• Your SPA must support DWDM. The 1-Port 10-Gigabit Ethernet DWDM SPA supports DWDM.

Information About the DWDM Controllers

DWDM support in Cisco IOS software is based on the Optical Transport Network (OTN) protocol that is specified in ITU-T G.709. This standard combines the benefits of SONET/SDH technology with the multiwavelength networks of DWDM. It also provides for forward error correction (FEC) that can allow a reduction in network costs by reducing the number of regenerators used.

To enable multiservice transport, OTN uses the concept of a wrapped overhead (OH). To illustrate this structure:

•

•

Optical channel payload unit (OPU) OH information is added to the information payload to form the

OPU. The OPU OH includes information to support the adaptation of client signals.

Optical channel data unit (ODU) OH is added to the OPU to create the ODU. The ODU OH includes information for maintenance and operational functions to support optical channels.

•

•

Optical channel transport unit (OTU) OH together with the FEC is added to form the OTU. The OTU

OH includes information for operational functions to support the transport by way of one or more optical channel connections.

Optical channel (OCh) OH is added to form the OCh. The OCh provides the OTN management functionality and contains four subparts: the OPU, ODU, OTU, and frame alignment signal (FAS).

See

Figure 5-2 .

Figure 5-2

FAS OTU

OTN Optical Channel Structure

Payload

ODU

FEC

Release 12.0(33)S, OL-8832-01, Rev. C9


5-17


How to Configure DWDM Controllers


The DWDM controllers are configured in the physical layer control element of the Cisco IOS software configuration space. This configuration is done using the controller dwdm command, and is described in the following tasks.

•

Configuring the Optical Parameters, page 5-18

•

Configuring G.709 Parameters, page 5-20

Note All interface configuration tasks for the GE interfaces still must be performed in interface configuration mode. .

Configuring the Optical Parameters

This task describes how to configure the receive power threshold and the wavelength parameters for the

DWDM controller. You should verify that the optical parameters are configured correctly for your

DWDM installation and if necessary, perform this task.

Prerequisites

The rx-threshold and wavelength commands can be used only when the controller is in the shutdown state. Use the shutdown command.

SUMMARY STEPS

6.

7.

4.

5.

8.

1.

2.

3.

configure controller dwdm <slot>/<subslot>/<port> shutdown rx-threshold power-level wavelength channel-number g709 fec enhanced no shutdown show controller dwdm <slot>/<subslot>/<port> [ g709 | optics | wavelegth-map ]

5-18


Release 12.0(33)S, OL-8832-01, Rev. C9



DETAILED STEPS

Command or Action

Step 1 configure t

Purpose


Example:

Router# configure t

Step 2 controller dwdm <slot>/<subslot>/<port> Specifies the DWDM controller name in the notation slot/subslot/port and enters DWDM configuration mode.

Example:

Router(config)# controller dwdm 3/0/0

Step 3 shutdown Disables the DWDM controller. You must disable the controller before you can use the DWDM configuration commands.

Example:

Router(config-dwdm)# shutdown

Step 4 rx-threshold power-level

Example:

Router(config-dwdm)# rx-threshold -10

Step 5 wavelength channel-number

Example:

Router(config-dwdm)# wavelength 1

Step 6 g709 fec enhanced

Configures the transponder receive power threshold for the

DWDM controllers. The range for the parameters are provided by the platform specific part of the software at the time of the init to the configuration utility. The all inclusive range of the values will be shown to the CLI options, however only the acceptable range is allowed to be configured on the specific controller.

Configures the channel number corresponding to the first wavelength. Values are selected between 1 to 80 and the platform supported will be checked before applying the configuration. The default channel selected is first channel on the transponder.

Configures the forward error correction (fec) mode for the

DWDM controller to enhanced.

Example:

Router(config-dwdm)# g709 fec enhanced

Step 7 no shutdown

Example:

Router(config-dwdm)# no shutdown

Step 8 show controllers dwdm <slot>/<subslot>/<port>

[ g709 | optics | wavelegth-map ]

Removes the shutdown configuration.

• The removal of the shutdown configuration removes the forced administrative down on the controller, enabling the controller to move to an up or down state.

Displays the g709 OTN protocol alarms, output power level, input power level, wavelength, and laser bias current monitoring information.

Example:

Router# show controller dwdm 3/0/0 g709

Troubleshooting Tips

You must shut down the controller before you can use the DWDM configuration commands.

Release 12.0(33)S, OL-8832-01, Rev. C9


5-19



Configuring G.709 Parameters

This task describes how to customize the alarm display and the thresholds for alerts and forward error correction (Refer ITU standards for STD FEC=ITU G.975 and Enhanced FEC=ITU G.975.1). You need to use this task only if the default values are not correct for your installation.

Prerequisites

The g709 disable , loopback , and g709 fec commands can be used only when the controller is in the shutdown state. Use the no shutdown command after configurating the parameters to remove the controller from shutdown state and enabling the controller to move to up or down state.

SUMMARY STEPS

7.

8.

5.

6.

9.

3.

4.

1.

2.

configure controller dwdm <slot>/<subslot>/<port> shutdown g709 disable loopback internal g709 fec { enhanced | standard } g709 { odu | otu } alarm disable no shutdown show controllers dwdm <slot>/<subslot>/<port> g709

DETAILED STEPS

Purpose



Step 1 configure

Example:

Router# configure

Step 2 controller dwdm <slot>/<subslot>/<port>

Example:

Router(config)# controller dwdm 3/0/0

Step 3 shutdown

Example:

Router(config-dwdm)# shutdown

Step 4 g709 disable

Example:

Router(config-dwdm)# g709 disable

Specifies the DWDM controller name in the notation

<slot>/<subslot>/<port> and enters DWDM configuration mode.

Disables the DWDM controller. You must disable the controller before you can use the DWDM configuration commands.

(Optional) Disables the G.709 wrapper. The wrapper is enabled by default.

5-20


Release 12.0(33)S, OL-8832-01, Rev. C9


Additional References


Step 5 loopback { internal | line }

Purpose

(Optional) Configures the DWDM controller for loopback mode.

Example:

Router(config-dwdm)# loopback internal

Step 6 g709 fec { enhanced | standard } (Optional) Configures the forward error correction mode

(FEC) for the DWDM controller. By default, enhanced FEC is enabled.

Example:

Router(config-dwdm)# g709 fec enhanced

Step 7 g709 { odu | otu } alarm disable

Example:

Router(config-dwdm)# g709 odu bdi disable

Step 8 no shutdown

Example:

Router(config-dwdm)# no shutdown

Step 9 show controllers dwdm <slot>/<subslot>/<port> g709

(Optional) Disables the logging of selected optical channel data unit (ODU) alarms or optical channel transport unit

(OTU) alarms to the console for a DWDM controller. By default, all alarms are logged to the console.

Removes the shutdown configuration.

• The removal of the shutdown configuration removes the forced administrative down on the controller, enabling the controller to move to an up or down state.

Displays detailed information about G.709 OTN protocol alarms and counters for Bit Errors, along with the FEC statistics and threshold based alerts.

Example:

Router# show controller dwdm 3/0/0 g709

Examples

The following example shows how to bring the DWDM controller down before using the configuration commands:

Router# configure

Router(config)# controller dwdm 3/0/0

Router(config-dwdm)# shutdown

Router(config-dwdm)# rx-threshold 0

Router(config-dwdm)# wavelength 1

Router(config-dwdm)# no shutdown

The following example shows how to customize the alarm display and the thresholds for alerts and forward error correction (FEC):

Router# configure



Router(config-dwdm)# no g709 disable

Router(config-dwdm)# loopback internal

Router(config-dwdm)# g709 fec standard

Router(config-dwdm)# g709 odu bdi disable



The following sections provide references related to DWDM controller configuration.

Release 12.0(33)S, OL-8832-01, Rev. C9


5-21



Standards

Standards

ITU-T G.709/Y.1331

MIBs

Title

Interfaces for the optical transport network (OTN)

MIBs

No new or modified MIBs are supported by this feature, and support for existing MIBs has not been modified by this feature

MIBs Link

To locate and download MIBs for selected platforms using

Cisco IOS software, use the Cisco MIB Locator found at the following URL: http://cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

RFCs

RFCs

No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified by this feature.

Title

—

Technical Assistance

Description

The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

Link http://www.cisco.com/techsupport

5-22


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

6

Troubleshooting the Gigabit Ethernet SPA

This chapter describes techniques that you can use to troubleshoot the operation of your Gigabit Ethernet

SPAs.

It includes the following sections:

•

General Troubleshooting Information, page 6-1

•

•

•

•

•

•

Performing Basic Interface Troubleshooting, page 6-2

Understanding SPA Automatic Recovery, page 6-6

Configuring the Interface for Internal Loopback, page 6-7

Using the Cisco IOS Event Tracer to Troubleshoot Problems, page 6-8

Preparing for Online Insertion and Removal of a SPA, page 6-8

Cleaning Optics, page 6-8

The first section provides information about basic interface troubleshooting. If you are having a problem with your SPA, use the steps in the

“Performing Basic Interface Troubleshooting” section to begin your

investigation of a possible interface configuration problem.

To perform more advanced troubleshooting, see the other sections in this chapter.

General Troubleshooting Information

This section describes general information for troubleshooting SIPs and SPAs. It includes the following sections:

•

Using show Commands, page 6-2

The debug hw-module subslot command is intended for use by Cisco Systems technical support personnel. For more information about the debug hw-module subslot command, see

Chapter 19, “SIP and SPA Command Reference.”

Caution Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.


6-1 Release 12.0(33)S, OL-8832-01, Rev. C9

Chapter 6 Troubleshooting the Gigabit Ethernet SPA

Performing Basic Interface Troubleshooting

Using show Commands

There are several show commands that you can use to monitor and troubleshoot the SIPs and SPAs on the Cisco 12000 Series Router. This chapter describes using the show interfaces and show controllers commands to perform troubleshooting of your SPA.

For more information about show commands to verify and monitor SIPs and SPAs, see the following chapters of this guide:

•

Chapter 5, “Configuring the Fast Ethernet and Gigabit Ethernet SPAs”

•

•

Chapter 7, “Command Summary for Gigabit Ethernet SPAs”

Chapter 19, “SIP and SPA Command Reference”


You can perform most of the basic interface troubleshooting using the show interfaces gigabitethernet command and examining several areas of the output to determine how the interface is operating.

The following example shows output from the show interfaces gigabitethernet command with some of the significant areas of the output to observe shown in bold:


GigabitEthernet3/0/0 is up, line protocol is up






Full Duplex , 10000Mbps , link type is autonegotiation, media type is T



Last input 00:00:01, output 00:00:01, output hang never












0 output errors, 0 collisions , 1 interface resets

0 babbles, 0 late collision , 0 deferred

0 lost carrier , 0 no carrier , 0 pause output


6-2


Release 12.0(33)S, OL-8832-01, Rev. C9



To verify that your interface is operating properly, complete the steps in

Table 6-1

:

Table 6-1

Step 1

Step 2

Step 3

Step 4

Basic Interface Troubleshooting Steps

Action

From global configuration mode, enter the show interfaces gigabitethernet command.

Verify that the interface is up.

Example


Verify that the line protocol is up.

Verify that the interface duplex mode matches the remote interface configuration.


GigabitEthernet2/1/1 is up , line protocol is up


GigabitEthernet2/1/1 is up, line protocol is up

The following example shows that the local interface is currently operating in full-duplex mode:


[text omitted]

Step 5

Step 6

Step 7

Verify that the interface speed matches the speed on the remote interface.


Full-duplex , 100Mb/s, 100BaseTX/FX

The following example shows that the local interface is currently operating at 100Mbps:

Observe the output hang status on the interface.


.

.

.

.

.

.


Last input 00:00:22, output 00:00:02, output hang never

Observe the CRC counter.

.

.


.


Full-duplex, 100Mb/s , 100BaseTX/FX

.

.

.

.

.


.


5 packets input, 320 bytes

Received 1 broadcasts (0 IP multicast)

0 runts, 0 giants, 0 throttles

.

.

0 input errors, 0 CRC , 0 frame, 0 overrun, 0 ignored

.

Release 12.0(33)S, OL-8832-01, Rev. C9


6-3



Table 6-1

Step 8

Basic Interface Troubleshooting Steps

Action

Observe the late collision counter.

Step 9 Observe the carrier signal counters.

Example

.

.

.

.

.


.

0 input packets with dribble condition detected



0 babbles, 0 late collision , 0 deferred

.

.

.

.


.



2 lost carrier, 0 no carrier

.

•

•

•

For more information about the verification steps in and possible responses to correct detected problems, see the following sections:

Verifying the Interface is Up, page 6-4

Verifying the Line Protocol is Up, page 6-5

•

•

•

Verifying Output Hang Status, page 6-5

Verifying the CRC Counter, page 6-5

Verifying Late Collisions, page 6-5

Verifying the Carrier Signal, page 6-5

Verifying the Interface is Up

In the output from the show interfaces gigabitethernet command, verify that the interface is up. If the interface is down, perform the following corrective actions:

• If the interface is administratively down , use the no shutdown interface configuration command to enable the interface.

•

•

Be sure that the cable is fully connected.

Verify that the cable is not bent or damaged. If the cable is bent or damaged, the signal will be degraded.

• Verify that a hardware failure has not occurred. Observe the LEDs to confirm the failure. See the other troubleshooting sections of this chapter, and refer to the Cisco 12000 Series Router SIP and

SPA Hardware Installation Guide . If the hardware has failed, replace the SPA as necessary.

6-4


Release 12.0(33)S, OL-8832-01, Rev. C9



Verifying the Line Protocol is Up

In the output from the show interfaces gigabitethernet command, verify that the line protocol is up. If the line protocol is down, the line protocol software processes have determined that the line is unusable.

Perform the following corrective actions:

• Swap the cable.

•

•

Check the local and remote interface for misconfiguration.

Verify that a hardware failure has not occurred. Observe the LEDs to confirm the failure. See the other troubleshooting sections of this chapter, and refer to the Cisco 12000 Series Router SIP and

SPA Hardware Installation Guide . If the hardware has failed, replace the SPA as necessary.

Verifying Output Hang Status

In the output from the show interfaces gigabitethernet command, observe the value of the output hang field.

The output hang provides the number of hours, minutes, and seconds since the last reset caused by a lengthy transmission. When the number of hours the field exceeds 24 hours, the number of days and hours is shown. If the field overflows, asterisks are printed. The field shows a value of never if no output hangs have occurred.

Verifying the CRC Counter

In the output from the show interfaces gigabitethernet command, observe the value of the CRC counter. Excessive noise will cause high CRC errors accompanied by a low number of collisions.

Perform the following corrective actions if you encounter high CRC errors:

•

•

Check the cables for damage.

Verify that the correct cables are being used for the SPA interface.

Verifying Late Collisions

In the output from the show interfaces gigabitethernet command, observe the value of the late collision counter.

Perform the following corrective actions if you encounter late collisions on the interface:

•

•

Verify that the duplex mode on the local and remote interface match. Late collisions occur when there is a duplex mode mismatch.

Verify the length of the Ethernet cables. Late collisions result from cables that are too long.

Verifying the Carrier Signal

In the output from the show interfaces gigabitethernet command, observe the value of the carrier signal counters. The lost carrier counter shows the number of times that the carrier was lost during transmission. The no carrier counter shows the number of times that the carrier was not present during transmission.


Release 12.0(33)S, OL-8832-01, Rev. C9 6-5


Understanding SPA Automatic Recovery

Carrier signal resets can occur when an interface is in loopback mode or shut down.

Perform the following corrective actions if you observe the carrier signal counter incrementing outside of these conditions:

•

•

Check the interface for a malfunction.

Check for a cable problem.

Understanding SPA Automatic Recovery

When the Gigabit Ethernet SPAs encounter thresholds for certain types of errors and identifies a fatal error, the SPA initiates an automatic recovery process.

You do not need to take any action unless the error counters reach a certain threshold, and multiple attempts for automatic recovery by the SPA fail.

The GigabitEthernet SPAs might perform automatic recovery for the following types of errors:

•

•

•

•

SPI4 TX/RX out of frame

SPI4 TX train valid

SPI4 TX DIP4

SPI4 RX DIP2

Note These SPA error counters do not appear in the show controllers gigabitethernet command output until at least one SPI4 error occurs.

When Automatic Recovery Occurs

If the SPI4 errors occur more than 25 times within 10 milliseconds, the SPA automatically deactivates and reactivates itself. Error messages are logged on the console indicating the source of the error and the status of the recovery.

If Automatic Recovery Fails

If the SPA attempts automatic recovery more than five times in an hour, then the SPA deactivates itself and remains deactivated.

To troubleshoot automatic recovery failure for a SPA, perform the following steps:

Step 1

Step 2

Step 3

Use the show hw-module subslot slot / subslot oir command to verify the status of the SPA. The status is shown as “failed” if the SPA has been powered off due to five consecutive failures.

If you verify that automatic recovery has failed, perform OIR of the SPA. For information about performing an OIR, see the

“Preparing for Online Insertion and Removal of a SPA” section on page 6-8

.

If reseating the SPA after OIR does not resolve the problem, replace the SPA hardware.

6-6


Release 12.0(33)S, OL-8832-01, Rev. C9


Configuring the Interface for Internal Loopback


Loopback support is useful for testing the interface without connectivity to the network, or for diagnosing equipment malfunctions between the interface and a device. The Gigabit Ethernet SPAs supports both an internal and an external loopback mode. The external loopback mode requires the use of a loopback cable and implements a loopback through the transceiver on the SPA.

You can also configure an internal loopback without the use of a loopback cable that implements a loopback at the PHY device internally on a Gigabit Ethernet interface port, or at the MAC device internally on a Gigabit Ethernet interface port. By default, loopback is disabled.


To enable internal loopback at the PHY device for an interface on a SPA, use the following commands beginning in interface configuration mode:

Step 10


Router(config-if)# loopback internal

Purpose

Enables an interface for internal loopback on the Gigabit Ethernet

SPA.

Configuring the Interface for External Loopback

Before beginning external loopback testing, remember that the external loopback mode requires the use of a loopback cable.

To enable external loopback, use the following commands beginning in interface configuration mode:

Command

Router(config-if)# loopback external

Purpose

Enables an interface for external loopback on the

Gigabit Ethernet SPA.

Verifying Loopback Status

To verify whether loopback is enabled on an interface port on a SPA, use the show interfaces gigabitethernet privileged EXEC command and observe the value shown in the “loopback” field.

The following example shows that loopback is disabled for interface port 0 (the first port) on the SPA installed in the top (0) subslot of the SIP that is located in slot 3 of the Cisco 12000 Series Router:





.

.


Encapsulation ARPA, loopback not set

.

Release 12.0(33)S, OL-8832-01, Rev. C9


6-7


Using the Cisco IOS Event Tracer to Troubleshoot Problems

Using the Cisco IOS Event Tracer to Troubleshoot Problems

Note This feature is intended for use as a software diagnostic tool and should be configured only under the direction of a Cisco Technical Assistance Center (TAC) representative.

The Event Tracer feature provides a binary trace facility for troubleshooting Cisco IOS software. This feature gives Cisco service representatives additional insight into the operation of the Cisco IOS software and can be useful in helping to diagnose problems in the unlikely event of an operating system malfunction or, in the case of redundant systems, route processor switchover.

Event tracing works by reading informational messages from specific Cisco IOS software subsystem components that have been preprogrammed to work with event tracing, and by logging messages from those components into system memory. Trace messages stored in memory can be displayed on the screen or saved to a file for later analysis.

The SPAs currently support the “spa” component to trace SPA OIR-related events.

For more information about using the Event Tracer feature, refer to the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s18/evn ttrcr.htm

Preparing for Online Insertion and Removal of a SPA

The Cisco 12000 Series Router supports online insertion and removal (OIR) of the SIP, in addition to each of the SPAs. Therefore, you can remove a SIP with its SPAs still intact, or you can remove a SPA independently from the SIP, leaving the SIP installed in the router.

This means that a SIP can remain installed in the router with one SPA remaining active, while you remove another SPA from one of the SIP subslots. If you are not planning to immediately replace a SPA into the SIP, then be sure to install a blank filler plate in the subslot. The SIP should always be fully installed with either functional SPAs or blank filler plates.

Cleaning Optics

It is important to inspect and clean fiber-optic components before making a fiber-optic connection (for example, plugging a fiber-optic connector into a fiber-optic receptacle). Any contamination in the fiber connection can cause the optic component or the whole system to fail. Even microscopic dust particles, oil from human hands, film residues (condensed from vapors in the air), and powdery coatings (left after water or other solvents evaporate) can cause a variety of problems for optical connections.

Caution With the high-powered lasers now in use, any contaminant can be burned into the fiber end face if it blocks the core while the laser is turned on. This burning may damage the optical surface enough that it cannot be cleaned.

See the following URL for instructions on how to clean fiber-optic components: http://www.cisco.com/warp/public/127/cleanfiber2.html

6-8


Release 12.0(33)S, OL-8832-01, Rev. C9


Cleaning Optics

Always follow the fiber-optic cleaning procedures carefully. The goal is to eliminate any dust or contamination and provide a clean environment for the fiber-optic connection. Inspection, cleaning, and reinspection are critical steps that must be performed before making any fiber-optic connection.

Release 12.0(33)S, OL-8832-01, Rev. C9


6-9

Cleaning Optics


6-10


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

7

Command Summary for Gigabit Ethernet SPAs

Table 7-1 provides an alphabetical list of the most significant commands that are needed to configure,

monitor, and maintain the Gigabit Ethernet shared port adapters (SPAs). For more information about the commands, see


in this book, and the Cisco IOS

Release 12.0 command reference and master index publications .

Table 7-1 Command Summary

Command

Router(config-subif)# encapsulation dot1q vlan-id

[ native ]

Purpose

Enables IEEE 802.1Q encapsulation of traffic on a specified subinterface in VLANs.

Router(config)# ip accounting mac-address { input | output }

Enables MAC address accounting. MAC address accounting provides accounting information for IP traffic based on the source and destination MAC addresses of the LAN interfaces.

Sets a primary or secondary IP address for an interface.

Router(config-if)# ip address ip-address mask

[ secondary ]

Router(config-if)# ipv6 address prefix-name ipv6-prefix / prefix-length

Router(config)# interface gigabitethernet slot / subslot / port [ .


Sets an IPv6 general prefix and enables IPv6 processing on an interface.

Specifies the Gigabit Ethernet interface to configure.

Router(config-if)#

Router(config-if)#

Router# loopback internal

Router(config-if)# loopback external

Router(config-if)# mac-address ieee-address


Router(config-if)# negotiation auto

Router(config-if)# no negotiation auto no shutdown show interfaces gigabitethernet

Enables internal loopback mode.

Enables external loopback mode.

Modifies the default Media Access Control (MAC) address of an interface to some user-defined address.

Configures the maximum packet size for an interface.

Enables advertisement of flow control on a Gigabit Ethernet interface.

Disables advertisement of flow control on a Gigabit Ethernet interface. Autonegotiation is enabled by default, so this command is required if you want to change the configuration.

Enables an interface.

Displays various Gigabit Ethernet interface statistics.


7-1 Release 12.0(33)S, OL-8832-01, Rev. C9

Chapter 7 Command Summary for Gigabit Ethernet SPAs

Table 7-1 Command Summary (continued)

Command Purpose

Router# show controller dwdm Displays error and alarm information that is useful in troubleshooting line problems.

Router# show vlans [ vlan-id ]

Router(config-if)# standby [ group-number ] ip

[ ip-address [ secondary ]]

Displays VLAN subinterfaces.

Creates (or enables) the HSRP group using its number and virtual IP address.

7-2


Release 12.0(33)S, OL-8832-01, Rev. C9

P A R T 3

Serial Shared Port Adapters

C H A P T E R

8

Overview of the Serial SPAs

This chapter provides an overview of the release history, and feature and MIB support for the

Cisco 12000 SIP-400, Cisco 12000 SIP-401, Cisco 12000 SIP-501, and Cisco 12000 SIP-601with the

2-Port and 4-Port Clear Channel T3/E3 SPA, 2-Port and 4-Port Channelized T3 SPA, 1-Port Channelized

OC-3/STM-1 SPA, and the 8-Port Channelized T1/E1 SPA.


• Release History, page 8-1

•

•

•




Release History


Cisco IOS Release 12.0S Support for the following hardware was introduced on the

Cisco 12000 Series routers:

•

•

•

•

•

•

•

•

Cisco 12000 SIP-400

Cisco 12000 SIP-401

Cisco 12000 SIP-501

Cisco 12000 SIP-601


2-Port and 4-Port Channelized T3 SPA




This section provides a list of some of the primary features supported by the SIP and SPA hardware and software.


8-1 Release 12.0(33)S, OL-8832-01, Rev. C9

Chapter 8 Overview of the Serial SPAs


SIP-400 Features

The SIP-400 is a carrier card designed to process packets between different Shared Port Adapters (SPAs) and the Cisco 12000.

•

•

•

Online insertion and removal (OIR)

Supports up to four single-height or two double-height Shared Port Adaptors (SPAs).

•

Field Programmable Gate Array (FPGA) upgrade support

The SIP-400 supports the standard FPGA upgrade methods for the Cisco 12000 Series router.

Compact Flash for code upgrade

SPA Features

The following is a list of some of the significant software features supported by the 2-Port and 4-Port

Channelized T3 SPA, 2-Port and 4-Port Clear Channel T3/E3 SPA, 8-Port Channelized T1/E1 SPA, and

1-Port Channelized OC-3/STM-1 SPA:

•

•

•

SONET and SDH multiplexing

24-hour history maintained for error statistics and failure counts, at 15-minute intervals

•

Software selectable between E3 or T3 framing on each card (ports are configured as all T3 or E3).

Applies to the 2 and 4-Port T3/E3 SPA.

Layer 2 encapsulation support:

–

–

Point-to-Point Protocol (PPP)

High-level Data Link Control (HDLC)

•

•

•

•

•

•

•

•

•

– Frame Relay

Internal or network clock (selectable per port)

Online insertion and removal (OIR)

Hot standby router protocol (HSRP)

Alarm reporting-24-hour history maintained, 15-minute intervals on all errors

16- and 32-bit cyclic redundancy checks (CRC) supported (16-bit default)

Local and remote loopback

Bit error rate testing (BERT) pattern generation and detection per port

Dynamic provisioning— Dynamic provisioning allows for the addition of new customer circuits within a channelized interface without affecting other customers.

FPD (field programmable device upgrades)

Channelized T1 Features

–

–

All ports can be fully channelized down to DS0

Data rates in multiples of 56Kbps or 64Kbps per channel

–

–

Maximum 1.536Mbps for each T1 port

D4 (SF) and ESF support for each T1 port

8-2


Release 12.0(33)S, OL-8832-01, Rev. C9



– ANSI T1.403 and AT&T TR54016 CI FDL Support

– Internal and receiver recovered clocking modes

–

–

Short haul and long haul CSU support

B8ZS and AMI line encoding

–

–

J1 framing (2 and 4-Port CT3 SPA)

Support for Multilink Frame Relay (MLFR)

Channelized T3 Features

–

–

Binary 3-zero substitution (B3ZS) line coding

Fragmentation counter support (supported only on the 2-Port and 4-Port Channelized T3 SPA)

–

–

Compliant with DS3 pulse mask per ANSI T1.102-1993

DS3 far-end alarm and control (FEAC) channel support

–

–

Full duplex connectivity at DS-3 rate (44.736 MHz)

672 DS0s per T3

–

–

Loopback modes: DTE, local, dual, and network

C-bit or M23 framing (software selectable)

–

–

Line build-out: configured for up to 450 feet (135 m) of type 734A or equivalent coaxial cable

DS-3 alarm/event detection (once per second polling)

–

- Alarm indication signal (AIS)

- Out of frame (OOF)

- Far-end receive failure (FERF)

Full FDL support and FDL performance monitoring

– Subrate and scrambling features for these DSU vendors:

- Digital Link

- ADC Kentrox

- Adtran

- Verilink

- Larscom

Unchannelized E1 Features

– Maximum 1.984Mbps for each E1 port in framed mode and a 2.048Mbps in unframed E1 mode

–

–

All ports can be fully channelized down to DS0

Compliant with ITU G.703, G.704, ETSI and ETS300156

–

–

Internal and receiver recovered clocking modes

HDB3 and AMI line encoding

Release 12.0(33)S, OL-8832-01, Rev. C9


8-3


Restrictions

Unchannelized E3 Features

– Full duplex connectivity at E3 rate (34.368 MHz)

–

–

Supports G.751 or G.832 framing (software selectable)

Hi-density bipolar with three zones (HD3B) line coding

–

–

Compliant with E3 pulse mask

Line build-out: configured for up to 450 feet (135 m) of type 728A or equivalent coaxial cable

–

–

Loopback modes: DTE, local, dual, and network

E3 alarm/event detection (once per second polling)

– Subrate and scrambling features for these DSU vendors:

- Digital Link

- ADC Kentrox

- Adtran

- Verilink

- Larscom

Restrictions

• The following features are supported only on channelized SPAs:

–

–

End-to-end FRF.12 fragmentation support

Link Fragmentation and Interleaving (LFI) support

Supported MIBs

•

•

•

The following MIBs are supported in Cisco IOS Release 12.2S for the serial SPAs on the

Cisco 12000 Series routers:

All serial SPAs:

• CISCO-ENTITY-ALARM-MIB

•

•

•

•

CISCO-CLASS-BASED-QOS-MIB

CISCO-ENVMON-MIB (For NPEs, NSEs, line cards, and SIPs only)

CISCO-ENTITY-ASSET-MIB

CISCO-ENTITY-FRU-CONTROL-MIB

•

•

•

CISCO-ENTITY-SENSOR-MIB

ENTITY-MIB

IF-MIB

RMON-MIB

MPLS-LDP-MIB

MPLS-LSR-MIB

8-4


Release 12.0(33)S, OL-8832-01, Rev. C9



•

•

MPLS-TE-MIB

MPLS-VPN-MIB

2 and 4-Port T3/E3 SPAs:

• DS3/E3 MIB

8-Port Channelized T1/E1 SPA:

• DS1/E1 MIB

2 or 4-Port CT3 SPA

•

•

DS1-MIB

DS3-MIB

CISCO-FRAME-RELAY-MIB •

•

•

IANAifType-MIB

RFC1381-MIB






To verify the SPA hardware type that is installed in your Cisco 12000 Series router, you can use the show diagbus command or the show interfaces command (can be used only if the interface has been configured). There are several other commands on the Cisco 12000 series routers that also provide SPA hardware information.

Table 8-1 shows the hardware description that appears in the show command output for each type of SPA that is supported on the Cisco 12000 series router.


SPA





Description in show interfaces and show controllers commands

“Hardware is SPA-4XT3/E3”

“Hardware is SPA-2XT3/E3”

“Hardware is 2 ports CT3 SPA”

“Hardware is 4 ports CT3 SPA”

Release 12.0(33)S, OL-8832-01, Rev. C9


8-5



Example of the show interface Command

The following example shows output from the show interface serial 0/0/0 command on a Cisco 12008 router with a 4-Port Channelized T3 SPA installed in slot 7:

Router# s how interface serial 7/0/0/1

Serial7/0/0/1:0 is down, line protocol is down

Hardware is SPA-4XCT3/DS0


Encapsulation FRAME-RELAY, crc 16, loopback not set


LMI enq sent 0, LMI stat recvd 0,LMI upd recvd 0

LMI enq recvd 0, LMI stat sent 0,LMI upd sent 0, DCE LMI down

LMI DLCI 1023 LMI type is CISCO frame relay DCE

Broadcast queue 0/64, broadcasts sent/dropped 0/0, interface broadcasts 0


Last clearing of "show interface" counters 1d17h








0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort




0 carrier transitions no alarm present

VC 1: timeslot(s): 1-24, Transmitter delay 0, non-inverted data

Router#

Router# show gsr

Slot 0 type = Performance Route Processor

state = ACTV RP IOS Running ACTIVE

Slot 3 type = 12 Port Packet over DS3


Slot 4 type = 4 Port Packet Over SONET OC-12c/STM-4


Slot 6 type = 1 Port Packet Over SONET OC-192c/STM-64




subslot 7/0: SPA-4XCT3/DS0 (0x43B), status is ok

subslot 7/1: Empty

subslot 7/2: SPA-1XCHSTM1/OC3 (0x463), status is out of service

subslot 7/3: Empty

Slot 16 type = Clock Scheduler Card 16XOC192


Slot 17 type = Clock Scheduler Card 16XOC192

state = Card Powered PRIMARY CLOCK

Slot 18 type = Switch Fabric Card 16XOC192










Slot 27 type = Bus Board(16)


8-6 Release 12.0(33)S, OL-8832-01, Rev. C9








Release 12.0(33)S, OL-8832-01, Rev. C9


8-7



8-8


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

9

Configuring the 2-Port and 4-Port Channelized T3

SPA

9

This chapter provides information about configuring the 2-Port and 4-Port Channelized T3 Shared Port

Adapters (SPAs) on the Cisco 12000 series routers. It includes the following sections:

•

•



• Configuration Examples, page 9-20




For more information about the commands used in this chapter, see Chapter 19, “SIP and SPA Command

Reference,” in this guide, which documents new and modified commands . Also refer to the related

Cisco IOS Release 12.0 software command reference and master index publications. For more information about accessing these publications, see the Related Documentation section in the Preface .


This section describes how to configure the serial SPAs for the Cisco 12000 series routers and includes information about verifying the configuration.

It includes the following topics:

•

•

•

•


Specifying the Interface Address on a SPA, page 9-7

Optional Configurations, page 9-8


Release 12.0(33)S, OL-8832-01, Rev. C9


9-1

Chapter 9 Configuring the 2-Port and 4-Port Channelized T3 SPA



This section lists the required configuration steps to configure the 2-Port and 4-Port Channelized T3

SPA. Some of the required configuration commands implement default values that might be appropriate for your network.

•

•

•

•

Configuring the T3 Controller, page 9-2

Configuring the Logical T1 Interfaces, page 9-3

Verifying T3 Controller Configuration, page 9-5

Verifying Interface Configuration, page 9-6

Note To better understand the address format used to specify the physical location of the SPA Interface

Processor (SIP), SPA, and interfaces, see the section Specifying the Interface Address on a SPA, page 9-7 .

Configuring the T3 Controller

To configure the T3 controller for the 2-Port and 4-Port Channelized T3 SPA, complete these steps:

Step 1

Step 2

Command


Router(config)# controller t3 slot/subslot/port

Step 3 Router(config-controller)# [ no ] channelized

Purpose


Selects the controller to configure and enters controller configuration mode.

• slot/subslot/port— Specifies the location of the

CT3 SPA port. See: “Specifying the Interface

Address on a SPA” section on page 9-7 .

(Optional) Specifies the channelization mode.

• channelized —In channelized mode, the T3 link can be channelized into 28 T1s, and each

T1 can be further channelized into 24 DS0s.

This is the default.

• no channelized —In the unchannelized mode the T3 link provides a single high-speed data channel of 44210 kbps.

9-2


Release 12.0(33)S, OL-8832-01, Rev. C9



Step 4

Step 5

Step 6

Command Purpose

Router(config-controller)# framing { auto-detect

| c-bit | m23 }

(Optional) Specifies the framing type in subrate T3 mode.

•

• auto-detect —Detects the framing type at the device at the end of the line and switches to that framing type. If both devices are set to auto-detect, c-bit framing is used.

c-bit —Specifies C-bit parity framing. This is the default.

•

Note m23 —Specifies M23 framing.

To set the framing type for an un-channelized T3, see: “Configuring T3

Framing” section on page 9-14 .

(Optional) Specifies the clock source.

Router(config-controller)# clock source

{ internal | line }

•

• internal —Specifies that the internal clock source is used. Default for channelized mode.

line —Specifies that the network clock source is used. Default for un-channelized mode.

Router(config-controller)# cablelength { 0 450 } (Optional) Specifies the cable length. The default is 50 ft.

• 0-450 —Cable length in feet.

Configuring the Logical T1 Interfaces

If channelized mode is configured for the T3 controller, use the following procedure to configure the logical T1 interfaces.

Step 1

Step 2

Command



Purpose





Address on a SPA” section on page 9-7

Release 12.0(33)S, OL-8832-01, Rev. C9


9-3



Step 3

Step 4

Command

Router(config-controller)# t1 t1-number channel-group channel-number timeslots range

[ speed { 56 | 64 }]

Purpose

Specifies the T1 channel and timeslots to be mapped to each channel.

•

• t1-number —T1 number from 1–28.

channel-number —Specifies a channel-group mapping(0–23) under the designated T1.

•

• range —List of timeslots under the channel-group. Timeslots assigned to this T1 can be 1–24 or a combination of subranges within 1– 24. You can indicate a range using a hyphen, commas, or a combination of both.

One timeslot equals one DS0.

speed 56 or 64 — Specifies the speed of a timeslot as either 56 or 64 kbps. The default speed of 64 kbps is not mentioned in the config.

Router(config-controller)# t1 t1-number framing

{ esf | sf [ hdlc-idle { 0x7e | 0xff }] [ mode { j1 }]}

(Optional) Specifies the T1 framing type using the framing command.

• sf —Specifies Super Frame as the T1 frame type.

Note If you select sf framing, you should consider disabling yellow alarm detection because the yellow alarm can be incorrectly detected with sf framing.

Step 5

Step 6

Router(config-controller)# clock source { internal | t1 line } channel-number

•

• esf —Specifies Extended Super Frame as the

T1 frame type. This is the default.

hdlc-idle — The hdlc-idle option allows you to set the idle pattern for the T1 interface to either 0x7e (the default) or 0xff .

(Optional) Specifies the T1 clock source.

• internal —Specifies that the internal clock source is used. This is the default.

• line —Specifies that the network clock source is used.

Configure the serial interfaces.

Note After a T1 channel is configured, it appears to the Cisco IOS software as a serial interface; therefore, all the configuration commands for a serial interface are available. However, not all commands are applicable to the T1 interface. All the encapsulation formats, such as PPP,

HDLC, and Frame Relay are applicable to the configured T1. Encapsulation can be set via the serial interface configuration commands.

For detailed interface configuration information, see the Cisco IOS Interface Configuration Guide,

Release 12.0

.

9-4


Release 12.0(33)S, OL-8832-01, Rev. C9



Verifying T3 Controller Configuration

Use the show controllers command to verify the controller configuration:

Router# show controllers t3

T3 3/1/0 is administratively down.


T3 3/1/2 is up. Hardware is 4 ports CT3 SPA

ATLAS FPGA version: 0, FREEDM336 version: 0

TEMUX84(1) version: 0, TEMUX84(1) version: 0

SUBRATE FPGA version: 0

Applique type is Channelized T3

No alarms detected.

Framing is M23, Line Code is B3ZS, Clock Source is Internal

Equipment customer loopback

Data in current interval (746 seconds elapsed):

0 Line Code Violations, 0 P-bit Coding Violation

0 C-bit Coding Violation, 0 P-bit Err Secs

0 P-bit Severely Err Secs, 0 Severely Err Framing Secs

0 Unavailable Secs, 0 Line Errored Secs

0 C-bit Errored Secs, 0 C-bit Severely Errored Secs

0 Severely Errored Line Secs

0 Far-End Errored Secs, 0 Far-End Severely Errored Secs

0 CP-bit Far-end Unavailable Secs

0 Near-end path failures, 0 Far-end path failures

0 Far-end code violations, 0 FERF Defect Secs

0 AIS Defect Secs, 0 LOS Defect Secs

T1 1 is up

timeslots: 1-24

FDL per AT&T 54016 spec.

No alarms detected.

Framing is ESF, Clock Source is Internal


0 Line Code Violations, 0 Path Code Violations

0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins

0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs

0 Unavail Secs, 0 Stuffed Secs

0 Near-end path failures, 0 Far-end path failures, 0 SEF/AIS Secs

Total Data (last 2 15 minute intervals):

0 Line Code Violations,0 Path Code Violations,

0 Slip Secs, 0 Fr Loss Secs, 0 Line Err Secs, 0 Degraded Mins,




T1 2

Not configured.

.

.

T1 3

Not configured.

.





Applique type is Subrate T3

No alarms detected.

MDL transmission is disabled

FEAC code received: No code is being received

Release 12.0(33)S, OL-8832-01, Rev. C9


9-5



Framing is C-BIT Parity, Line Code is B3ZS, Clock Source is Line














Verifying Interface Configuration

Use the show interface serial command to verify the interface configuration. The following example shows the ouput for the serial interface for an un-channelized T3:

Router# show interface serial3/0/0

Serial3/0/0 is down, line protocol is down

Hardware is Channelized/ClearChannel CT3 SPA

MTU 4470 bytes, BW 44210 Kbit, DLY 200 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation HDLC, crc 16, loopback not set




Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0


Output queue: 0/40 (size/max)






0 parity



0 output errors, 0 applique, 2 interface resets


1 carrier transitions alarm present

DSU mode 0, bandwidth 44210 Kbit, scramble 0, VC 0

The following example shows the ouput for a serial interface for the first T1 on a channelized T3:

Router# show interface serial3/0/1/1:0

Serial3/0/1/1:0 is administratively down, line protocol is down
















9-6 Release 12.0(33)S, OL-8832-01, Rev. C9










Specifying the Interface Address on a SPA

SPA interface ports begin numbering with “0” from left to right. Single-port SPAs use only the port number 0. To configure or monitor SPA interfaces, you need to specify the physical location of the SIP,

SPA, and interface in the CLI. The interface address format is slot / subslot / port , where:

•

• slot —Specifies the chassis slot number in the Cisco 12000 series router where the SIP is installed. subslot —Specifies the secondary slot of the SIP where the SPA is installed.

• port —Specifies the number of the individual interface port on a SPA.

The following example shows how to specify the first interface (0) on a SPA installed in the first subslot of a SIP (0) installed in chassis slot 3:

Router(config)# interface serial 3/0/0

This command shows a serial SPA as a representative example, however the same slot / subslot / port format is similarly used for other SPAs (such as ATM and POS) and other non-channelized SPAs.

For the 4-Port Channelized T3 SPA, the interface address format is slot/subslot/port/t1-number : channel-group , where:

•

• t1-number —Specifies the logical T1 number in channelized mode.

channel-group —Specifies the logical channel group assigned to the timeslots within the T1 link.

Release 12.0(33)S, OL-8832-01, Rev. C9


9-7



Optional Configurations

There are several standard, but optional configurations that might be necessary to complete the configuration of your serial SPA.

Note For additional command output details, see Chapter 19, “SIP and SPA Command Reference” .

•

•

•

•

•

•

•

Configuring the Data Service Unit Mode, page 9-9

Configuring Maintenance Data Link, page 9-11

Configuring Encapsulation, page 9-13

Configuring T3 Framing, page 9-14

Configuring FDL, page 9-15

Configuring Scramble, page 9-16

Configuring Fragmentation Counter Support for Frame Relay, page 9-17 x

9-8


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring the Data Service Unit Mode

Configure the SPA to connect with customer premise Data Service Units (DSUs) by setting the DSU mode. Subrating a T3 or E3 interface reduces the peak access rate by limiting the data transfer rate. To configure the Data Service Unit (DSU) mode, use the following commands.

Step 1

Step 2

Step 3

Step 4

Command


Router(config)# interface serial slot/subslot/port

Router(config-if)#

{ adtran kentrox |

| cisco | dsu mode

digital-link

larscom | verilink }

|

Purpose



• slot/subslot/port— Specifies the location of the controller.

See: Specifying the Interface Address on a SPA, page 9-7

Specifies the interoperability mode used by the T3 controller.

• digital-link —Connects a T3 controller to another T3 controller or to a Digital Link DSU. Bandwidth range is from

300 to 44210 kbps. This is the default.

•

Note kentrox —Connects a T3 controller to a Kentrox DSU.

Bandwidth range is from 1500 to 35000, or 44210 kbps.

If the bandwidth is set between 35000–44210 kbps, an error message is displayed.

Router(config-if)# bandwidth kbps dsu

•

•

• larscom —Connects a T3 controller to a Larscom DSU.

Bandwidth range is from 3100 to 44210 kbps.

cisco —Connects a T3 controller to a Cisco DSU.

adtran —Connects a T3 controller to an Adtran T3SU 300.


• verilink —Connects a T3 controller to a Verilink HDM 2182.


Specifies the maximum allowable bandwidth.

• kbps —Bandwidth range is from 1 to 44210 kbps.

Verifying DSU Mode

Use the show controllers serial command to display the DSU mode of the controller: router# show controllers serial

Serial3/1/0 -

Framing is c-bit, Clock Source is Internal

Bandwidth limit is 44210, DSU mode 0 , Cable length is 10

rx FEBE since last clear counter 0, since reset 0



0 C-bit Coding Violation

0 P-bit Err Secs, 0 P-bit Sev Err Secs

0 Sev Err Framing Secs, 0 Unavailable Secs

0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Sev Err Secs







Release 12.0(33)S, OL-8832-01, Rev. C9 9-9



Transmitter is sending AIS.

.

..


9-10


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring Maintenance Data Link

MDL messages are used to communicate identification information between local and remote ports. The type of information included in MDL messages includes the equipment identification code (EIC), location identification code (LIC), frame identification code (FIC), unit, Path Facility Identification

(PFI), port number, and Generator Identification numbers. To configure Maintenance Data Link (MDL), use the following commands:

Command


Purpose



Router(config-controller)# mdl [ string { eic | fic | generator | lic | pfi | port | unit } string }] |

[ transmit { idle-signal | path | test-signal }]

•


• slot/subslot/port— Specifies the location of the interface.

See: Specifying the Interface

Address on a SPA, page 9-7

Configures the MDL message.

string eic —Specifies the Equipment

Identification Code; can be up to 10 characters.

• string fic —Specifies the Frame Identification

Code; can be up to 10 characters.

•

•

•

• string generator —Specifies the Generator number string sent in the MDL Test Signal message; can be up to 38 characters. string lic — Specifies the Location

Identification Code; can be up to 11 characters. string pfi —Specifies the Path Facility

Identification Code sent in the MDL Path message; can be up to 38 characters. string port —Specifies the Port number string sent in the MDL Idle Signal message; can be up to 38 characters.

•

•

•

• string unit —Specifies the Unit Identification


transmit idle-signal —Enable MDL

Idle-Signal message transmission transmit path —Enable MDL Path message transmission.

transmit test-signal —Enable MDL

Test-Signal message transmission.

Release 12.0(33)S, OL-8832-01, Rev. C9


9-11



Verifying MDL

Use the show controller command to display the MDL settings:

Router# show controller t3 3/0/0

T3 3/0/0 is down. Hardware is 2 ports CT3 SPA





Receiver has loss of signal.

MDL transmission is enabled

EIC: new, LIC: US, FIC: 23, UNIT: myunit

Path FI: test pfi

Idle Signal PORT_NO: New-port

Test Signal GEN_NO: test-message
















9-12


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring Encapsulation

When traffic crosses a WAN link, the connection needs a Layer 2 protocol to encapsulate traffic. To set the encapsulation method, use the following commands:

Command


Channelized:

Router(config)# interface serial slot/subslot/port/t1-number:channel-group

Un-channelized:


Router(config-if)# encapsulation { hdlc | ppp | frame-relay }

Purpose


Selects the interface to configure and enters interface configuration mode.

• Channelized:

• slot/subslot/port/t1-number:channel-group—

Specifies the location of the interface.

See:


Un-channelized: slot/subslot/port— Specifies the location of the interface.



Set the encapsulation method on the interface.

• hdlc —High-Level Data Link Control (HDLC) protocol for serial interface. This is the default.

•

• ppp —Point-to-Point Protocol (PPP) (for serial interface).

frame-relay —Frame Relay (for serial interface).

Verifying Encapsulation

Use the show interface serial command to display the encapsulation method:






Encapsulation HDLC , crc 16, loopback not set












0 parity




Release 12.0(33)S, OL-8832-01, Rev. C9


9-13






Configuring T3 Framing

To set the T3 framing type, use the following commands:

Command


Purpose


Router(config)# interface serial slot/subslot/port Selects the interface to configure and enters interface configuration mode.


See: “Specifying the Interface


Router(config-if)# framing { auto-detect | c-bit | m23 }

Specifies the framing type in unchannelized mode.

• auto-detect —Specifies auto-detect framing.

• c-bit —Specifies C-bit parity framing. This is the default.

• m23 —Specifies DS3 Framing M23.

Verifying Framing

Use the show controller command to display the framing type:








Framing is M13 , Line Code is B3ZS, Clock Source is Line














9-14


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring FDL

Facility Data Link (FDL) is a far-end performance reporting tool. In ansi mode, you can enable 1-second transmissions of performance reports on both ends of the T1 connection. To configure FDL, use the following commands:

Command


Purpose


Router(config)# controller t3 slot/subslot/port Selects the controller to configure and enters controller configuration mode.




Router(config-controller)# t1 number fdl { ansi } (Optional) Enables FDL.

•

• number —Specifies the T1 channel number.

ansi —Specifies the FDL bit per the ANSI

T1.403 specification.

Verifying FDL

Use the show controller command to display the FDL setting:

Router# show controller t3 3/0/1/1





















T1 1 is down

timeslots: 2-14

FDL per ANSI T1.403 and AT&T 54016 spec .

Configured for FDL remotely line looped (bell)

Transmitter is sending LOF Indication.

Receiver is getting AIS.

Framing is ESF, Clock Source is Line

BERT running on timeslots 2,3,4,5,6,7,8,9,10,11,12,13,14,

BERT test result (running)

Test Pattern : All 1's, Status : Not Sync, Sync Detected : 0

Interval : 2 minute(s), Time Remain : 2 minute(s)

Bit Errors (since BERT started): 0 bits,


Release 12.0(33)S, OL-8832-01, Rev. C9 9-15



Bits Received (since BERT started): 0 Kbits

Bit Errors (since last sync): 0 bits

Bits Received (since last sync): 0 Kbits







Configuring Scramble

T3 scrambling is used to assist clock recovery on the receiving end. Scrambling is designed to randomize the pattern of 1s and 0s carried in the physical layer frame. Randomizing the digital bits can prevent continuous, nonvariable bit patterns—in other words, long strings of all 1s or all 0s. Several physical layer protocols rely on transitions between 1s and 0s to maintain clocking.

Scrambling can prevent some bit patterns from being mistakenly interpreted as alarms by switches placed between the Data Service Units (DSUs).

To configure scrambling, use the following commands:

Command


Purpose



Router(config-if)# scramble




Enables scrambling. Scrambling is disabled by default.

Verifying Scrambling

Use the show interface serial command to display the scramble setting:


















0 parity



9-16


Release 12.0(33)S, OL-8832-01, Rev. C9






DSU mode 0, bandwidth 44210 Kbit, scramble 1 , VC 0

Configuring Fragmentation Counter Support for Frame Relay

By default, the fragment size considered for the far-end router in the calculation of incoming fragmented packets will be symmetric with the SPA fragment size configuration. The fragmentation method used to evaluate incoming packets will not consider the fragmentation encapsulation overhead. This behavior allows the fragment counters to have the right settings to work by default with non-SPA platforms on the far-end, for example, Cisco 7200 eries routers. If this is not the desired behavior, use the far-end option to change the default setting.

For SPA hardware, the fragment size is defined as the sum of the fragment encap overhead size and the fragment payload size. But for non-SPA platforms like Cisco 7200 series routers, the fragment size is equivalent to the fragment payload size as the fragmentation encapsulation overhead is not considered during the fragmentation of a packet. In order to get accurate calculation of incoming fragmented packets, the correct fragmentation method and fragment size can be indicated with the with-encap and without-encap options for the far end router.

Input fragment sequencing error events are triggered by SPA hardware when it detects errors in the link.

Their occurrence will affect the accuracy of the fragmentation counters. Please inspect the output of show interface command for errors.

To enable fragmentation counter support of Frame Relay frames for a specific DLCI, use the following commands:

Step 1

Step 2

Step 3

Step 4

Step 5

Command

Router(config)# interface serial point-to-point slot/subslot/port


255.255.255.0

Purpose

Specifies a serial interface.

Specifies the IP address.

Router(config-if)# frame-relay interface-dlci 400

Router(config-fr-dlci)# class map-name

Enters dlci subinterface configuration mode.

Specifies Frame Relay map class name and enters map class configuration mode.

Router(config-fr-dlci)# fragment-counter Enables fragmentation counter support.

Note The attached map-class may need to have the frame-relay fragment frag-size command enabled as a requirement to use the fragment-counter command under DLCI configuration.

Verifying Framentation Counter Support

The following example shows the output of the show frame-relay fragment command on a subinterface:

Router# show frame-relay fragment interface serial 4/3/0/1:0.1 300

fragment size : 128 fragment type : end-to-end

Release 12.0(33)S, OL-8832-01, Rev. C9


9-17



*in fragmented pkts : 10527 out fragmented pkts : 10532

in un-fragmented pkts : 0 out un-fragmented pkts : 0

in assembled pkts : 1772 out pre-fragmented pkts : 1770 input fragment sequencing error events : 0

* "in fragmented pkts" is being calculated based on a fragment size of

256 bytes that does not include the encap overhead

The following example shows input fragment sequencing error events. Input fragment sequencing error events are triggered by SPA hardware when it detects errors in the link. Their occurrence will affect the accuracy of the counters. Inspect the output of show interface command for errors.

Router# show frame-relay fragment interface serial 4/3/0/1:0.1 300 fragment size : 128 fragment type : end-to-end



in assembled pkts : 1772 out pre-fragmented pkts : 1770

input fragment sequencing error events : 3





Command


Purpose






Besides using the show running-configuration command to display your Cisco 12000 Series router configuration settings, you can use the show interfaces serial and the show controllers serial commands to get detailed information on a per-port basis for your 2-Port and 4-Port Clear Channel

T3/E3 SPA.


To find detailed interface information on a per-port basis for the 2-Port and 4-Port Channelized T3 SPA, use the show interfaces serial command. For a description of the command output, see Chapter 19, “SIP and SPA Command Reference.”

The following example provides sample output for the serial interface on an un-channelized T3:

9-18


Release 12.0(33)S, OL-8832-01, Rev. C9




















0 parity







The following example provides sample output for the serial interface on a channelized T3:
























To find detailed status and statistical information on a per-port basis for the 2-Port and 4-Port Clear

Channel T3/E3 SPA, use the show controllers serial command. For a description of the command output, see Chapter 19, “SIP and SPA Command Reference.”

The following example provides sample controller statistics for the third port on the SPA located in the first subslot of the SIP-200 that is installed in slot 5 of a Cisco 12008 router: show controller serial 5/0/2

Serial5/0/2 -

Framing is c-bit, Clock Source is Line

Bandwidth limit is 44210, DSU mode 0, Cable length is 10



Release 12.0(33)S, OL-8832-01, Rev. C9


9-19








Data in Interval 1:






Data in Interval 2:






Data in Interval 3:






Data in Interval 4:






.

.

.


0 Line Code Violations, 0 P-bit Coding Violation,

0 C-bit Coding Violation,

0 P-bit Err Secs, 0 P-bit Sev Err Secs,

0 Sev Err Framing Secs, 0 Unavailable Secs,




40434 Sev Err Line Secs, 0 Far-End Err Secs, 0 Far-End Sev Err Secs

0 P-bit Unavailable Secs, 0 CP-bit Unavailable Secs



No FEAC code is being received




• DSU Configuration Example, page 9-21

•

•

•

MDL Configuration Example, page 9-21

Encapsulation Configuration Example, page 9-21

Framing - Unchannelized Mode Configuration Example, page 9-22

9-20


Release 12.0(33)S, OL-8832-01, Rev. C9



•

•

Facility Data Link Configuration Example, page 9-22

Scrambling Configuration Example, page 9-22

DSU Configuration Example

The following example sets the DSU mode on interface port 0 on slot 4, subslot 1.

! Specify the interface and enter interface configuration mode.

!

Router(config-int)# interface t3 4/1/0

!

!Specifies the interoperability mode used by the T3 interface.

!

Router(config-int)# dsu mode 2

!

!Specifies the maximum allowable bandwidth.

Router(config-int)# dsu bandwidth 23000

MDL Configuration Example

The following example configures the MDL strings on controller port 0 on slot 4, subslot 1.

! Enter controller configuration mode.

!

Router(config)# controller t3 4/1/0

!

! Specify the mdl strings.

!

Router(config-controller)# mdl string eic beic

Router(config-controller)# mdl string lic beic

Router(config-controller)# mdl string fic bfix

Router(config-controller)# mdl string unit bunit

Router(config-controller)# mdl string pfi bpfi

Router(config-controller)# mdl string port bport

Router(config-controller)# mdl string generator bgen

Router(config-controller)# mdl transmit path

Router(config-controller)# mdl transmit idle-signal

Router(config-controller)# mdl transmit test-signal

Encapsulation Configuration Example

The following example configures encapsulation on a channelized T1 interface.

! Specify the interface to configure and enter interface configuration mode.

!

Router(config)# interface serial 4/1/1/1:0

!

! Specify the encapsulation method.

!

Router(config-if)# encapsulation ppp

The following example configures encapsulation and framing on a un-channelized T3 interface.


!

Router(config)# interface serial 4/1/1

!


Release 12.0(33)S, OL-8832-01, Rev. C9 9-21




!


Framing - Unchannelized Mode Configuration Example

The following example configures framing on an un-channelized T3 interface.


!


!

! Specify the framing type.

!

Router(config-if)# framing m13

Facility Data Link Configuration Example

The following example configures FDL on a channelized T1 interface.

! Specify the controller to configure and enter controller configuration mode.

!


!

! Specify the T1 controller and set the FDL bit.

!

Router(config-controller)# t1 1 fdl ansi

Scrambling Configuration Example

The following example configures scrambling on the T3 interface:

! Enter global configuration mode.

!


!


!


!

! Enable scrambling.

!

Router(config-if)# scrambling

9

9-22


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

10

Configuring the 2-Port and 4-Port T3/E3 SPAs

9

This chapter provides information about configuring the 2-Port and 4-Port Channelized T3 Shared Port

Adapters (SPAs) on the Cisco 12000 series routers. It includes the following sections:

•

•







For more information about the commands used in this chapter, see Chapter 19, “SIP and SPA Command

Reference,” in this guide, which documents new and modified commands . Also refer to the related

Cisco IOS Release 12.0 software command reference and master index publications. For more information about accessing these publications, see the Related Documentation section in the Preface .


This section describes how to configure the serial SPAs for the Cisco 12000 series routers and includes information about verifying the configuration.


•

•

•

•





Release 12.0(33)S, OL-8832-01, Rev. C9


10-1

Chapter 9 Configuring the 2-Port and 4-Port T3/E3 SPAs



This section lists the required configuration steps to configure the 2-Port and 4-Port Channelized T3

SPA. Some of the required configuration commands implement default values that might be appropriate for your network.

•

•

•

•

Configuring the T3 Controller, page 9-2

Configuring the Logical T1 Interfaces, page 9-3

Verifying T3 Controller Configuration, page 9-5

Verifying Interface Configuration, page 9-6

Note To better understand the address format used to specify the physical location of the SPA Interface

Processor (SIP), SPA, and interfaces, see the section Specifying the Interface Address on a SPA, page 9-7 .

Configuring the T3 Controller

To configure the T3 controller for the 2-Port and 4-Port Channelized T3 SPA, complete these steps:

Step 1

Step 2

Command



Step 3 Router(config-controller)# [ no ] channelized

Purpose






(Optional) Specifies the channelization mode.

• channelized —In channelized mode, the T3 link can be channelized into 28 T1s, and each

T1 can be further channelized into 24 DS0s.

This is the default.

• no channelized —In the unchannelized mode the T3 link provides a single high-speed data channel of 44210 kbps.

9-2


Release 12.0(33)S, OL-8832-01, Rev. C9



Step 4

Step 5

Step 6

Command Purpose

Router(config-controller)# framing { auto-detect

| c-bit | m23 }

(Optional) Specifies the framing type in subrate T3 mode.

•

• auto-detect —Detects the framing type at the device at the end of the line and switches to that framing type. If both devices are set to auto-detect, c-bit framing is used.

c-bit —Specifies C-bit parity framing. This is the default.

•

Note m23 —Specifies M23 framing.

To set the framing type for an un-channelized T3, see: “Configuring T3

Framing” section on page 9-14 .

(Optional) Specifies the clock source.


{ internal | line }

•

• internal —Specifies that the internal clock source is used. Default for channelized mode.

line —Specifies that the network clock source is used. Default for un-channelized mode.

Router(config-controller)# cablelength { 0 450 } (Optional) Specifies the cable length. The default is 50 ft.

• 0-450 —Cable length in feet.

Configuring the Logical T1 Interfaces

If channelized mode is configured for the T3 controller, use the following procedure to configure the logical T1 interfaces.

Step 1

Step 2

Command



Purpose






Release 12.0(33)S, OL-8832-01, Rev. C9


9-3



Step 3

Step 4

Command

Router(config-controller)# t1 t1-number channel-group channel-number timeslots range

[ speed { 56 | 64 }]

Purpose

Specifies the T1 channel and timeslots to be mapped to each channel.

•

• t1-number —T1 number from 1–28.

channel-number —Specifies a channel-group mapping(0–23) under the designated T1.

•

• range —List of timeslots under the channel-group. Timeslots assigned to this T1 can be 1–24 or a combination of subranges within 1– 24. You can indicate a range using a hyphen, commas, or a combination of both.

One timeslot equals one DS0.

speed 56 or 64 — Specifies the speed of a timeslot as either 56 or 64 kbps. The default speed of 64 kbps is not mentioned in the config.

Router(config-controller)# t1 t1-number framing

{ esf | sf [ hdlc-idle { 0x7e | 0xff }] [ mode { j1 }]}

(Optional) Specifies the T1 framing type using the framing command.


Note If you select sf framing, you should consider disabling yellow alarm detection because the yellow alarm can be incorrectly detected with sf framing.

Step 5

Step 6

Router(config-controller)# clock source { internal | t1 line } channel-number

•

• esf —Specifies Extended Super Frame as the

T1 frame type. This is the default.

hdlc-idle — The hdlc-idle option allows you to set the idle pattern for the T1 interface to either 0x7e (the default) or 0xff .

(Optional) Specifies the T1 clock source.

• internal —Specifies that the internal clock source is used. This is the default.


Configure the serial interfaces.

Note After a T1 channel is configured, it appears to the Cisco IOS software as a serial interface; therefore, all the configuration commands for a serial interface are available. However, not all commands are applicable to the T1 interface. All the encapsulation formats, such as PPP,

HDLC, and Frame Relay are applicable to the configured T1. Encapsulation can be set via the serial interface configuration commands.

For detailed interface configuration information, see the Cisco IOS Interface Configuration Guide,

Release 12.0

.

9-4


Release 12.0(33)S, OL-8832-01, Rev. C9



Verifying T3 Controller Configuration










No alarms detected.















T1 1 is up

timeslots: 1-24

FDL per AT&T 54016 spec.

No alarms detected.

Framing is ESF, Clock Source is Internal








0 Line Code Violations,0 Path Code Violations,





T1 2

Not configured.

.

.

T1 3

Not configured.

.






No alarms detected.



Release 12.0(33)S, OL-8832-01, Rev. C9


9-5


















Use the show interface serial command to verify the interface configuration. The following example shows the ouput for the serial interface for an un-channelized T3:


















0 parity







The following example shows the ouput for a serial interface for the first T1 on a channelized T3:


Serial3/0/1/1:0 is administratively down, line protocol is down
















9-6 Release 12.0(33)S, OL-8832-01, Rev. C9













•






For the 4-Port Channelized T3 SPA, the interface address format is slot/subslot/port/t1-number : channel-group , where:

•

• t1-number —Specifies the logical T1 number in channelized mode.

channel-group —Specifies the logical channel group assigned to the timeslots within the T1 link.

Release 12.0(33)S, OL-8832-01, Rev. C9


9-7




There are several standard, but optional configurations that might be necessary to complete the configuration of your serial SPA.

Note For additional command output details, see Chapter 19, “SIP and SPA Command Reference” .

•

•

•

•

•

•

•

Configuring the Data Service Unit Mode, page 9-9

Configuring Maintenance Data Link, page 9-11


Configuring T3 Framing, page 9-14


Configuring Scramble, page 9-16

Configuring Fragmentation Counter Support for Frame Relay, page 9-17 x

9-8


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring the Data Service Unit Mode

Configure the SPA to connect with customer premise Data Service Units (DSUs) by setting the DSU mode. Subrating a T3 or E3 interface reduces the peak access rate by limiting the data transfer rate. To configure the Data Service Unit (DSU) mode, use the following commands.

Step 1

Step 2

Step 3

Step 4

Command



Router(config-if)#

{ adtran kentrox |

| cisco | dsu mode

digital-link

larscom | verilink }

|

Purpose




See: Specifying the Interface Address on a SPA, page 9-7

Specifies the interoperability mode used by the T3 controller.

• digital-link —Connects a T3 controller to another T3 controller or to a Digital Link DSU. Bandwidth range is from

300 to 44210 kbps. This is the default.

•

Note kentrox —Connects a T3 controller to a Kentrox DSU.

Bandwidth range is from 1500 to 35000, or 44210 kbps.

If the bandwidth is set between 35000–44210 kbps, an error message is displayed.

Router(config-if)# bandwidth kbps dsu

•

•

• larscom —Connects a T3 controller to a Larscom DSU.


cisco —Connects a T3 controller to a Cisco DSU.

adtran —Connects a T3 controller to an Adtran T3SU 300.


• verilink —Connects a T3 controller to a Verilink HDM 2182.


Specifies the maximum allowable bandwidth.

• kbps —Bandwidth range is from 1 to 44210 kbps.

Verifying DSU Mode

Use the show controllers serial command to display the DSU mode of the controller: router# show controllers serial

Serial3/1/0 -


Bandwidth limit is 44210, DSU mode 0 , Cable length is 10














Release 12.0(33)S, OL-8832-01, Rev. C9 9-9




.

..


9-10


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring Maintenance Data Link

MDL messages are used to communicate identification information between local and remote ports. The type of information included in MDL messages includes the equipment identification code (EIC), location identification code (LIC), frame identification code (FIC), unit, Path Facility Identification

(PFI), port number, and Generator Identification numbers. To configure Maintenance Data Link (MDL), use the following commands:

Command


Purpose



Router(config-controller)# mdl [ string { eic | fic | generator | lic | pfi | port | unit } string }] |

[ transmit { idle-signal | path | test-signal }]

•





Configures the MDL message.

string eic —Specifies the Equipment

Identification Code; can be up to 10 characters.

• string fic —Specifies the Frame Identification


•

•

•

• string generator —Specifies the Generator number string sent in the MDL Test Signal message; can be up to 38 characters. string lic — Specifies the Location

Identification Code; can be up to 11 characters. string pfi —Specifies the Path Facility

Identification Code sent in the MDL Path message; can be up to 38 characters. string port —Specifies the Port number string sent in the MDL Idle Signal message; can be up to 38 characters.

•

•

•

• string unit —Specifies the Unit Identification


transmit idle-signal —Enable MDL

Idle-Signal message transmission transmit path —Enable MDL Path message transmission.

transmit test-signal —Enable MDL

Test-Signal message transmission.

Release 12.0(33)S, OL-8832-01, Rev. C9


9-11



Verifying MDL

Use the show controller command to display the MDL settings:








MDL transmission is enabled

EIC: new, LIC: US, FIC: 23, UNIT: myunit

Path FI: test pfi

Idle Signal PORT_NO: New-port

Test Signal GEN_NO: test-message
















9-12


Release 12.0(33)S, OL-8832-01, Rev. C9





Command


Channelized:

Router(config)# interface serial slot/subslot/port/t1-number:channel-group

Un-channelized:


Router(config-if)# encapsulation { hdlc | ppp | frame-relay }

Purpose



• Channelized:

• slot/subslot/port/t1-number:channel-group—

Specifies the location of the interface.

See:


Un-channelized: slot/subslot/port— Specifies the location of the interface.




• hdlc —High-Level Data Link Control (HDLC) protocol for serial interface. This is the default.

•

• ppp —Point-to-Point Protocol (PPP) (for serial interface).



Use the show interface serial command to display the encapsulation method:


















0 parity




Release 12.0(33)S, OL-8832-01, Rev. C9


9-13






Configuring T3 Framing

To set the T3 framing type, use the following commands:

Command


Purpose






Router(config-if)# framing { auto-detect | c-bit | m23 }

Specifies the framing type in unchannelized mode.

• auto-detect —Specifies auto-detect framing.

• c-bit —Specifies C-bit parity framing. This is the default.

• m23 —Specifies DS3 Framing M23.

Verifying Framing

Use the show controller command to display the framing type:








Framing is M13 , Line Code is B3ZS, Clock Source is Line














9-14


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring FDL

Facility Data Link (FDL) is a far-end performance reporting tool. In ansi mode, you can enable 1-second transmissions of performance reports on both ends of the T1 connection. To configure FDL, use the following commands:

Command


Purpose


Router(config)# controller t3 slot/subslot/port Selects the controller to configure and enters controller configuration mode.




Router(config-controller)# t1 number fdl { ansi } (Optional) Enables FDL.

•

• number —Specifies the T1 channel number.

ansi —Specifies the FDL bit per the ANSI

T1.403 specification.

Verifying FDL

Use the show controller command to display the FDL setting:

Router# show controller t3 3/0/1/1





















T1 1 is down

timeslots: 2-14

FDL per ANSI T1.403 and AT&T 54016 spec .

Configured for FDL remotely line looped (bell)

Transmitter is sending LOF Indication.

Receiver is getting AIS.

Framing is ESF, Clock Source is Line

BERT running on timeslots 2,3,4,5,6,7,8,9,10,11,12,13,14,

BERT test result (running)

Test Pattern : All 1's, Status : Not Sync, Sync Detected : 0

Interval : 2 minute(s), Time Remain : 2 minute(s)

Bit Errors (since BERT started): 0 bits,


Release 12.0(33)S, OL-8832-01, Rev. C9 9-15



Bits Received (since BERT started): 0 Kbits

Bit Errors (since last sync): 0 bits

Bits Received (since last sync): 0 Kbits







Configuring Scramble

T3 scrambling is used to assist clock recovery on the receiving end. Scrambling is designed to randomize the pattern of 1s and 0s carried in the physical layer frame. Randomizing the digital bits can prevent continuous, nonvariable bit patterns—in other words, long strings of all 1s or all 0s. Several physical layer protocols rely on transitions between 1s and 0s to maintain clocking.

Scrambling can prevent some bit patterns from being mistakenly interpreted as alarms by switches placed between the Data Service Units (DSUs).

To configure scrambling, use the following commands:

Command


Purpose



Router(config-if)# scramble




Enables scrambling. Scrambling is disabled by default.

Verifying Scrambling

Use the show interface serial command to display the scramble setting:


















0 parity



9-16


Release 12.0(33)S, OL-8832-01, Rev. C9






DSU mode 0, bandwidth 44210 Kbit, scramble 1 , VC 0

Configuring Fragmentation Counter Support for Frame Relay

By default, the fragment size considered for the far-end router in the calculation of incoming fragmented packets will be symmetric with the SPA fragment size configuration. The fragmentation method used to evaluate incoming packets will not consider the fragmentation encapsulation overhead. This behavior allows the fragment counters to have the right settings to work by default with non-SPA platforms on the far-end, for example, Cisco 7200 eries routers. If this is not the desired behavior, use the far-end option to change the default setting.

For SPA hardware, the fragment size is defined as the sum of the fragment encap overhead size and the fragment payload size. But for non-SPA platforms like Cisco 7200 series routers, the fragment size is equivalent to the fragment payload size as the fragmentation encapsulation overhead is not considered during the fragmentation of a packet. In order to get accurate calculation of incoming fragmented packets, the correct fragmentation method and fragment size can be indicated with the with-encap and without-encap options for the far end router.

Input fragment sequencing error events are triggered by SPA hardware when it detects errors in the link.

Their occurrence will affect the accuracy of the fragmentation counters. Please inspect the output of show interface command for errors.

To enable fragmentation counter support of Frame Relay frames for a specific DLCI, use the following commands:

Step 1

Step 2

Step 3

Step 4

Step 5

Command

Router(config)# interface serial point-to-point slot/subslot/port


255.255.255.0

Purpose

Specifies a serial interface.

Specifies the IP address.

Router(config-if)# frame-relay interface-dlci 400

Router(config-fr-dlci)# class map-name

Enters dlci subinterface configuration mode.

Specifies Frame Relay map class name and enters map class configuration mode.

Router(config-fr-dlci)# fragment-counter Enables fragmentation counter support.

Note The attached map-class may need to have the frame-relay fragment frag-size command enabled as a requirement to use the fragment-counter command under DLCI configuration.

Verifying Framentation Counter Support

The following example shows the output of the show frame-relay fragment command on a subinterface:

Router# show frame-relay fragment interface serial 4/3/0/1:0.1 300

fragment size : 128 fragment type : end-to-end

Release 12.0(33)S, OL-8832-01, Rev. C9


9-17





in assembled pkts : 1772 out pre-fragmented pkts : 1770 input fragment sequencing error events : 0



The following example shows input fragment sequencing error events. Input fragment sequencing error events are triggered by SPA hardware when it detects errors in the link. Their occurrence will affect the accuracy of the counters. Inspect the output of show interface command for errors.

Router# show frame-relay fragment interface serial 4/3/0/1:0.1 300 fragment size : 128 fragment type : end-to-end



in assembled pkts : 1772 out pre-fragmented pkts : 1770

input fragment sequencing error events : 3





Command


Purpose






Besides using the show running-configuration command to display your Cisco 12000 Series router configuration settings, you can use the show interfaces serial and the show controllers serial commands to get detailed information on a per-port basis for your 2-Port and 4-Port Clear Channel

T3/E3 SPA.


To find detailed interface information on a per-port basis for the 2-Port and 4-Port Channelized T3 SPA, use the show interfaces serial command. For a description of the command output, see Chapter 19, “SIP and SPA Command Reference.”

The following example provides sample output for the serial interface on an un-channelized T3:

9-18


Release 12.0(33)S, OL-8832-01, Rev. C9




















0 parity







The following example provides sample output for the serial interface on a channelized T3:
























To find detailed status and statistical information on a per-port basis for the 2-Port and 4-Port Clear

Channel T3/E3 SPA, use the show controllers serial command. For a description of the command output, see Chapter 19, “SIP and SPA Command Reference.”

The following example provides sample controller statistics for the third port on the SPA located in the first subslot of the SIP-200 that is installed in slot 5 of a Cisco 12008 router: show controller serial 5/0/2

Serial5/0/2 -





Release 12.0(33)S, OL-8832-01, Rev. C9


9-19








Data in Interval 1:






Data in Interval 2:






Data in Interval 3:






Data in Interval 4:






.

.

.









40434 Sev Err Line Secs, 0 Far-End Err Secs, 0 Far-End Sev Err Secs

0 P-bit Unavailable Secs, 0 CP-bit Unavailable Secs



No FEAC code is being received




• DSU Configuration Example, page 9-21

•

•

•

MDL Configuration Example, page 9-21


Framing - Unchannelized Mode Configuration Example, page 9-22

9-20


Release 12.0(33)S, OL-8832-01, Rev. C9



•

•


Scrambling Configuration Example, page 9-22

DSU Configuration Example

The following example sets the DSU mode on interface port 0 on slot 4, subslot 1.

! Specify the interface and enter interface configuration mode.

!

Router(config-int)# interface t3 4/1/0

!

!Specifies the interoperability mode used by the T3 interface.

!

Router(config-int)# dsu mode 2

!

!Specifies the maximum allowable bandwidth.

Router(config-int)# dsu bandwidth 23000

MDL Configuration Example

The following example configures the MDL strings on controller port 0 on slot 4, subslot 1.

! Enter controller configuration mode.

!


!

! Specify the mdl strings.

!

Router(config-controller)# mdl string eic beic

Router(config-controller)# mdl string lic beic

Router(config-controller)# mdl string fic bfix

Router(config-controller)# mdl string unit bunit

Router(config-controller)# mdl string pfi bpfi

Router(config-controller)# mdl string port bport

Router(config-controller)# mdl string generator bgen

Router(config-controller)# mdl transmit path

Router(config-controller)# mdl transmit idle-signal

Router(config-controller)# mdl transmit test-signal


The following example configures encapsulation on a channelized T1 interface.


!

Router(config)# interface serial 4/1/1/1:0

!


!


The following example configures encapsulation and framing on a un-channelized T3 interface.


!


!


Release 12.0(33)S, OL-8832-01, Rev. C9 9-21




!


Framing - Unchannelized Mode Configuration Example

The following example configures framing on an un-channelized T3 interface.


!


!

! Specify the framing type.

!

Router(config-if)# framing m13


The following example configures FDL on a channelized T1 interface.

! Specify the controller to configure and enter controller configuration mode.

!


!

! Specify the T1 controller and set the FDL bit.

!

Router(config-controller)# t1 1 fdl ansi

Scrambling Configuration Example

The following example configures scrambling on the T3 interface:

! Enter global configuration mode.

!


!


!


!

! Enable scrambling.

!

Router(config-if)# scrambling

9-22


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

11

Configuring the 8-Port Channelized T1/E1 SPA

This chapter provides information about configuring the 8-Port Clear Channel T1/E1 SPA on

Cisco 12000 Series Routers. It includes the following sections:

•

•



•

Configuration Examples, page 11-18




Also refer to the related Cisco IOS Release 12.0 software command reference and master index publications. For more information about accessing these publications, see the “Related Documentation” section in the Preface.


This section describes how to configure the 8-Port Clear Channel T1/E1 SPA for the Cisco 12000 Series

Routers and includes information about verifying the configuration.


•

•

•

•






This section lists the required configuration steps to configure the 8-Port Clear Channel T1/E1 SPA.

Some of the required configuration commands implement default values that might be appropriate for your network. If the default value is correct for your network, then you do not need to configure the command.

•

Setting the Card Type

•

•

Enabling the Interfaces on the Controller

Verifying Controller Configuration

Release 12.0(33)S, OL-8832-01, Rev. C9


11-1

Chapter 11 Configuring the 8-Port Channelized T1/E1 SPA


•

•

Setting the IP Address

Verifying Interface Configuration

Note To better understand the address format used to specify the physical location of the SIP, SPA, and interfaces, see the:

“Specifying the Interface Address on a SPA” section on page 11-6

.

Setting the Card Type

The SPA is not functional until the card type is set. Information about the SPA is not indicated in the output of any show commands until the card type has been set. There is no default card type.

Note Mixing of interface types is not supported. All ports on a SPA must be of the same type.

To set the card type for the 8-Port Clear Channel T1/E1 SPA, complete these steps:

Step 1

Step 2

Step 3

Command


Purpose


Router(config)# card type { e1 | t1 } slot subslot Sets the serial mode for the SPA:

• t1 —Specifies T1 connectivity of 1.536 Mbps.

B8ZS is the default line code for T1.

Router(config)# exit

•

• e1 —Specifies a wide-area digital transmission scheme used predominantly in Europe that carries data at a rate of 1.984 Mbps in framed mode and a 2.048 Mbps in unframed E1 mode.

slot subslot— Specifies the location of the

SPA. See the:



Exits configuration mode and returns to the EXEC command interpreter prompt.

11-2


Release 12.0(33)S, OL-8832-01, Rev. C9



Enabling the Interfaces on the Controller

To create the interfaces for the 8-Port Clear Channel T1/E1 SPA, complete these steps:

Step 1

Step 2

Step 3

Step 4

Command

Router(config)# controller { t1 | e1 } slot/subslot/port

Router(config-controller)#

{ internal | line } clock source

Purpose

Select the controller to configure and enter controller configuration mode.

•

• t1 —Specifies the T1 controller.

e1 —Specifies the E1 controller.


See the:


Sets the clock source.

Note The clock source is set to internal if the opposite end of the connection is set to line and the clock source is set to line if the opposite end of the connection is set to internal.

• internal —Specifies that the internal clock source is used.

• line —Specifies that the network clock source is used. This is the default for T1 and E1.

Router(config-controller)# linecode { ami | b8zs | hdb3 }

Selects the linecode type.

• ami —Specifies Alternate Mark Inversion (AMI) as the linecode type. Valid for T1 and E1 controllers.

For T1 controllers:

Router(config-controller)# framing { sf | esf }

For E1 controllers:

•

Router(config-controller)# framing { crc4 | no-crc4 }

•

•

• b8zs —Specifies binary 8-zero substitution (B8ZS) as the linecode type. Valid for T1 controller only.

This is the default for T1 lines.

hdb3 —Specifies high-density binary 3 (hdb3) as the linecode type. Valid for E1 controller only. This is the default for E1 lines.

Selects the framing type.


esf —Specifies Extended Super Frame as the T1 frame type. This is the default for E1.

crc4 —Specifies CRC4 as the E1 frame type. This is the default for E1.

• no-crc4 —Specifies no CRC4 as the E1 frame type.

Release 12.0(33)S, OL-8832-01, Rev. C9


11-3



Step 5

Step 6

Command

Router(config-controller)# channel-group t1 t1-number { timeslots range | unframed } [ speed { 56 | 64 }]

Purpose

Define the time slots that belong to each T1 or E1 circuit.

• t1 t1-number can be values from 1 to 28. When configuring an E1 data line, channel-group numbers can be values from

0 to 30.

— Channel-group number. When configuring a T1 data line, channel-group numbers

• timeslots range — One or more time slots or ranges of time slots belonging to the channel group. The first time slot is numbered 1. For a T1 controller, the time slot range is from 1 to 24. For an E1 controller, the time slot range is from 1 to 31.

•

• unframed —Unframed mode (G.703) uses all 32 time slots for data. None of the 32 time slots are used for framing signals.

speed —(Optional) Speed of the underlying DS0s.

Note

–

–

56 —

64 —

The default is 64 if speed is not mentioned in the config.


Note Each channel group is presented to the system as a serial interface that can be configured individually.

Note Once a channel group has been created with the channel-group command, the channel group cannot be changed without removing the channel group. To remove a channel group, see the section:

Changing a Channel Group

Configuration, page 11-16 .


Verifying Controller Configuration


Router(config)# show controllers t1

T1 6/0/1 is up.


Cablelength is long gain36 0db

No alarms detected.

alarm-trigger is not set

Framing is ESF, Line Code is B8ZS, Clock Source is Line.




0 Errored Secs, 0 Bursty Err Secs, 0 Severely Err Secs, 0 Unavail Secs

Total Data (last 24 hours)

0 Line Code Violations, 0 Path Code Violations,



11-4 Release 12.0(33)S, OL-8832-01, Rev. C9




Setting the IP Address

To set the IP address for the 8-Port Clear Channel T1/E1 SPA, complete these steps:

Step 1

Step 2

Step 3

Command

Router(config)# interface serial slot/subslot/port : channel-group

Router(config-if)# address mask

Router(config)# ip address exit

Purpose

Selects the interface to configure from global configuration mode.

• slot/subslot/port:channel-group —Specifies the location of

the interface. See the: “Specifying the Interface Address on a

SPA” section on page 11-6

Sets the IP address and subnet mask.

• address —IP address.

• mask —Subnet mask.



Use the show interfaces command to verify the interface configuration:

.

.

Router(config)# show interfaces

.

Serial6/0/1:0 is up, line protocol is up

Hardware is SPA-T1E1



Encapsulation PPP, crc 16, loopback not set


LCP Open, multilink Open
















Timeslot(s) Used:1-24, subrate: 64Kb/s, transmit delay is 0 flags

.

.

Release 12.0(33)S, OL-8832-01, Rev. C9


11-5






•






For the 8-Port Channelized T1/E1 SPA, the interface address format is slot/subslot/port : channel-group , where:

• channel-group —Specifies the logical channel group assigned to the timeslots within the T1 link.


There are several standard, but optional, configurations that might be necessary to complete the configuration of your serial SPA.

Note For additional command output details, see

Chapter 19, “SIP and SPA Command Reference” .

•

•

•

•

•

•

•

•

•

•

•

•

Configuring Framing, page 11-7


Configuring the CRC Size for T1, page 11-9


Configuring Multilink Point-to-Point Protocol (Hardware-based), page 11-11

Configuring MLFR for T1/E1, page 11-13

Invert Data on the T1/E1 Interface, page 11-16

Changing a Channel Group Configuration, page 11-16

FRF.12 Guidelines, page 11-17

LFI Guidelines, page 11-17

HW MLPPP LFI Guidelines, page 11-17

FRF.12 LFI Guidelines, page 11-17

11-6


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring Framing

Framing is used to synchronize data transmission on the line. Framing allows the hardware to determine when each packet starts and ends. To configure framing, use the following commands.

Command


Router(config)# controller {t1 | e1} slot/subslot/port

For T1 controllers:

Router(config-controller)# framing {sf | esf}

For E1 controllers:

Router(config-controller)# framing {crc4 | no-crc4 | unframed}

Purpose


Selects the controller to configure.

• t1 —Specifies the T1 controller.

•

• e1 —Specifies the E1 controller.

slot/subslot/port— Specifies the location of the

controller. See: “Specifying the Interface


Set the framing on the interface.

•

•

•

•

• sf —Specifies Super Frame as the T1 frame type. esf —Specifies extended Super Frame as the

T1 frame type. This is the default. for T1.

crc4 —Specifies CRC4 frame as the E1 frame type. This is the default for E1.

no-crc4 —Specifies no CRC4 frame as the E1 frame type.

unframed —Unframed mode (G.703) uses all

32 time slots for data.

Verifying Framing Configuration

Use the show controllers command to verify the framing configuration:


T1 6/0/0 is down.



Receiver has loss of frame.


Framing is ESF , Line Code is B8ZS, Clock Source is Line.









Release 12.0(33)S, OL-8832-01, Rev. C9


11-7





Command


Router(config)# slot/subslot/port : interface serial channel-group

Router(config-if)# encapsulation encapsulation-type {hdlc | ppp | frame-relay}

Purpose


Selects the interface to configure.

• slot/subslot/port:channel-group— Specifies

the location of the interface. See: “Specifying the Interface Address on a SPA” section on page 11-6


•

•

• hdlc —High-Level Data Link Control (HDLC) protocol for serial interface. This encapsulation method provides the synchronous framing and error detection functions of HDLC without windowing or retransmission. This is the default for synchronous serial interfaces.

ppp —PPP (for serial interface).



Use the show interfaces serial command to verify encapsulation on the interface:

Router# show interfaces serial 6/0/0:0

Serial6/0/0:0 is down, line protocol is down




Encapsulation PPP , crc 32, loopback not set


LCP Closed, multilink Closed

Last input 1w0d, output 1w0d, output hang never



Queueing strategy: weighted fair

Output queue: 0/1000/64/0 (size/max total/threshold/drops)

Conversations 0/0/256 (active/max active/max total)

Reserved Conversations 0/0 (allocated/max allocated)












11-8


Release 12.0(33)S, OL-8832-01, Rev. C9




Configuring the CRC Size for T1

All 8-Port Clear Channel T1/E1 SPA interfaces use a 16-bit cyclic redundancy check (CRC) by default, but also support a 32-bit CRC. CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. The designators 16 and 32 indicate the length (in bits) of the frame check sequence (FCS). A CRC of 32 bits provides more powerful error detection, but adds overhead.

Both the sender and receiver must use the same setting.

CRC-16, the most widely used CRC throughout the United States and Europe, is used extensively with

WANs. CRC-32 is specified by IEEE 802 and as an option by some point-to-point transmission standards. It is often used on Switched Multimegabit Data Service (SMDS) networks and LANs.

To set the length of the cyclic redundancy check (CRC) on a T1 interface, use these commands:

Command



Router(config-if)# crc { 16 | 32 }

Purpose



• slot/subslot/port:channel-group— Specifies the location of the interface. See the:


Selects the CRC size in bits.

•

•

16 —16-bit CRC. This is the default

32 —32-bit CRC.

Verifying the CRC Size

Use the show interfaces serial command to verify the CRC size set on the interface: router# show interfaces serial 6/0/0:0





Encapsulation PPP, crc 32 , loopback not set




Last clearing of "show interface" counters 01:46:16















Release 12.0(33)S, OL-8832-01, Rev. C9


11-9



Configuring FDL

Facility Data Link (FDL) is a 4-kbps channel provided by the Extended Super Frame (ESF) T1 framing format. The FDL performs outside the payload capacity and allows you to check error statistics on terminating equipment without intrusion.

Command



Purpose





Router(config-controller)# fdl [ ansi | att | both ] If the framing format was configured for esf , configures the format used for Facility Data Link

(FDL).

•

•

• ansi —Select ansi for FDL to use the ANSI

T1.403 standard. att —Select att for FDL to use the AT&T

TR54016 standard.

both —Select both for FDL to use both the

ANSI T1.403 standard and the AT&T

TR54016 standard.

Verifying FDL

Use the show controllers t1 command to verify the fdl setting: router# show controllers t1

T1 6/0/1 is up.



No alarms detected.


Framing is ESF, FDL is ansi , Line Code is B8ZS, Clock Source is Line.







.

.



.

11-10


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring Multilink Point-to-Point Protocol (Hardware-based)

Multilink Point to Point Protocol (MLPPP) allows you to combine T1 or E1 lines into a bundle that has the combined bandwidth of multiple T1/E1 lines. You choose the number of bundles and the number of

T1 or E1 lines in each bundle.

MLPPP for T1/E1 Configuration Guidelines

The required conditions are:

•

•

•

Only T1 or E1 links in a bundle

All links on the same SPA

Maximum of 12 links in a bundle.

Note Some notes about hardware-based MLPPP:

Only 3 fragmentation sizes are possible 128, 256 and 512 bytes

Fragmentation is enabled by default, default size is 512 bytes

Fragmentation size is configured using the ppp multilink fragment-delay command after using the interface multilink command. The least of the fragmentation sizes (among the 3 sizes possible) satisfying the delay criteria is configured. (e.g., a 192 byte packet causes a delay of 1 millisecond on a

T1 link, so the nearest fragmentation size is 128 bytes.

The show ppp multilink command will indicate the MLPPP type and the fragmentation size:

Router# show ppp multilink

Multilink1, bundle name is Patriot2

Bundle up for 00:00:13

Bundle is Distributed

0 lost fragments, 0 reordered, 0 unassigned

0 discarded, 0 lost received, 206/255 load

0x0 received sequence, 0x0 sent sequence

Member links: 2 active, 0 inactive (max not set, min not set)

Se4/2/0/1:0, since 00:00:13, no frags rcvd


Distributed fragmentation on. Fragment size 512. Multilink in Hardware.

Fragmentation is disabled explicitly by using the no ppp multilink fragmentation command after using the interface multilink command.

Release 12.0(33)S, OL-8832-01, Rev. C9


11-11



Create a Multilink Bundle

To create a multilink bundle, use the following commands:

Command


Router(config)# interface multilink group-number

Router(config-if)# ip address address mask

Purpose


Creates a multilink interface and enter multilink interface mode.

• group-number —The group number for the multilink bundle.

Sets the IP address for the multilink group.

• address —The IP address.

• mask —The IP netmask.

Assign an interface to a Multilink Bundle

To assign an interface to a multilink bundle, use the following commands:

Command


Router(config)# interface serial slot/subslot/port/t1-number : channel-group

Purpose


Selects the interface to configure and enters interface configuration mode. See:



Router(config-if)# encapsulation ppp

Router(config-if)# multilink-group group-number

• slot/subslot/port/t1-number : channel-group— Selec t the interface to configure.

Enables PPP encapsulation.

Assigns the interface to a multilink bundle.

Router(config-if)# ppp multilink

Repeat these commands for each interface you want to assign to the multilink bundle.

• group-numbe r—The multilink group number for the T1 or E1 bundle.

Enables multilink PPP on the interface.

Configuring fragmentation size on an MLPPP Bundle (optional)

To configure the fragmentation size on a multilink ppp bundle, use the following commands:

Command


Purpose


11-12


Release 12.0(33)S, OL-8832-01, Rev. C9



Command

Router(config)# interface multilink slot/subslot/port/t1-number : channel-group

Router(config-if)# ppp multilink fragment-delay delay

Purpose

Creates a multilink interface and enters multilink interface mode.

• group-number—The group number for the multilink bundle. Range 1-2147483647

Sets the fragmentation size satisfying the configured delay on the multilink bundle.

• delay—delay in milliseconds

Disabling the fragmentation on an MLPPP Bundle (optional)


Command



Purpose




Disables the fragmentation on the multilink bundle.

Router(config-if)# no pppp multilink fragmentation

Verifying Multilink PPP

Use the show ppp multilink command to verify the PPP multilinks: router# show ppp multilink

Multilink1, bundle name is mybundle












Se6/0/6:0, since 01:01:06, no frags rcvd

Configuring MLFR for T1/E1

Multilink Frame Relay (MLFR) allows you to combine T1/E1 lines into a bundle that has the combined bandwidth of multiple T1/E1 lines. You choose the number of bundles and the number of T1/E1 lines in each bundle. This allows you to increase the bandwidth of your network links beyond that of a single

T1/E1 line.

Release 12.0(33)S, OL-8832-01, Rev. C9


11-13



MLFR for T1/E1 Configuration Guidelines

MLFR will function in hardware if all of the following conditions are met:

• Only T1 or E1 member links

•

•

All links are on the same SPA

Maximum of 12 links in a bundle



Command


Router(config)# interface mfr number

Router(config-if)# frame-relay multilink bid name

Purpose


Configures a multilink Frame Relay bundle interface.

• number —The number for the Frame Relay bundle.

(Optional) Assigns a bundle identification name to a multilink Frame Relay bundle.

•

Note name —The name for the Frame Relay bundle.

The bundle identification (BID) will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

Assign an Interface to a Multilink Bundle


Command


Router(config)# slot/subslot/port : interface serial channel-group

Router(config-if)# encapsulation frame-relay mfr number [ name ]

Purpose


Selects the interface to assign.

• slot/subslot/port:channel-group— Specifies the location of the interface.

“Specifying the

Interface Address on a SPA” section on page 11-6

Creates a multilink Frame Relay bundle link and associates the link with a bundle.

•


name —The name for the Frame Relay bundle.

11-14


Release 12.0(33)S, OL-8832-01, Rev. C9



Command

Router(config-if)# frame-relay multilink lid name

Router(config-if)# seconds

Router(config-if)# seconds frame-relay multilink hello frame-relay multilink ack

Router(config-if)# frame-relay multilink retry number

Purpose

(Optional) Assigns a bundle link identification name with a multilink Frame Relay bundle link.

•


The bundle link identification (LID) will not go into effect until the interface has gone from the down state to the up state.

One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

(Optional) Configures the interval at which a bundle link will send out hello messages. The default value is 10 seconds.

• seconds —Number of seconds between hello messages sent out over the multilink bundle.

(Optional) Configures the number of seconds that a bundle link will wait for a hello message acknowledgment before resending the hello message. The default value is 4 seconds.

• seconds —Number of seconds a bundle link will wait for a hello message acknowledgment before resending the hello message.

(Optional) Configures the maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment. The default value is 2 tries.

• number —Maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment.

Verifying Multilink Frame Relay

Use the show frame-relay multilink detailed command to verify the Frame Relay multilinks: router# show frame-relay multilink detailed

Bundle: MFR49, State = down, class = A, fragmentation disabled

BID = MFR49

No. of bundle links = 1, Peer's bundle-id =

Bundle links:

Serial6/0/0:0, HW state = up, link state = Add_sent, LID = test

Cause code = none, Ack timer = 4, Hello timer = 10,

Max retry count = 2, Current count = 0,

Peer LID = , RTT = 0 ms

Statistics:

Add_link sent = 21, Add_link rcv'd = 0,

Add_link ack sent = 0, Add_link ack rcv'd = 0,

Add_link rej sent = 0, Add_link rej rcv'd = 0,

Remove_link sent = 0, Remove_link rcv'd = 0,

Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,

Release 12.0(33)S, OL-8832-01, Rev. C9


11-15



Hello sent = 0, Hello rcv'd = 0,

Hello_ack sent = 0, Hello_ack rcv'd = 0,

outgoing pak dropped = 0, incoming pak dropped = 0

Invert Data on the T1/E1 Interface

If the interface on the 8-Port Clear Channel T1/E1 SPA is used to drive a dedicated T1 line that does not have B8ZS encoding, you must invert the data stream on the connecting CSU/DSU or on the interface.

Be careful not to invert data on both the CSU/DSU and the interface, as two data inversions will cancel each other out. To invert data on a T1/E1 interface, use the following commands:

Command



Router(config-if)# invert data

Purpose


Selects the serial interface.

Inverts the data stream.

Use the show running configuration command to verify that invert data has been set:

.

.

router# show running configuration

.

interface Serial6/0/0:0

no ip address

encapsulation ppp

logging event link-status

.

.

load-interval 30 invert data

no cdp enable

ppp chap hostname group1

ppp multilink

multilink-group 1

!

.

Changing a Channel Group Configuration

To alter the configuration of an existing channel group, the channel group needs to be removed first. To remove an existing channel group, use the following commands:

Command


Router(config)# controller { t1 | e1 } slot/subslot/port

Purpose




See:

Specifying the Interface


11-16


Release 12.0(33)S, OL-8832-01, Rev. C9



Command

Router(config-controller)# no channel-group t1 t1-number

Follow the steps in the section: Enabling the

Interfaces on the Controller, page 11-3

Purpose

Select the channel group you want to remove.

• t1 t1-number — Channel-group number.

Create a new channel group with the new configuration.

FRF.12 Guidelines

FRF.12 functions in hardware. Note the following:

• The fragmentation is configured at the main interface

• Only 3 fragmentation sizes are available - 128 bytes, 256 bytes, and 512 bytes.

LFI Guidelines

LFI can function two ways - using FRF.12 or MLPPP. MLPPP LFI can be done in both hardware and software while FRF.12 LFI is done only in hardware.

HW MLPPP LFI Guidelines

LFI using MLPPP will function only in hardware if there is just one member link in the MLPPP bundle.

The link can be a fractional T1 or full T1. Note the following:

• The ppp multilink interleave command needs to be configured to enable interleaving.

•

•

•

Only three fragmentation sizes are supported - 128 bytes, 256 bytes, and 512 bytes.

Fragmentation is enabled by default, the default size being 512 bytes.

A policy-map having a priority class needs to applied to main interface.

FRF.12 LFI Guidelines

•

•

•

LFI using FRF.12 is always done is hardware. Note the following:

The fragmentation is configured at the main interface

Only 3 fragmentation sizes are available - 128 bytes, 256 bytes, and 512 bytes.




Command


Purpose


Release 12.0(33)S, OL-8832-01, Rev. C9


11-17







Besides using the show running-configuration command to display your Cisco 12000 Series Router configuration settings, you can use the show interfaces serial and the show controllers serial commands to get detailed information on a per-port basis for your 8-Port Clear Channel T1/E1 SPA.


To find detailed interface information on a per-port basis for the 8-Port Clear Channel T1/E1 SPA, use the show interfaces serial command. For a description of the command output, see

Chapter 19, “SIP and SPA Command Reference.”

The following example provides sample output for interface port 0 on the SPA located in the first subslot of the SIP installed in slot 6 of a Cisco 7609 router:

Router# show interface serial 6/0/0:0





Encapsulation PPP, crc 32 , loopback not set





















•

•

•

•

Framing and Encapsulation Configuration Example, page 11-19

CRC Configuration Example, page 11-19


MLPPP Configuration Example, page 11-20

11-18


Release 12.0(33)S, OL-8832-01, Rev. C9



•

•

Invert Data on the T1/E1 Interface Example, page 11-22

MFR Configuration Example, page 11-21

Framing and Encapsulation Configuration Example

The following example sets the framing and encapsulation for the controller and interface:

! Specify the controller and enter controller configuration mode

!

Router(config)# controller t1 6/0/0

!

! Specify the framing method

!

Router(config-controller)# framing esf

!

! Exit controller configuration mode and return to global configuration mode

!

Router(config-controller)# exit

!

! Specify the interface and enter interface configuration mode

!

Router(config)# interface serial 6/0/0:0

!

! Specify the encapsulation protocol

!


!

! Exit interface configuratin mode

!

Router(config-if)# exit

!

! Exit global configuration mode

!


Router#

CRC Configuration Example

The following example sets the CRC size for the interface:

! Specify the interface and enter interface configuration mode

!


!

! Specify the CRC size

!

Router(config-if)# crc 32

!

! Exit interface configuration mode and return to global configuration mode

!


!


!


Router#

Release 12.0(33)S, OL-8832-01, Rev. C9


11-19




The following example configures Facility Data Link:

! Specify the controller and enter controller configuration mode

!


!

! Specify the FDL specification

!

Router(config-controller)# fdl ansi

!

! Exit controller configuration mode and return to global configuration mode

!


!


!


Router#

MLPPP Configuration Example

The following example creates a PPP Multilink bundle:

! Enter global configuration mode

!


!

! Create a multilink bundle and assign a group number to the bundle

!

Router(config)# interface multilink 1

!

! Specify an IP address for the multilink group

!

Router(config-if)# ip addres 123.456.789.111 255.255.255.0

!

! Enable Multilink PPP

!


!

! Leave interface multilink configuration mode

!


!

! Specify the interface to assign to the multilink bundle

!

Router(config)# interface serial 3/1//0:1

!

! Enable PPP encapsulation on the interface

!

Router(config-if)# encapsulation PPP

!

! Assign the interface to a multilink bundle

!

Router(config-if)# multilink-group 1

!

! Enable Multilink PPP

!


!

11-20


Release 12.0(33)S, OL-8832-01, Rev. C9



! Exit interface configuration mode

!


!


!


Router#

MFR Configuration Example

The following example configures Multilink Frame Relay (MFR):

! Create a MFR interface and enter interface configuration mode

!

Router(config)# interface mfr 49

!

! Assign the bundle identification (BID) name ‘test’ to a multilink bundle.

!

Router(config-if)# frame-relay multilink bid test

!


!


!

! Specify the serial interface to assign to a multilink bundle

!


!

! Creates a multilink Frame Relay bundle link and associates the link with a multilink bundle

!

Router(config-if)# encapsulation frame-relay mfr 49

!

! Assigns a bundle link identification (LID) name with a multilink bundle link

!

Router(config-if)# frame-relay multilink lid test

!

! Configures the interval at which the interface will send out hello messages

!

Router(config-if)# frame-relay multilink hello 15

!

! Configures the number of seconds the interface will wait for a hello message acknowledgement before resending the hello message

!

Router(config-if)# frame-relay multilink ack 6

!

! Configures the maximum number of times the interface will resend a hello message while waiting for an acknowledgement

!

Router(config-if)# frame-relay multilink retry 5

!


!


!


!


Router#

Release 12.0(33)S, OL-8832-01, Rev. C9


11-21



Invert Data on the T1/E1 Interface Example

The following example inverts the data on the serial interface:

! Enter global configuration mode

!


!

! Specify the serial interface and enter interface configuration mode

!


!

! Configure invert data

!


!


!


!


!


Router#

11-22


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

12

Configuring the 1-Port Channelized OC-3/STM-1

SPA

This chapter provides information about configuring the 1-Port Channelized OC-3/STM-1 SPA on

Cisco 12000 Series Routers. It includes the following sections:

•


•





Also refer to the related Cisco IOS Release 12.0 software command reference and master index publications. For more information about accessing these publications, see the “Related Documentation” section in the Preface.


This section describes how to configure the 1-Port Channelized OC-3/STM-1 SPA for the Cisco 12000

Series Routers and includes information about verifying the configuration. This document shows how to configure the 1-Port Channelized OC-3/STM-1 SPA in either SONET or SDH framing modes.


•

•

•

•


Selection of Physical Port and Controller configuration, page 12-2




This section lists the required configuration steps to configure the 1-Port Channelized OC-3/STM-1

SPA. Some of the required configuration commands implement default values that might be appropriate for your network. If the default value is correct for your network, then you do not need to configure the command.

•

Selection of Physical Port and Controller configuration

•

Interface Naming


Release 12.0(33)S, OL-8832-01, Rev. C9 12-1

Chapter 12 Configuring the 1-Port Channelized OC-3/STM-1 SPA


•

•

•

SONET mode Configuration

SDH mode Configuration

Verifying Interface Configuration

Note To better understand the address format used to specify the physical location of the Cisco 12000

SIP-401, SPA, and interfaces, see the:

“Selection of Physical Port and Controller configuration” section on page 12-2 .

Selection of Physical Port and Controller configuration

To select the physical port and controller configuration, use the following command: controller sonet slot / subslot / port

If the 1-Port Channelized OC-3/STM-1 SPA sits in subslot 0 of a Cisco 12000 SIP-401 in slot3, the

1-Port Channelized OC-3/STM-1 SPA port would be identified as controller SONET 3/0/0. Since there is only 1 port on a 1-Port Channelized OC-3/STM-1 SPA, the port number is always 0.

Interface Naming

Interface names are automatically generated, and the format will be dependent on the mode each particular linecard is operating on. The name format of the serial interface created are listed below.

SONET mode

• If framing is SONET and mode is vt-15:

• interface serial [ slot / subslot / port ] .

[ sts 1/ ds1 / t1 ] : [ channel-group ]

If framing is SONET and mode is CT3

•

• interface serial [ slot / subslot / port ] .

[ sts 1 / ds1 / ds1 ] : [ channel-group ]

If framing is SONET and mode is CT3-E1: interface serial [ slot / subslot / port ] .

[ sts 1 / ds1 / e1 ] : [ channel-group ]

If framing is SONET and mode is T3: interface serial [ slot / subslot / port.sts1

]

SDH mode

If the aug mapping is au-4, the au-4 value is always 1; if the aug mapping is au-3, then the only supported mode is c-11 ( carrying a T1).

• If SDH-AUG mapping is au-4 and if the tug-3 is mode t3/e3:

•

• interface serial [ slot / subslot / 0.1 / <tug-3> ]

If SDH-AUG mapping is au-3: interface serial [ slot / subslot / port / au-3 / <tug-2> / t1 ] : [ channel-group ]

If framing is SDH with ct-12 mode: interface serial [ slot/ subslot / 0.1 / <tug-3> / <tug-2> / e1 ] : [ channel-group ]

12-2


Release 12.0(33)S, OL-8832-01, Rev. C9



• If framing is SDH with c-11 mode: interface serial [ slot / subslot / 0.<au-3> / <tug-2> / t1 ] : [ channel-group ]

For channelized T3 mode

• If framing is SONET or SDH with au-3: interface serial [ slot | subslot | port ] [ ds3| DS1 ] : [ channel-group ]

Selection of Physical Port and controller Configuration—SONET mode

To create the interface for the 1-Port Channelized OC-3/STM-1 SPA, complete these steps:

Step 1

Command

Router(config)# controller sonet slot/subslot/port

Purpose



See the:

“Selection of Physical Port and

Controller configuration” section on page 12-2

Note The port number is always zero on the 1-Port

Channelized OC-3/STM-1 SPA.

SONET mode Configuration

To configure the SONET controller, complete these steps:

Step 1

Step 2

For SONET controllers:

Router(config-controller)# framing

{ sonet | sdh }


• sonet —Specifies SONET as the frame type. This is the default.

•


{ internal | line }

Note sdh —Specifies sdh as the frame type.


The clock source is set to internal if the opposite end of the connection is set to line and the clock source is set to line if the opposite end of the connection is set to internal.

•

• internal —Specifies that the internal clock source is used. line —Specifies that the network clock source is used.

This is the default for T1 and E1.

Release 12.0(33)S, OL-8832-01, Rev. C9


12-3



Step 3 Router(config-controller)# loopback { local |

[no] network ]

Enables or disables loopback mode on a sonet controller.

•

• local loopback —loops data from the transmit path to the receive path. network loopback —loops data received on the external port to the transmit path and back out the external port.

Default is disabled loopback.

sts-1 # —Specifies the SONET STS level.

Step 4

Step 5

In SONET framing:

Router(config-controller)# sts-1 sts1#

[no] mode { vt-15 | ct3 | t3 | ct3-e1 }

Step 6 •

Specifies the mode of operation of a STS-1 path:

• vt-15 —A STS-1 is divided into 7 vtg. Each vtg then divided into 4 VT1.5’s, each carrying a T1.

•

• ct3 —A STS-1 carry a DS3 signal divided into 28 T1s

(PDH) t3— STS-1 or AU-4/TUG3 carries a unchannelized

(clear channel) T3 sts1 carries T1s (sonet - vt): router(config-controller-sts1)# mode vt-15

• ct3 —The channelized T3 is carrying E1 circuits

Selects a mode of operation.

Step 7 or

• sts1 carries T1s (sonet - ds3 down to ds1): router(config-controller-sts1)# mode ct3 or

• sts1 carries DS3(sonet - ds3): router(config-controller-sts1)# mode t3

Router(config-ctrlr-sts1)# vtg ?

<1-7> vtg number <1-7>

• vtg —Specifies the vtg number.

12-4


Release 12.0(33)S, OL-8832-01, Rev. C9



Step 8

Step 9

Router(config-ctrlr-sts1)# vtg 1 ?

T1 T1 line configuration

Router(config-ctrlr-sts1)#v tg 1 t1 1 chan

0 tim 1 - 3

Configures the T1s on the vtgs. For SONET framing, vtg# range is 1 to 7.

Router(config-ctrlr-sts1)# vtg 2 t1 4 chan

0 tim 1 - 2, 5-6

Router(config-ctrlr-sts1)# vtg 3 t1 #

<1-4> t1 line number <1-4>

Channelized OC-3: vtg <vtg#>...

ct3: no prefix

Configures channels. Once TUG-3/STS-1 is configured, then one of the parser modes config-ctrlr-{tug3|au3|sts1} can be set.

There is no channelized E3 mode.

The e1# range is from 1 to 3

The t1# range is from 1 to 4.

For PDH mode, where a channelized t3 is mapped into the sts-1, the t1# range is from 1 to 28.

Release 12.0(33)S, OL-8832-01, Rev. C9


12-5



SDH mode Configuration

To configure SDH mode, complete the following steps:

Step 1 For SDH controllers:

Router(config-controller)# framing

{ sonet | sdh }

Step 2

Step 3

Step 4

Router(config-controller)# aug mapping { au-3 | au-4 }

If AUG mapping is au-4: au-4 <au-4#> tug-3 <tug-3#>

If AUG mapping is au-3: au-3 <au-3#>

In SDH framing in AU-4 mode:

[no] mode {c-12 | t3 | e3}


•

• sonet —Specifies SONET as the frame type. This is the default. sdh —Specifies sdh as the frame type.

Configures AUG mapping for SDH only. If the AUG mapping is configured to be au-4, then the following muxing/alignment/mapping will be used:

TUG-3 <--> VC-4 <--> AU-4 <--> AUG

If the mapping is configured to be au-3, then the following muxing/alignment/mapping will be used:

VC-3 <--> AU-3 <--> AUG

This command will be available only when sdh framing is configured.

Default is au-4.

Configures TUG-3/AU-3/STS-1. Depending on the framing mode of Sonet or SDH, each STS-1 and each TUG-3/AU-3 of a STM-1 can be configured with this command.

Depending on currently configured AUG mapping setting, this command will further specify TUG-3, AU-3 or STS-1 muxing. As result, the CLI command parser will enter into config-ctrlr-tug3, config-ctrlr-au3 or config-ctrlr-sts1 parser mode, which will make only relevant commands visible.

The au-4# is 1.

The tug-3# range is from 1 to 3.

The au-3# range is from 1 to 3.

The sts-1# is from 1 to 3.

C-11 and c-12 are container level-n (SDH) Channelized T3s.

They are types of T3 channels that are subdivided into 28 T1 channels.

• c-12 —Specifies a AU-4/TUG-3 is divided into 7 tug2.

Each tug2 then divided into 3 TU12’s, each carrying an

E1 (C-12).

•

•

• c-11 —Specifies a AU-3 is divided into 7 tug2. Each tug2 then divided into 4 TU11’s, each carrying a T1 (C-11).

t3 —Specifies a STS-1 or AU-4/TUG3 carries a unchannelized (clear channel) T3 e3 —Specifies a AU-4/TUG3 carries a unchannelized

(clear channel) E3

12-6


Release 12.0(33)S, OL-8832-01, Rev. C9



Configure Channelized DS3

To configure channelized DS3 mode, complete the following steps:

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Router(config)# slot/subslot/port controller

Router(config)#sts-1 sts1-# sonet Select the controller to configure and enter controller configuration mode.


See the:

“Selection of Physical Port and Controller configuration” section on page 12-2

The sts-1# is from 1 to y, y being the Sonet STS level, such as in

OC-3.

Router(config)# t3 framing { c-bit | m23 | auto-detect }

Specifies framing mode.

• c-bit —Specifies C-bit parity framing.

Router(config-controller)# source { internal | line } clock

•

• m23 —Specifies M23 framing.

auto-detect— Detects the framing type at the device at the end of the line and switches to that framing type. If both devices are set to auto-detect, c-bit framing is used.


Note The clock source is set to internal if the opposite end of the connection is set to line and the clock source is set to line if the opposite end of the connection is set to internal.

• internal —Specifies that the internal clock source is used.

•


Router(config-controller)# [no] t3 loopback { local | network [line | payload] | remote [line | payload] }

Enables or disables loopback mode on a SONET controller.

• local loopback receive path.

—loops data from the transmit path to the

• network loopback —loops data received on the external port to the transmit path and back out the external port.

Remote loopback —Applicable only to c-bit framing.

[no] t3 mdl string string

[ eic | fic | generator | lic | pfi | port | unit

[no] t3 mdl transmit { idle-signal | test-signal path |

}

}

Default is no loopback.

Configures MDL support.

•

•

•

• eic —Specified equipment ID code fic — frame ID code generator —generator number in MDL test signal lic —location ID code

•

• pfi— facility ID code in MDL path message port — port number in MDL idle string message

• unit —unit code

Default is no mdl string and no mdl transmit.

Release 12.0(33)S, OL-8832-01, Rev. C9


12-7



Step 7 t3 equipment { customer | network } loopback

Step 8 t3 bert pattern pattern interval

1-14400

Equipment customer loopback enables the port to honor remote loopback request. Equipment network loopback disables this functionality.

Note Remote loopbacks are only available in c-bit framing mode.

Enables BERT testing.

12-8


Release 12.0(33)S, OL-8832-01, Rev. C9



DS1 Configuration (Channelized T3 mode)

To configure DS1 complete the following steps:

Step 1 [no] prefix t1 t1# clock source

{ internal | line}

Configures the clocking source.

Step 2 [no] prefix t1 t1# fdl ansi Enables the one-second transmission of the remote performance reports via Facility Data Link (FDL) per ANSI T1.403

Note that without this command, FDL will run in ATT mode. ATT mode is not mutually exclusive or different from ANSI mode,

ANSI mode is a super-set of ATT mode.

Step 3

Step 4

Step 5

[no] prefix t1 t1# framing { sf | esf }

[no] prefix t1 t1# yellow

{ detection | generation }

[no] prefix t1 t1# shutdown

[no] prefix t1 t1# channel-group channel-group# timeslots list-of-timeslots speed [ 56 | 64 ]

Enables detection and generation of DS1 yellow alarms

Note

Step 6 [no] prefix t1 t1# loopback { local

| network line | remote {line fdl

{ansi | bellcore } | payload fdl ansi }}

Note

Note

Local network payload loopback is not supported due to

TEMUX-84/TEMUX-84E limitations.

Only 6 E1 berts can be performed concurrently due to

TEMUX-84/TEMUX-84E limitations.

E1 Configuration (Channelized T3/E3 mode)

E1 configuration must be done in channelized DS3 mode. To configure E1, complete the following steps:

Step 1 [no] prefix e1 e1# channel-group channel-group# timeslots list-of-timeslots speed [ 56 | 64 ]

Step 2

Step 3

Step 4

Step 5

[no] prefix e1 e1# unframed

[no] prefix e1 e1# [unframed | framing] { crc4 | no-crc4 }

[no] prefix e1 e1# clock source

{ internal | line }

[no] prefix e1 e1# national bits pattern

Configures clock source.


Release 12.0(33)S, OL-8832-01, Rev. C9 12-9



Step 6 [no] prefix e1 e1# loopback [local

| network]

Step 7 [no] prefix e1 e1# shutdown

BERT Test Configuration

To configure BERT test, complete the following:

Step 1 [no] [ [ e1 | t1] [ e1# | t1# ] bert pattern { 2^11 | 2^15 || 2^20 QRSS

} interval time

Send a BERT pattern on a DS1/E1 line.

Unchannelized E3 Serial Interface Configuration

To configure an unchannelized E3 serial interface, complete the following:

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Step 8

[no] dsu mode { cisco | digital-link

| kentrox }

•

• cisco —Specifies cisco as the dsu mode.

digital-link —Specifies Digital link as the dsu mode. Range is from 300-34010.

[no]

[no]

[no]

[no]

dsu bandwidth number scramble national bit crc { 16 | 32 }

{ 0 | 1 }

• kentrox —Specifies kentrox as the dsu mode. Range is

1000-24500, 34010.

Default is cisco .

Specifies the maximum allowed bandwidth in Kpbs.

Default is no scramble.

Default is 0.

Default is 16 bit (CRC-CITT).

[no] loopback { network | local | remote }

[no] shutdown

[no] bert pattern pattern interval

1-14400

An example of a valid pattern is {2^15 | 2^23 | 0s | 1s }.


Router(config)# show controllers t1

T1 6/0/1 is up.



No alarms detected.

blarm-trigger is not set

12-10


Release 12.0(33)S, OL-8832-01, Rev. C9



Framing is ESF, Line Code is B8ZS, Clock Source is Line.










Use the show interface serial command to verify the interface configuration:

Router(config)# show interface serial

Serial2/0/0.1/2 unassigned YES TFTP administratively down down

Serial2/1/0.1/1/1:0 unassigned YES unset down down



Serial2/1/0.2/1:0 unassigned YES unset down down



Serial2/1/0.3 unassigned YES unset down down

UUT#sh int Serial2/1/0.1/1/1:0

Serial2/1/0.1/1/1:0 is down, line protocol is down

Hardware is Channelized-T3



















UUT#sh run | beg 2/1/0 controller SONET 2/1/0 ais-shut framing sonet clock source line overhead j0 1

!

sts-1 1 mode vt-15 vtg 1 t1 1 channel-group 0 timeslots 1-3 vtg 2 t1 4 channel-group 0 timeslots 1-2,5-6 vtg 2 t1 4 channel-group 1 timeslots 3,7,9

!

sts-1 2 mode ct3 t1 1 channel-group 0 timeslots 1-24 t1 2 channel-group 0 timeslots 1-12 t1 3 channel-group 0 timeslots 1

!


Release 12.0(33)S, OL-8832-01, Rev. C9 12-11



.

.

sts-1 3 mode t3

!

controller T3 3/1/0 shutdown cablelength 224

!

controller T3 3/1/1 shutdown cablelength 224

!

!

interface Loopback0 ip address 172.10.11.1 255.255.255.255


There are several standard, but optional, configurations that might be necessary to complete the configuration of your serial SPA.

•

•

•

•

•

•

•

•

•

•

•


Configuring the CRC Size for T1, page 12-13


Configuring Multilink Point-to-Point Protocol (Hardware-based), page 12-14

Configuring MLFR, page 12-17

Invert Data on the T1/E1 Interface, page 12-19

Changing a Channel Group Configuration, page 12-19

FRF.12 Guidelines, page 12-20

LFI Guidelines, page 12-20

HW MLPPP LFI Guidelines, page 12-20

FRF.12 LFI Guidelines, page 12-20



Step 1

Step 2

Command


Router(config)# interface serial

For addressing information, refer to the “Interface

Naming” section on page 12-2 .

Purpose




12-12


Release 12.0(33)S, OL-8832-01, Rev. C9



Step 3

Step 4

Command

Router(config-if)# encapsulation encapsulation-type {hdlc | ppp | frame-relay}

Router(config-if)# crc { 16 | 32 }

Purpose


•

• hdlc —High-Level Data Link Control

(HDLC) protocol for serial interface. This encapsulation method provides the synchronous framing and error detection functions of HDLC without windowing or retransmission. This is the default for synchronous serial interfaces.

ppp —PPP (for serial interface).

• frame-relay —Frame Relay (for serial interface).

Selects the CRC size in bits.

• 16 —16-bit CRC. This is the default

• 32 —32-bit CRC.

Configuring the CRC Size for T1

The 1-Port Channelized OC-3/STM-1 SPA interface uses a 16-bit cyclic redundancy check (CRC) by default, but also support a 32-bit CRC. CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. The designators 16 and 32 indicate the length (in bits) of the frame check sequence (FCS). A CRC of 32 bits provides more powerful error detection, but adds overhead. Both the sender and receiver must use the same setting.

CRC-16, the most widely used CRC throughout the United States and Europe, is used extensively with

WANs. CRC-32 is specified by IEEE 802 and as an option by some point-to-point transmission standards. It is often used on Switched Multimegabit Data Service (SMDS) networks and LANs.

To set the length of the cyclic redundancy check (CRC) on a T1 interface, use these commands:

Command


Purpose







Configuring FDL

Facility Data Link (FDL) is a 4-kbps channel provided by the Extended Super Frame (ESF) T1 framing format. The FDL performs outside the payload capacity and allows you to check error statistics on terminating equipment without intrusion.

Release 12.0(33)S, OL-8832-01, Rev. C9


12-13



Command


Purpose


Router(config)# controller sonet slot/subslot/port


See the “Interface Naming” section on page 12-2 .

Router(config-controller)# sts-1


If the framing format was configured for esf , configures the format used for Facility Data Link

(FDL).

Router(config-controller) vtg 1 t1 1 fdl

•

• ansi —Select ansi for FDL to use the ANSI

T1.403 standard. vtg —Specifies the vtg number

Verifying FDL

Use the show controllers t1 command to verify the fdl setting: router# show controllers t1

T1 6/0/1 is up.



No alarms detected.


Framing is ESF, FDL is ansi , Line Code is B8ZS, Clock Source is Line.







.

.



.

Configuring Multilink Point-to-Point Protocol (Hardware-based)

Multilink Point to Point Protocol (MLPPP) allows you to combine interfaces which correspind to an entire T1 or E1 multilink bundle. You choose the number of bundles and the number of T1 or E1 lines in each bundle.

MLPPP Configuration Guidelines

The required conditions are:

• Only T1 or E1 links in a bundle

•

•

All links on the same SPA

Maximum of 12 links in a bundle.

12-14


Release 12.0(33)S, OL-8832-01, Rev. C9



Note Some notes about hardware-based MLPPP:

Only 3 fragmentation sizes are possible 128, 256 and 512 bytes

Fragmentation is enabled by default, default size is 512 bytes

Fragmentation size is configured using the ppp multilink fragment-delay command after using the interface multilink command. The least of the fragmentation sizes (among the 3 sizes possible) satisfying the delay criteria is configured. (e.g., a 192 byte packet causes a delay of 1 millisecond on a

T1 link, so the nearest fragmentation size is 128 bytes.

The show ppp multilink command will indicate the MLPPP type and the fragmentation size:

Router# show ppp multilink

Multilink1, bundle name is Patriot2









Distributed fragmentation on. Fragment size 512. Multilink in Hardware.

Fragmentation is disabled explicitly by using the no ppp multilink fragmentation command after using the interface multilink command.



Command



Router(config-if)# ip address address mask

Purpose


Creates a multilink interface and enter multilink interface mode.

• group-number —The group number for the multilink bundle.

Sets the IP address for the multilink group.

• address —The IP address.

• mask —The IP netmask.

Release 12.0(33)S, OL-8832-01, Rev. C9


12-15



Assign an interface to a Multilink Bundle


Command



Purpose



For addressing information, refer to the

“Interface Naming” section on page 12-2

.


Router(config-if)# multilink-group group-number

Enables PPP encapsulation.

Assigns the interface to a multilink bundle.


Repeat these commands for each interface you want to assign to the multilink bundle.

• group-numbe r—The multilink group number for the T1 or E1 bundle.

Enables multilink PPP on the interface.

Configuring fragmentation size on an MLPPP Bundle (optional)

To configure the fragmentation size on a multilink ppp bundle, use the following commands:

Command


Router(config)# interface multilink


“Interface Naming” section on page 12-2

.

Router(config-if)# ppp multilink fragment-delay delay

Purpose




Sets the fragmentation size satisfying the configured delay on the multilink bundle.

• delay—delay in milliseconds

Disabling the fragmentation on an MLPPP Bundle (optional)


Command



Router(config-if)# no pppp multilink fragmentation

Purpose




Disables the fragmentation on the multilink bundle.

12-16


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring MLFR

Multilink Frame Relay (MLFR) allows you to combine T1/E1 lines into a bundle that has the combined bandwidth of multiple T1/E1 lines. You choose the number of bundles and the number of T1/E1 lines in each bundle. This allows you to increase the bandwidth of your network links beyond that of a single

T1/E1 line.

MLFR Configuration Guidelines

MLFR will function in hardware if all of the following conditions are met:

•

•

•

Only T1 or E1 member links

All links are on the same SPA

Maximum of 12 links in a bundle



Command


Router(config)# interface mfr number

Router(config-if)# frame-relay multilink bid name

Purpose


Configures a multilink Frame Relay bundle interface.


(Optional) Assigns a bundle identification name to a multilink Frame Relay bundle.

•


The bundle identification (BID) will not go into effect until the interface has gone from the down state to the up state. One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

Assign an Interface to a Multilink Bundle


Command


Purpose





Selects the interface to assign.

Release 12.0(33)S, OL-8832-01, Rev. C9


12-17



Command

Router(config-if)# encapsulation frame-relay mfr number [ name ]

Router(config-if)# name

Router(config-if)# seconds

Router(config-if)# seconds frame-relay multilink lid frame-relay multilink hello frame-relay multilink ack

Router(config-if)# frame-relay multilink retry number

Purpose

Creates a multilink Frame Relay bundle link and associates the link with a bundle.


name —The name for the Frame Relay bundle.

•

(Optional) Assigns a bundle link identification name with a multilink Frame Relay bundle link.

•


The bundle link identification (LID) will not go into effect until the interface has gone from the down state to the up state.

One way to bring the interface down and back up again is by using the shut and no shut commands in interface configuration mode.

(Optional) Configures the interval at which a bundle link will send out hello messages. The default value is 10 seconds.

• seconds —Number of seconds between hello messages sent out over the multilink bundle.

(Optional) Configures the number of seconds that a bundle link will wait for a hello message acknowledgment before resending the hello message. The default value is 4 seconds.

• seconds —Number of seconds a bundle link will wait for a hello message acknowledgment before resending the hello message.

(Optional) Configures the maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment. The default value is 2 tries.

• number —Maximum number of times a bundle link will resend a hello message while waiting for an acknowledgment.

Verifying Multilink Frame Relay

Use the show frame-relay multilink detailed command to verify the Frame Relay multilinks: router# show frame-relay multilink detailed

Bundle: MFR49, State = down, class = A, fragmentation disabled

BID = MFR49

No. of bundle links = 1, Peer's bundle-id =

Bundle links:

Serial6/0/0:0, HW state = up, link state = Add_sent, LID = test

Cause code = none, Ack timer = 4, Hello timer = 10,

Max retry count = 2, Current count = 0,

12-18


Release 12.0(33)S, OL-8832-01, Rev. C9



Peer LID = , RTT = 0 ms

Statistics:

Add_link sent = 21, Add_link rcv'd = 0,

Add_link ack sent = 0, Add_link ack rcv'd = 0,

Add_link rej sent = 0, Add_link rej rcv'd = 0,

Remove_link sent = 0, Remove_link rcv'd = 0,

Remove_link_ack sent = 0, Remove_link_ack rcv'd = 0,

Hello sent = 0, Hello rcv'd = 0,

Hello_ack sent = 0, Hello_ack rcv'd = 0,

outgoing pak dropped = 0, incoming pak dropped = 0

Invert Data on the T1/E1 Interface

If the interface on the 1-Port Channelized OC-3/STM-1 SPA is used to drive a dedicated T1 line that does not have B8ZS encoding, you must invert the data stream on the connecting CSU/DSU or on the interface. Be careful not to invert data on both the CSU/DSU and the interface, as two data inversions will cancel each other out. To invert data on a T1/E1 interface, use the following commands:

Command


Purpose






Selects the serial interface.

Inverts the data stream.

Use the show running configuration command to verify that invert data has been set:

.

.

router# show running configuration

.

interface Serial6/0/0:0

no ip address

encapsulation ppp

logging event link-status

.

.

load-interval 30 invert data

no cdp enable

ppp chap hostname group1

ppp multilink

multilink-group 1

!

.

Changing a Channel Group Configuration

To alter the configuration of an existing channel group, the channel group needs to be removed first using the no form of the channel-group command. To remove an existing channel group, use the following commands:

Release 12.0(33)S, OL-8832-01, Rev. C9


12-19



Command


Purpose


Router(config)#


“Interface

Naming” section on page 12-2

.


Router(config-controller)# no channel-group t1 t1-number

Select the channel group you want to remove.

• t1 t1-number — channel-group number.

FRF.12 Guidelines

FRF.12 functions in hardware. Note the following:

• The fragmentation is configured at the main interface

• Only 3 fragmentation sizes are available - 128 bytes, 256 bytes, and 512 bytes.

LFI Guidelines

LFI can function two ways - using FRF.12 or MLPPP. MLPPP LFI can be done in both hardware and software while FRF.12 LFI is done only in hardware.

HW MLPPP LFI Guidelines

LFI using MLPPP will function only in hardware if there is just one member link in the MLPPP bundle.

The link can be a fractional T1 or full T1. Note the following:

•

•

The ppp multilink interleave command needs to be configured to enable interleaving.

Only three fragmentation sizes are supported - 128 bytes, 256 bytes, and 512 bytes.

•

•

Fragmentation is enabled by default, the default size being 512 bytes.


FRF.12 LFI Guidelines

LFI using FRF.12 is always done is hardware. Note the following:

•

•

•

The fragmentation is configured at the main interface

Only 3 fragmentation sizes are available - 128 bytes, 256 bytes, and 512 bytes.


12-20


Release 12.0(33)S, OL-8832-01, Rev. C9





Command


Purpose






Besides using the show running-configuration command to display your Cisco 12000 Series Router configuration settings, you can use the show interface serial and the show controllers serial commands to get detailed information on a per-port basis for your1-Port Channelized OC-3/STM-1 SPA.


To find detailed interface information on a per-port basis for the 1-Port Channelized OC-3/STM-1 SPA use the show interface serial command.

The following example provides sample output for interface port 0 on the SPA located in the first subslot of the Cisco 12000 SIP-401 installed in slot 2 of a Cisco 12000 router:

Router# show interface serial 2/1/0.2/1:0

Serial2/1/0.2/1:0 is down, line protocol is down

Hardware is Channelized-T3


















UUT#sh int Serial2/1/0.3

Serial2/1/0.3 is down, line protocol is down

Hardware is CHOCx SPA







Release 12.0(33)S, OL-8832-01, Rev. C9 12-21










0 parity

(Remaining output omitted)

12-22


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

13

Command Summary for Serial SPAs

Table 13-1

provides an alphabetical list of some of the related commands to configure, monitor, and maintain Serial SPAs. For more information about the commands, see


Command Reference”

in this book and the Cisco IOS Release 12.2 command reference and master index publications.

Command Summary Table 13-1

Command

Router(config-subif) bert errors [number]

Router(config-subif) bert pattern {0s | 1s | 2^15 | 2^20 |

2^23 | alt-0-1 | qrss} interval minutes}

Router(config-subif) card type {t1 | e1} slot subslot

Purpose

Transmits BERT errors while running any bert pattern.

Starts a BERT pattern on a port.

Router(config-subif) card type {t3 | e3} slot subslot

Router(config-subif) framing {sf | esf}

Router(config-subif) framing {c-bit | m23}

Router(config-subif) framing {bypass | c-bit | m13}

Configures ports on SPA in T1 or E1 mode.

Configures ports on SPA in T3 or E3 mode.

Selects the frame type for a T1 or E1 data line.

Selects the frame type for a T3 port.

Selects the frame type for a T3 or E3 port.

Router(config-subif) loopback {dte | local | network {line

| payload} | remote}

Router(config-subif) mdl [string {eic | fic | generator | lic

| pfi | port | unit}string] | [transmit {idle-signal | path | test-signal}]

Sets a loopback at various points in a transmitting and receiving path

Configures the Maintenance Data Link (MDL) message defined in the ANSI T1.107a-1990 specification

Router(config-subif) show controllers serial [slot/port] Displays serial controller statistics.

Router(config-subif) show interfaces serial

[number[:channel-group]] [accounting]

Displays information about a serial interface.

Router(config-subif) t1 channel framing { esf | sf }

Router(config-subif) ttb {country | rnode | serial | snode | soperator | x} line

Specifies the type of framing used by T1 channels.

Sends a trace trail buffer in E3 g832 framing mode.

Release 12.0(33)S, OL-8832-01, Rev. C9


13-1

Chapter 13 Command Summary for Serial SPAs

13-2


Release 12.0(33)S, OL-8832-01, Rev. C9

P A R T 4

Packet over SONET Shared Port Adapters

C H A P T E R

14

Overview of the POS SPAs


(MIB) support for the Packet over SONET (POS) SPAs on the Cisco 12000 series router.


• Release History, page 14-1

•

•

•

•

•

•

POS Technology Overview, page 14-2


Restrictions, page 14-5


SPA Architecture, page 14-8


Release History

Release

Cisco IOS Release

12.0(32)SY

Modification


Cisco 12000 SIP-501, and Cisco 12000 SIP-601 was introduced on the


•

•

•

•







• 8-Port OC-3c/STM-1 and OC-12c/STM-4 POS SPA

Support for the Spatial Reuse Protocol (SRP) feature was introduced on the

OC-192c POS SPAs and the 2-Port OC-48c/STM-16 POS SPA.

Release 12.0(33)S, OL-8832-01, Rev. C9


14-1

Chapter 14 Overview of the POS SPAs

POS Technology Overview

Cisco IOS Release

12.0(32)S

Cisco IOS Release

12.0(31)S2

Cisco IOS Release

12.0(31)S



•

•

1-Port OC-192c/STM-64 POS/RPR XFP SPA

1-Port OC-192c/STM-64 POS/RPR VSR Optics SPA




Cisco Frame Relay and RFC 2427 Frame Relay encapsulation is introduced for all POS SPAs on the Cisco 12000 series router.





• 1-Port OC-192c/STM-64 POS/RPR XFP SPA

POS Technology Overview

Packet-over-SONET is a high-speed method of transporting IP traffic between two points. This technology combines the Point-to-Point Protocol (PPP) with Synchronous Optical Network (SONET) and Synchronous Digital Hierarchy (SDH) interfaces.

SONET is an octet-synchronous multiplex scheme defined by the American National Standards Institute

(ANSI) standard (T1.1051988) for optical digital transmission at hierarchical rates from 51.840 Mbps to 2.5 Gbps (Synchronous Transport Signal, STS-1 to STS-48) and greater. SDH is an equivalent international standard for optical digital transmission at hierarchical rates from 155.520 Mbps

(Synchronous Transfer Mode-1 [STM-1]) to 2.5 Gbps (STM-16) and greater.

SONET specifications have been defined for single-mode fiber and multimode fiber. The POS SPAs on the Cisco 12000 series router allow transmission over both single-mode and multimode fiber at various optical carrier rates. The multirate SPAs (such as the 2-Port OC-3c/STM-1 and OC-12c/STM-4 POS

SPA) support use of OC-3c and OC-12c SFPs.

SONET/SDH transmission rates are integral multiples of 51.840 Mbps. The following transmission multiples are currently specified and used on the POS SPAs on the Cisco 12000 series router:

•

•

•

•

OC-3c/STM-1—155.520 Mbps

OC-12c/STM-4—622.080 Mbps

OC-48—2.488 Gbps

OC-192c/STM-64—9.953 Gbps

The POS specification (RFC 1619) describes the use of PPP encapsulation over SONET/SDH links.

Because SONET/SDH is, by definition, a point-to-point circuit, PPP is well-suited for use over these links. PPP treats SONET/SDH transport as octet-oriented full-duplex synchronous links. PPP presents an octet interface to the physical layer. The octet stream is mapped into the SONET/SDH Synchronous

14-2


Release 12.0(33)S, OL-8832-01, Rev. C9



Payload Envelope (SPE), with the octet boundaries aligned with the SPE octet boundaries. The PPP frames are located by row within the SPE payload. Because frames are variable in length, the frames are allowed to cross SPE boundaries.


This section provides a list of some of the primary features supported by the POS SPA hardware and software:

•

•

Jumbo frames (up to 9216 bytes)

Internal buffering to support short bursts of data traffic at the bus interface

•

•

•

•

•

HDLC and PPP encapsulation—All POS SPAs

Cisco Frame Relay and RFC 2427 Frame Relay encapsulation

Online insertion and removal (OIR) from the SIP, or OIR of the SIP with the SPA inserted

Small form-factor pluggable (XFP) optics module OIR for the 1-Port OC-192c/STM-64 POS/RPR

XFP SPA and SFP optics module OIR for the 2-Port OC-48c/STM-16 POS SPA, 2-Port, 4-Port, and

8-Port OC-3c/STM-1 and OC-12c/STM-4 POS SPAs, and 4-Port and 8-Port OC-3c/STM-1 POS

SPAs

Multirate functionality on 2-Port, 4-Port, and 8-Port OC-3c/STM-1 and OC-12c/STM-4 POS SPAs with support of OC-3c and OC-12c SFPs.

• Field-programmable gate array (FPGA) upgrade support

The POS SPAs also support the following groups of features:

•

•

•

•

•

SONET/SDH Compliance Features, page 14-3

SONET/SDH Error, Alarm, and Performance Monitoring Features, page 14-4

SONET/SDH Synchronization Features, page 14-4

WAN Protocol Features, page 14-5

Network Management Features, page 14-5

SONET/SDH Compliance Features

This section lists the SONET/SDH compliance features supported by the POS SPAs on the Cisco 12000 series router:

•

•

•

•

1+1 SONET Automatic Protection Switching (APS) as per G.783 Annex A

1+1 SDH Multiplex Section Protection (MSP) as per G.783 Annex A

American National Standards Institute (ANSI) T1.105

ITU-T G.707, G.783, G.957, G.958

Release 12.0(33)S, OL-8832-01, Rev. C9


14-3



•

•

Telcordia GR-253-CORE: SONET Transport Systems: Common Generic Criteria

Telcordia GR-1244: Clocks for the Synchronized Network: Common Generic Criteria

SONET/SDH Error, Alarm, and Performance Monitoring Features

This section lists the SONET/SDH error, alarm, and performance monitoring features supported by the

POS SPAs on the Cisco 12000 series router:

•

•

Signal failure bit error rate (SF-BER)

Signal degrade bit error rate (SD-BER)

•

•

•

Signal label payload construction (C2)

Path trace byte (J1)

Section:

–

–

Loss of signal (LOS)

Loss of frame (LOF)

•

–

–

Error counts for B1

Threshold crossing alarms (TCA) for B1

Line:

– Line alarm indication signal (LAIS)

–

–

Line remote defect indication (LRDI)

Line remote error indication (LREI)

•

–

–

Error counts for B2


Path:

– Path alarm indication signal (PAIS)

–

–

Path remote defect indication (PRDI)

Path remote error indication (PREI)

–

–

Error counts for B3


–

–

Loss of pointer (LOP)

New pointer events (NEWPTR)

–

–

Positive stuffing event (PSE)

Negative stuffing event (NSE)

SONET/SDH Synchronization Features

This section lists the SONET/SDH synchronization features supported by the POS SPAs on the


• Local (internal) timing (for inter-router connections over dark fiber or Wavelength Division

Multiplex [WDM] equipment)

14-4


Release 12.0(33)S, OL-8832-01, Rev. C9


Restrictions

•

•

Loop (line) timing (for connecting to SONET/SDH equipment)

+/– 20 ppm clock accuracy over full operating temperature

WAN Protocol Features

This section lists the WAN protocols supported by the POS SPAs on the Cisco 12000 series router:

• RFC 1661, The Point-to-Point Protocol (PPP)

• RFC 1662, PPP in HDLC framing

•

•

•

•

RFC 2615, PPP over SONET/SDH (with 1+x43 self-synchronous payload scrambling)

RFC 3518, Point-to-Point Protocol (PPP) Bridging Control Protocol (BCP)

Cisco Protect Group Protocol over UDP/IP (Port 1972) for APS and MSP

Multiprotocol Label Switching (MPLS)

Network Management Features

This section lists the network management features supported by the POS SPAs on the Cisco 12000 series router:

•

•

•

•

•

Simple Network Management Protocol (SNMP) Management Information Base (MIB) counters

Local (diagnostic) loopback

Network loopback

NetFlow Data Export

•

IP over the Section Data Communications Channel (SDCC)

RFC 3592 performance statistics for timed intervals (current, 15-minute, multiple 15-minute, and

1-day intervals):

–

–

Regenerator section

Multiplex section

–

–

Path errored seconds

Severely errored seconds

– Severely errored framed seconds

Restrictions

Table 14-1 provides information about POS feature compatibility and restrictions by SIP and SPA combination.

Release 12.0(33)S, OL-8832-01, Rev. C9


14-5


Restrictions

Table 14-1

Feature

Frame Relay

Resilient Packet

Ring (RPR)

Section Data

Communications

Channel (SDCC)

Spatial Reuse

Protocol (SRP)

POS Feature Compatibility and Restrictions by SIP and SPA Combination

Cisco 12000 SIP-401

Supported for all POS

SPAs.

Cisco 12000 SIP-501


SPAs.

Not supported.

Not supported.

Cisco 12000 SIP-600

In Cisco IOS Release

12.0(31)S2 and earlier—Not supported.

Cisco 12000 SIP-601


12.0(31)S2 and earlier—Not supported.


12.0(32)S and later—Supported for all

POS SPAs.

Not supported.


12.0(32)S and later—Supported for all

POS SPAs.

Not supported.

Not supported for the following SPAs:

•

•

4-Port and 8-Port

OC-3c/STM-1

POS SPA

2-Port and 4-Port

OC-12c/STM-4

Multirate POS

SPA

Not supported on any

POS SPAs.



SPAs.

•

•

4-Port and 8-Port

OC-3c/STM-1 POS

SPA

2-Port, 4-Port, and

8-Port

OC-3c/STM-1 and

OC-12c/STM-4 POS

SPA


12.0(32)S and earlier—Not supported.




12.0(32)SY:

• Supported:

•

2-Port OC-48c/STM

-16 POS SPA

Not supported:

–

–

4-Port and

8-Port

OC-3c/STM-1

POS SPA

2-Port, 4-Port, and 8-Port

OC-3c/STM-1 and

OC-12c/STM-4

POS SPA


12.0(32)SY:

•

•

All 1-Port

OC-192c/STM-64

POS/RPR SPAs

2-Port OC-48c/STM-

16 POS SPA


•

•

4-Port and 8-Port

OC-3c/STM-1 POS

SPA

2-Port, 4-Port, and

8-Port

OC-3c/STM-1 and

OC-12c/STM-4

POS SPA




12.0(32)SY:

• Supported:

–

–

All 1-Port

OC-192c/STM-

64 POS/RPR

SPAs

2-Port OC-48c/S

TM-16 POS

SPA

• Not supported:

– 4-Port and

8-Port

OC-3c/STM-1

POS SPA

– 2-Port, 4-Port, and 8-Port

OC-3c/STM-1 and

OC-12c/STM-4

POS SPA

14-6


Release 12.0(33)S, OL-8832-01, Rev. C9


Supported MIBs

Supported MIBs

The following MIBs are supported for POS SPAs on the Cisco 12000 series router:

• CISCO-APS-MIB

•

•

•

•

•

•

•

CISCO-ENTITY-EXT-MIB

CISCO-ENTITY-FRU-CONTROL-MIB

CISCO-OPTICAL-MONITORING-MIB

CISCO-SRP-MIB—Beginning in Cisco IOS Release 12.0(32)SY for supported SPAs.

ENTITY-MIB

IF-MIB (RFC 2233, The Interface Group MIB using SMIv2

OLD-CISCO-CHASSIS-MIB

)

• SONET-MIB (RFC 3592, Definitions of Managed Objects for the SONET/SDH Interface Type )





Release 12.0(33)S, OL-8832-01, Rev. C9


14-7




1-Port OC-192c/STM-64 POS/RPR XFP SPA Architecture

Figure 14-1 identifies the primary hardware devices that are part of the POS SPA architecture. The figure shows a single optics transceiver supported by both of the POS SPAs. However, the 1-Port

OC-192c/STM-64 POS/RPR SPA and 1-Port OC-192c/STM-64 POS/RPR VSR Optics SPA support fixed optics, while the 1-Port OC-192c/STM-64 POS/RPR XFP SPA supports XFP optics. The path of a packet remains the same except for where the optic transceiver support resides.

Figure 14-1 1-Port OC-192c/STM-64 POS/RPR XFP SPA Architecture

SPA

Connector

Optics

Transceiver

SONET/SDH

Streams

SONET/SDH

Framer

Packets

SPI4.2 Bus

To

Host

From

In POS mode, every incoming and outgoing packet on the OC-192 POS SPAs goes through the

SONET/SDH framer and SPI4.2 interface.


The following steps describe the path of an ingress packet through the 1-Port OC-192c/STM-64

POS/RPR XFP SPA:

1.

The framer receives SONET/SDH streams from the XFP optics, extracts clocking and data, and processes the section, line, and path overhead.

2.

The framer extracts the POS frame payload and verifies the frame size and frame check sequence

(FCS).

3.

4.

The framer passes valid frames to the System Packet Level Interface 4.2 (SPI4.2) interface on the

SPA.

The SPI4.2 interface transfers frames to the host through the SPI4.2 bus for further processing and switching.


The following steps describe the path of an egress packet through the 1-Port OC-192c/STM-64

POS/RPR XFP SPA:

1.

The host sends packets to the SPA using the SPI4.2 bus.

14-8


Release 12.0(33)S, OL-8832-01, Rev. C9



2.

3.

4.

5.

The SPA stores the data in the appropriate channel’s first-in first-out (FIFO) queue.

The SPA passes the packet to the framer.

The framer accepts the data and stores it in the appropriate channel queue.

The framer adds the FCS and SONET/SDH overhead.

6.

The framer sends the data to the XFP optics for transmission onto the network.

This section provides an overview of the architecture of the POS SPAs and describes the path of a packet in the ingress and egress directions. Some of these areas of the architecture are referenced in the SPA software and can be helpful to understand when troubleshooting or interpreting some of the SPA CLI and show command output.

1-Port OC-192c/STM-64 POS/RPR SPA and 1-Port OC-192c/STM-64 POS/RPR

XFP SPA Architecture

Figure 14-2 identifies the primary hardware devices that are part of the POS SPA architecture. The figure shows a single optics transceiver supported by both of the POS SPAs. However, the 1-Port

OC-192c/STM-64 POS/RPR SPA supports fixed optics, while the 1-Port OC-192c/STM-64 POS/RPR

XFP SPA supports XFP optics. The path of a packet remains the same except for where the optic transceiver support resides.

Figure 14-2 1-Port OC-192c/STM-64 POS/RPR XFP SPA Architecture

SPA

Connector

Optics

Transceiver

SONET/SDH

Streams

SONET/SDH

Framer

Packets

SPI4.2 Bus

To

Host

From

In POS mode, every incoming and outgoing packet on the 1-Port OC-192c/STM-64 POS/RPR SPA and

1-Port OC-192c/STM-64 POS/RPR XFP SPAgoes through the SONET/SDH framer, and SPI4.2 interface.


The following steps describe the path of an ingress packet through the 1-Port OC-192c/STM-64

POS/RPR XFP SPA:

1.

The framer receives SONET/SDH streams from the XFP optics, extracts clocking and data, and processes the section, line, and path overhead.

2.

The framer extracts the POS frame payload and verifies the frame size and frame check sequence

(FCS).

Release 12.0(33)S, OL-8832-01, Rev. C9


14-9



3.

4.

The framer passes valid frames to the System Packet Level Interface 4.2 (SPI4.2) interface on the

SPA.



4.

5.

6.

The following steps describe the path of an egress packet through the 1-Port OC-192c/STM-64

POS/RPR XFP SPA:

1.


2.

3.

The SPA stores the data in the appropriate channel’s first-in first-out (FIFO) queue.

The SPA passes the packet to the framer.

The framer accepts the data and stores it in the appropriate channel queue.


The framer sends the data to the XFP optics for transmission onto the network.

14-10


Release 12.0(33)S, OL-8832-01, Rev. C9



2-Port OC-48c/STM-16 POS SPA Architecture

Figure 14-3 identifies the primary hardware devices that are part of the 2-Port OC-48c/STM-16 POS

SPA architecture.

Figure 14-3 2-Port OC-48c/STM-16 POS SPA Architecture

External

SDRAM SPA

Connector

SONET/SDH

Streams

SONET/SDH

Framer

SONET/SDH

Streams

POS

Processor

Optics

Transceivers

Ring

MAC

Packets/

SPI4.2 Bus

To

Host

From


The following steps describe the path of an ingress packet through the 2-Port OC-48c/STM-16 POS

SPA:

1.

The framer receives SONET/SDH streams from the SFP optics, extracts clocking and data, and processes the section, line, and path overhead.

2.

3.

4.

The framer detects Loss of Signal (LOS), Loss of Frame (LOF), Severely Errored Frame (SEF), Line

Alarm Indication Signal (AIS-L), Loss of Pointer (LOP), Line Remote Defect Indication Signal

(Enhanced RDI-L), Path Alarm Indication Signal (AIS-P), Standard and Enhanced Path Remote

Defect Indication Signal (RDI-P), Path Remote Error Indication (Enhanced REI-P). The framer extracts or inserts DCC bytes.

The framer processes the S1 synchronization status byte, the pointer action bytes (per Telcordia

GR-253-CORE), and extracts or inserts DCC bytes.

The POS processor extracts the POS frame payload and verifies the frame size and frame check sequence (FCS).

5.

6.

7.

The POS processor supports PPP, Frame Relay, or HDLC modes and optionally performs payload scrambling.

The POS processor passes valid frames to the System Packet Level Interface 4.2 (SPI4.2) interface on the SPA.



The following steps describe the path of an egress packet through the 2-Port OC-48c/STM-16 POS SPA:

1.


2.

The SPA stores the data in the appropriate SPI4 channel’s first-in first-out (FIFO) queue.

Release 12.0(33)S, OL-8832-01, Rev. C9


14-11



4.

5.

6.

3.

The SPA passes the packet from the SPI4 interface to the POS processor where it is encapsulated in a POS frame and FCS is added.

The POS frame is sent to the SONET/SDH framer where it is placed into the SONET payload.


The framer sends the data to the SFP optics for transmission onto the network.


To verify the SPA hardware type that is installed in your Cisco 12000 series router, you can use the show diags command. For other hardware information, you can also use the show interfaces or show controllers commands. There are several other commands on the Cisco 12000 series router that also provide SPA hardware information. For more information about these commands, see the “Command

Summary for POS SPAs” and the “SIP and SPA Commands” chapters in this guide.

Table 14-2 shows the hardware description that appears in the show command output for each type of

SPA that is supported on the Cisco 12000 series router.


SPA

1-Port OC-192c/STM-64

POS/RPR SPA

Description in show interfaces Command

Hardware is Packet over

SONET


POS/RPR XFP SPA


POS SPA




SONET


SONET


SONET

4-Port OC-3c/STM-1 POS

SPA


SONET



8-Port OC-3c/STM-1 POS

SPA


SONET


SONET




SONET

Description in show diags Command

1-port OC192/STM64 POS/RPR Shared Port

Adapter / SPA-OC192POS-VSR /

SPA-OC192POS-LR

1-port OC192/STM64 POS/RPR XFP Optics

Shared Port Adapter / SPA-OC192POS-XFP

2-port OC48/STM16 POS/RPR Shared Port

Adapter / SPA-2XOC48POS/RPR

2-port OC12/STM4 POS Shared Port Adapter

/ SPA-2XOC12-POS

4-port OC3/STM1 POS Shared Port Adapter /

SPA-2XOC3-POS


/ SPA-4XOC12-POS

8-port OC3/STM1 POS Shared Port Adapter /

SPA-8XOC3-POS


/ SPA-8XOC12-POS

Example of the show interfaces Command

The following example shows output from the show interfaces command on a Cisco 12000 series router for the only interface port (0) on a 1-Port OC-192c/STM-64 POS/RPR SPA installed in subslot 1 of the

SIP installed in chassis slot 1:

Router# show interfaces pos 1/1/0

POS1/1/0 is up, line protocol is up

14-12


Release 12.0(33)S, OL-8832-01, Rev. C9



Hardware is Packet over SONET




Keepalive not set

Scramble enabled










0 parity





0 carrier transitions

The following example shows output from the show interfaces command on a Cisco 12000 series router for the first interface port (0) on a 2-Port OC-48c/STM-16 POS SPA installed in subslot 0 of the SIP installed in chassis slot 0:

Router# show interfaces pos3/0/0

POS3/0/0 is down, line protocol is down

Hardware is Packet over SONET




Scramble enabled










0 parity






Example of the show diags Command

The following example shows output from the show diags command on a Cisco 12000 series router with a 1-Port OC-192c/STM-64 POS/RPR XFP SPA located in subslot 0 of the SIP installed in chassis slot 2:

Router# show diags subslot 2/0

SUBSLOT 2/0 ( SPA-OC192POS-XFP ): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port Adapter

Product Identifier (PID) : SPA-OC192POS-XFP

Version Identifier (VID) : V01

PCB Serial Number : PRTA1304177

Top Assy. Part Number : 68-2190-01

Top Assy. Revision : A0


Release 12.0(33)S, OL-8832-01, Rev. C9 14-13



Hardware Revision : 2.1

CLEI Code : UNASSIGNED

Insertion Time : 3d08h (00:18:18 ago)

Operational Status : ok

The following example shows output from the show diags command on a Cisco 12000 series router with a 2-Port OC-48c/STM-16 POS SPA located in subslot 0 of the SIP installed in chassis slot 3:

Router# show diags subslot 3/0

SUBSLOT 3/0 ( SPA-2XOC48POS/RPR ): 2-port OC48/STM16 POS/RPR Shared Port Adapter

Product Identifier (PID) : SPA-2XOC48-POS/RPR


PCB Serial Number : JAB0922079S


Top Assy. Revision : 32


CLEI Code :

Insertion Time : 00:00:37 (00:04:50 ago)


Example of the show controllers Command

The following example shows output from the show controllers pos command on a Cisco 12000 series router for the only interface port (0) on a 1-Port OC-192c/STM-64 POS/RPR SPA installed in subslot 1 of the SIP installed in chassis slot 1:

Router# show controllers pos 1/1/0

POS1/1/0

SECTION

LOF = 0 LOS = 0 BIP(B1) = 0

LINE

AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0

PATH

AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0

LOP = 0 NEWPTR = 0 PSE = 0 NSE = 0

Active Defects: None

Active Alarms: None

Alarm reporting enabled for: SF SLOS SLOF B1-TCA B2-TCA PLOP B3-TCA

Framing: SONET

APS

COAPS = 0 PSBF = 0

State: PSBF_state = False

ais_shut = FALSE

Rx(K1/K2): 00/00 S1S0 = 00, C2 = 16

Remote aps status (none); Reflected local aps status (none)

CLOCK RECOVERY

RDOOL = 0

State: RDOOL_state = False

PATH TRACE BUFFER : STABLE

Remote hostname : Test

Remote interface: POS2/0/0

Remote IP addr : 10.41.41.1

Remote Rx(K1/K2): 00/00 Tx(K1/K2): 08/00

BER thresholds: SF = 10e-3 SD = 10e-6

TCA thresholds: B1 = 10e-6 B2 = 10e-6 B3 = 10e-6

14-14


Release 12.0(33)S, OL-8832-01, Rev. C9



Release 12.0(33)S, OL-8832-01, Rev. C9


14-15



14-16


Release 12.0(33)S, OL-8832-01, Rev. C9

Configuring the POS SPAs

C H A P T E R

15

This chapter provides information about configuring the Packet over SONET (POS) shared port adapters

(SPAs) on the Cisco 12000 series router. This chapter includes the following sections:

•

•







For more information about the commands used in this chapter, first see Chapter 19, “SIP and SPA

Command Reference” in this book, which documents new and modified commands. Also refer to the related Cisco IOS Release 12.0 software command reference and master index publications. For more information about accessing these publications, see the “Related Documentation” section.


This section describes how to configure POS SPAs and includes information about verifying the configuration.


•

•

•

•

•



Modifying the Interface MTU Size, page 15-4

Modifying the POS Framing, page 15-5

•

•

•

•

Modifying the Keepalive Interval, page 15-7

Modifying the CRC Size, page 15-7

Modifying the Clock Source, page 15-8

Modifying SONET Payload Scrambling, page 15-9

•

•

•

Configuring the Encapsulation Type, page 15-10

Configuring APS, page 15-11

Configuring POS Alarm Trigger Delays, page 15-12

Configuring SDCC, page 15-15

Release 12.0(33)S, OL-8832-01, Rev. C9


15-1

Chapter 15 Configuring the POS SPAs


•

•

•

Configuring Dynamic Packet Transport Features, page 15-16


Shutting Down and Restarting an Interface on a SPA, page 15-22


Step 1

Step 2

Step 3

Step 4

Step 5

This section lists the required configuration steps to configure the POS SPAs. Some of the required configuration commands implement default values that might be appropriate for your network. If the default value is correct for your network, then you do not need to configure the command. These commands are indicated by “(As Required)” in the Purpose column.

To configure the POS SPAs, complete the following steps:

Command


Router(config)# interface pos slot / subslot / port

Router(config-if)# ip-address mask [ secondary

Router(config-if)#

{ sonet | sdh }

Router(config-if)# ip address

] pos framing mtu bytes

Purpose


Specifies the POS interface to configure and enters interface configuration mode, where:

• slot / subslot / port —Specifies the location of the interface. See the “Specifying the Interface Address on a SPA” section on page 15-3 .



•

• mask —Specifies the mask for the associated IP subnet.

secondary —(Optional) Specifies that the configured address is a secondary IP address. If this keyword is omitted, the configured address is the primary IP address.

(As Required) Specifies the POS framing type, where:

•

• sonet —Enables Synchronous Optical Network framing for optical carrier (OC) rates. This is the default.

sdh —Enables Synchronous Digital Hierarchy framing for synchronous transfer mode ( rates.

The POS framing type must be configured to be the same on both ends of the POS link.

(As Required) Configures the maximum transmission unit (or packet size) for an interface, where:



15-2


Release 12.0(33)S, OL-8832-01, Rev. C9



Step 6

Step 7

Step 8

Step 9

Step 10

Step 11

Command

Router(config-if)# keepalive

[ period [ retries ]]

Purpose

(As Required) Specifies the frequency at which the Cisco IOS software sends messages to the other end of the link, to ensure that a network interface is alive, where:

•

• period— Specifies the time interval in seconds for sending keepalive packets. The default is 10 seconds.

retries— Specifies the number of times that the device will continue to send keepalive packets without response before bringing the interface down. The default is 5 retries.

Router(config-if)#

Router(config-if)#

{ line | internal } crc [ 16 | 32 ] clock source

The keepalive must be configured to be the same on both ends of the POS link.

(As Required) Specifies the length of the cyclic redundancy check

(CRC), where:

• 16 — Specifies a 16-bit length CRC. This is the default.

• 32 —Specifies a 32-bit length CRC.

The CRC size must be configured to be the same on both ends of the POS link.

(As Required) Specifies the clock source for the POS link, where:

• line — The link uses the recovered clock from the line. This is the default.

•

• internal —The link uses the internal clock source.

Router(config-if)# encapsulation encapsulation-type

(As Required) Specifies the encapsulation method used by the interface, where: encapsulation-type— Can be HDLC, PPP, or Frame Relay. The default encapsulation is HDLC.

Router(config-if)# ble-atm pos scram-

The encapsulation must be configured to be the same on both ends of the POS link.

Note In Cisco IOS Release 12.0(31)S, the POS SPAs do not support Frame Relay.

(As Required) Enables SONET payload scrambling.

The default configuration is SONET payload scrambling enabled.

The SONET payload scrambling must be configured to be the same on both ends of the POS link.

Router(config-if)# no shutdown Enables the interface.




• slot —Specifies the chassis slot number in the Cisco 12000 series router where the SIP is installed.

• subslot —Specifies the secondary slot of the SIP where the SPA is installed.

Release 12.0(33)S, OL-8832-01, Rev. C9


15-3







Modifying the Interface MTU Size

The Cisco IOS software supports three different types of configurable maximum transmission unit

(MTU) options at different levels of the protocol stack:

•

•

Interface MTU—Checked by the SPA on traffic coming in from the network. Different interface types support different interface MTU sizes and defaults. The interface MTU defines the maximum packet size allowable (in bytes) for an interface before drops occur. If the frame is smaller than the interface MTU size, but is not smaller than three bytes of payload size, then the frame continues to process.

IP MTU—Can be configured on a subinterface and is used by the Cisco IOS software to determine whether fragmentation of a packet takes place. If an IP packet exceeds the IP MTU size, then the packet is fragmented.

• Tag or Multiprotocol Label Switching (MPLS) MTU—Can be configured on a subinterface and allows up to six different labels, or tag headers, to be attached to a packet. The maximum number of labels is dependent on your Cisco IOS software release.

Different encapsulation methods and the number of MPLS MTU labels add additional overhead to a packet. For example, for an Ethernet packet, SNAP encapsulation adds an 8-byte header, dot1q encapsulation adds a 2-byte header, and each MPLS label adds a 4-byte header ( n labels x 4 bytes).

Interface MTU Configuration Guidelines

When configuring the interface MTU size on the POS SPAs, consider the following guidelines:

• If you are also using MPLS, be sure that the mpls mtu command is configured for a value less than or equal to the interface MTU.

• If you change the interface MTU size, the giant counter increments when the interface receives a packet that exceeds the MTU size that you configured, plus an additional 88 bytes for overhead, and an additional 2 or 4 bytes for the configured cyclic redundancy check (CRC).

For example, with a maximum MTU size of 9216 bytes, the giant counter increments:

–

–

For a 16-bit CRC (or FCS), when receiving packets larger than 9306 bytes (9216 + 88 + 2).

For a 32-bit CRC, when receiving packets larger than 9308 bytes (9216 + 88 + 4).

• The Frame Relay Local Management Interface (LMI) protocol requires that all permanent virtual circuit (PVC) status reports fit into a single packet. Using the default MTU of 4470 bytes, this limits the number of data-link connection identifiers (DLCIs) to 890. The following formula demonstrates how to determine the maximum DLCIs for a configured interface MTU:

– Maximum DLCIs = (MTU bytes – 20)/(5 bytes per DLCI)

– Maximum DLCIs for the default MTU = (4470 – 20)/5 = 890 DLCIs per interface

15-4


Release 12.0(33)S, OL-8832-01, Rev. C9



Interface MTU Configuration Task

To modify the MTU size on an interface, use the following command in interface configuration mode:

Command


Purpose

Configures the maximum packet size for an interface, where:

• bytes— Specifies the maximum number of bytes for a packet. The default is 4470 bytes.

To return to the default MTU size, use the no form of the command.

Verifying the MTU Size

To verify the MTU size for an interface, use the show interfaces pos privileged EXEC command and observe the value shown in the “MTU” field.

The following example shows an MTU size of 4470 bytes for interface port 0 (the first port) on the SPA installed in subslot 1 of the SIP that is located in slot 2 of the Cisco 12000 series router:


POS2/1/0 is up, line protocol is up (APS working - active)

Hardware is Packet over Sonet


.

.

MTU 4470 bytes , BW 155000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255.

.

Modifying the POS Framing

POS framing can be specified as SONET (Synchronous Optical Network) or SDH (Synchronous Digital

Hierarchy). SONET and SDH are a set of related standards for synchronous data transmission over fiber- optic networks. SONET is the United States version of the standard published by the American National

Standards Institute (ANSI). SDH is the international version of the standard published by the

International Telecommunications Union (ITU).

To modify the POS framing, use the following command in interface configuration mode:

Command Purpose

Router(config-if)# pos framing { sonet | sdh } Specifies the POS framing type, where:

•

• sonet —Enables Synchronous Optical Network framing for optical carrier (OC) rates. This is the default.

sdh —Enables Synchronous Digital Hierarchy framing for synchronous transfer mode ( rates.

The POS framing type must be configured to be the same on both ends of the POS link.

Release 12.0(33)S, OL-8832-01, Rev. C9


15-5



To return to the default, use the no form of the command.

Verifying the POS Framing

To verify the POS framing, use the show controllers pos privileged EXEC command and observe the value shown in the “Framing” field. The following example shows that POS framing mode is set to

SONET for the first interface (0) on the POS SPA installed in subslot 2 of a SIP installed in chassis slot 3:


POS3/2/0

SECTION

LOF = 0 LOS = 0 BIP(B1) = 0

LINE

AIS = 0 RDI = 0 FEBE = 0 BIP(B2) = 0

PATH

AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 0

PLM = 0 UNEQ = 0 TIM = 0 TIU = 0



Active Alarms: None


Framing: SONET

APS

COAPS = 0 PSBF = 0


Rx(K1/K2): 00/00 Tx(K1/K2): 00/00

Rx Synchronization Status S1 = 00

S1S0 = 00, C2 = CF


CLOCK RECOVERY

RDOOL = 0


PATH TRACE BUFFER: STABLE

Remote hostname : sip-sw-7600-2



Remote Rx(K1/K2): 00/00 Tx(K1/K2): 00/00



Clock source: internal

15-6


Release 12.0(33)S, OL-8832-01, Rev. C9



Modifying the Keepalive Interval

When the keepalive feature is enabled, a keepalive packet is sent at the specified time interval to keep the interface active. The keepalive interval must be configured to be the same on both ends of the POS link.

To modify the keepalive interval, use the following command in interface configuration mode:

Command Purpose

Router(config-if)# keepalive [ period [ retries ]] Specifies the frequency at which the Cisco IOS software sends messages to the other end of the link, to ensure that a network interface is alive, where:

• period— Specifies the time interval in seconds for sending keepalive packets. The default is 10 seconds.

• retries— Specifies the number of times that the device will continue to send keepalive packets without response before bringing the interface down. The default is 5 retries.

To disable keepalive packets, use the no form of this command.

Verifying the Keepalive Interval

To verify the keepalive interval, use the show interfaces pos privileged EXEC command and observe the value shown in the “Keepalive” field.

The following example shows that keepalive is enabled for interface port 0 on the POS SPA installed in the SIP that is located in slot 2 of the Cisco 12000 series router:

.

.

.



Internet address is 10.1.1.1.2

MTU 9216 bytes, BW 622000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255

Keepalive set (10 sec)

Modifying the CRC Size

CRC is an error-checking technique that uses a calculated numeric value to detect errors in transmitted data. The CRC size indicates the length in bits of the FCS.


Release 12.0(33)S, OL-8832-01, Rev. C9


15-7



To modify the CRC size, use the following command in interface configuration mode:

Command

Router(config-if)# crc [ 16 | 32 ]

Purpose

(As Required) Specifies the length of the cyclic redundancy check (CRC), where:

• 16 — Specifies a 16-bit length CRC. This is the default.

32 —Specifies a 32-bit length CRC.

•


To return to the default CRC size, use the no form of the command.

Verifying the CRC Size

To verify the CRC size, use the show interfaces pos privileged EXEC command and observe the value shown in the “CRC” field.

The following example shows that the CRC size is 16 for interface port 0 on the POS SPA installed in the SIP that is located in slot 2 of the Cisco 12000 series router:

.

.

.



Internet address is 10.1.1.2.1

MTU 9216 bytes, BW 622000 Kbit, DLY 100 usec reliability 255/255, txload 1/255, rxload

1/255

Encapsulation HDLC, crc 16 , loopback not set

Modifying the Clock Source

A clock source of internal specifies that the interface clocks its transmitted data from its internal clock.

A clock source of line specifies that the interface clocks its transmitted data from a clock recovered from the line’s receive data stream.

For information about the recommended clock source settings for POS router interfaces, refer to

Configuring Clock Settings on POS Router Interfaces at the following URL: http://www.cisco.com/en/US/tech/tk482/tk607/technologies_tech_note09186a0080094bb9.shtml

To modify the clock source, use the following command in interface configuration mode:

Command Purpose

Router(config-if)# clock source { line | internal } Specifies the clock source for the POS link, where:

•

• line — The link uses the recovered clock from the line. This is the default.

internal —The link uses the internal clock source.

15-8


Release 12.0(33)S, OL-8832-01, Rev. C9



To return to the default clock source, use the no form of this command.

Verifying the Clock Source

To verify the clock source, use the show controllers pos privileged EXEC command and observe the value shown in the “Clock source” field.

The following example shows that the clock source is internal for interface port 0 on the POS SPA installed in subslot 0 of the SIP that is located in slot 2 of the Cisco 12000 series router:


POS2/0/0

SECTION

LOF = 0 LOS = 1 BIP(B1) = 7

LINE

AIS = 0 RDI = 1 FEBE = 20 BIP(B2) = 9

PATH

AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 5




Active Alarms: None

.

.

Alarm reporting enabled for: SF SLOS SLOF B1-TCA LAIS LRDI B2-TCA PAIS PLOP PRDI PUNEQ

B3-TCA RDOOL

APS

COAPS = 2 PSBF = 0


Rx(K1/K2): 00/00 Tx(K1/K2): 00/00


S1S0 = 02, C2 = CF

CLOCK RECOVERY

RDOOL = 0



Remote hostname : RouterTester. Port 102/1

Remote interface:

Remote IP addr :

Remote Rx(K1/K2): / Tx(K1/K2): /



Clock source: internal

.

Modifying SONET Payload Scrambling

SONET payload scrambling applies a self-synchronous scrambler (x43+1) to the Synchronous Payload

Envelope (SPE) of the interface to ensure sufficient bit transition density.

The default configuration is SONET payload scrambling disabled.

SONET payload scrambling must be configured to be the same on both ends of the POS link.

Release 12.0(33)S, OL-8832-01, Rev. C9


15-9



To modify SONET payload scrambling, use the following command in interface configuration mode:

Command

Router(config-if)# pos scramble-atm

Purpose

Enables SONET payload scrambling.

To disable SONET payload scrambling, use the no form of this command.

Verifying SONET Payload Scrambling

To verify SONET payload scrambling, use the show interfaces pos privileged EXEC command and observe the value shown in the “Scramble” field.

The following example shows that SONET payload scrambling is disabled for interface port 0 on the

POS SPA installed in subslot 0 of the SIP that is located in slot 2 of the Cisco 12000 series router:

.

.




MTU 9216 bytes, BW 622000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255


Keepalive not set

Scramble disabled

.

Configuring the Encapsulation Type

By default, the POS interfaces support High-Level Data Link Control (HDLC) encapsulation. The encapsulation method can be specified as HDLC, Point-to-Point Protocol (PPP) or Frame Relay. The encapsulation type must be configured to be the same on both ends of the POS link.

Note In Cisco IOS Release 12.0(31)S, the POS SPAs do not support Frame Relay.

To modify the encapsulation method, use the following command in interface configuration mode:

Command


Purpose

Specifies the encapsulation method used by the interface, where:

• encapsulation-type— Can be HDLC, PPP, or

Frame Relay. The default is HDLC.

Verifying the Encapsulation Type

To verify the encapsulation type, use the show interfaces pos privileged EXEC command and observe the value shown in the “Encapsulation” field.

The following example shows the encapsulation type is HDLC for port 0 on the POS SPA installed in subslot 0 of the SIP that is located in slot 2 of the Cisco 12000 series router:

15-10


Release 12.0(33)S, OL-8832-01, Rev. C9



.

.







Keepalive not set

Scramble disabled

.

Configuring APS

Automatic protection switching (APS) allows switchover of POS circuits in the event of circuit failure and is often required when connecting SONET equipment to telco equipment. APS refers to the mechanism of using a “protect” POS interface in the SONET network as the backup for a “working” POS interface. When the working interface fails, the protect interface quickly assumes its traffic load.

Depending on the configuration, the two circuits may be terminated in the same router, or in different routers.

For more information about APS, refer to A Brief Overview of Packet Over SONET APS at the following

URL: http://www.cisco.com/en/US/tech/tk482/tk607/technologies_tech_note09186a0080093eb5.shtml

To configure the working POS interface, use the following command in interface configuration mode:

Command

Router(config-if)# aps working circuit-number

Purpose

Configures a POS interface as a working APS interface, where:

• circuit-number— Specifies the circuit number associated with this working interface.

To remove the POS interface as a working interface, use the no form of this command.

To configure the protect POS interface, use the following command in interface configuration mode:

Command

Router(config-if)# aps protect circuit-number ip-address

Purpose

Configures a POS interface as a protect APS interface, where:

• circuit-number— Specifies the number of the circuit to enable as a protect interface.

• ip-address— Specifies the IP address of the router that has the working POS interface.

To remove the POS interface as a protect interface, use the no form of this command.

Release 12.0(33)S, OL-8832-01, Rev. C9


15-11



Verifying the APS Configuration

To verify the APS configuration or to determine if a switchover has occurred, use the show aps command.

The following is an example of a router configured with a working interface. In this example, POS interface 0/0/0 is configured as a working interface in group 1, and the interface is selected (that is, active).

Router# show aps

POS0/0/0 working group 1 channel 1 Enabled Selected

The following is an example of a router configured with a protect interface. In this example, POS interface 2/1/1 is configured as a protect interface in group 1. The output also shows that the working channel is located on the router with the IP address 10.0.0.1 and that the interface currently selected is enabled.


POS2/1/1 APS Group 1: protect channel 0 (inactive)

Working channel 1 at 10.0.0.1 (Enabled)

SONET framing; SONET APS signalling by default

.

.

Remote APS configuration: (null)

.

Configuring POS Alarm Trigger Delays

A trigger is an alarm that, when activated, causes the line protocol to go down. The POS alarm trigger delay helps to ensure uptime of a POS interface by preventing intermittent problems from disabling the line protocol. The POS alarm trigger delay feature delays the setting of the line protocol to down when trigger alarms are received. If the trigger alarm was sent because of an intermittent problem, the POS alarm trigger delay can prevent the line protocol from going down when the line protocol is functional.

Line-Level and Section-Level Triggers

The pos delay triggers line command is used for POS router interfaces connected to internally-protected

Dense Wavelength Division Multiplexing (DWDM) systems. This command is invalid for interfaces that are configured as working or protect APS. Normally a few microseconds of line- or section-level alarms brings down the link until the alarm has been clear for ten seconds. If you configure holdoff, the link-down trigger is delayed for 100 milliseconds. If the alarm stays up for more than 100 milliseconds, the link is brought down. If the alarm clears before 100 milliseconds, the link remains up.

The following line- and section-level alarms are triggers, by default, for the line protocol to go down:

• Line alarm indication signal (LAIS)

•

•

Section loss of signal (SLOS)

Section loss of frame (SLOF)

You can issue the pos delay triggers line command to delay a down trigger of the line protocol on the interface. You can set the delay from 50 to 10000 milliseconds. The default delay is 100 milliseconds.

15-12


Release 12.0(33)S, OL-8832-01, Rev. C9



To configure POS line- or section-level triggers, use the following commands beginning in interface configuration mode:

Step 1

Step 2

Step 3

Command

Router(config-if)# pos delay triggers line ms

Purpose

Specifies a delay for setting the line protocol to down when a line-level trigger alarm is received, where:

•

• ms —Specifies the delay in milliseconds. The default delay is

100 milliseconds.

Router(config-if)# pos threshold

{ b1-tca | b2-tca | b3-tca | sd-ber | sf-ber } rate

Configures the POS bit error rate (BER) threshold values of the specified alarms, where:

• b1-tca rate— Specifies the B1 BER threshold crossing alarm.

The default is 6.

b2-tca rate— Specifies the B2 BER threshold crossing alarm.

The default is 6.

Router(config-if)# pos ais-shut

•

• b3-tca rate— Specifies the B3 BER threshold crossing alarm.

The default is 6.

sd-ber rate— Specifies the signal degrade BER threshold.

The default is 6.

•

• sf-ber rate— Specifies the signal failure BER threshold. The default is 3.

rate —Specifies the bit error rate from 3 to 9 (10e-n). The default varies by the type of threshold that you configure.

Sends a line alarm indication signal (AIS-L) to the other end of the link after a shutdown command has been issued to the specified POS interface. AIS-L is also known as LAIS when alarm-related output is generated using the show controllers pos command.

By default, the AIS-L is not sent to the other end of the link.

Stops transmitting the AIS-L by issuing either the no shutdown or the no pos ais-shut commands.

To disable alarm trigger delays, use the no form of the pos delay triggers line command.

To determine which alarms are reported on the POS interface, and to display the BER thresholds, use the show controllers pos command.

Path-Level Triggers

You can issue the pos delay triggers path command to configure various path alarms as triggers and to specify an activation delay between 50 and 10000 milliseconds. The default delay value is 100 milliseconds. The following path alarms are not triggers by default. You can configure these path alarms as triggers and also specify a delay:

• Path alarm indication signal (PAIS)

•

•

Path remote defect indication (PRDI)

Path loss of pointer (PLOP)

Release 12.0(33)S, OL-8832-01, Rev. C9


15-13



•

•

•

• sd-ber (signal degrade [SD] bit error rate [BER]) sf-ber (signal failure [SF] BER) b1-tca (B1 BER threshold crossing alarm [TCA]) b2-tca (B2 BER TCA)

• b3-tca (B3 BER TCA)

The pos delay triggers path command can also bring down the line protocol when the higher of the B2 and B3 error rates is compared with the signal failure (SF) threshold. If the SF threshold is crossed, the line protocol of the interface goes down.

To configure POS path-level triggers, use the following command in interface configuration mode:

Command Purpose

Router(config-if)# pos delay triggers path ms Specifies that path-level alarms should act as triggers and specifies a delay for setting the line protocol to down when a path-level trigger alarm is received, where:

• ms —Specifies the delay in milliseconds. The default delay is 100 milliseconds.

To disable path-level triggers, use the no form of this command.

Verifying POS Alarm Trigger Delays

To verify POS alarm trigger delays, use the show controllers pos privileged EXEC command and observe the values shown in the “Line alarm trigger delay” and “Path alarm trigger delay” fields.

The following example shows the POS alarm trigger delays for interface port 0 on the POS SPA installed in the SIP that is located in slot 2 of the Cisco 12000 series router:

.

.

Router# show controllers pos 2/0/0 details

POS2/0/0

SECTION

LOF = 0 LOS = 1 BIP(B1) = 5

LINE

AIS = 0 RDI = 1 FEBE = 5790 BIP(B2) = 945

PATH

AIS = 0 RDI = 0 FEBE = 0 BIP(B3) = 5




Active Alarms: None


Line alarm trigger delay = 100 ms

Path alarm trigger delay = 100 ms

.

15-14


Release 12.0(33)S, OL-8832-01, Rev. C9



Configuring SDCC

Before any management traffic can traverse the section data communication channel (SDCC) links embedded in the POS SPA overhead, the SDCC interfaces must be configured and activated.

Note SDCC is not supported by the 4-Port and 8-Port OC-3c/STM-1 POS SPA or 2-Port, 4-Port, and 8-Port

OC-3c/STM-1 and OC-12c/STM-4 POS SPAs.

SDCC Configuration Guidelines

When configuring SDCC on a POS SPA, consider the following guidelines:

• SDCC must be enabled on the main POS interfaces.

• SDCC supports only HDLC and PPP encapsulation, not Frame Relay.

SDCC Configuration Task

To configure the POS SPAs for SDCC, complete the following steps:

Step 1

Step 2

Step 3

Command Purpose

Router(config)# interface sdcc slot / subslot / port Specifies the SDCC interface and enters interface configuration mode, where:

Router(config-if)#

[ secondary ] ip address ip-address mask

• slot / subslot / port —Specifies the location of the interface. See the “Specifying the

Interface Address on a SPA” section on page 15-3 .



•


mask —Specifies the mask for the associated

IP subnet.

• secondary —(Optional) Specifies that the configured address is a secondary IP address.



Verifying the SDCC Interface Configuration

To verify the SDCC interface, use the show interfaces sdcc privileged EXEC command and observe the value shown in the “Hardware is” field.

The following example shows the SDCC interface port 1 on the POS SPA installed in subslot 0 of the

SIP that is located in slot 5 of the Cisco 12000 series router:

Router# show interfaces sdcc 5/0/1

SDCC5/0/1 is up, line protocol is up

Release 12.0(33)S, OL-8832-01, Rev. C9


15-15



Hardware is SDCC





Keepalive not set

Last input 00:01:24, output never, output hang never

Last clearing of ''show interface'' counters 00:01:30














Configuring Dynamic Packet Transport Features

This section provides information about the Dynamic Packet Transport (DPT) features supported by the

SIPs and SPAs on the Cisco 12000 series router. It includes SIP- and SPA-specific configuration guidelines and restrictions for these features. Many of the features supported by the SIPs and SPAs work the same way as for other DPT products on the Cisco 12000 series router. However, be sure to apply the product-specific configuration guidelines in this document prior to using the documentation links referenced for additional configuration information about these features on the Cisco 12000 series router.

Configuring the Spatial Reuse Protocol

Spatial Reuse Protocol (SRP) is a Cisco-developed MAC-layer protocol, used in conjunction with

Cisco’s Dynamic Packet Transport (DPT) product family. SRP is implemented using fiber media on bidirectional, dual counter-rotating ring topologies in which multiple nodes can transmit simultaneously without any tokens required for access to the network.

Spatial reuse is a concept used in rings to increase the overall aggregate bandwidth of the ring. The bandwidth gain is possible because unicast traffic is only passed along ring spans between source and destination nodes, rather than across the entire ring, as in earlier ring-based protocols such as Token Ring and FDDI. SRP uses destination stripping of packets, while older technologies use source stripping. With source stripping, packets must cross the entire ring until they are removed by the source. In older technologies, even if the source and destination nodes are next to each other on the ring, packets continue to travel through the entire ring until they return to the source to be removed, which uses unnecessary bandwidth. SRP provides more efficient use of available bandwidth by having the destination node remove the packet after it is read.

SRP provides some of the following services:

• Topology discovery—Updates network topology maps for each SRP node. Each node performs topology discovery by sending out topology discovery packets, periodically or as needed, on both rings. The topology packet received on the outer ring is usually processed. This packet is a point-to-point packet which hops around the ring from node to node. Each node appends its MAC

15-16


Release 12.0(33)S, OL-8832-01, Rev. C9



•

•

•

•

• address, updates the length field and sends it to the next hop on the ring. When the node that generated the topology discovery packet receives it back, it reads the information in the packet and updates its topology map accordingly.

Intelligent Protection Switching (IPS)—Detects and recovers from fiber or equipment failures and signal degradation. When a failure is detected, traffic going to and from the failure direction is wrapped, or looped back, to go in the opposite direction on the other ring. The wrap takes place on nodes adjacent to the failure, under control of the IPS protocol.

Single Ring Recovery (SRR)—Provides detection of multiple faults on the same ring and corrective action by removal of all wraps use of the error-free ring for packet transmission.

Destination stripping of unicast packets

Broadcast and multicast packet transmission

SRP Fairness Algorithm for flow control

SRP Configuration Guidelines

When configuring SRP for SIPs and SPAs on the Cisco 12000 series router, consider the following guidelines:

• For information about SIPs and SPAs that support SRP, refer to the “POS Feature Compatibility and

Restrictions by SIP and SPA Combination” table in Chapter 14, “Overview of the POS SPAs.”

•

•

The SRP mate either can be on the same SIP or on an adjacent SIP according to certain installation guidelines for each SIP and SPA. For more information, refer to the “SRP Mate Configuration

Guidelines” section on page 15-17 .

The default mode for all SPA interfaces is POS. To change between POS and SRP modes, you must shut down the SPA interface.

•

•

•

•

•

Whenever you change modes on a POS SPA, the SPA automatically reloads.

To change the SRP mate configuration, you must shut down the SPA interfaces.

You cannot configure subinterfaces on an SRP interface.

To distinguish between the two rings, one is referred to as the “inner” ring and the other as the

“outer” ring. SRP operates by sending data packets in one direction (downstream) and sending the corresponding control packets in the opposite direction (upstream) on the other fiber. An SRP node uses SRP side A to receive (RX) outer ring data and transmit (TX) inner ring data. The node uses

SRP side B to receive (RX) inner ring data and transmit (TX) outer ring data. Side A on one node connects to Side B on an adjacent SRP node.

For configuration of SRP on POS SPAs in multiple slots on the same SIP, the lower-numbered slot and subslot combination hosts the SRP interface and becomes “Side A” of the SRP interface. The slot number of the side-A interface must be lower than the slot location of the SRP mate (side B) interface.

To configure SRP options, you must specify the slot and subslot location of the side-A interface, in addition to a port number.

SRP Mate Configuration Guidelines

The following mating rules apply for SRP on the SIPs and SPAs on the Cisco 12000 series router:

• For the 2-Port OC-48c/STM-16 POS SPA, the following guidelines apply:

– You cannot mate multiple 2-Port OC-48c/STM-16 POS SPAs.

Release 12.0(33)S, OL-8832-01, Rev. C9


15-17



•

•

•

– For a single 2-Port OC-48c/STM-16 POS SPA, mating is done internally between the two

SONET ports, and no mate cabling is required.

The Cisco 12000 SIP-600 and Cisco 12000 SIP-601 can support a maximum of two 1-Port

OC-192c/STM-64 POS/RPR XFP SPAs.

When mating two 1-Port OC-192c/STM-64 POS/RPR XFP SPAs for SRP within the same

Cisco 12000 SIP-600 or Cisco 12000 SIP-601, the SPAs can only be installed in subslot 0 and subslot 1.

If you configure SRP mating between two SPAs that are inserted into adjacent SIPs, each SPA must be inserted into the same subslot on both SIPs.

For example, if the 1-Port OC-192c/STM-64 POS/RPR SPA or 1-Port OC-192c/STM-64 POS/RPR

VSR Optics SPA is installed in subslot 1 on the first SIP, then the 1-Port OC-192c/STM-64

POS/RPR SPA or 1-Port OC-192c/STM-64 POS/RPR VSR Optics SPA mate also must be installed in subslot 1 on the adjacent SIP.

SRP Configuration Tasks

•

•

•

The following tasks describe how to configure SRP:

Enabling SRP Mode, page 15-18 (required)

Configuring SRP Options, page 15-19 (optional)

Changing from SRP Mode to POS Mode, page 15-20 (optional)

Enabling SRP Mode

When you install a POS/RPR SPA, POS mode is automatically enabled on all of the SPA interfaces.

Therefore, you must explicitly enable SRP on the SPA.

SRP Mode Configuration Guidelines

When enabling SRP mode, consider the following guidelines:

•

•

For proper configuration of SRP for SPAs installed in the same SIP, you should enable SRP using the hw-module subslot srp command on the POS SPA that is installed in the lower-numbered slot and subslot combination. This SPA is considered the host SRP interface.

You only need to configure the hw-module subslot srp command on the host SRP interface—not on the mate SRP interface.

•

•

•

•

•

The host SRP interface becomes “Side A” of the SRP interface. When configuring SPAs that are installed in different slots on the same SIP for SRP, the slot number of the side-A interface must be lower than the slot location of the SRP mate (side B) interface. Also, you must specify the side-A interface location for configuration of any SRP options.

The SIP reads the information it receives from the hardware cable mating to validate the mate cable connectivity with your software configuration.

You must shut down the POS interface before enabling SRP.

When you change the SPA mode, the SPA automatically reloads.

The entire SPA operates either in POS mode or SRP mode—you cannot have some interfaces configured for POS mode, and other interfaces configured for SRP mode.

15-18


Release 12.0(33)S, OL-8832-01, Rev. C9



To enable SRP on the host SRP interface, use the following commands beginning in global configuration mode:

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Step 7

Command

Router(config)#

Router(config)# srp { mate slot / interface pos

Router(config-if)#

Router(config-if)#

shutdown exit subslot } slot / subslot hw-module subslot slot /

/ port subslot

Purpose

Specifies the POS interface and enters interface configuration mode, where:



Disables the interface and puts it into an administratively shut down state.

Exits interface configuration mode and returns to global configuration mode.

Changes the POS SPA from POS mode to SRP mode for all interfaces on the POS SPA, where:

• slot / subslot— Specifies the location of the

SPA.

• mate slot / subslot— (Not required for the

2-Port OC-48c/STM-16 POS SPA) Specifies the location of the SPA that is the SRP mate.

Router(config-if)# interface srp slot / subslot / port Configures the SPA interface as an SRP interface, where:

Router(config-if)#

[ secondary ]

Router(config-if)# ip address ip-address mask no shutdown

• slot / subslot / port —Specifies the location of the interface.



•

• mask —Specifies the mask for the associated

IP subnet.

secondary —(Optional) Specifies that the configured address is a secondary IP address.



Configuring SRP Options

The POS SPAs support all of the SRP options available for other DPT products on the Cisco 12000 series router. You only configure SRP options on the SRP host interface, or side-A interface. For more information about the SRP host interface, see the “SRP Configuration Guidelines” section on page 15-17 .

Release 12.0(33)S, OL-8832-01, Rev. C9


15-19



For more information about configuring SRP options, refer to the Spatial Reuse Protocol Feature Guide , located at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/srpapsgs.ht

m

To enable SRP options on the host SRP interface, use the following commands beginning in global configuration mode:

Step 1

Step 2

Command Purpose

Router(config-if)# interface srp slot / subslot / port Selects the side-A or host SPA interface, where:

Router(config-if)# srp command



Configures an SRP option, where command represents one of the srp command syntax options.

For information about srp commands and their configuration, refer to the Spatial Reuse Protocol

Feature Guide , located at the following URL: http://www.cisco.com/univercd/cc/td/doc/product

/software/ios120/120newft/120limit/120s/srpapsg s.htm

Changing from SRP Mode to POS Mode

If a POS SPA has been configured for SRP mode using the hw-module subslot srp command, you can return the POS SPA to POS mode using the no form of this command.

Caution When you change modes on a POS SPA, the SPA automatically reloads.

To change from SRP mode to POS mode on a POS SPA, use the following commands beginning in global configuration mode:

Step 1

Command

Router(config)# interface srp slot / subslot / port

Step 2 Router(config-if) shutdown

Purpose

Selects the SRP SPA interface and enters interface configuration mode, where:

• slot / subslot / port— Specifies the location of the interface. See the “Specifying the


Disables the interface and puts it into an administratively shut down state.

15-20


Release 12.0(33)S, OL-8832-01, Rev. C9



Step 3

Command


Step 4 Router(config)# no hw-module subslot slot / subslot srp

Purpose

Exits interface configuration mode and returns to global configuration mode.

Changes the POS SPA from SRP mode to POS mode for all interfaces on the POS SPA, where:

• slot / subslot— Specifies the location of the

SPA. See the “Specifying the Interface


Configuring Single Ring Recovery

The Single Ring Recovery (SRR) protocol is an extension to SRP supported by the POS/RPR SPAs on the Cisco 12000 series router. For information about how to configure and use the SRR protocol, refer to the Single Ring Recovery Protocol publication at http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s16/srr.

htm .

Verifying the SRP Configuration

To display information about the configuration for an SRP interface, use the show interfaces srp command as shown in the following example:

Router# show interfaces srp 1/0

SRP1/0 is up, line protocol is up

Hardware is SRP over SONET, address is 0012.3456.0001 (bia 0008.200e.5954)



Encapsulation SRP2,

Side A: loopback not set

Side B: loopback not set

3 nodes on the ring MAC passthrough not set

Side A: not wrapped IPS local: IDLE IPS remote: IDLE

Side B: not wrapped IPS local: IDLE IPS remote: IDLE





Side A: 5 minutes output rate 0 bits/sec, 0 packets/sec

5 minutes input rate 0 bits/sec, 0 packets/sec

Side B: 5 minutes output rate 0 bits/sec, 0 packets/sec

5 minutes input rate 0 bits/sec, 0 packets/sec







Side A received errors:

0 input errors, 0 CRC, 0 ignored,

0 framer runts, 0 framer giants, 0 framer aborts,

0 mac runts, 0 mac giants, 0 mac aborts

Side B received errors:

0 input errors, 0 CRC, 0 ignored,

0 framer runts, 0 framer giants, 0 framer aborts,

0 mac runts, 0 mac giants, 0 mac aborts

Release 12.0(33)S, OL-8832-01, Rev. C9


15-21



For more information about monitoring and maintaining your SRP configuration and ring, refer to the

Spatial Reuse Protocol Feature Guide , located at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/srpapsgs.ht

m



Command


Purpose





Shutting Down and Restarting an Interface on a SPA

You can shut down and restart any of the interface ports on a SPA independently of each other. Shutting down an interface stops traffic and then enters the interface into an “administratively down” state.

If you are preparing for an OIR of a SPA, it is not necessary to independently shut down each of the interfaces prior to deactivation of the SPA. You do not need to independently restart any interfaces on a

SPA after OIR of a SPA or SIP.

To shut down an interface on a SPA, use the following command in interface configuration mode:

Command


Purpose

Disables an interface.

To restart an interface on a SPA, use the following command in interface configuration mode:

Command


Purpose

Restarts a disabled interface.


Besides using the show running-configuration command to display your Cisco 12000 series router configuration settings, you can use the show interfaces pos and show controllers pos commands to get detailed information on a per-port basis for your POS SPAs.

15-22


Release 12.0(33)S, OL-8832-01, Rev. C9




To find detailed interface information on a per-port basis for the POS SPAs, use the show interfaces pos command.

The following example provides sample output for interface port 0 (the first port) on the SPA located in the subslot 0 of the SIP that is installed in slot 3 of the Cisco 12000 series router:








Scramble disabled

LMI enq sent 18, LMI stat recvd 0, LMI upd recvd 0

LMI enq recvd 1473, LMI stat sent 1473, LMI upd sent 0, DCE LMI up

LMI DLCI 1023 LMI type is CISCO frame relay DCE

FR SVC disabled, LAPF state down












0 parity





3 carrier transitions.

Monitoring Per-Port Interface Statistics

To find detailed alarm and error information on a per-port basis for the POS SPAs, use the show controllers pos command. For a description of the command output, see Chapter 19, “SIP and SPA

Command Reference” .

The following is sample output from the show controllers pos command on a Cisco 12000 series router for POS interface 4/3/0 (which is the interface for port 0 of the SPA in subslot 3 of the SIP in chassis slot 4):


POS4/3/0

SECTION

LOF = 0 LOS = 0 BIP(B1) = 65535

LINE

AIS = 0 RDI = 0 FEBE = 65535 BIP(B2) = 16777215

PATH

AIS = 0 RDI = 0 FEBE = 65535 BIP(B3) = 65535




Active Alarms: None

Release 12.0(33)S, OL-8832-01, Rev. C9


15-23




Framing: SONET

APS

COAPS = 1 PSBF = 0


Rx(K1/K2): 00/00 Tx(K1/K2): 00/00


S1S0 = 00, C2 = CF


CLOCK RECOVERY

RDOOL = 0



Remote hostname : woodson



Remote Rx(K1/K2): 00/00 Tx(K1/K2): 00/00





This section includes the following examples for configuring a POS SPA installed in a Cisco 12000 series router:

• Basic Interface Configuration Example, page 15-25

•

•

•

•

•

MTU Configuration Example, page 15-25

POS Framing Configuration Example, page 15-26

Keepalive Configuration Example, page 15-26

CRC Configuration Example, page 15-26

•

•

•

•

Clock Source Configuration Example, page 15-27

SONET Payload Scrambling Configuration Example, page 15-27


APS Configuration Example, page 15-27

•

•

POS Alarm Trigger Delays Configuration Example, page 15-29

SDCC Configuration Example, page 15-29

SRP Configuration Example, page 15-29

15-24


Release 12.0(33)S, OL-8832-01, Rev. C9



Basic Interface Configuration Example

The following example shows how to enter global configuration mode to enter global configuration mode to specify the interface that you want to configure, configure an IP address for the interface, enable the interface, and save the configuration. This example configures interface port 0 (the first port) of the

SPA located in subslot 0 of the SIP that is installed in slot 2 of the Cisco 12000 series router:


!


!


!

Router(config)# interface pos 2/0/0

!


!


!

! Enable the interface

!

Router(config-if)# no shutdown

!


!



MTU Configuration Example

The following example sets the MTU to 4470 bytes on interface port 1 (the second port) of the SPA located in the bottom subslot (1) of the SIP that is installed in slot 2 of the Cisco 12000 series router:


!


!


!


!

! Configure MTU

!

Router(config-if)# mtu 4470

Release 12.0(33)S, OL-8832-01, Rev. C9


15-25



POS Framing Configuration Example

The following example shows how to change from the default POS framing of SONET to SDH:


!


!


!


! (The default pos framing is sonet)

!

!Modify the framing type

!

Router(config-if)# pos framing sdh

Keepalive Configuration Example

The following example shows how to change from the default keepalive period of 10 seconds to 20 seconds:


!


!


!


!

! Configure keepalive 20

!

Router(config-if)# keepalive 20

CRC Configuration Example

The following example shows how to change the CRC size from 32 bits to the default 16 bits for POS

SPAs:


!


!


!


!

! Configure crc 16

!

Router(config-if)# crc 16

15-26


Release 12.0(33)S, OL-8832-01, Rev. C9



Clock Source Configuration Example

The following example shows how to change from the default clock source of internal to line:


!


!


!


!

! Configure the clock source

!

Router(config-if)# clock source line

SONET Payload Scrambling Configuration Example

The following example shows how to change from a default SONET payload scrambling of disabled to enabled:


!


!


!


!

! Configure the SONET payload scrambling

!

Router(config-if)# pos scramble-atm


The following example shows how to change from the default encapsulation method of HDLC to PPP:


!




!

! Configure ppp

!


APS Configuration Example

The following example shows the configuration of APS on router A and router B, and how to configure more than one protect or working interface on a router by using the aps group command. See

Figure 15-1 .

Release 12.0(33)S, OL-8832-01, Rev. C9


15-27



Figure 15-1 Basic APS Configuration

POS 2/0/0

Working interface

Router A

E 0/0

SONET network equipment

Router B

E 0/0

POS 3/0/0

Protect interface

Add Drop Multiplexer (ADM)

In this example, router A is configured with the working interface and router B is configured with the protect interface. If the working interface on router A becomes unavailable, the connection will automatically switch over to the protect interface on router B. The loopback interface is used as the interconnect. The aps group command is used even when a single protect group is configured.

The following example shows how to configure Router A for this scenario:


!


!

! Configure a loopback interface as the protect interconnect path

!

Router(config)# interface loopback 1


! Configure the POS interface address for the APS working interface

!


!

! Configure the POS interface IP address and other interface parameters

!


Router(config-if)# no ip directed-broadcast

Router(config-if)# no keepalive


!

! Configure the APS group number by which to associate APS interfaces

!

Router(config-if)# aps group 1

!

! Configure a circuit number for the APS working interface

!

Router(config-if)# aps working 1

The following example shows how to configure Router B for this scenario:


!


!

! Configure the POS interface address for the APS protect interface

!


!

! Configure the POS interface IP address and other interface parameters

!

15-28


Release 12.0(33)S, OL-8832-01, Rev. C9




Router(config-if)# no ip directed-broadcast

Router(config-if)# no keepalive


!

! Configure the APS group number by which to associate APS interfaces

!

Router(config-if)# aps group 1

!

! Configure a circuit number for the protect interface and an IP address for the router

! that has the APS working interface. In this case, the loopback interface address is

! used.

!

Router(config-if)# aps protect 1 10.10.10.10

POS Alarm Trigger Delays Configuration Example

The following example shows how to change POS line-level and path-level alarm trigger delays from the default of 100 milliseconds to 200 milliseconds:


!


!


!


!

Router(config-if)# pos delay triggers line 200

Router(config-if)# pos delay triggers path 200

SDCC Configuration Example

The following example shows how to configure an SDCC interface:

!

! Specify the SDCC interface

!

Router(config)# interface sdcc 5/0/0

!

! Specify the IP address

!

Router(config-if)# ip address 10.14.14.14. 255.0.0.0

!

! Enable the interface

!

Router(config-if)# no shutdown

SRP Configuration Example

The following example shows how to enable SRP on a POS/RPR SPA:

! Select the POS interface

!

Router(config)# interface pos 1/0/0

!

! Shut down the POS interface

!

Release 12.0(33)S, OL-8832-01, Rev. C9


15-29




!

! Enable SRP on the host SRP SPA with optional mate CLI

! Note: When the SRP SPAs are installed in different slots on the same SIP, the SPA in the

! lower-numbered slot and subslot location is the side-A or host SPA.

! In this example, the SPA installed in slot 1 and subslot 0 of the SIP is the side-A SPA.

!


Router(config))# hw-module subslot 1/0 srp mate 1/1

!

! Configure an SRP interface

!

Router(config)# interface srp 1/0/0

Router(config-if)# mac-address 0003.0003.0003


Router(config-if)# no ip directed-broadcast

Router(config-if)# ipv6 address 10:4:4::1/64

Router(config-if)# service-policy output parent

15-30


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

16

Command Summary for the POS SPAs

Table 16-1

provides an alphabetical list of some of the related commands to configure, monitor, and maintain the POS SPAs. For more information about the commands, see


Command Reference”

.

If the command is not located in this guide refer to the Cisco IOS Release 12.0 command reference and master index publications.

Command Summary for POS SPAs Table 16-1

Command Purpose

Router(config-if)# aps protect circuit-number ip-address Configures a Packet over SONET (POS) interface as a protect automatic protection switching (APS) interface.

Router(config-if)# aps working circuit-number

Router(config-if)#

Router(config-if)# crc [ 16 | 32 ]


Router(config)# Router(config)# hw-module subslot slot / subslot srp { mate slot / subslot }

Router(config)# clock source interface pos

{ line

slot /

| internal subslot / port

Router(config)# interface sdcc slot / subslot / port

Router(config)# interface srp slot / subslot / port

}

Router(config-if)# ip address ip-address mask [ secondary ]

Router(config-if)# keepalive [ period [ retries ]]

Configures a Packet over SONET (POS) interface as a working

APS interface.

Specifies the clock source for the POS link.

Specifies the length of the cyclic redundancy check (CRC).

Specifies the encapsulation method used by the interface.

Changes the POS SPA from POS mode to SRP mode for all interfaces on the POS SPA. The mate keyword is not required for the 2-Port OC-48c/STM-16 POS SPA.

Specifies a POS interface.

Specifies an SDCC interface.

Specifies an SRP interface.

Specifies a primary or secondary IP address for an interface.

Router(config-if)#

Router(config-if)#

Router(config-if)# mtu bytes no shutdown pos ais-shut

Specifies the frequency at which the Cisco IOS software sends messages to the other end of the link, to ensure that a network interface is alive.

Configures the maximum transmission unit (or packet size) for an interface.

Enables an interface.

Sends a line alarm indication signal (AIS-L) to the other end of the link after a shutdown command has been issued to the specified POS interface.

Release 12.0(33)S, OL-8832-01, Rev. C9


16-1

Chapter 16 Command Summary for the POS SPAs

Table 16-1 Command Summary for POS SPAs (continued)

Command Purpose

Router(config-if)# pos delay triggers line ms Specifies a delay for setting the line protocol to down when a line-level trigger alarm is received.

Router(config-if)# pos delay triggers path ms


Router# show controllers pos slot / subslot / port

Specifies that path-level alarms should act as triggers and specifies a delay for setting the line protocol to down when a path-level trigger alarm is received.

Specifies the POS framing type.

Router(config-if)# pos framing { sonet | sdh }

Router(config-if)# pos scramble-atm

Router(config-if)# [no] sdcc [enable | disable]

Enables SONET payload scrambling.

Router(config-if)# pos threshold { b1-tca | b2-tca | b3-tca

| sd-ber | sf-ber } rate

Configures the POS bit rate error (BER) threshold values of the specified alarms.

Enables the IP/Section Data Communications Channel (SDCC) interface.

Displays information about the current APS feature.

Router#

[ show controllers pos time-interval ] [ time-interval ]]

[ slot / port ] [ details | pm

Displays POS controllers information.

Displays the POS controllers information for each of the time-intervals specified between the starting and ending time-interval or for a single time-interval on a Cisco 12000

Series Router.

Router# show controllers pos [ slot / subslot / port [ /sub_int ]]

[ alarm | details | pm [ time-interval ] [ time-interval ]]

Router# show diags subslot summary ] slot / subslot [ details |

Displays the POS controllers information for each of the time-intervals specified between the starting and ending time-interval or for a single time-interval on a POS Shared Port

Adapter.

Displays hardware information for a SPA.

Router# show interfaces pos slot / subslot / port

Router# show interfaces sdcc slot / subslot / port

Displays configuration information and statistics for a POS interface.

Displays configuration information for a SDCC interface.

16-2


Release 12.0(33)S, OL-8832-01, Rev. C9

P A R T 5

Field-Programmable Devices

C H A P T E R

17

Upgrading Field-Programmable Devices

In general terms, field-programmable devices (FPDs) are hardware devices implemented on router cards that support separate upgrades. The term “FPD” has been introduced to collectively and generically describe any type of programmable hardware device on SPAs. FPDs were introduced on the Cisco 12000 series routers to support SPAs.

This chapter describes the information that you need to know to verify image versions and to perform

SPA FPD upgrades.


•

•

•

•

•


FPD Quick Upgrade, page 17-2

Overview of FPD Images and Packages, page 17-3

Upgrading FPD Images, page 17-3

•

•

Optional FPD Procedures, page 17-6

FPD Image Upgrade Examples, page 17-12

Troubleshooting Problems with FPD Image Upgrades, page 17-14

Release History

Table 17-1

provides the release and modification history for all FPD-related features on the Cisco 12000 series routers.

Table 17-1 FPD Release History


Cisco IOS Release

12.0(31)S

SPAs were released on Cisco 12000 series routers for the first time. FPD images were introduced to support these SPAs.

Release 12.0(33)S, OL-8832-01, Rev. C9


17-1

Chapter 17 Upgrading Field-Programmable Devices

FPD Quick Upgrade

FPD Quick Upgrade

This section provides information if you simply want to upgrade FPD for SPAs as quickly as possible.

These instructions are not always feasible for operating network environments and are not the only methods available for upgrading FPD. If these methods of upgrade are not suitable for your situation, see the various other sections of this document for other methods of upgrading FPD.

This section addresses the following topics:

•

•

FPD Quick Upgrade Before Upgrading your Cisco IOS Release (Recommended), page 17-2

FPD Quick Upgrade After Upgrading your Cisco IOS Release, page 17-2

FPD Quick Upgrade Before Upgrading your Cisco IOS Release (Recommended)

Step 1

Step 2

When getting your Cisco IOS image, download the FPD image package for the Cisco IOS release that you are upgrading to to any Flash disk on your router before booting the new version of Cisco IOS. The

FPD image package can be retrieved from the same site where you went to get your Cisco IOS image.

Do not change the name of the FPD image package.

Boot using the new version of Cisco IOS. When the new Cisco IOS boots, it by defaults searches for the

FPD image package in the router flash file systems and the FPD images will be updated automatically as part of the IOS boot process.

FPD Quick Upgrade After Upgrading your Cisco IOS Release

Step 1

Step 2

Step 3

An FPD upgrade is not always necessary after Cisco IOS is upgraded. If you have already upgraded your

Cisco IOS, enter the show hw-module all fpd command to see if all system FPDs are compatible. If the

FPDs are compatible, no further action is necessary. If at least one FPD needs an upgrade, proceed to

Step 2

.

Go to the cisco.com site where you downloaded your specific Cisco IOS software and locate the FPD image package, if you haven’t already.

Download this FPD image package to a Flash disk on your router. Do not change the name of the FPD image package.

Do not change any FPD-related settings on your system (if upgrade fpd auto or upgrade fpd path has been changed, change the settings back to the default settings using the no form of the command).

Reboot your Cisco IOS release software. When the new Cisco IOS boots, it by defaults searches for the

FPD image package in the Flash file systems and the FPD images will be updated automatically as part of the IOS boot process.

17-2


Release 12.0(33)S, OL-8832-01, Rev. C9


Overview of FPD Images and Packages

Overview of FPD Images and Packages

An FPD image package is used to upgrade FPD images. Whenever a Cisco IOS image is released that supports carrier cards and SPAs, a companion FPD image package is also released for that Cisco IOS software release. The FPD image package is available from Cisco.com and is accessible from the Cisco

Software Center page where you also go to download your Cisco IOS software image.

If you are running SPAs on your router and are upgrading your Cisco IOS image, you should download the FPD image package file before booting the router using the new Cisco IOS release. If the SPA requires an FPD upgrade and the Cisco IOS image is unable to locate an FPD image package, the system messages will indicate that the FPD image is incompatible and you will need to go to the Cisco Software

Center on Cisco.com to download the FPD image package for your Cisco IOS software release. An FPD incompatibility on a SPA disables all interfaces on that SPA until the incompatibility is addressed.

Note The FPD automatic upgrade feature only searches for the FPD image package file that is the same version number as the Cisco IOS release being used by the system. For example, if the Cisco IOS release being used is Cisco IOS Release 12.0(31)S, then the system will search for the FPD image package file that supports the specific Cisco IOS release (c12k-fpd-pkg.120-31.S.pkg). Therefore, ensure the FPD image package file on your system is compatible with your Cisco IOS release and do not change the name of the FPD image package file.

Upgrading FPD Images

This section documents some of the common scenarios where FPD image updates are necessary. It discusses the following scenarios:

•

Migrating to a Newer Cisco IOS Release, page 17-3

•

Upgrading FPD Images in a Production System, page 17-5

Migrating to a Newer Cisco IOS Release

This section discusses the following topics:

•

•

Upgrading FPD Images Before Booting the New Cisco IOS Release (Recommended), page 17-3

Upgrading FPD Images in a Production System, page 17-5

Upgrading FPD Images Before Booting the New Cisco IOS Release (Recommended)

If you are still running your old Cisco IOS Release but are preparing to load a newer version of Cisco

IOS, you can upgrade FPD for the new Cisco IOS Release using the following method:

•

Placing FPD Image Package on Flash Disk Before Upgrading IOS (Recommended), page 17-3

Placing FPD Image Package on Flash Disk Before Upgrading IOS (Recommended)

Placing the FPD image package for the IOS release that you are upgrading to before upgrading IOS is the recommended method for upgrading FPD because it is simple in addition to being fast. To perform this type of FPD upgrade, follow these steps:

Release 12.0(33)S, OL-8832-01, Rev. C9


17-3



Step 1 While still running the Cisco IOS release that will be upgraded, place the FPD image package for the new version of Cisco IOS onto one of your router’s Flash file systems. For instance, if you are running

Cisco IOS Release 12.0(31)S and are upgrading to Cisco IOS Release 12.0(32)S, place the FPD image package for Cisco IOS Release 12.0(32)S onto a Flash file system while still running Cisco IOS Release

12.0(31)S. The FPD image package for a specific IOS release can be located on cisco.com from the same area where you download that Cisco IOS software image. Your router and SPAs should continue to operate normally since this action will have no impact on the current FPDs.

Caution Do not change the filename of the FPD image package file. The Cisco IOS searches for the FPD image package file by filename, so the FPD image package file cannot be found if it has been renamed.

Step 2

Step 3

Reboot your router using the new upgraded Cisco IOS image. As part of the bootup process, the router will search for the FPD image package. Since the default settings for the FPD image package search are to check for the FPD image package for the specific Cisco IOS Release in a Flash file system, the FPD image package will be located during the bootup procedure and all FPDs that required upgrades will be upgraded.

When the router has booted, verify the upgrade was successful by entering the show hw-module all fpd command.

Upgrading FPD Images after Booting the New Cisco IOS Release

The following steps explain how to upgrade FPD images if you have already upgraded your Cisco IOS release but still need to upgrade your FPD images.

To perform an FPD upgrade after the new Cisco release has been booted, follow these steps:

Step 1

Step 2

Step 3

Step 4

If you are unsure if your FPD images for your SPAs are compatible, enter the show hw-module all fpd command to verify compatibility of all SPAs. If all of your SPAs are compatible, there is no reason to perform this upgrade.

If an FPD upgrade is necessary, place the FPD image package for the new version of Cisco IOS onto the router’s Flash Disk or on an accessible FTP or TFTP server. The FPD image package can be located on cisco.com from the same area where you downloaded your Cisco IOS software image.

Enter the upgrade hw-module subslot slot-number / subslot-number fpd file-url [force] command. The file-url command should direct users to the location of the FPD image package. For instance, if you had placed the FPD image package for Release 12.0(31)S on the TFTP server mytftpserver/myname/myfpdpkg, you would enter upgrade hw-module subslot slot-number / subslot-number fpd file tftp://mytftpserver/myname/myfpdpkg/c12k-fpd-pkg.120-31.S.pkg

to complete this step.

If multiple SPAs require upgrades, the different pieces of hardware will have to be updated individually.

Note the force option is used in this command. This option will force an FPD upgrade even if no FPD mismatch is detected. In instances where the upgrade hw-module command is entered, this option is almost never necessary and should only be entered if requested by a technical support representative.

Verify the upgrade was successful by entering the show hw-module all fpd command.

17-4


Release 12.0(33)S, OL-8832-01, Rev. C9



Upgrading FPD Images in a Production System

Adding a SPA to a production system presents the possibility that the SPA may contain versions of FPD images that are incompatible with the Cisco IOS release currently running the router. Additionally, some processor CPU is required to perform FPD upgrades. The performance impact will vary depending on various factors, including network traffic load, the type of processing engine used, and the type of service configured.

For these reasons, we recommend that one of the following alternatives be used to perform the FPD upgrade on a production system if possible:

•

Using a Non-Production System to Upgrade the SPA FPD Image, page 17-5

•

Verifying System Compatibility Before Upgrading, page 17-5

Using a Non-Production System to Upgrade the SPA FPD Image

Before beginning the upgrade, ensure:

• The spare system is running the same version of the Cisco IOS software release that the target production system is running.

• The automatic upgrade feature is enabled on the spare system (the automatic upgrade feature is enabled by default. It can also be enabled using the upgrade fpd auto command).

Use the following procedure to perform an upgrade on a spare system:

Step 1

Step 2

Step 3

Step 4

Step 5

Download the FPD image package file to the router’s flash file system or TFTP or FTP server accessible by the spare system. In most cases, it is preferable to place the file in a Flash file system since the router, by default, searches for the FPD image package in the Flash file systems. If the Flash file systems are full, use the upgrade fpd path command to direct the router to search for the FPD image package in the proper location.

Insert the SPA into the spare system.

If an upgrade is required, the system will perform the necessary FPD image updates so that when this

SPA is inserted to the target production system it will not trigger an FPD upgrade operation there.

Verify the upgrade was successful by entering the show hw-module all fpd command.

Remove the SPA from the spare system after the upgrade.

Insert the SPA into the target production system.

Verifying System Compatibility Before Upgrading

If a spare system is not available to perform an upgrade, you can check for system compatibility by disabling the automatic upgrade feature before inserting the SPA(the automatic upgrade feature is enabled by default. It can be disabled using the no upgrade fpd auto command).

•

•

If the FPD images on the SPA are compatible with the system, you will only need to re-enable the automatic upgrade feature (the automatic upgrade feature can be re-enabled using the upgrade fpd auto command).

If the FPD images on the SPA are not compatible with the system, the SPA is disabled but will not impact system performance by attempting to perform an automatic upgrade.

Release 12.0(33)S, OL-8832-01, Rev. C9


17-5


Optional FPD Procedures

Use the following procedure to check the FPD images on the SPA for system compatibility:

Step 1

Step 2

Step 3

Disable the automatic upgrade feature using the no upgrade fpd auto global configuration command.

Insert the SPA into the system.

If the FPD images are compatible, the SPAs will operate successfully after bootup.

If the FPD images are not compatible, the SPA is disabled. At this point we recommend that you wait for a scheduled maintenance when the system is offline to manually perform the FPD upgrade using one of the procedures outlined in the

“Upgrading FPD Images” section on page 17-3 .

Re-enable the automatic upgrade feature using the upgrade fpd auto global configuration command.


This section provides information for optional FPD-related functions. None of the topics discussed in this section are necessary for completing FPD upgrades, but may be useful in some FPD-related scenarios. It covers the following topics:

•

Manually Upgrading SPA FPD Images, page 17-6

•

•

•

•

•

•

Upgrading FPD From an FTP or TFTP Server, page 17-7

Modifying the Default Path for the FPD Image Package File Location, page 17-9

Upgrading Multiple FPD Images, page 17-9

Displaying Current and Minimum Required FPD Image Versions, page 17-10

Displaying Information About the Default FPD Image Package, page 17-11

Verifying the FPD Image Upgrade Progress, page 17-12

Manually Upgrading SPA FPD Images

To manually upgrade the current FPD version on a SPA, use the following command:

Router# upgrade hw-module subslot slot-number / subslot-number fpd file file-url [ force ]

In this example, slot-number is the slot where the SIP is installed, subslot-number is the subslot number where the SPA is located, file-url is the location and name of the FPD image package file, and force is an option that forces the SPA to perform an FPD upgrade even if FPD is compatible (the force option is almost never necessary and should only be entered if requested by a technical support representative).

The SPA will automatically be reloaded to complete the FPD upgrade.

Caution An image upgrade can require a long period of time to complete depending on the hardware being upgraded.

17-6


Release 12.0(33)S, OL-8832-01, Rev. C9



Upgrading FPD From an FTP or TFTP Server

The generally recommended method to perform an FPD image upgrade is to download the FPD image package to a Flash file system and use the FPD automatic upgrade. By default, the system searches the

Flash file systems for the FPD image package file when an FPD incompatibility is detected.

This default behavior of loading an FPD image from Flash can be changed using the upgrade fpd path global configuration command, which sets the path to search for the FPD image package file to a location other than the router’s Flash file systems.

For large deployments where all the systems are being upgraded to a specific Cisco IOS software release, we recommend that the FPD image package file be placed on an FTP or TFTP server that is accessible to all the affected systems, and then use the upgrade fpd path global configuration command to configure the routers to look for the FPD image package file from the FTP or TFTP server prior to the reloading of the system with the new Cisco IOS release.

Note This approach can also be used if there is not enough disk space on the system Flash card to hold the

FPD image package file.

To download an FPD image package file to an FTP or TFTP server, use the following procedure:

Step 1

Step 2

Step 3

Copy the FPD image package file to the FTP or TFTP server.

Access the router from a connection that does not use the SPA interface for access, if possible. We recommend not using the SPA interface as your connection to the router because an FPD incompatibility disables all interfaces on the SPA, making a manual FPD upgrade impossible through a SPA interface.

If access through one of the SPA ports is the only access to the router you have, do not use the TFTP or

FTP upgrade method. Instead, copy the FPD image package to your router’s default Flash card before upgrading your Cisco IOS Release. This will allow the router to find the FPD image package during the first IOS bootup and upgrade FPD automatically.

From global configuration mode, use the upgrade fpd path command to instruct the router to locate the

FPD image package file from the FTP or TFTP server location.

For example, enter one of the following global configuration commands from the target system’s console:

Router(config)# upgrade fpd path tftp://my_tftpserver/fpd_pkg_dir/ or

Router(config)# upgrade fpd path ftp://login:password@my_ftpserver/fpd_pkg_dir/

Note The final “ / ” at the end of each of the above examples is required. If the path is specified without the trailing “ / ” character, the command will not work properly.

Step 4

In these examples, my_tftpserver or my_ftpserver is the path to server name, fpd_pkg_dir is the directory on the TFTP server where the FPD image package is located, and login:password is your FTP login name and password.

Make sure that the FPD automatic upgrade feature is enabled by examining the output of the show running-config command (look for the upgrade fpd auto configuration line in the output. If there are no upgrade commands in the output, then upgrade fpd auto is enabled because it is the default setting.) If automatic upgrades are disabled, use the upgrade fpd auto global configuration command to enable automatic FPD upgrades.

Release 12.0(33)S, OL-8832-01, Rev. C9


17-7



Step 5

Step 6

Enter the show upgrade fpd file command to ensure your router is connecting properly to the default

FPD image package. If you are able to generate output related to the FPD image package using this command, the upgrade should work properly.

In the following example, the router is able to generate FPD image package information for the FPD image package on the TFTP server.

Router# show upgrade fpd file tftp://mytftpserver/myname/myfpdpkg/c12k-fpd-pkg.120-31.S.pkg

Loading myname/myfpdpkg//c12k-fpd-pkg.120-31.S.pkg from 223.255.254.254 (via Ethernet0):

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[OK - 1577472 bytes]

Cisco Field Programmable Device Image Package for IOS

C12K Family FPD Image Package (c12k-fpd-pkg.120-31.S.pkg), Version 12.0(31)S

Copyright (c) 2004-2005 by cisco Systems, Inc.

Built Thu 31-Mar-2005 22:24 by luislu

=============================== ================================================

Bundled FPD Image Version Matrix

================================================

Min. Req.

Supported Card Types ID Image Name Version H/W Ver.

=============================== == ========================= ========= =========

2-port T3/E3 Serial SPA 1 T3E3 SPA ROMMON 2.12 0.0

2 T3E3 SPA I/O FPGA 0.24 0.0

3 T3E3 SPA E3 FPGA 0.6 0.0

4 T3E3 SPA T3 FPGA 0.14 0.0

------------------------------- -- ------------------------- --------- ---------


2 T3E3 SPA I/O FPGA 0.24 0.0

3 T3E3 SPA E3 FPGA 0.6 0.0

4 T3E3 SPA T3 FPGA 0.14 0.0

------------------------------- -- ------------------------- --------- ---------

2-port Channelized T3 SPA 1 CT3 SPA ROMMON 2.12 0.100

2 CT3 SPA I/O FPGA 1.4 0.100

3 CT3 SPA T3 FPGA R1 0.11 0.100

3 CT3 SPA T3 FPGA R2 0.15 0.200

------------------------------- -- ------------------------- --------- ---------


2 CT3 SPA I/O FPGA 1.4 0.100

3 CT3 SPA T3 FPGA R1 0.11 0.100

3 CT3 SPA T3 FPGA R2 0.15 0.200

------------------------------- -- ------------------------- --------- ---------

1-port OC-192 POS/SRP FH SPA 1 1-Port POS/RPR SPA IOFPGA 1.2 0.0

------------------------------- -- ------------------------- --------- ---------

1-port OC-192 POS/SRP HH SPA 1 1-Port POS/RPR SPA IOFPGA 1.2 0.0

1 1-Port POS/RPR SPA IOFPGA 1.2 2.0

------------------------------- -- ------------------------- --------- ---------

1-port OC-48 POS/SRP HH SPA 1 1-Port POS/RPR SPA IOFPGA 1.2 0.0

------------------------------- -- ------------------------- --------- ---------

10-port GE SPA 1 GE SPA FPGA 1.6 0.0

------------------------------- -- ------------------------- --------- ---------

5-port GE SPA 1 GE SPA FPGA 1.6 0.0

------------------------------- -- ------------------------- --------- ---------

1-port 10GE SPA 1 10GE SPA FPGA 1.6 0.0

=============================== ================================================

Save the configuration and reload the system with the new Cisco IOS release.

17-8


Release 12.0(33)S, OL-8832-01, Rev. C9



During the system startup after the reload, the necessary FPD image version check for all the SPAs will be performed and any upgrade operation will occur automatically if an upgrade is required. In each upgrade operation, the system extracts the necessary FPD images to the SPA from the FPD image package file located on the FTP or TFTP server.

Modifying the Default Path for the FPD Image Package File Location

By default, the Cisco IOS software looks for the FPD image package file on a Flash file system when performing an automatic FPD image upgrade.

Note Be sure there is enough space on one of your Flash file systems to accommodate the FPD image package file.

Alternatively, you can store an FPD image package file elsewhere. However, because the system looks on the Flash file systems by default, you need to change the FPD image package file location so that the system is directed to search an alternate location (such an FTP or TFTP server) that is accessible by the

Cisco IOS software. Enter the upgrade fpd path fpd-pkg-dir-url global configuration command, where fpd-pkg-dir-url is the alternate location, to instruct the router to search for the FPD image package elsewhere.

When specifying the fpd-pkg-dir-url , be aware of the following:

• The fpd-pkg-dir-url is the path to the FPD image package, but the FPD image package should not be specified as part of the fpd-pkg-dir-url . For instance, if the c12k-fpd-pkg.120-31.S.pkg file can be found on the TFTP server using the path mytftpserver/myname/myfpdpkg/c12k-fpd-pkg.120-31.S.pkg and you wanted the router to utilize this FPD image package for FPD upgrades, the upgrade fpd path tftp://mytftpserver/myname/myfpdpkg/ command should be entered so the router knows where to find the file. The actual filename should not be specified.

• The final “/” character in the fpd-pkg-dir-url is required. In the preceding example, note that the fpd-pkg-dir-url is tftp://mytftpserver/myname/myfpdpkg/. Entering tftp://mytftpserver/myname/myfpdpkg (note: the final “/” character is missing) as the fpd-pkg-dir-url in that scenario would not work .

If the upgrade fpd path global configuration command has not been entered to direct the router to locate an FPD image package file in an alternate location, the system searches the Flash file systems on the

Cisco 12000 series router for the FPD image package file.

Failure to locate an FPD image package file when an upgrade is required will disable the SPA. Because

SPAs will not come online until FPD is compatible, the SPA will also be disabled if it requires an FPD upgrade and the automatic upgrade feature is disabled.

Upgrading Multiple FPD Images

A single piece of hardware can contain multiple FPD images. The Cisco 12000 series routers can upgrade up to 4 FPD images simultaneously. However, only one FPD upgrade per router slot can occur at a time, so all FPD images on all SPAs in a single slot will have to wait for the previous FPD upgrade to finish before their specific FPD upgrade begins.

Release 12.0(33)S, OL-8832-01, Rev. C9


17-9



Users should note that some FPD images require the SPA to reload to complete. The FPD upgrade process will perform this step automatically, so users do not have to intervene. However, the other FPDs in the hardware of the specified slot will have to wait for this reload to complete before their upgrade process begins.

During an automatic upgrade, the Cisco 12000 series router will upgrade as many FPDs as possible at a time. No user intervention is possible or necessary. The upgrade process will not stop until all FPD images have been updated.

During manual upgrades, it is important to note that users can only specify upgrades for a single piece of hardware each time the upgrade hw-module [ slot slot-number | subslot slot-number / subslot-number ] fpd is entered. The up to 4 simultaneous upgrades applies to the manual upgrades as well; if you individually specify multiple manual FPD upgrades, only 4 FPDs can be upgraded simultaneously and that can only occur when the hardware is in different router slots. The FPD upgrade process will stop when all FPDs for the specified hardware have been upgraded.

Displaying Current and Minimum Required FPD Image Versions

To display the current version of FPD images on the SPAs installed on your router, use the show hw-module [ slot-number / subslot-number | all ] fpd command, where slot-number is the slot number where the SIP is installed, and subslot-number is the number of the SIP subslot where a target SPA is located. Entering the all keyword shows information for hardware in all router slots.

The following examples show the output when using this show command.

The output display in this example shows that FPD versions on SPAs in the system meet the minimum requirements:

Router# show hw-module all fpd

==== ====================== ====== =============================================

H/W Field Programmable Current Min. Required

Slot Card Type Ver. Device: "ID-Name" Version Version

==== ====================== ====== ================== =========== ==============

2/0 SPA-1XTENGE-XFP 2.1 1-10GE I/O FPGA 1.6 1.6

---- ---------------------- ------ ------------------ ----------- --------------

2/1 SPA-10X1GE 1.0 1-GE I/O FPGA 1.6 1.6

---- ---------------------- ------ ------------------ ----------- --------------

3/0 SPA-4XCT3/DS0 0.253 1-ROMMON 2.12 2.12

2-I/O FPGA 1.4 1.4

3-T3 SUBRATE FPGA 0.15 0.15

---- ---------------------- ------ ------------------ ----------- --------------

3/1 SPA-4XCT3/DS0 0.253 1-ROMMON 2.12 2.12

2-I/O FPGA 1.4 1.4


==== ====================== ====== =============================================

This example shows the output when using the slot-number / subslot-number argument to identify a particular SPA:

Router# show hw-module subslot 3/1 fpd

==== ====================== ====== =============================================



==== ====================== ====== ================== =========== ==============

3/1 SPA-4XCT3/DS0 0.253 1-ROMMON 2.12 2.12

2-I/O FPGA 1.4 1.4


==== ====================== ====== =============================================

17-10


Release 12.0(33)S, OL-8832-01, Rev. C9



The output display in this example shows that the SPA in subslots 3/0 and 3/1 are disabled because at least one of the programmable devices on each SPA does not meet the minimum version requirements.

The output also contains a “NOTES” section that provides the name of the FPD image package file needed to upgrade the disabled FPD image.


==== ====================== ====== =============================================



==== ====================== ====== ================== =========== ==============


---- ---------------------- ------ ------------------ ----------- --------------

2/1 SPA-10X1GE 1.0 1-GE I/O FPGA 1.6 1.6

---- ---------------------- ------ ------------------ ----------- --------------

3/0 SPA-4XCT... <DISABLED> 0.253 1-ROMMON 2.12 2.12

2-I/O FPGA 1.1 1.4 *


---- ---------------------- ------ ------------------ ----------- --------------

3/1 SPA-4XCT... <DISABLED> 0.253 1-ROMMON 2.12 2.12

2-I/O FPGA 1.1 1.4 *


==== ====================== ====== =============================================

NOTES:

- FPD images that are required to be upgraded are indicated with a '*'

character in the "Minimal Required Version" field.

- The following FPD image package file is required for the upgrade:

"c12k-fpd-pkg.120-31.S.pkg"

Displaying Information About the Default FPD Image Package

You can use the show upgrade fpd package default command to find out which SPAs are supported with your current Cisco IOS release and which FPD image package you need for an upgrade.

Router# show upgrade fpd package default

*************************************************************************

This IOS release requires the following default FPD Image Package for the automatic upgrade of FPD images:

*************************************************************************

Version: 12.0(31)S

Package Filename: c12k-fpd-pkg.120-31.S.pkg

List of card type supported in this package:

Minimal

No. Card Type HW Ver.

---- ------------------ -------

1) 2xT3E3 SPA 0.0

2) 4xT3E3 SPA 0.0

3) 10xGE SPA 0.0

4) 5xGE SPA 0.0

5) 1x10GE XFP SPA 0.0

6) 1xOC192 POS/RPR HH 0.0

7) 1xOC192 POS/RPR FH 0.0

8) 2xCT3 SPA 0.100

9) 2xCT3 SPA 0.200

10) 4xCT3 SPA 0.100

Release 12.0(33)S, OL-8832-01, Rev. C9


17-11


FPD Image Upgrade Examples

11) 4xCT3 SPA 0.200

---- ------------------ -------

Verifying the FPD Image Upgrade Progress

You can use the show upgrade fpd progress command to view a “snapshot” of the upgrade progress while an FPD image upgrade is taking place. The following example shows the type of information this command displays:

Router# show upgrade fpd progress

FPD Image Upgrade Progress Table:

==== =================== ====================================================

Field Programmable Time

Slot Card Description Device :"ID-Name" Needed Time Left State

==== =================== ================== ========== ========== ===========

2/0 SPA-1XTENGE-XFP 1-10GE I/O FPGA 00:06:00 00:05:17 Updating...

---- ------------------- ------------------ ----------- --------- -----------

2/1 SPA-10X1GE 1-GE I/O FPGA --:--:-- --:--:-- Waiting...

==== =================== ====================================================


This section provides examples of automatic and manual FPD image upgrades. It includes the following examples:

•

System Cannot Locate FPD Image Package File for an Automatic FPD Image Upgrade Example, page 17-12

•

•

Automatic FPD Image Upgrade Example, page 17-13

Manual FPD Image Upgrade Example, page 17-13

System Cannot Locate FPD Image Package File for an Automatic FPD Image Upgrade Example

The following example displays the output when a SPA-4XCT3/DS0 requires an FPD upgrade and the upgrade fpd auto command is enabled , but the system cannot find the FPD image package file.

SLOT 3:00:13:16: %SPA_OIR-6-INSCARD: Card inserted in Subslot 1

SLOT 3:00:13:27: %SPA_PLUGIN-6-FIRMWARE_DOWNLOADING: SPA-4XCT3/DS0[3/1]: Downloading SPA firmware (bundled)...via shared memory.

SLOT 3:00:13:31: %SPA_PLUGIN-6-FIRMWARE_APPS_DOWNLOADING: SPA-4XCT3/DS0[3/1]: Downloading

SPA firmware application (bundled)...via shared memory.

01:01:18: %FPD_MGMT-3-INCOMP_IMG_VER: Incompatible I/O FPGA (FPD ID=2) image version detected for SPA-4XCT3/DS0 card in subslot 3/1. Detected version = 1.1, minimum required version = 1.4. Current HW version = 0.253.

01:01:18: %FPD_MGMT-5-UPGRADE_ATTEMPT: Attempting to automatically upgrade the FPD image(s) for SPA-4XCT3/DS0 card in subslot 3/1. Use 'show upgrade fpd progress' command to view the upgrade progress ...

SLOT 3:00:13:43: %SPA_OIR-6-INSCARD: Card inserted in Subslot 0

01:01:20: %FPD_MGMT-3-PKG_FILE_SEARCH_FAILED: FPD image package

(c12k-fpd-pkg.120-31.S.pkg) cannot be found in system's flash card or disk to do FPD upgrade.

17-12


Release 12.0(33)S, OL-8832-01, Rev. C9



01:01:20: %FPD_MGMT-5-CARD_DISABLED: SPA-4XCT3/DS0 card in subslot 3/1 is being disabled because of an incompatible FPD image version. Note that the c12k-fpd-pkg.120-31.S.pkg package will be required if you want to perform the upgrade operation.

Automatic FPD Image Upgrade Example

The following example shows the output displayed when a SPA-4XCT3/DS0 requires an FPD image upgrade and the upgrade fpd auto command is enabled . The required FPD image is automatically upgraded.

01:43:56: %FPD_MGMT-3-INCOMP_IMG_VER: Incompatible I/O FPGA (FPD ID=2) image version detected for SPA-4XCT3/DS0 card in subslot 3/1. Detected version = 1.1, minimum required version = 1.4. Current HW version = 0.253.

01:43:56: %FPD_MGMT-5-UPGRADE_ATTEMPT: Attempting to automatically upgrade the FPD image(s) for SPA-4XCT3/DS0 card in subslot 3/1. Use 'show upgrade fpd progress' command to view the upgrade progress ...

01:43:56: %FPD_MGMT-6-BUNDLE_DOWNLOAD: Downloading FPD image bundle for SPA-4XCT3/DS0 card in subslot 3/1 ...

01:43:57: %FPD_MGMT-6-UPGRADE_TIME: Estimated total FPD image upgrade time for

SPA-4XCT3/DS0 card in subslot 3/1 = 00:00:50.

01:43:57: %FPD_MGMT-6-UPGRADE_START: I/O FPGA (FPD ID=2) image upgrade in progress for

SPA-4XCT3/DS0 card in subslot 3/1. Updating to version 1.4. PLEASE DO NOT INTERRUPT DURING

THE UPGRADE PROCESS (estimated upgrade completion time = 00:00:50) ...via shared memory.

01:44:23: %FPD_MGMT-6-UPGRADE_PASSED: I/O FPGA (FPD ID=2) image in the SPA-4XCT3/DS0 card in subslot 3/1 has been successfully updated from version 1.1 to version 1.4. Upgrading time = 00:00:25.652

01:44:23: %FPD_MGMT-6-OVERALL_UPGRADE: All the attempts to upgrade the required FPD images have been completed for SPA-4XCT3/DS0 card in subslot 3/1. Number of successful/failure upgrade(s): 1/0.

01:44:23: %FPD_MGMT-5-CARD_POWER_CYCLE: SPA-4XCT3/DS0 card in subslot 3/1 is being power cycled for the FPD image upgrade to take effect.

Manual FPD Image Upgrade Example

In the following example, FPD for the 1-Port 10 Gigabit Ethernet SPA in subslot 2/0 is upgraded manually from the FPD image package file that was placed on disk0:.

Router# upgrade hw-module subslot 2/0 fpd file disk1:c12k-fpd-pkg.120-31.S.pkg

% The following FPD(s) will be upgraded for SPA-1XTENGE-XFP (H/W ver = 2.1) in subslot

2/0:

================== =========== =========== ============

Field Programmable Current Upgrade Estimated

Device: "ID-Name" Version Version Upgrade Time

================== =========== =========== ============

1-10GE I/O FPGA 1.5 1.6 00:00:20

================== =========== =========== ============

% Are you sure that you want to perform this operation? [no]: y

% Restarting the target card in subslot 2/0 for FPD image upgrade. Please wait ...

Router#


SPA-1XTENGE-XFP card in subslot 2/0 = 00:00:20.

01:59:32: %FPD_MGMT-6-UPGRADE_START: 10GE I/O FPGA (FPD ID=1) image upgrade in progress for SPA-1XTENGE-XFP card in subslot 2/0. Updating to version 1.6. PLEASE DO NOT INTERRUPT

DURING THE UPGRADE PROCESS (estimated upgrade completion time = 00:00:20) ...

Release 12.0(33)S, OL-8832-01, Rev. C9


17-13


Troubleshooting Problems with FPD Image Upgrades

01:59:55: %FPD_MGMT-6-UPGRADE_PASSED: 10GE I/O FPGA (FPD ID=1) image in the

SPA-1XTENGE-XFP card in subslot 2/0 has been successfully updated from version 1.5 to version 1.6. Upgrading time = 00:00:23.440

01:59:55: %FPD_MGMT-6-OVERALL_UPGRADE: All the attempts to upgrade the required FPD images have been completed for SPA-1XTENGE-XFP card in subslot 2/0. Number of successful/failure upgrade(s): 1/0.

01:59:55: %FPD_MGMT-5-CARD_POWER_CYCLE: SPA-1XTENGE-XFP card in subslot 2/0 is being power cycled for the FPD image upgrade to take effect.


This section contains information to help troubleshoot problems that can occur during the upgrade process.

Power Failure or Removal of a SPA During an FPD Image Upgrade

If the FPD upgrade operation is interrupted by a power failure or the removal of the SPA, it could corrupt the FPD image. This corruption of the FPD image file makes the SPA unusable by the router and the system will display the following message when it stops trying to power up the SPA:

Note To find more information about FPD-related messages, check the system error messages guide for your Cisco IOS software release.

02:10:10: %SPA_OIR-3-SPA_POWERED_OFF: subslot 2/0: SPA 1x10GE XFP SPA powered off after 5 failures within 600 seconds

The show hw-module subslot slot-number / subslot-number fpd command can be used to verify that the

SPA is using a corrupted FPD image. In this example, the SPA in slot 4/1 is corrupted.


==== ====================== ====== =============================================



==== ====================== ====== ================== =========== ==============

2/0 SPA-1XTENGE-XFP 2.1 1-10GE I/O FPGA ?.? ?.?

==== ====================== ====== =============================================

Performing a FPD Recovery Upgrade

The recovery upgrade procedure can only be performed on a SPA that has been powered off by the system after it has failed all of the retries attempted to initialize the SPA.

The following example displays the output of an attempt to perform a recovery upgrade before all the initialization retries have been attempted for the SPA in subslot 2/0.

02:04:08: %FPD_MGMT-4-UPGRADE_EXIT: Unexpected exit of FPD image upgrade operation for

SPA-1XTENGE-XFP card in subslot 2/0.

02:04:15: %FPD_MGMT-5-CARD_DISABLED: SPA-1XTENGE-XFP card in subslot 2/0 is being disabled because of an incompatible FPD image version. Note that the c12k-fpd-pkg.120-31.S.pkg package will be required if you want to perform the upgrade operation.

Router#upgrade hw-module subslot 2/0 file disk1:c12k-fpd-pkg.120-31.S.pkg

17-14


Release 12.0(33)S, OL-8832-01, Rev. C9



% Cannot get FPD version information for version checking. If a previous upgrade attempt has failed for the target card, then a recovery upgrade would be required to fix the failure.


2/0:

================== =========== =========== ============



================== =========== =========== ============

1-10GE I/O FPGA ?.? 1.6 00:00:20

================== =========== =========== ============

% Do you want to perform the recovery upgrade operation? [no]: y

% Cannot perform recovery upgrade operation because the target card is not in a failed state. Please try again later.

Once the following error message is displayed, you can perform the recovery upgrade:

Note You must wait to see this error message before you attempt the upgrade.

%SPA_OIR-3-SPA_POWERED_OFF: subslot 2/0: SPA 1x10GE XFP SPA powered off after 5 failures within 600 seconds

Perform the manual FPD image upgrade method using the upgrade hw-module subslot command to recover from a corrupted image after the SPA has been powered off by the system. In this command, slot-number is the slot where the SIP is installed, subslot-number is the subslot of the SIP where the SPA is located, and file-url is the location of the FPD image package file.

Note Before proceeding with this operation, make sure that the correct version of the FPD image package file has been obtained for the corresponding Cisco IOS release that the system is using.

The following example displays the console output of a recovery upgrade operation:

Router#upgrade hw-module subslot 2/0 file disk1:c12k-fpd-pkg.120-31.S.pkg

% Cannot get FPD version information for version checking. If a previous upgrade attempt has failed for the target card, then a recovery upgrade would be required to fix the failure.


2/0:

================== =========== =========== ============



================== =========== =========== ============

1-10GE I/O FPGA ?.? 1.6 00:00:20

================== =========== =========== ============

% Do you want to perform the recovery upgrade operation? [no]: y

Release 12.0(33)S, OL-8832-01, Rev. C9


17-15



% Proceeding with recovery upgrade operation ...

Router#


SPA-1XTENGE-XFP card in subslot 2/0 = 00:00:20.

02:14:47: %FPD_MGMT-6-UPGRADE_START: Unknown FPD (FPD ID=1) image upgrade in progress for

SPA-1XTENGE-XFP card in subslot 2/0. Updating to version 1.6. PLEASE DO NOT INTERRUPT

DURING THE UPGRADE PROCESS (estimated upgrade completion time = 00:00:20) ...

02:15:10: %FPD_MGMT-6-UPGRADE_PASSED: Unknown FPD (FPD ID=1) image in the SPA-1XTENGE-XFP card in subslot 2/0 has been successfully updated from version ?.? to version 1.6.

Upgrading time = 00:00:23.540

02:15:10: %FPD_MGMT-6-OVERALL_UPGRADE: All the attempts to upgrade the required FPD images have been completed for SPA-1XTENGE-XFP card in subslot 2/0. Number of successful/failure upgrade(s): 1/0.

02:15:10: %FPD_MGMT-5-CARD_POWER_CYCLE: SPA-1XTENGE-XFP card in subslot 2/0 is being power cycled for the FPD image upgrade to take effect.

Verifying a Successful Upgrade

After the upgrade process is complete, you can use the show hw-module subslot slot-number / subslot-number fpd command to verify that the FPD image has been successfully upgraded:


==== ====================== ====== =============================================



==== ====================== ====== ================== =========== ==============


==== ====================== ====== =============================================

17-16


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

18

Command Summary for FPDs

Table 18-1

provides an alphabetical list of some of the related commands to configure, monitor, and upgrade FPD images for SPAs on the Cisco 12000 Series Router. For more information about the commands, see


in this book.

Table 18-1 FPD Command Summary

Command

Router# show hw-module [ subslot slot-number / subslot-number | all ] fpd

Router# show upgrade fpd file file-url

Router# show upgrade fpd package default

Router#

Router#

Router(config)#

Router(config)#

Router# show upgrade fpd progress show upgrade fpd table upgrade fpd auto upgrade fpd path fpd-pkg-dir-url upgrade hw-module subslot slot-number / subslot-number file file-url [ force ]

Purpose

Displays all current versions of FPD image files for all of the active SPAs on a router.

Displays the contents of an FPD image package file.

Displays the default FPD image package file that is needed for the router to properly support the SPAs running on the Cisco

IOS software release.

Displays the progress of an FPD upgrade while an FPD upgrade is taking place.

Displays various information used by the Cisco IOS software to manage the FPD image package file.

Configures the router to automatically upgrade the current FPD images on a SPA when an FPD version incompatibility is detected.

Configures the router to search for an FPD image package file in a location other than the router’s primary Flash file system during an automatic FPD upgrade.

Manually upgrades the current FPD image package on a SPA.

Release 12.0(33)S, OL-8832-01, Rev. C9


18-1

Chapter 18 Command Summary for FPDs

18-2


Release 12.0(33)S, OL-8832-01, Rev. C9

C H A P T E R

19

SIP and SPA Command Reference

This chapter documents new and modified commands. All other commasnds used with this feature are documented in the Cisco IOS Release 12.0 command reference and master index publications.

Note Some of the commands in this chapter apply to multiple Cisco products and are supported on different platforms. The documentation for these commands describes differences in syntax and usage for certain platform or product variations. Therefore, when you see multiple forms of syntax, examples, or usage guidelines for a command in this guide, be sure to locate the heading within the command reference page that corresponds to the related SPA (or SIP) for your platform.

The following list shows the new and modified commands contained in this chapter:

•

•

•

bert errors(2-Port and 4-Port Clear Channel T3/E3 SPA), page 19-3

bert errors(8-Port Channelized T1/E1 SPA), page 19-4

•

•

•

•

bert errors(4-Port and 2-Port Channelized T3 to DS0 and 1-Port Channelized OC-3/STM-1 SPA), page 19-5

bert pattern(4-Port Clear Channel T3/E3 SPA), page 19-6

bert pattern with interval (8-Port Channelized T1/E1 SPA), page 19-8

bert pattern with channel-group(8-Port Channelized T1/E1 SPA), page 19-10

•

bert pattern(4-Port and 2-Port Channelized T3 to DS0 and 1-Port Channelized OC-3/STM-1 SPA), page 19-12

bert pattern with channel-group(4-Port and 2-Port Channelized T3 to DS0 and 1-Port Channelized

OC-3/STM-1 SPA), page 19-14

•

•

•

•

•

card type (T1/E1), page 19-17

card type (T3/E3), page 19-19

controller dwdm, page 19-21

flowcontrol bidirectional, page 19-24

•

•

•

•

•

framing (T1/E1 controller), page 19-26

framing (T3 controller), page 19-28

framing (T3/E3 interface), page 19-30

hw-module subslot reload, page 19-32

hw-module subslot shutdown, page 19-34

hw-module subslot srp, page 19-36


Release 12.0(33)S, OL-8832-01, Rev. C9 19-1

Chapter 19 SIP and SPA Command Reference

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

•

interface, page 19-38

loopback (T3/E3 interface), page 19-47

loopback remote line fdl, page 19-49

loopback remote line inband (Smartjack), page 19-51

loopback remote line inband csu, page 19-52

loopback remote payload fdl ansi, page 19-53

loopback network payload, page 19-55

loopback remote esf (FDL Remote Loopback), page 19-57

loopback remote iboc (In-Band Remote Loopback), page 19-58

mdl, page 19-59

show controller dwdm, page 19-61

show controllers pos, page 19-70

show controllers serial, page 19-80

show diag, page 19-87

show hw-module all fpd, page 19-97

show hw-module subslot fpd, page 19-99

show hw-module subslot oir, page 19-102

speed, page 19-154

show interface sdcc, page 19-107

show hw-module subslot oir, page 19-102

show interfaces pos, page 19-114

show interfaces serial, page 19-120

show upgrade fpd file, page 19-145

show upgrade fpd package default, page 19-148

show upgrade fpd progress, page 19-150

show upgrade fpd table, page 19-152

t1 framing, page 19-157

ttb, page 19-159

upgrade fpd auto, page 19-160

upgrade fpd path, page 19-162

upgrade hw-module slot, page 19-164

upgrade hw-module subslot fpd file, page 19-167

19-2


Release 12.0(33)S, OL-8832-01, Rev. C9


bert errors(2-Port and 4-Port Clear Channel T3/E3 SPA)

bert errors(2-Port and 4-Port Clear Channel T3/E3 SPA)

To transmit bert errors while running any bert pattern, use the bert error command in interface configuration mode.

bert errors [ number ]

Syntax Description number (Optional) Range of 1-255 bert errors that may be introduced in a bert pattern.

Defaults Default is 1

Command Modes Interface configuration

Command History Release

12.1(12c)EX1

12.2(18)S

12.2(18)SXE

12.0(31)S

Modification

This command was introduced for Cisco 7304 routers.

This command was introduced on Cisco 7304 routers running Cisco IOS

Release 12.2 S.

This command was integrated into Cisco IOS release 12.2(18)SXE to support SPAs on the Cisco 7600 series router.

This command was integrated into Cisco IOS Release 12.0(31)S.

Usage Guidelines Use this command to test link availability by injecting a fixed number of bert errors when a pattern is running and check that the same number of errors were received on the remote end.

Examples This example injects 200 bit errors in a running bit pattern on slot 5, bay 2.


Router(config)# int serial 5/0/0

Router(config-if)# bert errors 200

Related Commands Command bert pattern show controller serial

Description

Start a BERT pattern on a port.

Displays serial line statistics.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-3


bert errors(8-Port Channelized T1/E1 SPA)

bert errors(8-Port Channelized T1/E1 SPA)





Command Modes Controller configuration


12.0(33)S

Modification



Examples This example injects 200 bit errors in a running bit pattern on slot 5, bay 0, and port 0.



Router(config-controller)# bert errors 200

Related Commands Command bert pattern show controller

Description


Displays the result of a bit error rate test.

19-4


Release 12.0(33)S, OL-8832-01, Rev. C9


bert errors(4-Port and 2-Port Channelized T3 to DS0 and 1-Port Channelized OC-3/STM-1 SPA)

bert errors(4-Port and 2-Port Channelized T3 to DS0 and 1-Port

Channelized OC-3/STM-1 SPA)







12.0(33)S

Modification



Examples This example injects 100 bit errors on a channelized T3 SPA on slot 1, bay 3, and port 0.



Router(config-controller)# bert errors 100

This example injects 100 bit errors on a channelized OC3-SPA on slot 1, bay 3, and port 0.


Router(config)# controller sonet 1/3/0

Router(config-controller)# sts-1 1

Router(config-controller-sts1)# vtg 1 t1 1 bert errors 100

Related Commands Command bert pattern show controller

Description



Release 12.0(33)S, OL-8832-01, Rev. C9


19-5


bert pattern(4-Port Clear Channel T3/E3 SPA)


To start a BERT pattern on a port, use the bert pattern command in interface configuration mode. Use the no bert command to stop the sequence.

bert pattern { 0s | 1s | 2^15 | 2^20 | 2^23 | alt-0-1 | qrss } interval minutes no bert

Syntax Description 0s

1s

2^15

2^20

2^23 alt-0-1 qrss interval minutes

Repeating pattern of zeros (...000...).

Repeating pattern of ones (...111...).

Pseudorandom 0.151 test pattern that is 32,768 bits in length.

Pseudo-andom 0.153 test pattern that is 1,048,575 bits in length.

Pseudorandom 0.151 test pattern that is 8,388,607 bits in length.

Repeating pattern of alternating zeros and ones (...01010...).

Pseudorandom quasi-random signal sequence (QRSS) 0.151 test pattern that is

1,048,575 bits in length.

Specifies the length of the BERT test in minutes.

Defaults Bert is disabled by default.



11.1CC

12.0(5)XE

12.0(7)XE1

Modification

The command was introduced.

The command was enhanced as an ATM interface configuration command

Support for Cisco 7100 series routers was added.

12.1(5)T This command was integrated into Cisco IOS Release 12.1(5)T.

12.1(12c)EX1 Support for Cisco 7304 routers was added.

12.2(18)S Support for Cisco 7304 routers was added.

12.2(18)SXE This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series router.

12.0(31)S This command was integrated into Cisco IOS Release 12.0(31)S.

Usage Guidelines Use the bert pattern commamd to start or stop a specific bit pattern. To test link availability, start a pattern on one end and put the remote end in network loopback and verify that there are no bert errors.

Examples This example starts a bert pattern on slot 5, bay 0.


19-6


Release 12.0(33)S, OL-8832-01, Rev. C9




Router(config-if)# bert pattern 0s

Related Commands Command bert errors show controller loopback

Description

Transmit bert errors while running any bert pattern.


Loopback at various points in the transmit and receive path.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-7


bert pattern with interval (8-Port Channelized T1/E1 SPA)


To start a BERT pattern on a port, use the bert pattern command in controller configuration mode. Use the no bert command to stop the sequence.

bert pattern { 0s | 1s | 2^11 | 1-in-8 | 2^15 | 2^15-inverted | 2^20-0153 | 2^23 | 2^23 inverted |

2^9 | 3-in-24 | alt-0-1 | 2^20 QRSS } interval minutes [ timeslots timeslots-range ] speed { 56 |

64 } no bert


1s

2^11

1-in-8

2^15

2^15-inverted

2^20-0153

2^23

2^23-inverted

2^9

3-in-24 alt-0-1

2^20-QRSS interval minutes timeslots timeslots-range speed 56 / 64



Pseudorandom test pattern of 2047 bits in length.

Repeating pattern of one (1) bit in eight (8) is set.


Pseudorandom 0.151 test pattern that is 32,768 bits in length with inverted bits.



Pseudorandom 0.151 test pattern that is 8,388,607 bits in length with inverted bits.

Pseudorandom 0.153 test pattern of 511 bits in length.

Repeating pattern of three (3) bits in twenty-four (24) are set to one(1) and others are set to zero(0).





(Optional) Lists the timeslots which comprises the channel. It is used only if user wants to run fractional BERT, that is running BERT only on partial T1. The valid range is 1-24.

Specifies the speed for sending bert patterns. The valid values are 56/64. Speed needs tobe mentioned if timeslots parameter is specified in command syntax.




12.0(33)S

Modification

Support for the 1-in-8, 2^15-inverted, 2^23-inverted, 2^9, and 3-in-24 test patterns, on

Cisco 12000 series routers was added.

19-8


Release 12.0(33)S, OL-8832-01, Rev. C9




Examples This example starts a bert pattern 0s having interval of 1 minute for 10 to 15 timeslots at the speed of 56 kbps on slot 5, bay 0 and port 0.



Router(config-controller)# bert pattern 0s interval 1 timeslots 10-15 speed 56

Related Commands Command bert errors loopback show controller

Description




Release 12.0(33)S, OL-8832-01, Rev. C9


19-9


bert pattern with channel-group(8-Port Channelized T1/E1 SPA)



bert pattern { 0s | 1s | 2^11 | 1-in-8 | 2^15 | 2^15-inverted | 2^20-0153 | 2^23 | 2^23 inverted |

2^9 | 3-in-24 | alt-0-1 | 2^20 QRSS | 55Octet | DS0-1 | DS0-2 | DS0-3 | DS0-4 | 55Daly } interval minutes channel-group channel-group# no bert


1s

2^11

1-in-8

2^15

2^15-inverted

2^20-0153

2^23

2^23-inverted

2^9

3-in-24 alt-0-1

2^20-QRSS

55Octet

DS0-1

DS0-2

DS0-3

DS0-4

55Daly interval minutes channel group channel-group#















Repeating pattern of fifty-five (55), eight bit octets of data. 55 OCTET has fifteen (15) consecutive zeros.

A repeating sequence of 100x FFh followed by 100x 00h. This combination of minimum and maximum densities causes stressing of the signal recovery circuitry.

A repeating sequence of 100x 7Eh followed by 100x 00h. This provides minimum ones density stressing as well as layer two "flag bytes".

A repeating sequence of 200x 4Ch. This combination represents the typical

SDD traffic patterns.

A repeating sequence of 200x 40h. This combination represents the typical DEC

VT traffic.

Repeating pattern of fifty-five (55), eight bit octets of data. The 55 Daly pattern introduces rapid transitions from long sequences of low density octets to high density octets, high density octets to low density octets, and rapid 1010 bit transitions.


Specifies the channgel group and channel group number to run BERT.

19-10


Release 12.0(33)S, OL-8832-01, Rev. C9






12.0(33)S

Modification

Support for the 1-in-8, 2^15-inverted, 2^23-inverted, 2^9, and 3-in-24 test patterns, 55

Octet, 55 Daly, DS0-1, DS0-2, DS0-3, and DS0-4 test patterns, on Cisco 12000 series routers was added.

Usage Guidelines Use the bert pattern command to start or stop a specific bit pattern. To test link availability, start a pattern on one end and put the remote end in network loopback and verify that there are no bert errors.

Examples This example starts a bert pattern DS0-1 having interval of 1 minute for channel group 1 on slot 5, bay

0 and port 0.



Router(config-controller)# bert pattern DS0-1 interval 1 channel-group 1


Description




Release 12.0(33)S, OL-8832-01, Rev. C9


19-11


bert pattern(4-Port and 2-Port Channelized T3 to DS0 and 1-Port Channelized OC-3/STM-1 SPA)

bert pattern(4-Port and 2-Port Channelized T3 to DS0 and 1-Port

Channelized OC-3/STM-1 SPA)


bert [ timeslots timeslots-range ] pattern { 0s | 1s | 2^11 | 1-in-8 | 2^15 | 2^15-inverted | 2^20-0153

| 2^23 | 2^23 inverted | 2^9 | 3-in-24 | alt-0-1 | 2^20 QRSS } interval minutes no bert


1s

2^11

2^15

1-in-8

2^15-inverted

2^20-0153

2^23

2^23-inverted

2^9

3-in-24 alt-0-1

2^20-QRSS interval minutes timeslots timeslots-range
















(Optional) Lists the timeslots which comprises the channel. It is used only if user wants to run fractional BERT, that is running BERT only on partial T1. The valid range is 1-24.




12.0(33)S

Modification

Support for the 1-in-8, 2^15-inverted, 2^23-inverted, 2^9, and 3-in-24 test patterns, on

Cisco 12000 series routers was added.

19-12


Release 12.0(33)S, OL-8832-01, Rev. C9


bert pattern(4-Port and 2-Port Channelized T3 to DS0 and 1-Port Channelized OC-3/STM-1 SPA)

Usage Guidelines Use the bert pattern command to start or stop a specific bit pattern. To test link availability, start a pattern on one end and put the remote end in network loopback and verify that there are no bert errors.

Examples This example starts a bert pattern 0s on first channel group of t1 1 channel of t3 controller having interval of 1 minute for 10 to 15 timeslots on slot 1, bay 3 and port 0.



Router(config-controller)# t1 1 bert timeslots 10-15 pattern 0s interval 1

This example starts a unframed bert test pattern 0s on first channel group of t1 1 channel of path 1 of sonet controller having interval of 1 minute for 10 to 15 timeslots on slot 1, bay 3 and port 0.



Router(config-controller)# sts 1

Router(config-ctrlr-sts1)# vtg 1 t1 1 bert time-slots 10-15 pattern 0s interval 1


Description




Release 12.0(33)S, OL-8832-01, Rev. C9


19-13


bert pattern with channel-group(4-Port and 2-Port Channelized T3 to DS0 and 1-Port Channelized OC-3/STM-1 SPA)

bert pattern with channel-group(4-Port and 2-Port Channelized

T3 to DS0 and 1-Port Channelized OC-3/STM-1 SPA)


bert channel-group channel-group pattern { 0s | 1s | 2^11 | 1-in-8 | 2^15 | 2^15-inverted |

2^20-0153 | 2^23 | 2^23 inverted | 2^9 | 3-in-24 | alt-0-1 | 2^20 QRSS | 55Octet | 55Daly |

DS0-1 | DS0-2 | DS0-3 | DS0-4 } interval minutes no bert

Note The bert patterns 55 Octet and 55 Daly are only supported for T1 controller.


1s

2^11

1-in-8

2^15

2^15-inverted

2^20-0153

2^23

2^23-inverted

2^9

3-in-24 alt-0-1

2^20-QRSS

55Octet

DS0-1

DS0-2

DS0-3

DS0-4















Repeating pattern of fifty-five (55), eight bit octets of data. 55 OCTET has fifteen (15) consecutive zeros.

A repeating sequence of 100x FFh followed by 100x 00h. This combination of minimum and maximum densities causes stressing of the signal recovery circuitry.

A repeating sequence of 100x 7Eh followed by 100x 00h. This provides minimum ones density stressing as well as layer two "flag bytes".

A repeating sequence of 200x 4Ch. This combination represents the typical

SDD traffic patterns.

A repeating sequence of 200x 40h. This combination represents the typical DEC

VT traffic.

19-14


Release 12.0(33)S, OL-8832-01, Rev. C9



55Daly interval minutes channel-group channel-group

Repeating pattern of fifty-five (55), eight bit octets of data. The 55 Daly pattern introduces rapid transitions from long sequences of low density octets to high density octets, high density octets to low density octets, and rapid 1010 bit transitions.


Specifies the channgel group and channel group number to run BERT.




12.0(33)S

Modification

Support for the 1-in-8, 2^15-inverted, 2^23-inverted, 2^9, 3-in-24 test patterns,

55Daly, 55Octet, DS0-1, DS0-2, DS0-3, and DS0-4 test patterns on Cisco 12000 series routers was added.


Examples This example starts a bert pattern 55Daly on first channel group of t1 1 channel of t3 controller, slot 5, bay 0 and port 0 at an interval of 1.



Router(config-controller)# t1 1 bert channel-group 1 pattern 55Daly interval 1

This example starts a bert pattern 55Daly on first channel group of t1 1 channel of path 1 of sonet controller, slot 5, bay 0 and port 0 at an interval of 1.




Router(config-ctrlr-sts1)# vtg 1 t1 1 bert channel-group 1 pattern 55Daly interval 1

Release 12.0(33)S, OL-8832-01, Rev. C9


19-15



Related Commands

This example stops a bert pattern 55Daly on first channel group of t1 1 channel of path 1 of sonet controller, slot 5, bay 0 and port 0 at an interval of 1.




Router(config-ctrlr-sts1)# no vtg 1 t1 1 bert channel-group 1 pattern 55Daly interval 1

Command bert errors loopback

Description



19-16


Release 12.0(33)S, OL-8832-01, Rev. C9


Release 12.0(33)S, OL-8832-01, Rev. C9

card type (T1/E1)


To configure the ports on SPA in T1 or E1 mode, use the card type command in global configuration mode. To deselect the card type, use the no form of this command.

Note The no form of this command is not supported on the Cisco 12000 router family.

card type { t1 | e1 } slot subslot no card type { t1 | e1 } slot subslot

Syntax Description slot subslot t1 e1

Chassis slot number.

Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding

“Identifying Slots and Subslots for SIPs and SPAs” topic in the platform-specific SPA software configuration guide.

Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.

Refer to the platform-specific SPA hardware installation guide and the corresponding “Specifying the Interface Address on a SPA” topic in the platform-specific SPA software configuration guide for subslot information.

Clear-channel T1 with integrated data service units (DSUs).

Clear-channel E1 with integrated data service units (DSUs).

Defaults No default behavior or values. There is no card type when the SPA is inserted for the first time. The user must configure this command before they can configure individual ports.

Command Modes Global configuration


12.0(5)XE

12.0(7)T

12.2S

Modification

This command was introduced.

This command was integrated into Cisco IOS Release 12.0(7)T.

This command was integrated into Cisco IOS Release 12.2S.

12.2(18)SXE This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.

12.0(31)S This command was integrated into Cisco IOS Release 12.0(31)S to support SPAs on the Cisco 12000 series routers.

Usage Guidelines To change all the SPA ports from T1 or T3 to E1 or E3 (or E3 to T3), you must deselect the card type and then configure the card with the new type of interface.


19-17



Examples The following example configures all ports of a T3/E3 SPA, seated in slot 5, bay 2, in T3 mode:


Router(config)# card type t3 5 2

Related Commands Command show interface serial

Description

Displays the serial interface type and other information.

19-18


Release 12.0(33)S, OL-8832-01, Rev. C9




To configure the ports on SPA in T3 or E3 mode, use the card type command in global configuration mode. To deselect the card type, use the no form of this comand.

card type { t3 | e3 } slot subslot no card type { t3 | e3 } slot subslot

Syntax Description slot subslot t3 e3






Clear-channel T3 with integrated data service units (DSUs).

Clear-channel E3 with integrated data service units (DSUs).

Defaults No default behavior or values. There is no card type when the SPA is inserted for first time. The user must configure this command before they can configure individual ports.



12.0(5)XE

12.0(7)T

12.1(1)T

12.2(11)YT

12.2(15)T

12.3(1)

12.2S

Modification




This command was integrated into Cisco IOS Release 12.2(11)YT and implemented on the following platforms: Cisco 2650XM, Cisco 2651XM, Cisco 2691, Cisco 3660 series, Cisco 3725, and Cisco 3745 routers.


This command was integrated into Cisco IOS Release 12.3(1) and support was added for Cisco 2610XM, Cisco 2611XM, Cisco 2620XM, Cisco 2621XM, Cisco 2650XM,

Cisco 2651XM, Cisco 2691, Cisco 3631, Cisco 3660, Cisco 3725, and Cisco 3745 platforms.


Release 12.0(33)S, OL-8832-01, Rev. C9


19-19




12.2(18)SXE This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.


Usage Guidelines To change all the SPA ports from T3 to E3, you must deselect the card type and then configure the card with the new type of interface.

Once a card type is issued, the user can enter the no card type command and then another card type command to configure a new card type. The user must save the configuration to NVRAM and reboot the router in order for the new configuration to take effect.

When the router comes up, the software comes up with the new card type. Note that the software will reject the configuration associated with the old controller and old interface. The user will now have to configure the new controller and serial interface and save it.

Examples The following example configures all ports of a T3/E3 SPA, seated in slot 5, bay 2, in T3 mode:


Router(config)# card type t3 5 2

Related Commands Command show interface serial

Description

Displays the serial interface type and other information.

19-20


Release 12.0(33)S, OL-8832-01, Rev. C9


controller dwdm

controller dwdm

To configure DWDM parameters on a 1-Port 10-Gigabit Ethernet DWDM SPA, use the controller dwdm command. Use the controller dwdm slot/subslot/port no command to negate a command or to set to its default value.

controller dwdm < slot> /< subslot> /< port> default [ g709 { disable | fec | odu | otu } | loopback | shutdown | wavelength ] controller dwdm < slot> /< subslot> /< port> no [ g709 { disable | fec | odu | otu } | loopback | shutdown | wavelength ]

Syntax Description slot subslot port default g709 disable fec odu otu loopback


Refer to the appropriate hardware manual for slot information. For SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding “Identifying Slots and Subslots for SIPs and SPAs” topic in the platform-specific SPA software configuration guide.

Subslot in the line card.

Port or interface number.

Refer to the appropriate hardware manual for port information. For SPAs, refer to the corresponding “Specifying the Interface Address on a SPA” topics in the platform-specific SPA software configuration guide.

Sets a command to its defaults.

Configures g709 protocol features in the areas of reporting of the alarms, thresholds for alerts, FEC etc.

Disables g709 function.

The forward error correction (fec) mode for the DWDM controller must be allowed to be disable/standard/enhanced. The command is supported only in shutdown state of the dwdm controller. The default configuration will be the enhanced FEC mode. If G.709 is not enabled, FEC must be disabled.

Configures optical data unit (odu) alarms reporting and threshold values to the console for a DWDM controller.

Configures optical transport unit (otu) alarms reporting and threshold values to the console for a DWDM controller.

Configures the DWDM controller for line or internal loopback mode. The line loopback allows the received Trunk/DWDM line Rx to be connected to

Trunk/DWDM line Tx towards the line. This is used for line diagnostics. The internal loopback allows the received data from the Ethernet Framer to be looped back to the ingress side of the Rx Framer allowing the packets to be looped back to the Linecard . This command is supported only in the shutdown state of the dwdm controller. The default configuration is with no loopbacks.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-21


controller dwdm shutdown wavelength

Disables the DWDM controller. You must disable the controller before you can use the DWDM configuration command.

Configures the channel number corresponding to the first wavelength.

Values are selected between 1 to 80 and the platform supported will be checked before applying the configuration. The default channel selected is first channel on the transponder.

Defaults

Command Modes Controller configuration and DWDM configurations

Command History

Execute controller dwdm slot/subslot/port default <parameter> to configure the default value for the specified parameter.

Release

12.0(33)S

Modification

This command was introduced to configure the interface parameters for

1-Port 10-Gigabit Ethernet DWDM SPA on the Cisco 12000 series routers.

Usage Guidelines The g709 disable command disables the g709 functions on DWDM SPA 1-Port 10-Gigabit Ethernet

DWDM SPA slot 3, subslot 0, port 0.

Router# config t


Router(config-dwdm)# g709 disable

Examples Examples of configuring DWDM parameters on the Cisco 12000 Series Router

The following example shows how to bring the DWDM controller down before using the configuration commands:

Router# config t



The following example configures the signal degrade BER threshold on the Cisco 12000 Series Router on Slot 3, subslot 0 and port 0:



Router(config-dwdm)# g709 otu threshold sd-ber 5

The following example removes the forced shutdown state on the controller and enabling the controller to move to an up or down state:




The following example displays the options and details of all the functional areas under DWDM controller:

Router# show controller dwdm 3/0/0 ?

g709 show g709 info

19-22


Release 12.0(33)S, OL-8832-01, Rev. C9


controller dwdm optics show transponder info wavelength-map wavelength channel number map table

| Output Modifiers

<cr>

The following example displays the serial controller statistics for a DWDM controller which can be used for diagnostic function:

Router# show controller dwdm 3/0/0

Port:dwdm0_0_0_0 DWDM info

Loopback: None

G709 status

OTU

LOS = 0 LOF = 0 LOM = 0

AIS = 0 BDI = 0

TIM = 0 EOC = 0

ODU

AIS = 0 BDI = 0 TIM = 0

EOC = 0 OCI = 0 LCK = 0

PTIM = 0

FEC Mode: EFEC(default)

EC = 0 UC= 0

Detected Alarms: LOF ODU-AIS

Asserted Alarms: ODU-AIS

Detected Alerts: PM-TCA

Asserted Alerts: PM-TCA

Alarm reporting enabled for:LOS LOF LOM

Alert reporting enabled for:SM-TCA PM-TCA

BER thresholds: OTU-SF = 10e-3 OTU-SD= 10e-6

ODU-SF = 10e-3 ODU-SD= 10e-6

TCA thresholds: SM = 10e-6 PM = 10e-6

Optics

optics type: ***

clock info: ***

Wavelength: C-band, channel 1, 1529.55nm, 196.00 THZ

RX Power = 0 dbm

TX power = 0 dbm

Tx Laser current bias = 0 mA

TX power threshold = 0

TX laser bias current threshold = 0

OPT-MIN = 0 OPT-MAX = 0 OPT_AVG = 0

OPR-MIN = 0 OPR-MAX = 0 OPR_AVG = 0

LBC-MIN = 0 LBC-MAX = 0 LBC_AVG = 0

output power fail = 0

input power fail = 0

Related Commands Command show controller dwdm

Description

Displays parameters configuration on a DWDM interface.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-23


flowcontrol bidirectional


To enable flowcontrol configuration (on) on a Gigabit Ethernet (GE)/Fast Ethernet (FE) SPA interface on Cisco 12000 series router, use the flowcontrol bidirectional command in interface configuration mode. Use the no flowcontrol bidrectional command to disable flowcontrol. The no flowcontrol bidrectional command is useful in a situation when the remote end does not support flowcontrol and the need arises to switch off flowcontrol on Cisco 12000 series router.

Note Flowcontrol must be enabled or disabled only after auto-negotiation is disabled. Auto-negotiation can be disabled using the no negotiation auto command. Flowcontrol configuration on both ends of the link must be same. Flowcontrol should be either enabled on both ends or disabled on both ends. flowcontrol bidirectional no flowcontrol bidirectional

Syntax Description This command has no arguments or keywords.

Defaults By default, flowcontrol is enabled.



12.0(33)S2

Modification

This command was introduced in Cisco IOS Release 12.0(33)S2 for the


Usage Guidelines This command is supported only for GE and FE interfaces of a SIP-401/501/600/601 on a Cisco 12000 series router. The default behaviour is flow control is enabled.

This command is not supported in following conditions:

• When GE SPA interface has Copper SFP inserted in it

•

•

On a 1-Port 10-Gigabit Ethernet SPA

Not supported on SPA-2X1GE-V2

Note This command is used in conjunction with no negotiation auto command. Auto negotiation should be first disabled using the no negotiation auto command before you enable or disable flowcontrol.

The following example shows how to enable flowcontrol on a GE SPA interface. Before this command is executed, you need to disable auto-negotiation:


Router(config)# interface g4/1/1

Router(config-if)# flowcontrol bidirectional

19-24


Release 12.0(33)S, OL-8832-01, Rev. C9



The above command enables flowcontrol on GE interfaces 4/1/1.

The following example shows how to disable flowcontrol on a GE SPA interface. Before this command is executed, you need to disable auto-negotiation:

Router(config-if)# no flowcontrol bidirectional

The above command disables flowcontrol on GE interfaces 4/1/1.

Related Commands Command Description

show interfaces flowcontrol

Dispalys flowcontrol configuration for a GE or FE SPA interfaces on a SIP-401/501/600/601.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-25


framing (T1/E1 controller)


To select the frame type for the T1 or E1 data line, use the framing command in controller configuration mode.

T1 Lines framing { sf | esf }

E1 Lines framing { crc4 | no-crc4 } [ australia ]

T1 Shared Port Adapter framing { sf | esf } no framing { sf | esf }

E1 Shared Port Adapter framing { crc4 | no-crc4 | unframed } no framing { crc4 | no-crc4 | unframed }

Syntax Description sf esf crc4 no-crc4 australia

Specifies super frame as the T1 frame type. This is the default for T1.

Specifies extended super frame as the T1 frame type.

Specifies CRC4 frame as the E1 frame type. This is the default for E1.

Specifies no CRC4 frame as the E1 frame type.

(Optional) Specifies the E1 frame type used in Australia.

Defaults sf (for a T1 line) crc4 (for an E1 line)



12.2S

12.2(18)SXE

12.0(31)S

Modification


This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers.


19-26


Release 12.0(33)S, OL-8832-01, Rev. C9



Usage Guidelines Use this command in configurations in which the router or access server is intended to communicate with

T1 or E1 fractional data lines. The service provider determines the framing type required for your T1/E1 circuit.

To return to the default mode on a T1/E1 SPA, use the no form of this command. This command does not have a no form for other T1/E1 lines.

Examples The following example selects extended super frame as the T1 frame type:

Router(config-controller)# framing esf

Related Commands Command cablelength linecode

Description

Specifies the distance of the cable from the routers to the network equipment.

Selects the linecode type for T1 or E1 line.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-27


framing (T3 controller)


To choose framing mode on a T3 port, use the framing command in controller configuration mode. To return to the default mode, use the no form of this command.

T3 Controllers framing { c-bit | m23 } no framing

T3/E3 Shared Port Adapters and the Cisco 7500 Series Routers with CT3IP Port Adapter framing { c-bit | m23 | auto-detect } no framing

Syntax Description auto-detect c-bit m23

Specifies detection of the framing type that it receives from the far-end equipment.

Specifies that C-bit framing is used as the T3 framing type.

Specifies that M23 framing is used as the T3 framing type.

Defaults c-bit (for T3 and most T3 controllers) auto-detect (for the CT3IP in a Cisco 7500 series router)



11.1CA

12.2(11)YT

12.2(15)T

12.2S

12.2(18)SXE

12.0(31)S

Modification


This command was integrated into Cisco IOS Release 12.2(11)YT and implemented on the following platforms for T3: Cisco 2650XM,

Cisco 2651XM, Cisco 2691, Cisco 3660 series, Cisco 3725, and Cisco 3745 routers.





Usage Guidelines Use the framing command to set the framing mode on the T3/E3 port.

19-28


Release 12.0(33)S, OL-8832-01, Rev. C9



Examples


The following example sets the framing mode on a T3 interface.



Router(config-controller)# framing m23

The following example sets the framing for the CT3IP to C-bit:


Router(config-controller)# framing c-bit

Command controller show controller

Description

Configures a T1, E1, or T3 controller and enters controller configuration mode.

Displays controller configuration.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-29


framing (T3/E3 interface)


To choose framing mode on a T3 port, use the framing command in interface configuration mode. To return to the default mode, use the no form of this command.

framing { bypass | c-bit | m13 } no framing { bypass | c-bit | m13 }

To choose framing mode on an E3 port, use the framing command in interface configuration mode. To return to the default mode, use the no form of this command.

framing { bypass | g751 | g832 } no framing { bypass | g751 | g832 }

Syntax Description bypass c-bit m13 g751 g832

Bypasses DS3 framing mode.

Enables DS3 C-bit framing mode.

Enables DS3 M13 framing mode.

Enables E3 G.751 framing mode.

Enables E3 G.832 framing mode.

Defaults T3: C-bit framing

E3: g751 framing



11.1

12.2S

12.2(18)SXE

12.0(31)S

Modification



This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers. The g832 keyword option was added to the command.


Usage Guidelines Use the framing command to set the framing mode on the T3 port.

Examples The following example sets the framing mode on the first port on slot 5.



Router(config-if)# framing bypass

19-30


Release 12.0(33)S, OL-8832-01, Rev. C9


Related Commands Command show controller serial

Description



Release 12.0(33)S, OL-8832-01, Rev. C9


19-31


hw-module subslot reload


To restart a shared port adapter (SPA) and its interfaces, use the hw-module subslot reload command in privileged EXEC configuration mode. The command does not have a no form. hw-module subslot slot / subslot reload

Syntax Description slot

/ subslot






Defaults No default behavior or values

Command Modes Privileged EXEC


12.2(25)S3

12.2(18)SXE

12.0(31)S

Modification


This command was integrated into Cisco IOS Release 12.2(18)SXE to support

SPAs on the Cisco 12000 Series Routers.

This command was integrted into Cisco IOS Release 12.0(31)S to support SPAs on the Cisco 12000 series routers.

Usage Guidelines The hw-module subslot reload command stops and starts power to the SPA. This command is useful when you want to restart all interfaces on a SPA.

The command is recommended to restart a SPA under some of the following conditions:

•

•

To restart a SPA after it has been powered off because of a failure.

To recover from corrupted messaging between the RouteProcessor (RP) and the SIP.

19-32


Release 12.0(33)S, OL-8832-01, Rev. C9



Examples The following command power cycles the SPA in subslot 2 of the SIP installed in chassis slot 13:

Router# hw-module subslot 13/2 reload

Router#

Note The hw-module subslot reload command does not produce a message on the router console to indicate the status of the command action. However, some interface configurations might produce console output related to the action of reloading the SPA.

Related Commands Command show hw-module subslot oir

Description

Displays the operational status of a SPA.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-33


hw-module subslot shutdown


To shut down a shared port adapter (SPA) with or without power and ensure that the SPA remains shut down, use the hw-module subslot shutdown command in global configuration mode. To reenable the

SPA, use the no form of this command.

hw-module subslot slot / subslot shutdown [ powered | unpowered ] no hw-module subslot slot / subslot shutdown [ powered | unpowered ]


/ subslot powered unpowered





(Optional) Shuts down the SPA and all of its interfaces, and leaves them in an administratively down state with power enabled. This is the default state.

(Optional) Shuts down the SPA and all of its interfaces, and leaves them in an administratively down state wihout power.

Defaults If this command is not used, no hw-module subslot shutdown is the default behavior. The SPA will not be shutdown unless specified by the user.

If this command is entered but both powered and unpowered are not specified in the CLI, powered is the default.



12.2(25)S3

12.2(18)SXE

12.0(31)S

Modification


This command was integrated into Cisco IOS Release 12.2(18)SXE.


19-34


Release 12.0(33)S, OL-8832-01, Rev. C9



Usage Guidelines When you shut down a SPA, you can choose to put it into one of two states:

•

•

Powered state—(Default) Shuts down the SPA, but the SPA remains powered on. Use this option when you plan to leave the SPA physically installed and cabled in the router. You might choose to do this if you want to install a SPA and configure it, but do not want it online or to start communicating with the remote end of the connection.

Unpowered state—Shuts down the SPA and removes power from the SPA. Use this option when you plan to remove the SPA from the chassis.

This command is useful when a user wants all the interfaces on a SPA disabled but does not or cannot remove the SPA. Unlike the hw-module subslot stop EXEC command on the Cisco 7304 router, this command is saved in the configuration file and will keep the SPA disabled when other router events (such as a router reload or OIR) attempt to restart the SPA. All other settings and configurations of the SPA will be maintained even if the SPA itself is shutdown using this command.

As a general rule, you do not need to shut down a SPA if you are removing it and replacing it with the same exact model of SPA in an online insertion and removal (OIR) operation. However, you should shut down a SPA whenever you are replacing a SPA with a different model of SPA.

When you shut down a SPA using the hw-module subslot shutdown command, it remains shut down even if you reset the router or install a new SPA in that subslot. You must manually reenable the card, using the no hw-module subslot shutdown command, so you can begin using the card again.

Examples The following example shows how to disable the SPA in subslot 4/1 while leaving the SPA in the router chassis. This command will be saved to the configuration file and no actions, outside of changing this configuration, will reenable the SPA:

Router(config)# hw-module subslot 4/1 shutdown unpowered

The following example shows how to configure the SPA to resume normal operation after the unpowered option has been used to disable the SPA:

Router(config)# hw-module subslot 4/1 shutdown powered

No messages are provided on the console when you shut down or reenable a SPA.

Related Commands Command show hw-module subslot oir hw-module slot 1

Description

Displays the operational status of a SPA.

Deactivates or reactivates a carrier card that is installed in a router slot. This command is entered in EXEC mode and is not saved to the configuration file.

1.

Refer to the Cisco 7300 Series Platform-Specific Commands publication.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-35


hw-module subslot srp


To change from Packet over SONET (POS) mode to Spatial Reuse Protocol (SRP) mode for all interfaces on a POS/Resilient Packet Ring (RPR) SPA, use the hw-module subslot srp command in global configuration mode. To return the SPA to POS mode, use the no form of the command.

hw-module subslot slot / subslot srp { mate slot / subslot } no hw-module subslot slot / subslot srp { mate slot / subslot }

Syntax Description

/ slot subslot mate slot / subslot






(Not required for the 2-Port OC-48c/STM-16 POS SPA) Specifies the location of the SPA that is the SRP mate.




12.0(32)SY

Modification


Usage Guidelines When enabling SRP mode using the hw-module subslot srp command, consider the following guidelines:

• For proper configuration of SRP for SPAs installed in the same SIP, you should enable SRP using the hw-module subslot srp command on the POS SPA that is installed in the lower-numbered slot/subslot combination. This SPA is considered the host SRP interface.

•

•

You only need to configure the hw-module subslot srp command on the host SRP interface—not on the mate SRP interface.

The host SRP interface becomes “Side A” of the SRP interface. The slot number of the side-A interface must be lower than the slot location of the SRP mate (side B) interface. Also, you must specify the side-A interface location for configuration of any SRP options.

19-36


Release 12.0(33)S, OL-8832-01, Rev. C9



Examples

•

•

•

•

•

The mate keyword does not apply to the 2-Port OC-48c/STM-16 POS SPA. For a single

2-Port OC-48c/STM-16 POS SPA, mating is done internally between the two SONET ports, and no mate cabling is required.

The SIP reads the information it receives from the hardware cable mating to validate the mate cable connectivity with your software configuration.

You must shut down the POS interface before enabling SRP.

When you change the SPA mode, the SPA automatically reloads.

The entire SPA operates either in POS mode or SRP mode—you cannot have some interfaces configured for POS mode, and other interfaces configured for SRP mode.

The following example shows how to enable SRP on a 1-Port OC-192c/STM-64 POS/RPR SPA:

Router(config)# interface pos 1/0/0



Router(config))# hw-module subslot 1/0 srp mate 1/1

Router(config)# interface srp 1/0/0

Related Commands Command interface srp

Description

Configures a POS/RPR SPA interface as an SRP interface.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-37


interface

interface

To configure an interface type and enter interface configuration mode, use the interface command in global configuration mode.

Standard Syntax interface type number [ name-tag ]

Analysis Module Network Module interface analysis-module slot / unit

Content Engine Network Module interface content-engine slot / unit

Cisco 7200 Series and Cisco 7500 Series with a Packet over SONET Interface Processor interface type slot / port

Cisco 7200 VXR Router used as a Router Shelf in a Cisco AS5800 Universal Access Server interface type router-shelf / slot / port

Cisco 7500 Series with Channelized T1 or E1 interface serial slot / port : channel-group

Cisco 7500 Series with Ports on VIP Cards interface type slot / port-adapter / port

To configure a subinterface, use this form of the interface global configuration command.

Cisco 7200 Series interface type slot / port .

subinterface-number [ multipoint | point-to-point ]

Cisco 7500 Series interface type slot / port-adapter .


Cisco 7500 Series with Ports on VIP Cards interface type slot / port-adapter / port .


Shared Port Adapters interface type slot / subslot / port [ .


19-38


Release 12.0(33)S, OL-8832-01, Rev. C9


interface

Syntax Description type number name-tag

Type of interface to be configured. See Table 19-1 .

Port, connector, or interface card number. On Cisco 4700 series routers, specifies the network interface module (NIM) or network processor module (NPM) number. The numbers are assigned at the factory at the time of installation or when added to a system, and can be displayed with the show interfaces command.

(Optional) Specifies the logic name to identify the server configuration so that multiple server configurations can be entered.

/

/ slot subslot unit

This optional argument is for use with the Redundant Link Manager

(RLM) feature.



Secondary slot number on a SIP where a SPA is installed.


Number of the daughter card on the network module. For analysis module and content engine (CE) network modules, always use 0.


/ port router-shelf

: channel-group

Refer to the appropriate hardware manual for port information. For

SPAs, refer to the corresponding “Specifying the Interface Address on a

SPA” topics in the platform-specific SPA software configuration guide.

Router shelf number in a Cisco AS5800 universal access server. Refer to the appropriate hardware manual for router shelf information.

Channel group number. Cisco 7500 series routers specify the channel group number in the range of 0 to 4 defined with the channel-group controller configuration command.

.

/ port-adapter subinterface-number

Port adapter number. Refer to the appropriate hardware manual for information about port adapter compatibility.

Subinterface number in the range 1 to 4294967293. The number that precedes the period (.) must match the number to which this subinterface belongs.

multipoint | point-to-point (Optional) Specifies a multipoint or point-to-point subinterface. There is no default.

Defaults No interface types are configured.


Note To use this command with the RLM feature, you must be in interface configuration mode.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-39


interface


10.0

11.0

12.0(3)T

12.2(13)T

12.2(15)T

12.3(7)T

12.2(20)S2

12.2(18)SXE

12.0(31)S

Modification

This command was introduced for the Cisco 7000 series routers.

This command was implemented on the Cisco 4000 series routers.

The optional name-tag argument was added for the RLM feature.

The content-engine keyword was added.

The lex keyword was removed because the LAN Extension feature is no longer available in Cisco IOS software.

The analysis-module keyword was added.

This command was implemented for SPAs on the Cisco 7304 router.

This command was implemented for SPAs on the Cisco 7600 series routers.

This command was implemented for SPAs on the Cisco 12000 series routers.

19-40


Release 12.0(33)S, OL-8832-01, Rev. C9


interface

Usage Guidelines This command does not have a no form.

Subinterfaces can be configured to support partially meshed Frame Relay networks. Refer to the

“Configuring Serial Interfaces” chapter in the Cisco IOS Interface and Hardware Component

Configuration Guide .

Table 19-1 displays the keywords that represent the types of interfaces that can be configured with the interface command. Replace the type argument with the appropriate keyword from the table.

Table 19-1 Interface Type Keywords

Keyword analysis-module async atm bri content-engine dialer ethernet fastethernet fddi gigabitethernet group-async hssi loopback null port-channel

Interface Type

Analysis module interface. The analysis module interface is a Fast

Ethernet interface on the router that connects to the internal interface on the Network Analysis Module (NAM). This interface cannot be configured for subinterfaces or for speed, duplex mode, and similar parameters. See the command-line interface (CLI) help for a list of valid parameters.

Port line used as an asynchronous interface.

ATM interface.

ISDN BRI. This interface configuration is propagated to each of the B channels. B channels cannot be individually configured. The interface must be configured with dial-on-demand commands in order for calls to be placed on that interface.

Content engine (CE) network module interface. The CE network module interface cannot be configured for subinterfaces or for speed, duplex mode, and similar parameters. See the command-line interface (CLI) help for a list of valid parameters. The content-engine keyword was formerly documented as the interface content-engine command.

Dialer interface.

Ethernet IEEE 802.3 interface.

100-Mbps Ethernet interface. The fastethernet keyword was formerly documented as the interface fastethernet command.

FDDI interface.

1000-Mbps Ethernet interface. The gigabitethernet keyword was formerly documented as the interface gigabitethernet command.

Master asynchronous interface. The group-async keyword was formerly documented as the interface group-async command.

High-Speed Serial Interface (HSSI).

Software-only loopback interface that emulates an interface that is always up. It is a virtual interface supported on all platforms. The number argument is the number of the loopback interface that you want to create or configure. There is no limit on the number of loopback interfaces that you can create.

Null interface.

Port channel interface. The port-channel keyword was formerly documented as the interface port-channel command.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-41


interface

Table 19-1

Keyword pos sdcc serial switch tokenring tunnel vg-anylan

Interface Type Keywords (continued)

Interface Type

Packet OC-3 interface on the Packet-over-SONET (POS) interface processor. The pos keyword was formerly documented as the interface pos command.

Section data communications channel interface.

Serial interface.

Switch interface.

Token Ring interface.

Tunnel interface; a virtual interface. The number argument is the number of the tunnel interface that you want to create or configure. There is no limit on the number of tunnel interfaces that you can create.

100VG-AnyLAN port adapter. The vg-anylan keyword was formerly documented as the interface vg-anylan command.

Using the analysis-module Keyword

The analysis module interface is used to access the NAM console for the initial configuration. After the

NAM IP parameters are configured, the analysis module interface is typically used only during NAM software upgrades and while troubleshooting if the NAM Traffic Analyzer is inaccessible.

Visible only to the Cisco IOS software on the router, the analysis module interface is an internal Fast

Ethernet interface on the router that connects to the internal NAM interface. The analysis module interface is connected to the router’s Peripheral Component Interconnect (PCI) backplane, and all configuration and management of the analysis module interface must be performed from the Cisco IOS

CLI.

Using the group-async Keyword

Using the group-async keyword, you create a single asynchronous interface with which other interfaces are associated as members using the group-range command. This one-to-many configuration allows you to configure all associated member interfaces by entering one command on the group master interface, rather than entering this command on each individual interface. You can create multiple group masters on a device; however, each member interface can be associated only with one group.

Using the port-channel Keyword

The Fast EtherChannel feature allows multiple Fast Ethernet point-to-point links to be bundled into one logical link to provide bidirectional bandwidth of up to 800 Mbps. You can configure the port-channel interface as you would any Fast Ethernet interface.

After you create a port-channel interface, you assign Fast Ethernet interfaces (up to four) to it. For information on how to assign a Fast Ethernet interface to a port-channel interface, refer to the channel-group interface configuration command.

Caution The port-channel interface is the routed interface. Do not enable Layer 3 addresses on the physical

Fast Ethernet interfaces. Do not assign bridge groups on the physical Fast Ethernet interfaces because it creates loops. Also, you must disable spanning tree.

19-42


Release 12.0(33)S, OL-8832-01, Rev. C9


interface

Examples

Caution With Release 11.1(20)CC, the Fast EtherChannel supports Cisco Express Forwarding (CEF) and distributed Cisco Express Forwarding (dCEF). We recommend that you clear all explicit ip route-cache distributed commands from the Fast Ethernet interfaces before enabling dCEF on the port-channel interface. Clearing the route cache gives the port-channel interface proper control of its physical Fast Ethernet links. When you enable CEF/dCEF globally, all interfaces that support

CEF/dCEF are enabled. When CEF/dCEF is enabled on the port-channel interface, it is automatically enabled on each of the Fast Ethernet interfaces in the channel group. However, if you have previously disabled CEF/dCEF on the Fast Ethernet interface, CEF/dCEF is not automatically enabled. In this case, you must enable CEF/dCEF on the Fast Ethernet interface.

As you work with the port-channel keyword, consider the following points:

• Currently, if you want to use the Cisco Discovery Protocol (CDP), you must configure it only on the port-channel interface and not on the physical Fast Ethernet interface.

• If you do not assign a static MAC address on the port-channel interface, the Cisco IOS software automatically assigns a MAC address. If you assign a static MAC address and then later remove it,

Cisco IOS software automatically assigns a MAC address.

Using the vg-anylan Keyword

The 100VG-AnyLAN port adapter provides a single interface port that is compatible with and specified by IEEE 802.12. The 100VG-AnyLAN port adapter provides 100 Mbps over Category 3 or Category 5 unshielded twisted-pair (UTP) cable with RJ-45 terminators, and supports IEEE 802.3 Ethernet packets.

You configure the 100VG-AnyLAN port adapter as you would any Ethernet or Fast Ethernet interface.

The 100VG-AnyLAN port adapter can be monitored with the IEEE 802.12 Interface MIB.

Serial Interface Example

The following example shows how to configure serial interface 0 with PPP encapsulation:

Router(config)# interface serial 0


Loopback Interace Example

The following example shows how to enable loopback mode and assigns an IP network address and network mask to the interface. The loopback interface established here will always appear to be up.

Router(config)# interface loopback 0


Cisco 7500 Series Router Ethernet Interface Processor Example

The following example shows how to configure Ethernet port 4 on the Ethernet Interface Processor (EIP) in slot 2 on the Cisco 7500 series router:

Router(config)# interface ethernet 2/4

Cisco 7500 Series Router Token Ring Interface Example

The following example shows how to configure the Token Ring interface processor in slot 1 on port 0 of a Cisco 7500 series router:

Router(config)# interface tokenring 1/0

Release 12.0(33)S, OL-8832-01, Rev. C9


19-43


interface

Network Analysis Module Interface Example

The following example configures an analysis module interface when the NAM router is in router slot 1:

Router(config)# interface analysis-module 1/0

Content Engine Network Module Interface Example

The following example configures an interface for a content engine network module in slot 1:

Router(config)# interface content-engine 1/0

Cisco 4700 Series Router Fast Ethernet Interface Example

The following example shows how to configure Fast Ethernet interface 0 for standard ARPA encapsulation (the default setting) on a Cisco 4700 series router:

Router(config)# interface fastethernet 0

Gigabit Ethernet Interface Example

The following example shows how to configure the Gigabit Ethernet interface for slot 0, port 0:

Router(config)# interface gigabitethernet 0/0

Asynchronous Group Master Interface Example

The following example shows how to define asynchronous group master interface 0:

Router(config)# interface group-async 0

Port Channel Interface Example

The following example shows how to create a port-channel interface with a channel group number of 1 and adds two Fast Ethernet interfaces to port-channel 1:

Router(config)# interface port-channel 1



Router(config)# interface fastethernet 1/0/0

Router(config-if)# channel-group 1



Router(config-if)# channel-group 1

Packet over SONET Interface Example

The following example shows how to specify the single Packet OC-3 interface on port 0 of the POS OC-3 port adapter in slot 2:

Router(config)# interface pos 2/0

100VG-AnyLAN Interface Example

The following example shows how to specify the 100VG-AnyLAN port adapter in the first port adapter in slot 1:

Router(config)# interface vg-anylan 1/0/0

Frame Relay Subinterface Example

The following example shows how to configure a partially meshed Frame Relay network. In this example, subinterface serial 0.1 is configured as a multipoint subinterface with two associated Frame

Relay permanent virtual connections (PVCs), and subinterface serial 0.2 is configured as a point-to-point subinterface.

Router(config)# interface serial 0

19-44


Release 12.0(33)S, OL-8832-01, Rev. C9


interface

Router(config-if)# encapsulation frame-relay


Router(config)# interface serial 0/0.1 multipoint


Router(config-if)# frame-relay interface-dlci 42 broadcast



Router(config)# interface serial 0/0.2 point-to-point



T1 Serial Interface Example

The following example shows how to configure circuit 0 of a T1 link for PPP encapsulation:

Router(config)# controller t1 4/1

Router(config-controller)# circuit 0 1


Router(config)# interface serial 4/1:0



SDCC Interface on a POS Shared Port Adapter Example

The following example configures the first interface (port 0) as a section data communications channel

(SDCC) interface on a POS SPA, where the SPA is installed in the top subslot (0) of the MSC, and the

MSC is installed in slot 4 of the Cisco 7304 router:

Router(config)# interface sdcc 4/3/0


Router(config-if)# logging event link-status

Router(config-if)# load-interval 30

Router(config-if)# no keepalive

Router(config-if)# no fair-queue

Router(config-if)# no cdp enable

Shared Port Adapter Interface Example

The following example configures the second interface (port 1) on a 4-Port 10/100 Fast Ethernet SPA for standard ARPA encapsulation (the default setting), where the SPA is installed in the bottom subslot

(1) of the MSC, and the MSC is installed in slot 2 of the Cisco 7304 router:


Related Commands Command channel-group channel-group (Fast

EtherChannel) clear interface controller group-range mac-address ppp show controllers content-engine

Description

Defines the timeslots that belong to each T1 or E1 circuit.

Assigns a Fast Ethernet interface to a Fast EtherChannel group.

Resets the hardware logic on an interface.

Configures an E1, J1, T1, or T3 controller and enters controller configuration mode.

Creates a list of asynchronous interfaces that are associated with a group interface on the same device.

Sets the MAC layer address.

Starts an asynchronous connection using PPP.

Displays controller information for CE network modules.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-45

interface


Command show interfaces show interfaces content-engine shutdown (RLM) slip

Description

Displays information about interfaces.

Displays basic interface configuration information for a CE network module.

Shuts down all of the links under the RLM group.

Starts a serial connection to a remote host using SLIP.

19-46


Release 12.0(33)S, OL-8832-01, Rev. C9


Release 12.0(33)S, OL-8832-01, Rev. C9

loopback (T3/E3 interface)


To loopback at various points in the transmit and receive path, use the loopback command in interface configuration mode on a 4-Port Clear Channel T3/E3 SPA. To stop the loopback, use the no form of this command.

PA-T3 Port Adapter loopback { dte | local | network { line | payload } | remote } no loopback

PA-E3 Port Adapter loopback { dte | local | network { line | payload }} no loopback

T3/E3 Shared Port Adapters loopback { dte | local | dual | network { line | payload } | remote } no loopback { dte | local | dual | network { line | payload } | remote }

Syntax Description dte local dual network { line | payload } remote

Loopback after the line interface unit (LIU) towards the terminal.

Loopback after going through the framer toward the terminal.

Sets both local loopback and network line loopback.

Sets the loopback toward the network before going through the framer

( line ) or after going through the framer ( payload ).

Sends FEAC to set remote in loopback.

Defaults No loopback by default.



11.1

11.3

12.2(11)YT

12.2(15)T

12.2S

Modification



This command was integrated into Cisco IOS Release 12.2(11)YT and implemented on the following platforms for E3: Cisco 2650XM,

Cisco 2651XM, Cisco 2691, Cisco 3660 series, Cisco 3725, and Cisco 3745 routers.




19-47



Release

12.2(18)SXE

12.0(31)S

Modification

This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers. The dual keyword was added.


Usage Guidelines Use the loopback command to diagnose problems on the local port, between the framer and the line interface unit (LIU) level.

Examples The following example creates a loopback on slot 5, bay 0, and port 0 after the LIU towards the terminal.



Router(config-if)# loopback dte

19-48


Release 12.0(33)S, OL-8832-01, Rev. C9


loopback remote line fdl


To send ANSI or BellCore loop codes to remote end using FDL (Facility Data Link) channel use the loopback remote line fdl commands. To stop the loopback, use the no form of this command. loopback remote line fdl [ ansi | bellcore ] no loopback

Syntax Description ansi bellcore

(Optional) Specify the ansi keyword to enable the remote line facility data link (FDL) ANSI bit loopback on the T1 channel, per the ANSI T1.403

Specification. Sends a repeating, 16-bit ESF data link code word (00001110

11111111 for FDL ANSI) to the remote end requesting that it enter into a network line loopback.

(Optional) Specify the bellcore keyword to enable the remote SmartJack loopback on the T1 channel, per the TR-TSY-000312 Specification. Sends a repeating, 16-bit ESF data link code word (00010010 11111111 for FDL

Bellcore) to the remote end requesting that it enter into a network line loopback.

Defaults No loopback by default or values.



12.0(32)S

Modification


Usage Guidelines Used to put the remote end in loopback so that BERT can be run from this router interface to test the integrity of the line. Valid only when T1 is in ESF framing.

Examples The following example creates a remote line ansi loopback on first channel group of t1 1 channel of path

1 of sonet controller, slot 1, bay 3 for a 1-Port Channelized OC-3/STM-1 SPA.




Router(config-ctrlr-sts1)# vtg 1 t1 1 loopback remote line fdl ansi

The following example creates a remote line ansi loopback on first channel group of t1 1 channel of t3 controller, slot 5, bay 0 and port 0 for a 4-Port and 2-Port Channelized T3 to DS0.



Router(config-controller)# t1 1 loopback remote line fdl ansi

Release 12.0(33)S, OL-8832-01, Rev. C9


19-49



Related Commands Command loopback remote line inband csu loopback remote line inband

(Smartjack)

Description

Sends an inband line loop code to remote end channel service unit

(CSU).

Sends inband 4-bit fac1 or 5-bit fac2 "Smartjack" loopcode to remote end.

19-50


Release 12.0(33)S, OL-8832-01, Rev. C9


loopback remote line inband (Smartjack)

loopback remote line inband (Smartjack)

To send inband 4-bit fac1 or 5-bit fac2 “Smartjack” loopcode to remote end use the loopback remote line inband commands. To stop the loopback, use the no form of this command. loopback remote line inband [ fac1 | fac2 ] no loopback

Syntax Description fac1 fac2

Specifies a Network Interface Unit (Smartjack) line loopback with 4-bit loop code.

Specifies a Network Interface Unit (Smartjack) line loopback with 5-bit loop code as per TR-TSY-000312 Specification.




12.0(33)S

Modification


Usage Guidelines Used to put the remote end in loopback so that BERT can be run from this router interface to test the integrity of the line.

Examples The following example sends inband 4-bit fac1 on first channel group of t1 1 channel of path 1 of sonet controller, slot 1, bay 3 for a 1-Port Channelized OC-3/STM-1 SPA.




Router(config-ctrlr-sts1)# vtg 1 t1 1 loopback remote line inband fac1

The following example sends inband 4-bit fac1 on first channel group of t1 1 channel of t3 controller, slot 5, bay 0 and port 0 for a 4-Port and 2-Port Channelized T3 to DS0.



Router(config-controller)# t1 1 loopback remote line inband fac1

Related Commands Command loopback remote line inband csu

Description

Sends an inband line loop code to remote end channel service unit

(CSU).

Release 12.0(33)S, OL-8832-01, Rev. C9


19-51


loopback remote line inband csu

loopback remote line inband csu

To send an inband loop code to remote end channel service unit (CSU) use the loopback remote line inband csu command. To stop the loopback, use the no form of this command. loopback remote line inband csu no loopback

Syntax Description csu (Optional)Specifies a CSU or equivalent device is attached to the router or access server on a MCI and SCI serial interface cards.

Defaults CSU line loopback



12.0(32)S

Modification


Usage Guidelines Used to put the remote end CSU in loopback so that BERT can be run from this router interface to test the integrity of the line. Valid in both SF and ESF framing.

Examples The following example sends inband loop code to remote end CSU on first channel group of t1 1 channel of path 1 of sonet controller, slot 1, bay 3 for a 1-Port Channelized OC-3/STM-1 SPA.




Router(config-ctrlr-sts1)# vtg 1 t1 1 loopback remote line inband csu

The following example sends loop code to remote end CSU on first channel group of t1 1 channel of t3 controller, slot 5, bay 0 and port 0 for a 4-Port and 2-Port Channelized T3 to DS0.



Router(config-controller)# t1 1 loopback remote line inband csu

Related Commands Command loopback remote line inband

(Smartjack)

Description

Sends inband 4-bit fac1 or 5-bit fac2 "Smartjack" loopcode to remote end.

19-52


Release 12.0(33)S, OL-8832-01, Rev. C9


loopback remote payload fdl ansi


To send ANSI payload loopback code to remote end using FDL channel use the loopback remote payload fdl ansi command. To stop the loopback, use the no form of this command. loopback remote payload fdl ansi no loopback

Syntax Description ansi Specify the ansi keyword to enable the remote line facility data link (FDL)

ANSI bit loopback on the T1 channel, per the ANSI T1.403 Specification.

Sends a repeating, 16-bit ESF data link code word (00001110 11111111 for

FDL ANSI) to the remote end requesting that it enter into a network line loopback.




12.0(32)S

Modification



Examples The following example sends ANSI payload loopback code to remote end using FDL channel on first channel group of t1 1 channel of path 1 of sonet controller, slot 1, bay 3 for a 1-Port Channelized

OC-3/STM-1 SPA.




Router(config-ctrlr-sts1)# vtg 1 t1 1 loopback remote payload fdl ansi

Release 12.0(33)S, OL-8832-01, Rev. C9


19-53



The following example sends ANSI payload loopback code to remote end using FDL channel on first channel group of t1 1 channel of t3 controller, slot 5, bay 0 and port 0 for a 4-Port and 2-Port Channelized

T3 to DS0.



Router(config-controller)# t1 1 loopback remote payload fdl ansi

19-54


Release 12.0(33)S, OL-8832-01, Rev. C9


loopback network payload


To put the T1/E1 controller looped towards the network with payload loop use the loopback network payload command. To stop the loopback, use the no form of this command. loopback network payload no loopback

Syntax Description payload Specifies payload loopback towards the network.


Command Modes Controller configuration and Interface configuration


12.0(33)S

Modification



Examples The following example sends payload loopback towards the network on first channel group of t1 1 channel of path 1 of sonet controller, slot 1, bay 3 for a 1-Port Channelized OC-3/STM-1 SPA.




Router(config-ctrlr-sts1)# vtg 1 t1 1 loopback network payload

Release 12.0(33)S, OL-8832-01, Rev. C9


19-55



The following example sends payload loopback towards the network on first channel group of t1 1 channel of t3 controller, slot 5, bay 0 and port 0 for a 4-Port and 2-Port Channelized T3 to DS0.



Router(config-controller)# t1 1 loopback network payload

The following example puts the serial interface configuration looped towards the network with payload on slot 5, bay 0, port 0 for 2-Port Clear Channel T3/E3 SPA.



Router(config-if)# loopback network payload

19-56


Release 12.0(33)S, OL-8832-01, Rev. C9


loopback remote esf (FDL Remote Loopback)

loopback remote esf (FDL Remote Loopback)

To activate a remote loopback, use the loopback remote esf command. The esf option is only available under T1 controllers when Extended Super Frame (ESF) is configured on the controller. When ESF framing is configured then loopback code can be sent through the Facility Data Link (FDL). To stop the loopback, use the no form of this command. loopback remote esf { line [ csu | niu ] | payload } no loopback

Syntax Description line csu niu payload

Activates remote line loopback by sending FDL code.

(Optional) CSU line loopback (per ANSI T1.403 Spec.)

(Optional) Sends remote line loopback to a Network Interface unit.

Activates remote payload loopback by sending Facility Data Link (FDL) code. FDL is a 4Kbps out-of-band signalling channel in ESF

Defaults CSU Line loopback



12.0(33)S

Modification


Usage Guidelines Used to send remote loopback code to the far end when ESF framing is configured, then loopback code can be sent through the Facility Date Link.

Examples The following example activates a remote line loopback by sending FDL code.



Router(config-controller)# loopback remote esf line

Related Commands Command loopback remote iboc

(In-Band Remote Loopback)

Description

Sends inband line loopback code to a Network Interface Unit

(Smartjack device) on the far end.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-57


loopback remote iboc (In-Band Remote Loopback)

loopback remote iboc (In-Band Remote Loopback)

To send in-band line loopback code to the far end, use the loopback remote iboc command. The fac1 and fac2 options are used to send in-band line loopback code to a Network Interface Unit (SmartJack device) on the far-end. Use the no loopback command to stop the in-band loop code.

loopback remote iboc [ csu | fac1 | fac2 ] no loopback

Syntax Description csu fac1 fac2

CSU line loopback (per ANSI T1.403 Spec.).

Specifies Network Interface Unit (Smartjack device) line loopback with

4-bit loop code.

Specifies Network Interface Unit (Smartjack device) line loopback with

5-bit loop code as per TR-TSY-000312 Spec.).

Defaults

Command Modes Controller configuration s

Command History

CSU Line loopback

Release

12.0(33)S

Modification


Usage Guidelines Used to send in-band line loopback code to a Network Interface Unit (Smartjack device) on the far end.

Examples The following example sends a remote inband CSU loop code with IBOC.



Router(config-controller)# loopback remote iboc csu

The following example stops a remote inband loop code with IBOC.



Router(config-controller)# no loopback

Related Commands Command loopback remote esf (FDL

Remote Loopback)

Description

Activates a remote loopback under T1 controllers when ESF is configure.

19-58


Release 12.0(33)S, OL-8832-01, Rev. C9


mdl

mdl

To configure the Maintenance Data Link (MDL) message defined in the ANSI T1.107a-1990 specification, use the mdl command in controller configuration mode.

mdl [ string { eic | fic | generator | lic | pfi | port | unit } string ] | [ transmit { idle-signal | path | test-signal }] no mdl [ string { eic | fic | generator | lic | pfi | port | unit } string ] | [ transmit { idle-signal | path | test-signal }]

Syntax Description string eic string string fic string string generator string Specifies the Generator number string sent in the MDL Test Signal message; can be up to 38 characters.

string lic string string pfi string

Specifies the Location Identification Code; can be up to 11 characters.

Specifies the Path Facility Identification Code sent in the MDL Path message; can be up to 38 characters.

string port string

Specifies the Equipment Identification Code; can be up to 10 characters.

Specifies the Frame Identification Code; can be up to 10 characters.

string unit string transmit idle-signal transmit path transmit test-signal

Specifies the Port number string sent in the MDL Idle Signal message; can be up to 38 characters.

Specifies the Unit Identification Code; can be up to 6 characters.

Enables MDL Idle-Signal message transmission.

Enables MDL Path message transmission.

Enables MDL Test-Signal message transmission.




11.3

12.1(13)EX

12.2(11)YT

12.2(15)T

12.2(18)S

12.2(18)SXE

12.0(31)S

Modification


This command was introduced on the Cisco 7304 router.

This command was integrated into Cisco IOS Release 12.2(11)YT and implemented on the following platforms: Cisco 2650XM, Cisco 2651XM,

Cisco 2691, Cisco 3660 series, Cisco 3725, and Cisco 3745 routers.


This command was introduced on Cisco 7304 routers running Cisco IOS

Release 12.2 S.



Release 12.0(33)S, OL-8832-01, Rev. C9


19-59


mdl

Usage Guidelines Use the mdl command to send msgs in maintainance data link in T3 c-bit framing mode.

Examples


The following example sends a test signal on the maintenance data link.



Router(config-controller)# mdl transmit test-signal

Command controller show controllers serial

Description



19-60


Release 12.0(33)S, OL-8832-01, Rev. C9


show controller dwdm


To display serial controller statistics, use the show controller dwdm command in privileged EXEC mode.

Standard Syntax show controller dwdm < slot> / <subslot> /< port > [ g709 { registers } | optics { registers } | wavelegth ]

Syntax Description slot subslot port g709 g709 registers optics optics registers wavelegth



Subslot in the line card.



Displays detailed information about G.709 OTN protocol alarms and counters for Bit Errors, along with the FEC statistics and threshold based alerts.

Displays g709 register information.

Displays detailed information for the optics regarding the transponder output power level, input power level, wavelength, and laser bias current monitoring.

Displays transponder register information.

Displays the wavelength channel number map table.




12.0(33)S

Modification

This command was introduced to support the 1-Port 10-Gigabit Ethernet

DWDM SPA on the Cisco 12000 series routers.

Usage Guidelines The output from the show controller dwdm command provides error and alarm information that is useful in troubleshooting line problems.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-61



The information displayed is generally useful for diagnostic tasks performed by Cisco Systems technical support personnel only. The show controller dwdm command also displays configuration information such as for G709, optical parameters, and registers.

Example of the show controller dwdm Command on the Cisco 12000 Series Router

The following example shows the details about the functional areas for the DWDM controller.

Router# show controller dwdm ?

3/0/0 dwdm Interface Instance

Router#sh controller dwdm 3/0/0 ?

g709 show G709 info

optics Show transponder info

wavelegth-map wavelengh channel number map table

| Output Modifiers

<cr>

The following is a sample output from the show controller dwdm 3/0/0 command on the Cisco 12000

Series Router:

Router# show controller dwdm 3/0/0

Port:dwdm0_0_0_0 DWDM info

Loopback: None

G709 status

OTU

LOS = 0 LOF = 0 LOM = 0

AIS = 0 BDI = 0

TIM = 0 EOC = 0

ODU

AIS = 0 BDI = 0 TIM = 0

EOC = 0 OCI = 0 LCK = 0

PTIM = 0


EC = 0 UC= 0










Optics

optics type: ***

clock info: ***


RX Power = 0 dbm

TX power = 0 dbm







19-62


Release 12.0(33)S, OL-8832-01, Rev. C9





The following is a sample output from the show controller dwdm 3/0/0 g709 command on the

Cisco 12000 Series Router:

Router# show controller dwdm 3/0/0 g709

G709 status

OTU

LOS = 0 LOF = 0 LOM = 0

AIS = 0 BDI = 0

TIM = 0 EOC = 0

ODU

AIS = 0 BDI = 0 TIM = 0

EOC = 0 OCI = 0 LCK = 0

PTIM = 0


EC = 0 UC= 0










The following is a sample output from the show controller dwdm 3/0/0 g709 registers command on the


Router# show controller dwdm 3/0/0 g709 registers

G709 framer register info

Supported C-band wavelength table

---------------------------------------channel frequency wavelength

Num (THZ) (nm)

----------------------------------------

01 196.00 1529.55

--------------------------------------------

02 195.95 1529.94

--------------------------------------------

03 195.90 1530.33

--------------------------------------------

04 195.85 1530.72

--------------------------------------------

05 195.80 1531.12

--------------------------------------------

06 195.75 1531.51

--------------------------------------------

07 195.70 1531.90

--------------------------------------------

08 195.65 1532.29

--------------------------------------------

09 195.60 1532.68

The following is a sample output from the show controller dwdm 3/0/0 optics command on the


Router# show controller dwdm 3/0/0 optics

Optics

Release 12.0(33)S, OL-8832-01, Rev. C9


19-63



optics type: ***

clock info: ***


RX Power = 0 dbm

TX power = 0 dbm









The following is a sample output from the show controller dwdm 3/0/0 wavelegth-map command on the Cisco 12000 Series Router:

Router# show controller dwdm 3/0/0 wavelegth-map

Supported C-band wavelength table

---------------------------------------channel frequency wavelength

Num (THZ) (nm)

----------------------------------------

01 196.00 1529.55

--------------------------------------------

02 195.95 1529.94

--------------------------------------------

03 195.90 1530.33

--------------------------------------------

04 195.85 1530.72

--------------------------------------------

05 195.80 1531.12

--------------------------------------------

06 195.75 1531.51

--------------------------------------------

07 195.70 1531.90

--------------------------------------------

08 195.65 1532.29

--------------------------------------------

09 195.60 1532.68

--------------------------------------------

10 195.55 1533.07

--------------------------------------------

11 195.50 1533.47

--------------------------------------------

12 195.45 1533.86

--------------------------------------------

13 195.40 1534.25

--------------------------------------------

14 195.35 1534.64

--------------------------------------------

15 195.30 1535.04

--------------------------------------------

16 195.25 1535.43

--------------------------------------------

17 195.20 1535.82

--------------------------------------------

18 195.15 1536.22

--------------------------------------------

19 195.10 1536.61

--------------------------------------------

19-64


Release 12.0(33)S, OL-8832-01, Rev. C9



20 195.05 1537.00

--------------------------------------------

21 195.00 1537.40

--------------------------------------------

22 194.95 1537.79

--------------------------------------------

23 194.90 1538.19

--------------------------------------------

24 194.85 1538.58

--------------------------------------------

25 194.80 1538.98

--------------------------------------------

26 194.75 1539.37

--------------------------------------------

27 194.70 1539.77

--------------------------------------------

28 194.65 1540.16

--------------------------------------------

29 194.60 1540.56

--------------------------------------------

30 194.55 1540.95

--------------------------------------------

31 194.50 1541.35

--------------------------------------------

32 194.45 1541.75

--------------------------------------------

33 194.40 1542.14

--------------------------------------------

34 194.35 1542.54

--------------------------------------------

35 194.30 1542.94

--------------------------------------------

36 194.25 1543.33

--------------------------------------------

37 194.20 1543.73

--------------------------------------------

38 194.15 1544.13

--------------------------------------------

39 194.10 1544.53

--------------------------------------------

40 194.05 1544.92

--------------------------------------------

41 194.00 1545.32

--------------------------------------------

42 193.95 1545.72

--------------------------------------------

43 193.90 1546.12

--------------------------------------------

44 193.85 1546.52

--------------------------------------------

45 193.80 1546.92

--------------------------------------------

46 193.75 1547.32

--------------------------------------------

47 193.70 1547.72

--------------------------------------------

48 193.65 1548.11

--------------------------------------------

49 193.60 1548.51

--------------------------------------------

50 193.55 1548.91

--------------------------------------------

51 193.50 1549.32

--------------------------------------------


Release 12.0(33)S, OL-8832-01, Rev. C9 19-65


52 193.45 1549.72

--------------------------------------------

53 193.40 1550.12

--------------------------------------------

54 193.35 1550.52

--------------------------------------------

55 193.30 1550.92

--------------------------------------------

56 193.25 1551.32

--------------------------------------------

57 193.20 1551.72

--------------------------------------------

58 193.15 1552.12

--------------------------------------------

59 193.10 1552.52

--------------------------------------------

60 193.05 1552.93

--------------------------------------------

61 193.00 1553.33

--------------------------------------------

62 192.95 1553.73

--------------------------------------------

63 192.90 1554.13

--------------------------------------------

64 192.85 1554.54

--------------------------------------------

65 192.80 1554.94

--------------------------------------------

66 192.75 1555.34

--------------------------------------------

67 192.70 1555.75

--------------------------------------------

68 192.65 1556.15

--------------------------------------------

69 192.60 1556.55

--------------------------------------------

70 192.55 1556.96

--------------------------------------------

71 192.50 1557.36

--------------------------------------------

72 192.45 1557.77

--------------------------------------------

73 192.40 1558.17

--------------------------------------------

74 192.35 1558.58

--------------------------------------------

75 192.30 1558.98

--------------------------------------------

76 192.25 1559.39

--------------------------------------------

77 192.20 1559.79

--------------------------------------------

78 192.15 1560.20

--------------------------------------------

79 192.10 1560.61

--------------------------------------------

80 192.05 1561.01

--------------------------------------------

Supported L-band wavelength table

----------------------------------------channel frequency wavelength

Num (THZ) (nm)

-----------------------------------------

01 190.90 1570.42

19-66



Release 12.0(33)S, OL-8832-01, Rev. C9



-----------------------------------------

02 190.85 1570.83

-----------------------------------------

03 190.80 1571.24

-----------------------------------------

04 190.75 1571.65

-----------------------------------------

05 190.70 1572.06

-----------------------------------------

06 190.65 1572.48

-----------------------------------------

07 190.60 1572.89

-----------------------------------------

08 190.55 1573.30

-----------------------------------------

09 190.50 1573.71

-----------------------------------------

10 190.45 1574.13

-----------------------------------------

11 190.40 1574.54

-----------------------------------------

12 190.35 1574.95

-----------------------------------------

13 190.30 1575.37

-----------------------------------------

14 190.25 1575.78

-----------------------------------------

15 190.20 1576.20

-----------------------------------------

16 190.15 1576.61

-----------------------------------------

17 190.10 1577.03

-----------------------------------------

18 190.05 1577.44

-----------------------------------------

19 190.00 1577.86

-----------------------------------------

20 189.95 1578.27

-----------------------------------------

21 189.90 1578.69

-----------------------------------------

22 189.85 1579.10

-----------------------------------------

23 189.80 1579.52

-----------------------------------------

24 189.75 1579.93

-----------------------------------------

25 189.70 1580.35

-----------------------------------------

26 189.65 1580.77

-----------------------------------------

27 189.60 1581.18

-----------------------------------------

28 189.55 1581.60

-----------------------------------------

29 189.50 1582.02

-----------------------------------------

30 189.45 1582.44

-----------------------------------------

31 189.40 1582.85

-----------------------------------------

32 189.35 1583.27

-----------------------------------------

33 189.30 1583.69


Release 12.0(33)S, OL-8832-01, Rev. C9 19-67


-----------------------------------------

34 189.25 1584.11

-----------------------------------------

35 189.20 1584.53

-----------------------------------------

36 189.15 1584.95

-----------------------------------------

37 189.10 1585.36

-----------------------------------------

38 189.05 1585.78

-----------------------------------------

39 189.00 1586.20

-----------------------------------------

40 188.95 1586.62

-----------------------------------------

41 188.90 1587.04

-----------------------------------------

42 188.85 1587.46

-----------------------------------------

43 188.80 1587.88

-----------------------------------------

44 188.75 1588.30

-----------------------------------------

45 188.70 1588.73

-----------------------------------------

46 188.65 1589.15

-----------------------------------------

47 188.60 1589.57

-----------------------------------------

48 188.55 1589.99

-----------------------------------------

49 188.50 1590.41

-----------------------------------------

50 188.45 1590.83

-----------------------------------------

51 188.40 1591.26

-----------------------------------------

52 188.35 1591.68

-----------------------------------------

53 188.30 1592.10

-----------------------------------------

54 188.25 1592.52

-----------------------------------------

55 188.20 1592.95

-----------------------------------------

56 188.15 1593.37

-----------------------------------------

57 188.10 1593.79

-----------------------------------------

58 188.05 1594.22

-----------------------------------------

59 188.00 1594.64

-----------------------------------------

60 187.95 1595.06

-----------------------------------------

61 187.90 1595.49

-----------------------------------------

62 187.85 1595.91

-----------------------------------------

63 187.80 1596.34

-----------------------------------------

64 187.75 1596.76

-----------------------------------------

65 187.70 1597.19

19-68



Release 12.0(33)S, OL-8832-01, Rev. C9



-----------------------------------------

66 187.65 1597.62

-----------------------------------------

67 187.60 1598.04

-----------------------------------------

68 187.55 1598.47

-----------------------------------------

69 187.50 1598.89

-----------------------------------------

70 187.45 1599.32

-----------------------------------------

71 187.40 1599.75

-----------------------------------------

72 187.35 1600.17

-----------------------------------------

73 187.30 1600.60

-----------------------------------------

74 187.25 1601.03

-----------------------------------------

75 187.20 1601.46

-----------------------------------------

76 187.15 1601.88

-----------------------------------------

77 187.10 1602.31

-----------------------------------------

78 187.05 1602.74

-----------------------------------------

79 187.00 1603.17

-----------------------------------------

80 186.95 1603.60

-----------------------------------------

Related Commands Command controller dwdm

Description

Configures DWDM parameters on a 1-Port 10-Gigabit Ethernet

DWDM SPA.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-69


show controllers pos


To display information about the Packet over SONET (POS) controllers, use the show controllers pos command in privileged EXEC mode.

Cisco 7500 Series Routers show controllers pos [ slot / port-adapter / port ] [ details | pm [ time-interval ]]

Cisco 12000 Series Routers show controllers pos [ slot / port ] [ details | pm [ time-interval ] [ time-interval ]]

POS Shared Port Adapters show controllers pos [ slot / subslot / port [ / sub_int ]] [ alarm | details | pm [ time-interval ]

[ time-interval ]]

Syntax Description slot / port-adapter / port slot / port

(Optional) Cisco 7500 Series Routers

Number of the chassis slot that contains the POS interface (for example,

2/0/0), where:

• slot —Chassis slot number.

•

•

/ port-adapter— Port adapter number.

/ port— Port or interface number.

Refer to the appropriate hardware manual for slot and port information, and port adapter compatibility.

(Optional) Cisco 12000 Series Routers


4/0), where:


• / port— Port or interface number.

Refer to the appropriate hardware manual for slot and port information.

19-70


Release 12.0(33)S, OL-8832-01, Rev. C9


show controllers pos slot / subslot / port [ / sub_int ] alarm details pm time-interval time-interval

(Optional) POS Shared Port Adapters

Number of the chassis slot that contains the POS interface (for example

4/3/0), where:


Refer to the appropriate hardware manual for slot information. For

SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding “Identifying Slots and Subslots for SIPs and

SPAs” topic in the platform-specific SPA software configuration guide.

•

•

/ subslot— Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.


/ port —Port or interface number.

For SPAs, refer to the corresponding “Specifying the Interface

Address on a SPA” topics in the platform-specific SPA software configuration guide.

• / sub_int —(Optional) Subinterface number.

(Optional) Displays SONET/SDH alarm event counters.

(Optional) In addition to the normal information displayed by the show controllers pos command, the details keyword provides a hexadecimal and ASCII “dump” of the path trace buffer.

(Optional) Displays general information of the SONET performance monitoring statistics if the command is executed without specifying the time-interval argument. To view the POS interface details between two specific time intervals, specify the starting and ending time-interval. The

24-hour period is considered from the time the router boots-up.

To view the POS interface details for only a particular time-interval, enter the time-interval and press the Enter key. For example, to view the POS interface details for time-interval 6, execute the command show controllers pos 1/0 pm 6.

(Optional) Specify the initial time-interval from when you want to start viewing the POS interface details on a Cisco 12000 Series Routers or on

POS Shared Port Adapters. Number of the SONET MIB 15-minute time interval in the range from 1 to 96.

(Optional) Specify the ending time-interval till when you want to view the

POS interface details on a Cisco 12000 Series Routers or on POS Shared

Port Adapters. Number of the SONET MIB 15-minute time interval in the range from 1 to 96.

Defaults If you do not specify any slot addressing, information for all installed POS interfaces is displayed.


Release 12.0(33)S, OL-8832-01, Rev. C9


19-71




11.1CC

12.2S

12.2(25)S3

Modification



This command was integrated into Cisco IOS Release 12.2(25)S3 to support SPAs on the Cisco 7304 router. The command was modified to support a new addressing format for SPAs on the Cisco 7304 router.

12.2(18)SXE This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers and Catalyst 6500 series switches.

12.0(31)S This command was integrated into Cisco IOS Release 12.0(31)S to support SPAs on the Cisco 12000 series routers.

12.2(33)SRA This command was integrated into Cisco IOS Release 12.2(33)SRA.

12.0(32)SY6 Added a starting and ending <time-interval> arguments in the command for the Cisco

12000 Series Routers and for POS Shared Port Adapters.

Change in command output executed on a Cisco 12000 Series Router and on POS

Shared Port Adapters. The command output displays POS interface details for each of the time-intervals between the starting and ending time-intervals.

Usage Guidelines The show controllers pos command with the pm keyword displays SONET performance monitoring statistics accumulated at 15-minute intervals, and these statistics can be queried using Simple Network

Management Protocol (SNMP) tools. The performance monitoring statistics are collected according to the RFC 1595 specification.

The information that this command displays is generally useful only for diagnostic tasks performed by

Cisco Systems technical support personnel.

Use the show controllers pos command with the starting and ending <time-interval> arguments to view the POS interface details for each of the time-intervals between the specified range on a Cisco 12000

Series Router or on POS Shared Port Adapters. Each time-interval constitutes of 15 minutes and the statistics are polled from the time the Router comes-up. The <time-interval> range must be between 1 to 96. The command is executed from Privilege Exec mode.

Execute following command to display performance monitoring statistics for each of the tme-intervals between 1 to 96 on a Cisco 12000 Series Router.

Router# show controllers pos 1 / 0 pm 1 96

Execute following command to display performance monitoring statistics for each of the tme-intervals between 1 to 96 on POS Shared Port Adapters.

Router# show controllers pos 4 / 3/0 pm 1 96

Execute the following command from the Privielge Exec Mode to view the POS interface details for a time-interval 4 on a Cisco 12000 Series Router.

Router# show controllers pos 1 / 0 pm 4

Examples Example of the show controllers pos Command on the Cisco 7500 Series Router

The following is sample output from the show controllers pos command on a Cisco 7500 series router:

Router# show controllers pos

POS2/0/0

19-72


Release 12.0(33)S, OL-8832-01, Rev. C9



SECTION

LOF = 0 LOS = 2335 BIP(B1) = 77937133

LINE

AIS = 2335 RDI = 20 FEBE = 3387950089 BIP(B2) = 1622825387

PATH

AIS = 2340 RDI = 66090 FEBE = 248886263 BIP(B3) = 103862953


Active Defects: B2-TCA B3-TCA

Active Alarms: None

Alarm reporting enabled for: B1-TCA

APS

COAPS = 12612784 PSBF = 8339


Rx(K1/K2): 00/CC Tx(K1/K2): 00/00

S1S0 = 03, C2 = 96

CLOCK RECOVERY

RDOOL = 64322060

State: RDOOL_state = True

PATH TRACE BUFFER: UNSTABLE

Remote hostname :

Remote interface:

Remote IP addr :

Remote Rx(K1/K2): ../.. Tx(K1/K2): ../..



Table 19-2 describes the fields shown in this display.

Table 19-2 show controllers pos Field Descriptions

Field

POS x/y/z

LOF

LOS

BIP(B1)/BIP(B2)/BIP(B3)

Description

Slot number of the POS interface.

Section loss of frame is detected when a severely error framing (SEF) defect on the incoming SONET signal persist for 3 milliseconds.

Section loss of signal is detected when an all-zeros pattern on the incoming SONET signal lasts 19 plus or minus 3 microseconds or longer. This defect might also be reported if the received signal level drops below the specified threshold.

Bit interleaved parity (BIP).

For B1, the BIP error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B1 byte of the following frame.

Differences indicate that section-level bit errors have occurred.

For B2, the BIP error report is calculated by comparing the BIP-8/24 code with the BIP-8 code extracted from the B2 byte of the following frame. Differences indicate that line-level bit errors have occurred.

For B3, the BIP error report is calculated by comparing the BIP-8 code with the BIP-8 code extracted from the B3 byte of the following frame.

Differences indicate that path-level bit errors have occurred.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-73



Table 19-2 show controllers pos Field Descriptions (continued)

Field

AIS

RDI

Description

Alarm indication signal.

A line alarm indication signal is sent by the section terminating equipment (STE) to alert the downstream line terminating equipment

(LTE) that a loss of signal (LOS) or loss of frame (LOF) defect has been detected on the incoming SONET section.

A path alarm indication signal is sent by the LTE to alert the downstream path terminating equipment (PTE) that it has detected a defect on its incoming line signal.

Remote defect indication.

A line remote defect indication is reported by the downstream LTE when it detects LOF, LOS, or AIS.

A path remote defect indication is reported by the downstream PTE when it detects a defect on the incoming signal.

Far end block errors.

FEBE

LOP

NEWPTR

Line FEBE (accumulated from the M0 or M1 byte) is reported when the downstream LTE detects BIP(B2) errors.

Path FEBE (accumulated from the G1 byte) is reported when the downstream PTE detects BIP(B3) errors.

Path loss of pointer is reported as a result of an invalid pointer (H1, H2) or an excess number of new data flag (NDF)-enabled indications.

Inexact count of the number of times that the SONET framer has validated a new SONET pointer value (H1, H2).

PSE

NSE

Active Defects

Active Alarms

Inexact count of the number of times that the SONET framer has detected a positive stuff event in the received pointer (H1, H2).

Inexact count of the number of times that the SONET framer has detected a negative stuff event in the received pointer (H1, H2).

List of all currently active SONET defects.

List of current alarms as enforced by Sonet Alarm Hierarchy.

Alarm reporting enabled for List of alarms for which you enabled reporting with the pos report interface command.

APS Automatic protection switching.

COAPS

PSBF

An inexact count of the number of times that a new APS value has been detected in the K1, K2 bytes.

An inexact count of the number of times that a protection switching byte failure has been detected (no three consecutive SONET frames contain identical K1 bytes).

PSBF_state

Rx(K1/K2)/Tx(K1/K2)

S1S0

C2

Protection switching byte failure state.

Contents of the received and transmitted K1 and K2 bytes.

The two S bits received in the last H1 byte.

The value extracted from the SONET path signal label byte (C2).

19-74


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-2

BER thresholds

TCA thresholds show controllers pos Field Descriptions (continued)

Field

CLOCK RECOVERY

PATH TRACE BUFFER

Description

The SONET clock is recovered using information in the SONET overhead. RDOOL is an inexact count of the number of times that

Receive Data Out Of Lock has been detected, which indicates that the clock recovery phased lock loop is unable to lock to the receive stream.

SONET path trace buffer is used to communicate information regarding the remote host name, interface name and number, and IP address. This is a Cisco-proprietary use of the J1 (path trace) byte.

List of the bit error rate (BER) thresholds that you configured with the pos threshold interface command.

List of the threshold crossing alarms (TCAs) that you configured with the pos threshold interface command.

Example of the show controllers pos Command on a POS Shared Port Adapter

The following is sample output from the show controllers pos command on a Cisco 7600 series router for POS interface 4/3/0 (which is the interface for port 0 of the SPA in subslot 3 of the SIP in chassis slot

4):


POS4/3/0

SECTION

LOF = 0 LOS = 0 BIP(B1) = 65535

LINE

AIS = 0 RDI = 0 FEBE = 65535 BIP(B2) = 16777215

PATH

AIS = 0 RDI = 0 FEBE = 65535 BIP(B3) = 65535




Active Alarms: None


Framing: SONET

APS

COAPS = 1 PSBF = 0


Rx(K1/K2): 00/00 Tx(K1/K2): 00/00


S1S0 = 00, C2 = CF


CLOCK RECOVERY

RDOOL = 0



Remote hostname : woodson



Remote Rx(K1/K2): 00/00 Tx(K1/K2): 00/00




Release 12.0(33)S, OL-8832-01, Rev. C9


19-75



Table 19-2 describes the fields shown in this display.

Example of the show controllers pos alarm Command on the Cisco 7600 Series Router

The following is sample output from the show controllers pos alarm command that displays

SONET/SDH alarm event counters on a Cisco 7600 series router:

Router# show controllers pos3/2/0 alarm

POS3/2/0

Alarm Event Statistics:

SECTION

LOF = 0 LOS = 0 B1-TCA = 0

LINE

AIS = 0 RDI = 0 RDOOL = 0

SF = 0 SD = 0 B2-TCA = 0

PATH

AIS = 0 RDI = 0 LOP = 0 B3-TCA = 0

PLM = 0 UNEQ = 0

Example of the show controllers pos pm Command on the Cisco 12000 Series Router

The following is sample output from the show controllers pos pm command that displays performance monitoring statistics on a Cisco 12000 series router:

Router# show controllers pos 1/0 pm

POS1/0

Medium is SONET

Line coding is RZ, Line type is LONG SM

Data in current interval (516 seconds elapsed)

SECTION ( NO DEFECT )

515 Errored Secs, 515 Severely Err Secs

0 Coding Violations, 515 Sev Err Framing Secs

LINE ( NO DEFECT )


0 Coding Violations, 0 Unavailable Secs

FAR END LINE



PATH ( NO DEFECT )



FAR END PATH



Table 19-3 describes the fields shown in the display.

Table 19-3

Field

POS x/y

Line coding

Line type show controllers pos pm Field Descriptions

Description


Shows the current line encoding type, either return to zero (RZ) or nonreturn to zero (NRZ).

Line type for this interface. Optical line types can be either long range

(LONG) or short range (SHORT), and either single mode (SM) or multimode

(MM).

19-76


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-3 show controllers pos pm Field Descriptions (continued)

Field Description

Data in current interval Shows the current accumulation period, which rolls into the 24-hour accumulation every 15 minutes. Accumulation period is from 1 to 900 seconds. The oldest 15-minute period falls off the back of the 24-hour accumulation buffer.

Errored Secs An errored second is a second in which one of the following is detected:

• One or more coding violations.

Severely Err Secs

• One or more incoming defects (for example, a severely errored frame

[SEF] defect, an LOS defect, an AIS defect, or an LOP defect).

A severely errored second (SES) is a second with one of the following errors:

Coding Violations

• A certain number of coding violations. The number is dependent on the line rate and the BER.

A certain number of incoming defects.

•

Number of coding violations for the current interval. Coding violations are defined as BIP errors that are detected in the incoming signal. The coding violations counter is incremented for each BIP error detected.

Sev Err Framing Secs Severely errored framing seconds (SEFS) are seconds with one or more SEF defects.

Unavailable Secs Total number of seconds for which the interface is unavailable. The interface is considered to be unavailable after a series of ten consecutive SESs.

Example of the show controllers pos pm <time-interval> <time-interval> command on the Cisco 12000 Series

Router

The following is a sample output from the show controllers pos pm 1 96 command that displays performance monitoring statistics for each of the time-intervals between 1 to 96 on a Cisco 12000 series router:

Router# show controllers pos 1/7 pm 1 96

POS1/7

Medium is SONET

Line coding is NRZ, Line type is OTHER

Data in interval 1

SECTION



LINE


0 Coding Violations, 0 Unavailabe Secs

FAR END LINE



PATH



FAR END PATH



Data in interval 2

SECTION

Release 12.0(33)S, OL-8832-01, Rev. C9


19-77





LINE



FAR END LINE



PATH



FAR END PATH




Table 19-4 show controllers pos pm Field Descriptions

Field

POS x/y

Line coding

Line type

Data in interval <x> x=Time-interval number

Errored Secs

Description


Shows the current line encoding type, either return to zero (RZ) or nonreturn to zero (NRZ).

Line type for this interface. Optical line types can be either long range

(LONG) or short range (SHORT), and either single mode (SM) or multimode

(MM).

Shows the interval number for which the performance monitoring statistics are displayed subsequetly. Each interval is of 15-minutes which accumulates the statistics from 1 to 900 seconds over a period of 24 hours. Statistical data is counted from the time the router comes-up. The oldest 15-minute period falls off the back of the 24-hour accumulation buffer.

An errored second is a second in which one of the following is detected:

• One or more coding violations.

Severely Err Secs

• One or more incoming defects (for example, a severely errored frame

(SEF) defect, an LOS defect, an AIS defect, or an LOP defect).

A severely errored second (SES) is a second with one of the following errors:

• A certain number of coding violations. The number is dependent on the line rate and the BER.

Coding Violations

• A certain number of incoming defects.

Number of coding violations for the current interval. Coding violations are defined as BIP errors that are detected in the incoming signal. The coding violations counter is incremented for each BIP error detected.

Sev Err Framing Secs Severely errored framing seconds (SEFS) are seconds with one or more SEF defects.

Unavailable Secs Total number of seconds for which the interface is unavailable. The interface is considered to be unavailable after a series of ten consecutive SESs.

19-78


Release 12.0(33)S, OL-8832-01, Rev. C9



Command pos report pos threshold


Description

Permits selected SONET alarms to be logged to the console for a POS interface.

Sets the BER threshold values of specified alarms for a POS interface.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-79


show controllers serial


To display serial controller statistics, use the show controllers serial command in privileged EXEC mode.

Standard Syntax show controllers serial [ slot / port ]

Cisco 7000 Series Routers with the RSP7000 and RSP7000CI and Cisco 7500 Series Routers show controllers serial [ slot / port-adapter / port ]

T3/E3 Shared Port Adapters and 2-Port and 4-Port Channelized T3 SPA in Unchannelized Mode show controllers serial [ slot / subslot / port ]

Channelized T3 Shared Port Adapters show controllers serial [ slot / subslot / port / t1-number ]

Syntax Description slot port-adapter

/ subslot port t1-number

(Optional) Chassis slot number.


(Optional) On Cisco 7500 series routers and Cisco 7000 series routers with the RSP7000 and RSP7000CI, the location of the port adapter on a Versatile

Interface Processor (VIP). The value can be 0 or 1.

(Optional) Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.


(Optional) Port or interface number.


(Optional) Logical T1 number in channelized mode.

For SPAs, refer to the corresponding “Specifying the Interface Address on a

SPA” topics in the platform-specific SPA software configuration guide.



19-80


Release 12.0(33)S, OL-8832-01, Rev. C9




10.0

11.1CA

12.2S

12.2(18)SXE

12.0(31)S

Modification


This command was modified to include support for the PA-E3 and PA-T3 port adapters.


This command was integrated into Cisco IOS Release 12.2(18)SXE and introduced a new output for interfaces on the serial SPAs on the Cisco 7600 series routers.


Usage Guidelines The output from the show controllers serial command provides error and alarm information that is useful in troubleshooting line problems.

The information displayed is generally useful for diagnostic tasks performed by Cisco Systems technical support personnel only. For the PA-E3 or PA-T3 port adapters, the show controllers serial command also displays configuration information such as the framing, clock source, bandwidth limit, whether scrambling is enabled, the national bit, the international bits, and DSU mode configured on the interface.

Also displayed are the performance statistics for the current interval and last 15-minute interval and whether any alarms exist.

Examples Example of the show controllers serial Command on the Cisco 4000 Series Router

The following is sample output from the show controllers serial command on the Cisco 4000:

Router# show controllers serial

MK5 unit 0, NIM slot 1, NIM type code 7, NIM version 1 idb = 0x6150, driver structure at 0x34A878, regaddr = 0x8100300

IB at 0x6045500: mode=0x0108, local_addr=0, remote_addr=0

N1=1524, N2=1, scaler=100, T1=1000, T3=2000, TP=1 buffer size 1524

DTE V.35 serial cable attached

RX ring with 32 entries at 0x45560 : RLEN=5, Rxhead 0

00 pak=0x6044D78 ds=0x6044ED4 status=80 max_size=1524 pak_size=0

01 pak=0x60445F0 ds=0x604474C status=80 max_size=1524 pak_size=0

02 pak=0x6043E68 ds=0x6043FC4 status=80 max_size=1524 pak_size=0

03 pak=0x60436E0 ds=0x604383C status=80 max_size=1524 pak_size=0

04 pak=0x6042F58 ds=0x60430B4 status=80 max_size=1524 pak_size=0

05 pak=0x60427D0 ds=0x604292C status=80 max_size=1524 pak_size=0

06 pak=0x6042048 ds=0x60421A4 status=80 max_size=1524 pak_size=0

07 pak=0x60418C0 ds=0x6041A1C status=80 max_size=1524 pak_size=0

08 pak=0x6041138 ds=0x6041294 status=80 max_size=1524 pak_size=0

09 pak=0x60409B0 ds=0x6040B0C status=80 max_size=1524 pak_size=0

10 pak=0x6040228 ds=0x6040384 status=80 max_size=1524 pak_size=0

11 pak=0x603FAA0 ds=0x603FBFC status=80 max_size=1524 pak_size=0

12 pak=0x603F318 ds=0x603F474 status=80 max_size=1524 pak_size=0

13 pak=0x603EB90 ds=0x603ECEC status=80 max_size=1524 pak_size=0

14 pak=0x603E408 ds=0x603E564 status=80 max_size=1524 pak_size=0

15 pak=0x603DC80 ds=0x603DDDC status=80 max_size=1524 pak_size=0

16 pak=0x603D4F8 ds=0x603D654 status=80 max_size=1524 pak_size=0

17 pak=0x603CD70 ds=0x603CECC status=80 max_size=1524 pak_size=0

18 pak=0x603C5E8 ds=0x603C744 status=80 max_size=1524 pak_size=0

19 pak=0x603BE60 ds=0x603BFBC status=80 max_size=1524 pak_size=0

20 pak=0x603B6D8 ds=0x603B834 status=80 max_size=1524 pak_size=0

Release 12.0(33)S, OL-8832-01, Rev. C9


19-81



21 pak=0x603AF50 ds=0x603B0AC status=80 max_size=1524 pak_size=0

22 pak=0x603A7C8 ds=0x603A924 status=80 max_size=1524 pak_size=0

23 pak=0x603A040 ds=0x603A19C status=80 max_size=1524 pak_size=0

24 pak=0x60398B8 ds=0x6039A14 status=80 max_size=1524 pak_size=0

25 pak=0x6039130 ds=0x603928C status=80 max_size=1524 pak_size=0

26 pak=0x60389A8 ds=0x6038B04 status=80 max_size=1524 pak_size=0


28 pak=0x6037A98 ds=0x6037BF4 status=80 max_size=1524 pak_size=0


30 pak=0x6036B88 ds=0x6036CE4 status=80 max_size=1524 pak_size=0


TX ring with 8 entries at 0x45790 : TLEN=3, TWD=7 tx_count = 0, tx_head = 7, tx_tail = 7

00 pak=0x000000 ds=0x600D70C status=0x38 max_size=1524 pak_size=22

01 pak=0x000000 ds=0x600D70E status=0x38 max_size=1524 pak_size=2






07 pak=0x000000 ds=0x6000000 status=0x38 max_size=1524 pak_size=0

XID/Test TX desc at 0xFFFFFF, status=0x30, max_buffer_size=0, packet_size=0

XID/Test RX desc at 0xFFFFFF, status=0x0, max_buffer_size=0, packet_size=0

Status Buffer at 0x60459C8: rcv=0, tcv=0, local_state=0, remote_state=0 phase=0, tac=0, currd=0x00000, curxd=0x00000 bad_frames=0, frmrs=0, T1_timeouts=0, rej_rxs=0, runts=0

0 missed datagrams, 0 overruns, 0 bad frame addresses

0 bad datagram encapsulations, 0 user primitive errors

0 provider primitives lost, 0 unexpected provider primitives

0 spurious primitive interrupts, 0 memory errors, 0 tr

%LINEPROTO-5-UPDOWN: Linansmitter underruns mk5025 registers: csr0 = 0x0E00, csr1 = 0x0302, csr2 = 0x0704

csr3 = 0x5500, csr4 = 0x0214, csr5 = 0x0008

Example of the show controllers serial Command for a PA-E3 Serial Port Adapter

The following is sample output from the show controllers serial command for a PA-E3 serial port adapter installed in slot 2:

Router# show controllers serial 2/0

M1T-E3 pa: show controller:

PAS unit 0, subunit 0, f/w version 2-55, rev ID 0x2800001, version 2 idb = 0x6080D54C, ds = 0x6080F304, ssb=0x6080F4F4

Clock mux=0x30, ucmd_ctrl=0x0, port_status=0x1

Serial config=0x8, line config=0x1B0202 maxdgram=4474, bufpool=128Kb, 256 particles

rxLOS inactive, rxLOF inactive, rxAIS inactive

txAIS inactive, rxRAI inactive, txRAI inactive line state: up

E3 DTE cable, received clockrate 50071882 base0 registers=0x3D000000, base1 registers=0x3D002000 mxt_ds=0x608BA654, rx ring entries=128, tx ring entries=256 rxring=0x4B01F480, rxr shadow=0x6081081C, rx_head=26 txring=0x4B01F960, txr shadow=0x60810E48, tx_head=192, tx_tail=192, tx_count=0 throttled=0, enabled=0, disabled=0 rx_no_eop_err=0, rx_no_stp_err=0, rx_no_eop_stp_err=0 rx_no_buf=0, rx_soft_overrun_err=0, dump_err= 1 tx_underrun_err=0, tx_soft_underrun_err=0, tx_limited=0 tx_fullring=0, tx_started=11504

Framing is g751, Clock Source is Line, Bandwidth limit is 34010.

19-82


Release 12.0(33)S, OL-8832-01, Rev. C9



Scrambling is enabled

National Bit is 0, International Bits are: 0 0

DSU mode 1




0 P-bit Err Secs, 0 P-bit Severely Err Secs

0 Severely Err Framing Secs, 0 Unavailable Secs

0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely Errored Secs




0 P-bit Err Secs, 0 P-bit Severely Err Secs,

0 Severely Err Framing Secs, 0 Unavailable Secs,

0 Line Errored Secs, 0 C-bit Errored Secs, 0 C-bit Severely Errored Secs

No alarms detected.

Example of the show controllers serial Command for a PA-T3 Serial Port Adapter

The following is sample output from the show controllers serial command that shows serial port 1/0/0 on a 1-port PA-T3 serial port adapter installed on a VIP2 in chassis slot 1:

Router# show controllers serial 2/0/1

Serial1/0/0 -

Mx T3(1) HW Revision 0x3, FW Revision 2.55















No alarms detected.

Example of the show controllers serial Command for a Channelized T3 SPA

The following is sample output from the show controllers serial command for a 2 or 4-Port CT3 SPA located in slot 3 of a Cisco 7304 router:

Router# show controllers serial

Serial3/1/0 -














Release 12.0(33)S, OL-8832-01, Rev. C9


19-83







Serial3/1/3 -
















No alarms detected.

Table 19-5 describes the fields shown in the show controllers serial output.

Note The fields appearing in the ouput will vary depending on card type, controller configuration, and the status of the controller line.

Table 19-5 show controllers serial Field Descriptions

Field

Serial

Framing

Clock source

Bandwidth limit

DSU mode

Cable length rx FEBE since last clear counter rx FEBE since last reset

Line Code Violations

P-bit Coding Violations

Description

Name of the serial controller.

Framing type.

Source of the synchronization signal (clock).

The allowable bandwidth for the controller.

The Data Service Unit (DSU) interoperability mode.

The distance to the first repeater.

Number of received far-end block errors.

Note Line far-end block error (accumulated from the M0 or

M1 byte) is reported when the downstream LTE detects BIP(B2) errors.

Path far-end block error (accumulated from the G1 byte) is reported when the downstream PTE detects

BIP(B3) errors.

Number of received far-end block errors.

Number of Bipolar Violation (BPV) errors or Excessive

Zeros (EXZ) errors.

Number of P-bit errors encountered between source and destination.

19-84


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-5 show controllers serial Field Descriptions (continued)


C-bit coding violations Number of C-bit errors encountered between source and destination.

P-bit Err Secs (PES)

P-bit Sev Err Secs (PSES)

Number of seconds with P-bit errors.

Note A PES is a second with one or more PCVs or one or more Out of Frame defects or a detected incoming

AIS. This gauge is not incremented when UASs are counted.

Number of seconds with P-bit severe errors.

Sev Err Framing Secs

Unavailable Secs

Line Errored Secs

C-bit Errored Secs (CES)

Note A PSES is a second with 44 or more PCVs or one or more Out of Frame defects or a detected incoming

AIS. This gauge is not incremented when UASs are counted.

The number of 1-second intervals in which either a Remote

Alarm Indication was received or a Loss Of Frame condition occurred.

The number of 1-second intervals in which the controller was down.

The number of 1-second intervals in which a Line Code

Violation occurred.

Number of seconds with C-bit errors.

C-bit Sev Err Secs (CSES)

Severely Errored Line Secs

Note A CES is a second with one or more CCVs or one or more Out of Frame defects or a detected incoming

AIS. This count is only for the SYNTRAN and C-bit

Parity DS3 applications. This gauge is not incremented when UASs are counted.

Number of seconds with severe C-bit errors.

Note A CSES is a second with 44 or more CCVs or one or more Out of Frame defects or a detected incoming

AIS. This count is only for the SYNTRAN and C-bit

Parity DS3 applications. This gauge is not incremented when UASs are counted.

For ESF signals, this is a second in which one of the following defects is detected:

• 320 or more Path Code Violation errors.

•

•

One or more Out of Frame defects.

An AIS defect.

For E1-CRC signals, this is a second with one of the following errors:

• 832 or more Path Code Violation errors.

• One or more Out of Frame defects.

For E1-nonCRC signals, this is a second with 2048 or more

Line Code Violations.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-85



Table 19-5 show controllers serial Field Descriptions (continued)


Far-End Errored Secs

Far-End Severely Errored Secs

Number of seconds of far-end failures.

P-bit Unavailable Secs

The number of 1-second intervals in which either a Remote

Alarm Indication was received or a Loss Of Frame condition occurred.

Number of seconds the interface is unavailable because of

P-bit errors.

CP-bit Unavailable Secs

CP-bit Far-end Unavailable Secs


CP-bit errors.


CP-bit errors from the far-end device.

Near-end path failures

Far-end path failures

Far-end code violations

FERF Defect Secs

AIS Defect Secs

LOS Defect Secs

Path Code Violations

Slip Secs

Fr Loss Secs

Line Err Secs

Degraded Mins

Errored Secs

Number of far-end receive failures detected per second.

Number of alarm indication signals per second.

Number of loss of signal alarms per second.

Indicates a frame synchronization bit error in the D4 and

E1-no CRC formats, or a CRC error in the Extended

Superframe (ESF) and E1-CRC formats.

Indicates the replication or deletion of the payload bits of a domestic trunk interface (DS1) frame. A slip might happen when there is a difference between the timing of a synchronous receiving terminal and the received signal.

Indicates the number of seconds an Out of Frame (OOF) error is detected.

Line Errored Seconds (LES) is a second in which one or more

Line Code Violation errors are detected.

A degraded minute is one in which the estimated error rate exceeds 1E-6 but does not exceed 1E-3.

In ESF and E1-CRC links, an errored second is a second in which one of the following defects is detected:

• One or more Path Code Violations.

Bursty Err Secs

•

Note

One or more Controlled Slip events.

For SF and E1 no-CRC links, the presence of Bipolar

Violations also triggers an errored second.

A second with more than one but fewer than 320 Path Coding

Violation errors, no Severely Errored Frame defects, and no detected incoming AIS defects. Controlled slips are not included in this parameter.

19-86


Release 12.0(33)S, OL-8832-01, Rev. C9


show diag

show diag

To display diagnostic information about the controller, interface processor, and port adapters for a networking device, use the show diag command in privileged EXEC mode. show diag [ slot-number | subslot slot / subslot ] [ details | summary ]

Syntax Description slot-number (Optional) Slot number of the interface. If a slot number is not specified, diagnostic information for all slots is displayed.

subslot slot / subslot (Optional) Specifies the display of diagnostic information about the shared port adapter (SPA), where:

• slot —Chassis slot number. details summary



• subslot —Secondary slot number on a SIP where a SPA is installed.


(Optional) Displays more details than the normal show diag output.

(Optional) Displays a summary (one line per slot) of the chassis.



11.2

11.2 GS

12.0

12.0(7)T

12.2(8)T

12.2(13)T

12.2(15)ZJ

12.3(4)T

Modification


This command was implemented on the Cisco 12000 series.

This command was implemented on the Cisco AS5300.

This command was implemented on the Cisco 1750 router.

This command was implemented for AIC and WIC cards on the Cisco 2600 series and the Cisco 3600 series.

This command was implemented for the AIM-VPN/EPII and AIM-VPN/HPII cards on the following platforms: Cisco 2691, Cisco 3660, Cisco 3725, and

Cisco 3745.

This command was implemented for the AIM-VPN/BPII card on the following platforms: Cisco 2610XM, Cisco 2611XM, Cisco 2620XM, Cisco 2621XM,

Cisco 2650XM, and Cisco 2651XM.

Support for the AIM-VPN/BPII card on the Cisco 2600XM series was integrated into Cisco IOS Release 12.3(4)T.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-87


show diag

Release

12.0(31)S

12.0(32)SY07 and

12.0(33)S02

Modification

This command was modified in Cisco IOS Release 12.0(31)S. The subslot keyword is added to support slot/subslot addressing for SIPs and SPAs on the

Cisco 12000 series routers.

The command output includes the DIMM size of each slot on SDRAM along with the total DRAM size. The command output change is applicable, if the command is executed for a route processor.

Usage Guidelines Use this command to determine the type of hardware installed in your networking device. This command displays information for the EEPROM, motherboard, WAN interface cards (WICs), voice interface cards

(VICs), ATM interface cards (AICs), and advanced integration modules (AIMs).

The command output includes the DIMM size of each slot along with the SDRAM size if the command is executed for a route processor. To display the DIMM size of each slot the ROMMON version must be upgraded using the command upgrade rom-monitor slot <slot-number of PRP> .

Note To display the DIMM size of each slot, the ROMMON version should be upgraded to 1.20 for 12.0(32)S and 12.0(32)SY throttle branches. For 12.0(33)S branch the ROMMON version should be upgraded to

1.22.

Examples Example for a Route Processor on a Cisco 12000 Series Internet Router

The show diag command output now displays the DIMM size of each slot along with the total DRAM size. The following is a sample output for a PRP having 2-GB memory on each of the 2 DIMMs (total

4-GB):

Router# show diag 5

SLOT 5 (RP/LC 5): Performance Route Processor

MAIN: type 96, 800-23469-08 rev B0

Deviation: 0

HW config: 0x10 SW key: 00-00-00

PCA: 73-8812-11 rev B0 ver 7

Design Release 0.0 S/N SAD1148095F

MBUS: MBUS Agent (1) 73-8048-07 rev A0 dev 0

HW version 0.1 S/N SAL1132X2UD

Test hist: 0x00 RMA#: 00-00-00 RMA hist: 0x00

DIAG: Test count: 0x00000000 Test results: 0x00000000

FRU: Linecard/Module: PRP-2=

Route Memory: MEM-PRP/LC-3584=

MBUS Agent Software version 2.68 (RAM) (ROM version is 2.32)

ROM Monitor version 1.20(0.1)

Primary clock is CSC 1

Board State is IOS Running ACTIVE (ACTV RP )

Insertion time: 00:00:04 (00:16:54 ago)

DRAM size: 3758096384 bytes

DRAM DIMM Slot 1: 2048M found, Slot 2: 2048M found

The following is a sample output of show diag command for a PRP having one DIMM with 512-MB memory:


SLOT 15 (RP/LC 15): Performance Route Processor

MAIN: type 96, 800-26107-02 rev A0

Deviation: 0

19-88


Release 12.0(33)S, OL-8832-01, Rev. C9


show diag


PCA: 73-9870-02 rev A0 ver 7

Design Release 0.0 S/N SAD092606BW

MBUS: MBUS Agent (1) 73-8048-07 rev A0 dev 0

HW version 0.1 S/N SAL09190DQN



FRU: Linecard/Module: PRP-1=

Route Memory: MEM-PRP/LC-512=


ROM Monitor version 1.20(0.1)


Board State is IOS Running ACTIVE (ACTV RP )



DRAM DIMM Slot 1: 512M found, Slot 2: Empty

Example for a 1-Port T3 Serial Port Adapter

The following is sample output from the show diag command for a 1-port T3 serial port adapter in chassis slot 1 on a Cisco 7200 series router:


Slot 1:

Physical slot 1, ~physical slot 0xE, logical slot 1, CBus 0

Microcode Status 0x4

Master Enable, LED, WCS Loaded

Board is analyzed

Pending I/O Status: None

EEPROM format version 1

VIP2 controller, HW rev 2.4, board revision D0

Serial number: 04372053 Part number: 73-1684-03

Test history: 0x00 RMA number: 00-00-00

Flags: cisco 7000 board; 7500 compatible

EEPROM contents (hex):

0x20: 01 15 02 04 00 42 B6 55 49 06 94 03 00 00 00 00

0x30: 68 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Slot database information:

Flags: 0x4 Insertion time: 0x14A8 (5d02h ago)

Controller Memory Size: 16 MBytes DRAM, 1024 KBytes SRAM

PA Bay 0 Information:

T3 Serial PA, 1 ports


HW rev FF.FF, Board revision UNKNOWN

Serial number: 4294967295 Part number: 255-65535-255

Examples for a Cisco 12000 Series Internet Router

The following is sample output from the show diag command on a Cisco 12000 series Internet router:


SLOT 3 (RP/LC 3 ): 4 Port Packet Over SONET OC-3c/STM-1 Multi Mode

MAIN: type 33, 00-0000-00 rev 70 dev 0


PCA: 73-2147-02 rev 94 ver 2

HW version 1.0 S/N 04499695

MBUS: MBUS Agent (1) 73-2146-05 rev 73 dev 0




Release 12.0(33)S, OL-8832-01, Rev. C9 19-89

show diag



MBUS Agent Software version 01.27 (RAM) using CAN Bus A

ROM Monitor version 00.0D

Fabric Downloader version used 00.0D (ROM version is 00.0D)

Board is analyzed

Board State is Line Card Enabled (IOS RUN )



FrFab SDRAM size: 67108864 bytes

ToFab SDRAM size: 16777216 bytes

The following is sample output from the show diag command with the summary keyword:

Router# show diag summary

SLOT 0 (RP/LC 0 ): Route Processor

SLOT 2 (RP/LC 2 ): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode




SLOT 11 (RP/LC 11): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode

SLOT 16 (CSC 0 ): Clock Scheduler Card

SLOT 17 (CSC 1 ): Clock Scheduler Card

SLOT 18 (SFC 0 ): Switch Fabric Card



SLOT 24 (PS A1 ): AC Power Supply

SLOT 26 (PS B1 ): AC Power Supply

SLOT 28 (TOP FAN ): Blower Module

SLOT 29 (BOT FAN ): Blower Module

The following is sample output from the show diag command with the details keyword:

Router# show diag 4 details

SLOT 4 (RP/LC 4): 4 Port Packet Over SONET OC-3c/STM-1 Single Mode

MAIN: type 33, 800-2389-01 rev 71 dev 16777215

HW config: 0x00 SW key: FF-FF-FF

PCA: 73-2275-03 rev 75 ver 3


MBUS: MBUS Agent (1) 73-2146-06 rev 73 dev 0


Test hist: 0xFF RMA#: FF-FF-FF RMA hist: 0xFF



00: 01 00 01 00 49 00 08 62 06 03 00 00 00 FF FF FF

10: 30 34 35 34 31 33 39 35 FF FF FF FF FF FF FF FF

20: 01 01 00 00 00 00 00 FF FF FF FF FF FF FF FF FF

30: A5 FF A5 A5 A5 A5 FF A5 A5 A5 A5 A5 A5 A5 A5 A5

40: 00 21 01 01 00 49 00 08 E3 03 05 03 00 01 FF FF

50: 03 20 00 09 55 01 01 FF FF FF 00 FF FF FF FF FF

60: 30 34 35 32 39 34 36 35 FF FF FF FF FF FF FF FF

70: FF FF FF FF FF FF FF FF 05 00 00 01 00 00 00 00

MBUS Agent Software version 01.24 (RAM)

Fabric Downloader version 00.0D

Board is analyzed

Flags: 0x4

Board State is Line Card Enabled (IOS RUN)



FrFab SDRAM size: 67108864 bytes

ToFab SDRAM size: 16777216 bytes

19-90


Release 12.0(33)S, OL-8832-01, Rev. C9


show diag

Example for an ATM SAR AIM in a Cisco 3660

The following is sample output from the show diag command for one ATM Segmentation and

Reassembly (SAR) AIM in a Cisco 3660 router:


3660 Chassis type: ENTERPRISE c3600 Backplane EEPROM:



.

.

.

ATM AIM: 1

ATM AIM module with SAR only (no DSPs)



Board Revision : A0

Deviation Number : 0-0

Fab Version : 02

PCB Serial Number : JAB9801ABCD

Example for an NM-AIC-64 Installed in a Cisco 2611

The following is sample output from the show diag command for a Cisco 2611 router with the

NM-AIC-64 installed.

Router# show diag

Slot 0:

C2611 2E Mainboard Port adapter, 2 ports

Port adapter is analyzed

Port adapter insertion time unknown

EEPROM contents at hardware discovery:


PCB Serial Number : JAD044808SG (1090473337)

Part Number : 73-2840-13

RMA History : 00

RMA Number : 0-0-0-0

Board Revision : C0

Deviation Number : 0-0



0x00: 04 FF 40 00 92 41 02 03 C1 18 4A 41 44 30 34 34

0x10: 38 30 38 53 47 20 28 31 30 39 30 34 37 33 33 33

0x20: 37 29 82 49 0B 18 0D 04 00 81 00 00 00 00 42 43

0x30: 30 80 00 00 00 00 FF FF FF FF FF FF FF FF FF FF

0x40: FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF




Slot 1:

NM_AIC_64 Port adapter, 3 ports

Port adapter is analyzed

Port adapter insertion time unknown

EEPROM contents at hardware discovery:


Part Number : 74-1923-01

Board Revision : 02

PCB Serial Number : DAN05060012




Release 12.0(33)S, OL-8832-01, Rev. C9 19-91


show diag

0x00: 04 FF 40 02 55 41 01 00 82 4A 07 83 01 42 30 32

0x10: C1 8B 44 41 4E 30 35 30 36 30 30 31 32 FF FF FF







Table 19-6 describes significant fields shown in the display.

Table 19-6 show diag (AIC) Field Descriptions

Field

C2611 2E Mainboard Port adapter, 2 ports

Description

Line card type; number of ports available.

Port adapter is analyzed The system has identified the port adapter.

Port adapter insertion time Elapsed time since insertion.

Hardware Revision

PCB Serial Number

Part Number

RMA History

Version number of the port adapter.

Serial number of the printed circuit board.

Part number of the port adapter.

Counter that indicates how many times the port adapter has been returned and repaired.

RMA Number Return material authorization number, which is an administrative number assigned if the port adapter needs to be returned for repair.

Revision number (signifying a minor revision) of the port adapter.

Board Revision

Deviation Number Revision number (signifying a minor deviation) of the port adapter.

EEPROM format version Version number of the EEPROM format.

EEPROM contents (hex) Dumps of EEPROM programmed data.

Example for an AIM-VPN in a Cisco 2611XM

The following example shows how to obtain hardware information about an installed AIM-VPN on the

Cisco 2611XM router.


Encryption AIM 1:

Hardware Revision :1.0

Top Assy. Part Number :800-03700-01

Board Revision :A0

Deviation Number :0-0

Fab Version :02

PCB Serial Number :JAB9801ABCD

RMA Test History :00

RMA Number :0-0-0-0

RMA History :00



0x00:04 FF 40 03 0B 41 01 00 C0 46 03 20 00 0E 74 01

0x10:42 41 30 80 00 00 00 00 02 02 C1 8B 4A 41 42 39

0x20:38 30 31 41 42 43 44 03 00 81 00 00 00 00 04 00

0x30:FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF

19-92


Release 12.0(33)S, OL-8832-01, Rev. C9






show diag

Release 12.0(33)S, OL-8832-01, Rev. C9


19-93

show diag



Table 19-7 show diag (AIM-VPN) Field Descriptions

Field

Hardware Revision

Top Assy. Part Number

Board Revision

Deviation Number

PCB Serial Number

RMA Number

RMA History

EEPROM format version

EEPROM contents (hex)

Description

Version number of the port adapter.

Part number of the port adapter.

Revision number (signifying a minor revision) of the port adapter.

Revision number (signifying a minor deviation) of the port adapter.


Return material authorization number, which is an administrative number assigned if the port adapter needs to be returned for repair.

Counter that indicates how many times the port adapter has been returned and repaired.

Version number of the EEPROM format.

Dumps of EEPROM programmed data.

Examples for a Shared Port Adapter on a Cisco 12000 Series Router

The following is sample output from the show diag subslot command for the 1-Port OC-192c/STM-64

POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000 series router:

Router# show diag subslot 1/1

SUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port Adapter





Top Assy. Revision : A0





Table 19-7 describes the significant fields shown in the display.

Table 19-8 show diag subslot Field Descriptions

Field

Product Identifier (PID)

Version Identifier (VID)

PCB Serial Number

Top Assy. Part Number

Top Assy. Revision

Hardware Revision

CLEI Code

Description

Product number of the SPA.

Version number of the SPA.


Part number of the SPA.

Revision number (signifying a minor revision) of the SPA.

Revision number (signifying a minor revision) of the SPA hardware.

Common Language Equipment Identification number.

19-94


Release 12.0(33)S, OL-8832-01, Rev. C9


show diag

Table 19-8

Field

Insertion Time show diag subslot Field Descriptions (continued)

Operational Status

Description

Time when the SPA was installed, and elapsed time between that insertion time and the current time.

Current status of the SPA. For more information about the status field descriptions, refer to the show hw-module subslot oir command.

The following is sample output from the show diag subslot details command for the 1-Port

OC-192c/STM-64 POS/RPR XFP SPA in subslot 1 of the SIP located in chassis slot 1 on a Cisco 12000 series router:

Router# show diag subslot 1/1 details

SUBSLOT 1/1 (SPA-OC192POS-XFP): 1-port OC192/STM64 POS/RPR XFP Optics Shared Port Adapter

EEPROM version : 4

Compatible Type : 0xFF

Controller Type : 1100


Boot Timeout : 400 msecs


PCB Part Number : 73-8546-01

PCB Revision : A0 Fab Version : 01

RMA Test History : 00

RMA Number : 0-0-0-0

RMA History : 00

Deviation Number : 0




Top Assy. Revision : A0 IDPROM Format Revision : 36

System Clock Frequency : 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

00 00 00 00 00 00


Base MAC Address : 00 00 00 00 00 00

MAC Address block size : 0

Manufacturing Test Data : 00 00 00 00 00 00 00 00

Field Diagnostics Data : 00 00 00 00 00 00 00 00

Calibration Data : Minimum: 0 dBmV, Maximum: 0 dBmV

Calibration values :

Power Consumption : 11000 mWatts (Maximum)

Environment Monitor Data : 03 30 04 B0 46 32 07 08

46 32 09 C4 46 32 0C E4

46 32 13 88 46 32 07 08

46 32 EB B0 50 3C 00 00

00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

00 00 FE 02 F6 AC

Processor Label : 00 00 00 00 00 00 00

Platform features : 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

00 00 00 00 00 00 00

Asset ID :

Asset Alias :



Release 12.0(33)S, OL-8832-01, Rev. C9


19-95


show diag

Example for a SPA Interface Processor on a Cisco 12000 Series Router

The following is sample output from the show diag command for a SIP located in chassis slot 2 on a



SLOT 2 (RP/LC 2 ): Modular 10G SPA Interface Card

MAIN: type 149, 800-26270-01 rev 84

Deviation: 0


PCA: 73-9607-01 rev 91 ver 1

Design Release 1.0 S/N SAD08460678

MBUS: Embedded Agent



FRU: Linecard/Module: 12000-SIP-650

FRU: Linecard/Module: 12000-SIP-650

Processor Memory: MEM-LC5-1024=(Non-Replaceable)

Packet Memory: MEM-LC5-PKT-256=(Non-Replaceable)

L3 Engine: 5 - ISE OC192 (10 Gbps)


ROM Monitor version 255.255

Fabric Downloader version used 3.7 (ROM version is 255.255)


Board is analyzed

Board State is Line Card Enabled (IOS RUN )

Insertion time: 1d00h (2d08h ago)

Processor Memory size: 1073741824 bytes

TX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes

RX Packet Memory size: 268435456 bytes, Packet Memory pagesize: 32768 bytes

0 crashes since restart

SPA Information:

subslot 2/0: SPA-OC192POS-XFP (0x44C), status is ok

subslot 2/1: Empty

subslot 2/2: Empty

subslot 2/3: Empty

Related Commands Command dsl operating-mode (ADSL) show dsl interface atm

Description

Modifies the operating mode of the digital subscriber line for an

ATM interface.

Shows all of the ADSL-specific information for a specified ATM interface.

19-96


Release 12.0(33)S, OL-8832-01, Rev. C9


show hw-module all fpd


To display the current versions of all field-programmable devices (FPDs) for all of the supported card types on a router, enter the show hw-module all fpd command in privileged EXEC configuration mode.





12.2(18)SXE

12.0(31)S

Modification


This command was integrated into Cisco IOS Software Release 12.0(31)S.

Usage Guidelines Other than the FPD version information, the output for this command may also contain useful

FPD-related notes.

Examples This example shows FPD image file versions for all SIPs and SPAs in the Cisco 12000 Series Router:


==== ====================== ====== =============================================



==== ====================== ====== ================== =========== ==============

4 7600-SIP-200 0.132 1-I/O FPGA 0.19 0.18

2-EOS FPGA 0.22 0.22

3-PEGASUS TX FPGA 0.121 0.121

4-PEGASUS RX FPGA 0.13 0.13

5-ROMMON 1.1 1.1

---- ---------------------- ------ ------------------ ----------- --------------

4/0 SPA-4XOC3-ATM 1.0 1-I/O FPGA 0.121 0.121

---- ---------------------- ------ ------------------ ----------- --------------

4/1 SPA-8XCHT1/E1 0.117 1-ROMMON 2.12 2.12

2-I/O FPGA 0.22 0.22

---- ---------------------- ------ ------------------ ----------- --------------

4/3 SPA-4XCT3/DS0 0.253 1-ROMMON 2.12 2.12

2-I/O FPGA 0.21 0.21


==== ====================== ====== =============================================

This example shows FPD image file versions that require an upgrade (indicated by the asterisk) for two

SIPs in the Cisco 12000 Series Router. The SIPs are disabled due to the version mismatch:


==== ====================== ====== =============================================



Release 12.0(33)S, OL-8832-01, Rev. C9


19-97



==== ====================== ====== ================== =========== ==============

1 7600-SIP... <DISABLED> 0.550 1-I/O FPGA 1.1 1.1

2-EOS FPGA 1.211 1.211



5-ROMMON 1.1 1.2 *

---- ---------------------- ------ ------------------ ----------- --------------

4 7600-SIP... <DISABLED> 0.550 1-I/O FPGA 1.1 1.1

2-EOS FPGA 1.211 1.211



5-ROMMON 1.1 1.2 *

==== ====================== ====== =============================================

NOTES:

- FPD images that are required to be upgraded are indicated with a '*'

character in the "Minimal Required Version" field.

- The following FPD image package file is required for the upgrade:

"c7600-fpd-pkg.122-18.SXE.pkg"

Related Commands Command show hw-module slot fpd

Description

Displays the current versions of all FPDs for a SIP in the specified slot location and for all of the SPAs installed in that SIP.

show hw-module subslot fpd Displays the current versions of all FPDs for a particular SPA or all of the active SPAs on a router.

19-98


Release 12.0(33)S, OL-8832-01, Rev. C9


show hw-module subslot fpd


To display the current versions of all field-programmable devices (FPDs) for a particular SPA or all of the active SPAs on a router, enter the show hw-module subslot fpd command in privileged EXEC configuration mode.

Cisco 7304 Router show hw-module subslot [ slot / subslot ] fpd

Cisco 7600 Series Router show hw-module subslot { slot / subslot | all } fpd


/ subslot all


Refer to the platform-specific SPA hardware installation guide and the corresponding “Identifying Slots and Subslots for SIPs and SPAs” topic in the platform-specific SPA software configuration guide.


Refer to the platform-specific SPA hardware installation guide and the corresponding “Specifying the Interface Address” topic in the platform-specific SPA software configuration guide for subslot information.

Specifies display of FPD information for all SPAs in the system.

Note The all keyword is not supported for SPAs on the Cisco 7304 router.

Defaults For the Cisco 7304 router, if no location is specified, the output for this command will show information for all supported card types on the router.

For the Cisco 12000 Series Routers, there is no default behavior or values.



12.2(20)S2

12.2(18)SXE

12.0(31)S

Modification


The all keyword was added in Cisco IOS Release 12.2(18)SXE on the

Cisco 12000 Series Routers.

This command was integrated into Cisco IOS Release 12.0(31)S and introduced on Cisco 12000 series router.

Usage Guidelines Other than the FPD version information, the output for this command may also contain useful

FPD-related notes.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-99



Cisco 7304 Router

The all keyword is not supported on the Cisco 7304 router. The slot/subslot arguments are optional, and if you do not specify them, the command displays FPD information for all supported card types on the router.

Cisco 7600 Series Router

If you do not use the all keyword, then you must specify the slot/subslot arguments to select the location of a particular card. There is no default behavior for this command on the Cisco 12000 Series Router.

Examples Displaying FPD Information for a Particular SPA Example

This example shows the output when using the slot/subslot arguments to identify a particular SPA. This

SPA meets the minimum FPD requirements with that particular Cisco IOS Release:


==== ====================== ====== =============================================


Slot Card Description Ver. Device: "ID-Name" Version Version

==== ====================== ====== ================== =========== ==============


==== ====================== ====== =============================================

Displaying FPD Information for all SPAs in the System Example

This example shows FPD image file versions for all SPAs in the system:

Router# show hw-module subslot all fpd

==== ====================== ====== =============================================



==== ====================== ====== ================== =========== ==============


---- ---------------------- ------ ------------------ ----------- --------------

4/1 SPA-8XT1/E1 0.143 1-ROMMON 2.12 2.12

2-I/O FPGA 0.22 0.22

---- ---------------------- ------ ------------------ ----------- --------------

4/3 SPA-4XOC3-POS 0.100 1-I/O FPGA 3.4 3.4

---- ---------------------- ------ ------------------ ----------- --------------

7/0 SPA-8XCHT1/E1 0.117 1-ROMMON 2.12 2.12

2-I/O FPGA 0.22 0.22

---- ---------------------- ------ ------------------ ----------- --------------


==== ====================== ====== =============================================

Displaying Information for All SPAs in the System Example (Cisco 7304 only)

The all keyword is not supported on the Cisco 7304 router.

To display all FPD image file versions for all SPAs on a Cisco 7304 router, enter the show hw-module subslot fpd command without specifying a slot and subslot. The following example shows all FPD image file versions on a Cisco 7304 router:

Router# show hw-module subslot fpd

==== ====================== ====== =============================================


Slot Card Description Ver. Device:"ID-Name" Version Version

==== ====================== ====== ================== =========== ==============

2/0 SPA-4FE-7304 0.32 1-Data & I/O FPGA 4.13 4.13

19-100


Release 12.0(33)S, OL-8832-01, Rev. C9



---- ---------------------- ------ ------------------ ----------- --------------

2/1 SPA-2GE-7304 0.15 1-Data & I/O FPGA 4.13 4.13

==== ====================== ====== =============================================

Related Commands Command show hw-module all fpd show hw-module slot fpd

Description

Displays the current versions of all FPDs for all of the supported card types on a router.

Displays the current versions of all FPDs for a SIP in the specified slot location on a router, and for all of the SPAs installed in that SIP.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-101


show hw-module subslot oir


To display the operational status of a shared port adapter (SPA), use the show hw-module subslot oir command in privileged EXEC configuration mode. The command does not have a no form. show hw-module subslot { slot / subslot | all } oir [ internal ]


/ subslot all internal






Displays OIR status for all supported card types in the system.

(Optional) Displays detailed diagnostic information. This option is intended for internal diagnostic use with Cisco Systems technical support personnel.


If no location is specified, the output for this command will show information for all SPAs in the router.



12.2(25)S3

Modification


12.2(18)SXE This command was integrated into Cisco IOS Release 12.2(18)SXE.


Usage Guidelines Use the show hw-module subslot oir command to obtain operational status information about one or all SPAs. To display information for a specific SPA, specify the slot number of the SIP and the subslot number of the SPA about which you want information. To display information for all SPAs in the router, do not specify the slot / subslot arguments and use the all keyword.

The optional internal keyword displays detailed diagnostic information that is recommended only for use with Cisco Systems technical support personnel.

Note The following status descriptions are not applicable to every SPA and can be platform-specific.

19-102


Release 12.0(33)S, OL-8832-01, Rev. C9


Examples


The following example shows the operational status of all of the SPAs installed in a router where two of the SPAs are in an out-of-service condition:

Router# show hw-module subslot all oir

Module Model Operational Status

-------------- ------------------ ------------------------subslot 4/0 SPA-4XOC3-POS booting subslot 4/1 SPA-4XOC3-ATM out of service(FPD upgrade failed) subslot 4/2 SPA-4XOC3-POS ok subslot 4/3 SPA-1XTENGE-XFP out of service(SPA unrecognized)

Table 19-9 describes the possible values for the Operational Status field in the output.

Table 19-9 booting missing ok

Operational Status Field Descriptions

Operational Status admin down

Description

SPA is administratively disabled by the hw-module subslot shutdown global configuration command.

SPA is initializing.

SPA is not present in the SIP subslot.

SPA is operational.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-103



Table 19-9 Operational Status Field Descriptions

Operational Status out of service ( reason )

Description

The SPA is out of service for one of the following reasons:

Note The following reasons are not applicable to every SPA and can be platform-specific.

•

•

•

•

•

•

•

•

•

•

•

Analyze failed—Failed to create a SPA data structure, most likely due to a memory allocation problem.

Authentication failed—SPA has failed hardware validation.

Data structure create error—Failed to create a SPA data structure, most likely due to a memory allocation problem.

Event corrupt—A SPA online insertion and removal (OIR) event has been corrupted. This could be caused by a corrupted message between the SIP and the route processor

(RP) or some other software or hardware problem.

Event sequence error—A SPA OIR event was received out of sequence. This could be caused by a corrupted message between the SIP and the route processor (RP) or some other software or hardware problem.

Fail code not set—Failure code could not be read from a

SPA OIR event message. This could be caused by a corrupted message between the SIP and the RP or some other software or hardware problem.

Failed too many times—SPA is disabled because it has failed more than the allowable limit on the platform.

FPD upgrade failed—A field-programmable device, such as the Field-Programmable Gate Array (FPGA), failed to automatically upgrade.

H/W signal deasserted—The SPA_OK or PWR_OK hardware signal indicating that the SPA is accessible are no longer asserted.

Heartbeat failed—Occurs when intelligent SPAs encounter heartbeat failures.

Incompatible FPD—An FPGA version mismatch with the

Cisco IOS software has been detected for the SPA.

19-104


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-9 stopped

Operational Status Field Descriptions

Operational Status out of service

( reason )—CONTINUED

Description

•

•

Init timeout—Time limit has been reached during initialization of a SPA.

Read SPA type failed—A read from the hardware for the

SPA type failed.

•

•

•

•

Note

Reload request—SPA reload is in progress from the hw-module subslot reload command.

SPA h/w error—The SPA software driver has detected a hardware error.

SPA ready timeout—A timeout ocurred on the RP while waiting for the SPA to become operational.

SPA type mismatch—Occurs when you have pre-configured a SPA of one type, but have inserted a SPA of a different type.

This reason code only applies to those platforms that support pre-configuration. This is not applicable to a


•

•

•

•

SPA unrecognized—SPA is not supported by the Cisco IOS software release.

Start failed—Failed to start interfaces on SPA.

Unexpected inserted event—The SPA OIR software has received a SPA insertion event when the OIR software considered the SPA already present.

Wait h/w ok timeout—A timeout occurred while waiting for the SPA_OK and PWR_OK hardware signals to be asserted.

• Wait start timeout—A timeout occurred on the SIP while waiting for permission from the RP to bring up the SPA.

SPA has been gracefully deactivated using the hw-module subslot stop privileged EXEC command on the Cisco 7304 router.

The following example shows the operational status of all of the SPAs installed in a router where all

SPAs are running successfully:

Router# show hw-module subslot all oir

Module Model Operational Status

------------- -------------------- -----------------------subslot 1/1 SPA-2XOC3-ATM ok subslot 4/0 SPA-2XT3/E3 ok subslot 4/1 SPA-4XOC3-POS ok subslot 4/2 SPA-8XCHT1/E1 ok

The following example shows sample output when using the optional internal keyword:

Router# show hw-module subslot 4/0 oir internal

WARNING: This command is not intended for production use and should only be used under the supervision of

Cisco Systems technical support personnel.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-105


show hw-module subslot oir sm(spa_oir_tsm subslot 4/0 TSM), running yes, state ready

Admin Status: admin enabled, Operational Status: ok(1)

Last reset Reason: manual

TSM Context:

configured_spa_type 0x483

soft remove fail code 0x0(none)

last_fail_code 0x110E(SPA unrecognized)

fail_count 0

timed_fail_count 0, failed_spa_type 0x483

recovery_action 6

associated_fail_code 0x110E(SPA unrecognized)

sequence numbers: next from tsm 4, last to tsm 2

flags 0x0

Subslot:

spa type 0x483, active spa type 0x483

subslot flags 0x0, plugin flags 0x0

TSM Parameters:

wait_psm_ready_timeout 360000 ms, init_timeout 240000 ms

short_recovery_delay 5000 ms, long_recovery_delay 120000 ms

ok_up_time 1200000 ms, bad_fail_count 10

fail_time_period 600000 ms, max_fail_count 5

does not support pre-configuration

SPA OIR state machine audit statistics

In-sync poll-count qry-fail resp-fail restarts fail-count subslot 4/0 yes 1 0 0 0 0

Related

Command hw-module subslot reload

Description

Restarts a SPA and its interfaces.

hw-module subslot shutdown Shuts down a SPA with or without power.

19-106


Release 12.0(33)S, OL-8832-01, Rev. C9




To display configuration information and statistics for a sections data communications channel (SDCC) interface, use the show interface sdcc command in privileged EXEC mode. show interface sdcc slot / subslot / port


/ subslot

/ port






(Optional) Port or interface number.





12.2(11)BC3

12.2(25)S3

12.2(18)SXE

12.0(31)S

Modification


This command was integrated into Cisco IOS Release 12.2(25)S3 to support

POS SPAs on the Cisco 7304 router.


POS SPAs on the Cisco 7600 series routers and Catalyst 6500 series switches.

This command was integrated into Cisco IOS Release 12.0(31)S to support POS

SPAs on the Cisco 12000 series routers.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-107



Examples Cisco 7600 Series Router and Catalyst 6500 Series Switch Example

The following command displays configuration information and statistics for SDCC interface 7/0/0:

Router# show interface sdcc 7/0/0

SDCC7/0/0 is up, line protocol is up

Hardware is SDCC





Keepalive not set



Input queue:0/75/0/0 (size/max/drops/flushes); Total output drops:0

Queueing strategy:fifo

Output queue:0/40 (size/max)











Cisco 12000 Series Router Example

The following is sample output from the show interface sdcc command on a Cisco 12000 series router for POS interface 1/1/0 (which is the interface for port 0 of the SPA in subslot 1 of the SIP in chassis slot 1):

Router# show interface sdcc 1/1/0

SDCC1/1/0 is administratively down, line protocol is down

Hardware is SDCC

















19-108


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-10 describes the significant fields shown in these displays.

Table 19-10 show interface sdcc Field Descriptions

Field

Hardware is. . .

Description

SDCCx/y/z is up, line protocol is up Indicates whether the interface hardware is currently active and can transmit and receive or whether it has been taken down by an administrator.

Hardware type:

• SDCC— Section Data Communications Channel

Internet address is

MTU

BW

DLY rely

Internet address and subnet mask.

Maximum transmission unit of the interface.

Bandwidth of the interface, in kilobits per second.

Delay of the interface, in microseconds.

Reliability of the interface as a fraction of 255 (255/255 is

100 percent reliability), calculated as an exponential average over 5 minutes.

load

Encapsulation crc

Loopback

Keepalive

Last input

(Last) output

(Last) output hang

Load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.

The calculation uses the value from the bandwidth interface configuration command.

Encapsulation method assigned to interface.

Cyclic redundancy check size (16 or 32 bits).

Indicates whether loopback is set.

Indicates whether keepalives are set.

Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.

Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. This counter is updated only when packets are process-switched, not when packets are fast-switched.

Number of hours, minutes, and seconds (or never) since the interface was last reset because of a transmission that took too long. When the number of hours in any of the “last” fields exceeds 24 hours, the number of days and hours is printed. If that field overflows, asterisks are printed.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-109



Table 19-10 show interface sdcc Field Descriptions (continued)


Last clearing Time at which the counters that measure cumulative statistics

(such as number of bytes transmitted and received) shown in this report were last reset to zero. Note that variables that might affect routing (for example, load and reliability) are not cleared when the counters are cleared.

Queueing strategy

Output queue, drops input queue, drops

*** indicates the elapsed time is too large to be displayed.

0:00:00 indicates the counters were cleared more than 22

31 ms

(and less than 2

32 ms) ago.

First-in, first-out (FIFO) queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).

Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.

5 minute input rate

5 minute output rate packets input bytes (input) no buffer

Average number of bits and packets received or transmitted per second in the last 5 minutes.

Total number of error-free packets received by the system.

Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.

Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count.

Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.

broadcasts runts giants throttles parity input errors

CRC

Total number of broadcast or multicast packets received by the interface.

Number of packets that are discarded because they are smaller than the minimum packet size of the medium.

Number of packets that are discarded because they exceed the maximum packet size of the medium.

Not supported for POS interfaces.

Report of the parity errors on the interface.

Total number of no buffer, runts, giants, CRCs, frame, overrun, ignored, and abort counts. Other input-related errors can also increment the count, so that this sum might not balance with the other counts.

Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.

19-110


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-10 show interface sdcc Field Descriptions (continued)

Field Description frame Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.

overrun ignored abort packets output bytes (output) underruns

Number of times the serial receiver hardware was unable to hand received data to a hardware buffer because the input rate exceeded the receiver’s ability to handle the data.

Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.

Illegal sequence of one bits on the interface.

Total number of messages transmitted by the system.

Total number of bytes, including data and MAC encapsulation, transmitted by the system.

Number of times that the far-end transmitter has been running faster than the near-end router’s receiver can handle. output errors collisions interface resets

Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.


output buffer failures output buffers swapped out carrier transitions

Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.



Number of times the carrier detect signal of the interface has changed state.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-111




To view the flowcontrol configuration (on or off) on a Gigabit Ethernet (GE)/Fast Ethernet (FE) SPA interface on Cisco 12000 series router, use the show interfaces flowcontrol command in privilege

EXEC mode. show interfaces flowcontrol


Defaults By default, flow control is enabled.



12.0(33)S2

Modification

This command was introduced into Cisco IOS Release 12.0(33)S2 for the


Usage Guidelines This command is supported only for GE and FE interfaces of a SIP-401/501/600/601 on a Cisco 12000 series router. The default behaviour is flow control is enabled.

Note This command is used in conjunction with


and no flowcontrol bidrectional command.

The following example shows the flowcontrol configuration on a GE SPA interface:

Router# show interfaces flowcontrol

Port SendFlowControl ReceiveFlowControl

GigabitEthernet4/0/0 off off

GigabitEthernet4/1/0 off off

GigabitEthernet4/1/1 on on









Ethernet0 unsupported unsupported

Ethernet1 unsupported unsupported

The above command output shows that flowcontrol for sending and receiving frames is enabled for GE interfaces 4/1/1 to 4/1/9, it is disabled on GE interfaces 4/0/0 and 4/1/0, while flowcontrol is not supported on Ethernet interfaces 0 and 1.

19-112


Release 12.0(33)S, OL-8832-01, Rev. C9



Related Commands Command


Description

Enables flow control on GE and FE SPA interfaces on a

SIP-401/501/600/601. By default flowcontrol is enabled.

no flowcontrol bidirectional Disables flow control on GE and FE SPA interfaces on a

SIP-401/501/600/601.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-113




To display configuration information and statistics for a Packet over SONET (POS) interface, use the show interfaces pos command in user EXEC or privileged EXEC configuration mode.

Cisco 7000 and Cisco 7500 Series with VIPs show interfaces pos [ slot / port-adapter / port ]

POS Shared Port Adapters show interfaces pos [ slot / subslot / port [ / sub_int ]]

Syntax Description slot / port-adapter / port slot / subslot / port [ / sub_int ]

(Optional) Cisco 7000 or Cisco 7500 Series Routers


2/0/0), where:

•


/ port-adapter— Port adapter number.

•

•

/ port— Port or interface number.

Refer to the appropriate hardware manual for slot and port information, and port adapter compatibility.

(Optional) POS Shared Port Adapters

Number of the chassis slot that contains the POS interface (for example

4/3/0), where: slot —Chassis slot number.

•

•

•

Refer to the appropriate hardware manual for slot information. For

SIPs, refer to the platform-specific SPA hardware installation guide or the corresponding “Identifying Slots and Subslots for SIPs and SPAs” topic in the platform-specific SPA software configuration guide.

/ subslot— Secondary slot number on a SPA interface processor (SIP) where a SPA is installed.


/ port —Port or interface number.

For SPAs, refer to the corresponding “Specifying the Interface

Address on a SPA” topics in the platform-specific SPA software configuration guide.

/ sub_int —(Optional) Subinterface number.

Command Modes User EXEC

Privileged EXEC

19-114


Release 12.0(33)S, OL-8832-01, Rev. C9




11.2

11.3

12.2(25)S3

12.2(18)SXE

12.0(31)S

Modification

The show interface posi command was introduced.

The name of the command was modified from show interface posi to show interfaces pos , and the sample output was updated.

This command was integrated into Cisco IOS Release 12.2(25)S3 to support SPAs on the Cisco 7304 router. The command was modified to support a new addressing format for SPAs.


SPAs on the Cisco 7600 series routers.

This command was integrated into Cisco IOS Release 12.0(31)S to support SPAs on the Cisco 12000 series routers.

Examples Cisco 7513 Example

The following is sample output from the show interfaces pos command on a Cisco 7513 router with one

Packet OC-3 Interface Processor (POSIP):



Hardware is cyBus Packet over Sonet

Description: PRI-T1 net to zippy (4K) to Pac-Bell



Encapsulation HDLC, loopback not set, keepalive set (3 sec)


Last clearing of “show interface” counters 00:23:09






Received 485 broadcasts, 0 runts, 0 giants, 0 parity






Cisco 7600 Series Router POS Shared Port Adapter Example

The following is sample output from the show interfaces pos command on a Cisco 7600 series router for POS interface 4/3/0 (which is the interface for port 0 of the SPA in subslot 3 of the SIP in chassis slot

4):


POS4/3/0 is up, line protocol is up (APS working - active)





Keepalive not set

Scramble disabled



Queueing strategy:fifo


Release 12.0(33)S, OL-8832-01, Rev. C9


19-115








0 parity






Cisco 12000 Series Router POS Shared Port Adapter Example

The following is sample output from the show interfaces pos command on a Cisco 12000 series router for POS interface 1/1/0 (which is the interface for port 0 of the SPA in subslot 1 of the SIP in chassis slot

1):







Keepalive not set

Scramble enabled










0 parity






Table 19-10 describes the significant fields shown in these displays.

Table 19-11 show interfaces pos Field Descriptions


POSx/y/z is up, line protocol is up Indicates whether the interface hardware is currently active and can transmit and receive or whether it has been taken down by an administrator.

Hardware is. . .

Hardware type:

Internet address is

MTU

BW

DLY

•

•

For POSIP— cyBus Packet over Sonet

For POS SPAs—Packet over SONET

Internet address and subnet mask.


Bandwidth of the interface, in kilobits per second.


19-116


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-11 show interfaces pos Field Descriptions (continued)

Field Description rely Reliability of the interface as a fraction of 255 (255/255 is


load

Encapsulation

Loopback

Keepalive

Scramble


The calculation uses the value from the bandwidth interface configuration command.


Indicates whether loopbacks are set.

Indicates whether keepalives are set.

Indicates whether or not SONET payload scrambling is enabled.

SONET scrambling is disabled by default. For the POS SPAs on the

Cisco 12000 series routers, scrambling is enabled by default.

Last input

(Last) output

(Last) output hang

Last clearing

Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.



Time at which the counters that measure cumulative statistics


Queueing strategy


5 minute input rate

5 minute output rate packets input


0:00:00 indicates the counters were cleared more than 22

31 ms

(and less than 2

32 ms) ago.

First-in, first-out (FIFO) queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair).

Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because a queue was full.

Average number of bits and packets received or transmitted per second in the last 5 minutes.


Release 12.0(33)S, OL-8832-01, Rev. C9


19-117




Field Description bytes (input) Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.

no buffer broadcasts

Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count.

Broadcast storms on Ethernets and bursts of noise on serial lines are often responsible for no input buffer events.


runts giants throttles parity input errors




Report of the parity errors on the interface.

CRC


Cyclic redundancy checksum generated by the originating LAN station or far-end device does not match the checksum calculated from the data received. On a LAN, this usually indicates noise or transmission problems on the LAN interface or the LAN bus itself. A high number of CRCs is usually the result of collisions or a station transmitting bad data. On a serial link, CRCs usually indicate noise, gain hits or other transmission problems on the data link.

frame overrun ignored abort packets output bytes (output) underruns

Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.


Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. These buffers are different than the system buffers mentioned previously in the buffer description. Broadcast storms and bursts of noise can cause the ignored count to be incremented.

Illegal sequence of one bits on the interface.



Number of times that the far-end transmitter has been running faster than the near-end router’s receiver can handle.

19-118


Release 12.0(33)S, OL-8832-01, Rev. C9





Field Description output errors Sum of all errors that prevented the final transmission of datagrams out of the interface being examined. Note that this might not balance with the sum of the enumerated output errors, as some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.

applique interface resets output buffer failures output buffers swapped out carrier transitions

Indicates an unrecoverable error has occurred on the POSIP applique. The system then invokes an interface reset.

Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within a certain interval. If the system notices that the carrier detect line of an interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an unrecoverable interface processor error occurred, or when an interface is looped back or shut down.



Number of times the carrier detect signal of the interface has changed state.

Command interface

Description

Configures an interface type and enters interface configuration mode.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-119




To display information about a serial interface, use the show interfaces serial command in privileged

EXEC mode. When using Frame Relay encapsulation, use the show interfaces serial command in user

EXEC or privileged EXEC mode to display information about the multicast data-link connection identifier (DLCI), the DLCIs used on the interface, and the DLCI used for the Local Management

Interface (LMI).

Cisco 4000 Series show interfaces serial [ number [ : channel-group ]] [ accounting ]

Cisco 7000 and Cisco 7500 Series with the RSP7000, RSP7000CI, or Ports on VIPs show interfaces serial [ slot / port-adapter / port ]

Cisco 7500 Series show interfaces serial [ slot / port [ : channel-group ]] [ accounting ]

Cisco 7500 Series with a CT3IP show interfaces serial [ slot / port-adapter / port ][ : t1-channel ] [ accounting | crb ]

Cisco AS5350 and Cisco AS5400 Universal Gateways show interfaces serial slot / port

Cisco AS5800 Access Servers show interfaces serial dial-shelf / slot / t3-port : t1-num : chan-group

T3/E3 Shared Port Adapters and 2-Port and 4-Port Channelized T3 SPA in Unchannelized Mode show interfaces serial [ slot / subslot / port ]

Channelized T3 Shared Port Adapters show interfaces serial [ slot / subslot / port / t1-num : channel-group ]

Syntax Description number

: channel-group accounting

(Optional) Number of the port being displayed.

(Optional) On the Cisco 4000 series with a Network Management Processor

(NPM) or the Cisco 7500 series routers with a MultiChannel Interface Processor

(MIP), specifies the T1 channel-group number in the range of 0 to 23 defined with the channel-group controller configuration command.

For channelized T3 SPAs, number 0–23 of the DS0 link on the T1 channel.

(Optional) Displays the number of packets of each protocol type that have been sent through the interface.

19-120


Release 12.0(33)S, OL-8832-01, Rev. C9


show interfaces serial slot port port-adapter subslot

: t1-channel crb dial-shelf slot t3-port

: t1-num

: chan-group

(Optional) Chassis slot number.


“Identifying Slots and Subslots for SIPs and SPAs” topic in the platform-specific

SPA software configuration guide.

(Optional) Number of the port being displayed. Refer to the appropriate hardware manual for slot and port information.

(Optional) Number of the port adapter being displayed. Refer to the appropriate hardware manual for information about port adapter compatibility.



(Optional) T1 channel number. For the CT3IP, the T1 channel is a number between 1 and 28.

T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme (0 to 27) used with other Cisco products. This scheme ensures consistency with telco numbering schemes for T1 channels within channelized T3 equipment.

(Optional) Displays interface routing and bridging information.

Dial-shelf chassis in the Cisco AS5800 access server that contains the CT3 interface card.

Location of the CT3 interface card in the dial shelf chassis.

T3 port number. The only valid value is 0.

T1 time slot in the T3 line. The value can be from 1 to 28.

Channel group identifier.


Command Modes User EXEC when Frame Relay encapsulation is used

Privileged EXEC


10.0

11.0

11.1CA

11.3

12.0(3)T

Modification

This command was introduced on the Cisco 4000 series routers.

This command was implemented on the Cisco 7000 series routers.

This command was modified to include sample output for the PA-2JT2,

PA-E3, and PA-T3 serial port adapters.

This command was modified to include the CT3IP.

This command was implemented on the Cisco AS5800 access servers. This command was modified to include support for flow-based WRED.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-121



Release

12.0(4)T

12.0(7)T

12.2(11)T

12.2(13)T

12.2S

12.2(18)SXE

12.0(31)S

Modification

This command was modified to include enhanced display information for dialer bound interfaces.

This command was modified to include dialer as an interface type, and to reflect the default behavior.

This command was implemented on the Cisco AS5350 and Cisco AS5400.

This command was modified to display information about Frame Relay interface queueing and fragmentation.




Usage Guidelines Frame Relay

Use this command to determine the status of the Frame Relay link. This display also indicates Layer 2 status if switched virtual circuits (SVCs) are configured.

Channel Groups as Virtual Serial Interfaces

To find out about channel groups configured as virtual serial interfaces, to verify that the router has

High-Level Data Link Control (HDLC) encapsulation on the interface, and to verify that the interface sees the loopback, use the show interfaces serial command in privileged EXEC mode.

Examples Example of Synchronous Serial Interface

The following is sample output from the show interfaces serial command for a synchronous serial interface:

Router# show interfaces serial

Serial 0 is up, line protocol is up

Hardware is MCI Serial

Internet address is 192.168.10.203, subnet mask is 255.255.255.0





Five minute input rate 0 bits/sec, 0 packets/sec

Five minute output rate 0 bits/sec, 0 packets/sec


Received 13983 broadcasts, 0 runts, 0 giants




0 output errors, 0 collisions, 2 interface resets, 0 restarts


19-122


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-12 show interfaces serial Field Descriptions—Synchronous Serial Interface

Field

Serial ... is {up | down} ... is administratively down

Description

Indicates whether the interface hardware is currently active (whether carrier detect is present), is currently inactive, or has been taken down by an administrator. line protocol is

{up | down}

Hardware is

Internet address is

MTU

BW

DLY rely

Indicates whether the software processes that handle the line protocol consider the line usable (that is, whether keepalives are successful) or whether the line has been taken down by an administrator.

Specifies the hardware type.

Specifies the Internet address and subnet mask.


Indicates the value of the bandwidth parameter that has been configured for the interface (in kbps). If the interface is attached to a serial line with a line speed that does not match the default (1536 or 1544 kbps for T1 and

56 kbps for a standard synchronous serial line), use the bandwidth command to specify the correct line speed for this serial line.


load

Encapsulation loopback keepalive

Last input

Reliability of the interface as a fraction of 255 (255/255 is 100 percent reliability), calculated as an exponential average over 5 minutes.



Indicates whether or not loopback is set.

Indicates whether or not keepalives are set.

Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router.

Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.

Last output output hang




Number of packets in output and input queues. Each number is followed by a slash, the maximum size of the queue, and the number of packets dropped because of a full queue.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-123



Table 19-12

Field

5 minute input rate

5 minute output rate packets input bytes no buffer

Received... broadcasts runts giants input errors

CRC frame overrun ignored abort packets output show interfaces serial Field Descriptions—Synchronous Serial Interface (continued) carrier transitions

Description

Average number of bits and packets transmitted per second in the last

5 minutes.

The 5-minute input and output rates should be used only as an approximation of traffic per second during a given 5-minute period. These rates are exponentially weighted averages with a time constant of

5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.


Total number of bytes, including data and MAC encapsulation, in the error-free packets received by the system.

Number of received packets discarded because there was no buffer space in the main system. Compare with ignored count. Broadcast storms on

Ethernet networks and bursts of noise on serial lines are often responsible for no input buffer events.





Cyclic redundancy checksum generated by the originating station or far-end device does not match the checksum calculated from the data received. On a serial link, CRCs usually indicate noise, gain hits, or other transmission problems on the data link.

Number of packets received incorrectly having a CRC error and a noninteger number of octets. On a serial line, this is usually the result of noise or other transmission problems.


Number of received packets ignored by the interface because the interface hardware ran low on internal buffers. Broadcast storms and bursts of noise can cause the ignored count to be increased.

Illegal sequence of one bits on a serial interface. This usually indicates a clocking problem between the serial interface and the data link equipment.

Number of times the carrier detect signal of a serial interface has changed state. For example, if data carrier detect (DCD) goes down and comes up, the carrier transition counter will increment two times. Indicates modem or line problems if the carrier detect line is changing state often.


19-124


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-12 show interfaces serial Field Descriptions—Synchronous Serial Interface (continued)

Field bytes output underruns output errors

Description


Number of times that the transmitter has been running faster than the router can handle. This might never be reported on some interfaces.

Sum of all errors that prevented the final transmission of datagrams out of the interface from being examined. Note that this might not balance with the sum of the enumerated output errors because some datagrams can have more than one error, and others can have errors that do not fall into any of the specifically tabulated categories.

collisions interface resets restarts alarm indications, remote alarms, rx LOF, rx LOS

BER inactive, NELR inactive, FELR inactive

Number of messages retransmitted because of an Ethernet collision. Some collisions are normal. However, if your collision rate climbs to around 4 or 5 percent, you should consider verifying that there is no faulty equipment on the segment and/or moving some existing stations to a new segment. A packet that collides is counted only once in output packets.

Number of times an interface has been completely reset. This can happen if packets queued for transmission were not sent within several seconds’ time. On a serial line, this can be caused by a malfunctioning modem that is not supplying the transmit clock signal or by a cable problem. If the system notices that the carrier detect line of a serial interface is up, but the line protocol is down, it periodically resets the interface in an effort to restart it. Interface resets can also occur when an interface is looped back or shut down.

Number of times the controller was restarted because of errors.

Number of CSU/DSU alarms and number of occurrences of receive loss of frame and receive loss of signal.

Status of G.703-E1 counters for bit -error rate (BER) alarm, near-end loop remote (NELR), and far-end loop remote (FELR). Note that you cannot set the NELR or FELR.

Example of PA-2JT2 Serial Interface

The following is sample output from the show interfaces serial command for a PA-2JT2 serial interface:

Router# show interfaces serial 3/0/0

Serial3/0/0 is up, line protocol is up

Hardware is cyBus Serial



Encapsulation HDLC, loopback not set, keepalive not set












Release 12.0(33)S, OL-8832-01, Rev. C9


19-125





0 cv errors, 0 crc5 errors, 0 frame errors

rxLOS inactive, rxLOF inactive, rxPAIS inactive

rxAIS inactive, rxRAI inactive, rxHBER inactive

Table 19-13 describes significant fields shown in the display that are different from the fields described in Table 19-12 .

Table 19-13 show interfaces serial Field Descriptions—PA-2JT2 Serial Interface

Field

Last clearing of “show interface” counters

Description

Time the counters were last cleared.

Queueing strategy output buffer failures

First-in, first-out queueing strategy (other queueing strategies that you might see are priority-list, custom-list, and weighted fair).

Number of “no resource” errors received on the output.

output buffers swapped out Number of packets swapped to DRAM.

carrier transitions cv errors crc5 errors

Number of times the carrier detect signal of a serial interface has changed state. For example, if data carrier detect (DCD) goes down and comes up, the carrier transition counter will increment two times.

Indicates modem or line problems if the carrier detect line is changing state often.

B8ZS/B6ZS (zero suppression) coding violation counter.

CRC-5 error counter.

frame errors rxLOS rxLOF rxPAIS rxAIS rxRAI rxHBER

Framing error counter.

Receive loss of signal alarm. Values are active or inactive.

Receive loss of frame alarm. Values are active or inactive.

Receive loss of payload alarm indication signal (AIS). Values are active or inactive.

Receive loss of physical AIS. Values are active or inactive.

Receive remote AIS. Values are active or inactive.

Receive high bit-error rate alarm. Values are active or inactive.

Example of PA-E3 Serial Port Adapter

The following is sample output from the show interfaces serial command for a PA-E3 serial port adapter installed in chassis slot 2:

Router# show interfaces serial 2/0


Hardware is M1T-E3 pa




Last input 1w0d, output 00:00:48, output hang never

Last clearing of “show interface” counters 1w0d





19-126


Release 12.0(33)S, OL-8832-01, Rev. C9




Received 0 broadcasts, 0 runts, 0 giants, 0 parity







txAIS inactive, rxRAI inactive, txRAI inactive

Table 19-14 describes significant fields shown in the display that are different from the fields described in Table 19-12 on page 19-123 .

Table 19-14 show interfaces serial Field Descriptions—PA-E3

Field


Queueing strategy

Description

Time the counters were last cleared.


Number of the parity errors on the interface.

parity applique Indicates that an unrecoverable error has occurred on the E3 applique.

The router then invokes an interface reset.


output buffer failures output buffers swapped out Number of packets swapped to DRAM.

rxLOS, rxLOF, rxAIS Receive loss of signal, loss of frame, and alarm indication signal status.

Values are inactive or active.

txAIS, rxRAI, txRAI Transmit alarm indication signal, receive remote alarm indicator, and transmit remote alarm indicator status. Values are inactive or active.

When the router receives an LOS, LOF, or AIS, the txRAI is active.

When the remote router receives an LOS, LOF, or AIS, the rxRAI is active.

Example of 1-Port PA-T3 Serial Port Adapter Installed in a VIP2

The following is sample output from the show interfaces serial command for a 1-port PA-T3 serial port adapter installed in a VIP2 in chassis slot 1, in port adapter slot 0:

Router# show interfaces serial 1/0/0


Hardware is cyBus PODS3 Serial





Last clearing of “show interface” counters 5d02h







0 parity



Release 12.0(33)S, OL-8832-01, Rev. C9


19-127









Table 19-15 show interfaces serial Field Descriptions—PA-T3

Field


Queueing strategy

Description

Time the counters were last cleared. parity applique


Number of the parity errors on the interface.

Indicates that an unrecoverable error has occurred on the T3 applique. The router then invokes an interface reset.


Number of packets swapped to DRAM.

output buffer failures output buffers swapped out rxLOS, rxLOF, rxAIS txAIS, rxRAI, txRAI

Receive loss of signal, loss of frame, and alarm indication signal status.

Values are inactive or active.

Transmit alarm indication signal, receive remote alarm indicator, and transmit remote alarm indicator status. Values are inactive or active. When the router receives an LOS, LOF, or AIS, the txRAI is active. When the remote router receives an LOS, LOF, or AIS, the rxRAI is active.

Example of CT3IP Serial Interface

The following is sample output from the show interfaces serial command for the CT3IP serial interface:

Router# show interfaces serial 3/0/0:25


Hardware is cyBus T3






Input queue: 0/75/0 (size/max/drops); Total output drops: 0


Output queue: 0/64/0 (size/threshold/drops)

Conversations 0/1 (active/max active)











19-128


Release 12.0(33)S, OL-8832-01, Rev. C9



Timeslot(s) Used:1-24, Transmitter delay is 0 flags, transmit queue length 5

non-inverted data

Table 19-16 describes significant fields relevant to the CT3IP shown in the display that are different from the fields described in Table 19-12 on page 19-123 .

Table 19-16 show interfaces serial Field Descriptions—CT3IP

Field

Timeslot(s) Used

Transmitter delay transmit queue length non-inverted data

Description

Number of time slots assigned to the T1 channel.

Number of idle flags inserted between each HDLC frame.

Number of packets allowed in the transmit queue.

Indicates whether or not the interface is configured for inverted data.

Example of an HDLC Synchronous Serial Interface on a Cisco 7500 Series Router

The following is sample output from the show interfaces serial command for an HDLC synchronous serial interface on a Cisco 7500 series router:



Hardware is cxBus Serial





Last clearing of “show interface” counters 2w4d










Table 19-12 on page 19-123 describes significant fields shown in the display.

Example of HDLC Encapsulation

The following example displays High-Level Data Link Control (HDLC) encapsulation on serial interface

0:

Router# show interfaces serial 0

Serial0 is up, line protocol is up (looped)

Hardware is HD64570



Encapsulation HDLC, loopback set, keepalive set (10 sec)


Release 12.0(33)S, OL-8832-01, Rev. C9


19-129



Example of a G.703 Interface with Framing

The following is sample output from the show interfaces serial command for a G.703 interface on which framing is enabled:



Hardware is cxBus Serial





Last clearing of “show interface” counters never










19-130


Release 12.0(33)S, OL-8832-01, Rev. C9



2 alarm indications, 333 remote alarms, 332 rx LOF, 0 rx LOS

RTS up, CTS up, DTR up, DCD up, DSR up

BER inactive, NELR inactive, FELR inactive


Example with Frame Relay Encapsulation

When using Frame Relay encapsulation, use the show interfaces serial command to display information on the multicast data-link connection identifier (DLCI), the DLCI of the interface, and the DLCI used for the Local Management Interface (LMI).

The multicast DLCI and the local DLCI can be set using the frame-relay multicast-dlci and frame-relay local-dlci configuration commands. The status information is taken from the LMI, when active.

The following is sample output from the show interfaces serial command when Frame Relay encapsulation and LMI are enabled:



Hardware type is MCI Serial



Encapsulation FRAME-RELAY, loopback not set, keepalive set (10 sec)

multicast DLCI 1022, status defined, active

source DLCI 20, status defined, active

LMI DLCI 1023, LMI sent 10, LMI stat recvd 10, LMI upd recvd 2








518 packets output, 391205 bytes



In this display, the multicast DLCI has been changed to 1022 using the frame-relay multicast-dlci interface configuration command.

The display shows the statistics for the LMI as the number of status inquiry messages sent (LMI sent), the number of status messages received (LMI recvd), and the number of status updates received (upd recvd). Refer to the Frame Relay Interface specification for additional explanations of this output.

Example with Frame Relay Queueing and Fragmentation at the Interface

The following is sample output from the show interfaces serial command when low-latency queueing and FRF.12 end-to-end fragmentation are configured on a Frame Relay interface:



Hardware is M4T





LMI enq sent 0, LMI stat recvd 0, LMI upd recvd 0, DTE LMI up

LMI enq recvd 0, LMI stat sent 0, LMI upd sent 0

LMI DLCI 1023 LMI type is CISCO frame relay DTE

Release 12.0(33)S, OL-8832-01, Rev. C9


19-131



Fragmentation type: end-to-end, size 80, PQ interleaves 0


Last input 2d15h, output 2d15h, output hang never




Output queue: 0/1000/64/0 (size/max total/threshold/drops)

Conversations 0/0/256 (active/max active/max total)











1 carrier transitions DCD=up DSR=up DTR=up RTS=up CTS=up


Table 19-17 show interfaces serial Field Descriptions—Frame Relay Interface Queueing and

Fragmentation

Field txload rxload crc

LMI enq sent

LMI stat recvd

LMI upd recvd

DTE LMI up

LMI enq recvd

LMI stat sent

LMI upd sent

Fragmentation type size

PQ interleaves

Broadcast queue broadcasts sent/dropped interface broadcasts

Input queue

Queueing strategy

Description

Interface load in the transmit direction.

Interface load in the receive direction.

Number of Layer 1 checksum errors during reception.

Number of Frame Relay status inquiry messages sent.

Number of Frame Relay status request messages received.

Number of single PVC asynchronous status messages received.

LMI peers are synchronized.

Number of Frame Relay status inquiry messages received.

Number of Frame Relay status request messages sent.

Number of single PVC asynchronous status messages sent.

Type of fragmentation: end-to-end, Cisco, or VoFR

Fragmentation size.

Number of priority queue frames that have interleaved data fragments.

Number on queue/queue depth.

Number of broadcasts sent and dropped.

Number of broadcasts sent on interface.

size—Current size of the input queue. max—Maximum size of the queue.

drops—Number of messages discarded.

flushes—Number of times that data on queue has been discarded.

Type of queueing configured on the interface.

19-132


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-17 show interfaces serial Field Descriptions—Frame Relay Interface Queueing and

Fragmentation (continued)

Field

Output queue

Conversations throttles

Description size—Current size of the output queue.

max total—Maximum number of frames that can be queued.

threshold—Congestive-discard threshold. Number of messages in the queue after which new messages for high-bandwidth conversations are dropped.

drops—Number of dropped messages.

active—Number of currently active conversations.

max active—Maximum number of conversations that have ever occurred at one time. max total—Maximum number of active conversations allowed.

Number of times the receiver on the port was disabled, possibly because of processor or buffer overload.

output buffer failures output buffers swapped out


Number of packets swapped to DRAM.

Example with ANSI LMI

For a serial interface with the ANSI Local Management Interface (LMI) enabled, use the show interfaces serial command to determine the LMI type implemented. The following is sample output from the show interfaces serial command for a serial interface with the ANSI LMI enabled:






Encapsulation FRAME-RELAY, loopback not set, keepalive set

LMI DLCI 0, LMI sent 10, LMI stat recvd 10

LMI type is ANSI Annex D










Notice that the show interfaces serial output for a serial interface with ANSI LMI shown in this display is very similar to that for encapsulation set to Frame Relay, as shown in the previous display. Table 19-18 describes the few differences that exist.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-133



Table 19-18 show interfaces serial Field Descriptions—ANSI LMI

Field

LMI DLCI

LMI sent

LMI type is ANSI

Annex D

Description

Identifies the DLCI used by the LMI for this interface. The default is 1023.

Number of LMI packets that the router sent.

Indicates that the interface is configured for the ANSI-adopted Frame Relay specification T1.617 Annex D.

Example with LAPB Encapsulation

Use the show interfaces serial command to display operation statistics for an interface that uses Link

Access Procedure, Balanced (LAPB) encapsulation. The following is partial sample output from the show interfaces serial command for a serial interface that uses LAPB encapsulation:


LAPB state is SABMSENT, T1 3000, N1 12056, N2 20, k7,Protocol ip

VS 0, VR 0, RCNT 0, Remote VR 0, Retransmissions 2

IFRAMEs 0/0 RNRs 0/0 REJs 0/0 SABMs 3/0 FRMRs 0/0 DISCs 0/0

Table 19-19 shows the fields relevant to all LAPB connections.

Table 19-19

Field

LAPB state is

T1 3000, N1 12056, ...

Protocol

VS

VR

RCNT

Remote VR

Retransmissions

IFRAMEs

RNRs

REJs

SABMs

FRMRs

DISCs show interfaces serial Field Descriptions—LAPB

Window is closed

Description

State of the LAPB protocol.

Current parameter settings.

Protocol encapsulated on a LAPB link; this field is not present on interfaces configured for multiprotocol LAPB or X.25 encapsulations.

Modulo 8 frame number of the next outgoing information frame.

Modulo 8 frame number of the next information frame expected to be received.

Number of received information frames that have not yet been acknowledged.

Number of the next information frame that the remote device expects to receive.

Count of current retransmissions because of expiration of T1.

No more frames can be transmitted until some outstanding frames have been acknowledged. This message should be displayed only temporarily.

Count of information frames in the form of sent/received.

Count of Receiver Not Ready frames in the form of sent/received.

Count of Reject frames in the form of sent/received.

Count of Set Asynchronous Balanced Mode commands in the form of sent/received.

Count of Frame Reject frames in the form of sent/received.

Count of Disconnect commands in the form of sent/received.

19-134


Release 12.0(33)S, OL-8832-01, Rev. C9



Example with PPP Encapsulation

The output for an interface configured for synchronous PPP encapsulation differs from the standard show interfaces serial output. An interface configured for PPP might include the following information:

Router# show interfaces serial 1 lcp state = OPEN ncp ipcp state = OPEN ncp osicp state = NOT NEGOTIATED ncp ipxcp state = NOT NEGOTIATED ncp deccp state = NOT NEGOTIATED ncp bridgecp state = NOT NEGOTIATED ncp atalkcp state = NOT NEGOTIATED

Table 19-20 show the fields relevant to PPP connections.

Table 19-20 show interfaces serial Field Descriptions—PPP Encapsulation

Field lcp state ncp ipcp state ncp osicp state ncp ipxcp state ncp deccp state ncp bridgecp state ncp atalkcp state

Description

Link Control Protocol.

Network Control Protocol Internet Protocol Control Protocol.

Network Control Protocol OSI (CLNS) Control Protocol.

Network Control Protocol IPX (Novell) Control Protocol.

Network Control Protocol DECnet Control Protocol.

Network Control Protocol Bridging Control Protocol.

Network Control Protocol AppleTalk Control Protocol.

Example with SDLC Connections

Use the show interfaces serial command to display the Synchronous Data Link Control (SDLC) information for a given SDLC interface. The following is sample output from the show interfaces serial command for an SDLC primary interface that supports the SDLLC function:





Encapsulation SDLC-PRIMARY, loopback not set

Timers (msec): poll pause 100 fair poll 500. Poll limit 1

[T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: none

SDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10

largest token ring frame 2052]

SDLC addr C1 state is CONNECT

VS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0

Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0

Poll: clear, Poll count: 0, chain: p: C1 n: C1

SDLLC [largest SDLC frame: 265, XID: disabled]











Release 12.0(33)S, OL-8832-01, Rev. C9


19-135



Table 19-21 shows the fields relevant to all SDLC connections.

Table 19-21 show interfaces serial Field Descriptions—SDLC Enabled

Field

Timers (msec): poll pause, fair poll, Poll limit

T1, N1, N2, K

Description

Current values of these timers for the primary SDLC interface.

Values for these parameters for the primary SDLC interface.

Table 19-22 shows other data given for each SDLC secondary interface configured to be attached to the serial interface.

Table 19-22 SDLC Secondary Interface Descriptions

Field addr state is

VS

VR

Remote VR

Current retransmit count:

Hold queue

IFRAMEs, RNRs, SNRMs,

DISCs

Description

Address of this SDLC secondary interface.

Current state of this connection, which is one of the following:

•

•

DISCONNECT—No communication is being attempted to this secondary.

CONNECT—A normal connect state exists between this router and this secondary.

•

•

•

•

DISCSENT—This router has sent a disconnect request to this secondary and is awaiting its response.

SNRMSENT—This router has sent a connect request

(SNRM) to this secondary and is awaiting its response.

THEMBUSY—This secondary has told this router that it is temporarily unable to receive any more information frames.

USBUSY—This router has told this secondary that it is temporarily unable to receive any more information frames.

•

•

BOTHBUSY—Both sides have told each other that they are temporarily unable to receive any more information frames.

ERROR—This router has detected an error and is waiting for a response from the secondary acknowledging this.

Sequence number of the next information frame that this station sends.

Sequence number of the next information frame from this secondary that this station expects to receive.

Last frame transmitted by this station that has been acknowledged by the other station.

Number of times the current I-frame or sequence of I-frames has been retransmitted.

Number of frames in hold queue and maximum size of hold queue.

Sent/received count for these frames.

19-136


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-22

Field

Poll

Poll count chain

SDLC Secondary Interface Descriptions (continued)

Description

“Set” if this router has a poll outstanding to the secondary; “clear” if it does not.

Number of polls in a row that have been given to this secondary at this time.

Shows the previous (p) and next (n) secondary address on this interface in the round robin loop of polled devices.

Example with SDLLC

Use the show interfaces serial command to display the SDLLC statistics for SDLLC-configured interfaces. The following is sample output from the show interfaces serial command for a serial interface configured for SDLLC:





Encapsulation SDLC-PRIMARY, loopback not set

Timers (msec): poll pause 100 fair poll 500. Poll limit 1

[T1 3000, N1 12016, N2 20, K 7] timer: 56608 Last polled device: none

SDLLC [ma: 0000.0C01.14--, ring: 7 bridge: 1, target ring: 10

largest token ring frame 2052]

SDLC addr C1 state is CONNECT

VS 6, VR 3, RCNT 0, Remote VR 6, Current retransmit count 0

Hold queue: 0/12 IFRAMEs 77/22 RNRs 0/0 SNRMs 1/0 DISCs 0/0

Poll: clear, Poll count: 0, chain: p: C1 n: C1

SDLLC [largest SDLC frame: 265, XID: disabled]










6608 Last polled device: none

SDLLC [ma: 0000.0C01.14--, ring: 7 brid2 carrier transitions

Most of the output shown in the display is generic to all SDLLC-encapsulated interfaces and is described in the Cisco IOS Bridging and IBM Networking Command Reference , Volume 2 of 2: IBM Networking.

Table 19-23 shows the parameters specific to SDLLC.

Table 19-23

Field

SDLLC ma

SDLLC Parameter Descriptions ring, bridge, target ring largest token ring frame

Description

Lists the MAC address configured for this interface. The last byte is shown as “--” to indicate that it is filled in with the SDLC address of the connection.

Lists the parameters as configured by the sdllc traddr command.

Shows the largest Token Ring frame that is accepted on the Logical Link control, type 2 (LLC2) side of the connection.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-137



Table 19-23

XID

SDLLC Parameter Descriptions (continued)

Field largest SDLC frame

Description

Shows the largest SDLC frame that is accepted and will be generated on the SDLC side of the connection.

Enabled or disabled: Shows whether XID processing is enabled on the

SDLC side of the connection. If enabled, it will show the XID value for this address.

Example with X.25

The following is partial sample output from the show interfaces serial command for a serial X.25 interface:


X25 address 000000010100, state R1, modulo 8, idle 0, timer 0, nvc 1

Window size: input 2, output 2, Packet size: input 128, output 128

Timers: T20 180, T21 200, T22 180, T23 180, TH 0

Channels: Incoming-only none, Two-way 1-1024, Outgoing-only none

(configuration on RESTART: modulo 8,

Window size: input 2 output 2, Packet size: input 128, output 128

Channels: Incoming-only none, Two-way 5-1024, Outgoing-only none)

RESTARTs 3/2 CALLs 1000+2/1294+190/0+0/ DIAGs 0/0

The stability of the X.25 protocol requires that some parameters not be changed without a restart of the protocol. Any change to these parameters is held until a restart is sent or received. If any of these parameters changes, information about the router configuration at restart will be displayed as well as the values that are currently in effect.


Table 19-24

Field

X25 address state modulo idle timer nvc show interfaces serial Field Descriptions—X.25 Enabled

Description

Address used to originate and accept calls.

State of the interface. Possible values follow:

•

•

R1 is the normal ready state.

R2 is the DTE restarting state.

• R3 is the DCE restarting state.

If the state is R2 or R3, the interface is awaiting acknowledgment of a Restart packet.

Modulo value; determines the packet sequence numbering scheme used.

Number of minutes for which the Cisco IOS software waits before closing idle virtual circuits that it originated or accepted.

Value of the interface timer, which is zero unless the interface state is R2 or R3.

Default maximum number of simultaneous virtual circuits permitted to and from a single host for a particular protocol.

19-138


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-24

Timers:

TH show interfaces serial Field Descriptions—X.25 Enabled (continued)

Field

Window size: input, output

Packet size: input, output

Description

Default window sizes (in packets) for the interface. The x25 facility interface configuration command can be used to override these default values for the switched virtual circuits originated by the router.

Default maximum packet sizes (in bytes) for the interface. The x25 facility interface configuration command can be used to override these default values for the switched virtual circuits originated by the router.

Values of the X.25 timers:

•

•

T10 through T13 for a DCE device

T20 through T23 for a DTE device

Packet acknowledgment threshold (in packets). This value determines how many packets are received before an explicit acknowledgment is sent. The default value (0) sends an explicit acknowledgment only when the incoming window is full.

Displays the virtual circuit ranges for this interface.

Channels: Incoming-only,

Two-way, Outgoing-only

RESTARTs

CALLs

DIAGs

Shows Restart packet statistics for the interface using the format

Sent/Received.

Successful calls sent + failed calls/calls received + calls failed/calls forwarded + calls failed. Calls forwarded are counted as calls sent.

Diagnostic messages sent and received.

Example with Accounting Option

The following example illustrates the show interfaces serial command with the accounting option on a Cisco 7500 series routers:

Router# show interfaces serial 1/0 accounting

Serial1/0

Protocol Pkts In Chars In Pkts Out Chars Out

IP 7344 4787842 1803 1535774

Appletalk 33345 4797459 12781 1089695

DEC MOP 0 0 127 9779

ARP 7 420 39 2340


Release 12.0(33)S, OL-8832-01, Rev. C9


19-139



Table 19-25

Field

Protocol

Pkts In

Chars In

Pkts Out

Chars Out show interfaces serial Field Descriptions—Accounting

Description

Protocol that is operating on the interface.

Number of packets received for that protocol.

Number of characters received for that protocol.

Number of packets transmitted for that protocol.

Number of characters transmitted for that protocol.

Example with Cisco AS5800 Access Server

The following example shows the activity that occurred on the serial interface in shelf 1, slot 4, port 0 for time slot 2 in group 23:

Router# show interfaces serial 1/4/0:2:23

Serial1/4/0:2:23 is up, line protocol is up (spoofing)

Hardware is DS-T1


Encapsulation HDLC, loopback not set














Timeslot(s) Used:24, subrate: 64Kb/s, transmit delay is 0 flags

Table 19-26 describes the significant fields shown in the display that are different from the fields described in Table 19-12 on page 19-123 .

Table 19-26 show interfaces serial Field Descriptions—Cisco AS5800



Queueing strategy

Time at which the counters that measure cumulative statistics (such as number of bytes transmitted and received) were last reset to zero.

Displays the type of queueing configured for this interface. In the example output, the type of queueing configured is FIFO.

throttles output buffer failures output buffer swapped out

Timeslot(s) Used

Number of times that the receiver on the port was disabled, possibly because of buffer or processor overload.

Number of times that the output buffer has failed.

Number of times that the output buffer has been swapped out.

Number of time slots assigned to the T1 channel.

19-140


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-26 show interfaces serial Field Descriptions—Cisco AS5800 (continued)

Field subrate transmit delay is ...

Description

Bandwidth of each time slot.

Number of idle flags inserted between each frame.

Example with a T3/E3 Shared Port Adapter

The following example shows the interface statistics on the first port of a T3/E3 SPA installed in subslot 0 of the SIP located in chassis slot 5.



Hardware is SPA-4T3E3
















0 parity








Table 19-27 describes the fields shown in the show interfaces serial output.

Note The fields appearing in the ouput will vary depending on card type, interface configuration, and the status of the interface.

Table 19-27 T3/E3 SPA—Command Field Descriptions

Field

Serial line protocol is

Hardware is

Internet address is

Description

Name of the serial interface.

If the line protocol is up, the local router has received keepalive packets from the remote router. If the line protocol is down, the local router has not received keepalive packets form the remote router.

Designates the specific hardware type of the interface.

The IP address of the interface.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-141



Table 19-27 T3/E3 SPA—Command Field Descriptions (continued)


MTU The maximum packet size set for the interface.

BW

DLY reliability

Bandwidth in kilobits per second.

Interface delay in microseconds.

txload

Reliability of the interface as a fraction of 255 (255/255 is


Transmit load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.

rxload encapsulation crc loopback keepalive

Last input

Receive load on the interface as a fraction of 255 (255/255 is completely saturated), calculated as an exponential average over 5 minutes.

Encapsulation method.

CRC size in bits.

Indicates whether loopback is set or not.

Indicates whether keepalives are set or not.

Number of hours, minutes, and seconds since the last packet was successfully received by an interface and processed locally on the router. Useful for knowing when a dead interface failed. This counter is updated only when packets are process switched, not when packets are fast switched.

Last ouput output hang

Last clearing of show interface

Number of hours, minutes, and seconds since the last packet was successfully transmitted by an interface. Useful for knowing when a dead interface failed. This counter is updated only when packets are process-switched, not when packets are fast-switched.


Time at which the counters that measure cumulative statistics



0:00:00 indicates the counters were cleared more than 231 ms

(and less than 232 ms) ago.

19-142


Release 12.0(33)S, OL-8832-01, Rev. C9



Table 19-27 T3/E3 SPA—Command Field Descriptions (continued)


Input queue size —Current size of the input queue.

max —Maximum size of the input queue.

drops —Packets dropped because the queue was full.

flushes —Number of times that data on queue has been discarded.

Total output drops

Queueing strategy

Output queue

Total number of dropped packets.

First-in, first-out queueing strategy (other queueing strategies you might see are priority-list, custom-list, and weighted fair). size —Current size of the output queue.

max —Maximum size of the ouput queue.

5-minute input rate

5-minute output rate

Average number of bits and packets received per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic).

The 5-minute input and output rates should be used only as an approximation of traffic per second during a given

5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.

Average number of bits and packets transmitted per second in the last 5 minutes. If the interface is not in promiscuous mode, it senses network traffic it sends and receives (rather than all network traffic).

rxLOS rxLOF rxAIS txAIS rxRAI txRAI

The 5-minute input and output rates should be used only as an approximation of traffic per second during a given

5-minute period. These rates are exponentially weighted averages with a time constant of 5 minutes. A period of four time constants must pass before the average will be within two percent of the instantaneous rate of a uniform stream of traffic over that period.

Receive loss of signal status. Values are inactive or active.

Receive loss of frame status. Values are inactive or active.

Receive alarm indication signal status. Values are inactive or active.

Transmit alarm indication signal status. Values are inactive or active.

Receive remote alarm indication signal status. Values are inactive or active.

Transmit remote alarm indication signal status. Values are inactive or active.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-143


Related Commands Command show controllers serial

Description

Displays controller statistics.


19-144


Release 12.0(33)S, OL-8832-01, Rev. C9


show upgrade fpd file


To display the contents of an FPD image package file, enter the show upgrade fpd file command in privileged EXEC configuration mode.

show upgrade fpd file file-url [ detail ]

Syntax Description file-url detail

Specifies the location of the FPD image package file, beginning with the location or type of storage device (examples include disk0, slot0, tftp, or ftp) and followed by the path to the FPD image.

(Optional) Displays detailed information about the contents of the FPD image package file. This option is intended for use by customer support personnel only.




12.2(20)S6

12.2(25)S3

12.2(18)SXE

12.0(31)S

Modification

This command was introduced and replaced the show upgrade file command on the Cisco 7304 router.

The output of the show upgrade fpd file file-url command was changed to only display brief versioning information. The output generated from this command in previous Cisco IOS releases can still be generated in this release by entering the show upgrade fpd file-url detail command. The detail option is also new in this release.

This command was integrated into Cisco IOS Release 12.2(18)SXE on a



Usage Guidelines This command provides information related to the FPD image package file. Most of the information in this command is useful for customer support purposes only.

Examples The output in the following example shows the show upgrade file command on a Cisco 7600 series router:

Router# show upgrade fpd file tftp://mytftpserver/myname/myfpdpkg/c7600-fpd-pkg.122-18.SXE.pkg

Loading myname/myfpdpkg/c7600-fpd-pkg.122-18.SXE.pkg from 124.0.0.0 (via FastEthernet0):

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

[OK]

Release 12.0(33)S, OL-8832-01, Rev. C9


19-145



Cisco Field Programmable Device Image Package for IOS

C7600 Family FPD Image Package (c7600-fpd-pkg.122-18.SXE.pkg), Version 12.2(SXE)

Copyright (c) 2004-2005 by cisco Systems, Inc.

Built Fri 25-Mar-2005 09:12 by integ

=============================== ================================================

Bundled FPD Image Version Matrix

================================================

Min. Req.

Supported Card Types ID Image Name Version H/W Ver.

=============================== == ========================= ========= =========


2 T3E3 SPA I/O FPGA 0.24 0.0

3 T3E3 SPA E3 FPGA 0.6 0.0

4 T3E3 SPA T3 FPGA 0.14 0.0

------------------------------- -- ------------------------- --------- ---------


2 T3E3 SPA I/O FPGA 0.24 0.0

3 T3E3 SPA E3 FPGA 0.6 0.0

4 T3E3 SPA T3 FPGA 0.14 0.0

------------------------------- -- ------------------------- --------- ---------

8-port Channelized T1/E1 SPA 1 CTE1 SPA ROMMON 2.12 0.140

1 CTE1 SPA ROMMON NP 2.12 0.0

2 CTE1 SPA I/O FPGA 1.2 0.0

------------------------------- -- ------------------------- --------- ---------


2 CT3 SPA I/O FPGA 1.1 0.100

3 CT3 SPA T3 FPGA R1 0.11 0.100

3 CT3 SPA T3 FPGA R2 0.15 0.200

------------------------------- -- ------------------------- --------- ---------


2 CT3 SPA I/O FPGA 1.1 0.100

3 CT3 SPA T3 FPGA R1 0.11 0.100

3 CT3 SPA T3 FPGA R2 0.15 0.200

------------------------------- -- ------------------------- --------- ---------

2-port OC3 POS SPA 1 POS SPA IOFPGA P1 3.4 0.0

1 POS SPA IOFPGA P2 3.4 0.200

------------------------------- -- ------------------------- --------- ---------



------------------------------- -- ------------------------- --------- ---------



------------------------------- -- ------------------------- --------- ---------

2-port OC3 ATM SPA 1 KATM SPA IOFPGA 1.24 0.0

------------------------------- -- ------------------------- --------- ---------


------------------------------- -- ------------------------- --------- ---------


------------------------------- -- ------------------------- --------- ---------

SIP-200 1 SIP-200 I/O FPGA P1 1.1 0.100

1 SIP-200 I/O FPGA P4 1.1 0.400

1 SIP-200 I/O FPGA P6 1.1 0.600

2 SIP-200 EOS FPGA P1 0.27 0.100

2 SIP-200 EOS FPGA P450 1.211 0.450

2 SIP-200 EOS FPGA P5 0.27 0.500

2 SIP-200 EOS FPGA P550 1.211 0.550

2 SIP-200 EOS FPGA P6 1.211 0.600

3 SIP-200 PEG TX FPGA P1 1.129 0.100

3 SIP-200 PEG TX FPGA P6 1.129 0.600

4 SIP-200 PEG RX FPGA P1 1.3 0.100

4 SIP-200 PEG RX FPGA P4 1.3 0.400

4 SIP-200 PEG RX FPGA P6 1.3 0.600

19-146


Release 12.0(33)S, OL-8832-01, Rev. C9



5 SIP-200 ROMMON 1.2 0.100

------------------------------- -- ------------------------- --------- ---------

SIP-400 1 SIP-400 ROMMON 1.1 0.1

2 SIP-400 I/O FPGA 0.82 0.1

3 SIP-400 SWITCH FPGA 0.25 0.1

------------------------------- -- ------------------------- --------- ---------

CWPA2 1 CWPA2 I/O FPGA P1 0.37 0.1

2 CWPA2 EOS FPGA P1 0.28 0.1

3 CWPA2 ROMMON 1.1 0.1

=============================== ================================================

Related Commands Command Description upgrade hw-module subslot Manually upgrades the current FPD image on the specified SPA.

upgrade fpd auto upgrade fpd path

Configures the router to automatically upgrade the FPD image when an FPD version incompatability is detected.

Specifies the location from where the FPD image package should be loaded when an automatic FPD upgrade is initiated by the router.

show hw-module slot fpd Displays the current versions of FPD image files for all of the active

SIPs on a router.

show hw-module subslot fpd Displays the FPD version on each SPA in the router.

show upgrade fpd package default show upgrade fpd progress show upgrade fpd table

Displays which FPD image package is needed for the router to properly support the SPAs.

Displays the progress of the FPD upgrade while an FPD upgrade is taking place.


Release 12.0(33)S, OL-8832-01, Rev. C9


19-147


show upgrade fpd package default


To display which FPD image package is needed for the router to properly support the SPAs for the running Cisco IOS software release, enter the show upgrade fpd package default command in privileged EXEC configuration mode.






12.2(20)S6

12.2(18)SXE

12.0(31)S

Modification

This command was introduced and replaced the show upgrade package default command on the Cisco 7304 router.




Usage Guidelines It is important to note that the output from this command is generated from the Cisco IOS image and provides information regarding the default FPD image package file that is needed for your particular

Cisco IOS release. This command also lists the SPAs supported by the default FPD image package file for the running Cisco IOS image.

Examples In the following example, the original form of the show upgrade package default command output shows that the spa_fpd.122-20-S3.pkg FPD image package file is required if you install the

SPA-4FE-7304 or the SPA-2GE-7304 on this particular router with this particular Cisco IOS release:

Router# show upgrade package default

*************************************************************************

This IOS release supports the following default FPD Image Package(s) for automatic upgrade:

*************************************************************************

19-148


Release 12.0(33)S, OL-8832-01, Rev. C9



SPA FPD Image Package:spa_fpd.122-20.S3.pkg

List of SPAs supported in this package:

Minimal

No. SPA Name HW Ver.

---- ------------------ -------

1) SPA-4FE-7304 0.0

2) SPA-2GE-7304 0.0

---- ------------------ -------





show hw-module slot fpd show hw-module subslot fpd Displays the FPD version on each SPA in the router.

show upgrade fpd file Displays the contents of an FPD image package file.

show upgrade fpd progress show upgrade fpd table

Displays the current versions of FPD image files for all of the active

SIPs on a router.



Release 12.0(33)S, OL-8832-01, Rev. C9


19-149


show upgrade fpd progress


To view the progress of an FPD upgrade while an FPD upgrade is taking place, enter the show upgrade fpd progress command in privileged EXEC configuration mode.






12.2(20)S6

12.2(18)SXE

12.0(31)S

Modification

This command was introduced and replaced the show upgrade progress command on the Cisco 7304 router.




Examples The following example shows the status of FPD updates on the SPAs located in subslots 0 and 1:

Router# show upgrade progress

FPD Image Upgrade Progress Table:

==== =================== ====================================================

Field Programmable Time

Slot Card Description Device :"ID-Name" Needed Time Left State

==== =================== ================== ========== ========== ===========

2/0 SPA-2GE-7304 1-4FE/2GE FPGA 00:06:00 00:05:17 Updating...

---- ------------------- ------------------ ----------- --------- -----------

2/1 SPA-4FE-7304 1-4FE/2GE FPGA --:--:-- --:--:-- Waiting...

==== =================== ====================================================






SIPs on a router.


19-150


Release 12.0(33)S, OL-8832-01, Rev. C9



Command show upgrade fpd file show upgrade fpd package default show upgrade fpd table

Description




Release 12.0(33)S, OL-8832-01, Rev. C9


19-151


show upgrade fpd table


To view various information used by the Cisco IOS software to manage the FPD image package file, enter the show upgrade fpd table command in privileged EXEC configuration mode.






12.2(20)S6

12.2(18)SXE

12.0(32)S

Modification

This command was introduced and replaced the show upgrade table command on the Cisco 7304 router.




Usage Guidelines This command provides version information used by the Cisco IOS image to manage the FPD image package file and to locate the correct FPD image within the FPD image package file to perform an FPD upgrade. Most of the information provided by this command is useful for customer support purposes.

Examples The following example displays various FPD information for Cisco IOS Release 12.2(20)S5:

Router# show upgrade table

Field Programmable Devices (FPD) Bundle Information Table:

==========================================================

Table Entry #1:

Bundle Card Type:SPA-4FE-7304 (0x435)

Platform Family:0x0

Bundle Name Prefix:spa_4fe2ge

Bundle Version:0.5

Minimal H/W Version:0.0

FPD Image Count:1

FPD Image Required:

Min. Required

FPD ID FPD Name Version

------ ------------------------ -------------

1 Data & I/O FPGA 4.17

------ ------------------------ -------------

19-152


Release 12.0(33)S, OL-8832-01, Rev. C9



Table Entry #2:

Bundle Card Type:SPA-2GE-7304 (0x436)

Platform Family:0x0

Bundle Name Prefix:spa_4fe2ge

Bundle Version:0.5

Minimal H/W Version:0.0

FPD Image Count:1

FPD Image Required:

Min. Required

FPD ID FPD Name Version

------ ------------------------ -------------

1 Data & I/O FPGA 4.17

------ ------------------------ -------------






SIPs on a router.



show upgrade fpd package default show upgrade fpd progress



Release 12.0(33)S, OL-8832-01, Rev. C9


19-153


speed

speed


To configure the speed for a Fast Ethernet interface, use the speed command in interface configuration mode. To return to the default setting, use the no form of this command.

speed { 10 | 100 | auto } no speed

10

100 auto

Configures the interface to transmit at 10 Mbps.

Configures the interface to transmit at 100 Mbps.

Enables autonegotiation. The interface automatically operates at 10 Mbps or

100 Mbps depending on environmental factors, such as the type of media and transmission speeds for the peer routers, hubs, and switches used in the network configuration. This is the default.

Defaults Auto



11.2(10)P

12.2(20)S1

12.0(32)S

Modification


This command was integrated into Cisco IOS Release 12.2(20)S1 and the default value was modified to Auto.

This command was integrated into Cisco IOS Release 12.2(32)S for the


Usage Guidelines To enable the autonegotiation capability on an interface, you must set either the speed command or the duplex command to auto . The default configuration is that both commands are set to auto .

Table 28 describes the interface behavior for different combinations of the

duplex and speed command settings. The specified duplex command configured with the specified speed command produces the resulting system action.

If you specify both a duplex and speed setting on an interface other than auto , then autonegotiation is disabled for the interface.

Note If you need to force an interface port to operate with certain settings and therefore disable autonegotiation, you must be sure that the remote link is configured for compatible link settings for proper transmission. This includes support of flow control on the link.

19-154


Release 12.0(33)S, OL-8832-01, Rev. C9


speed

Note Every interface on a 4-Port 10/100 Fast Ethernet SPA and 2-Port 10/100/1000 Gigabit Ethernet SPA automatically supports transmission of pause frames to stop packet flow when the MSC is full. You cannot disable flow control for an interface on the 4-Port 10/100 Fast Ethernet SPA or 2-Port

10/100/1000 Gigabit Ethernet SPA. Therefore, flow control support is not configurable, but it is advertised during autonegotiaton.

If you disable autonegotiation, then you must be sure that the remote device is configured to support flow control because flow control is automatically enabled for all interfaces on the 4-Port 10/100 Fast

Ethernet SPA and the 2-Port 10/100/1000 Gigabit Ethernet SPA.

Table 28 Relationship Between duplex and speed Commands duplex Command duplex auto duplex auto duplex half duplex half duplex full or speed Command speed auto

Resulting System Action

Autonegotiates both speed and duplex mode.

The interface advertises capability for the following link settings:

• 10 Mbps and half duplex

•

•

10 Mbps and full duplex

100 Mbps and half duplex

• 100 Mbps and full duplex speed 100 or speed 10 Autonegotiates the duplex mode. The interface advertises capability for the configured speed with capability for both half-duplex or full-duplex mode.

For example, if the speed 100 command is configured with duplex auto , then the interface advertises the following capability:

duplex full speed auto speed 10 speed 10

•

•

100 Mbps and half duplex


Autonegotiates the speed. The interface advertises capability for the configured duplex mode with capability for both 10 Mbps or 100

Mbps operation.

For example, if the duplex full command is configured with the speed auto command, then the interface advertises the following capability:

•

•



Forces 10 Mbps and half-duplex operation, and disables autonegotiation on the interface.

Forces 10 Mbps and full-duplex operation, and disables autonegotiation on the interface.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-155


speed

Table 28 Relationship Between duplex and speed Commands (continued) duplex Command duplex half duplex full speed Command speed 100 speed 100

Resulting System Action

Forces 100 Mbps and half-duplex operation, and disables autonegotiation on the interface.

Forces 100 Mbps and full-duplex operation, and disables autonegotiation on the interface.

Examples The following example specifies advertisement of 10 Mbps operation only, and either full-duplex or half-duplex capability during autonegotiation for the second interface (port 1) on the SPA located in the bottom (1) subslot of the MSC that is installed in slot 2 of the Cisco 7304 router:



Router(config-if)# speed 10

Router(config-if)# duplex auto

With this configuration, the interface advertises the following capabilities during autonegotiation:

• 10 Mbps and half duplex

• 10 Mbps and full duplex

Note Recall that flow control support is always advertised when autonegotiation is enabled.

Related Commands Command duplex

Description

Configures the duplex operation on an interface.

interface fastethernet show controllers fastethernet

Selects a particular Fast Ethernet interface for configuration.

Displays interface information, transmission statistics and errors, and the MAC destination address and VLAN filtering table on a Fast

Ethernet interface on the Cisco 7304 router.

show interfaces fastethernet Displays information about the Fast Ethernet interfaces.

19-156


Release 12.0(33)S, OL-8832-01, Rev. C9


t1 framing

t1 framing

To specify the type of framing used by T1 channels, use the t1 framing command in controller configuration mode.

Cisco 7500 Series Routers with Channelized T3 Interface Processor t1 channel framing { esf | sf }

Channelized T3/E3 Shared Port Adapters t1 channel framing { esf | sf [ hdlc-idle { 0x7e | 0xff }] [ mode { j1 }]} no t1 channel framing { esf | sf [ hdlc-idle { 0x7e | 0xff }] [ mode { j1 }]}

Syntax Description channel esf sf hdlc-idle { 0x7e |

0xff } mode { j1 }

Number indicating the T1 channel.

• On the CT3IP—1 to 28

• On the CT3 SPA—0 to 23

Specifies that Extended Super Frame (ESF) is used as the T1 framing type. This is the default for the CT3IP.

Specifies that Super Frame (SF) is used as the T1 framing type. This is the default for the T3/E3 SPA.

(Optional) Sets the idle pattern for the T1 interface to either 0x7e (the default) or 0xff .

(Optional) Specifies the JT-G704 Japanese frame type.

Defaults esf (for C3TIP) sf (for T3/E3 SPA)



11.3

12.0(14)S

12.2S

12.2(18)SXE

12.0(31)S

Modification


This command was integrated into Cisco IOS Release 12.0(14)S. The hdlc-idle keyword option was added.


This command was integrated into Cisco IOS Release 12.2(18)SXE to support SPAs on the Cisco 7600 series routers. The mode keyword option was added.


Release 12.0(33)S, OL-8832-01, Rev. C9


19-157


t1 framing

Usage Guidelines If you do not specify the t1 framing command, the default ESF is used.

Note T1 channels on the CT3IP are numbered 1 to 28 rather than the more traditional zero-based scheme

(0 to 27) used with other Cisco products. This numbering scheme ensures consistency with telco numbering schemes for T1 channels within channelized T3 equipment.

To return to the default mode, use the no form of this command. This command does not have a no form on the Cisco 7500 series router with the CT3IP.

Examples


The following example shows how to set the framing for the T1 6 and T1 8 on the CT3IP to Super Frame:


Router(config-controller)# t1 6 framing sf

Router(config-controller)# t1 8 framing sf

Command controller show controller

Description


Displays controller configuration.

19-158


Release 12.0(33)S, OL-8832-01, Rev. C9


ttb

ttb


To send a trace trail buffer in E3 g832 framing mode, use the ttb command in interface configuraton mode. To disable the trace, use the no form of this command.

ttb { country | rnode | serial | snode | soperator | x } line no ttb { country | rnode | serial | snode | soperator | x } line country rnode serial line line line snode line soperator line x line

Two-character country code.

Receive node code.

M.1400 Serial

Sending Town/Node ID code.

Sending Operator code.

XO




12.2S

12.2(18)SXE

12.0(31)S

Modification




Usage Guidelines Use the ttb command to attach a header that contains fields to send to a remote device.

Examples The following example starts a TTB message on the first port on slot 5.



Router(config-if)# ttb country us

Router(config-if)# ttb snode 123

Router(config-if)# ttb rnode rn

Router(config-if)# ttb x 9

Router(config-if)# ttb serial 432

Related Commands Command show controller serial

Description

Displays controller statistics.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-159


upgrade fpd auto


To configure the router to automatically upgrade the current FPD images on a SPA when an FPD version incompatibly is detected, enter the upgrade fpd auto global configuration command. To disable automatic FPD image upgrades, use the no form of this command.

upgrade fpd auto no upgrade fpd auto


Defaults This command is enabled by default if your router has any installed SPAs. The router will check the SPA

FPD image during bootup or after an insertion of a SPA into a SIP subslot. If the router detects an incompatibility between an FPD image and a SPA, an automatic FPD upgrade attempt will occur unless the user has disabled automatic FPD upgrades by entering the no upgrade fpd auto command.

By default, the upgrade fpd auto will search the router’s primary Flash file system for the FPD image package file. If you would like the router to search for the FPD image package file in a location other than the router’s primary Flash file system when an FPD incompatibility is detected, enter the upgrade fpd path fpd-pkg-dir-url command to specify the location where the router should search for the FPD image package file. Once the FPD image package file is successfully located, the FPD upgrade process begins automatically.



12.2(20)S2

12.2(18)SXE

12.0(31)S

Modification


This command was integrated into Cisco IOS release 12.2(18)SXE.


Usage Guidelines This command is enabled by default. In most cases, this default configuration should be retained.

By default, the upgrade fpd auto command instructs the router to search its primary Flash file system

(for example, disk0:) for the FPD image package file. If you would like the router to search for the FPD image package file in a different location when an FPD incompatibility is detected, enter the upgrade fpd path command to have the router find the FPD image package file in a different location.

If this command is disabled but an FPD upgrade is required, the upgrade hw-module subslot command can be used to upgrade the SPA FPD image manually after the SPA is disabled because of the existing

FPD incompatibility.

Upgrading the FPD image on a SPA places the SPA offline while the upgrade is taking place. The time required to complete an FPD image upgrade can be lengthy. The show upgrade fpd progress command can be used to gather more information about estimated FPD download times for a particular SPA.

19-160


Release 12.0(33)S, OL-8832-01, Rev. C9



Examples The following example shows the output displayed when a SPA requires an FPD image upgrade and the upgrade fpd auto command is enabled . The incompatible FPD image is automatically upgraded.

% Uncompressing the bundle ... [OK]

*Jan 13 22:38:47:%FPD_MGMT-3-INCOMP_FPD_VER:Incompatible 4FE/2GE FPGA (FPD ID=1) image version detected for SPA-4FE-7304 card in subslot 2/0. Detected version = 4.12, minimal required version = 4.13. Current HW version = 0.32.

*Jan 13 22:38:47:%FPD_MGMT-5-FPD_UPGRADE_ATTEMPT:Attempting to automatically upgrade the

FPD image(s) for SPA-4FE-7304 card in subslot 2/0 ...

*Jan 13 22:38:47:%FPD_MGMT-6-BUNDLE_DOWNLOAD:Downloading FPD image bundle for SPA-4FE-7304 card in subslot 2/0 ...

*Jan 13 22:38:49:%FPD_MGMT-6-FPD_UPGRADE_TIME:Estimated total FPD image upgrade time for

SPA-4FE-7304 card in subslot 2/0 = 00:06:00.

*Jan 13 22:38:49:%FPD_MGMT-6-FPD_UPGRADE_START:4FE/2GE FPGA (FPD ID=1) image upgrade in progress for SPA-4FE-7304 card in subslot 2/0. Updating to version 4.13. PLEASE DO NOT

INTERRUPT DURING THE UPGRADE PROCESS (estimated upgrade completion time = 00:06:00)

...[...............................................................................

(part of the output has been removed for brevity)

..........................................................................................

..........................................................................................

........]

SUCCESS - Completed XSVF execution.

*Jan 13 22:44:33:%FPD_MGMT-6-FPD_UPGRADE_PASSED:4FE/2GE FPGA (FPD ID=1) image upgrade for

SPA-4FE-7304 card in subslot 2/0 has PASSED. Upgrading time = 00:05:44.108

*Jan 13 22:44:33:%FPD_MGMT-6-OVERALL_FPD_UPGRADE:All the attempts to upgrade the required

FPD images have been completed for SPA-4FE-7304 card in subslot 2/0. Number of successful/failure upgrade(s):1/0.

*Jan 13 22:44:33:%FPD_MGMT-5-CARD_POWER_CYCLE:SPA-4FE-7304 card in subslot 2/0 is being power cycled for the FPD image upgrade to take effect.


upgrade fpd path Specifies the location from where the FPD image package should be loaded when an automatic FPD upgrade is initiated by the router.


SIPs on a router.


show upgrade fpd file show upgrade fpd package default show upgrade fpd progress show upgrade fpd table





Release 12.0(33)S, OL-8832-01, Rev. C9


19-161


upgrade fpd path


To configure the router to search for an FPD image package file in a location other than the router’s primary Flash file system during an automatic FPD upgrade, enter the upgrade fpd path global configuration command to specify the new location that should be searched for an FPD image package file when an automatic FPD upgrade occurs. To return to the default setting of the router searching for the FPD image package file in the router’s primary Flash file system when an automatic FPD upgrade is triggered, use the no form of this command.

upgrade fpd path fpd-pkg-dir-url no upgrade fpd path fpd-pkg-dir-url

Syntax Description fpd-pkg-dir-url Specifies the location of the FPD image package file, beginning with the location or type of storage device (examples include disk0, slot0, tftp, or ftp) and followed by the path to the FPD image package file. It is important to note that the name of the FPD image package file should not be specified as part of fpd-pkg-dir-url ; the Cisco IOS will automatically download the correct FPD image package file once directed to the proper location.

It is important to note that the last character of the fpd-pkg-dir-url is always a “/”.

Defaults By default, the router checks its primary Flash file system for an FPD image package file when an incompatibility between an FPD image on the SPA and the running Cisco IOS image is detected. The upgrade fpd path command is used to specify a new location for a router to locate the FPD image package file if you want to store the FPD image package file in a location other than the router’s default

Flash file system for automatic FPD upgrades.



12.2(20)S2

12.2(18)SXE

12.0(31)S

Modification




Usage Guidelines It is important to note that the last character of the fpd-pkg-dir-url is always a “/”. This path points users to the directory that stores the file, but not the file itself. See the Examples section of this command reference for examples of how to properly enter this command.

Examples

When specifying the path to the location of the new FPD image package file, do not include the filename in the path. The Cisco IOS will automatically download the correct FPD image package file once directed to the proper location, even if multiple FPD image package files of different versions are stored in the same location.

19-162


Release 12.0(33)S, OL-8832-01, Rev. C9



Examples

If the upgrade fpd path command is not entered, the router will search the default primary Flash file system for the FPD image.

In the following example, the FPD image package file that is stored on the TFTP server using the path johnstftpserver/fpdfiles will now be scanned for the latest FPD image package file when an automatic

FPD upgrade occurs.

upgrade fpd path tftp://johnstftpserver/fpdfiles/

In the following example, the FPD package file that is stored on the FTP server using the path johnsftpserver/fpdfiles will now be scanned for the latest FPD image package when an automatic FPD upgrade occurs. In this example, john is the username and XXXXXXX is the FTP password.

upgrade fpd path ftp://john:XXXXXXX@johnsftpserver/fpdfiles/


upgrade fpd auto show hw-module slot fpd



SIPs on a router.







Release 12.0(33)S, OL-8832-01, Rev. C9


19-163


upgrade hw-module slot


To manually upgrade the current FPD image package on a SIP, enter the upgrade hw-module slot command in privileged EXEC configuration mode. The command does not have a no form.

upgrade hw-module slot slot file file-url [ force ]

Syntax Description slot file file-url force



Specifies that a file will be downloaded.

Specifies the location of the FPD image package file, beginning with the location or type of storage device (examples include disk0, slot0, tftp, or ftp) and followed by the path to the FPD image package file.

(Optional) Forces the update of all compatible FPD images in the indicated

FPD image package on the SPA that meet the minimal version requirements. Without this option, the manual upgrade will only upgrade incompatible FPD images.

Defaults No default behavior or values, although it is important to note that the router containing the SIP is configured, by default, to upgrade the FPD images when it detects a version incompatibility between a the FPD image on the SIP and the FPD image required to run the SPA with the running Cisco IOS image.

The upgrade hw-module slot command is used to manually upgrade the FPD images; therefore, the upgrade hw-module slot command should only be used when the automatic upgrade default configuration fails to find a compatible FPD image for one of the SPAs or when the automatic upgrade default configuration has been manually disabled. The no upgrade fpd auto command can be entered to disable automatic FPD upgrades.

If no FPD incompatibility is detected, this command will not upgrade SPA FPD images unless the force option is entered.



12.2(18)SXE

Modification


Usage Guidelines This command is used to manually upgrade the FPD images on a SIP. In most cases, the easiest and recommended method of upgrading FPD images is the automatic FPD upgrade, which is enabled by default. The automatic FPD upgrade will detect and automatically upgrade all FPD images when an FPD incompatibility is detected.

A manual FPD upgrade is usually used in the following situations:

19-164


Release 12.0(33)S, OL-8832-01, Rev. C9


Examples


• The target SIP was disabled by the system because of an incompatible FPD image (the system could not find the required FPD image package file).

A recovery upgrade must be performed.

•

• A special bug fix to an FPD image is provided in the FPD image package file.

The FPD image upgrade process places the SIP and all the SPAs in the SIP offline. The time required to complete an FPD image upgrade can be lengthy. The show upgrade progress command can be used to gather more information about estimated FPD download times for a particular SIP.

The following example shows a sample manual FPD upgrade:

Router# upgrade hw-module slot 4 file disk0:c7600-fpd-pkg.122-18.SXE.pkg

% The following FPD(s) will be upgraded for 7600-SIP-200 (H/W ver = 0.550) in slot 4:

================== =========== =========== ============


Device:"ID-Name" Version Version Upgrade Time

================== =========== =========== ============

5-ROMMON 1.1 1.2 00:02:00

================== =========== =========== ============


% Restarting the target card in slot 4 for FPD image upgrade. Please wait ...

Router#

Mar 25 16:39:37:%CWAN_RP-6-CARDRELOAD:Module reloaded on slot 4/0

SLOT 4:00:00:06:%SSA-5-FABRICSYNC_DONE:Fabric sync on Primary channel done.

Mar 25 16:39:40:%MLS_RATE-4-DISABLING:The Layer2 Rate Limiters have been disabled.

Mar 25 16:39:40:%FPD_MGMT-6-UPGRADE_TIME:Estimated total FPD image upgrade time for

7600-SIP-200 card in slot 4 = 00:02:00.

Mar 25 16:39:40:%FPD_MGMT-6-UPGRADE_START:ROMMON (FPD ID=5) image upgrade in progress for

7600-SIP-200 card in slot 4. Updating to version 1.2. PLEASE DO NOT INTERRUPT DURING THE

UPGRADE PROCESS (estimated upgrade completion time = 00:02:00) ...

Mar 25 16:39:39:%DIAG-SP-6-RUN_COMPLETE:Module 4:Running Complete Diagnostics...

Mar 25 16:39:40:%DIAG-SP-6-DIAG_OK:Module 4:Passed Online Diagnostics

SLOT 1:Mar 26 00:39:40:%SSA-5-FABRICSYNC_DONE:Fabric sync on Primary channel done.

Mar 25 16:39:40:%OIR-SP-6-INSCARD:Card inserted in slot 4, interfaces are now online

Mar 25 16:39:46:%FPD_MGMT-6-UPGRADE_PASSED:ROMMON (FPD ID=5) image in the 7600-SIP-200 card in slot 4 has been successfully updated from version 1.1 to version 1.2. Upgrading time = 00:00:06.000

Mar 25 16:39:46:%FPD_MGMT-6-OVERALL_UPGRADE:All the attempts to upgrade the required FPD images have been completed for 7600-SIP-200 card in slot 4. Number of successful/failure upgrade(s):1/0.

Mar 25 16:39:47:%FPD_MGMT-5-CARD_POWER_CYCLE:7600-SIP-200 card in slot 4 is being power cycled for the FPD image upgrade to take effect.

Mar 25 16:39:47:%OIR-6-REMCARD:Card removed from slot 4, interfaces disabled

Mar 25 16:39:47:%C6KPWR-SP-4-DISABLED:power to module in slot 4 set off (Reset)

Mar 25 16:40:38:%CWAN_RP-6-CARDRELOAD:Module reloaded on slot 4/0

SLOT 4:00:00:06:%SSA-5-FABRICSYNC_DONE:Fabric sync on Primary channel done.

Mar 25 16:40:41:%MLS_RATE-4-DISABLING:The Layer2 Rate Limiters have been disabled.

Mar 25 16:40:40:%DIAG-SP-6-RUN_COMPLETE:Module 4:Running Complete Diagnostics...

Mar 25 16:40:41:%DIAG-SP-6-DIAG_OK:Module 4:Passed Online Diagnostics

SLOT 1:Mar 26 00:40:41:%SSA-5-FABRICSYNC_DONE:Fabric sync on Primary channel done.

Mar 25 16:40:41:%OIR-SP-6-INSCARD:Card inserted in slot 4, interfaces are now online

Release 12.0(33)S, OL-8832-01, Rev. C9


19-165



Related Commands Command upgrade fpd auto upgrade fpd path show hw-module slot fpd

Description




SIPs on a router.







upgrade hw-module subslot Manually performs an FPD upgrade for a specific SPA.

19-166


Release 12.0(33)S, OL-8832-01, Rev. C9


upgrade hw-module subslot fpd file


To manually upgrade the current FPD image package on a SPA, use the upgrade hw-module subslot fpd file command in privileged EXEC mode. upgrade hw-module subslot slot / subslot fpd file file-url [ force ]

Syntax Description slot subslot file-url force





Specifies the location of the FPD image package file, beginning with the location or type of storage device (examples include disk0 , slot0 , tftp , or ftp ) and followed by the path to the FPD image package file.

(Optional) Forces the update of all compatible FPD images in the indicated

FPD image package on the SPA that meet the minimal version requirements. Without this option, the manual upgrade will only upgrade incompatible FPD images.

Defaults No default behavior or values, although it is important to note that the router containing the SPA is configured, by default, to upgrade the FPD images when it detects a version incompatibility between a the FPD image on the SPA and the FPD image required to run the SPA with the running Cisco IOS image.

Manual upgrade of FPD images is recommended only when the automatic upgrade default configuration fails to find a compatible FPD image for one of the SPAs, or when the automatic upgrade default configuration has been manually disabled. The no upgrade fpd auto command can be entered to disable automatic FPD upgrades.

If no FPD incompatibility is detected, this command will not upgrade SPA FPD images unless the force option is entered.



12.2(33)SRB

12.0(33)S

Modification

This command was introduced. This command replaces the upgrade hw-module subslot command.

This command was introduced. This command replaces the upgrade hw-module subslot command.

Release 12.0(33)S, OL-8832-01, Rev. C9


19-167



Usage Guidelines This command is used to manually upgrade the FPD images on a SPA. In most cases, the easiest and recommended method of upgrading FPD images is the automatic FPD upgrade, which is enabled by default. The automatic FPD upgrade will detect and automatically upgrade all FPD images when an FPD incompatibility is detected.

A manual FPD upgrade is usually used in the following situations:

• The target SPA was disabled by the system because of an incompatible FPD image (the system could not find the required FPD image package file).

•

•

A recovery upgrade must be performed.

A special bug fix to an FPD image is provided in the FPD image package file.

The FPD image upgrade process places the SPA offline. The time required to complete an FPD image upgrade can be lengthy. The show upgrade progress command can be used to gather more information about estimated FPD download times for a particular SPA.

For more information about FPD upgrades on SPA interface processors (SIPs) and shared port adapters

(SPAs), refer to the Cisco 7600 Series Router SIP, SSC, and SPA Software Configuration Guide or to the

Cisco 12000 Series Router SIP and SPA Software Configuration Guide .

Examples The following example shows a sample manual FPD upgrade:

Router# upgrade hw-module subslot 2/0 fpd file disk0:spa_fpd.122-20.S2.pkg

% Uncompressing the bundle ... [OK]

% The following FPD(s) will be upgraded for card in subslot 2/0 :

================== =========== =========== ============


Device:"ID-Name" Version Version Upgrade Time

================== =========== =========== ============

1-Data & I/O FPGA 4.12 4.13 00:06:00

================== =========== =========== ============


% Restarting the target card (subslot 2/0) for FPD image upgrade. Please wait ...

Router#

*Jan 14 00:37:17:%FPD_MGMT-6-FPD_UPGRADE_TIME:Estimated total FPD image upgrade time for

SPA-4FE-7304 card in subslot 2/0 = 00:06:00.

*Jan 14 00:37:17:%FPD_MGMT-6-FPD_UPGRADE_START:4FE/2GE FPGA (FPD ID=1) image upgrade in progress for SPA-4FE-7304 card in subslot 2/0. Updating to version 4.13. PLEASE DO NOT

INTERRUPT DURING THE UPGRADE PROCESS (estimated upgrade completion time = 00:06:00)

...[..........................(part of the output has been removed for brevity)....

.................................................................................]

SUCCESS - Completed XSVF execution.

*Jan 14 00:42:59:%FPD_MGMT-6-FPD_UPGRADE_PASSED:4FE/2GE FPGA (FPD ID=1) image upgrade for

SPA-4FE-7304 card in subslot 2/0 has PASSED. Upgrading time = 00:05:42.596

*Jan 14 00:42:59:%FPD_MGMT-6-OVERALL_FPD_UPGRADE:All the attempts to upgrade the required

FPD images have been completed for SPA-4FE-7304 card in subslot 2/0. Number of successful/failure upgrade(s):1/0.

*Jan 14 00:42:59:%FPD_MGMT-5-CARD_POWER_CYCLE:SPA-4FE-7304 card in subslot 2/0 is being power cycled for the FPD image upgrade to take effect.

19-168


Release 12.0(33)S, OL-8832-01, Rev. C9



Related Commands Command upgrade fpd auto upgrade fpd path show hw-module slot fpd

Description




SIPs on a router.







Release 12.0(33)S, OL-8832-01, Rev. C9


19-169


19-170


Release 12.0(33)S, OL-8832-01, Rev. C9

G L O S S A R Y

B blank filler plate An empty panel used to fill vacant subslots on a SIP. For proper operation, a SIP should be fully installed with either functional SPAs or blank filler plates.

D double height Describes the dimension of a SPA that occupies two, vertically-aligned SIP subslots.

F

FPD Field-programmable device. General term for any hardware component implemented on router cards that supports separate software upgrades. SIPs and SPAs must have the right FPD version to function properly; an FPD incompatibility will disable all interfaces on the SPA or all SPAs within the SIP.

FPD image package An FPD image package is used to upgrade FPD images. Whenever a Cisco IOS image is released that supports SPAs, a companion SPA FPD image package is also released for that Cisco IOS software release.

O

OIR Online insertion and removal. Feature supported by SIPs and SPAs allowing removal of the cards while the router and the cards are activated, without affecting the operation of other cards or the router.

Although this removal can be done while the SIP or SPA is activated, it is generally recommended that you gracefully deactivate the hardware using the appropriate commands for your platform prior to removal of the hardware.

S

SFP single height

Small form-factor pluggable optical transceiver. A type of fiber optic receptacle device that mounts flush with the front panel to provide network connectivity.

Describes the dimension of a SPA that occupies a single SIP subslot, or half of the SIP.

Release 12.0(33)S, OL-8832-01, Rev. C9


GL-171

Glossary

SIP

SPA subslot

SPA interface processor. A SIP is a platform-specific carrier card that inserts into a router slot like a line card. A SIP can hold one or more SPAs in its subslots, depending on the SIP type. The SPA provides the network interface. The SIP provides the connection between the route processor (RP) and the SPA.

Shared port adapter. A SPA is a modular, platform-independent port adapter that inserts into a subslot of a compatible SIP carrier card to provide network connectivity and increased interface port density.

The SPA provides the interface between the network and the SIP.

Secondary slot on a SIP where a SPA is installed. The primary slot is the chassis slot on the router.

GL-172


Release 12.0(33)S, OL-8832-01, Rev. C9

I N D E X

Symbols

<cr>

1-7

? command

1-7

A administratively down state

5-12

aps protect command

16-1

aps working command

16-1

asynchronous interfaces groups, designating

19-42

automatic SPA FPD image upgrade

(example)

17-13

cannot locate FPD image package (example)

17-12

disabling

17-6 re-enabling 17-6

autonegotiation configuring

5-9 to 5-10

disabling on fiber interfaces

5-9

enabling on fiber interfaces

5-9

cautions, usage in text

1-xxi

Cisco 12000 router slot locations (figure)

5-5

Cisco IOS configuration changes, saving

1-11

Cisco MIB Locator

4-3

clock source command

16-1

command line processing

1-4

command modes, understanding 1-5 to 1-6

commands

context-sensitive help for abbreviating 1-7

default form, using

1-10

no form, using

1-10

command summary

FPD commands (table)

18-1

command syntax conventions

1-xx

displaying (example)

1-7

configurations, saving 1-11

configuration tasks, required for the Fast Ethernet SPA

5-3

configure terminal command

5-2, 5-3

copy command

5-12

crc command

16-1

B

bert pattern command

19-6, 19-8, 19-10, 19-12, 19-14

blank filler panel in a SIP

2-1

blank filler plate 6-8

C carriage return (<cr>)

1-7

D

DLCI (data-link connection identifier) interface statistics, displaying

19-120

multicast mechanism, displaying statistics

about 19-120

document organization

1-xviii

dot1q encapsulation

5-9

configuration (example)

5-16

configuring

5-10


Release 12.0(33)S, OL-8832-01, Rev. C9 IN-1

Index

DSU (data service unit) configuration information, displaying

19-81

duplex command

5-2

E

EEPROM

19-88

electrically erasable programmable read-only memory

<Emphasis>See EEPROM

encapsulation

ARPA 5-9 configuring 5-9

dot1q

5-9

configuration (example) 5-16

configuring 5-10

SAP

5-9

SNAP

5-7, 5-9

encapsulation command

16-1

encapsulation dot1q command

5-10, 7-1

event tracer feature

6-8

F features on 4-port 10/100 Fast Ethernet SPA

4-2

filtering output, show and more commands 1-11

flow control support

5-11

verifying

5-11

FPD image packages cannot locate (example)

17-12

caution 17-4, 17-9

displaying default information

17-11

downloading

17-7, 17-9

modifying the default path

17-9

overview 17-3

version number requirements

17-3

FPD images

IN-2

Cisco 12000 Series Router SIP and SPA Software Configuration Guide (Cisco IOS) displaying minimum and current versions

17-10

manually upgrading 17-6

troubleshooting upgrades

17-14, ?? to 17-16

upgrade failure recovery (example)

17-14 to 17-16

upgrade scenarios

17-3

upgrading in production 17-5, 17-6

verifying successful upgrade 17-16

verifying upgrade progress

17-12

FPDs (field-programmable devices) description

17-1

Frame Relay

DLCI

interface statistics 19-120

multicast mechanism statistics

19-120

LMI general statistics, displaying

19-120

frame type, selecting

19-26

framing

T1

19-158

framing (T1/E1controller) command 19-26

framing (T3 controller) command

19-28

FTP server, downloading FPD images to

17-7, 17-9

G

global configuration mode, summary of 1-6

group and member asynchronous interfaces

19-42

H hardware platforms

See

platforms, supported help command

1-7

hw-module subslot command

5-12

hw-module subslot reload command

19-32

hw-module subslot shutdown command

19-34

hw-module subslot srp command

15-19, 16-1, 19-36

Release 12.0(33)S, OL-8832-01, Rev. C9

Index

I

IEEE 802.1Q encapsulation 5-9

configuration (example)

5-16

configuring

5-10

interface

basic configuration (example) 5-14

enabling

5-2, 5-4

restarting 5-12

shutting down

5-12

verifying configuration

5-12 to 5-13

interface address, specifying

5-4

interface command

19-38

interface configuration mode, summary of 1-6

interface fastethernet command

5-2, 5-3, 7-1

interface pos command

16-1

interfaces unit numbers

19-39

interface sdcc command

16-1

interface srp command

16-1

ip address command

5-2, 5-3, 5-10, 7-1, 16-1

ISL (Inter-Switch Link) encapsulation 5-10

K keepalive command

16-1

keyboard shortcuts

1-4

L

LAPB (Link Access Procedure, Balanced) interface statistics, displaying

19-134

LMI (Local Management Interface) general statistics, displaying

19-120

loopback (E3/T3 interface) command

19-47

loopback driver command

7-1

loopback interfaces 19-41

loopback mac command

7-1

M

MAC address


modifying 5-5 to 5-6

verifying

5-6

mac-address command

7-1

Management Information Base (MIB) downloading

4-3 supported on SPAs 4-3

MIBs

10G SIP

3-6

modes

See

command modes

MPLS labels, and interface MTU size

5-7

mpls mtu command

5-8, 15-4

MTU (maximum transmission unit)


default size

5-7

interface MTU additional overhead

5-7

and MPLS labels

5-7

configuration guidelines

5-7

configuring 5-8

description

5-7

verifying

5-8

IP MTU description

5-7

maximum size

5-7

MPLS MTU description

5-7

tag MTU description

5-7 types 5-7

mtu command

5-2, 5-3, 5-8, 7-1, 16-1

N

negotiation auto command 5-10, 7-1


Release 12.0(33)S, OL-8832-01, Rev. C9 IN-3

Index no negotiation auto command

5-9

no shut command 5-2, 5-4

no shutdown command

7-1, 16-1

notes, usage in text

1-xxi

no upgrade fpd auto command

17-6

NVRAM (nonvolatile random-access memory)

5-12

O

OIR (online insertion and removal) and shutting down or restarting interfaces

5-12

event tracing for SPAs

6-8

for SIPs 2-1

for SPAs

2-2, 6-8

troubleshooting

6-8

P packet flow, on SPA

4-4 to ??

platforms, supported release notes, identify using

1-12

pos ais-shut command 16-1

pos delay triggers line command

16-2

pos delay triggers path command

16-2

pos framing command

16-2

pos scramble-atm command

16-2

pos threshold command

16-2

privileged EXEC mode, summary of

1-6

prompts, system

1-6

Q

question mark (?) command 1-7

R release history

MSCs and SPAs

4-1

release notes

See

platforms, supported

ROM monitor mode, summary of

1-6

running configuration, saving to NVRAM

5-12

S

SAP (Service Access Point) encapsulation

5-9

sdcc command

16-2

serial interfaces

monitoring synchronous 19-135

show aps command

16-2

show controllers fastethernet command

5-11

show controllers pos command

14-14, 16-2, 19-70

show diagbus command

19-87

show diag command

19-87

show diags command

14-13, 14-14

show diags subslot command

16-2

show gsr

3-10

show history command

1-5

show hw-module all fpd command

19-97

show hw-module subslot command 17-10, 18-1

show hw-module subslot fpd command 19-99

show hw-module subslot oir command

19-102

show interfaces

SDLC information, displaying

19-135

show interfaces command

4-4, 14-12, 14-13

show interface sdcc command

19-107

show interfaces fastethernet command

4-5

show interfaces gigabit ethernet command

5-8

show interfaces gigabitethernet command

5-6

show interfaces pos command

16-2, 19-114

show interfaces sdcc command

16-2

show interfaces serial accounting command

19-120

show running-config command

17-7

show upgrade file command 18-1

show upgrade fpd file command 19-145

show upgrade fpd package default command

19-148

show upgrade fpd progress command 19-150


IN-4 Release 12.0(33)S, OL-8832-01, Rev. C9

Index show upgrade fpd table command

19-152

show upgrade package default command 17-11, 18-1

show upgrade progress command

17-12, 18-1

show upgrade table command

18-1

show vlans command

5-10, 7-2

shutdown command

5-12

SIP (SPA interface processor) blank filler panels

2-1

definition

2-1 general characteristics 2-1

subslots

2-1

slot number, on Cisco 7304 router

5-4

SNAP (Subnetwork Access Protocol) encapsulation

5-7,

5-9

SPA (shared port adapter) definition

2-2

FPD image packages overview

17-3

interfaces

2-2

sizes

2-2

SPA architecture description

4-4, ?? to 14-12

SPA Architecture Design

14-9

SPA hardware type, displaying

4-4

SPA operational status (table)

19-103

speed command

5-2, 19-154

subinterfaces, configuring

5-10, 19-38, 19-41, 19-44

subslot numbers, on Cisco 7304 MSC-100

5-4

subslots on a SIP

2-1

T

T3

display interface 19-128

T1 framing

19-158

Tab key, command completion 1-7

TFTP server, downloading FPD images to

17-7, 17-9

U unit numbers

interface 19-39

upgrade fpd auto command

17-6, 17-7, 17-12, 17-13, 18-1,

19-160

upgrade fpd path command

17-7, 17-9, 18-1, 19-162

upgrade hw-module slot command

19-164

upgrade hw-module subslot command

17-6, 18-1, 19-167

user EXEC mode, summary of

1-6

V

VIC (voice interface cards), slot information

19-88

virtual interfaces loopback interface

19-41

tunnel interface

19-42

VLANs (virtual LANs)


configuring on a subinterface

5-10

verifying configuration

5-10

X

X.25

interface statistics, displaying

19-138

Release 12.0(33)S, OL-8832-01, Rev. C9


IN-5

Index

IN-6


Release 12.0(33)S, OL-8832-01, Rev. C9