Cisco WS C4224V 8FXS - 200Mbps Ethernet Switch, Catalyst 4224 Software Configuration Manual

Catalyst 4224 Access Gateway
Switch Software Configuration
Guide

March 2003

Corporate Headquarters

Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: [phone]

800 553-NETS (6387)

Fax: [phone]

Text Part Number: OL-2031-02

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.

CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare,
iQ Net Readiness Scorecard, Networking Academy, and ScriptShare are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and
Learn, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX,
Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco
Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step,
GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet , PIX,
Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, TransPath, and VCO are
registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other trademarks mentioned in this document or Web site 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. (0303R)

Catalyst 4224 Access Gateway Switch Software Configuration Guide

Copyright © 2001-2003 Cisco Systems, Inc. All rights reserved.

Preface xvii

Objectives xvii
Audience xviii
Organization xviii
Related Documentation xix
Conventions xx
Obtaining Documentation xxi

Cisco.com xxi
Documentation CD-ROM xxi

CONTENTS

CHAPTER

Ordering Documentation xxii
Documentation Feedback xxii

Obtaining Technical Assistance xxiii

Cisco.com xxiii
Technical Assistance Center xxiii

Cisco TAC Website xxiv
Cisco TAC Escalation Center xxv

Obtaining Additional Publications and Information xxv

1 Product Overview 1-1

Features 1-2
Solution 1-3
IP Telephony 1-5

Ethernet Switching 1-5
Survivable Remote Site Telephony 1-6

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

iii

Contents

VoIP Gateway 1-6
IP Routing and WAN Features 1-7

Quality of Service 1-9
VPN and Firewall Features 1-9

Application Notes 1-10

Architecture 1-10
DSP Allocation 1-11
InterVLAN Routing 1-14
Quality of Service 1-14
Layer 2 QoS 1-14
Separate Voice and Data VLANs 1-15
Single Voice and Data VLAN with dot1p 1-15
Layer 3 QoS 1-16
WAN QoS Queuing and Scheduling 1-16
Summary of the Layer 3 WAN QoS Features 1-16

Configuration Guidelines 1-18

Default Port Configuration 1-18
Separate VLAN for Voice and Data 1-19
Port Configuration for a Single Subnet 1-19
InterVLAN and WAN Routing Configuration 1-20
Centralized Cisco CallManager and DHCP Server 1-20
Voice Port Configuration 1-21
Interface Range Command Support 1-22
Switched Port Analyzer (SPAN) 1-22

Recommended Configurations 1-22

No VTP or DTP Support 1-23
Creating a VLAN 1-23
Defining a VLAN on a Trunk Port 1-23
Trunking 1-24
Fractional PRI Configuration 1-24

Catalyst 4224 Access Gateway Switch Software Configuration Guide

iv

OL-2031-02

No Ring Back Tone Generated 1-25
MTP Required on Cisco CallManager 1-26
H323-Gateway VOIP Bind SRCADDR Command 1-27
Port Fast Not Enabled on Trunk Ports 1-28
Priority Queuing on Frame Relay 1-28
Maximum Number of VLAN and Multicast Groups 1-29
IP Multicast Support 1-29

Contents

CHAPTER

CHAPTER

2 Configuring for the First Time 2-1

First-Time Configuration 2-1

Booting the Catalyst 4224 2-2
Downloading an Image to Boot Flash Memory 2-2

Connecting a Terminal 2-3

Connecting a Modem 2-3
Configuring the Management Port 2-3
Interface Numbering 2-4

Using the Cisco IOS CLI 2-5

Getting Help 2-6
Command Modes 2-6
Disabling a Command or Feature 2-8
Saving Configuration Changes 2-8

3 Configuring Ethernet Switching 3-1

Configuring the Catalyst 4224 for Cisco IP Telephony 3-1

Default Switch Configuration 3-2
Connecting IP Phones to Your Campus Network 3-2

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

v

Contents

Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained
Workstation

Configuring Separate Voice and Data Subnets 3-4

Configuring a Single Subnet for Voice and Data 3-7

Configuring Ethernet Ports to Support IP Phones with Multiple Ports 3-9

IP Addressing 3-9
Sample Configuration 3-10

Managing the Catalyst 4224 Access Gateway Switch 3-10

Adding Trap Managers 3-11

3-3

Voice Traffic and VVID 3-5

Sample Configuration 1 3-6

Sample Configuration 2 3-6

Sample Configuration 3-9

Configuring IP Information 3-11

Assigning IP Information to the Switch—Overview 3-11

Assigning IP Information to the Switch—Procedure 3-12

Removing an IP Address 3-13

Specifying a Domain Name and Configuring the DNS 3-13
Configuring Voice Ports 3-14

Configuring a Port to Connect to a Cisco 7960 IP Phone 3-15

Disabling Inline Power on a Catalyst 4224 3-15
Enabling and Disabling Switch Port Analyzer 3-16

Enabling the Switch Port Analyzer 3-17

Disabling Switch Port Analyzer 3-17
Managing the ARP Table 3-17
Managing the MAC Address Tables 3-18

MAC Addresses and VLANs 3-19

Changing the Address Aging Time 3-19

Catalyst 4224 Access Gateway Switch Software Configuration Guide

vi

Adding Secure Addresses 3-20

Adding and Removing Static Addresses 3-22

OL-2031-02

Contents

CHAPTER

CHAPTER

4 Configuring the Data Interfaces 4-1

Configuring the Host Name and Password 4-2
Configuring the Fast Ethernet Interface 4-4
Configuring Asynchronous/Synchronous Serial Interfaces 4-6
Configuring ISDN BRI Interfaces 4-9
Configuring T1 and E1 Interfaces 4-12

Configuring T1 Interfaces 4-12
Configuring E1 Interfaces 4-16

Checking the Interface Configuration 4-18
Saving Configuration Changes 4-19

5 Configuring the Voice Interfaces 5-1

Configuring Voice Interfaces 5-1
MGCP Configuration 5-3

Enabling MGCP 5-4

Enabling Switchover and Switchback 5-5
Configuring FXS and FXO Analog Ports 5-8
Configuring T1-CAS E&M Emulation 5-8
Configuring T1/E1 (ISDN-PRI) Ports 5-10

Configuring T1 Interfaces 5-10

Configuring E1 Interfaces 5-13
Where to Go Next 5-16

H.323 Gateway Configuration 5-16
Configuring T1-CAS Analog Emulation (H.323) 5-19

Managing Input Gain for Cisco IP Voice Applications 5-21
FXS Emulation Example 5-21
FXO Emulation Example 5-23
E&M Emulation Example 5-23

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

vii

Contents

ISDN BRI Configuration (H.323) 5-24

Configuring ISDN BRI Lines 5-26

ISDN BRI Provisioning by Switch Type 5-26

Defining ISDN Service Profile Identifiers 5-29
BRI Direct-Inward Dialing Configuration 5-29

Gateway 1 Configuration 5-30

Gateway 2 Configuration 5-31

T1/E1 Configuration (H.323) 5-31

Configuring T1 Interfaces 5-31
T1/PRI Configuration Example 5-33
Configuring E1 Interfaces 5-33
E1/PRI Configuration Example 5-34

CHAPTER

E&M Trunk Line Configuration (H.323) 5-35

Scenario 5-35

Handling Incoming Caller ID Digits on an E&M Port 5-36

Gateway San Jose Configuration 5-37

Gateway Salt Lake City Configuration 5-37

6 Configuring VoIP 6-1

Prerequisite Tasks 6-2
Configuration Tasks 6-3
Configure IP Networks for Real-Time Voice Traffic 6-3

Configure RSVP for Voice 6-5

Enable RSVP 6-5

RSVP Configuration Example 6-6
Configure Multilink Point-to-Point Protocol with Interleaving 6-7

Multilink PPP Configuration Example 6-9

Catalyst 4224 Access Gateway Switch Software Configuration Guide

viii

OL-2031-02

Configure Real-Time Transport Protocol Header Compression 6-9

Enable RTP Header Compression on a Serial Interface 6-11

Change the Number of Header Compression Connections 6-11

RTP Header Compression Configuration Example 6-11
Configure Custom Queuing 6-11
Configure Weighted Fair Queuing 6-12

Configure Number Expansion 6-12

Create a Number Expansion Table 6-13
Configure Number Expansion 6-15

Configure Dial Peers 6-15

Inbound Versus Outbound Dial Peers 6-17
Create a Dial-Peer Configuration Table 6-19

Contents

Configure POTS Dial Peers 6-20

Outbound Dialing on POTS Dial Peers 6-20
Configure VoIP Dial Peers 6-21

Verifying Your Configuration 6-21

Troubleshooting Tips 6-22

Configure Voice Ports 6-22

Configure FXS or FXO Voice Ports 6-23

Verifying Your Configuration 6-24

Troubleshooting Tips 6-25
Fine-Tune FXS and FXO Voice Ports 6-25
Configure E&M Voice Ports 6-27

Verifying Your Configuration 6-29

Troubleshooting Tips 6-30
Fine-Tune E&M Voice Ports 6-30

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

ix

Contents

Additional VoIP Dial-Peer Configurations 6-33

Configure IP Precedence for Dial Peers 6-33
Configure RSVP for Dial Peers 6-34
Configure codec and VAD for Dial Peers 6-35

Configure codec for a VoIP Dial Peer 6-35

Configure VAD for a VoIP Dial Peer 6-36

Configure Frame Relay for VoIP 6-37

Frame Relay for VoIP Configuration Example 6-38

CHAPTER

CHAPTER

7 Configuring the Eight-Port FXS RJ-21 Module 7-1

Eight-Port RJ-21 FXS Module User Interface Conventions 7-2
Configuring FXS Voice Ports 7-2

Changing Default Configurations 7-2
Validating the Configuration 7-4
Troubleshooting the Configuration 7-5

Fine-Tuning FXS Voice Ports 7-6
Activating the Voice Port 7-8
Sample Configuration 7-8

Cisco 2600 Sample Configuration 7-10
FXS Module Sample Configuration 7-10
Displaying Cisco 2600 Configuration Values 7-11
Displaying FXS Module Configuration Values 7-12

8 Configuring Survivable Remote Site Telephony 8-1

Overview of Survivable Remote Site Telephony 8-2

Restrictions 8-2
Prerequisites 8-3
Supported Features 8-3
Fallback Behavior 8-4

Catalyst 4224 Access Gateway Switch Software Configuration Guide

x

OL-2031-02

Configuring Survivable Remote Site Telephony 8-7
Verifying Survivable Remote Site Telephony 8-9
Troubleshooting Survivable Remote Site Telephony 8-10
Monitoring and Maintaining Survivable Remote Site Telephony 8-11
SRST Configuration Example 8-12

Contents

CHAPTER

CHAPTER

9 Implementing Fax over IP on Cisco Voice Gateways 9-1

Overview 9-2

Fax Pass-Through 9-2
Cisco Fax Relay 9-3

Supported Platforms and Features 9-4

10 Traffic Shaping 10-1

About Traffic Shaping 10-2

Why Use Traffic Shaping? 10-2
Traffic Shaping and Rate of Transfer 10-3
Discard Eligible Bit 10-4
Differences Between Shaping Mechanisms 10-4
Traffic Shaping and Queueing 10-6

Generic Traffic Shaping 10-6

How It Works 10-6
Configuration and Commands 10-7

Class-Based Traffic Shaping 10-8

How It Works 10-8
Configuration and Commands 10-8
Restrictions 10-9

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xi

Contents

Frame Relay Traffic Shaping 10-9

How It Works 10-10
Derived Rates 10-10
Configuration and Commands 10-11
Restrictions 10-12

Distributed Traffic Shaping 10-12

Prerequisites 10-12
How It Works 10-12
Configuration 10-13
Restrictions 10-14

Low-Latency Queueing 10-14

CHAPTER

11 Configuring Encryption Services 11-1

Configuring the Encryption Service Adapter 11-2

Step 1: Configure the T1 Channel Group 11-2
Step 2: Configure the Internet Key Exchange Security Protocol 11-3
Step 3: Configure IPSec Network Security 11-5
Step 4: Configure Encryption on the T1 Channel Group Serial Interface 11-8

Verifying the Configuration 11-9
Sample Configurations 11-9

Encrypting Traffic Between Two Networks 11-10

Configuration File for the Public Gateway 11-10

Configuration File for the Private Gateway 11-11
Exchanging Encrypted Data Through an IPSec Tunnel 11-14

Configuration File for Peer 1 11-14

Configuration File for Peer 2 11-16

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xii

OL-2031-02

Contents

CHAPTER

12 Configuring Other Routing Protocols 12-1

Novell IPX 12-1

The Cisco Implementation of Novell IPX 12-1

IPX MIB Support 12-2

IPX Enhanced IGRP Support 12-2

LAN Support 12-3

VLAN Support 12-3

Multilayer Switching Support 12-3
IPX Configuration 12-3

IBM SNA 12-4

The Cisco Four-Phase Model for SNA-to-IP Integration 12-4

Phase One: SNA Centric 12-6

Phase Two: IP Transport 12-7

Phase Three: IP Client 12-8

Phase Four: IP Centric 12-9

APPENDIX

Summary of Four-Phase Model 12-9
Scenarios for SNA-to-IP Integration 12-10

Line Consolidation 12-10

FEP Replacement 12-10

Desktop Consolidation 12-11
SNA Configuration 12-12

A Command Reference for Voice VLAN A-1

interface range A-1

Syntax A-1
Syntax Description A-2
Defaults A-2
Command Modes A-2
Usage Guidelines A-2
Example A-2

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xiii

Contents

interface vlan A-3

Syntax A-3
Syntax Description A-3
Defaults A-3
Command Modes A-3
Usage Guidelines A-3
Example A-4

monitor session A-4

Syntax A-4
Syntax Description A-4
Defaults A-4
Command Modes A-5
Usage Guidelines A-5
Examples A-5

spanning-tree A-6

Syntax A-6
Syntax Description A-6
Defaults A-6
Command Modes A-6
Usage Guidelines A-6
Example A-7

spanning-tree portfast A-7

Syntax A-7
Syntax Description A-7
Defaults A-8
Command Modes A-8
Usage Guidelines A-8
Example A-8

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xiv

OL-2031-02

switchport access A-8

Syntax A-9
Syntax Description A-9
Defaults A-9
Command Modes A-9
Usage Guidelines A-9
Example A-9

switchport voice vlan A-10

Syntax A-10
Syntax Description A-10
Defaults A-11
Command Modes A-11
Usage Guidelines A-11

Contents

APPENDIX

Example A-11

B Synopsis of Basic VoIP Concepts B-1

VoIP Overview B-1
A Voice Primer B-2

How VoIP Processes a Typical Telephone Call B-2
Numbering Scheme B-3
Analog Versus Digital B-3
codecs B-4

Mean Opinion Score B-4
Delay B-5

Jitter B-6

End-to-End Delay B-7
Echo B-7
Signaling B-7

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xv

Contents

APPENDIX

C VoIP Configuration Examples C-1

FXS-to-FXS Connection Using RSVP C-1

Configuration for Catalyst 4224 RLB-1 C-3

Configuration for Catalyst 4224 RLB-w C-4

