Motorola 68230 - Vanguard 300 DSU/CSU, Vanguard 300, Vanguard 305 Operator's Manual

Vanguard 300/305 Operator's Guide

Notice

1995 Motorola Inc.
20 Cabot Boulevard
Mansfield, Massachusetts 02048
[phone]
All rights reserved
Printed in U.S.A.

Restricted Rights Notification for U.S. Government Users

The software (including firmware) addressed in this manual is provided to the
U.S. Government under agreement which grants the government the minimum
"restricted rights" in the software, as defined in the Federal Acquisition
Regulation (FAR) or the Defense Federal Acquisition Regulation Supp lement
(DFARS), whichever is applicable.

If the software is procured for use by the Department of Defense, the following
legend applies:

Restricted Rights Legend

Use, duplication, or disclosure by the Government is subject to restrictions as set
forth in s ubparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013.

If the software is procured for use by any U.S. Government entity other than the
Department of Defense, the following notice applies:

Notice

Notwithstanding any other lease or license agreement that may pertain to, or
accompany the delivery of, this computer software, the rights of the Government
regarding its use, reproduction, and disclosure as set forth in FAR 52.227-19(C).

Unpublished - rights reserved under the copyright laws of the United States.

Proprietary Material

Information and software in this document are proprietary to Motorola Inc. (or its
Suppliers) and without the express prior permission of an officer of Motorola Inc.,
may not be copied, reproduced, disclosed to others, published, or used, in whole
or in part, for any purpose other than that for which it is being made available.
Use of software described in this document is subject to the terms and conditions
of the Motorola Software License Agreement.

This document is for information purposes only and is subject to change without
notice.

Vanguard 300/305 Radio Frequency Interference Regulations

This equipment has been tested and found to comply with the limits for a Class B
digital device, pursuant to Part 15 of the FCC Rules, CISPR 22 and EN 55022.
These limits are designed to provide reasonable protection against interference in
a residential installation. This equipment generates, uses, and can radiate radio
frequency energy and, if not installed and used in accordance with the
instructions, may cause harmful interference to radio communications. However,
there is no guarantee that interference will not occur in a particular installation. If
this equipment does cause harmful interference to radio or television reception,
which can be determined by turning the equipment off and on, the user is
encouraged to try to correct the interference by one or more of the following
measures:

• Reorient or relocate the receiving antenna.

• Increase the separation between the equipment and receiver.

• Connect the equipment into an outlet on a circuit different from that to

which the receiver is connected.

• Consult the dealer or an experienced radio/TV technician to help.

Changes or modifications not expressly approved by Motorola could void the
user's authority to operate the equipment.

This Class B digital apparatus meets all requirements of the Canadian
Interference-Causing Equipment Regulations.

This product was FCC certified under test conditions that included use of shielded
data terminal equipment cables. Use of different cables will invalidate FCC
certification and increase the risk of causing interference to radio and TV
reception.

You can obtain the proper cables from Motorola.

Writer: Donna McLean
Project Editor: Susan L. Roswit
Publication Specialist: Paul Tavares
Illustrator: Tim Kinch
Manual is current for Release 4.50 of the Vanguard 300 operating software, and
Release 4.49 of the Vanguard 305 operating software.

To comment on this manual, please send email to: [e-mail] or use the
Customer Response Card located in this manual.

Internet Information

Additional company and product information can be found on our Internet Web
page at:

Part No.: 09965, Rev B
Publication Code: RC
First Printing: Aug. 1995

http://www.mot.com/MIMS/ISG/

Introduction

This manual describes features, hardware, specifications, and applications for the
Motorola Vanguard 300 and Vanguard 305 Frame Relay Access Devices
(FRADs).

For information on operating system software and configuration see the 6500
Series Documentation Kit, which includes the 6500 Series Introduction Manual
and the 6500 Series Configuration and Administration Manual.

Audience

This manual is intended for operators of the Motorola Vanguard 300/305 FRAD.

Software Revision Level

The Vanguard 300 runs Release 4.33 or higher releases of operating software. The
Vanguard 305 runs Release 4.49 or higher.

Special Notices

The following notices emphasize certain information in the manual. Each serves a
special purpose and is displayed in the format shown:

About This Manual

IMPORTANT: Important is used to emphasize any significant procedural information.

Caution provides you with information that, if not followed, can result in
damage to software, hardware, or data.

Warning is the most serious notice, indicating that you can be physically hurt.

How to Use This Manual

The following table describes the contents of this guide.

This chapter... Describes

Chapter 1 Vanguard 300/305 hardware and software features, and FCC

Chapter 2 Setting up a Vanguard 300/305, including site preparation,

Chapter 3 Vanguard 300/305 applications and configuration

Chapter 4 Maintaining the Vanguard 300/305, including replacing

Part 68 guidelines and Telephone Company procedures.

how to unpack the unit, installation procedures, powerup and
diagnostic procedures, and how to connect to the Control
Terminal Port

information, including step-by-step configuration sequences

option cards and troubleshooting information

Related Documentation

The following documentation is not provided with the Motorola Vanguard
300/305; it can be ordered separately. You should familiarize yourself with the
6500 Series documentation before you use the Vanguard Series.

To acquire any of these sets of documentation, refer to the following product
codes:

Product Code Documentation Kit Includes:

17460 6500 Series Documentation

Kit

The printed documentation
set including:

6500 Series Introduction
Manual (Part No. 09871,
Rev D)

6500 Series Configuration
and Administration Manual
(Part No. 09873, Rev D)

6500 Installation Manual
(Part No. 09872, Rev E)

6520 Installation Manual
(Part No. 09901, Rev C)

17461 Documentation Change

Notices

Documentation for all
software releases since the
last printing of the main
documentation set.

17313 Multi-Product CD-ROM All 6500 Series

documentation and some
Vanguard user
documentation, as was
available at the time of
release.

6500 Series documentation is prepared using FrameMaker document publishing
software.

Additional Related Documentation

The following documents contain information related to the installation and
operation of 65xx and Vanguard platforms:

• The 6500 Series Options and Protocols Binder (Part No. 09950)

Vanguard Operator's Guides

• Vanguard 100 Operator's Guide (Part No. 09962, Rev A)

• Vanguard 200 Operator's Guide (Part No. 09968, Rev A)

• Vanguard 300/305 Operator's Guide (Part No. 09965, Rev B)

Software Download Guides

• 6520 Software Download Guide (Part No. 09901-6, Rev A)

• 6500 PLUS Software Download Guide (Part No. 09872-2, Rev A)

• Vanguard 100 Software Download Guide (Part No. 09962-2, Rev A)

• Vanguard 200 Software Download Guide (Part No. 09968-1, Rev A)

• Vanguard 300/305 Software Download Guide (Part No. 09965-1, Rev B)

Trademarks

The following are trademarks or registered trademarks of their respective
companies or organizations.

DECconnect Digital Equipment Corporation

Overview

The Vanguard 300/305

The Motorola Vanguard 300/305 Frame Relay Access Device (FRAD) provides
serial devices with LAN Ethernet (Vanguard 300) or Token Ring (Vanguard 305)
access into public or private Frame Relay networks.

The FLASH-based Vanguard 300/305 is available in FRAD, mono FRAD, or duo
FRAD configurations with either two or three serial ports and an abundant list of
protocol choices. You can order the base unit with an integral DSU and a software
application package, making this low-cost FRAD an economical choice for
connecting remote LAN sites with both LAN and Serial traffic to public Frame
Relay services.

You can also configure extra serial ports on the mono and duo FRAD to provide a
backup link to the Frame Relay network port. Or, you can connect them to an
external analog dial modem, SW56 DSU or ISDN BRI TA, to provide an
alternate path in case of network failure.

Example of the Vanguard 300/305

The Vanguard 300/305 is available either with or without an integral DSU
daughtercard or DIM Site daughtercard in a desktop-size standalone enclosure, as
shown in Figure 1-1.

About the Vanguard 300/305

Figure 1-1. The Vanguard 300 and Vanguard 305

Features

Introduction

This section describes Vanguard 300/305 hardware configurations and standard
features.

Configurations Options

The Vanguard 300/305 is available in the following hardware configurations.

This configuration: Offers...

300 Ethernet FRAD Ethernet port, V.24 port, CTP port.
300 Ethernet FRAD with

DSU
300 Ethernet mono

FRAD

Ethernet port, DSU daughtercard in Port 1, CTP
port.

Ethernet port, serial port with a choice of DIM port
interface (V.24, V.35, V.36, or V.11) in Port 2, CTP
port.

300 Ethernet mono
FRAD with DSU

Ethernet port, V.24 port, DSU daughtercard in Port
1, CTP port.

300 Ethernet duo FRAD Ethernet port, V.24 port, DIM S ite daughtercard in

Port 1 with choice of DIM port interface (V.24,
V.35, V.36, or V.11), CTP port.

300 Ethernet duo FRAD
with DSU

Ethernet port, V.24 port, DSU daughtercard in Port
1, serial port with a choice of DIM port interface

(V.24, V.35, V.36, or V.11) in Port 2, CTP port.
305 Token Ring FRAD Token Ring port, V.24 port, CTP port.
305 Token Ring FRAD

with DSU
305 Token Ring mono

FRAD

Token Ring port, DSU daughtercard in Port 1, CTP

port.

Token Ring port, serial port with a choice of DIM

port interface (V.24, V.35, V.36, or V.11) in Port 2,

CTP port.
305 Token Ring mono

FRAD with DSU
305 Token Ring duo

FRAD

305 Token Ring duo
FRAD with DSU

Token Ring port, V.24 port, DSU daughtercard in

Port 1, CTP port.

Token Ring port, V.24 port, DIM Site daughtercard

in Port 1 with a choice o f DIM port interface (V.24,

V.35, V.36, or V.11), CTP port.

Token Ring port, V.24 port, DSU daughtercard in

Port 1, serial port with a choice of DIM port

interface (V.24, V.35, V.36, or V.11) in Port 2, CTP

port.

Standard Features

The Vanguard 300/305 features 1, 2, or 3 port Serial FRAD functionality with
LAN access to Frame Relay networks.

All Vanguard 300/305 base units provide the following:

• Control Terminal Port (CTP) for configuration and management

• Dual link ability

• Optional DSU

• Optional ISDN Daughtercards

• Ethernet (Vanguard 300) or Token Ring (Vanguard 305) interface

• Frame Relay and X.25 service

• X.25 PAD support

• X.25 PAD support

• Multiprotocol support

• SNMP management

• Software download through Trivial File Transfer Protocol (TFTP)

• Fully compatible with 6500 PLUS and 6520.

• RFC 877 encapsulation

CTP Port

Port 3 on the Vanguard 300/305 can be used as a CTP for configuration,
reporting, and troubleshooting. You can default Port 3 for CTP access from the
front panel of the Vanguard. See "Connecting to the CTP" in Chapter 2 for more
details.

DSU Functionality

The DSU daughtercard functionality suits an extended range of 56 kbps point-to­point DDS1 interface that conforms to AT&T 62310 or ANSI T1E1.4/91-006.

The DSU is FCC Part 68 registered.
Diagnostic loopbacks from the telephone company are supported; local

diagnostics are activated from the CTP.

LAN Support

The Vanguard 300 features an onboard Ethernet interface that supports both
10BaseT and AUI. The factory default is AUI.

The Vanguard 305 features an onboard Token Ring interface. Support includes:

• 4 and 16 Mbps support

• Type 1 STP (DB-9)

• Type 3 UTP (RJ-45)

Frame Relay & X.25 Service

The Vanguard 300/305 provides serial devices with economical LAN access into
public or private Frame Relay WAN networks via Ethernet or Token Ring.
Because the Vanguard 300/305 also supports X.25, you can configure it as a PAD
if Frame Relay is not an immediate need. When Frame Relay service becomes
available, you can reconfigure the Vanguard 300/305 as a FRAD.

Multiprotocol Support

Support includes SDLC, Bisync, X.25, Async, IP/IPX, and Routing and Bridging,
as well as many other serial protocols.

Software Download

Trivial File Transfer Protocol (TFTP) provides software downloading for network
software and device configuration software.

RFC 877

RFC 877 encapsulation of IP datagrams over an X.25 network allows for
interoperability of Front End Processors (FEPs) that support X.25 and IP traffic as
well as router vendors supporting RFC 877/1356.

Sample Applications

Figure 1-2 shows sample applications for the Vanguard 300/305.

Figure 1-2. Vanguard 300/305 Sample Applications

Hardware

Introduction

This section describes the Vanguard 300/305 hardware components.
See the Software Release Notice (SRN) accompanying your Vanguard product for

details on hardware platform bundles currently available.

Components

Vanguard 300/305 base units include the following components:

• A motherboard

• A power supply

• One V.24 port with DB25 connector

• Optional port for daughtercard (DIM Site or DSU)

• Optional DIM port on the motherboard

• One LAN port:

§ Vanguard 300: Ethernet with either 10BaseT or AUI interface

§ Vanguard 305: Token Ring with connectors for both shielded

(STP) and unshielded

• (UTP) cables

• One Async port used for control port:

§ Vanguard 300: DECconnect connector

§ Vanguard 305: RJ45 connector

• Two MB FLASH, four MB DRAM

See Figure 1-4 for a view of the Vanguard 300/305 rear panel.

Motherboard

The motherboard supports up to three serial interfaces.

Serial Ports

The Vanguard 300/305 is available with one or two serial ports, plus an optional
third port for a daughtercard option (DSU, V.35 DIM site card, etc.). You can also
use the optional port for dial backup or as a second user port. See "Port
Characteristics" in this section for more details.

Vanguard 300 Ethernet Port

On the Vanguard 300, one port is a LAN port configured for Ethernet AUI and
10BaseT interfaces. Strapping is required during installation to configure the unit
for AUI or 10BaseT operation. The default configuration, shipped from the
factory, is 10BaseT.

Vanguard 305 Token Ring Port

On the Vanguard 305, one port is a LAN port configured for a Token Ring
connection. There are connectors for both shielded (STP) and unshielded (UTP)
cables, but only one cable can be connected at any time. No strapping is required
during installation to configure the unit as the port will automatically configure
for the connected interface.

The following table describes the port characteristics for the Vanguard 300/305.

Port
No.

1

Connector Interface Default Speed DTE/DCE

DB25
connector for
V.24, V.35,
V.36, V.11

RJ48S
connector for
DSU

DIM Site
Daughtercard

DSU
Daughtercard

Frame
Relay

See Port 2
for DIM
speeds

DSU Sync
speed is 56
kbps

• DIM Card

-Selectable

• DCE

• DSU -

NA

2 DB25

connector
Supported

DIMs include
V.11, V.35,
V.24, V.36,
Integral DSU

DIM Frame

Relay

• Maximum

async speed
is 115.2
kbps

• Maximum

sync speed
is 384 kbps

Selectable

with INT
clocks or
1536 to
2048 kbps
with EXT
clocks

3 DB25 V.24 Async

PAD

4 Async port Control

CTP Maximum
Terminal Port
(CTP) or serial
port (some
limitations).

LAN Vanguard 300:

Ethernet

Support
includes:

• 10BaseT

• AUI

Ethernet 10 Mbps N/A

Either one of
the interfaces
can be
connected and
operated, but
not
simultaneously.

• Maximum

async speed
is DCE

115.2 kbps

• Maximum

synch speed
is 80 kbps

async speed
is 19.2 kbps

DCE

Memory

Two Mbytes of FLASH memory and four Mbytes of DRAM reside on the
motherboard. An optional SIMM can be used to expand DRAM to 8 Mbytes.

Vanguard 305:

Token Ring

Support
includes:

• STP

• UTP

Either one of
the interfaces
can be
connected and
operated, but
not
simultaneously.

Token

Ring

4 or 16
Mbps
(Default is 4
Mbps)

N/A

Example of the Vanguard 300/305 Front Panel

Figure 1-3 shows the front panel of the Vanguard 300/305.

Figure 1-3. Vanguard 300 /305 Front Panel

Front Panel DIP Switch Definitions

The six DIP switches on the front panel are defined as follows:

Switch
Position

Switch Name Down Up

1 Port 2 RI/TM Pin 22 is input on

2 Port 2 MB Pin 25 is input on

3 Port 3 RI/TM Pin 22 is input on

4 Port 3 ->CTP Normal operation Configure Port 3 as PAD

5 DIAGNOSTICS Normal operation Reserved.
6 DEFAULT

NODE

Pin 22 is output on Port 2.

Port 2.

Pin 25 is output on Port 2.

Port 2.

Pin 22 is output on Port 3.

Port 3.

port.

Normal operation Resets all configurable

parameters to default values.

Example of the Vanguard 300 Back Panel

The Vanguard 300 back panel features the following connectors, as shown in
Figure 1-4.

Figure 1-4. Vanguard 300 Back Panel

Example of the Vanguard 305 Back Panel

The Vanguard 305 back panel features the following connectors, as shown in
Figure 1-5.

Figure 1-5. Vanguard 305 Back Panel

Cabling

All cables for the Vanguard 300/305 are the same cables used for the 6500 Series.
For example, DB25 cables, the 6509 EIM telco cable, and 6520 Ethernet cables
currently available for the 6500 Series can be used with the Vanguard 300/305.

The DSU telco cable is provided with the DSU daughtercard. Port 4 requires a
DECconnect interface cable on the Vanguard 300, and a straight through 8­conductor RJ45 cable (e.g. Inmac P/N Q0462-1 or Black Box P/N RM-EL08MS-

07) for the Vanguard 305. See "Vanguard 300 Cabling Pinouts" and "Vanguard
300 Cabling Pinouts" in the "Connecting to the CTP" section in Chapter 2 for
information about the pinouts of the RJ45 to DB25 adapter.

Software

Introduction

This section describes the operating software for the Vanguard 300/305.

Operating Software

The operating software is compressed in FLASH and loaded into RAM for
operation. There are a variety of operating software bundles available for the
Vanguard family. See the Software Release Notice accompanying your Vanguard
product for feature information on the operating software for the Vanguard
300/305, and see the Vanguard 300/305 Software Download Guide (Part No.
09965-1, Rev B) for information on installing the operating software.

FCC Part 68 and Telephone Company Procedures and Requirements
for DSU

Introduction

Before the Motorola Vanguard 300/305 can be connected to the network, you
must:

• Provide the local telephone company with the equipment's registration

number

• Order the proper connections

This information is for North America only.

How to Order Connections

To order the proper connections, provide the telephone company with the
following information:

• Interface type

• Required USOC jack connector number

• Service code

• Facility interface codes