Configuration for Catalyst 4224 RLB-e C-5

Configuration for Catalyst 4224 RLB-2 C-6
Linking PBX Users with E&M Trunk Lines C-7

Router San Jose Configuration C-8

Router Salt Lake City Configuration C-9
FXO Gateway to PSTN C-10

Router San Jose Configuration C-11

Router Salt Lake City Configuration C-11
FXO Gateway to PSTN (PLAR Mode) C-12

Router San Jose Configuration C-13

Router Salt Lake City Configuration C-13

I

NDEX

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xvi

OL-2031-02

Preface

This preface contains these sections:

• Objectives, page xvii

• Audience, page xviii

• Organization, page xviii

Objectives

• Related Documentation, page xix

• Conventions, page xx

• Obtaining Documentation, page xxi

• Obtaining Technical Assistance, page xxiii

This guide explains how to configure basic commands and scenarios for Ethernet
switching, IP WAN routing, Voice over IP (VoIP), and IP telephony on the
Catalyst 4224 Access Gateway Switch. To use this document effectively, you
need to be an experienced data networking professional with a background in
telecommunications.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xvii

Audience

Audience

This guide is intended for network administrators, engineers, and managers who
need to understand the Catalyst 4224 system or configure the software. It is also
intended for Cisco customer service representatives and system engineers.

Organization

This guide contains the following chapters:

Chapter 1 Product Overview Provides an overview of the

Preface

Title Description

Catalyst 4224 Access Gateway
Switch software features.

Chapter 2 Configuring for the First

Time

Chapter 3 Configuring Ethernet

Switching

Chapter 4 Configuring the Data

Interfaces

Chapter 5 Configuring the Voice

Interfaces

Chapter 6 Configuring VoIP Provides comprehensive

Chapter 7 Configuring the

Eight-Port FXS RJ-21
Module

Chapter 8 Configuring Survivable

Remote Site Telephony

Chapter 9 Implementing Fax over

IP on Cisco Voice
Gateways

Describes the initial steps of
configuring the Catalyst 4224.

Describes how to configure the
Ethernet ports and voice VLANs.

Describes how to configure the data
interfaces for IP WAN routing.

Describes how to configure key
voice interfaces.

information on Cisco VoIP
configuration.

Describes how to configure the
8-Port FXS Module.

Describes how to configure
survivable remote site telephony.

Provides an overview and
configuration information for fax
over IP technologies supported on
Cisco voice gateways.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xviii

OL-2031-02

Preface

Related Documentation

Title Description

Chapter 10 Traffic Shaping Describes different types of traffic

shaping and provides pointers to
configuration and command
information.

Chapter 11 Configuring Encryption

Services

Chapter 12 Configuring Other

Routing Protocols

Appendix A Command Reference for

Voice VLAN

Appendix B Synopsis of Basic VoIP

Concepts

Appendix C VoIP Configuration

Examples

Related Documentation

The following publications are available for the Catalyst 4224 Access Gateway
Switch:

Describes how to configure
encryption services.

Describes how to configure the
Novell Internetwork Packet
Exchange (IPX) and IBM Systems
Network Architecture (SNA)
routing protocols.

Describes the key voice VLAN
commands used on Catalyst 4224.

Describes some basic VoIP
concepts.

Provides examples of VoIP
configurations.

• Catalyst 4224 Access Gateway Switch Hardware Installation Guide

• Cisco IOS configuration guides and command references—Use these

publications to help you configure the Cisco IOS software.

• For information about MIBs, refer to the following URL:

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xix

Conventions

Conventions

This guide uses the following conventions:

Convention Description

boldface font Commands and keywords are in boldface.

italic font Arguments for which you supply values are in italics.
[ ] Elements in square brackets are optional.
{ x | y | z } Alternative keywords are grouped in braces and

[ x | y | z ] Optional alternative keywords are grouped in brackets

Preface

separated by vertical bars.

and separated by vertical bars.

string A nonquoted set of characters. Do not use quotation

marks around the string or the string will include the
quotation marks.

screen font Terminal sessions and information the system displays

boldface screen

are in
Information you must enter is in boldface screen font.

screen font.

font

italic screen font Arguments for which you supply values are in italic

screen font.

This pointer highlights an important line of text
in an example.

^ The symbol ^ represents the key labeled Control—for

example, the key combination ^D in a screen display
means hold down the Control key while you press the
Dkey.

< > Nonprinting characters, such as passwords are in angle

brackets.

Note Means reader take note. Notes contain helpful suggestions or references to

material not covered in the publication.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xx

OL-2031-02

Preface

Caution Means reader be careful. In this situation, you might do something that could

result in equipment damage or loss of data.

Obtaining Documentation

Cisco provides several ways to obtain documentation, technical assistance, and
other technical resources. These sections explain how to obtain technical
information from Cisco Systems.

Cisco.com

Obtaining Documentation

You can access the most current Cisco documentation on the World Wide Web at
this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

International Cisco websites can be accessed from this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco
Documentation CD-ROM package, which may have shipped with your product.
The Documentation CD-ROM is updated monthly and may be more current than
printed documentation. The CD-ROM package is available as a single unit or
through an annual subscription.

Registered Cisco.com users can order the Documentation CD-ROM (product
number DOC-CONDOCCD=) through the online Subscription Store:

http://www.cisco.com/go/subscription

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xxi

Obtaining Documentation

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

• Registered Cisco.com users (Cisco direct customers) can order Cisco product

documentation from the Networking Products MarketPlace:

http://www.cisco.com/en/US/partner/ordering/index.shtml

• Registered Cisco.com users can order the Documentation CD-ROM

(Customer Order Number DOC-CONDOCCD=) through the online
Subscription Store:

http://www.cisco.com/go/subscription

• Nonregistered Cisco.com users can order documentation through a local