Interface Type USOC Jack

Connector

56-kbps digital interface RJ48S 6.0F 04DU5-56

Troubleshooting Your Connection

If any of your equipment is not operating correctly, immediately remove it from
the telephone line before it harms your network. If the telephone company notes
the problem, they may temporarily disconnect your service. They will notify you
in advance of the disconnection, when possible.

If advance notice is not feasible, you will be notified as soon as possible. When
you are notified, you will be given the chance to correct the problem and be
informed of your right to file a complaint with the FCC.

Customer-Provided Telephone Equipment

FCC regulations and telephone company procedures prohibit connection of
customer-provided equipment to telephone company-provided coin service
(central office-implemented systems). Connection to party lines is subject to state
tariffs.

Occasionally, the telephone company may make changes in their equipment,
operations, or procedures. If these changes affect your equipment or service, the
telephone company will provide written notice so you can make the necessary
changes to maintain uninterrupted service.

Service Code Facility Interface

Code

Contact your telephone company if you have any questions about your telephone
line.

In so me circumstances, the telephone company may ask you for information
about your equipment that is connected to the telephone line. Within the United
States (at the request of the telephone company), you should provide your
equipment's FCC registration numbe r. This number is located on the unit's label.

Setting Up the Vanguard 300/305

Overview

Introduction

This chapter describes site preparation, unpacking, and installation for the
Vanguard 300/305.

Preparing a Site

How to Choose a Site for the Vanguard 300/305

Choose a site that is within an appropriate distance of a power source. The
selected site should be free of accumulated dust and environmental extremes.
Depending on your application and the country in which the Vanguard 300/305
will operate, the power source must be a grounded 100 to 240 VAC outlet.

Warnings and Cautions

The following special notices apply to all equipment handling procedures in this
operator's guide.

Only trained, qualified technicians should perform procedures outlined in this
guide.

Motorola Vanguard 300/305 daughtercards and DIMs are sensitive to static
discharge, which can damage components. Trained, qualified technicians will
use proper handling and grounding precautions when handling a Motorola
Vanguard 300/305 daughtercard or DI M.

Ports capable of connecting to ports on other apparatus are defined as Safety
Extra Low Voltage (SELV). To conform with EN60950, ensure that these
ports are only connected to ports of the same type on other apparatus.

Avertissement

Les ports qui sont susceptibles d'etre connectes a des equipements sont
designes comme TBTS. Pour garantir la conformite a la norme EN 60950,
n'interconnecte ces ports qu'avec des ports du meme type sur des autres
materiels.

Warnung

Anschlusse, die mit anderen Geraten verbinde t werden konnen, sind als SELV
beschrieben. Um Konformitat mit EN 60950 zu versichern, sichern Sie es, daß
diese Anschlusse nur mit den des selben Type auf anderen Geraten verbindet
werden.

Cable Clearance/Air Circulation

To avoid overheating the unit's circuitry, you should never place anything on top
of the unit, within 1 inch (2.5 cm) of the ventilation slots on the front panel, or
within 12 inches (30.5 cm) of the back of the unit. Allow at least 12 inches (30.5
cm) in back of the unit for interfacing cable clearance and air circulation, as
shown in Figure 2-1.

Figure 2-1. Proper cable and air clearance

Unpacking

What You Should Receive

The Vanguard 300/305 is packaged in shock-absorbent packing material. Inside
your shipping carton, you should find the following items:

• Vanguard 300/305 base unit

• Operator's Guide

• Telco cable for DSU (if ordered)

How to Unpack the Vanguard 300/305

Follow these steps to unpack the Vanguard 300/305.

Step Action
1

Check the shipping carton and its contents for damage.

2
3

Open the shipping carton from the top as shown in Figure 2-2.
Lift the Vanguard 300/305 from its shipping carton and remove the

packing material.

Vanguard 300/305 components are installed in the base unit before it is shipped
from the factory. In add ition to the base unit and accompanying components, the
shipping carton may include a sleeve containing the power cord if you ordered
one.

Example of Unpacking Vanguard 300/305

Figure 2-2 shows how to properly unpack the Vanguard 300/305 from its shipping
carton.

Figure 2-2. Unpacking the Motorola Vanguard 300/305

In Case of Damage or Missing Parts

If the equipment is damaged, contact the shipper. If you have additional concerns
about damaged or missing parts, contact your nearest Motorola ISG
representative.

In the United States, contact: Motorola ISG, Customer Administration, 20 Cabot
Blvd., Mansfield, MA 02048-1193, [phone], Extension 4745.

Outside the United States, contact the nearest Motorola ISG distributor.

Installing

Introduction

After you unpack the Vanguard 300/305, you can connect the cabling to complete
the installation.

All Motorola Vanguard 300/305 devices should be used in environments designed
for computers and electronic equipment. In areas susceptible to lightning, take
precautions to prevent damage to electronic equipment. Contact your telephone
company, or an electronic accessories vendor, for information on lightning
protection equipment. Customers experiencing problems caused by surges from
lightning have eliminated such proble ms by installing appropriate surge
suppressors on power and data lines connected to Motorola Vanguard 300/305
devices.

Control Terminal Port

You can use Port 4 to connect to an asynchronous device for Control Terminal
Port (CTP) access. The Vanguard 300/305 defaults this port to 9.6 kbps, 8 bits, no
parity.

For a Vanguard 300, a DECconnect compatible cable is required.
For a Vanguard 305, a straight-through 8-conductor RJ45 cable (e.g., Inmac P/N

Q0462-1 or Black Box P/N RM-EL08MS-07) is required for the Va nguard 305.
See "Vanguard 300 Cabling Pinouts" under "Connecting to the CTP" in Chapter 2
for information about the pinouts of the RJ45 to DB25 adapter.

DSU telco cable

The DSU telco cable is twisted-pair 19 to 26 AWG. This cable is shipped with the
DSU daughtercard.

Vanguard 300 Ferrite Bead

This section explains how to install a ferrite bead to filter out line disturbances, on
your Vanguard 300, which could cause radio interference to radio and TV
reception. The bead is required for the Control Terminal Port connection cable
(Port 4 on the Vanguard 300), and a bead is included with each Vanguard 300.

Follow the instructions below to ensure the ferrite bead is properly installed.

Installing the Ferrite Bead on the CTP Cable

Before beginning, ensure that you have the cable shipped with your Vanguard

300.

1) Make sure you have the correct cable (for connection to the CTP (Port 4)).

2) Snugly wrap the cable once completely around the bead (see Figure 2-3).

3) Set the cable into the bead cutouts.

4) Ensure that 1 to 1-1/2 inches of the cable protrude from the bead (on the end

you will install into the modem's rear panel connector).

5) Snap the bead closed.

6) Insert the cable into the appropriate connector (Port 4) on the rear of the

Vanguard 300 (with the ferrite bead close to the Vanguard 300 rear panel
connector).

Example Installation

Figure 2-3 shows how the ferrite bead is to be installed on the cable.

Connecting Cables

Follow these steps to cable the Vanguard 300/305.

Step Action
1

2
3
4

Connect the power cables
Install the Ferrite Bead on the CTP cable.
Connect the interface cables.
For a Vanguard 300, confirm strapping for either 10BaseT or AUI (see

the "Strapping the Ethernet Interface on a Vanguard 300" in Chapter 4).
For a Vanguard 305, no strapping is required as the connection type is
automatically sensed. The connection can be either STP or UTP, but only
one can be connected at a time.

5

Connect the power cord to a power source.

Figure 2-3. Installing a Ferrite Bead on the CTP Cable

Powerup Diagnostics

Introduction

This section describes diagnostics that run automatically when you power up the
Vanguard 300/305.

The front panel LEDs on the Vanguard 300/305 help you isolate problems at
powerup.

Powerup Sequence

The following table shows the normal powerup sequence when you turn on the
Vanguard 300/305.

Stage Action Comment
1

POWER light turns green. Vanguard is receiving power.

2

STATUS light blinks at a slow
rate.

3

TEST light turns red and blinks
five times.

4

STATUS light stays off for up to
10 seconds, then turns green.

5

PORT/DATA OUT lights come on
and go off in sequence.

Hardware Failure

If the TEST light turns on and remains on, one or more of the diagnostic tests
have failed, indicating there is a hardware problem. Contact Motorola ISG
Customer Support for possible repairs to your Vanguard 300/305.

Diagnostic Failure

If the TEST light does not blink at all, but the Status light is on, the diagnostic
software image is corrupted. Perform a download of the software option bundle.

Powerup Failure

Indicates software is being
downloaded from FLASH.

Diagnostics executes for 30
seconds.

The option bundle is initializing
your system configuration.

Port lights remain on, depending
on their configuration.

If the STATUS light blinks continuously, at a constant rate, the software bundle
in FLASH memory is corrupted. Perform a cold load of the software option
bundle. See the Vanguard 300/305 Software Download Guide (Part No. 09965-1,
Rev B) for more information.

Connecting to the CTP

Introduction

This section describ es how to connect to the CTP to configure your Vanguard
300/305.

CTP Port

There are 2 ways to access the CTP via direct connection:

1) If you connect a local terminal to Port 3 of the Vanguard, set the "CTP -> Port

3" switch in the on position, and reboot the node.

2) If you connect a local terminal to the Vanguard directly via an RJ45 cable to

Port 4. See the Vanguard 300/305 Operator's Guide (Part No. 09965, Rev B)
for the required pinout for the RJ45 CTP cable.

Any port can be used for CTP access, but only Por t 3 can be automatically
defaulted for CTP access. Port 3 is a DCE.

CTP Access Using ATPAD

For software image options that contain ATPAD instead of APAD, access to
the CTP is established with a default port type ATPAD. When the APAD
option in active, the prompt that appears is *. When ATPAD is active, the
prompt is OK.

To access the CTP via direct connection, type:

ATDS0 <CR>

Another way that you can access a local CTP, or to access a remote CTP from any
ATPAD port, type:

ATD <nodeaddress+98> <CR>

You can terminate the call to the CTP by selecting menu item 1 from the Main
menu, or by typing:

+++

When you get the OK prompt, type:

ATH <CR>

For more information on ATPAD, see the Documentation Change Notice for
Release 4.41 (Part No. 09871-49).

Steps to Connect to the CTP

Use the CTP for initial configuration, reporting, and troubleshooting. Follow
these steps to connect to the CTP.

Step Action Result
1

Connect a local PC or terminal to
the CTP port (9600 baud, 8 bit
characters, 1 stop bit, no parity) on
the Vanguard 300/305.

If the APAD option is in your
software image, the * prompt
appears. If the ATPAD option is in
your software image, the OK
prompt appears.

2

For APAD access, enter .ctp and
press Return to call the CTP. For
ATPAD access, enter ATDS0

3

At the Password prompt, press
Return.

See the 6500 Series Introduction Manual for additional information about the
CTP.

Steps to Default Port 3 CTP Configuration

Follow these steps to default Port 3 to 9600 kbps, 8N1.

Step Action
1

From the front panel of the unit, set the switch CTP -> Port 3to the Up
position.

2
3

Reset or power cycle the unit.
For APAD access, enter .ctp, or for ATPAD access, enter ATDS0, and

configure port parameters.

A call places a mnemonic call to
the CTP. A prompt appears to enter
the password.

The Main menu appears; logon to
the CTP is complete. The local
terminal functions as a control
terminal.

4

Set the CTP -> Port 3 switch to the Down position. Reset or power cycle
the unit.

5
6

Reset or power cycle the unit.
Reboot to verify that the configuration in configuration memory is

operating.

Refer to the 6500 Series Configuration and Administration Manual for additional
information about configuration.

Vanguard 300 CTP Cabling

On the Vanguard 300, Port 4 uses a 6-pin modified modular jack (RJ-11/MMJ) as
its connector (also referred to as a DECconnect connector). The cable can be a flat
ribbon telephone cable with a recommended length of 6 to 10 feet.

Vanguard 300 Cabling Pinouts

The pinout on the connector follows:

Pin Signal

1 DSR (output)
2 RxD (output)
3 Signal ground
4 Signal ground
5 TxD (input)
6 DTR (input)

Vanguard 305 CTP Cabling