account representative by calling Cisco Systems Corporate Headquarters
(California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by
calling 800 553-NETS (6387).

Preface

Documentation Feedback

You can submit comments electronically on Cisco.com. On the Cisco
Documentation home page, click Feedback at the top of the page.

You can e-mail your comments to [e-mail].
You can submit your comments by mail by using the response card behind the

front cover of your document or by writing to the following address:
Cisco Systems

Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xxii

OL-2031-02

Preface

Obtaining Technical Assistance

Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center
(TAC) Website, as a starting point for all technical assistance. Customers and
partners can obtain online documentation, troubleshooting tips, and sample
configurations from the Cisco TAC website. Cisco.com registered users have
complete access to the technical support resources on the Cisco TAC website,
including TAC tools and utilities.

Cisco.com

Cisco.com offers a suite of interactive, networked services that let you access
Cisco information, networking solutions, services, programs, and resources at any
time, from anywhere in the world.

Obtaining Technical Assistance

Cisco.com provides a broad range of features and services to help you with these
tasks:

• Streamline business processes and improve productivity

• Resolve technical issues with online support

• Download and test software packages

• Order Cisco learning materials and merchandise

• Register for online skill assessment, training, and certification programs

To obtain customized information and service, you can self-register on Cisco.com
at this URL:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with
a Cisco product, technology, or solution. Two levels of support are available: the
Cisco TAC website and the Cisco TAC Escalation Center. The avenue of support
that you choose depends on the priority of the problem and the conditions stated
in service contracts, when applicable.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xxiii

Obtaining Technical Assistance

We categorize Cisco TAC inquiries according to urgency:

Cisco TAC Website

Preface

• Priority level 4 (P4)—You need information or assistance concerning Cisco

product capabilities, product installation, or basic product configuration.

• Priority level 3 (P3)—Your network performance is degraded. Network

functionality is noticeably impaired, but most business operations continue.

• Priority level 2 (P2)—Your production network is severely degraded,

affecting significant aspects of business operations. No workaround is
available.

• Priority level 1 (P1)—Your production network is down, and a critical impact

to business operations will occur if service is not restored quickly. No
workaround is available.

You can use the Cisco TAC website to resolve P3 and P4 issues yourself, saving
both cost and time. The site provides around-the-clock access to online tools,
knowledge bases, and software. To access the Cisco TAC website, go to this
URL:

http://www.cisco.com/tac

All customers, partners, and resellers who have a valid Cisco service contract
have complete access to the technical support resources on the Cisco TAC
website. Some services on the Cisco TAC website require a Cisco.com login ID
and password. If you have a valid service contract but do not have a login ID or
password, go to this URL to register:

http://tools.cisco.com/RPF/register/register.do

If you are a Cisco.com registered user, and you cannot resolve your technical
issues by using the Cisco TAC website, you can open a case online at this URL:

http://www.cisco.com/en/US/support/index.html

If you have Internet access, we recommend that you open P3 and P4 cases through
the Cisco TAC website so that you can describe the situation in your own words
and attach any necessary files.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xxiv

OL-2031-02

Preface

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses priority level 1 or priority level 2
issues. These classifications are assigned when severe network degradation
significantly impacts business operations. When you contact the TAC Escalation
Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a
case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country,
go to this URL:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

Before calling, please check with your network operations center to determine the
level of Cisco support services to which your company is entitled: for example,
SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When
you call the center, please have available your service agreement number and your
product serial number.

Obtaining Additional Publications and Information

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is
available from various online and printed sources.

• The Cisco Product Catalog describes the networking products offered by

Cisco Systems as well as ordering and customer support services. Access the
Cisco Product Catalog at this URL:

http://www.cisco.com/en/US/products/products_catalog_links_launch.html

• Cisco Press publishes a wide range of networking publications. Cisco

suggests these titles for new and experienced users: Internetworking Terms
and Acronyms Dictionary, Internetworking Technology Handbook,
Internetworking Troubleshooting Guide, and the Internetworking Design
Guide. For current Cisco Press titles and other information, go to Cisco Press

online at this URL:

http://www.ciscopress.com

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xxv

Obtaining Additional Publications and Information

• Packet magazine is the Cisco monthly periodical that provides industry

professionals with the latest information about the field of networking. You
can access Packet magazine at this URL:

http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_maga
zine.html

• iQ Magazine is the Cisco monthly periodical that provides business leaders

and decision makers with the latest information about the networking
industry. You can access iQ Magazine at this URL:

http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=tru
e&kbns=1.html

• Internet Protocol Journal is a quarterly journal published by Cisco Systems

for engineering professionals involved in the design, development, and
operation of public and private internets and intranets. You can access the
Internet Protocol Journal at this URL:

Preface

http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_
protocol_journal.html

• Training—Cisco offers world-class networking training, with current

offerings in network training listed at this URL:

http://www.cisco.com/en/US/learning/le31/learning_recommended_training
_list.html

Catalyst 4224 Access Gateway Switch Software Configuration Guide

xxvi

OL-2031-02

CHAPTER

1

Product Overview

The Cisco Catalyst 4224 Access Gateway Switch (Catalyst 4224) is an integrated
switch/router that provides Voice-over-IP (VoIP) gateway and IP telephony
services to a small branch office. This section provides an overview of the
Catalyst 4224.

This section contains the following topics:

• Features, page 1-2

• Solution, page 1-3

• IP Telephony, page 1-5

OL-2031-02

• VoIP Gateway, page 1-6

• IP Routing and WAN Features, page 1-7

• Application Notes, page 1-10

• Configuration Guidelines, page 1-18

• Recommended Configurations, page 1-22

For a synopsis of basic VoIP concepts, see the following section in this manual:

Appendix B, “Synopsis of Basic VoIP Concepts”

For Voice-over-IP (VoIP) configuration examples, see the following section in
this manual:

Appendix C, “VoIP Configuration Examples”

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-1

Features

Features

Chapter 1 Product Overview

The Catalyst 4224 supports the following features:

• 24 10/100 Ethernet ports with inline power and quality of service (QoS) that

connect IP telephony phones and PCs

• An integrated eight-port Foreign Exchange Station (FXS) module that

connects analog phones, fax machines, modems, key telephone systems
(KTS) or voicemail systems for VoIP

• Three modular slots that support up to six ports on a wide variety of cards and

can provide connectivity to the public switched telephone network (PSTN) or
wide-area network (WAN)

–

Multiflex Voice/WAN Interface Card (VWIC)

–

Voice interface card (VIC)

–

WAN interface card (WIC)

• Onboard hardware-based encryption accelerator

Note These cards can be shared with the Cisco 1600 series,

Cisco 1700 series, Cisco 2600 series, and Cisco 3600 series
platforms.

The Catalyst 4224 supports Cisco IOS software feature sets from the
Cisco IOS Release 12.1.4T. The following Cisco IOS images are available:

• IP Plus (standard)

• IP Plus with Firewall

• IP Plus with IPsec 56

• IP Plus with 3DES

• IP Plus with Firewall and IPsec 56

• IP Plus with Firewall and 3DES

• Optional feature license required to use SRST

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-2

OL-2031-02

Chapter 1 Product Overview

Solution

Solution

The Catalyst 4224 can be deployed as part of a centralized call processing
network with a Cisco CallManager and Survivable Remote Site Telephony
(SRST) software that provides Ethernet switching, IP routing, VoIP gateway, and
IP telephony services for a small branch office.

Centralized call processing allows network administrators to deploy and manage
IP telephony applications at the corporate headquarters or the corporate data
center. Deploying and managing key systems or PBXs in branch offices is no
longer necessary. Centralized call processing provides remote branch office users
with access to IP telephony applications at centralized locations over the IP WAN.

Centralized call processing has the following benefits:

• Centralized configuration and management

• Remote access at to all Cisco CallManager features

• IT staff not required at each remote site

• Ability to rapidly deploy applications for remote users

• Easy upgrades and maintenance

• Lower total cost of ownership (TCO)

Figure 1-1 shows the Catalyst 4224 at a remote site with a centrally deployed

Cisco CallManager at corporate headquarters.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-3

Solution

Figure 1-1 Centralized Call Processing Solution

Catalyst 4224

Chapter 1 Product Overview

IP

A

C

B

V

VIC/WIC ISDN BU MFT-T1

Single T-1 access to

each branch office

IP WAN

PSTN

IP

IP

IP

12 Channels voice/
12 Channels data

55335

In the diagram, a Cisco CallManager cluster at a central site uses Simple Client
Control Protocol (SCCP) to control IP phones at two branch offices. In the branch
VoIP network, a Catalyst 4224 acts as an H.323 gateway, interconnecting the
analog devices, the PSTN, and IP WAN. This system uses ISDN Basic Rate
Interface (BRI) as a lifeline to the PSTN.

If the WAN link (or the Cisco CallManager cluster) becomes unavailable,
Survivable Remote Site Telephony (SRST) allows the Catalyst 4224 to keep the
IP phones on the branch networks running. Under these circumstances, the
Catalyst 4224 functions as an H.323 gateway, thereby ensuring uninterrupted
connectivity to the PSTN.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-4

OL-2031-02

Chapter 1 Product Overview

IP Telephony

The term IP telephony identifies a networking solution that integrates a switched
LAN, the Cisco CallManager, and IP phones.

The Catalyst 4224 is designed to work as part of a centralized Cisco CallManager
network that supports up to 24 remote users. As part of an IP telephony solution,
the Catalyst 4224 provides:

• 24 ports of switched 10/100 Ethernet connectivity to PCs and servers on a

• Line-powered Ethernet for Cisco IP phones

• Limited backup capability when Cisco CallManager is unavailable

Note The Catalyst 4224 has digital signal processors (DSPs) installed on the

motherboard but does not support a DSP farm. Transcoding and conferencing
services are supplied to the branch office by a central Cisco CallManager.

IP Telephony

LAN

Ethernet Switching

Using the auxiliary VLAN feature, you can segment phones into separate logical
networks even though the data and voice infrastructure are physically the same.
The auxiliary VLAN feature places the phones into their own VLANs without the
need for end-user intervention. You can plug the phone into the switch, and the
switch provides the phone with the necessary VLAN information.

Key Ethernet switch features include:

• Hardware-based Layer 2 switching

• Software-based Layer 3 switching

• Twenty-four 10BASE-T/100BASE-TX auto-sensing ports, each delivering

up to 200 Mbps of bandwidth or 100 Mbps of full-duplex bandwidth

• Forwarding and filtering at full wire speed on each port

• Port security that restricts a port to a user-defined group of stations

• Support for up to 8000 unicast and more than 242 multicast addresses

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-5

VoIP Gateway

• Protocol Independent Multicast (PIM) and Internet Group Management

Protocol (IGMP) snooping

• Per-port broadcast, multicast, and unicast storm control that prevents faulty

end stations from degrading overall system performance

• Inline 48-volt DC power

• MAC-based port-level security to prevent unauthorized stations from

accessing the switch

Survivable Remote Site Telephony

As enterprises extend IP telephony from central sites to remote offices, it is
important to provide backup redundancy at the remote branch office. The
Survivable Remote Site Telephony (SRST) software feature on the Catalyst 4224
automatically detects a failure in the network and uses Cisco Simple Network
Automated Provisioning (SNAP) to provide call-processing backup for the IP
phones in the remote office.

Chapter 1 Product Overview

The Catalyst 4224 provides call processing for the duration of the failure and
ensures that the phones remain operational. Upon restoration of the WAN and
connectivity to the network, the system automatically shifts call-processing
functions to the primary Cisco CallManager cluster. Configuration for this
capability is done only once in the Cisco CallManager at the central site.

VoIP Gateway

Voice Over IP (VoIP) receives voice traffic at one location, converts it to TCP/IP
packets for the benefits of toll-bypass, and transports the packets across the WAN
to their destination.

To facilitate the migration to VoIP, the Catalyst 4224 includes an integrated
high-density eight-port FXS module. These FXS ports can connect analog
phones, modems, and fax machines to the Catalyst 4224.

The Catalyst 4224 supports a wide range of voice interface cards with the most
popular signaling protocols. Supported protocols and interface types include
T1-PRI, E1-PRI, T1-CAS, E1-CAS R2, ISDN BRI, and FXO.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-6

OL-2031-02

Chapter 1 Product Overview

Table 1-1 describes the voice interface cards supported by the Catalyst 4224.

Table 1-1 Voice Interface Cards

Module Description

VIC-2FXS Two-port FXS voice/fax interface card
VIC-2FXO Two-port FXO voice/fax interface card (North

VIC-2FXO-EU Two-port FXO voice/fax interface card (European

VIC-2BRI-S/T-TE Two-port BRI S/T terminal equipment voice/fax

VWIC-1MFT-T1 One-port T1/Fractional T1 Multiflex Trunk with

IP Routing and WAN Features

American version)

version)

interface card (also supports data)

CSU/DSU

VWIC-2MFT-T1 Dual-port T1/Fractional T1 Multiflex Trunk with

CSU/DSU
VWIC-1MFT-E1 One-port E1/Fractional E1 Multiflex Trunk with DSU
VWIC-2MFT-E1 Dual-port E1/Fractional E1 Multiflex Trunk with DSU

Additional VoIP gateway benefits include:

• Private branch exchange (PBX) and PSTN connectivity

• H.323v2 VoIP gateway functions

• Onboard DSPs allocated to voice interfaces

• Fax pass-through and Fax relay

• Modem pass-through

IP Routing and WAN Features

The Catalyst 4224 supports the following WAN features:

• Multilink Point-to-Point Protocol (MLPPP)

• Frame relay

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-7

IP Routing and WAN Features

• Asynchronous start-stop on ASCII

• Synchronous PPP

The Catalyst 4224 supports the following IP routing features:

• A high-performance MPC8260 processor running at 200 MHz provides the

• Packet-processing capabilities of 35,000 pps at 64-byte Layer 3

• Onboard hardware encryption provides up to 10 times the performance of

• Modular WIC interfaces that can be shared with the Cisco 1600 series,

Table 1-2 describes the data interface cards supported by the Catalyst 4224.

Chapter 1 Product Overview

processing power required for delivering voice, streaming video, and data to
the branch office

software-only encryption by offloading the processing from the routing CPU

Cisco 1700 series, Cisco 2600 series, and Cisco 3600 series platforms

Table 1-2 Data Interface Cards

Module Description

VWIC-1MFT-T1 One-port T1/Fractional T1Multiflex Trunk with

CSU/DSU
VWIC-2MFT-T1 Dual-port T1/Fractional T1 Multiflex Trunk with

CSU/DSU
VWIC-1MFT-E1 One-port E1/Fractional E1 Multiflex Trunk with DSU
VWIC-2MFT-E1 Dual-port E1/Fractional E1 Multiflex Trunk with DSU
WIC-1DSU-T1 T1/Fractional T1 CSU/DSU
WIC-1DSU-56K4 One-port four-wire 56/64 Kbps CSU/DSU
WIC-1T One-port high-speed serial
WIC-2T Dual-port high-speed serial
WIC-2A/S Dual-port async/sync serial

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-8

OL-2031-02

Chapter 1 Product Overview

Quality of Service

The Catalyst 4224 provides the performance and intelligent services of Cisco IOS
software for branch office applications. The Catalyst 4224 can identify user
applications—such as voice or multicast video—and classify traffic with the
appropriate priority levels. Quality of service (QoS) policies are enforced using
Layer 2 and 3 information such as 802.1p and IP precedence. The Catalyst 4224
queues use weighted random early detection (WRED), weighted round-robin
(WRR), and type-of-service/class-of-service (ToS/CoS) mapping to ensure that
QoS is maintained as packets traverse the network.

To ease the deployment of QoS, the Catalyst 4224 supports Cisco QoS Policy
Manager (QPM). QPM is a complete policy management tool that enables
provisioning of end-to-end differentiated services across network infrastructures
with converged voice, video, and data applications. The combination of QPM and
CiscoWorks Service Management Solution enables network administrators to
adjust service levels in accordance with defined QoS policies. The end result is
network-wide intelligent and consistent QoS that enables performance protection
for voice applications while reducing costs for growing networks.

IP Routing and WAN Features

VPN and Firewall Features

The Catalyst 4224 provides the same security to voice and video networks that is
available for data networks. The Catalyst 4224 supports the optional Cisco IOS
Software Firewall Feature Set, IP Security (IPsec) with data encryption standard
(DES), and Triple DES (3DES). Hardware encryption using the onboard
encryption accelerator provides higher performance than software-based
encryption, and frees processor capacity for other services.

The Catalyst 4224 supports the following encryption features:

• 56-bit DES encryption using Cipher Block Chaining (CBC) mode

• 168-bit 3DES encryption using CBC mode

• MD5 and SHA-1 hashing, including support for the HMAC transform with

IPsec AH and ESP

• Support for Dif-fie-Hellman key exchange

• RSA and DSA public key signature and verification (when implemented by

IOS IPsec Crypto Engine)

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-9

Application Notes

Note DES and 3DES software is controlled by U.S. export regulations on encryption

products. For additional details visit the following URL:

http://www.cisco.com/wwl/export/crypto/

Application Notes

This section contains the following topics:

• Architecture, page 1-10

• DSP Allocation, page 1-11

• InterVLAN Routing, page 1-14

Chapter 1 Product Overview

Architecture

• Quality of Service, page 1-14

• Layer 2 QoS, page 1-14

• Separate Voice and Data VLANs, page 1-15

• Single Voice and Data VLAN with dot1p, page 1-15

• Layer 3 QoS, page 1-16

• WAN QoS Queuing and Scheduling, page 1-16

• Summary of the Layer 3 WAN QoS Features, page 1-16

The Catalyst 4224 consists of the following physical subsystems:

• Time-division multiplexing (TDM) subsystem—Two VIC/WIC/VWIC slots,

one VIC slot, a built-in high-density FXS module, and a TDM switch

• CPU subsystem—Supports routing functions and interfaces for the TDM and

switch subsystems

• Switch subsystem—24 10/100 Ethernet port switch with QoS and interfaces

to the CPU and power subsystems

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-10

OL-2031-02

Chapter 1 Product Overview

• DSP subsystem—Interfaces to the TDM subsystem and CPU subsystem for

• Power subsystem—Provides power to the Catalyst 4224 and inline power to

From a logical view, the Catalyst 4224 looks like a router that connects an
Ethernet switch and a TDM switch in one system.

Figure 1-2 shows a logical view of the Catalyst 4224.

Figure 1-2 Logical View of Catalyst 4224

Application Notes

converting voice streams to IP packets

the IP phones that connect to the 10/100 Ethernet ports

IP

WAN

DSP Allocation

The Catalyst 4224 has six digital signal processors (DSPs) installed on the
motherboard. The DSPs convert voice signals into data packets and data packets
into voice signals. The DSPs on the Catalyst 4224 do not perform transcoding and
hardware conferencing. These services are performed at the central site by
Cisco CallManager. The DSPs only support VoIP. They do not support Voice
over Frame Relay (VoFR) and Voice over ATM (VoATM). The DSPs are not
field upgradeable.

IP

IP phone

PC

Switch

Printer

Router

TDM

PSTN

POTS

Fax

58705

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-11

Application Notes

Chapter 1 Product Overview

The DSPs compress and decompress packets based on codecs. The Catalyst 4224
supports the following codecs:

• G.711 a-law 64 Kbps

• G.711 mu-law 64 Kbps

• G.729 abr 8 Annex-A & B 8 Kbps

• G.729 ar8 G729 Annex-A 8 Kbps

• G 729 r8 G729 8 Kbps

The number of DSP channels that you can use depends upon the VIC
configuration. The following rules apply when you allocate DSP channels for
T-1/E-1 VWICs:

• The eight-port FXS Module uses two of the six DSPs by default, leaving four

DSPs to configure for digital voice.

• The maximum number of T1/E1 DS0s that you can configure is 24 on the six

available DSPs. The eight-port FXS module must be disabled using the CLI;
otherwise, only 16 channels are supported by four available DSPs.

• Only use DSP channels if you configure voice DS0s.

• Each set of four DS0s uses one DSP.

• One entire DSP is used even if less than four DS0s are configured. Five DS0s

use two DSPs.

• T1/E-1 DS0 channels cannot be used for analog channels.

Note You can disable the eight-Port FXS Module using the command line interface

(CLI), and thereby free up eight DSP channels for additional digital voice
channels.

The following rules apply when you allocate DSP channels for BRI, FXS, and
FXO VICs:

• The two-Port BRI VIC uses two of the available four DS0 channels if you

configure voice. You can use the other two DS0s for voice FXS or FXO, but
not T-1/E-1.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-12

OL-2031-02

Chapter 1 Product Overview

• The two-Port FXS and FXO VIC uses two of the available four DSO

• The eight-Port FXS Module uses eight DS0 channels or two DSPs, even if it

The following sample configuration shows DSP allocations:

C4224# sh voice dsp
BOOT
TYPE DSP CH CODEC VERS STATE STATE RST AI PORT TS
==== === == ======== ==== ===== ======= === == ======= ==

5409 001 00 {anlgHC} .8 IDLE idle 0 0 3/0 0
01 {anlgHC} .8 IDLE idle 0 0 3/1 0
5409 002 00 {anlgMC} .3 IDLE idle 0 0 4/0 0
01 {anlgMC} .3 IDLE idle 0 0 4/1 0
02 {anlgMC} .3 IDLE idle 0 0 4/2 0
03 {anlgMC} .3 IDLE idle 0 0 4/3 0
5409 003 04 {anlgMC} .3 IDLE idle 0 0 4/4 0
05 {anlgMC} .3 IDLE idle 0 0 4/5 0
06 {anlgMC} .3 IDLE idle 0 0 4/6 0
07 {anlgMC} .3 IDLE idle 0 0 4/7 0
5409 004 00 {medium} 3.5 IDLE idle 0 0 2/0:1 1
01 {medium} .8 IDLE idle 0 0 2/0:1 2
02 {medium} IDLE idle 0 0 2/0:1 3
03 {medium} IDLE idle 0 0 2/0:1 4
5409 005 00 {medium} 3.5 IDLE idle 0 0 2/0:1 5
01 {medium} .8 IDLE idle 0 0 2/0:1 6
02 {medium} IDLE idle 0 0 2/0:1 7
03 {medium} IDLE idle 0 0 2/0:1 8
5409 006 00 {medium} 3.5 IDLE idle 0 0 2/0:1 9
01 {medium} .8 IDLE idle 0 0 2/0:1 10
02 {medium} IDLE idle 0 0 2/0:1 11
03 {medium} IDLE idle 0 0 2/0:1 12

Application Notes

channels. The DSP is used when the VIC is plugged in, even if the ports are
not configured.

is not used (unless it is disabled using the CLI).

In the sample configuration, port 3/0 is an analog VIC that uses two of the four
channels in DSP 1. Slot 4 contains the eight-port FXS Module. This module takes
up two DSPs. DSP four, five, and six are being used for the 12 voice channels on
a MFT VWIC.

DSP resources are used for signaling and voice bearer channels. The signaling
channel is used for detecting off-hook/on-hook transitions.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-13

Application Notes

InterVLAN Routing

The forwarding performance for interVLAN routing on the Catalyst 4224 is
35 Kpps for 64-byte packets. Fast Switching is the default switching path. The
Catalyst 4224 supports Cisco Express Forwarding (CEF).

Quality of Service

The Catalyst 4224 can function as a Layer 2 switch connected to a Layer 3 router.
When a packet enters the Layer 2 engine directly from a switch port, it is placed
into one of four queues in the dynamic, 32-Mbyte shared memory buffer. The
queue assignment is based on the dot1p value in the packet. Any voice bearer
packets that come in from the IP phones on the voice VLAN are automatically
placed in the highest priority (Queue 3) based on the 802.1p value generated by
the IP phone. The queues are then serviced on a WRR basis. The control traffic,
which uses a CoS/ToS of 3, is placed in Queue 2.

Chapter 1 Product Overview

Layer 2 QoS

Table 1-3 summarizes the queues, CoS values, and weights for Layer 2 QoS on
the Catalyst 4224.

Table 1-3 Queues, CoS values, and Weights for Layer 2 QoS

Queue Number CoS Value Weight

3 5,6,7 255
23,464
1216
00,11

The weights specify the number of packets that are serviced in the queue before
moving on to the next queue. Voice Real-Time Transport Protocol (RTP) bearer
traffic marked with a CoS /ToS of 5 and Voice Control plane traffic marked with

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-14

OL-2031-02

Chapter 1 Product Overview

a CoS/ToS of 3 are placed into the highest priority Queues. If the queue has no
packets to be serviced, it will be skipped. WRED is not supported on the Fast
Ethernet ports.

The WRR default values cannot be changed. There are currently no CLI
commands to determine QoS information for WRR weights and queue mappings.
You cannot configure port-based QoS on the Layer 2 switch ports.

Separate Voice and Data VLANs

To be consistent with Cisco IP Telephony QoS design recommendations, you
should configure separate voice and data VLANs. The following sample
configuration shows how to configure separate voice and data VLANs.

interface FastEthernet5/22
no ip address
duplex auto
speed auto
switchport access vlan 60
switchport voice vlan 160
snmp trap link-status

Application Notes

Packets arriving on the specified voice VLAN will automatically have the 802.1p
priority values read on ingress. Unlike the Catalyst 3500, trunking mode does not
have to be used to distinguish between a voice and a data VLAN on a single port.

Single Voice and Data VLAN with dot1p

If the voice and data VLAN must be the same (a single subnet), using the dot1p
extension will enable the Catalyst 4224 to recognize the dot 1p CoS value from
the IP phone and place the packet in a queue based on the 802.1p value. The
following sample configuration shows how to configure a single voice and data
VLAN with dot1p.

interface FastEthernet5/23
no ip address
duplex auto
speed auto
switchport access vlan 160
switchport voice vlan dot1p

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-15

Application Notes

Similar to other voice-enabled Catalyst platforms, the Catalyst 4224 learns that an
IP phone is attached to the port via the CDP message exchange.

Layer 3 QoS

You can configure QoS on the Layer 3 CPU from the CLI, which is very similar
to the interface on the Cisco 1750, Cisco 2600 series, and Cisco 3600 series
routers.

WAN QoS Queuing and Scheduling

The Catalyst 4224 supports WAN QoS queuing and scheduling. Table 1-4 shows
Catalyst 4224 WAN QoS queuing and scheduling features.

Chapter 1 Product Overview

Table 1-4 Catalyst 4224 WAN QoS Queuing and Scheduling Features

Frame Relay MLPPP PPP HDLC

No LLQ/CBWFQ No LLQ/CBWFQ LLQ/CBWFQ LLQ/CBWFQ
IP RTP Priority No IP RTP

Priority

FRF.12 LFI

The Service Policy command is disabled for Frame Relay.

IP RTP Priority
with CBWFQ

Summary of the Layer 3 WAN QoS Features

In summary, the Catalyst 4224 supports the following Cisco IOS Layer 3 WAN
QoS features:

• Classification and Marking

–

Access control lists (ACL)

IP RTP Priority

–

Class-based marking

–

Class-based matching

–

Committed Access Rate (CAR)

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-16

OL-2031-02

Chapter 1 Product Overview

• Congestion Avoidance:

–

Differentiated services code point (DSCP) marking

–

IP Precedence

–

L2 Marking

–

L2 Matching

–

Match RTP

–

Network-based Application Recognition (NBAR)

–

Policy-based Routing (PBR)

–

QoS Preclassification for tunnels

–

Flow-based RED (FRED)

–

Weighted RED (WRED)

Application Notes

–

WRED with DSCP

• Policing and Traffic Shaping:

–

Class-based policing

–

Class-based shaping

–

IP Precedence

–

Frame Relay Traffic Shaping (FRTS)

–

General Traffic Shaping (GTS)

• Link Efficiency:

–

cRTP fast/CEF-switching

–

FR LFI (FRF.12)

–

MLPPP/LFI

–

RTP Header Compression (cRTP)

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-17

Configuration Guidelines

Configuration Guidelines

This section provides platform specific guidelines for configuring the
Catalyst 4224.

This section contains the following topics:

• Default Port Configuration, page 1-18

• Separate VLAN for Voice and Data, page 1-19

• Port Configuration for a Single Subnet, page 1-19

• InterVLAN and WAN Routing Configuration, page 1-20

• Centralized Cisco CallManager and DHCP Server, page 1-20

• Voice Port Configuration, page 1-21

• Interface Range Command Support, page 1-22

Chapter 1 Product Overview

• Switched Port Analyzer (SPAN), page 1-22

For Voice over IP (VoIP) configuration examples, see the following section in
this manual:

Appendix C, “VoIP Configuration Examples”

Default Port Configuration

The Catalyst 4224 boots up as a Layer 2 switch. The following sample
configuration shows a default port configuration.

C4224_SF# sh run int fas5/7

Building configuration...
Current configuration : 96 bytes
interface FastEthernet5/7
no ip address
duplex auto
speed auto
snmp trap link-status
end

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-18

OL-2031-02

Chapter 1 Product Overview

Separate VLAN for Voice and Data

Unlike the Catalyst 3500, you do not need to preconfigure VLANs with a VLAN
database command. To be consistent with Cisco IP Telephony QoS design
guidelines, you should configure a separate VLAN for voice and data. The
following example shows a recommended configuration.

interface FastEthernet5/22
no ip address
duplex auto
speed auto
switchport access vlan 60
switchport voice vlan 160
snmp trap link-status
spanning-tree portfast

This sample configuration instructs the IP phone to generate a packet with an

802.1q VLAN ID of 160 and an 802.1p value of 5 (default for voice bearer
traffic).

Configuration Guidelines

Note Portfast is supported only on nontrunk ports.

Port Configuration for a Single Subnet

If you have only a single subnet available, use the same subnet for voice and data.
The following sample configuration shows a port configuration for a single
subnet.

interface FastEthernet5/23
no ip address
duplex auto
speed auto
switchport access vlan 160
switchport voice vlan dot1p
snmp trap link-status
spanning-tree portfast

This sample configuration instructs the IP phone to generate an 802.1 Q frame
with a null VLAN ID value and an 802.1p value (default is CoS of 5 for bearer
traffic). The voice VLAN and data VLAN are both 160 in this example.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-19

Configuration Guidelines

InterVLAN and WAN Routing Configuration

Configuring interVLAN routing on the Catalyst 4224 is identical to configuring
interVLAN routing on the Catalyst 6000 with an MSFC. Configuring an interface
for WAN routing is consistent with other Cisco IOS platforms. The following
sample shows a configuration for interVLAN routing.

interface Vlan 160
description Voice VLAN
ip address 10.6.1.1 255.255.255.0

interface Vlan 60
description Data VLAN
ip address 10.60.1.1 255.255.255.0

interface Serial1/0
ip address 160.3.1.2 255.255.255.0

Chapter 1 Product Overview

The Catalyst 4224 supports standard IGP routing protocols such as RIP, Interior
Gateway Routing Protocol (IGRP), Enhanced Interior Gateway Routing Protocol
(EIGRP), and open shortest path first (OSPF). It also supports multicast routing
for PIM dense mode, sparse mode, and sparse-dense mode.

Centralized Cisco CallManager and DHCP Server

In a centralized Cisco CallManager deployment model, the DHCP server would
probably be located across the WAN link. You should include an ip helper
command on the voice VLAN interface that points to the DHCP server so that the
IP phone can obtain the IP address and the TFTP server address. The following
sample configuration shows a configuration for ip helper-address on the voice
VLAN:

interface Vlan 160
description Voice VLAN
ip address 10.6.1.1 255.255.255.0
ip helper-address 172.20.73.14

As an alternative, you could use the Cisco IOS DHCP server capabilities on the
Catalyst 4224. The following sample configuration shows a configuration for the
DHCP configuration options.

C4224_SF(config)# ip dhcp pool SF
C4224_SF(dhcp-config)# ?

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-20

OL-2031-02

Chapter 1 Product Overview

DHCP pool configuration commands:

client-identifier Client identifier
client-name Client name
default-router Default routers
dns-server DNS servers
domain-name Domain name
hardware-address Client hardware address
host Client IP address and mask
option Raw DHCP options

C4224_SF(dhcp-config)# option 150 ip ?

Hostname or A.B.C.D Server's name or IP address

Note DHCP option 150 is supported locally. This local support provides the IP address

of the TFTP server, which has the IP phones’ configuration. An ip
helper-address would not be required in this case because the IP phone has its IP

address and the TFTP server address. The configuration request to the TFTP
server is a unicast packet.

Configuration Guidelines

Voice Port Configuration

You configure voice ports on the Catalyst 4224 as you would in standard
Cisco IOS software. The following sample configuration shows a configuration
for the eight-port FXS Module:

dial-peer voice 41 voip
destination-pattern 1...
session target ipv4:172.20.73.13
codec g711ulaw
!
dial-peer voice 1005 pots
destination-pattern 1005
port 4/0

Catalyst 4224 Access Gateway Switch Software Configuration Guide

OL-2031-02

1-21

Recommended Configurations

Interface Range Command Support

You can use the range command. The following sample configuration shows how
to configure the range command:

C4224_SF(config)# int range fas5/2 - 5
switchport access vlan 60
switchport voice vlan 160

Switched Port Analyzer (SPAN)

Switched Port Analyzer (SPAN), also known as port monitoring, is supported for
up to two sessions. Spanning a VLAN is not supported. You can only span
selected interfaces. The following sample configuration shows a configuration for
setting a port monitor session with the range command:

Chapter 1 Product Overview

C4224_SF(config)# monitor session 1 ?
destination SPAN destination interface or VLAN
source SPAN source interface or VLAN

Recommended Configurations

This section contains the following topics:

• No VTP or DTP Support, page 1-23

• Creating a VLAN, page 1-23

• Defining a VLAN on a Trunk Port, page 1-23

• Trunking, page 1-24

• Fractional PRI Configuration, page 1-24

• No Ring Back Tone Generated, page 1-25

• MTP Required on Cisco CallManager, page 1-26

• H323-Gateway VOIP Bind SRCADDR Command, page 1-27

• Port Fast Not Enabled on Trunk Ports, page 1-28

• Priority Queuing on Frame Relay, page 1-28

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-22

OL-2031-02

Chapter 1 Product Overview

• Maximum Number of VLAN and Multicast Groups, page 1-29

• IP Multicast Support, page 1-29

No VTP or DTP Support

Using the interface switchport access or switchport trunk VLAN commands
automatically creates a voice VLAN and data VLAN. If you require an additional
VLAN beyond the voice and data VLAN when connecting to another switch, you
must add it manually using the VLAN database command from the EXEC prompt.

Creating a VLAN

The following sample configuration shows how to define a VLAN manually:

Recommended Configurations

C4224(vlan)# vlan 10 name external_switch_Vlan10

VLAN 10 added:
Name: external_switch_Vlan10
C4224(vlan)#vlan 11 name external_switch_Vlan11
VLAN 11 added:
Name: external_switch_Vlan11
C4224(vlan)#exit
APPLY completed.
Exiting...

Defining a VLAN on a Trunk Port

The following sample configuration shows how to define a VLAN on a trunk port.

C4224(config-if)# switchport trunk allowed vlan 10
C4224(config-if)# switchport trunk allowed vlan add 11

By default, the trunk interface accepts all VLANs created by the VLAN database.
Therefore, you should use the switchport trunk allowed command to delete
unwanted VLANs from the interface.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-23

Recommended Configurations

Trunking

The Catalyst 4224 supports only dot1Q trunking. Dynamic Trunking Protocol
(DTP) is not supported. A Catalyst switch that is trunked to the Catalyst 4224
must have the trunking mode set to either On or No negotiate and type dot1q.

Fractional PRI Configuration

The maximum of 16 channels are available for trunk voice ports. This can cause
a problem when a PSTN or PBX uses an unavailable channel to send a call to the
Catalyst 4224. To prevent this type of problem, follow this procedure:

Step 1 Always configure the Primary Rate Interface (PRI) VIC last (after you configure

all the VIC cards that require the DSP resources).

Chapter 1 Product Overview

Step 2 Allocate all 24 time slots for the PRI group. The following sample configuration

shows a configuration for the range command.

controller T1 1/0
framing esf
linecode b8zs
pri-group timeslots 1-24

Note The DSP resources are not sufficient for the 24 time slots. Therefore

you receive this message: insufficient DSP resources. Ignore this
message.

Note You need to tell the switch or PBX to make the time slots

out-of-service. If you do not allocate 24 time slots, a SERVICE
message is not sent for the unallocated time slots. This is an important
caveat.

Step 3 Use the show voice dsp command to see how many channels are allocated with

the available DSP resources. In a test case, 16 time slots could be allocated DSP
resources.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-24

OL-2031-02

Chapter 1 Product Overview

Step 4 Busy-out the time slots for which DSP resources could not be allocated. The

following sample configuration shows how to busy-out the time slots:

isdn service dsl 0 b_channel 17-24 state 2

Step 5 Use the show isdn service command to ensure that the channel is out-of-service.

The following sample configuration shows channels in service:

C4224# sh isdn ser
PRI Channel Statistics:
ISDN Se1/0:23, Channel [1-24]
Configured Isdn Interface (dsl) 0
Channel State (0=Idle 1=Proposed 2=Busy 3=Reserved 4=Restart
5=Maint_Pend)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3

Service State (0=Inservice 1=Maint 2=Outofservice)
Channel : 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
State : 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 2 2 2 2 2 2 2

Recommended Configurations

For incoming calls, only time slots 1-16 are used by the switch or PBX. North
American CO ISDN switches should support SERVICE/SERVCE ACK messages
for maintenance service of B-channels on the PRI span. For the CO switches that
do not support this service, you must ask the provider to busy-out the channels.

No Ring Back Tone Generated

When receiving or placing a call from an ISDN terminal (T1/E1 PRI), there is no
Progress IE in the setup. (Progress IE = 0.) The Catalyst 4224 does not generate
ringback when it receives an alert from Cisco CallManager. You can avoid this
situation and force the Catalyst 4224 to generate a ringback using the progress
indicator commands on the VoIP and POTS dial-peer statements. The following
sample configuration shows how to generate a ringback.

dial-peer voice 500 voip
destination-pattern 5...
progress_ind setup enable 3
session target ipv4:10.200.73.15
codec g711ulaw

dial-peer voice 300 pots
destination-pattern 1...

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-25

Recommended Configurations

progress_ind alert enable 8
port 3/1:23
forward-digits all

Note alert enable 8 is a hidden command option, which you cannot find by using

the ? at the CLI.

The following sample configuration shows what happens when you try to find this
command option:

C4224-2(config-dial-peer)# progress_ind alert ?

% Unrecognized command

This ringback situation applies only to PRI. It does not apply to BRI.

Chapter 1 Product Overview

MTP Required on Cisco CallManager

Prior to support for H.323 Version 2, you needed to enable the MTP Required
checkbox. This checkbox is located in the Catalyst 4224 H.323 Gateway
Configuration page in Cisco CallManager to define an H.323 gateway. All
Cisco IOS H.323 gateways with Cisco IOS 12.07 or later now support H.323
Version 2. You should not ordinarily enable this checkbox box when defining the
Catalyst 4224 as an H.323 Gateway. The only time you should check the box is if
transcoding is used at the central site. Transcoding would be necessary in
situations where the Catalyst 4224 uses G.729 for IP WAN calls and a voice mail
system at the central site supports G.711 only.

If you enable MTP Required on the Catalyst 4224 H.323 Gateway, analog POTS
calls to an IP phone locally connected will traverse the IP WAN. The call between
the analog FXS POTS and the IP Phone is anchored at the central site transcoding
device. This is normal behavior for a Cisco IOS H.323 gateway when MTP
Required is enabled. This leads to performance that is not optimal. Therefore,
unless transcoding is required, Media Termination Point (MTP) should not be
enabled on the H.323 Gateway definition for Catalyst 4224. Another option
would be to use G.711 across the IP WAN.

The following sample configurations show how the VoIP endpoints can be
verified.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-26

OL-2031-02

Chapter 1 Product Overview

With the MTP Required checkbox enabled:

The Catalyst 4224 is 10.253.1.1
Transcoder is Catalyst 6000 at Central : 10.1.1.11

C4224_SF# sh ip sock

Proto Remote Port Local Port In Out Stat TTY
OutputIF

17 10.1.1.11 16541 10.253.1.1 18757 0 0 1 0

With the MTP Required checkbox not enabled:

IP Phone is 10.6.1.4

C4224_SF# sh ip sock

Proto Remote Port Local Port In Out Stat TTY
OutputIF

17 10.6.1.4 26287 10.253.1.1 17047 0 0 1 0

Recommended Configurations

When the MTP Required checkbox is enabled, a call between a local IP phone and
an FXS analog POTS connected to the Catalyst 4224 is anchored at the transcoder
at the Central site, and local calls use WAN bandwidth. When the MTP Required
checkbox is not enabled, the local FXS-to-IP phone call is directly connected
between the Catalyst 4224 H.323 gateway and the IP phone.

H323-Gateway VOIP Bind SRCADDR Command

You must always use the following command to configure the IP address of the
gateway. This command ensures that the IP address included in the H.323 packet
is deterministic—it consistently indicates the same address for the source. If the
end point is non-deterministic, the call is anchored at the serial interface port and
silence or one-way audio occurs. The following sample configuration shows the
H323-gateway voip bind srcaddr command:

interface Loopback1
description h323 gateway address
ip address 10.253.1.1 255.255.255.0
h323-gateway voip bind srcaddr 10.253.1.1

You must place the h323 bind interface command on the interface with the IP
address that Cisco CallManager uses to define the H.323 gateway.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-27

Recommended Configurations

Port Fast Not Enabled on Trunk Ports

You should configure ports as switched access ports. However, there may be
implementations where your requirements dictate configuring ports as trunks and
you want to standardize this configuration across all 24 ports. This is not the
recommended configuration. Because of DHCP request timeouts on Windows
95/NT, portfast may be a desirable feature. However, portfast is not supported on
ports in trunking mode. To reduce the forwarding delay time of a port, use the
global configuration commands for the specific VLAN and reduce the forwarding
timers to the minimum value of four seconds. See the following sample
configuration:

spanning-tree portfast bpduguard
spanning-tree vlan 60 forward-time 4
spanning-tree vlan 160 forward-time 4

These commands configure VLAN ports to forward data in eight seconds.

Chapter 1 Product Overview

If you connect Catalyst 4224 to another switch, make sure that the timers are the
same value. Otherwise Spanning Tree issues may arise. Also note that only

802.1Q trunking is supported on the Catalyst 4224.

Priority Queuing on Frame Relay

Frame relay does not support LLQ/CBWFQ. The service policy output command
is currently disabled. Therefore, only ip rtp priority is supported as a voice
priority queuing scheme. FRF.12 is supported on frame relay links.

The recommended configuration for FRF.12 and ip rtp priority is shown in the
following procedure. The parameter values are for illustrative purposes only.
Your values may differ.

Step 1 Define the appropriate map class. The following sample configuration shows how

to define the map class:

map-class frame-relay VOIP_256
no frame-relay adaptive-shaping
frame-relay cir 250000
frame-relay bc 1000
frame-relay be 0
frame-relay mincir 250000
frame-relay fair-queue

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-28

OL-2031-02

Chapter 1 Product Overview

frame-relay fragment 320
frame-relay ip rtp priority 16384 16383 170

Step 2 Apply the map class to a frame relay sub interface. The following sample

configuration shows how to apply the map class:

interface Serial0/0.300 point-to-point
ip address 1.1.1.1
frame-relay interface-dlci 300
frame-relay class VOIP_256

Step 3 Apply frame relay shaping at the main interface. The following sample

configuration shows how to apply shaping:

interface ser0/0
encapsulation frame-relay
frame-relay traffic-shaping

Recommended Configurations

Maximum Number of VLAN and Multicast Groups

The maximum number of VLANs multiplied by the number of multicast groups
must be less than or equal to 242. For example, the number for 10 VLANs and 20
groups would be 200, which is within the 242 limit.

IP Multicast Support

The maximum number of multicast groups is related to the maximum number of
VLANs. The product of the number of multicast groups and the number of
VLANs cannot exceed 242. Multicast support includes the following items:

• Support for sparse mode, dense mode, and sparse-dense mode

• IGMP snooping Versions 1, 2, and 3

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-29

Recommended Configurations

Chapter 1 Product Overview

Catalyst 4224 Access Gateway Switch Software Configuration Guide

1-30

OL-2031-02

CHAPTER

2

Configuring for the First Time

This section describes the initial steps of configuring the Catalyst 4224 and
outlines the features of the Cisco IOS command line interface (CLI). Use this tool
when you configure Catalyst 4224 interfaces.

This section contains the following topics:

• First-Time Configuration, page 2-1

• Using the Cisco IOS CLI, page 2-5

First-Time Configuration

This section contains the following topics:

• Booting the Catalyst 4224, page 2-2

• Downloading an Image to Boot Flash Memory, page 2-2

• Configuring the Management Port, page 2-3

• Interface Numbering, page 2-4

Catalyst 4224 Access Gateway Switch Software Configuration Guide

OL-2031-02

2-1

First-Time Configuration

Booting the Catalyst 4224

The factory configures the Catalyst 4224 to automatically load a Cisco IOS
image. The software configuration register in the Catalyst 4224 determines where
to find the image. The factory sets this register to load the Cisco IOS image into
boot flash memory from configuration register 0x0101. This register enables
autoboot at register 0x0103.

Table 2-1 shows the Catalyst 4224 default configuration.

Table 2-1 Catalyst 4224 Default Configuration

Feature Default Value

Host name Router
Interface configuration None

Chapter 2 Configuring for the First Time

VLAN configuration None
Password encryption Disabled
Break to console Ignore

After booting the Catalyst 4224 for the first time, you can configure the interfaces
and then save the configuration to a file in NVRAM.

Downloading an Image to Boot Flash Memory

Note Before you can download an image, you must first configure the management

port. See “Configuring the Management Port” section on page 2-3.

If you have already configured the Catalyst 4224, you can download a run-time
image from a TFTP server on the network. TFTP downloads can take place over
the Ethernet management port.

To download an image to boot flash memory, use privileged mode to enter the
following command:

copy tftp: [/directory] /filename [/directory] /filename

Catalyst 4224 Access Gateway Switch Software Configuration Guide

2-2

OL-2031-02

Chapter 2 Configuring for the First Time

Connecting a Terminal

To connect a terminal to the console port using the cable and adapters provided
with the Catalyst 4224, connect to the port using the RJ-45-to-RJ-45 cable and
RJ-45-to-DB-25 DTE adapter or RJ-45-to-DB-9 DTE adapter (labeled Terminal).

Check the documentation that came with your terminal to determine the baud rate.
The baud rate of the terminal must match the default baud rate (9600 baud) of the
console port.

Set up the terminal as follows:

• 9600 baud

• Eight data bits

• No parity

• Two stop bits

First-Time Configuration

• No flow control

Connecting a Modem

Connect the modem to the port using the RJ-45-to-RJ-45 cable and the
RJ-45-to-DB-25 DCE adapter (labeled Modem).

Configuring the Management Port

You can manage the Catalyst 4224 through the 10/100 management port by
assigning it an IP address.

Caution By default, the Fast Ethernet interface does not route data traffic.

Cisco recommends that you do not override this default
configuration.

If the Ethernet 10/100 management port is up and an IP address has been
configured, the Catalyst 4224 selects the IP address assigned to the 10/100
Ethernet management port.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

2-3

First-Time Configuration

If the selected network management IP address is removed or the interface or
subinterface associated with this IP address is shut down, the Catalyst 4224
selects another IP address as a replacement.

If all the interfaces are down or no IP address has been assigned to any interface
or subinterface that is running, the IP address for network management is 0.0.0.0.

Interface Numbering

The Catalyst 4224 has three slots in which you can install interface cards:

• Slot 1 supports voice interface cards (VICs), WAN interface cards (WICs),

and voice and WAN interface cards (VWICs).

• Slot 2 supports VICs, WICs, and VWICs.

• Slot 3 supports VICs and VWICs but does not support WICs.

Chapter 2 Configuring for the First Time

• Slot 4 supports an eight-Port FXS RJ21 Module.

• Slot 5 supports 10/100 Ethernet switching ports.

Each individual interface is identified by a slot number and a port number. The
slots are numbered as follows:

• Slot 0 supports the following interfaces embedded in the mainboard:

–

Console port (con 0)

–

Ethernet Management port (Fast Ethernet 0/0)

• Slot 1 ports are numbered from right to left (1/1 and 1/0).

Note On the WIC-2A/S, the top slot is 1 and the bottom slot is 0.

• Slot 2 ports are numbered from right to left (2/1 and 2/0).

• Slot 3 ports are numbered from right to left (3/0 and 3/1).

When you configure an interface, identify the interface name before the slot and
port numbers. For example, if you install a serial T1 VWIC interface in Slot 2,
port 0 would be labeled as serial 2/0.

Figure 2-1 shows the Catalyst 4224 front panel.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

2-4

OL-2031-02

Chapter 2 Configuring for the First Time

Figure 2-1 Catalyst 4224 Front Panel

Using the Cisco IOS CLI

10/100 Ethernet (slot 5)

12 3456 78

V

W

IC

VW

IC

1

STATUS

ACCESS GATEWAY SWITCH

2

Status LED

VWIC

(slots 1 and 2)

Using the Cisco IOS CLI

Cisco voice gateways run versions of Cisco IOS software that includes
specialized adaptations for Voice over IP (VoIP) and Media Gateway Control
Protocol (MGCP). If you are familiar with other versions of Cisco IOS, you will
find configuring Cisco voice gateways straightforward because you will use the
Cisco IOS CLI, with which you are familiar.

Switch
utilization

910111213141516

CONSOLE

VIC 3

10/100 Mgt port

VIC

(slot 3)

17 18 19 20 21 22 23 24

04
15
26
37

WS-U4604-8FXS

HDA

STATUS

CATALYST 4224

8-Port RJ21 FXS
(slot 4)

PS

RPS

55803

If you have never used the Cisco IOS CLI, you should still be able to perform the
configuration required using the instructions and examples provided in this guide.
To help get you started, this section provides a brief overview of some of the main
features of the CLI. For further information, refer to the Cisco IOS configuration
guides and command references for details about specific commands.

This section contains the following topics:

• Getting Help, page 2-6

• Command Modes, page 2-6

• Disabling a Command or Feature, page 2-8

• Saving Configuration Changes, page 2-8

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

2-5

Using the Cisco IOS CLI

Getting Help

Chapter 2 Configuring for the First Time

Use the question mark (?) and arrow keys to help you enter commands, as follows:

• For a list of available commands, enter a question mark, for example:

Gateway> ?

• To complete a command, enter a few known characters followed by a

question mark (with no space), for example:

Gateway> s?

• For a list of command variables, enter the command followed by a space and

a question mark, for example:

Gateway> show ?

• To redisplay a command you previously entered, press the Up Arrow key.

You can continue to press the Up Arrow key for more commands.

Command Modes

The Cisco IOS interface is divided into different modes. Each command mode
permits you to configure different components on your gateway. The commands
available at any given time depend on which mode you are currently using.
Entering a question mark (?) at the prompt displays a list of commands available
for each command mode. Table 2-2 lists the most common command modes.

Table 2-2 Common Command Modes

Command Mode Access Method

User EXEC Log in.

Privileged EXEC From user EXEC mode,

enter the enable command.

Gateway Prompt
Displayed Exit Method

hostname>

Use the logout command.

The default is

router>

hostname#

To exit to user EXEC
mode, use the disable,

The default is

router#

exit, or logout command.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

2-6

OL-2031-02

Chapter 2 Configuring for the First Time

Table 2-2 Common Command Modes (continued)

Command Mode Access Method

Using the Cisco IOS CLI

Gateway Prompt
Displayed Exit Method

Global configuration From the privileged EXEC

mode, enter the configure
terminal command.

Interface
configuration

From the global
configuration mode, enter
the interface type number
command, such as
FastEthernet int 0/0.

Dial-peer
configuration

From the global
configuration mode, enter
the dial-peer voice
command, such as

dial-peer voice 1
pots/voip.

hostname
(config)#

The default is

router (config)#

hostname
(config-if)#

The default is

router (config-if)#

hostname(config-

dial-peer)

The default is

router

(config-dial-peer)#

To exit to privileged EXEC
mode, use the exit or end
command, or press Ctrl-Z.

To exit to global
configuration mode, use
the exit command.

To exit directly to
privileged EXEC mode,
press Ctrl-Z.

To exit to global
configuration mode, use
the exit command.

To exit directly to
privileged EXEC mode,
press Ctrl-Z.

OL-2031-02

Timesaver Each command mode restricts you to a subset of commands. If you are having

trouble entering a command, check the prompt and enter the question mark (?) for
a list of available commands. You might be in the wrong command mode or using
the wrong syntax.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

2-7

Using the Cisco IOS CLI

Note You can press Ctrl-Z in any mode to return immediately to privileged EXEC

Chapter 2 Configuring for the First Time

In the following example, which uses the default prompt (router>), notice how the
prompt changes after each command to indicate a new command mode:

router> enable
Password: <enable password>
router# configure terminal
router(config-if)# line 0
router(config-line)# controller t1 1/0
router(config-controller)# exit
router(config)# exit
router#
%SYS-5-CONFIG_I: Configured from console by console

The last message is normal and does not indicate an error. Press Return to return
to the prompt.

mode (router#), instead of entering exit, which returns you to the previous mode.

Disabling a Command or Feature

If you want to undo a command you entered or disable a feature, enter the
keyword no before most commands; for example, no mgcp.

Saving Configuration Changes

You need to enter the copy running-config startup-config command to save
your configuration changes to nonvolatile random-access memory (NVRAM), so
the changes are not lost if there is a system reload or power outage; for example:

router# copy running-config startup-config

Building configuration...

Note It might take a minute or two to save the configuration to NVRAM. After the

configuration has been saved, the privileged EXEC mode prompt (
reappears.

router#)

Catalyst 4224 Access Gateway Switch Software Configuration Guide

2-8

OL-2031-02

CHAPTER

3

Configuring Ethernet Switching

This section describes the Ethernet switching capabilities of the Catalyst 4224.
These capabilities are designed to work as part of the Cisco IP Telephony
solution.

This section also outlines how to configure Ethernet ports on the Catalyst 4224 to
support IP phones in a branch office on your network.

This section contains the following topics:

• Configuring the Catalyst 4224 for Cisco IP Telephony, page 3-1

• Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained

Workstation, page 3-3

• Configuring Ethernet Ports to Support IP Phones with Multiple Ports,

page 3-9

• Managing the Catalyst 4224 Access Gateway Switch, page 3-10

Configuring the Catalyst 4224 for Cisco IP Telephony

The Catalyst 4224 has 24 10/100 switched Ethernet ports with integrated inline
power and Quality of Service (QoS) features. These features allow you to extend
Voice-over-IP (VoIP) networks to small branch offices.

As an access gateway switch, the Catalyst 4224 can be deployed as a component
of a centralized call processing network using a centrally deployed
Cisco CallManager. Instead of deploying and managing key systems or PBXs in
small branch offices, applications are centrally located at the corporate
headquarters or data center and are accessed via the IP WAN.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

OL-2031-02

3-1

Chapter 3 Configuring Ethernet Switching

Configuring the Catalyst 4224 for Cisco IP Telephony

Default Switch Configuration

By default, the Catalyst 4224 provides the following settings with respect to
Cisco IP Telephony:

• All switch ports are in access VLAN 1.

• All switch ports are static access ports, not 802.1Q trunk ports.

• Default voice VLAN is not configured on the switch.

• Inline power is automatically supplied on the 10/100 ports.

Connecting IP Phones to Your Campus Network

There are three ways to connect an IP phone to a campus network. You can use a
single cable, multiple cables, or the Cisco IP SoftPhone application running on a
PC. (See Figure 3-1.)

Figure 3-1 Ways to Connect IP Phones to the Network

Single

1

cable

IP

IP

Multiple

2

cables

3

Cisco.IP
SoftPhone

IP

55371

For more information about Option 1, see the “Configuring Ethernet Ports to

Support IP Phones and a Daisy-Chained Workstation” section on page 3-3.

For more information about Option 2, see the “Configuring Ethernet Ports to

Support IP Phones with Multiple Ports” section on page 3-9.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-2

OL-2031-02

Chapter 3 Configuring Ethernet Switching

Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation

For more information about Option 3, which entails the Cisco IP SoftPhone
application, see the Cisco IP SoftPhone documentation library. The
Cisco IP SoftPhone application was developed to provide clients with a phone
that runs on software. This application can be installed on any PC that connects
to an IP telephony network.

Configuring Ethernet Ports to Support IP Phones and
a Daisy-Chained Workstation

Figure 3-2 shows the topology of a centralized Cisco CallManager deployment

model used to enable converged networks.

Figure 3-2 Catalyst 4224 with IP Phone and Workstation

Central

Cisco CallManager

Switch

Router

IP

WAN

Catalyst 4224

V

IP

IP phone

58654

The configurations described in this section use the model shown in Figure 3-2.
In this model, voice traffic is given a higher priority (CoS=5) than data traffic
(CoS=0). Hence, voice traffic is placed in a high-priority queue that gets serviced
first, and data traffic is placed in a low-priority queue that gets serviced later.

This section describes the following configuration schemes:

• Configuring Separate Voice and Data Subnets, page 3-4

• Configuring a Single Subnet for Voice and Data, page 3-7

For details on the commands used in the following configuration examples, refer
to Appendix A, “Command Reference for Voice VLAN.”

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-3

Chapter 3 Configuring Ethernet Switching

Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation

Note In the following configurations, the powerinline command is set to auto by

default.

Configuring Separate Voice and Data Subnets

For ease of network administration and increased scalability, network managers
can configure the Catalyst 4224 to support Cisco IP phones such that the voice
and data traffic reside on separate subnets. You should always use separate
VLANs when you are able to segment the existing IP address space of your branch
office.

User priority bits in the 802.1p portion of the 802.1Q standard header are used to
provide prioritization in Ethernet switches. This is a vital component in designing
Cisco IP Telephony networks.

The Catalyst 4224 provides the performance and intelligent services of Cisco IOS
software for branch office applications. The Catalyst 4224 can identify user
applications—such as voice or multicast video—and classify traffic with the
appropriate priority levels. QoS policies are enforced using Layer 2 and 3
information such as 802.1p, IP precedence, and DSCP.

Note Refer to the Cisco AVVID QoS Design Guide for more information on how to

implement end-to-end QoS as you deploy Cisco IP Telephony solutions.

The following exit procedure shows how to automatically configure Cisco IP
phones to send voice traffic on the voice VLAN ID (VVID). (See the “Vo i c e

Traffic and VVID” section on page 3-5.)

Task Command

Step 1

Enable VLAN database.

ID range is 1 to 1005.

enable
vlan database
vlan id
exit

Step 2

Set up switch port to configure IP phone on
voice VLAN (on per-port basis).

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-4

OL-2031-02

Chapter 3 Configuring Ethernet Switching

Task Command

Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation

Step 3

Enter the privileged EXEC mode. A preset
password may be required to enter this
mode.

Enter global configuration mode.
Enter the interface configuration mode and

the port to be configured (for example,
interface fa5/1).

Configure the port as access and assign a
data VLAN.

Configure the voice port with a VVID that
will be used exclusively for voice traffic.

Verify the switch port configuration and
save it.

Verify the port configuration you just
entered.

Save the current configuration in Flash
memory.

enable

configure terminal

interface interface

switchport access vlan

vlan-id

switchport voice vlan vlan-id

show run interface interface

write memory

Voice Traffic and VVID

The Catalyst 4224 can automatically configure voice VLAN. With the
automatically configured voice VLAN feature, network administrators can
segment phones into separate logical networks even though the data and voice
infrastructure is physically the same. The voice VLAN feature places the phones
into their own VLANs without the need for end-user intervention. A user can plug
the phone into the switch, and the switch provides the phone with the necessary
VLAN information.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-5

Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation

Sample Configuration 1

The following example shows how to configure separate subnets for voice and
data on the Catalyst 4224:

interface FastEthernet5/1
description DOT1Q port to IP Phone
switchport access vlan 50
switchport voice vlan 150
spanning-tree portfast (See Note below)

interface Vlan 150

description voice vlan
ip address 10.150.1.1 255.255.255.0
ip helper-address 172.20.73.14 (See Note below)

interface Vlan 50

description data vlan
ip address 10.50.1.1 255.255.255.0

Chapter 3 Configuring Ethernet Switching

This configuration instructs the IP phone to generate a packet with an 802.1Q
VLAN ID of 150 with an 802.1p value of 5 (default for voice bearer traffic).

Note The portfast command is only supported on nontrunk ports.

Note In a centralized Cisco CallManager deployment model, the DHCP server

might be located across the WAN link. If so, an ip helper-address command
pointing to the DHCP server should be included on the voice VLAN interface
for the IP phone. This is done to obtain its IP address as well as the address of
the TFTP server required for its configuration.

Be aware that Cisco IOS supports a DHCP server function. If this function is
used, the Catalyst 4224 serves as a local DHCP server and a helper address
would not be required.

Sample Configuration 2

Configuring inter-VLAN routing is identical to the configuration on a Catalyst
6000 with an MSFC. Configuring an interface for WAN routing is consistent with
other Cisco IOS platforms.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-6

OL-2031-02

Chapter 3 Configuring Ethernet Switching

The following example provides a sample configuration:

interface Vlan 160
description voice vlan
ip address 10.6.1.1 255.255.255.0

interface Vlan 60

description data vlan
ip address 10.60.1.1 255.255.255.0

interface Serial1/0

ip address 160.3.1.2 255.255.255.0

Note Standard IGP routing protocols such as RIP, Interior Gateway Routing

Protocol (IGRP), Enhanced Interior Gateway Routing Protocol (EIGRP), and
open shortest path first (OSPF) are supported on the Catalyst 4224. Multicast
routing is also supported for PIM dense mode, sparse mode, and sparse-dense
mode.

Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation

Configuring a Single Subnet for Voice and Data

For network designs with incremental IP telephony deployment, network
managers can configure the Catalyst 4224 so that the voice and data traffic coexist
on the same subnet. This might be necessary when it is impractical to allocate an
additional IP subnet for IP phones. You must still prioritize voice above data at
both Layer 2 and Layer 3.

Layer 3 classification is already handled because the phone sets the type of
service (ToS) bits in all media streams to an IP Precedence value of 5. (With
Cisco CallManager Release 3.0(5), this marking changed to a Differentiated
Services Code Point [DSCP] value of EF.) However, to ensure that there is
Layer 2 classification for admission to the multiple queues in the branch office
switches, the phone must also use the User Priority bits in the Layer 2 802.1p
header to provide class of service (CoS) marking. Setting the bits to provide
marking can be done by having the switch look for 802.1p headers on the native
VLAN.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-7

Configuring Ethernet Ports to Support IP Phones and a Daisy-Chained Workstation

This configuration approach must address two key considerations:

• Network managers should ensure that existing subnets have enough available

IP addresses for the new Cisco IP phones, each of which requires a unique
IP address.

• Administering a network with a mix of IP phones and workstations on the

same subnet might pose a challenge.

The following procedure shows how to automatically configure Cisco IP phones
to send voice and data traffic on the same VLAN.

Task Command

Chapter 3 Configuring Ethernet Switching

Step 1

Set up switch port to configure IP phone on
the same VLAN as the access VLAN.

Enter global configuration mode.
Enter the interface configuration mode and

the port to be configured (for example,

interface fa5/1)

Set the native VLAN for untagged traffic.
vlan-id represents the ID of the VLAN that

is sending and receiving untagged traffic on
the port. Valid IDs are from 1 to 1001.
Leading zeroes are not accepted.

Configure the Cisco IP Phone to send voice
traffic with higher priority (CoS=5 on

802.1Q tag) on the access VLAN. Data
traffic (from an attached PC) is sent
untagged for lower priority (port
default=0).

Return to the privileged EXEC mode.

configure terminal

interface interface

switchport access vlan

vlan-id

switchport voice vlan dot1p

end

Step 2

Verify the switch port configuration and
save.

Verify the port configuration you just
entered.

Save the current configuration in Flash
memory.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-8

show run interface interface

write memory

OL-2031-02

Chapter 3 Configuring Ethernet Switching

Sample Configuration

The Catalyst 4224 supports the use of an 802.1p-only option when configuring
the voice VLAN. Use this option to allow the IP phone to tag VoIP packets with
a CoS of 5 on the native VLAN, while all PC data traffic is sent untagged.

The following example shows a single subnet configuration for the Catalyst 4224
switch:

interface FastEthernet5/2
description Port to IP Phone in single subnet
switchport access vlan 40
switchport voice vlan dot1p
spanning-tree portfast

The Catalyst 4224 instructs the IP phone to generate an 802.1Q frame with a null
VLAN ID value but with an 802.1p value (default is CoS of 5 for bearer traffic).
The voice and data vlans are both 40 in this example.

Configuring Ethernet Ports to Support IP Phones with Multiple Ports

Configuring Ethernet Ports to Support IP Phones with
Multiple Ports

You might want to use multiple ports to connect the IP phones (option 2 in

Figure 3-1) if any of the following conditions apply to your Cisco IP telephony

network:

• You are connecting IP phones that do not have a second Ethernet port for

attaching a PC.

• You want to create a physical separation between the voice and data

networks.

• You want to provide in-line power easily to the IP phones without having to

upgrade the data infrastructure.

• You want to limit the number of switches that need UPS power.

IP Addressing

The recommended configuration for using multiple cables to connect IP phones
to the network is to use a separate IP subnet and separate VLANs for IP telephony.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-9

Managing the Catalyst 4224 Access Gateway Switch

Sample Configuration

The following example illustrates the configuration on the IP phone:

interface FastEthernetx/x
switchport voice vlan x

The following example illustrates the configuration on the PC:

interface FastEthernetx/y
switchport access vlan y

Note Using a separate subnet, and possibly a separate IP address space, may not be an

option for some small branch offices due to the IP routing configuration. If the IP
routing can handle an additional subnet at the remote branch, you can use Cisco
Network Registrar and secondary addressing.

Chapter 3 Configuring Ethernet Switching

Managing the Catalyst 4224 Access Gateway Switch

This section illustrates how to perform basic management tasks on the
Catalyst 4224 with the Cisco IOS command-line interface (CLI). You might find
this information useful when you configure the switch for the previous scenarios.

Note For reference information on the voice commands used in this section, refer to the

Appendix A, “Command Reference for Voice VLAN.”

This section contains the following topics:

• Adding Trap Managers, page 3-11

• Configuring IP Information, page 3-11

• Configuring Voice Ports, page 3-14

• Enabling and Disabling Switch Port Analyzer, page 3-16

• Managing the ARP Table, page 3-17

• Managing the MAC Address Tables, page 3-18

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-10

OL-2031-02

Chapter 3 Configuring Ethernet Switching

Adding Trap Managers

A trap manager is a management station that receives and processes traps. When
you configure a trap manager, community strings for each member switch must
be unique. If a member switch has an assigned IP address, the management station
accesses the switch by using its assigned IP address.

By default, no trap manager is defined, and no traps are issued.
Beginning in privileged EXEC mode, follow these steps to add a trap manager and

community string:

Task Command

Managing the Catalyst 4224 Access Gateway Switch

Step 1
Step 2

Enter global configuration mode.
Enter the trap manager IP address,

community string, and the traps to generate.

Step 3
Step 4

Return to privileged EXEC mode.
Verify that the information was entered

correctly by displaying the running
configuration.

Configuring IP Information

This section describes how to assign IP information on the Catalyst 4224, and
contains the following topics:

• Assigning IP Information to the Switch—Overview, page 3-11

• Assigning IP Information to the Switch—Procedure, page 3-12

• Removing an IP Address, page 3-13

• Specifying a Domain Name and Configuring the DNS, page 3-13

config terminal

snmp-server host

172.2.128.263 traps1 snmp
vlan-membership

end

show running-config

Assigning IP Information to the Switch—Overview

You can use a BOOTP server to automatically assign IP information to the switch;
however, the BOOTP server must be set up in advance with a database of physical
MAC addresses and corresponding IP addresses, subnet masks, and default

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-11

Managing the Catalyst 4224 Access Gateway Switch

gateway addresses. In addition, the switch must be able to access the BOOTP
server through one of its ports. At startup, a switch without an IP address requests
the information from the BOOTP server; the requested information is saved in the
switch running the configuration file. To ensure that the IP information is saved
when the switch is restarted, save the configuration by entering the write memory
command in privileged EXEC mode.

You can change the information in these fields. The mask identifies the bits that
denote the network number in the IP address. When you use the mask to create a
subnet on a network, the mask is then referred to as a subnet mask. The broadcast
address is reserved for sending messages to all hosts. The CPU sends traffic to an
unknown IP address through the default gateway.

Assigning IP Information to the Switch—Procedure

Beginning in privileged EXEC mode, follow these steps to enter the IP
information:

Chapter 3 Configuring Ethernet Switching

Step 1
Step 2

Step 3

Step 4
Step 5
Step 6
Step 7

Task Command

Enter global configuration mode.
Enter interface configuration mode, and

configure terminal

interface vlan 1

enter the VLAN to which the IP
information is assigned.

VLAN 1 is the management VLAN, but you
can configure any VLAN from IDs 1 to

1001.
Enter the IP address and subnet mask.

Return to global configuration mode.
Enter the IP address of the default router.
Return to privileged EXEC mode.
Verify that the information was entered

ip address ip_address
subnet_mask

exit

ip default-gateway ip_address

end

show running-config

correctly by displaying the running
configuration. If the information is
incorrect, repeat the procedure.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-12

OL-2031-02

Chapter 3 Configuring Ethernet Switching

Removing an IP Address

Use the following procedure to remove IP information from a switch.

Note Using the no ip address command in configuration mode disables the IP protocol

stack and removes the IP information. Cluster members without IP addresses rely
on the IP protocol stack being enabled.

Beginning in privileged EXEC mode, follow these steps to remove an IP address:

Task Command

Managing the Catalyst 4224 Access Gateway Switch

Step 1

Enter interface configuration mode, and
enter the VLAN to which the IP
information is assigned.

VLAN 1 is the management VLAN, but you
can configure any VLAN from IDs 1 to

1001.

Step 2
Step 3
Step 4

Remove the IP address and subnet mask.
Return to privileged EXEC mode.
Verify that the information was removed by

displaying the running configuration.

Caution If you are removing the IP address through a Telnet session, your connection to

the switch will be lost.

Specifying a Domain Name and Configuring the DNS

interface vlan 1

no ip address

end

show running-config

Each unique IP address can have an associated host name. Cisco IOS software
maintains a cache of host name-to-address mappings for use by the EXEC mode
commands connect, telnet, ping, and related Telnet support operations. This
cache speeds the process of converting names to addresses.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-13

Managing the Catalyst 4224 Access Gateway Switch

IP defines a hierarchical naming scheme that allows a device to be identified by
its location or domain. Domain names are pieced together with periods (.) as the
delimiting characters. For example, Cisco Systems is a commercial organization
that IP identifies by a com domain name, so its domain name is cisco.com. A
specific device in this domain, such as the File Transfer Protocol (FTP) system,
is identified as ftp.cisco.com.

To track domain names, IP has defined the concept of a domain name server
(DNS), whose purpose is to hold a cache (or database) of names mapped to
IP addresses. To map domain names to IP addresses, you must first identify the
host names and then specify a name server and enable the DNS, the Internet’s
global naming scheme that uniquely identifies network devices.

Specifying the Domain Name

You can specify a default domain name that the software uses to complete domain
name requests. You can specify either a single domain name or a list of domain
names. When you specify a domain name, any IP host name without a domain
name will have that domain name appended to it before being added to the host
table.

Chapter 3 Configuring Ethernet Switching

Specifying a Name Server

You can specify up to six hosts that can function as a name server to supply name
information for the DNS.

Enabling the DNS

If your network devices require connectivity with devices in networks for which
you do not control name assignment, you can assign device names that uniquely
identify your devices within the entire internetwork. The Internet’s global naming
scheme, the DNS, accomplishes this task. This service is enabled by default.

Configuring Voice Ports

The Catalyst 4224 can connect to a Cisco 7960 IP Phone and carry IP voice
traffic. If necessary, the Catalyst 4224 can supply electrical power to the circuit
connecting it to the Cisco 7960 IP Phone.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-14

OL-2031-02

Chapter 3 Configuring Ethernet Switching

Managing the Catalyst 4224 Access Gateway Switch

Because the sound quality of an IP telephone call can deteriorate if the data is
unevenly transmitted, the current release of the Cisco IOS software supports
Quality of Service (QoS) based on IEEE 802.1p Class of Service (CoS). QoS uses
classification and scheduling to transmit network traffic from the switch in a
predictable manner.

The Cisco 7960 IP Phone contains an integrated three-port 10/100 switch. These
dedicated ports connect to the following devices:

• Port 1 connects to the Catalyst 4224 switch or other Voice-over-IP device.

• Port 2 is an internal 10/100 interface that carries the phone traffic.

• Port 3 connects to a PC or other device.

Figure 3-2 on page 3-3 shows a sample configuration for a Cisco 7960 IP Phone.

Configuring a Port to Connect to a Cisco 7960 IP Phone

Because a Cisco 7960 IP Phone also supports connection to a PC or other device,
a port connecting a Catalyst 4224 to a Cisco 7960 IP Phone can carry a mix of
traffic. There are three ways to configure a port connected to a Cisco 7960 IP
Phone:

• All traffic is transmitted according to the default CoS priority (0) of the port.

This is the default.

• Voice traffic is given a higher priority by the phone, and all traffic is in the

same VLAN.

• Voice and data traffic are carried on separate VLANs, and voice traffic

always has a CoS priority of five.

Disabling Inline Power on a Catalyst 4224

The Catalyst 4224 can supply inline power to the Cisco 7960 IP Phone if
necessary. The Cisco 7960 IP Phone can also be connected to an AC power source
and supply its own power to the voice circuit. When the Cisco 7960 IP Phone is
supplying its own power, a Catalyst 4224 can forward IP voice traffic to and from
the phone.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-15

Managing the Catalyst 4224 Access Gateway Switch

A detection mechanism on the Catalyst 4224 determines whether it is connected
to a Cisco 7960 IP Phone. If the switch senses that there is no power on the circuit,
the switch supplies the power. If there is power on the circuit, the switch does not
supply it.

You can configure the switch to never supply power to the Cisco 7960 IP Phone
and to disable the detection mechanism.

Beginning in privileged EXEC mode, follow these steps to configure a port to
never supply power to Cisco 7960 IP Phones:

Task Command

Chapter 3 Configuring Ethernet Switching

Step 1
Step 2

Enter global configuration mode.
Enter interface configuration mode,

configure terminal
interface interface

and enter the port to be configured.

Step 3

Permanently disable inline power on

power inline never

the port.

Step 4
Step 5

Return to privileged EXEC mode.
Verify the change by displaying the

setting as configured.

Note Entering the show power inline [interface-type number] command in privileged

end

show power inline interface
configured

EXEC mode displays the power allocated to the IP phone by the Catalyst 4224.
To display the maximum power requested by the IP phone, enter the show cdp
neighbors [interface-type number] detail command in privileged EXEC mode.

Enabling and Disabling Switch Port Analyzer

You can monitor traffic on a given port by forwarding incoming and outgoing
traffic on the port to another port in the same VLAN. A Switch Port Analyzer
(SPAN) port cannot monitor ports in a different VLAN, and a SPAN port must be
a static-access port. Any number of ports can be defined as SPAN ports, and any
combination of ports can be monitored. SPAN is supported for up to two sessions.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-16

OL-2031-02

Chapter 3 Configuring Ethernet Switching

Enabling the Switch Port Analyzer

Beginning in privileged EXEC mode, follow these steps to enable SPAN:

Task Command

Managing the Catalyst 4224 Access Gateway Switch

Step 1
Step 2

Enter global configuration mode.
Enable port monitoring for a specific

session (“number”).
Optionally, supply a SPAN destination
interface, and a source interface

Step 3
Step 4

Return to privileged EXEC mode.
Verify your entries.

Disabling Switch Port Analyzer

Beginning in privileged EXEC mode, follow these steps to disable SPAN:

Task Command

Step 1
Step 2

Step 3

Enter global configuration mode.
Disable port monitoring for a specific

session.
Return to privileged EXEC mode.

configure terminal

monitor session number

destination source

end

show running-config

configure terminal

no monitor session number

end

Step 4

Verify your entries.

Managing the ARP Table

To communicate with a device (on Ethernet, for example), the software first must
determine the 48-bit MAC or local data link address of that device. The process
of determining the local data link address from an IP address is called address
resolution.

OL-2031-02

show running-config

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-17

Managing the Catalyst 4224 Access Gateway Switch

The Address Resolution Protocol (ARP) associates a host IP address with
corresponding media or MAC addresses and VLAN ID. Taking an IP address as
input, ARP determines the associated MAC address. Once a MAC address is
determined, the IP-MAC address association is stored in an ARP cache for rapid
retrieval. Then, the IP datagram is encapsulated in a link-layer frame and sent
over the network.

Encapsulation of IP datagrams and ARP requests and replies on IEEE 802
networks other than Ethernet is specified by the Subnetwork Access Protocol
(SNAP). By default, standard Ethernet-style ARP encapsulation (represented by
the arpa keyword) is enabled on the IP interface.

When you manually add entries to the ARP Table by using the CLI, you must be
aware that these entries do not age and must be manually removed.

Managing the MAC Address Tables

Chapter 3 Configuring Ethernet Switching

The switch uses the MAC address tables to forward traffic between ports. All
MAC addresses in the address tables are associated with one or more ports. These
MAC tables include the following types of addresses:

• Dynamic address—A source MAC address that the switch learns and then

drops when it is not in use.

• Secure address—A manually entered unicast address that is usually

associated with a secured port. Secure addresses do not age.

• Static address—A manually entered unicast or multicast address that does not

age and that is not lost when the switch resets.

The address tables list the destination MAC address and the associated VLAN ID,
module, and port number associated with the address. Figure 3-3 shows an
example of a list of addresses as they would appear in the dynamic, secure, or
static address table.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-18

OL-2031-02

Chapter 3 Configuring Ethernet Switching

Figure 3-3 Contents of the Address Table

MAC Addresses and VLANs

All MAC addresses are associated with one or more VLANs. An address can exist
in more than one VLAN and have different destinations in each. Multicast
addresses, for example, could be forwarded to port 1 in VLAN 1 and ports 9, 10,
and 11 in VLAN 5.

Managing the Catalyst 4224 Access Gateway Switch

Each VLAN maintains its own logical address table. A known address in one
VLAN is unknown in another until it is learned or statically associated with a port
in the other VLAN. An address can be secure in one VLAN and dynamic in
another. Addresses that are statically entered in one VLAN must be static
addresses in all other VLANs.

Changing the Address Aging Time

Dynamic addresses are source MAC addresses that the switch learns and then
drops when they are not in use. Use the Aging Time field to define how long the
switch retains unseen addresses in the table. This parameter applies to all VLANs.

Configuring the Aging Time

Setting too short an aging time can cause addresses to be prematurely removed
from the table. When the switch receives a packet for an unknown destination, the
switch floods the packet to all ports in the same VLAN as the receiving port. This
unnecessary flooding can impact performance. Setting too long an aging time can
cause the address table to be filled with unused addresses; it can cause delays in
establishing connectivity when a workstation is moved to a new port.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-19

Managing the Catalyst 4224 Access Gateway Switch

Beginning in privileged EXEC mode, follow these steps to configure the dynamic
address table aging time.

Task Command

Chapter 3 Configuring Ethernet Switching

Step 1
Step 2

Enter global configuration mode.
Enter the number of seconds that dynamic

addresses are to be retained in the address
table. You can enter a number from 10 to

1000000.

Step 3
Step 4

Return to privileged EXEC mode.
Verify your entry.

Removing Dynamic Address Entries

Beginning in privileged EXEC mode, follow these steps to remove a dynamic
address entry:

Task Command

Step 1
Step 2

Enter global configuration mode.
Enter the MAC address to be removed from

dynamic MAC address table.

configure terminal

mac-address-table aging-time

seconds

end

show mac-address-table
aging-time

configure terminal

no mac-address-table dynamic

hw-addr

Step 3
Step 4

Return to privileged EXEC mode.
Verify your entry.

You can remove all dynamic entries by using the clear mac-address-table
dynamic command in privileged EXEC mode.

Adding Secure Addresses

The secure address table contains secure MAC addresses and their associated
ports and VLANs. A secure address is a manually entered unicast address that is
forwarded to only one port per VLAN. If you enter an address that is already
assigned to another port, the switch reassigns the secure address to the new port.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-20

end

show mac-address-table

OL-2031-02

Chapter 3 Configuring Ethernet Switching

You can enter a secure port address even when the port does not yet belong to a
VLAN. When the port is later assigned to a VLAN, packets destined for that
address are forwarded to the port.

Adding Secure Addresses

Beginning in privileged EXEC mode, follow these steps to add a secure address:

Task Command

Managing the Catalyst 4224 Access Gateway Switch

Step 1
Step 2

Enter global configuration mode.
Enter the MAC address, its associated port,

and the VLAN ID.

Step 3
Step 4

Return to privileged EXEC mode.
Verify your entry.

Removing Secure Addresses

Beginning in privileged EXEC mode, follow these steps to remove a secure
address:

Task Command

Step 1
Step 2

Enter global configuration mode.
Enter the secure MAC address, its

associated port, and the VLAN ID to be
removed.

Step 3

Return to privileged EXEC mode.

configure terminal

mac-address-table secure

hw-addr interface

vlan vlan-id

end

show mac-address-table secure

configure terminal

no mac-address-table secure

hw-addr

end

vlan vlan-id

Step 4

Verify your entry.

You can remove all secure addresses by using the clear mac-address-table
secure command in privileged EXEC mode.

OL-2031-02

show mac-address-table secure

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-21

Managing the Catalyst 4224 Access Gateway Switch

Adding and Removing Static Addresses

A static address has the following characteristics:

• It is manually entered in the address table and must be manually removed.

• It can be a unicast or multicast address.

• It does not age and is retained when the switch restarts.

Because all ports are associated with at least one VLAN, the switch acquires the
VLAN ID for the address from the ports that you select on the forwarding map. A
static address in one VLAN must be a static address in other VLANs. A packet
with a static address that arrives on a VLAN where it has not been statically
entered is flooded to all ports and not learned.

Adding Static Addresses

Chapter 3 Configuring Ethernet Switching

Step 1
Step 2

Step 3
Step 4

Beginning in privileged EXEC mode, follow these steps to add a static address:

Task Command

Enter global configuration mode.
Enter the static MAC address, the interface,

and the VLAN ID of those ports.

Return to privileged EXEC mode.
Verify your entry.

configure terminal

mac-address-table static

hw-addr

[vlan] vlan-id

end

show mac-address-table static

[interface] interface

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-22

OL-2031-02

Chapter 3 Configuring Ethernet Switching

Removing Static Addresses

Beginning in privileged EXEC mode, follow these steps to remove a static
address:

Task Command

Managing the Catalyst 4224 Access Gateway Switch

Step 1
Step 2

Step 3
Step 4

Enter global configuration mode.
Enter the static MAC address, the interface,

and the VLAN ID of the port to be removed

Return to privileged EXEC mode.
Verify your entry.

configure terminal

no mac-address-table static

hw-addr

[vlan] vlan-id

end

show mac-address-table static

[interface] interface

You can remove all secure addresses by using the clear mac-address-table static
command in privileged EXEC mode.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-23

Managing the Catalyst 4224 Access Gateway Switch

Chapter 3 Configuring Ethernet Switching

Catalyst 4224 Access Gateway Switch Software Configuration Guide

3-24

OL-2031-02

CHAPTER

4

Configuring the Data Interfaces

This section describes how to configure the data interfaces on the Catalyst 4224
To configure a data interface, you must use configuration mode. In this mode, you
enter Cisco IOS command-line interface (CLI) commands at the gateway prompt.

This section contains the following topics:

• Configuring the Host Name and Password, page 4-2

• Configuring the Fast Ethernet Interface, page 4-4

• Configuring Asynchronous/Synchronous Serial Interfaces, page 4-6

• Configuring ISDN BRI Interfaces, page 4-9

OL-2031-02

• Configuring T1 and E1 Interfaces, page 4-12

• Checking the Interface Configuration, page 4-18

• Saving Configuration Changes, page 4-19

This section describes some of the most commonly used configuration
procedures. For advanced configuration topics, refer to the Cisco IOS
configuration guide and command reference publications. These publications are
available on the Documentation CD-ROM or on Cisco.com. You can also order
printed copies separately.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-1

Chapter 4 Configuring the Data Interfaces

Configuring the Host Name and Password

Configuring the Host Name and Password

One of your first configuration tasks is to configure the host name and set an
encrypted password. Configuring a host name allows you to distinguish multiple
Catalyst 4224s. Setting an encrypted password allows you to prevent
unauthorized configuration changes.

To configure the host name and password, perform these tasks:

Task Command

Step 1

Step 2

Step 3

Step 4

Enter enable mode.
Enter the password.
You know you have entered enable mode

when the prompt changes to

gateway#.

Enter global configuration mode.

You know you have entered global
configuration mode when the prompt changes
to

gateway(config)#.

Provide the Catalyst 4224 a meaningful
name. Substitute your host name for gwy1.

Substitute your enable secret password for

guessme.

This password gives you access to privileged
EXEC mode. When you type enable at the
EXEC prompt (

gateway> ), you must enter

the enable secret password to gain access to
configuration mode.

gateway> enable

Password: <password>

gateway#

gateway# configure terminal

Enter configuration commands, one per
line. End with Ctrl-Z.

gateway(config)#

gateway(config)# hostname gwy1

gwy1(config)#

gwy1(config)# enable secret guessme

Step 5

Enter line configuration mode to configure
the console port. When you enter line
configuration mode, the prompt changes to

gwy1(config-line)#.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-2

gwy1(config)# line con 0

gwy1(config-line)#

OL-2031-02

Chapter 4 Configuring the Data Interfaces

Task Command

Configuring the Host Name and Password

Step 6

Step 7

Enter exec-timeout 0 0 to prevent the
Catalyst 4224’s EXEC facility from timing
out if you do not type any information on the
console screen for an extended period.

Exit to global configuration mode.

To verify that you configured the correct host name and password, follow these
steps:

Step 1 Enter the show config command:

gwy1# show config

Using 1888 out of 126968 bytes
!
version XX.X
.
.
.
!
hostname gwy1
!
enable secret 5 $1$60L4$X2JYOwoDc0.kqa1loO/w8/
.
.
.

gwy1(config-line)# exec-timeout 0 0

gwy1(config-line)# exit

gwy1(config)#

Check the host name and encrypted password displayed near the top of the
command output.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-3

Configuring the Fast Ethernet Interface

Step 2 Exit global configuration mode and attempt to reenter it using the new enable

password:

gwy1# exit
.
.
.
gwy1 con0 is now available
Press RETURN to get started.

gwy1> enable
Password: guessme
gwy1#

Tip If you are having trouble, ensure that the Caps Lock function is off; passwords are

case sensitive.

Chapter 4 Configuring the Data Interfaces

Configuring the Fast Ethernet Interface

This section describes how to configure the Fast Ethernet interface on the
Catalyst 4224.

Timesaver Before you begin, disconnect all WAN cables from the Catalyst 4224 to prevent

it from running the AutoInstall process. The Catalyst 4224 attempts to run
AutoInstall if there is a WAN connection on both ends and the Catalyst 4224 does
not have a valid configuration file stored in nonvolatile random-access memory
(NVRAM). The Catalyst 4224 can take several minutes to determine that
AutoInstall is not connected to a remote TCP/IP host.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-4

OL-2031-02

Chapter 4 Configuring the Data Interfaces

To configure the Fast Ethernet interface, follow these steps:

Task Command

Configuring the Fast Ethernet Interface

Step 1

Step 2

Step 3

Step 4

Step 5

Step 6

Enter enable mode.
Enter the password.
You know you have entered enable mode when the prompt

changes to

gateway#.

Enter global configuration mode.

You know you have entered global configuration mode
when the prompt changes to

gateway(config)#.

Enable routing protocols as required for your global
configuration.

Enter interface configuration mode.
You know you have entered interface configuration mode

when the prompt changes to

gateway(config-if)#.

Assign an IP address and subnet mask to the interface.

Exit to global configuration mode.

gateway> enable

Password: <password>

gateway#

gateway# configure terminal

Enter configuration
commands, one per line. End
with Ctrl-Z.

gateway(config)#

gateway(config)# ip routing

gateway(config)# interface

fastethernet 0/0

gateway(config-if)#

gateway(config-if)# ip

address 172.16.74.3

255.255.255.0

gateway(config-if)# exit

Step 7

OL-2031-02

If your Catalyst 4224 has more than one Fast Ethernet
interface that you need to configure, repeat Step 4 through
Step 6.

When you finish configuring interfaces, return to enable
mode.

You know you have entered enable mode when the prompt
changes to

gateway#.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

gateway(config)# Ctrl-Z

gateway#

4-5

Chapter 4 Configuring the Data Interfaces

Configuring Asynchronous/Synchronous Serial Interfaces

Configuring Asynchronous/Synchronous Serial
Interfaces

This section describes how to configure the serial interfaces on your
asynchronous/synchronous serial WIC.

Note The asynchronous/synchronous serial WIC supports synchronous

mode only. At this time, asynchronous mode is not supported.

Timesaver Before you begin, disconnect all WAN cables from the Catalyst 4224 to keep it

from running the AutoInstall process. The Catalyst 4224 attempts to run
AutoInstall if there is a WAN connection on both ends and the Catalyst 4224 does
not have a valid configuration file stored in NVRAM. The Catalyst 4224 can take
several minutes to determine that AutoInstall is not connected to a remote TCP/IP
host.

Step 1

Step 2

Step 3

To configure the serial interfaces, perform these steps:

Task Command

Enter enable mode.
Enter the password.

gateway> enable

Password: <password>

gateway#

You know you have entered enable mode when the prompt
changes to

Enter global configuration mode.

You know you have entered global configuration mode
when the prompt changes to

Enable routing protocols as required for your global

gateway#.

gateway(config)#.

gateway# configure terminal

Enter configuration
commands, one per line. End
with Ctrl-Z.

gateway(config)#

gateway(config)# ip routing

configuration.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-6

OL-2031-02

Chapter 4 Configuring the Data Interfaces

Task Command

Configuring Asynchronous/Synchronous Serial Interfaces

Step 4

Step 5

Step 6

Step 7

Enter the interface configuration mode.
You know you have entered interface configuration mode

when the prompt changes to

gateway(config-if)#.

Assign the IP address and subnet mask to the interface.

Note All serial ports are initially configured as

synchronous.

To use a port in Data Communication Equipment (DCE)
mode, connect a DCE cable and set the internal transmit
clock signal (TXC) speed in bits per second. (For ports used
in Data Terminal Equipment (DTE) mode, the
Catalyst 4224 automatically uses the external timing
signal.)

When a port is operating in DCE mode, the default
operation is for the DCE to send serial clock transmit (SCT)
and serial clock receive (SCR) clock signals to the DTE, and
for the DTE to return an serial clock transmit external
(SCTE) signal to the DCE.

If the DTE does not return an SCTE signal, enter this
command to configure the DCE port to use its own clock
signal.

gateway(config)# interface
serial 1/0

gateway(config-if)#

gateway(config-if)# ip

address 172.16.74.1

255.255.255.0

gateway(config-if)# clock
rate 7200

gateway(config-if)#

dce-terminal-timing-enable

Step 8

Step 9

OL-2031-02

A Catalyst 4224 that uses long cables might experience high
error rates when operating at higher transmission speeds,
because the clock and data signals can shift out of phase.

If a DCE port is reporting a high number of error packets,
you can often correct the shift by inverting the clock using
this command.

All serial interfaces support both nonreturn to zero (NRZ)
and nonreturn to zero inverted (NRZI) formats. NRZ is the
default; NRZI is commonly used with EIA/TIA-232
connections in IBM environments. To enable NRZI
encoding on an interface, enter this command.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

gateway(config-if)#

invert-txcclock

gateway(config-if)#

nrzi-encoding

4-7

Chapter 4 Configuring the Data Interfaces

Configuring Asynchronous/Synchronous Serial Interfaces

Task Command

Step 10

Exit back to global configuration mode.

gateway(config-if)# exit

If your Catalyst 4224 has more that one serial interface that
you need to configure, repeat Step 4 through Step 9.

Step 11

When you finish configuring the interface, return to enable
mode.

gateway(config)# Ctrl-z

gateway#

Table 4-1 lists the half-duplex timer commands.

Table 4-1 Half-duplex timer commands

Timer Syntax Default Setting (Milliseconds)

CTS delay

1

CTS drop timeout

2

DCD

drop delay

DCD transmission start delay

3

RTS

drop delay

half-duplex timer cts-delay

half-duplex timer
cts-drop-timeout

half-duplex timer
dcd-drop-delay

half-duplex timer
dcd-txstart-delay

half-duplex timer
rts-drop-delay

100
5000

100

100

100

RTS timeout

Transmit delay

1. CTS = Clear To Send.

2. DCD = Data Carrier Detect

3. RTS = Request To Send.

The following clock rate settings are for two-port asynchronous/synchronous
serial WICs:

• 1200 bps

• 2400 bps

• 4800 bps

• 9600 bps

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-8

half-duplex timer
rts-timeout

half-duplex timer
transmit-delay

2000

0

OL-2031-02

Chapter 4 Configuring the Data Interfaces

• 14400 bps

• 19200 bps

• 28800 bps

• 32000 bps

• 38400 bps

• 56000 bps

• 57600 bps

• 64000 bps

• 72000 bps

• 115200 bps

• 125000 bps

Configuring ISDN BRI Interfaces

• 128000 bps

Configuring ISDN BRI Interfaces

This section describes how to configure the interfaces on the basic rate interface
(BRI) card of your Catalyst 4224.

Note Before using a Catalyst 4224 with an ISDN BRI interface, you must order a

correctly configured ISDN BRI line from your local telecommunications
service provider. ISDN BRI provisioning refers to the types of services
provided by the ISDN BRI line. Although provisioning is performed by your
ISDN BRI service provider, you must tell the provider what you want.

Timesaver Before you begin, disconnect all WAN cables from the Catalyst 4224 to keep

it from running the AutoInstall process. The Catalyst 4224 attempts to run
AutoInstall if there is a WAN connection on both ends and the Catalyst 4224
does not have a valid configuration file stored in NVRAM. The Catalyst 4224
can take several minutes to determine that AutoInstall is not connected to a
remote TCP/IP host.

OL-2031-02

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-9

Chapter 4 Configuring the Data Interfaces

Configuring ISDN BRI Interfaces

To configure ISDN BRI interfaces, perform the following steps:

Task Command

Step 1

Step 2

Step 3

Step 4

Step 5

Enter enable mode.
Enter the password.
You know you have entered enable mode when the prompt

changes to

gateway#.

Enter global configuration mode.

You know you have entered global configuration mode
when the prompt changes to

gateway(config)#.

Enter an ISDN switch type. See Table 4-2 for a list of ISDN
switch types.

Note Switch types configured in interface

configuration mode override this setting for the
configured interface.

Enable routing protocols as required for your global
configuration.

Enter the interface configuration mode.
You know you have entered interface configuration mode

when the prompt changes to

gateway(config-if)#.

gateway> enable

Password:

gateway#

gateway# configure terminal

Enter configuration
commands, one per line. End
with Ctrl-Z.

gateway(config)#

gateway(config)# isdn

switch-type switch-type

gateway(config)# ip routing

gateway(config)# interface

bri 2/0

gateway(config-if)#

<password>

Step 6

Enable encapsulation. For data, you need to change the
encapsulation to hdlc, ppp, or frame-relay. The default is
voice.

Step 7

Assign the IP address and subnet mask to the interface.

If you are configuring this interface for voice, enter the
switch type instead of an IP address.

Step 8

Exit back to global configuration mode.
If your Catalyst 4224 has more than one BRI interface that

you need to configure, repeat Step 5 through Step 7.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-10

gateway(config)# encaps
encaps-type

gateway(config-if)# ip

address 172.16.74.2

255.255.255.0

gateway(config-if)# isdn
switch-type basic-5ess

gateway(config-if)# exit

OL-2031-02

Chapter 4 Configuring the Data Interfaces

Task Command

Configuring ISDN BRI Interfaces

Step 9

Step 10

By default, the Catalyst 4224 allocates 25 percent of
DRAM to shared memory (used for data transmitted (or
received) by WAN interface cards). Specifying

memory-size iomem 40 increases shared memory from 25

percent to 40 percent.
When you finish configuring the interface, return to enable

mode.

Table 4-2 lists the supported ISDN switch types by country.

Table 4-2 ISDN Switch Types

ISDN Switch

Region

Type Description

Australia basic-ts013 Australian TS013 switches
Europe basic-1tr6 German 1TR6 ISDN switches

basic-nwnet3 Norwegian NET3 ISDN switches (phase 1)
basic-net3 NET3 ISDN switches (UK and others)

gateway(config)#

memory-size iomem 40

gateway(config)# Ctrl-z

gateway#

OL-2031-02

vn2 French VN2 ISDN switches

vn3 French VN3 ISDN switches
Japan ntt Japanese NTT ISDN switches
New Zealand basic-nznet3 New Zealand NET3 switches
North

America

basic-5ess AT&T basic rate switches

basic-dms100 NT DMS-100 basic rate switches

basic-nil1 National ISDN-1 switches

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-11

Configuring T1 and E1 Interfaces

Configuring T1 and E1 Interfaces

This section describes how to configure a T1/E1 multiflex trunk interface on your
Catalyst 4224. It describes a basic configuration, including how to enable the
interface and to specify IP routing. Depending on your own requirements and the
protocols you plan to route, you might also need to enter other configuration
commands.

Timesaver Before you begin, disconnect all WAN cables from the Catalyst 4224 to keep

it from running the AutoInstall process. The Catalyst 4224 attempts to run
AutoInstall if there is a WAN connection on both ends and the Catalyst 4224
does not have a valid configuration file stored in NVRAM. The Catalyst 4224
can take several minutes to determine that AutoInstall is not connected to a
remote TCP/IP host.

Chapter 4 Configuring the Data Interfaces

Configuring T1 Interfaces

To configure a new T1, Channelized T1 (CT1)/PRI, or CT1/PRI-channel status
unit (CSU) interface, or to change the configuration of an existing interface,
perform these steps:

Task Command

Step 1

Step 2

Step 3

Enter enable mode.
Enter the password.
You know you have entered enable mode when the prompt

changes to

gateway#.

Enter global configuration mode.

You know you have entered global configuration mode
when the prompt changes to

gateway(config)#.

Enable routing protocols as required for your global
configuration.

gateway> enable

Password:

gateway#

gateway# configure terminal

Enter configuration commands,
one per line. End with Ctrl-Z.

gateway(config)#

gateway(config)# ip routing

<password>

Step 4

Select frame clock.

Catalyst 4224 Access Gateway Switch Software Configuration Guide

4-12

gateway(config)# frame-clock

-select

OL-2031-02