On the Vanguard 305, Port 4 uses a straight-through 8-conductor RJ45 cable (e.g.,
Inmac P/N Q0462-1 or Black Box P/N RM-EL08MS-07. An RJ45 to DB25
(female) adapter (e.g., Inmac P/N Q0352-2 or Black Box P/N RQ-FA027) can be
constructed using the following pinout information:

Vanguard 305 Cabling Pinouts

RJ45 Pin No. Signal DB25 Pin No.

1 Not used 5
2 DTR (input) 6
3 TxD (input) 3
4 Signal ground 7
5 Signal ground 7
6 RxD (output) 2
7 DCD (output) 20
8 Not used 4

Overview

This chapter contains sample applications you can use as a reference to configure
your own Vanguard 300/305 applications.

The following configurations show critical parameters only. You should be
familiar with the 6500 Series configuration procedures before you configure a
Vanguard 300/305. Refer to the 6500 Series Introduction Manualand the 6500
Series Configuration and Administration Manual for more information.

CTP Menu Navigation

The following convention shows you how to navigate through CTP menus when
configuring parameters for the Vanguard using the sample procedures in this
section.

When you see... This means...

...select Configure Router -> Configure
IP -> Interfaces -> IP Interfaces
Configuration Table.

IPX Over Frame Relay

Configuring the Vanguard 300/305

...select these options, records or tables
from the CTP menus in the order they
appear in the documented procedure.

Introduction

The example shown in Figure 3-1 shows IPX running over Frame Relay using
RFC1294.

What You Need to Configure

The following table lists the items that you need to configure for nodes 100 and

200.

For Node 100... For Node 200...

LAN Connection Table LAN Connection Table
IPX Parameters and Interfaces IPX Parameters and Interfaces
LLC-SDLC FR Station Table Port records
Port Records Route Selection Table
Route Selection Table PVC Table
PVC Table Mnemonic Table
FRI Stations FRI Stations
Interfaces XDLC Port Stations
Interfaces

Example of IPX Over Frame Relay

Figure 3-1 shows the sample configuration for IPX over Frame Relay using
RFC1294.

Node 100 Configuration Sequence

Follow these steps to configure node 100 as shown in Figure 3-1.

Figure 3-1. IPX Over Frame Relay

Step Action Result/Description
1

From the Configure menu, select Port. Then
configure the following.

Prompt Enter Result/Description

The Port record
appears.

Port Number: 1 Identifies port

number 1 of this
node.

Port Type: FRI Identifies an FRI

interface port.

Clock
Source:

Int Identifies that the

clock will be
generated from this
port.

Clock Speed: 38400 Specifies the speed

of this port.

Highest
Station
Number:

2 Limits the number

of configurable
stations to 2.

Port Number: 3 Identifies port

number 3 of this
node.

Port Type: FRI Identifies an FRI

interface port.

Clock
Source:

Ext Identifies that the

clock will be
generated from this
port.

No. of
Stations:

1 Limits the number

of configurable
stations to 2.

Port Number: 5 Identifies port

Port Type:
Select TR on

the 305, and
ETH on the
300

number 5 of this
node.

ETH

Identifies an
Ethernet interface
port.

TR Identifies a Token

Ring interface port.

2

From the Configure menu, select Configure LAN
Connection -> LAN Connection Ta ble. Then
configure the following.

Prompt Enter Result/Description

Entry
Number:

1 References this

table record.

The LAN
Connection Table
appears.

3

LAN
Forwarder
Type:

ROUT Specifies that the

LAN connection is
to pass routed
traffic.

Router
Interface
Number:

Encapsulation
Type:

5 Identifies the router

interface number
being configured.

RFC1294 Specifies the type

of encapsulation
used for this LAN.

From the Configure menu, select Configure Network
Service -> PVC Table. Then configure the following.

Prompt Enter Result/Description

Entry
Number:

1 Identifies the PVC

Table entry being
configured.

Source: FRI-1S2 Specifies the PVC

source.

The PVC Table
appears.

4

#1
Destination:

From the Configure menu, select Configure Router ­> Configure Interface States. Then configure the
following.

Prompt Enter Result/Description

Interface #1
State:

Interface #5
State:

LCON-1 Identifies the PVC

destination.

The Configure
Interfaces record
appears.

Enabled Enables the router

interface.

Enabled Enables the router

interface.

5

From the Configure menu, select Configure Router ­> Configure IPX -> Parameters. Then configure the
following.

Prompt Enter Result/Description

Enable IPX: Enabled Enables overall

routing of Internal
Protocol Exchange
(IPX) packets.
Enables Novell
workstations to
connect to remote
file and printer
services.

The Parameters
record appears.

6

From the Configure menu, select Configure Router ­> Configure IPX -> Interfaces. Then configure the
following.

Prompt Enter Result/Description

Interface
Number:

1 Identifies the router

interface number
being configured.

Network
Number:

00000100 Identifies the four-

byte Novell
network number
assigned to the
network attached to
this interface.

Interface
Enable:

Enabled Enables IPX

routing on this
interface.

Interface
Number:

5 Identifies the router

interface number
being configured.

The Interfaces
record appears.

Network
Number:

Interface
Enable:

00000101 Identifies the four-

byte Novell
network number
assigned to the
network attached to
this interface.

Enabled Enables the router

interface.

7

From the Configure menu, select Configure LLC to
SDLC Tables -> Frame Relay Station Table. Then
configure the following

Prompt Enter Result/Description

Entry
Number:

1 References this

record.

The Frame Relay
Station table
appears.

8

Frame Relay
Port Number:

3 Identifies the

Frame Relay port
this LLC -SDLC
conversion station
is connected to.

Frame Relay
Station
Number:

1 The Frame Relay

station number on
the Frame Relay
port the LLC ­SDLC conversion
station is connected
to.

QLLC
Station
Address:

FF Identifies the

primary station
address FF for
QLLC primary
(HPAD) address.

XID Value: 020001744001 This is unique for

each application.

From the Configure menu, select Configure FRI
Stations. Then configure the following.

The FRI Stations
table appears.

Prompt Enter Result/Description

Port Number: 1 Identifies port

Station
Number:

Station Type: ANNEX_G Adds a packet

No. of PVC 0 Specifies the

number 1 of this
node.

1 Identifies the

station being
configured.

header and LAPB
header to frame for
reliability checking
between Frame
Relay stations.

Chan: number of channels

used for Permanent
Virtual Circuits.

No. of SVC
Chan:

16 Specifies the

number of lo gical
SVC channels on
this port.

Starting SVC
Chan:

1 Specifies the

starting logical
channel number for
the SVCs on this
link.

Port Number: 1 Identifies port

number 1 of this
node.

Station
Number:

2 Identifies the

station being
configured.

Station Type: BYPASS Bypass does not

add packet or
LAPB headers,
meaning there is no
reliability check,
but there is more
throughput
capability.

No. of PVC
Chan:

0 Specifies the

number of channels
used for Permanent
Virtual Circuits.

No. of SVC
Chan:

16 Specifies the

number of logical
SVC channels on
this port.

Starting SVC
Chan:

1 Specifies the

starting logical
channel number for
the SVCs on this
link.

Port Number: 3 Identifies the

physical port
position at the rear
of the unit and is
also the reference
number for this
record. The port
number selected
must be for a FRI
port.

Station
Number:

1 Identifies the

station being
configured.

Station Type: BYPASS Bypass does not

add packet or
LAPB headers,
meaning there is no
reliability check,
but the re is more
throughput
capability.

No. of PVC
Chan:

0 Specifies the

number of channels
used for Permanent
Virtual Circuits.

No. of SVC
Chan:

16 Specifies the

number of logical
SVC channels on
this port.

Starting SVC
Chan:

1 Specifies the

starting logical
channel number for
the SVCs on this
link.

Node 200 Configuration Sequence

Follow these steps to configure node 200 as shown in Figure 3-1.

Step Action Result/Description
1

From the Configure menu, select Port. Then
configure the following.

Prompt Enter Result/Description

The Port record
appears.

Port Number: 1 Identifies port

number 1 of this
node.

Port Type: FRI Identifies an FRI

interface port.

Clock
Source:

Ext Identifies that the

clock will be
generated from this
port.

Clock Speed: 38400 Specifies the speed

of this port.

Highest
Station
Number:

2 Limits the number

of configurable
stations to 2.

Port Number: 2 Identifies port

number 3 of this
node.

Port Type: XDLC Identifies an XDLC

interface port.

Clock
Source:

Int Identifies that the

clock will be
generated from this
port.

No. of
Stations:

1 Limits the number

of configurable
stations to 2.

Port Number: 5 Identifies port

Port Type:
Select TR on

the 305, and
ETH on the
300

number 5 of this
node.

ETH

Identifies an
Ethernet interface
port.

TR Identifies a Token

Ring interface port.

2

From the Configure menu, select Configure LAN
Connection -> LAN Connection Table. Then
configure the following.

Prompt Enter Result/Description

Entry
Number:

1 References this

table record.

The LAN
Connection Table
appears.

3

LAN
Forwarder
Type:

ROUT Specifies that the

LAN connection is
to pass routed
traffic.

Router
Interface
Number:

Encapsulation
Type:

5 Identifies the router

interface number
being configured.

RFC1294 Specifies the type

of encapsulation
used for this LAN.

From the Configure menu, select Configure Network
Service -> Route Selection Table. Then configure the
following.

Prompt Enter Result/Description

Entry
Number:

1 References this

table record

Address: 100 Identifies the

address to be
routed.

The Route
Selection Table
appears.

4

#1
Destination:

FRI-1S1 Calls with a

network address
corresponding to
this destination.

From the Configure menu, select Configure Network
Service -> PVC Table. Then configure the following.

Prompt Enter Result/Description

Entry
Number:

1 Identifies the PVC

Table entry being
configured.

Source: FRI-1S2 Specifies the PVC

source.

#1
Destination:

LCON-1 Identifies the PVC

destination.

The PVC Table
appears.

5

From the Configure menu, select Configure XDLC
Port Stations. Then configure the following.

Prompt Enter Result/Description

Port Number: 2 Identifies port

number 2 of this
node.

The XDLC
Stations record
appears.

6

Station
Number:

1 The numb er of the

station on the
multidrop line.

Station Type: SDLC Identifies the

station type as
SDLC.

Station
Address:

C1 The station address

on the multidrop
line.

Autocall
Mnemonic:

SDLCC1001 Identifies the

remote address that
is called when
polling activity is
detected on the
SDLC line.

QLLC
Options:

XID3 Specifies that SIDs

will pass
transparently.

From the Configure menu, select Configure Router ­> Configure Interface States. Then configure the
following.

The Configure
Interfaces record
appears.

Prompt Enter Result/Description

Interface #1
State:

Interface #5
State:

Enabled Enables the LAN

interface.

Enabled Enables the LAN

interface.

7

From the Configure menu, select Configure Router ­> Configure IPX -> Parameters. Then configure the
following.

Prompt Enter Result/Description

Enable IPX: Enabled Enables overall

routing of Internal
Protocol Exchange
(IPX) packets.
Enables Novell
workstations to
connect to remote
file and printer
services.

The Parameters
record appears.

8

From the Configure menu, select Configure Router ­> Configure IPX -> Interfaces. Then configure the

The Interfaces
record appears.

following.

Prompt Enter Result/Description

Interface
Number:

1 Identifies the router

interface number
being configured.

Network
Number:

00000200 Identifies the four-

byte Novell
network number
assigned to the
network attached to
this interface.

Interface
Enable:

Enabled Enables IPX

routing on this
interface.

9

From the Configure menu, select Configure Network
Services -> Mnemonic Table. Then configure the
following

Prompt Enter Result/Description

Entry
Number:

1 References this

table record.

The Mnemonic
table appears.

10

Mnemonic
Name:

Call
Parameters:

SDLC1001 Identifies the

mnemonic name

1000201 Identifies the

location to send the
autocall. The
convention is to
identify the node
and port number in
this parameter

From the Configure menu, select Configure FRI
Stations. Then configure the following.

Prompt Enter Result/Description

Port Number: 1 Identifies port

number 1 of this
node.

Station
Number:

1 Identifies the

station being
configured.

Station Type: ANNEX_G Adds a packet

header and LAPB
header to frame for
reliability checking
between Frame
Relay stations.

The FRI Stations
table appears.

Link
Address:

No. of PVC
Chan:

No. of SVC
Chan:

DTE Specifies the type

of link address

0 Specifies the

number of channels
used for Permanent
Virtual Circuits.

16 Specifies the

number of logical
SVC channels on
this port.

Starting SVC
Chan:

1 Specifies the

starting logical
channel number for
the SVCs on this
link.

Port Number: 1 Identifies port

number 1 of this
node.

Station
Number:

2 Identifies the

station being
configured.

Station Type: BYPASS Bypass does not

add packet or
LAPB headers,
meaning there is no
reliability check,
but there is more
throughput
capability.

Link
Address:

No. of PVC
Chan:

DTE Specifies the type

of link address

0 Specifies the

number of channels
used for Permanent
Virtual Circuits.

No. of SVC
Chan:

16 Specifies the

number of logical
SVC channels on
this port.

Starting SVC
Chan:

1 Specifies the

starting logical
channel number for
the SVCs on this
link.

IP Over X.25

Introduction

Figures 3-2 and 3-3 show an example of Ethernet Routing over X.25.

What You Need to Configure

Configure the following tables and records.

For Node 100... For Nodes 200 and 300...

Node record Node record
LAN Connection Table LAN Connection Table
Router Table Router Table
Interface States Interface States
Interfaces Interfaces
Route Selection Table Route Selection Table
Port records Port records
Mnemonic Table

Example of Node 100 Configuration

Figure 3-2 shows the sample configuration for node 100.

Figure 3-2. Node 100 Ethernet Routing over X.25

Node 100 Configuration Sequence

Follow these steps to configure node 100 as shown in Figure 3-2.

Step Action Result/Description
1

From the Configure menu, select Configure Router

-> Configure Interface States. Then: Configure the
following parameters:

Prompt: Enter: Result/Description

Interface #1
State:

Enabled Enables the router

interface.

The Configure
Interface States
menu appears.

2

Interface #5
State:

Interface #6
State:

Enabled Enables the router

interface.

Enabled Enables the router

interface.

From the Configure Router menu, select Configure
IP -> Interfaces. Then: Configure the following.

Prompt: Enter: Result/Description

Entry
Number:

Interface
Number:

1 References this

table record.

1 Identifies the router

interface number
being configured.

IP Address: 219.1.83.100 Identifies the IP

address associated
with this interface.

Entry
Number:

Interface
Number:

2 References this

table record.

5 Identifies the router

interface number
being configured.

The Interfaces
menu appears.

IP Address: 200.1.1.100 Identifies the IP

Entry
Number:

Interface
Number:

IP Address: 200.1.2.100 Identifies the IP

From the Configure menu, select LAN Connection The LAN

address associated
with this interface.

3 References this

table record.

6 Identifies the router

interface number
being configured.

address associated
with this interface.

3

Table. Then: Configure the following.

Prompt: Enter: Result/Description

Entry
Number:

1 References this

table record.

Connection table
appears.

LAN
Forwarder
Type:

Router
Interface
Number:

Encapsulation
Type:

Autocall
Mnemonic:

Entry
Number:

ROUT Specifies that the

LAN connection is
to pass routed
traffic.

5 Specifies a router

interface that is
using this LAN
connection record.

CODEX Specifies the type

of encapsulation
used over this LAN
connection.

(blank) Specifies the

mnemonic name
used when this
LAN connection
record initiates the
autocall.

2 References this

table record.

LAN
Forwarder
Type:

ROUT Specifies that the

LAN connection is
to pass routed
traffic.

Router
Interface
Number:

6 Specifies a router

interface that is
using this LAN
connection record.

Encapsulation
Type:

CODEX Specifies the type

of encapsulation
used over this LAN
connection.

Autocall
Mnemonic:

(blank) Specifies that an

autocall is not
initiated.

4

From the Configure menu, select Route Selection.
Then: Configure the following.

Prompt: Enter: Result/Description

Entry
Number:

1 References this

table record.

Address: 10094 Identifies the

address to be
routed.

The Route
Selection table
appears.

5

#1
Destination:

LCON Identifies an

internal LAN
connection module.

From the Configure menu, select Port record. Then:
Configure the following.

Prompt: Enter: Result/Description

Port Number: 1 Identifies port

number 1 of node

100.

Port Type: X25 Identifies an X.25

interface port.

Clock
Source:

Ext Identifies that the

clock will be
generated by this
Vanguard 300 on
this port.

Link
Address:

DTE Defines the logical

address of the port
for X.25 operation.

The Port record
appears.

Port Number: 5 Identifies port

Port Type:
(Select TR on
the 305, and
ETH on the

300)

number 5 of node

100.

ETH Identifies an

Ethernet interface
port.

TR Identifies a Token

Ring interface port.

IExample of Node 200 and 300 Configuration

Figure 3-3 shows the sample configuration for nodes 200 and 300.

Figure 3-3. Nodes 200 and 300 Ethernet Routing Over X.25

Node 200 Configuration Sequence

Follow these steps to configure Node 200 as shown in Figure 3-3.

Step Action Result/Description
1

From the Configure menu, select LAN Connection
Table. Then: Configure the following.

The LAN
Connection table
appears.

Prompt: Enter: Result/Description

Entry Number: 1 References this

node's table record.

LAN Forwarder
Type:

ROUT Specifies that the

LAN connection is
to pass routed
traffic.

Router Interface
Number:

6 Specifies a router

interface that is
using this LAN
connection record.

EncapsulationType: CODEX Specifies the type

of encapsulation
used over this LAN
connection.

Autocall
mnemonic:

LAN100 Specifies the

mnemonic name
used when this
LAN connection
record initiates the
autocall.

Remote Connection
ID:

2 Identifies which

record in the
remote LAN
connection table to
connect to.

2

From the Configure menu, select Configure Router ->
Configure Interface States. Then: Configure the
following.

Prompt: Enter: Result/Description

Interface #1 State: Enabled Enables the router

Interface #6 State: Enabled Enables the router

The Configure
Interface States
menu appears.

interface.

interface.

3

From the Configure IP menu, select Interfaces. Then:
Configure the following.

Prompt: Enter: Result/Description

Entry Number: 1 References this

table record.

Interface Number: 1 Identifies the router

interface number
being configured.

IP Address: 219.2.83.200 Identifies the IP

address associated
with this interface.

Entry Number: 2 References this

table record.

Interface Number: 6 Identifies the router

interface number
being configured.

IP Address: 200.1.2.200 Identifies the IP

address associated
with this interface.

The Interfaces
menu appears.

4

From the Configure menu, select Port record. Then:
Configure the following.

Prompt: Enter: Result/Description

Port Number: 1 Identifies port

number 1 of node

200.

Port Type: X25 Identifies an X.25

interface port.

Clock Source: Ext Identifies that the

clock will not be
generated by this
Vanguard 300 on
this port.

Link Address: DTE Defines the logical

address of the port
for X.25 operation.

Port Number: 5 Identifies port

number 5 of node

200.

The Port record
appears.

Port Type: (Select
one of either
Ethernet or Token
Ring)

ETH Identifies an

Ethernet interface
port.

TR Identifies a Token

Ring interface port.

5

6

From the Configure menu, select Route Selection. Then:
Configure the following.

Prompt: Enter: Result/Description

Entry Number: 1 References this

table record.

Address: 100* Identifies the

address to be
routed.

#1 Destination: P1 Identifies Port 1 of

this node.

From the Configure menu, select Mnemonic table. Then:
Configure the following.

Prompt: Enter: Result/Description

Entry Number: 1 References this

table record.

Mnemonic name: LAN100 Identifies the

mnemonic name.

Call parameters: 10094 Identifies the

location to send the
autocall to. The
convention is to
identify the node
and port number in
this parameter.

The Route
Selection table
appears.

The Mnemonic
table appears.

Follow these steps to configure Node 300 as shown in Figure 3-3.

Node 300 Configuration Sequence

Step Action Result/Description
1

From the Configure menu, select LAN Connection
Table. Then: Configure the following.

Prompt: Enter: Result/Description

Entry Number: 1 References this

The LAN
Connection table
appears.

table record.

LAN Forwarder
Type:

Router Interface
Number:

Encapsulation
Type:

Autocall
mnemonic:

Remote
Connection ID:

ROUT Specifies that the

LAN connection is
to pass routed
traffic.

5 Specifies a router

interface that is
using this LAN
connection record.

CODEX Specifies the type

of encapsulation
used over this LAN
connection.

LAN100 Specifies the

mnemonic name
used when this
LAN connection
record initiates the
autocall.

1 Identifies which

record in the
Remote LAN
Connection table to
connect to.

2

From the Configure menu, select Configure Router ->
Configure Interface States. Then: Configure the
following.

Prompt: Enter: Result/Description

Interface #1
State:

Interface #5
State:

The Configure
Interface States
menu appears.

Enabled Enables LAN interface.

Enabled Enables LAN interface.

3

From the Configure IP menu, select Interfaces. Then:
Configure the following.

Prompt: Enter: Result/Description

Entry Number: 1 References this table

record.

The Interfaces
menu appears.

4

Interface
Number:

1 Identifies the router

interface number being
configured.

IP Address: 219.3.83.23

0

Identifies the IP
address associated with
this interface.

Entry Number: 2 References this table

record.

Interface
Number:

5 Identifies the router

interface number being
configured.

IP Address: 200.1.1.230 Identifies the IP

address associated with
this interface.

From the Configure menu, select Port record. Then:
Configure the following.

Prompt: Enter: Result/Description

Port Number: 1 Identifies port number

1 of this node.

The Port record
appears.

Port Type: X25 Identifies an X.25

interface port.

Clock Source: Ext Identifies that the clock

will not be generated
by this port.

Link Address: DTE Defines the logical

address of the port for
X.25 operation.

Port Number: 5 Identifies port number

5 of node 300.

Port Type:
(Select TR on
the 305, and
ETH on the

300)

ETH Identifies an Ethernet

interface port.

TR Identifies a Token Ring

interface port.

5

From the Configure menu, select Route Selection. Then:
Configure the following.

The Route
Selection table
appears.

Prompt: Enter: Result/Description

Entry Number: 1 References this table

record.

Address: 100* Identifies the address to

be routed.

#1 Destination: P1 Identifies Port 1 of this

node.

6

From the Configure menu, select Mnemonic table.
Then: Configure the following.

Prompt: Enter: Result/Description

Entry Number: 1 References this table

record.

Mnemonic
name:

Call
parameters:

LAN100 Identifies the

mnemonic name.

10094 Identifies the location

to send the autocall to.
The convention is to
identify the node and
port number in this
parameter.

The Mnemonic
table appears.

Overview

Introduction

This section explains how to maintain and replace Vanguard 300/305
components, including daughtercards.

Only trained, qualified technicians should perform the procedures outlined in this
chapter.

Motorola Vanguard 300/305 daughtercards and DIMs are sensitive to static
discharge, which can damage components. Use proper handling and grounding
precautions when handling a Motorola Vanguard 300/305 daughtercard or DIM.

Opening the Enclosure

Introduction

This section explains how to open the Vanguard 300/305 enclosure.

Before You Begin

Power down and disconnect the Vanguard 300/305 before you remove the top
cover, front panel, and handle any components.

Maintaining and Troubleshooting

Procedure to Remove the Top Cover and Front Panel

Follow these steps to open the enclosure.

Step Action
1

Open the front panel door by separating the mounting tabs from the base
of the unit and using a downward motion to pull it toward you and off as
shown in Figure 4-1.

2

Release the plastic locking clips at the bottom of the Vanguard unit, as
shown in Figure 4-2.

3

Insert a 0.25-inch flathead screwdriver at a 45-degree angle between the
unit and along the topmost portion of each of the six snap hinges, (three
located on each side of the unit) and push downward, as shown in Figure
4-3.

4

The hinges snap out toward you. Lift off the top cover, as shown in
Figure 4-4.

Example of Removing the Front Panel

Figure 4-1 shows how to remove the front panel.

Figure 4-1. Removing the Front Panel

Example of Releasing Locking Clips

Figure 4-2 shows how to release the plastic locking clips at the bottom of the
standalone unit.

Figure 4-2. Releasing Plastic Locking Clips

Example of How to Release Snap Hinges

Figure 4-3 shows how to release the snap hinges located at the bottom of the unit.

Figure 4-3. Releasing the Snap Hinges

Example of Removing Top Cover

Figure 4-4 shows how to properly remove the top cover after you unlock releases
and snap hinges on the unit.

Figure 4-4. Removing Top Cover

Strapping the Ethernet Interface on a Vanguard 300

Introduction

This section describes how to set the strapping for the Ethernet interface on a
Vanguard 300. Ethernet strapping is located under the daughtercard for the
Vanguard 300 unit. The default setting for Ethernet strapping is 10BaseT.

This information is only applicable to the Vanguard 300, as the Vanguard 305
does not have an Ethernet interface.

Steps to Strap Ethernet Card

Follow these steps to set Ethernet strapping.

Step Action
1

Remove the enclosure.

2
3

Remove the rear filler panel above the daughtercard.
Remove the two screws attaching the daughtercard panel to the rear panel

of the Vanguard 300.

4

Remove one screw attaching the daughtercard to the standoff on the
motherboard.

5

Carefully, by applying equal force at both ends, pull off the daughtercard
until it unplugs from the header.

6
7

Set the strapping as shown in Figure 4-5.
Reassemble the Vanguard 300.

Example of Setting Ethernet Strapping

Figure 4-5 shows the strapping for the Ethernet interface.

Figure 4-5. Strapping the Ethernet Interface

Adding or Replacing Optional Components

Introduction

You can upgrade and replace components on the Vanguard 300/305 processor
card. This section provides instructions for the following:

• DIMs (Data Interface Modules) and DIM Site daughtercards

• DRAM and Data Compression SIMMs (Single In-line Memory Modules)

• DSU daughtercards

• ISDN daughtercards

Vanguard 300/305 cards and their components are sensitive to static discharge,
which can damage components. Use proper handling and grounding precautions,
including the use of an anti-static grounding strap, whenever you handle a card.

Adding or Replacing a DIM

Overview

The Vanguard 300/305 supports V.24, V.35, V.36, or V.11 DIMs. DIMs reside on
the motherboard and DIM Site daughtercard, if installed.

Example of DIM Position

Figure 4-6 shows how to position a DIM on the Vanguard 300/305 motherboard.

Figure 4-6. DIM Position

DIP Switch Settings

The following tables describe DIP switch settings for DIM configurations.

For Set Switch To

V.24 DIM 1-5

ON

6-8

V.11,V.35, V.36 DIMs 1-5

6-8

Example of DIM Dip Switch Settings

Figure 4-7 shows the DIM DIP switch settings on the motherboard.

OFF
OFF
ON

Figure 4-7. DIM Dip Switch Settings

Example of DIM Replacement on Motherboard

DIMs may be replaced in the field, as shown in Figure 4-8, using the same DIM
removal strap used for the 6500 Series products.

Figure 4-8. DIM Replacement on Motherboard

Adding or Replacing a DIM Site Daughtercard

Introduction

This sectio n describes how to add or replace a DIM Site daughtercard.
The DIM Site daughtercard provides an optional V.24, V.35, V.36, or V.11

interface and attached DIM with a DB25 connector and comes installed from the
factory if you ordered one.

DIM Site Daughtercard

Figure 4-9 shows a DIM Site daughtercard.

Figure 4-9. DIM Site Daughtercard

Before You Add/Replace DIM SIte Daughtercard

Power down and disconnect the Vanguard 300/305 before you add or replace a
DIM daughtercard.

Steps to Add/Replace DIM Site Daughtercard

Follow these steps:

Step Action
1

Unplug the power cord from the primary power source and remove
interface cables and power cables.

2

3

4

5

6

7

8

9

Open front panel door by using a downward motion to pull it toward you
and off.

Position the blade of a 0.25-inch flathead screwdriver between the unit
and along the topmost portion of each of the six snap hinges (three
located on each side of the unit), and push downward until the hinge
snaps out toward you.

Remove the daughtercard mounting screw that attaches the daughtercard
to the board.

Unscrew the two rear panel coverplate screws. Unplug the existing
daughtercard.

If you are adding a daughtercard rather than replacing it, connect the 68­pin interface header onto the motherboard, as shown in Figure 4-10.

If you are replacing the daughtercard, align the standoff on the
motherboard with the hole on the new daughtercard as shown in Figure
4-10.

Push the daughtercard down onto the connector, being careful to align
pins.

Fasten the screw that attaches the daughtercard to the motherboard, then
fasten the two screws into the rear panel coverplate. The daughtercard is
replaced.

10

Reassemble the Vanguard unit; power on the unit.

Example of Adding/Replacing DIM Daughtercard

Figure 4-10 shows how to add or replace a DIM Site daughtercard.

Figure 4-10. Replacing the DIM Daughtercard

Strapping the DIM Site Daughtercard

Overview

This section describes how to strap the DIM Site daughtercard.

Strapping the DIM Daughtercard

The strapping on the DIM daughtercard typically comes configured from the
factory in Ring Indicator mode, which causes pin 22 on the DB25 connector to
indicate the presence of an incoming call to the attached DTE. Otherwise, the
strap is set to Test Mode (see Figures 4-11 and 4-12).

Steps to Set Strap on a DIM daughtercard

Follow these steps:

Step Action
1

Power down and disconnect the Vanguard 300/305 before you set the
strap on a DIM daughtercard.

2

Unplug the power cord from the primary power source and remove
interface cables and power cables.

3
4

Remove the top cover of the Vanguard unit.
Set the strapping as shown in Figures 4-11 and 4-12 for the following:
Pin 22: Normally defined as Test Mode Indicator, an input for a DCE

device. However, you can configure it as an output and use it in Ring
Indicator mode when the port is configured to emulate a dial modem
(DCE only).

Pin 25: Normally defined as Make Busy, an input for a DCE device.
However, you can configure it as an output (Make Busy) or an input
(Test Mode) when the port is a DTE.

5

Push the strap down onto the pins.

Example of Strapping the DIM Site Daughtercard

Figure 4-11 shows the strapping for the DIM Site.

Figure 4-11. Strapping DIM Site Daughtercard Example

Description of DIM Daughtercard Strapping

Figure 4-12 describes the strapping and DIP switch settings for the DIM Site
daughtercard.

Figure 4-12. DIM Daughtercard Strapping Description

Adding or Replacing DRAM and Data Compression SIMMs

Overview

The Vanguard 300/305 processor card comes with 4Mbytes of RAM o n the card.
You can obtain additional DRAM to be inserted on your Vanguard 300/305
motherboard. Also, the Vanguard 300/305 has an optional Frame Data
Compressor feature that requires a Data Compression SIMM DSP. The
following section gives information about installing these optional SIMMs.

SIMM Location

For proper operation, the optional SIMMs must installed in the correct SIMM
slots. The DRAM SIMM must be in socket U73 and DC SIMM DSP must be in
socket U69. Figure 4-13 shows the location of the SIMM slots on the Vanguard
300/305 processor card.

Figure 4-13. SIMM Slot Locations

U73 and U69 are marked on the surface of the motherboard, just below the SIMM
slots. The SIMMs are different sizes, so you cannot install the SIMMs in the
incorrect slots.

Procedure to Install SIMMs

Use the following procedure to install SIMMs.

Step Action
1

Insert the SIMM into a slot at a slight angle as shown in 4-14.

2
3

Press the SIMM into the socket.
Make sure it locks in place with the locking tabs.

Figure 4-14. SIMM Installation

Procedure to Remove SIMMs

Use the following procedure to remove SIMMs.

Step Action
1

Disengage the locking tabs by pushing them outward and, at the same
time, press against the side with the chips so the SIMM disengages from
the locking tabs.

2

Lift out the SIMM.

Adding or Replacing a DSU Daughtercard

Overview

This section describes how to add or replace the DSU daughtercard.
The DSU daughtercard provides an RJ48S connector on Port 1 and comes

installed from the factory if you ordered a daughtercard. It supports speeds of 56
kbps (synchronous), and does not support multipoint.

DSU Functionality

The DSU daughtercard functionality suits an extended range of 56 kbps point-to­point DDS1 interface for North American service that conforms to AT&T 62310
or ANSI T1E1.4/91-006.

The DSU daughtercard is FCC Part 68 registered.
The DSU normally uses external clocking derived from the network.
Diagnostic loopbacks from the telephone company are supported; local

diagnostics are activated from the CTP.

DSU Daughtercard

Figure 4-15 shows the DSU daughtercard.

Figure 4-15. DSU Daughtercard

Before You Add/Replace DSU Daughtercard

Power down and disconnect the Vanguard 300/305 before you add or replace a
DSU daughtercard.

Steps to Replace a DSU Daughtercard

Follow these steps:

Step Action
1

Unplug the power cord from the primary power source and remove
interface cables and power cables.

2
3

4

5

6

7

8

9
10

Remove the top cover and front panel of the Vanguard base unit.
Remove the daughtercard mounting screw that attaches the daughtercard

to the board.
Unscrew the two rear panel coverplate screws. Unplug the existing

daughtercard.
If you are adding a daughtercard rather than replacing it, connect the 68-

pin interface header onto the motherboard, as shown in Figur e 4-16.
If you are replacing the daughtercard, align the standoff on the

motherboard with the hole on the new daughtercard, as shown in Figure
4-16.

Push the da ughtercard down onto the connector, being careful to align
pins.

Fasten the screw that attaches the daughtercard to the motherboard, then
fasten the two rear panel coverplate screws. The daughtercard is replaced.

Replace the top cover and front panel.
Reconnect the interface cables and power cables; power on the unit.

Example of Adding/Replacing a DSU Daughtercard

Figure 4-16 shows how to add or replace a DSU daughtercard on a Vanguard
300/305.

Figure 4-16. Replacing the DSU Daughtercard

DSU Configuration

Parameters Inapplicable to DSU

The following configuration parameters are not applicable when configuring a
DSU option:

• Clock Speed

• Connection Type

• Port Control

Clock Source Parameter Values

Configure the Clock Source parameter as follows.

Use To do this...

INT provide clock to the network.
EXT use the network-provided clock (usual mode for DSU operation).

DSU Reporting

Introduction

CTP reporting of information differs for the DSU daughtercard in terms of input
signaling. Use the CTP "Monitor" function from the Main menu to view these
signals.

Note: "L" stands for "Signal Low" and "H" is "Signal High".

Differences in CTP Reporting of Input Signals

Input Signal Function

NIS (Not In Service) Normally "L." Used to determine if the other

end of the connection is available. If no signal is
received, the DSU option is in DSU loopback
mode, Or If idle codes are received, NIS is "H."

BPV (Bipolar Violation) An "L" means the DSU option has received a

bipolar violation. An "H" is expected during
normal operation. Expected to toggle during a
DSU loopback condition.

DL (DSU Loopback) Normally "H." An "L" indicates entry into a

DSU loopback mode.

C+ (Positive Sealing Current) "H" if the DC current on the telephone company

interface is not in the positive direction. If both
C+ and C- are "H", no sealing current exists,
which often occurs when connected to other
DSU type hardware. C+ would be expected to
be "L" normally when connected to central
office equipment (OCU) hardware.

C- (Negative Sealing Current) "H" if the DC current on the telephone company

interface is not in the negative direction. If both
C+ and C- are "H", no sealing current exists,
which often occurs when connected to other
DSU type hardware. C+ would be expected to
be "L" normally when connected to central
office equipment (OCU) hardware.

CTP reporting of information for the DSU differs in terms of output signaling.
Although these output signals are not directly accessible to the user, the DSU
option software manipulates these signals a nd may be useful for informational
purposes.

Differences in CTP Reporting of Output Signals

Use the CTP "Monitor" function from the Main menu to view these signals.

Input Signal Function

RS (Reset) Resets the DSU option hardware. Normal operating state

is "H."

LL (Local Loopback) When "L", the DSU hardware is locally looping data

back to the Vanguard hardware.

CL (CSU Loopback) When "L", the DSU hardware is looping the remote

connection's receive to transmit.

IDL (Idle) An "H" informs the DSU hardware to send idle bipolar

violations to the remote system.

CLK (Clock Mode) When "H", denotes network clock use. When "L", the

DSU option provides the clock.

Differences in CTP Statistics

CTP statistics output also differs in the following ways:

• Detailed Port Statistics show DSU input/output signaling, as well as

noting the installed DSU.

• Detailed Node Statistics show DSU installation.

CTP Loopback Modes

Two additional CTP loopback modes now exist.

Mode Function

DSU Internal
Loopback

DSU Internal and
External Loopback

Does not affect the exter nal interface. Loops the local
transmit data back to the receive data. Failure indicates
no connection.

Performs the internal loopback by looping the external
transmit to the external receive to allow manual testing of
the remote interface.

DSU Troubleshooting

Introduction

Use the following information to help troubleshoot potential installation
problems.

Potential Installation Problems

Installation problems may include the following:

• Improper telephone company interfa ce connection

• Incorrect DSU port Clock Source option

• No signal from telephone company interface

CTP-Derived Information

The following information may be derived from the CTP.

Function used to...

Node Statistics

• verify that the software is a version that contains

the DSU option modifications.

• show if the software recognizes the DSU.

Port Statistics

• verify that data is sent without error; error counts

may denote an error in clocking mode
configuration.

• show if the software recognizes the DSU.

Monitor

• determine, via input/output signals, if the DSU

option is in a loopback mode requested by the
remote end (which would result in an inability to
send data); continuous bipolar violations indicate
the remote system is out of service.

DSU Internal Loopback

• indicate a failure of this loopback mode, meaning

a connection has not been made.

Adding or Replacing an ISDN Daughtercard

Introduction

The ISDN daughtercard provides an RJ45 connector on Port 1 and comes
installed from the factory if you ordered the ISDN option when you ordered your
Vanguard 300/305.

Packaging

The following items will be enclosed in the Vanguard ISDN daughtercard
package:

1 - Vanguard Daughtercard Installation Instructions
1 - Vanguard Daughtercard
1 - RJ45 ISDN connection cable
1 - Male to male header (interface connector)
3 - Screws with locking washers

ISDN Daughtercard

Figure 4-17 shows the ISDN daughtercard.

Figure 4-17. ISDN Daughtercard

ISDN Daughtercard Compatibility

Use the following table to verify that your ISDN daughtercard is compatible with
your Vanguard:

Platform Platform Version ISDN Daughtercard Part Numbers

Vanguard 100 71955G01 Rev B and up U card: 72291G01 S card:

Vanguard 300 72005G11 Rev A and up U card: 72291G01 S card:

Vanguard 305 All U card: 72291G01 S card:

The daughtercard serial number appears on the surface of the daughtercard, and
the platform version appears on the Vanguard motherboard.The platform version
can also be read from the CTP from the Status/Statistics menu item, Hardware
Stats screen, beside the item marked "Assembly".

Before Adding/Replacing the ISDN Daughtercard

Power down and disconnect the Vanguard 300/305 before you add or replace an
ISDN daughtercard.

72300G01

72300G01

72300G01

Steps to Add or Replace an ISDN Daughtercard

Follow these steps:

Step Action
1

Unplug the power cord from the primary power source and remove
interface cables and power cables.

2
3

4

5

6

7

8

9

10

Remove the top cover and front panel of the Vanguard (see Figur e 4-4.)
Check the serial number on the surface of the daughte rcard, and on the

surface of the motherboard to verify compatibility (see the "ISDN
Daughtercard Compatibility" table, above, to check compliance.)

Remove the daughtercard mounting screw that attaches the daughtercard
to the board.

Unscrew the two rear panel coverplate screws. Unplug the existing
daughtercard.

If you are adding a daughtercard rather than replacing it, connect the 68­pin interface header onto the motherboard, as shown in Figur e 4-18.

To replace the daughtercard, align the standoff on the motherboard with
the hole on the new daughtercard as shown in Figur e 4-18.

Push the daughtercard down onto the connector, being careful to align
pins.

Fasten the screw that attaches the daughtercard to the motherboard, then
fasten the two rear panel coverplate screws. The daughtercard is replaced.

Replace the top cover and front panel, snapping them together.

11
12

Reinstall the front door.
Reconnect the interface cables and power cables; power on the unit.

Adding/Replacing the ISDN Daughtercard

Figure 4-16 shows how to replace the ISDN daughtercard.

Figure 4-18. Replacing the ISDN Daughtercard

Back Panel with the ISDN Daughtercard

Figure 4-19 shows the back panel of the Vanguard after you have installed the
ISDN daughtercard.

Figure 4-19. Vanguard Back Panel with ISDN Daughtercard

ISDN Interface RJ45 Connector

The following table shows the pinouts for the RJ45 ISDN U and S/T interface
connection cable:

U Card S Card
Pin Name Function Name Function
1

Battery Status No connection PS 3 + No connection

2
3

4

5

6

7
8

Battery Status No connection PS 3 - No connection

--- No connection TE NT + TE to NT pair,

Signal U interface tip

Signal U interface tip

--- No connection TE NT - TE to NT pair,

Powering No connection PS 2 - No connection
Powering No connection PS 2 + No connection

Connector Pin Numbers

The connector pins are numbered from right to left as indicated in the following
diagram:

or ring

or ring

no power
connection

NT TE + NT to TE pair,

no power
connection

NT TE - NT to TE pair,

no power
connection

no power
connection

ISDN Cable Connection

Figure 4-20 shows how to connect the ISDN Cable to the ISDN daughtercard.

Do not attach the ISDN Cable until the daughtercard is installed in the Vanguard
chassis, and the unit is completely reassembled.

Figure 4-20. Connecting the ISDN Cable

Introduction

This section describes the physical and environmental specifications and power
requirements for the Vanguard 300/305.

Environmental

The following environmental specifications must be adhered to:

• Operating temperature: 32° to 104° F maximum (0° to 40°C maximum)

• Storage temperature: -40° to +158°F (-40° to +70°C)

• Relative humidity: 0% to 95% (noncondensing)

Electro Magnetic Compatibility

Compatibility features include:

• FCC Part 15, Class A

• CISPR 22 and EN 55022, Class B

• AS 3548, Class B

Specifications and Requirements

• EN 50082-1

Safety

The Vanguard 300/305 adheres to the following safety codes:

• EN60950 (Europe)

• CSA 950

• UL Listed per UL 1950

• BABT (England)

• AUSTEL (Austra lia)

Power Requirements

Vanguard 300/305 requires the following power:

• 100 to 240 VAC nominal at 47 to 63 Hz

• 31 watts

Physical

Vanguard 300/305 physical measurements include:

• Height: 3 inches (7.6 cm)

• Width: 8.5 inches (21.6 cm)

• Depth: 16 inches (40.6 cm)

Weight

Weight specifications include :

Vanguard 300/305 base 6.9 lb (3.2 kg)
DSU daughtercard 0.25 lb (0.2 kg)
DIM Site daughtercard 0.25 lb (0.2 kg)
ISDN daughtercard 0.25 lb (0.2 kg

Power Supply Description

The Vanguard 300/305 is powered by a fixed-frequency, switch mode 35W power
supply.

Hardware

Hardware specifications include:

• 68360 processor

• Battery backed configuration memory

• Shelf life: 10 years

• Code compression in FLASH memory