13 AccessGate1000InstallationManual

AccessGate 1000 Installation Manual
9000-62482-13
100 Crossing Boulevard Framingham, MA 01702-5406 USA www.nmscommunications.com
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of NMS Communications Corporation. 2006 NMS Communications Corporation. All Rights Reserved. Alliance Generation is a registered trademark of NMS Communications Corporation or its subsidiaries. NMS Communications, Natural MicroSystems, AG, CG, CX, QX, Convergence Generation, Natural Access, Natural Access MX, CT Access, Natural Call Control, Natural Media, NaturalFax, NaturalRecognition, NaturalText, Fusion, Open Telecommunications, Natural Platforms, NMS HearSay, AccessGate, MyCaller, and HMIC are trademarks or service marks of NMS Communications Corporation or its subsidiaries. MultiVendor Integration Protocol (MVIP) is a registered trademark of GO-MVIP, Inc. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. Windows NT, MS-DOS, MS Word, Windows 2000, and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Clarent and Clarent ThroughPacket are trademarks of Clarent Corporation. Sun, Sun Microsystems, Solaris, Netra, and the Sun logo are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. in the United States and/or other countries. Products bearing SPARC trademarks are based upon an architecture developed by Sun Microsystems, Inc. Linux is a registered trademark of Linus Torvalds. Red Hat is a registered trademark of Red Hat, Inc. All other marks referenced herein are trademarks or service marks of the respective owner(s) of such marks. All other products used as components within this product are the trademarks, service marks, registered trademarks, or registered service marks of their respective owners. Every effort has been made to ensure the accuracy of this manual. However, due to the ongoing improvements and revisions to our products, NMS Communications cannot guarantee the accuracy of the printed material after the date of publication or accept responsibility for errors or omissions. Revised manuals and update sheets may be published when deemed necessary by NMS Communications. P/N 9000-62482-13
Revision history
Revision Release date 1.0 1.1 1.2 1.3 July, 2005 November, 2005 March, 2006 September, 2006 Notes MVH, AccessGate firmware release 2.0 MVH, AccessGate firmware release 2.1 MVH, AccessGate firmware release 2.2 MVH, AccessGate firmware release 3.0
Last modified: September 29, 2006 Refer to www.nmscommunications.com for product updates and for information about support policies, warranty information, and service offerings.
NMS Communications
Table Of Contents
Chapter 1: Introduction .................................................................................7 Chapter 2: Overview of AccessGate 1000.......................................................9 AccessGate 1000 product description ............................................................. 9 TDM backhaul configurations...................................................................... 9 IP backhaul configurations ........................................................................10 Virtual gateways......................................................................................10 Terminology ..............................................................................................12 AccessGate network locations....................................................................12 Backhaul and service trunks......................................................................12 In-path and bypass state ..........................................................................13 Protected and unprotected trunks ..............................................................13 AccessGate 1000 sixteen-trunk variants ........................................................14 Sixteen-trunk front I/O variant ..................................................................14 Sixteen-trunk rear I/O variant ...................................................................15 AccessGate 1000 eight-trunk variants ...........................................................16 Eight trunk front I/O variant......................................................................16 Eight-trunk rear I/O variant ......................................................................17 Connectors................................................................................................18 ACO switch................................................................................................19 ACO switch operation ...............................................................................19 LED indicators............................................................................................20 Status LEDs ............................................................................................20 Trunk LEDs.............................................................................................20 Ethernet LEDs .........................................................................................21 ACO LED ................................................................................................21 Chapter 3: Preparing for installation............................................................23 Required tools ...........................................................................................23 Computer requirements ..............................................................................24 Unpacking and inspecting the equipment .......................................................25 AccessGate 1000 device kit.......................................................................25 AccessGate 1000 panel extender kit (optional).............................................26 AccessGate 1000 rear support kit (optional) ................................................26 Summary of the installation procedure ..........................................................27 Safety precautions...................................................................................28 Global installation recommendations .............................................................29 Chapter 4: Installing AccessGate in a frame ................................................31 AccessGate installation overview ..................................................................31 Assembling the panel extender mounting kit ..................................................32 Assembling the rear support kit....................................................................33 Installing AccessGate ..................................................................................34 Normal installation...................................................................................34 Rear support kit ......................................................................................35 Panel extender kit ...................................................................................36 Grounding AccessGate ................................................................................37 Ground cable requirements .......................................................................37 Connecting a ground cable........................................................................38
NMS Communications
Table of Contents
Chapter 5: Providing a DC power source ......................................................39 Power installation overview..........................................................................39 Power cable and tool requirements ...............................................................39 Assembling the power input connector ..........................................................40 Assembling the strain relief housing ..............................................................41 Installing the power connector .....................................................................43 Turning on power for the device ................................................................43 Chapter 6: Configuring and verifying the installation...................................45 Configuring and verifying with the AccessGate CLI ..........................................45 Verifying with the web interface ...................................................................46 Chapter 7: Connecting serial port, Ethernet, and alarm relay interfaces ......47 Cable connection overview...........................................................................47 Cable requirements ....................................................................................48 Connecting a serial port cable ......................................................................49 Serial port connector................................................................................49 Connecting Ethernet cables..........................................................................50 Ethernet connector ..................................................................................51 IP connection restrictions..........................................................................51 Connecting alarm dry relay contacts .............................................................52 Alarm dry relay contacts...........................................................................52 Chapter 8: Connecting T1/E1 interfaces ......................................................55 Connecting trunk cables ..............................................................................55 Device-to-device trunk connections ............................................................55 Sixteen-trunk front I/O variant trunk connectors..........................................55 Sixteen-trunk rear I/O variant trunk connectors...........................................56 Eight-trunk front and rear I/O variant trunk connectors ................................58 Connecting trunk cables ..............................................................................59 Device-to-device trunk connections ............................................................59 Sixteen-trunk front I/O variant trunk connectors..........................................59 Sixteen-trunk rear I/O variant trunk connectors...........................................60 Eight-trunk front and rear I/O variant trunk connectors ................................62 Connecting a BITS clock source ....................................................................63 BITS framing ..........................................................................................64 Trunk mapping for sixteen-trunk variants ......................................................65 Trunk mapping for eight-trunk variants .........................................................66 Trunk routing in bypass mode ......................................................................67 Trunk allocation in a bypass state ..............................................................67 Manually assigning virtual gateway trunk connections......................................68 Trunk allocation rules and recommendations ...............................................68 Planning trunk assignments ......................................................................69 Typical trunk configurations ......................................................................71 Chapter 9: Configuring 1+1 redundant devices............................................73 Overview of 1+1 redundancy .......................................................................73 Frequently used terminology .....................................................................73 Redundant configuration cabling requirements ...............................................74 AccessGate redundant failover .....................................................................76 Trunk mappings in redundant configurations ..................................................77 AccessGate sixteen-trunk variants .............................................................77 AccessGate eight-trunk variants ................................................................77
NMS Communications
Table of Contents
Setting up an AccessGate redundant configuration ..........................................78 Redundancy rules of operation .....................................................................80 Chapter 10: Replacing equipment...............................................................81 Equipment replacement overview .................................................................81 Removing an AccessGate 1000 device ...........................................................83 Configuring a replacement device .................................................................85 Replacing a protected device in a redundant configuration................................86 Replacing the protected device ..................................................................86 Chapter 11: Compliance, regulatory, and reference information ................87 Physical characteristics ...............................................................................87 Electrical requirements................................................................................88 DC input requirements .............................................................................88 Overcurrent protection requirements ..........................................................88 Power requirements .................................................................................88 Ground requirements ...............................................................................89 Environmental requirements ........................................................................90 Compliance and regulatory certification .........................................................91 Reference documents .................................................................................92 Chapter 12: Glossary ..................................................................................93
NMS Communications
1
This manual...
Introduction
The AccessGate 1000 Installation Manual describes how to install and verify the operation of AccessGate 1000 devices using AccessGate 3.0 firmware. This manual is intended for operators and administrators who install and configure NMS AccessGate 1000 equipment. The manual assumes a working knowledge of 2Gand 3G networks, local area networks, and wide area networks. The following manuals provide additional information about configuring, verifying, and monitoring AccessGate:
Provides information about... Configuring and monitoring AccessGate with the AccessGate command line interface (CLI) or web interface. Configuring and monitoring AccessGate with AccessView 3.0. Configuring and monitoring AccessGate with an SNMP client.
AccessGate Configuration Manual AccessView 3.0 User's Manual AccessGate SNMP Administration Manual
NMS Communications
Overview of AccessGate 1000
AccessGate 1000 product description

AccessGate 1000 aggregates data and performs bandwidth optimization processing that reduces the bandwidth required to transfer data over backhaul circuits in Abis, Ater, and Iub based GSM environments. TDM backhaul configurations Groups of AccessGate devices, operating within terrestrial leased line, satellite, and microwave-based RAN, optimize backhaul data in order to reduce the number of T1 or E1 backhaul trunks required. AccessGate devices can connect to multiple T1/E1 trunks at the BSC and BTS, optimize the data transferred to and from TDM connections, and relay the optimized stream over the backhaul through a smaller number of T1/E1 trunks. The following illustration shows AccessGate devices in a TDM backhaul configuration:
T1/E1 links
AccessGate 1000
BTS
T1/E1 links
Circuit switched network T1/E1 links AccessGate 1000 T1/E1 links
BSC
TDM backhaul
This enables operators to reduce costs by minimizing the number of backhaul links they lease to accommodate backhaul traffic.
NMS Communications
IP backhaul configurations AccessGate devices can connect to multiple T1/E1 trunks at the BSC and BTS, optimize the data transferred to and from an IP network connection, and relay the optimized stream over the backhaul using reduced IP bandwidth. The following illustration shows AccessGate devices in an IP backhaul configuration:
T1/E1 links
BTS
AccessGate 1000 Ethernet link
Packet switched network Ethernet link AccessGate 1000 T1/E1 links
BSC
IP backhaul
Note: AccessGate devices in TDM backhaul configurations and device in IP backhaul configurations require different AccessGate firmware. The following restrictions apply when configuring AccessGate IP backhaul network elements: There must be one virtual gateway on the AccessGate BSC device for each AccessGate BTS device connected over the IP backhaul. The cell site location must have access to a high-precision clock source. Otherwise, the data transferred over the backhaul connection can experience quality degradation in the form of packet underruns or overruns. On the AccessGate BSC device, the Ethernet 1 connection used for transferring IP backhaul data can also be used for monitoring or controlling the AccessGate 1000 device through an IP connection (for example, with the AccessGate web interface or AccessView). The Ethernet 2 connection can be used for monitoring or controlling the AccessGate 1000 device, but not for transferring IP backhaul data. When the Ethernet 2 connection on the AccessGate 1000 BSC device is used for monitoring and controlling the AccessGate, the Ethernet 1 connection and Ethernet 2 connection must be on different IP subnets. Redundant 1+1 configurations are not supported for IP backhaul configurations.
Virtual gateways AccessGate 1000 devices can be configured to support multiple virtual gateways per AccessGate BSC device. This allows a single BSC device to connect to multiple BTS devices in one-to-many topologies. In TDM backhaul configurations, a virtual gateway can consist of up to ten service trunks and up to six backhaul trunks. In IP backhaul configurations, a virtual gateway can consist of up to ten service trunks whose optimized data is transferred over an IP backhaul link.
10
NMS Communications
The following illustration shows an AccessGate 1000 BSC device using virtual gateways to connect to two AccessGate 1000 BTS devices (in 3:2 configurations) over TDM backhaul links:
BTS
AccessGate 20XX
AccessGate Virtual gateways
Network
LAN
AccessGate 20XX
AccessGate
BSC
BTS
AccessGate 20XX
Backhaul
AccessGate
The following table shows the configuration restrictions for AccessGate 1000 devices:
Configuration type TDM backhaul IP backhaul TDM backhaul IP backhaul AccessGate variant 16-trunk AG 1016 16-trunk AG 1016 8-trunk AG 1008 8-trunk AG 1008 Maximum number of virtual gateways 7* 8 3 5 Maximum number of trunks for a virtual gateway (service:backhaul) 10:6 10:IP 5:3 5:IP
*If you have an AG 1016 HF5001, the maximum number of virtual gateways is 8. Note: When an AccessGate BSC device connects to a single AccessGate BTS device, only one virtual gateway is required (virtual gateway 0) to manage the traffic between the two devices.
NMS Communications
11
Terminology
The following specialized terms are used in this document: AccessGate network locations Backhaul and service trunks In-path and bypass states Protected and unprotected trunks
AccessGate network locations AccessGate devices can be deployed in networks that implement Abis, Ater, or Iub data transmission. Within these networks, different terms apply to the network locations where the AccessGate devices are installed. This document primarily uses the terminology used for Abis networks when describing the AccessGate network locations. The following table shows the corresponding terminology used to describe installation locations in networks that use Ater and Iub data transmission:
Data transmission Abis Ater Iub AccessGate parent node location BSC TCU RNC AccessGate child node location BTS Remote-BSC (R-BSC) Node B
The following illustration shows AccessGate devices in networks that use Abis, Ater, and Iub transmission:
BTS device BSC device Backhaul AccessGate BSC TRAU MSC
Abis transmission
BTS
AccessGate
R-BSC device
TCU device Backhaul AccessGate TRAU MSC
Ater transmission
BTS
BSC
AccessGate
NodeB device
RNC device Backhaul AccessGate RNC
Iub transmission
Node B
AccessGate
Backhaul and service trunks Trunks connected to AccessGate 1000 are referred to as backhaul trunks or service trunks as described in the table below:
Trunk type Backhaul Service Description Transfers traffic between remote BTS and BSC locations. Connects the AccessGate device to the Abis, Ater, or Iub interface of a BTS or BSC.
12
NMS Communications
In-path and bypass state The normal operating state for AccessGate 1000 is the in-path state. In this state, AccessGate 1000 reduces backhaul bandwidth by consolidating service trunk data onto a reduced number of backhaul trunks. AccessGate 1000 can also operate in a bypass state. When in the bypass state, AccessGate 1000 transfers data through the device without performing any processing operations. When either AccessGate device in a network element goes into bypass, its peer device also transitions to bypass mode. AccessGate 1000 can transition to the bypass mode under the following conditions:
Bypass conditions Absence of communication between AccessGate BSC and BTS devices Example AccessGate BSC and BTS devices can lose backhaul communication under any of the following conditions:
Mismatched configurations (system or trunk level parameters) between the AccessGate BSC and BTS devices. The AccessGate BTS or the BSC device is powered down. All backhaul trunks fail between the AccessGate BSC and the BTS device.
Explicit configuration to enter into a bypass state
You can configure AccessGate 1000 to remain in forced bypass mode through any of the following methods:
Configuration through the AccessGate command line interface. Configuration with an SNMP client. Configuration with the AccessView application.
For more information, refer to Trunk allocation in a bypass state on page 67. Auto versus forced bypass mode You can configure AccessGate 1000 to operate in either of two modes that determine the state under particular conditions.
Mode Auto Description AccessGate 1000 devices remain in the bypass state until they detect their BTS or BSC peer in the AccessGate network element. If there are no critical alarms and if the two configurations are correct, the devices transition to an in-path state when the devices detect their peer. AccessGate 1000 remains in the bypass state until commanded to go in-path through the AccessGate command line interface or AccessView.
Forced bypass
Protected and unprotected trunks

Trunk type Protected trunk Unprotected trunk Description A service trunk connected to an AccessGate device that remains active and continues to transfer data even when the device goes into bypass. A service trunk connected to an AccessGate device whose data is interrupted when the device goes into bypass.
NMS Communications
13
AccessGate 1000 sixteen-trunk variants

AccessGate 1000 is available in front and rear I/O variants with sixteen-trunk interfaces. Sixteen-trunk front I/O variant The AccessGate 1000 sixteen-trunk front I/O variant provides a power connector, T1/E1 trunk connectors, Ethernet connectors, alarm cut-off (ACO) switch, alarm connectors, a serial port connector and all trunk, Ethernet, and status LEDs on the front panel. The following illustration shows the front panel of an AccessGate 1000 sixteen-trunk front I/O variant:
Trunk connectors Ethernet connectors ACO switch
!
16 15 14 13 12 11 10 9 7 ~8 5 ~6 3 ~4 1 ~2 2
ETHERNET 1
ACO
SILENCE
1 2
ACT 100 MB
2 4 6 8 10 12 14 16
RESET FAULT STANDBY OK
- +- +
VISUAL
AUDIBLE
1 3 5 7 9 11 13 15
AccessGate Power connector Alarm connector Ground studs
Serial port connector
Ethernet LEDs
Trunk LEDs
Status LEDS
The following illustration shows the rear panel of an AccessGate 1000 sixteen-trunk front I/O variant:
Ground studs
14
NMS Communications
Sixteen-trunk rear I/O variant The AccessGate sixteen-trunk 1000 rear I/O variant provides a serial port connector, ACO switch, and all trunk, Ethernet, and status LEDs on the front panel. The device power connector, alarm connectors, Ethernet connectors, BITS clock connector, and T1/E1 trunk connectors reside on the rear panel. The following illustration shows the front panel of an AccessGate 1000 sixteen-trunk rear I/O variant:
ACO switch
ACO
1 2
ACT 100 MB
2 4 6 8 10 12 14 16
RESET
1 3 5 7 9 11 13 15
FAULT STANDBY OK
AccessGate
Ethernet LEDs
Trunk LEDs
Status LEDS
The following illustration shows the rear panel of an AccessGate 1000 sixteen-trunk rear I/O variant:
Ethernet connectors
ETHERNET 2 1 FAULT STANDBY OK 16 BITS
- + - +
VISUAL
AUDIBLE
Trunks
Trunks
Power connector
Alarm connectors
BITS clock connector
Trunk connectors
NMS Communications
15
AccessGate 1000 eight-trunk variants

AccessGate 1000 is available in front and rear I/O variants with eight-trunk interfaces. Eight trunk front I/O variant The AccessGate 1000 eight-trunk front I/O variant provides a power connector, T1/E1 connectors, Ethernet connectors, alarm cut-off (ACO) switch, alarm connectors, a serial port connector and all trunk, Ethernet, and status LEDs on the front panel. The following illustration shows the front panel of an AccessGate 1000 eight-trunk front I/O variant:
Trunk connectors Ethernet connectors ACO switch
!
8 7 6 5 4
ACT 100 MB
ACO
3 1 2
2 1 2 4 6 8
ETHERNET 1
SILENCE
- +- +
VISUAL
1 3 5 7
RESET
FAULT STANDBY OK
AUDIBLE
AccessGate Power connector Alarm connector Ground studs
Ethernet LEDs
Trunk LEDs
Status LEDS
The following illustration shows the AccessGate 1000 eight-trunk front I/O variant rear view:
Ground studs
16
NMS Communications
Eight-trunk rear I/O variant The AccessGate eight trunk 1000 rear I/O variant provides a serial port connector, ACO switch, and trunk, Ethernet, and status LEDs on the front panel. The device power connector, alarm connectors, Ethernet connectors, BITS clock connector, and T1/E1 trunk connectors reside on the rear panel. The following illustration shows the AccessGate 1000 eight-trunk rear I/O variant front view:
ACO switch
ACO
1 2
ACT 100 MB
2 4 6 8
RESET
1 3 5 7
FAULT STANDBY OK
AccessGate
Ethernet LEDs
Trunk LEDs
Status LEDS
Ground studs
The following illustration shows the AccessGate 1000 eight-trunk rear I/O variant rear view:
B A
- + - +
VISUAL ETHERNET 2 1 AUDIBLE FAULT STANDBY OK
Power connector
Alarm connectors
Ethernet connectors
Status LEDS
Trunk connectors
Ground studs
NMS Communications
17
Connectors
AccessGate 1000 equipment provides the following physical interfaces:
Connector Serial port connector: Female D-sub DB9F Trunk connectors: RJ-48C or RJ-48M trunk T1/E1 connectors Variant dependent AccessGate 1000 variants provide the following T1/E1 trunk interfaces: Connector 16 trunk front I/O Description Quantity 1 Description Provides connectivity for performing initial configuration and diagnostic tasks.
Eight single RJ-45 single trunk E1/T1 interfaces. Four NMS RJ-45 dual trunk E1/T1 interfaces.
16 trunk rear I/O 8 trunk front I/O 8 trunk rear I/O
Two RJ-48M trunk T1/E1 interfaces (each providing an interface for eight trunks). Eight single RJ-45 single trunk E1/T1 interfaces. Eight single RJ-45 single trunk E1/T1 interfaces.
For more information, refer to AccessGate 1000 sixteen-trunk variants on page 14 and AccessGate 1000 eight-trunk variants on page 16. Ethernet connectors: RJ-45 dual 10/100Base-T 2 Provide Ethernet connectivity for the following:
AccessGate 1000 management and monitoring tasks AccessGate IP backhaul data transmission BTS private subnet access.
When using DHCP, only one Ethernet connector is active. For information about configuration-specific Ethernet interface assignments, refer to Connecting Ethernet cables on page 50. Alarm dry relay contacts: DB-9M Power connector Lug mount studs Clock connector: DB-9F BITS (16 trunk rear I/O only) 1 2 1 Provides ports for two redundant power feeds with a nominal 24 V DC or -48 V DC voltage. Provide front and rear ground connection for the equipment. Provide two BITS clock source for 16 trunk rear I/O device. 2 Provide interfaces between AccessGate 1000 and an external alarm system for visual and audible alarms.
18
NMS Communications
ACO switch
The AccessGate 1000 rear I/O alarm cut-off (ACO) switch silences the AccessGate 1000 audible alarm indicator by temporarily disabling the audible alarms. You can use the ACO switch to perform the following tasks: Silence any active audible alarms while allowing any new alarms to activate the audible alarm indications. Indefinitely silence all audible alarms until you re-enable the audible alarm relay for existing alarms.
ACO switch operation The ACO switch can be switched in the following positions:
ACO switch position Up (ACO) Description Suppresses any existing audible alarms and then springs back to the middle position. If the AccessGate device detects any new audible alarms, the device generates an audible alarm. Therefore the ACO position is useful for performing a one-time clear of audible alarm relays. AccessGate device alarms are not deleted or acknowledged and are still active internally. The effect is to temporarily disable the hardware audible relay. The alarm relay is cleared until a new alarm triggers it again. Middle Down (SILENCE) Does not alter normal audible relay behavior. Suppresses any active audible alarms and remains in the down position until switched back to the middle position. As long as the switch is down, audible alarms are suppressed. The downward switch position temporarily disables the hardware audible relay, but does not delete or acknowledge any AccessGate device alarms. Any active alarms remain internally active and trigger audible alarms when the switch returns to the middle position.
Note: Switching the ACO switch from the middle position down and then up restores the AccessGate audible alarm relays from ACO mode to normal operating mode. For more information, refer to ACO LED on page 21.
NMS Communications
19
LED indicators
AccessGate 1000 equipment has the following indicators: Status LEDs Trunk LEDs Ethernet LEDs ACO LED
Status LEDs Each AccessGate 1000 device has green, red, and yellow LEDs to indicate status conditions.
FAULT
Status LEDs
STANDBY OK
Status LEDs provide the following indications:

LED Fault Standby OK Color Red Yellow Green Description When on, the AccessGate 1000 device is experiencing one or more alarm conditions. When off, no alarm condition exists. When on, the AccessGate 1000 device is in the bypass state. When off, the AccessGate 1000 device is in the in-path state. When on, indicates that the AccessGate 1000 device is running without faults. When off, the LED indicates either the AccessGate 1000 device is experiencing alarm conditions or is not receiving power.
Trunk LEDs Each AccessGate 1000 device has a pair of green LEDs for each service-side trunk. Only LEDs for available trunks are active (sixteen-trunk version shown below).
2 Trunk LEDs 1 3 5 7 9 11 13 15 4 6 8 10 12 14 16
Trunk LEDs provide the following indications:

LED color Green Red Yellow NA LED action On Slow blink Fast blink Off Description Trunk is configured and working properly. Trunk is configured, but it is in a loss-of-signal (LOS) or loss-of-frame (LOF) condition. Trunk is configured, but it is receiving remote alarm indications (RAI). Trunk not configured.
20
NMS Communications
Ethernet LEDs Each AccessGate 1000 device has two green LEDs to indicate the status of each Ethernet link.
Ethernet LEDs 1 2 ACTIVITY 100MB
These LEDs provide the following indications:

LED ACTIVITY 100MB Description Activity on the Ethernet link. When the Ethernet link has established link integrity and is transmitting or receiving data on the link, the LED blinks off and on. Data rate of the Ethernet link. When the LED is on, the data rate is 100 megabits per second. When the LED is off, the data rate is 10 megabits per second. The LED is active only when a reliable Ethernet connection is established.
ACO LED The ACO LED provides a single yellow LED to indicate the status of the audible indicators on an AccessGate 1000 device.
ACO ACO LED SILENCE
The AccessGate 1000 ACO LED provides the following indications:

LED activity On Description ACO switch LED indicators vary depending on the ACO switch position:
When the switch is in the down (Silence) position, a solid lit LED means alarms are present. When the switch is in the middle position after having been in the up (ACO) position, a solid lit LED indicates that alarms are still present that were present before the switch was moved to the ACO position. Any new alarms cause the LED to flash.
Off Flashing
No alarms are present, the audible relay is off. Alarms are present and the audible relay is active. When the switch is in the middle position after having been in the up (ACO) position, a flashing LED indicates that new alarms were generated since the switch changed position.
For more information, refer to ACO switch on page 19.
NMS Communications
21
3
Tool
Preparing for installation
Required tools
Installing AccessGate 1000 equipment requires the following tools:
Used for... Securing the AccessGate device to a frame. Securing panel extenders or rack mount guides to the device. Removing and securing the ground lug to the device.
#2 Phillips tip screwdriver #1 Phillips tip screwdriver Full cycle ratchet with 8 mm hexsocket fitting Recommended: M8 nutdriver, Xcelite Regular-drilled shaft Crimp tool Recommended: Palladin CrimpAll with 2031.1 die set Metric slotted screwdriver with 3.5 mm blade Recommended: Wiha 32015
Attaching a ground cable to the ground lug.
Assembling the power connector strain relief housing (optional) and securing the power connector to the device.
NMS Communications
23
Computer requirements
Use a PC or laptop computer to perform initial configuration and to run diagnostics for AccessGate 1000 equipment. The computer must meet the following requirements:
Requirement Serial port connectivity Terminal emulator software Description Use a straight-through DB-9M cable to connect the PC or laptop computer with the serial port connector on the AccessGate device. Configure the terminal emulator software on the PC or laptop to run with the following settings: Category Bits per second Data bits Parity Stop bits Flow control Terminal emulation Web access (Optional) Setting 115200 8 None 1 None ANSI
Use a 10/100Base-T Ethernet cable to connect from the Ethernet connector on the AccessGate device to a local LAN. The PC or laptop must be running web browser software (Firefox recommended) and have access to the same LAN as the AccessGate device.
24
NMS Communications
Unpacking and inspecting the equipment

When unpacking AccessGate 1000 equipment, perform the following tasks: Observe the condition of the shipping container and inspect the equipment for any signs of external damage. Compare the bill of lading with the delivered equipment, and specify on the bill of lading any discrepancies or damage. Compare the packing list with the equipment received. Make sure that you received all of the equipment that is specified and that it is listed on the packing slip. Make sure that the model and part numbers match the numbers displayed on the equipment. If there are any discrepancies, contact your support representative.
AccessGate 1000 device kit The AccessGate 1000 device kit contains: One AccessGate 1000 front I/O or rear I/O device One power supply input connector with optional connector strain relief housing One ground lug Note: M5 8 mm kep nuts are attached to front and rear panel. One screw kit that contains four optional screw sets for securing the device to a frame: 4 10-32 x 1/2" Phillips head screws 4 10-24 x 1/2" Phillips head screws 4 M6-1 x 12 mm Phillips head screws 4 12-24 x 1/2" Phillips head screws AccessGate 1000 documentation set that includes: AccessGate 1000 installation sheet Declaration of Conformity Software revision sheet
NMS Communications
25
The following illustration shows the AccessGate 1000 kit:
AC TIV 10
T IY
0 Mb
2
OK FA S TAN UL T D BY
Screw kits
Ac c es sG ate
Power connector Strain relief housing
Ground lug
AccessGate 1000 panel extender kit (optional) The AccessGate 1000 panel extender kit [P/N 2850-34028] extends the width of the device (19 inches or 49.2 cm) for installation into a 23 inch (58.4 cm) frame. The panel extender kit includes:
Item Device panel extenders Panel extender screws Quantity 2 4
For information, refer to Assembling the panel extender mounting kit on page 32. AccessGate 1000 rear support kit (optional) The AccessGate 1000 rear support kit includes brackets and guides for providing additional support for the back end of AccessGate device when rear support is not provided by the rack in which it is installed. The rear support kit includes:
Item Device side mounting guide Device side mounting guide screw kit Frame rack rear mount bracket Frame rack rear mount bracket screws Quantity 2 4 2 4
For more information, refer to Assembling the rear support kit on page 33.
26
NMS Communications
Summary of the installation procedure

Before installing AccessGate 1000 equipment at BSC or BTS locations, consider the following recommendations: Pairs of AccessGate 1000 BSC and BTS devices in the same network element must be configured according to the same operating parameters. Failure to configure compatible settings for the AccessGate BSC and BTS devices can disrupt communication between them. Save and maintain a copy of the most current configuration of each device for future reference. If you need to replace equipment at a BSC or BTS site, use a copy of the most current configuration to configure the replacement equipment and to ensure that the AccessGate 1000 devices at both facilities have compatible parameter settings. For more information about viewing the current configuration parameters, refer to the AccessGate Configuration Manual. NMS Communications recommends that you first install AccessGate 1000 equipment at the BSC site and use a local crossover cable to test the backhaul communication between the AccessGate BSC and BTS devices. This ensures that when both devices are properly installed, the backhaul link will support communication between the two devices.
The AccessGate 1000 installation procedure includes the following steps:

Step 1 Action Unpack and inspect the AccessGate 1000 equipment and assemble required tools. Refer to... Unpacking and inspecting the equipment on page 25 Required tools on page 23 2 3 Install the AccessGate 1000 device into a system frame and ground the device. Connect a ground cable and power cables to the AccessGate 1000 device; power up the equipment. Connect the serial port cable necessary for running hardware diagnostics and configuring the device. Run hardware diagnostics. AccessGate installation overview on page 31 Power installation overview on page 39
Configuring and verifying with the AccessGate CLI on page 45 Configuring and verifying with the AccessGate CLI on page 45 Cable connection overview on page 47
Configure the equipment with AccessGate command line interface, and create required virtual gateways. Record the parameter settings for future reference. Connect the following cables to the AccessGate 1000 device:
Trunk cables Ethernet cable (as appropriate) Alarm cables (optional) BITS clock cables
Use AccessGate 1000 tools to verify and monitor the status of the AccessGate equipment at the BSC and BTS sites and to monitor the data transferred between them.
Configuring and verifying with the AccessGate CLI on page 45
NMS Communications
27
For recommendations about the sequence and method used to install pairs of AccessGate 1000 BSC and BTS devices, refer to Global installation recommendations on page 29. Safety precautions When installing AccessGate 1000 equipment, follow general safety precautions as they apply to your site to prevent injury to personnel or damage to equipment.
Warning: Authorize only trained personnel familiar with installing high energy DC electrical equipment to install AccessGate 1000 equipment. Use non-magnetic insulated tools or apply at least two layers of electrical tape to the handles of metal tools when working around live equipment. If using a metal tape measure, be cautious around live equipment. Avoid electrostatic discharge (ESD) damage to electronic circuits by observing antistatic precautions. Ensure that the installation meets all government codes and regulations concerning facilities. In addition, all sites where AccessGate 1000 equipment is deployed must meet all local, national, and international codes covered in this specification. The subjects covered include fire and safety, building, and electrical codes. If using reels when installing cables, protect floors, carpets, or adjacent equipment from damage by covering with sheets of heavy cardboard, hardboard, or similar material.
Caution:
28
NMS Communications
Global installation recommendations

The following recommendations assume that the AccessView application is installed and running on a computer that has access to the LAN associated with the AccessGate 1000 BSC device. When installing AccessGate 1000 equipment, the following installation sequence is recommended:
Step 1 Site BSC Description Install AccessGate BSC device at the BSC site, provide a ground connection, and turn the power on. Refer to... AccessGate installation overview on page 31 Power installation overview on page 39 2 BSC Using the AccessGate command line interface: Configuring and verifying with the AccessGate CLI on page 45
Configure AccessGate BSC device settings. Configure virtual gateways to connect to other AccessGate BTS devices.
If the BSC site is configured in auto mode (the default mode), it transitions to the in-path state as soon as it detects a BTS peer across the backhaul connection. 3 BSC Connect an Ethernet cable from the Ethernet connector 1 to the local LAN. In IP backhaul configurations you can also connect a cable from Ethernet connector 2 to the LAN. Use a web browser to test IP connectivity to the AccessGate BSC device by viewing the status information for the BSC device with the browser. Connect T1 or E1 trunks to the AccessGate BSC device in a way that is consistent with the AccessGate BSC configuration and virtual gateway trunk mapping. Install one or more AccessGate BTS devices according to the instructions in steps 1 through 5. Use the AccessGate command line interface to configure each AccessGate BTS device with configuration parameters compatible with those configured on the AccessGate BSC device (with the exception of the device type, which should be BTS rather than BSC). Trunk mappings for TDM backhaul trunks on AccessGate BTS device virtual gateways and the associated AccessGate BTS device must follow the trunk mapping rules outlined in Trunk allocation rules and recommendations on page 68. 8 BTS In TDM backhaul configurations, connect T1 or E1 trunks to the AccessGate 1000 BTS device as appropriate for the AccessGate BTS configuration. Note: The backhaul trunks on the AccessGate BTS must be connected in the same incremental order as backhaul trunks on the associated AccessGate BSC device. Connecting Ethernet cables on page 50 Verifying with the web interface on page 46 Connecting trunk cables on page 55 See steps 1 through 5 Configuring and verifying with the AccessGate CLI on page 45 Connecting trunk cables on page 55
BSC
BSC
6 7
BTS BTS
Connecting trunk cables on page 55
NMS Communications
29
Step 9
Site BTS
Description Use the AccessGate command line interface at the BTS site to test backhaul communication between the AccessGate device at the BTS and the AccessGate device at the BSC site. Inform administrators at the BSC location that an AccessGate device is installed at the BTS and can communicate with its BSC peer. Use AccessView (recommended) or a web browser to view status information for the AccessGate devices at the BSC and BSC locations. For this to take place, the AccessGate device must be connected to a common LAN through an Ethernet connection and the two devices must be communicating data through a backhaul link. If you initially set the operating mode of the AccessGate BSC device to forced bypass (see Step 2), use AccessView (recommended) or the AccessGate command line interface to change the operating mode of the AccessGate BTS device from forced bypass to auto mode when you are prepared to initiate AccessGate data processing. Use AccessView (recommended) or a web browser to view the processing state of all AccessGate virtual gateways associated with the AccessGate network element to ensure that both are in an inpath state.
Refer to... Configuring and verifying with the AccessGate CLI on page 45
10 11
BTS BSC
AccessView 3.0 User's Manual
12
BSC
13
BSC
30
NMS Communications
4
If you are...
Installing AccessGate in a frame
AccessGate installation overview

Use the following table to determine which tasks to perform when installing an AccessGate 1000 device into a frame:
Refer to Installing AccessGate on page 34 Grounding AccessGate on page 37 Assembling the panel extender mounting kit on page 32 Installing AccessGate using the panel extender kit on page 36 Grounding AccessGate on page 37 Installing AccessGate 1000 in a frame without a rear support. Assembling the rear support kit on page 33 Installing AccessGate using the rear support kit on page 35 Grounding AccessGate on page 37
Installing AccessGate 1000 in a 19 inch frame with a rear support. Installing AccessGate 1000 in a 23 inch frame with a rear support.
NMS Communications
31
Assembling the panel extender mounting kit

The AccessGate 1000 panel extender kit extends the width of the device (19 inches or 49.2 cm) for installation into a 23 inch (58.4 cm) frame. Complete the following procedure to secure the AccessGate 1000 panel extenders to the device:
Step 1 2 Action Align the screw holes on one side of the AccessGate device with those on the panel extender bracket. Insert the panel extender screws through holes in the AccessGate wing brackets and the extender brackets. Tighten the screws with a #2 Phillips screwdriver to 12 lbf-in (1.4 Nm) of torque.
#2 Phillips
12 lbf-in (1.4 Nm)
Repeat steps 1 and 2 with the exterior bracket for the opposite side of the AccessGate device.
32
NMS Communications
Assembling the rear support kit

The AccessGate 1000 rear support kit provides additional support for the back end of the AccessGate device when rear support is not provided by the rack in which it is installed. Complete the following procedure to secure the side mounting guides to the device and the mounting brackets to the frame:
Step 1 Action Using a #2 Phillips screwdriver, secure a side-mounting guide to each side of the device by inserting and tightening the supplied screws.
Screws
Side mounting guides
Screws
#2 Phillips 12 lbf-in (1.4 Nm)
Using a #1 Phillips screwdriver, secure the rear support mounting brackets to the frame by inserting the supplied screws and washers through the mounting bracket into the rear of the frame. Tighten the screws.
Mounting bracket
Screws
Mounting bracket
Screws
#1 Phillips
NMS Communications
33
Installing AccessGate
Before installing the AccessGate 1000 device, refer to Summary of the installation procedure on page 27 and Required tools on page 23. Make sure to choose a screw kit appropriate for the frame. For more information about mount screw kits available for the AccessGate 1000, refer to Unpacking and inspecting the equipment on page 25. Choose one of the following installations: Normal installation (19 inch frame without rear support kit or panel extenders) Panel extender kit (23 inch frame with panel extenders) Rear support kit (19 inch frame with rear support kit)
Note: The torque value for tightening mount screws into a frame depends on the frame model and manufacturer. For more information, refer to the manufacturer specifications.
Warning: When securing the device to the frame, using screws that are the incorrect size can result in an improper installation and strip the frame screw holes. For information about the appropriate mount screw size and type for the frame, refer to the frame manufacturer specifications.
Normal installation Complete the following steps to install an AccessGate 1000 device into a 19 inch frame:
Step 1 Action Carefully insert the device into the frame.
Guide
#1 Phillips
Screws
2 Insert the appropriate size mount screws into the holes in the device front panel brackets. Tighten the screws into the frame holes with a #1 Phillips screwdriver.
34
NMS Communications
Rear support kit Complete the following steps to install an AccessGate 1000 device into a frame using the rear support kit:
Step 1 Action Insert the device into the front of the frame, making sure that the mounting guides on each side of the device slide between the guides located on the rear support brackets.
Guides Guide
Guides
#1 Phillips
Guide Screws
2 Insert the appropriate size mount screws into the holes in the front panel brackets. Tighten the screws into the frame holes with a #1 Phillips screwdriver.
NMS Communications
35
Panel extender kit Complete the following steps to install an AccessGate 1000 device with panel extenders into a 23 inch frame:
Step 1 Action Carefully insert the device into the frame.
#1 Phillips
Chassis screw kit
Insert the appropriate size mount screws into the holes in the panel extenders. Tighten the screws into the frame holes with a #1 Phillips screwdriver.
36
NMS Communications
Grounding AccessGate
AccessGate 1000 devices must be connected to an earth or frame ground. The recommended safety grounding point is the two-hole ground lug. The ground lug is attached to the AccessGate 1000 front or rear panel near the power connector. Ground the AccessGate 1000 device by terminating a ground conductor at the twohole ground lug.
Warning:
Authorize only trained personnel familiar with installing high energy DC electrical equipment to install the AccessGate 1000 device. Use non-magnetic insulated tools or apply at least two layers of electrical tape to the handles of metal tools when working around live equipment. If using a metal tape measure, be cautious around live equipment.
Caution:
Ensure that the installation meets all government codes and regulations concerning facilities. In addition, all sites where AccessGate 1000 devices are deployed, must meet all local, national, and international codes described in Compliance and regulatory certification on page 91, including fire, safety, building, and electrical codes.
Ground cable requirements Cables used to provide a ground connection for an AccessGate 1000 device must meet the following requirements: Cable must be green or green with yellow tracer. Per NEC2002, no ground conductor for communications equipment shall be less than 14 AWG. Cables must be consistent with fire-spread characteristics for the deployment location: Plenum ANSI/UL910 Riser - ANSI/UL 1666 (requirement found in ANSI T1.307)
NMS Communications
37
Connecting a ground cable Complete the following steps to ground the AccessGate 1000 device:
Step 1 2 3 4 Action Insert a grounded cable into the open end of the AccessGate 1000 right-angled ground lug. Use a crimping tool to crimp the cable securely into the ground lug. Remove the hex nuts connected to the ground mounting screws on the AccessGate 1000 front or rear panel. Connect the ground lug to the device by sliding it onto the exposed ground mounting screws and tightening the hex nuts onto the device.
Ground lug Hex nuts
Crimp Ground stud
Crimp 8 mm Ground cable 26 lbf-in (2.9 Nm)
Connect the free end of the ground cable to an earthing bar located near the equipment.
38
NMS Communications
Providing a DC power source
Power installation overview

This section provides the following information about providing a DC power source for an AccessGate 1000 device: Power cable and tool requirements Assembling the power input connector Assembling the strain relief housing (optional) Installing the power connector
Power cable and tool requirements

The following requirements apply to the cables used to deliver power to AccessGate 1000 device: Strip length for the wires is 7 mm. 12 AWG or heavier wire gauge. Consistent with the following fire-spread characteristics for the deployment location: Plenum ANSI/UL910 Riser - ANSI/UL 1666 (requirement found in ANSI T1.307)
Meet appropriate IPC specifications for cable construction.
Assembling and installing the AccessGate 1000 power input connector requires a 3.5 mm slotted screwdriver. For more information, refer to Electrical requirements on page 88 and Required tools on page 23.
NMS Communications
39
Assembling the power input connector

Warning: Do not connect live power feeds to AccessGate 1000 equipment. Connect only power cables that have been disabled through fuses or circuit breakers. Once the power cables are connected to the AccessGate 1000 equipment, you can enable the power source.
Complete the following steps to connect power to the AccessGate 1000 device:
Step 1 2 3 4 Action Disable the power cables for the AccessGate device by removing the associated fuses or opening the associated circuit breakers. Strip 7 mm of insulation from the end of each wire of a redundant DC power source. Feed the exposed end of a wire into the appropriate hole in the front of the DC power input connector. Using a 3.5 mm slotted screwdriver, tighten the slotted head screw on the DC power input connector directly above the inserted wire.
7 mm
4.5 lbf-in (0.5 Nm)
_ + _ +
5 6
Repeat steps 3 and 4 for each wire of the redundant power supply until all cables for the redundant power supply are secure within the power input connector. If you are using the provided strain relief housing, secure the DC input cables and assemble the strain relief housing around the power input connector as described in Assembling the strain relief housing on page 41.
For information, refer to Installing the power connector on page 43.
40
NMS Communications
Assembling the strain relief housing

The input power connector strain relief housing reduces the amount of tension on the power cables at the connection point to the AccessGate device. Complete the following steps to assemble the strain relief housing:
Step 1 2 Action Remove the cable brace from the bottom portion of the strain relief housing by unscrewing the screws and lifting the metal brace. Insert an input power connector with attached power cables into the notches in the bottom section of the strain relief housing. For more information, refer to Assembling the power input connector on page 40. Secure the power input cables by reattaching the cable brace over the connected power cables. Secure the brace to the bottom section of the strain relief housing by tightening the screws.
Input power connector
Cable brace
4.5 lbf-in Notches Strain relief housing (bottom) (0.5 Nm)
NMS Communications
41
Step 4
Action Lower the top section of the strain relief housing onto the lower section of the housing. The notches on the top section hold the input power connector in place, and the prongs on the top and bottom sections snap into place.
Strain relief housing (top)
Notches
Prongs
Input power connector
Strain relief housing (bottom)
The assembled input power connector with strain relief housing is shown in the following illustration:
Power input connector with strain relief housing
For information, refer to Installing the power connector on page 43.
42
NMS Communications
Installing the power connector

Complete the following steps to install the power connector and power up the AccessGate 1000 device:
Step 1 Action Carefully slide the assembled power input connector into the AccessGate 1000 power connector in the front or rear panel.
Chassis power connector
- +- +
Power input connector
Using the metric slotted screwdriver, tighten the slotted head screws on both sides of the power input connector.
4.5 lbf-in (0.5 Nm)
Turning on power for the device Turn on the power for an AccessGate device by enabling the associated fuse or circuit breaker for the DC power source. AccessGate status LEDs blink intermittently as the device boots and powers up. Note: If you choose, you can run AccessGate command line hardware diagnostics for the device at this point. To run diagnostics, start a terminal emulator program on a PC or laptop computer and connect a straight-through cable from the device serial port connector to the computer. For more information, refer to Computer requirements on page 24.
NMS Communications
43
Configuring and verifying the installation
Configuring and verifying with the AccessGate CLI

AccessGate provides a command line interface (CLI) for configuring and monitoring AccessGate configuration, status, and log information. For information about using the AccessGate CLI or AccessGate web interface to monitor or configure AccessGate, refer to the AccessGate Configuration Manual. To use the AccessGate CLI:
Step 1 Action Start a terminal emulator program (such as HyperTerminal) on the PC or laptop computer. Make sure the terminal emulator program is configured according to the settings described in Computer requirements on page 24. Note: Only one terminal can be connected to a serial port on the AccessGate device at the same time.
AccessGate 1000
Serial port connector Serial port cable

An illusion that exalts us is more dear to us then a thousand sober truths...
Laptop running terminal emulator
Connect a straight-through serial cable from the computer to the AccessGate 1000 serial port connector and refresh the screen of the terminal emulator before entering a carriage return. The CLI displays the following menu in the terminal emulator window: Top-level menu. Please select: 1: Display current configuration 2: Configure AccessGate 3: Display status 4: Hardware diagnostics 5: Test backhaul OAM link 6: Manage/Test alarms 7: Reboot AccessGate 8: Restore factory defaults 9: Clone firmware from peer AccessGate 10: Chat with peer AccessGate 11: Dump system log 12: Change admin password 13: Alarm Cut-off
NMS Communications
45
Configuring and verifying the installation
Step 3
Action Select the appropriate CLI main menu option to perform the following tasks: Menu Option Hardware diagnostics Configure AccessGate Test backhaul OAM link Display status Display current configuration Description Run hardware diagnostics for the AccessGate device. Configure the AccessGate BSC or BTS device. To run the AccessGate configuration wizard, select Wizard from the displayed configuration menu. Test backhaul connectivity between the devices. View status information for the devices Confirm configuration settings for the devices.
For more information about verifying AccessGate settings and status information with the AccessGate interface, refer to the AccessGate Configuration Manual.
Verifying with the web interface

AccessGate provides a web interface through which you can view AccessGate configuration, status, and log information. To view AccessGate device information with a web browser:
Step 1 2 Action Start a web browser that has access to the same LAN to which the AccessGate device is connected. In the web browser address bar, enter a URL containing the IP address assigned to the AccessGate 1000 BSC device. A web page appears for the specified AccessGate device that displays hardware information for the device on the right, and a list of device-specific links on the left. 3 4 Click the Setting link to verify settings and trunk mappings for the AccessGate device. Click the Status link.
For more information about verifying AccessGate settings and status information with the AccessGate interface, refer to the AccessGate Configuration Manual.
46
NMS Communications
Connecting serial port, Ethernet, and alarm relay interfaces
Cable connection overview

This section provides the following information about connecting AccessGate 1000 cables: Cable requirements Connecting a serial port cable (for initial configuration) Connecting Ethernet cables Connecting trunk cables Connecting alarm dry relay contacts (optional) Providing a BITS clock connection (rear I/O only)
NMS Communications
47
Cable requirements
The following cable requirements apply to connections made to and from AccessGate 1000 equipment:
Interface T1 or E1 trunk Cable requirement Front I/O: Shielded Category 5. For information about trunk connector pin assignments, refer to Connecting trunk cables on page 55. Rear I/O: Shielded Category 5 25-pair straight cable with RJ48M male connector. Ethernet Serial port Alarm 10/100Base-T shielded Category 5 cable. For information about Ethernet connector pin assignments, refer to Connecting Ethernet cables on page 50. Straight-through serial cable with no null modem. For information about serial port connector pinouts, refer to Connecting a serial port cable on page 49. Shielded 9 conductor cable. Cables must be consistent with the following fire-spread characteristics for the deployment location:
Plenum ANSI/UL910 Riser - ANSI/UL 1666 (requirement found in ANSI T1.307)
For information about alarm connector pin assignments, refer to Connecting alarm dry relay contacts on page 52. BITS Shielded 9 conductor cable. Cables must be consistent with the following fire-spread characteristics for the deployment location:
Plenum ANSI/UL910 Riser - ANSI/UL 1666 (requirement found in ANSI T1.307)
For information about BITS connector pin assignments, refer to Connecting a BITS clock source on page 63.
AccessGate redundant configurations have additional cable requirements. For more information, refer to Redundant configuration cabling requirements on page 74.
48
NMS Communications
Connecting a serial port cable

Connect a straight-through null modem serial cable to the RS-232 serial port connector to run the AccessGate command line interface. For more information about the AccessGate command line interface, refer to Configuring and verifying with the AccessGate CLI on page 45. Serial port connector AccessGate DCE RS-232 interface female connector slots are numbered as follows:
5 4 3 2 1
9 8 7 6
Pin assignments The following table lists pin assignments for the serial port connector:
Pin 1 2 3 4 5 6 7 8 9 Signal Not used RXD: Receive TXD: Transmit Not used GND: Signal ground Not used RTS: Request to send CTS: Clear to send Not used
Default settings The following table lists default settings for the serial port connector:
Category Baud Data bits Parity Stop bits Setting 115200 8 None 1
NMS Communications
49
Connecting Ethernet cables

To verify connectivity with a web browser or with AccessView, connect a shielded Category 5 10/100Base-T Ethernet cable from a local area network (LAN) or wide area network (WAN) to the RJ-45 Ethernet connector 1 on the AccessGate 1000 BSC device. If the device uses DHCP to acquire IP addresses, only Ethernet 1 is active. If you configure static IP addresses for the AccessGate device, you can configure both Ethernet ports for the device. However, Ethernet 2 can only transfer traffic if it is configured for a separate subnet. Therefore, when you configure static IP addresses, assign a separate subnet mask for each Ethernet interface. This topic includes the following information: Ethernet_connector IP connection restrictions
Note: You can use a straight Ethernet cable or a crossover Ethernet cable to connect the AccessGate to the local LAN. The Ethernet physical structure automatically swaps the transmit and receive signal pairs at the Ethernet physical interface, in accordance with the cable type.
50
NMS Communications
Ethernet connector RJ-45 Ethernet connectors use the following pin assignments:
Pin 8 Pin Pin Pin Pin Pin Pin Pin Pin 8: 7: 6: 5: 4: 3: 2: 1: Ground Ground Rx-: Receive from network Ground Ground Rx+: Receive from network Tx-: Transmit to network Tx+: Transmit to network
Pin 1
Pins 4, 5, 7 and 8 are grounded through a 2KV capacitor for the Ethernet connections.
IP connection restrictions The following restrictions apply to connecting Ethernet cables for AccessGate configurations:
AccessGate 1000 device IP backhaul Restriction
The following restructions apply: Device location BSC Restriction
Ethernet 1 connection is used for carrying media over the IP backhaul link and can optionally be used for simultaneously transferring AccessGate control information. Ethernet 2 connection can be used for transferring AccessGate control information over an IP connection (for example, using the AccessGate web interface or AccessView). When you use Ethernet 2 to carry AccessGate control information the connection must be associated with a different subnet than Ethernet connection 1.
BTS
Ethernet 1 connection is used for carrying data over the IP backhaul link.
Routed BTS subnet
When the AccessGate 1000 BTS device is configured to support a private IP subnet (typically, in a TDM backhaul configuration), the Ethernet 2 connection on the equipment is reserved for providing the IP connection to the private subnet.
NMS Communications
51
Connecting alarm dry relay contacts

Connect shielded 9 conductor cables, as needed, to one or both of the DB-9 connectors labeled AUDIBLE and VISUAL. Cables must comply with the fire-spread restrictions applicable to the deployment location: Plenum ANSI/UL 910 Riser - ANSI/UL 1666 (ANSI T1.307 requirement)
Alarm dry relay contacts The alarm dry relay contact connectors are located near the AccessGate 1000 power supply connector. The connectors provide an interface to a central office building alarm system. One connector is for visual alarms and the other is for audible alarms. The DB-9 male alarm dry relay contact connectors use the following pin assignments:
1 2 3 4 5
6 7 8 9
The alarm state or condition of each dry relay contact is with no power applied. The following pin assignments apply to conditions when no power is applied. Pin assignments The following table lists visual alarm DB-9 dry relay contact connector pins:
Pin 1 2 3 4 5 6 7 8 9 Signal COM4 NO4 NC5 COM6 NO6 NC4 COM5 NO5 NC6 Description Critical visual common lead Critical visual normally open lead Major visual normally closed lead Minor visual common lead Minor visual normally open lead Critical visual normally closed lead Major visual common lead Major visual normally open lead Minor visual normally closed lead
52
NMS Communications
The following table lists audible alarm DB-9 dry relay contact connector pins:
Pin 1 2 3 4 5 6 7 8 9 Signal COM1 NO1 Reserved Reserved Reserved NC1 Reserved Reserved Reserved Description Critical audible common lead Critical audible normally open lead NA NA NA Critical audible normally closed lead NA NA NA
NMS Communications
53
Connecting T1/E1 interfaces
Connecting trunk cables

During the initial configuration process, the number of Abis and backhaul trunks you specify for the AccessGate device determines the trunk connectors allotted for each type of trunk, and which connectors (if any) remain disabled. For more information, refer to the AccessGate Configuration Manual. This topic contains the following information: Device-to-device trunk connections Sixteen-trunk front I/O variant trunk connectors Sixteen-trunk rear I/O variant trunk connectors Eight-trunk front and rear I/O variant trunk connectors
Device-to-device trunk connections Backhaul trunks on the AccessGate BTS device must be connected in the same incremental order as the backhaul trunks on the associated AccessGate BSC device. That is, the lowest numbered backhaul trunk on the AccessGate BTS device must be connected to the lowest numbered backhaul trunk on the AccessGate BSC device, the next highest backhaul trunk on the AccessGate BTS device must be connected to the next highest numbered backhaul trunk on the AccessGate BSC device, and so on to the highest numbered backhaul trunks on both devices.
Caution: Connecting backhaul trunks in the wrong order causes the connected AccessGate devices to generate alarms and can result in loss of backhaul connectivity or loss of traffic. For more information about the trunk mappings established for particular AccessGate configurations, refer to Trunk mapping for eight-trunk variants on page 66, Trunk mapping for sixteen-trunk variants on page 65, and Trunk mappings in redundant configurations on page 77.
Sixteen-trunk front I/O variant trunk connectors Using shielded T1 or E1 RJ-48 cables, connect T1 or E1 trunks to the AccessGate 1000 BTS device according to the trunk assignments established during initial configuration. Trunk connectors 9-16 use standard RJ-48 T1/E1 pin assignments. Trunk connectors 1 and 2, 3 and 4, 5 and 6, and 7 and 8 are combined in dual-trunk jacks. When using these trunks, you must use trunk adapter cables (such as NMS P/N 32851) to divide each 8-pin modular jack into two RJ-48C connectors or build custom cables appropriately.
For information about the E1 and T1 service and backhaul trunk assignments, refer to Trunk routing in bypass mode on page 67 and the AccessGate Configuration Manual. Note: NMS recommends shielded Category 5e cables for DS-1 connections.
NMS Communications
55
Pin assignments AccessGate RJ-48C single trunk E1/T1 interfaces use the following pin assignments:
Pin 8 Pin Pin Pin Pin Pin Pin Pin Pin 8: 7: 6: 5: 4: 3: 2: 1: Optional shield, not used Optional shield, not used No connection T1 - Transmit to network R1 - Transmit to network No connection T - Receive from network R - Receive from network
Pin 1
AccessGate NMS RJ-45 dual trunk E1/T1 connectors use the following pin assignments:
Pin 8 Pin Pin Pin Pin Pin Pin Pin Pin 8: 7: 6: 5: 4: 3: 2: 1: R - Receive from T - Receive from R1 - Transmit to T1 - Transmit to R1 - Transmit to T1 Transmit to T - Receive from R - Receive from network network network network network network network network (2) (2) (2) (1) (1) (2) (1) (1)
Pin 1
The following illustration shows a trunk adapter cable used to split a dual T1/E1 interfaces into pairs of RJ-48C connectors:
RJ-48C interfaces
NMS RJ-45 interface
Sixteen-trunk rear I/O variant trunk connectors The AccessGate 1000 sixteen-trunk rear I/O variant provides two eight-trunk RJ-48M interfaces for connecting T1 or E1 trunks. Use two 25-pair Category 5 shielded cables with straight 50-pin RJ-48M male connectors to connect T1 or E1 trunks to the AccessGate 1000 BTS device according to the trunk assignments established during initial configuration. Custom built cables are required if you connect the cables to a patch panel with pin assignments that vary from the RJ-48M standard.
50 26
25 RJ-48M
56
NMS Communications
Pin assignments The AccessGate RJ-48M E1/T1 interfaces use the following pin assignments:
Ring 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Tip 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 Connection Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Not used Trunks 1 and 9 1 and 9 NA 2 and 10 2 and 10 NA 3 and 11 3 and 11 NA 4 and 12 4 and 12 NA 5 and 13 5 and 13 NA 6 and 14 6 and 14 NA 7 and 15 7 and 15 NA 8 and 16 8 and 16 NA NA
NMS Communications
57
Eight-trunk front and rear I/O variant trunk connectors Connect shielded Category 5 E1 or T1 trunk cables for service and backhaul trunks to AccessGate device trunk connectors as appropriate for your configuration. To access trunks 1 through 8, connect shielded T1 or E1 RJ-48 cables to the appropriately numbered 8-pin modular jacks. Pin assignments The RJ-48C single trunk E1/T1 interfaces use the following pin assignments:
Pin 1
58
NMS Communications
Connecting trunk cables

During the initial configuration process, the number of Abis and backhaul trunks you specify for the AccessGate device determines the trunk connectors allotted for each type of trunk, and which connectors (if any) remain disabled. For more information, refer to the AccessGate Configuration Manual. This topic contains the following information: Device-to-device trunk connections Sixteen-trunk front I/O variant trunk connectors Sixteen-trunk rear I/O variant trunk connectors Eight-trunk front and rear I/O variant trunk connectors
Device-to-device trunk connections Backhaul trunks on the AccessGate BTS device must be connected in the same incremental order as the backhaul trunks on the associated AccessGate BSC device. That is, the lowest numbered backhaul trunk on the AccessGate BTS device must be connected to the lowest numbered backhaul trunk on the AccessGate BSC device, the next highest backhaul trunk on the AccessGate BTS device must be connected to the next highest numbered backhaul trunk on the AccessGate BSC device, and so on to the highest numbered backhaul trunks on both devices.
Caution: Connecting backhaul trunks in the wrong order causes the connected AccessGate devices to generate alarms and can result in loss of backhaul connectivity or loss of traffic. For more information about the trunk mappings established for particular AccessGate configurations, refer to Trunk mapping for eight-trunk variants on page 66, Trunk mapping for sixteen-trunk variants on page 65, and Trunk mappings in redundant configurations on page 77.
Sixteen-trunk front I/O variant trunk connectors Using shielded T1 or E1 RJ-48 cables, connect T1 or E1 trunks to the AccessGate 1000 BTS device according to the trunk assignments established during initial configuration. Trunk connectors 9-16 use standard RJ-48 T1/E1 pin assignments. Trunk connectors 1 and 2, 3 and 4, 5 and 6, and 7 and 8 are combined in dual-trunk jacks. When using these trunks, you must use trunk adapter cables (such as NMS P/N 32851) to divide each 8-pin modular jack into two RJ-48C connectors or build custom cables appropriately.
For information about the E1 and T1 service and backhaul trunk assignments, refer to Trunk routing in bypass mode on page 67 and the AccessGate Configuration Manual. Note: NMS recommends shielded Category 5e cables for DS-1 connections.
NMS Communications
59
Pin assignments AccessGate RJ-48C single trunk E1/T1 interfaces use the following pin assignments:
Pin 1
AccessGate NMS RJ-45 dual trunk E1/T1 connectors use the following pin assignments:
Pin 8 Pin Pin Pin Pin Pin Pin Pin Pin 8: 7: 6: 5: 4: 3: 2: 1: R - Receive from T - Receive from R1 - Transmit to T1 - Transmit to R1 - Transmit to T1 Transmit to T - Receive from R - Receive from network network network network network network network network (2) (2) (2) (1) (1) (2) (1) (1)
Pin 1
The following illustration shows a trunk adapter cable used to split a dual T1/E1 interfaces into pairs of RJ-48C connectors:
RJ-48C interfaces
NMS RJ-45 interface
Sixteen-trunk rear I/O variant trunk connectors The AccessGate 1000 sixteen-trunk rear I/O variant provides two eight-trunk RJ-48M interfaces for connecting T1 or E1 trunks. Use two 25-pair Category 5 shielded cables with straight 50-pin RJ-48M male connectors to connect T1 or E1 trunks to the AccessGate 1000 BTS device according to the trunk assignments established during initial configuration. Custom built cables are required if you connect the cables to a patch panel with pin assignments that vary from the RJ-48M standard.
60
NMS Communications
50
26
25 RJ-48M
Pin assignments The AccessGate RJ-48M E1/T1 interfaces use the following pin assignments:
Ring 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 Tip 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 Connection Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Receive from network Transmit to network Not used Not used Trunks 1 and 9 1 and 9 NA 2 and 10 2 and 10 NA 3 and 11 3 and 11 NA 4 and 12 4 and 12 NA 5 and 13 5 and 13 NA 6 and 14 6 and 14 NA 7 and 15 7 and 15 NA 8 and 16 8 and 16 NA NA
NMS Communications
61
Eight-trunk front and rear I/O variant trunk connectors Connect shielded Category 5 E1 or T1 trunk cables for service and backhaul trunks to AccessGate device trunk connectors as appropriate for your configuration. To access trunks 1 through 8, connect shielded T1 or E1 RJ-48 cables to the appropriately numbered 8-pin modular jacks. Pin assignments The RJ-48C single trunk E1/T1 interfaces use the following pin assignments:
Pin 1
62
NMS Communications
Connecting a BITS clock source

AccessGate 1000 rear I/O sixteen-trunk devices provide a BITS DB-9F connector for providing a master timing reference to the AccessGate device. Two timing references can be connected to this BITS input connector. Connect a shielded 9 conductor cable to the DB-9 connector labeled BITS. Note: In order to support GR-1244 compliance, NMS can provide a BITS-to-wirewrap adaptor (P/N 408698819). A single adapter provides a wire-wrap interface for both BITS inputs. AccessGate BITS clock connector slots are numbered as follows:
5 4 3 2 1
9 8 7 6
Pin assignments The following table lists BITS connector pins:

Pin 1 2 3 4 5 6 7 8 9 Signal BITS in A ring BITS in B ring Reserved Reserved (No connect) BITS in A tip BITS in B tip Reserved Reserved
BITS cable adapter cable pin assignments The following table lists BITS adapter pins:
Pin R1 T1 R2 T2 GND Signal BITS in A ring BITS in A tip BITS in B ring BITS in B tip Shield DB9M 1 6 2 7 Connector shield
NMS Communications
63
BITS framing The BITS source can be in any of the following formats for AccessGate 1000 devices:
Line type T1 T1 E1 E1 Framing Unframed, all-ones AIS ESF B8ZS (optional) Unframed, all-ones AIS CEPT HDB3
64
NMS Communications
Trunk mapping for sixteen-trunk variants

For sixteen-trunk variants, protected service trunks automatically fail over to the corresponding backhaul trunk if the AccessGate device goes into bypass mode. For example, if the device goes into bypass mode, data received on service trunk 1 continues to move to backhaul trunk 9. However, if the device goes into bypass mode, data received on service trunk 7 (an unprotected trunk) is interrupted before it reaches the backhaul. The following table shows the trunk mappings for AccessGate 1000 sixteen-trunk variants in TDM backhaul configurations (in IP backhaul configurations, the service trunk recommendations are the same, but the backhaul trunks are omitted).
Service trunk 1 2 3 4 5 6 7 8 15 16 Failover backhaul trunk 9 10 11 12 13 14 NA NA NA NA Protection Protected Protected Protected Protected Protected Protected Unprotected Unprotected Unprotected Unprotected
As the table shows, trunks 1 - 6 are protected because any data transferred to these trunks continues to travel through the AccessGate device even if the device goes into bypass mode. Service trunks 7, 8, 15, and 16 are unprotected. Data transferred to these trunks is dropped if the AccessGate 1000 device goes into bypass mode. If the configuration requires additional backhaul trunks, use trunks 15 and 16 for backhaul traffic (for example, to support eight 1:1 virtual gateways for satellite applications). The following table shows the alternate trunk mappings that apply to this configuration:
Service trunk 1 2 3 4 5 6 7 8 Failover backhaul trunk 9 10 11 12 13 14 15 16 Protection Protected Protected Protected Protected Protected Protected Protected Protected
NMS Communications
65
By subtracting two available service trunks, this mapping offers two additional backhaul trunks that are both protected. This trunk mapping applies to AccessGate devices contained within redundant configurations. For more information, refer to Trunk mappings in redundant configurations on page 77.
Trunk mapping for eight-trunk variants

The following table shows the trunk relay mappings for AccessGate 1000 eight-trunk variants in TDM backhaul configurations (in IP backhaul configurations, the service trunk recommendations are the same, but the backhaul trunks are omitted):
Service trunk 1 2 3 4 8 Failover backhaul trunk 5 6 7 NA NA Protection Protected Protected Protected Unprotected Unprotected
As shown in the previous table, trunks 1 - 3 are protected because any data transferred to these trunks continues to travel through the AccessGate device even if the device goes into bypass mode. Service trunks 4 and 8 are unprotected. Data transferred to these trunks is dropped if the AccessGate 1000 device goes into bypass mode. If the configuration requires an additional backhaul trunk, use trunk 8 for backhaul traffic (for example, to support four 1:1 virtual gateways for satellite applications). For eight-trunk variants, protected service trunks automatically fail over to the corresponding backhaul trunk if the AccessGate device goes into bypass mode. For example, if the device goes into bypass mode, data received on service trunk 1 continues to move to backhaul trunk 5. However, if the device goes into bypass mode, data received on service trunk 4 (an unprotected trunk) is interrupted before it reaches the backhaul. The following table shows the alternate trunk mappings that apply to this configuration:
Service trunk 1 2 3 4 Failover backhaul trunk 5 6 7 8 Protection Protected Protected Protected Protected
This mapping offers an additional backhaul trunk (which is protected) by subtracting an available service trunk. This trunk mapping applies to AccessGate devices contained within redundant configurations. For more information, refer to Trunk mappings in redundant configurations on page 77.
66
NMS Communications
Trunk routing in bypass mode

In TDM backhaul configurations, when an AccessGate device goes into bypass, the AccessGate devices in the network element direct data from particular service trunks to specific backhaul trunks. As a result, the devices continue to transfer data at a reduced capacity even when they are in bypass. For information about configuring AccessGate 1000 for E1 or T1 operation, refer to the AccessGate Configuration Manual. Trunk allocation in a bypass state When an AccessGate 1000 device goes into a bypass state, it transfers data at reduced capacity. The reduction occurs because the device is typically connected to more service trunks than backhaul trunks. The traffic from at least one service trunk must be dropped to match the number of backhaul trunks available to transfer the data. The following illustration shows trunk activity when an AccessGate 1000 sixteen-trunk device with two service trunks and one backhaul trunk is in-path:
Service trunk 1 (protected)
AccessGate 1000 BTS device
AccessGate 1000 BSC device
BTS
Service trunk 7 (unprotected) AccessGate processing
Backhaul trunk 9
Circuit switched network
BSC
AccessGate 2:1 BTS virtual gateway in-path
AccessGate 2:1 BSC virtual gateway in-path
The following illustration shows trunk activity on the same AccessGate 1000 devices when it transitions to a bypass state:
Service trunk 1 (protected) AccessGate 1000 BTS device Backhaul trunk 9 AccessGate 1000 BSC device
BTS
Service trunk 7 (unprotected) AIS AccessGate bypass

AIS
BSC
AccessGate 2:1 BTS virtual gateway in bypass
AccessGate 2:1 BSC virtual gateway in bypass
NMS Communications
67
Manually assigning virtual gateway trunk connections

The AccessGate command line interface enables you to assign specific trunk connections to backhaul and service trunks when creating virtual gateways. In order to use AccessGate trunk resources in the most efficient way, consider the following information when manually configuring the AccessGate virtual gateways: Trunk allocation rules and recommendations Planning trunk assignments Typical trunk configurations
Note: This information is only important if you configure the virtual gateway manually using the AccessGate command line interface or through AccessView. If you choose the standard method for creating virtual gateways with the AccessGate command line interface, trunk assignments are automatically allocated. For more information, refer to the AccessGate Configuration Manual. Trunk allocation rules and recommendations The following rules apply when allocating trunks for AccessGate 1000 virtual gateways: Service trunks connected to AccessGate devices are either protected or unprotected. If an AccessGate device goes into bypass, data continues to flow through protected trunks. Data traveling through unprotected trunks is interrupted when the device goes into bypass. For more information about protected and unprotected trunks, refer to Terminology on page 12. For each virtual gateway, you can arrange to protect a number of service trunks equal to the number of backhaul trunks for that virtual gateway (for more information refer to Trunk routing in bypass mode on page 67). For example, in a virtual gateway with five service trunks and three backhaul trunks, you can protect three of the five service trunks. The two highest numbered service trunks are therefore unprotected, and data traveling through these trunks is interrupted if the device goes into bypass. In a sixteen-trunk AccessGate 1000 device, trunks connected to interfaces 7, 8, 15 and 16 are unprotected. On eight-trunk variants, trunks connected to interfaces 4 and 8 are unprotected. Therefore, when configuring multiple virtual gateways, the most effective way to allocate service trunks is to decide in advance which service trunks to leave unprotected, and to connect these trunks to unprotected interfaces first. The backhaul trunks on the AccessGate BTS must be mapped in the same incremental order as backhaul trunks on the associated AccessGate BSC device to which they are connected.
68
NMS Communications
Recommended practice In addition to the previous rules, NMS highly recommends that you follow the following guidelines when allocating trunks for AccessGate devices: On sixteen-trunk variants use trunk connectors 9 through 14 for backhaul trunks. On eight-trunk variants use trunk connectors 5 through 7 for backhaul trunks. This allows for a more predictable service-to-backhaul trunk bypass behavior when the AccessGate device goes into bypass. Use the same virtual gateway name on both the AccessGate BSC and BTS device to which it is mapped. Although it is not mandatory to assign the same name to a virtual gateway on both the AccessGate BTS and BSC device, using a common virtual gateway name simplifies the process of maintaining and monitoring the virtual gateway.
Planning trunk assignments A virtual gateway is an association of service trunks with backhaul trunks. To allocate and create gateways, complete the following steps: 1. Determine the number and configuration of virtual gateways that are required to run on the AccessGate BSC device. Assign an index to each virtual gateway starting from 0, and create a chart of the trunks required to support the two virtual gateways. 2. Assign trunk numbers incrementally to service trunks starting at interface 1, and assign unprotected trunks incrementally to trunk interfaces 7, 8, 15, and 16. 3. Assign backhaul trunk interfaces incrementally, starting at interface 9. The following example shows service trunk mappings for an AccessGate BSC sixteen-trunk device with a 5:3 virtual gateway:
Virtual gateway 0 Service trunks 1 2 3 7* 8* Backhaul trunks 9 10 11
* Unprotected trunk 4. Repeat Steps 2 and 3 for each required virtual gateway with the following modifications: Start service trunk numbering upwards from the lowest unused service trunk interface (in the example, 4). Assign unprotected trunk numbering starting at the lowest unused unprotected trunk interface in the 7, 8, 15, 16 group (in the example, this is 15 because trunks 7 and 8 are used). Continue backhaul trunk numbering upwards from the lowest unused trunk (in the example, 12).
NMS Communications
69
For example, the following configuration shows trunk mappings for an AccessGate sixteen-trunk device with one 5:3 virtual gateway, one 3:2 virtual gateway, and one 2:1 virtual gateway:
Virtual gateway 0 (5:3) Service trunks 1 2 3 7* 8* Backhaul trunks 9 10 11 Virtual gateway 1 (3:2) Service trunks 4 5 15* Backhaul trunks 12 13 Virtual gateway 2 (2:1) Service trunks 6 16* Backhaul trunks 14
* Unprotected trunk 5. Using the AccessGate command line interface, select the Configure gateway option from the main window to create the virtual gateways and to map trunk assignments according to the trunk mapping chart completed in Step 4. For more information, refer to the AccessGate Configuration Manual. 6. Connect trunk cables according to the trunk mapping chart of service trunks and backhaul trunks completed in Step 4, and consistent with the configuration set with the command line interface in Step 5. 7. Configure device settings at the corresponding AccessGate 1000 BTS devices so that the number and ratio of service and backhaul trunks is consistent with the virtual gateways configured on the BTS device.
70
NMS Communications
Typical trunk configurations The following tables show sample trunk configurations for AccessGate 1000 where all virtual gateways use the same ratio of service trunks to backhaul trunks: AccessGate 1000 sixteen-trunk with two 5:3 virtual gateways:
Virtual gateway 0 Service trunks 1 2 3 7* 8* Backhaul trunks 9 10 11 Virtual gateway 1 Service trunks 4 5 6 15* 16* Backhaul trunks 12 13 14
AccessGate 1000 sixteen-trunk with three 3:2 virtual gateways:

Virtual gateway 0 Service trunks 1 2 7* Backhaul trunks 9 10 Virtual gateway 1 Service trunks 3 4 8* Backhaul trunks 11 12 Virtual gateway 2 Service trunks 5 6 15* Backhaul trunks 13 14
* Unprotected trunk AccessGate 1000 sixteen-trunk with five 2:1 virtual gateways:
Virtual Gateway 0 Service trunks 1 7* Backhaul trunks 9 Virtual Gateway 1 Service trunks 2 8* Backhaul trunks 10 Virtual Gateway 2 Service trunks 3 15* Backhaul trunks 11 Virtual Gateway 4 Service trunks 4 16* Backhaul trunks 12 Virtual Gateway 4 Service trunks 5 6* Backhaul trunks 13
* Unprotected trunk AccessGate 1000 eight-trunk device with two 2:1 virtual gateways:
Virtual gateway 0 Service trunks 1 2* Backhaul trunks 5 Virtual gateway 1 Service trunks 3 4* Backhaul trunks 6
* Unprotected trunk
NMS Communications
71
Configuring 1+1 redundant devices
Overview of 1+1 redundancy

Redundant configurations are sets of network components organized so that if one component ceases to operate, another component performs the functions of the failed one. The term 1+1 redundancy describes configurations in which two devices are configured so that if the first (protected) device fails, the other device acts as its backup and resumes processing. Note: 1+1 redundancy is not supported in AccessGate IP backhaul configurations. You can connect and configure pairs of AccessGate 1000 devices at BSC and BTS locations to provide 1+1 redundancy for the devices. The configuration process requires special configuration and cabling. You can set up AccessGate redundant configurations at the BSC, at the BTS, or both. Frequently used terminology The following table describes the terminology used to describe AccessGate 1+1 redundant configurations:
Term Protected Description The role assigned to the AccessGate device that performs the primary backhaul optimization tasks in a 1+1 redundant system. If the protected device fails, the spare device takes over these tasks. The role assigned to the AccessGate device in a 1+1 redundant system that remains inactive until the protected device goes out of service. When the protected device goes out of service, the spare device performs backhaul optimization tasks. The mode in which a protected or spare AccessGate device actively processes trunk traffic. The mode in which an AccessGate protected or spare device does not actively process trunk data. A process by which the AccessGate spare device assumes the responsibilities of a protected device when the protected device fails. A protected device fails over to a spare device when it relinquishes the backhaul optimization tasks to the spare device. Recovery Field replaceable unit (FRU) A process by which an AccessGate protected device resumes performing its processing tasks after it has been replaced or repaired. An AccessGate physical device used to replace another AccessGate at a BTS or BSC.
Spare
Active Standby Failover
NMS Communications
73
Redundant configuration cabling requirements

The requirements of AccessGate devices in a redundant configuration vary according to the device variant (8 or 16 trunks) and the location of the devices. The following ill1`ustration shows the cable requirements for AccessGate 8 trunk variants in redundant configurations at BSC locations:
a T1/E1 crossover cables To BTS Circuit switched network
Backhaul trunks
Redundant pair a Protected device T1/E1 crossover cables Spare device
a T1/E1 crossover cables BSC
5 6 7 8
EN1 EN2
1 2 3 4
5 6 7 8
EN2 EN1
1 2 3 4
Service trunks
Ethernet crossover cable c Ethernet cable
c Ethernet cable Ethernet switch
AccessGate redundant configuration cable requirements: BSC
The following cable requirements apply to connections made to and from AccessGate devices in a redundant configuration:
Letter in illustration a Description Shielded Category 5 T1/E1 crossover cable Functions
Connects T1/E1 interfaces on the protected AccessGate device to T1/E1 interfaces on AccessGate spare device. Connects protected AccessGate device to the backhaul. Connects spare AccessGate device to service interface. Connects the EN2 Ethernet interface on the protected AccessGate device to the EN2 interface on the spare AccessGate device. (BSC only) Connects protected and spare AccessGate device EN1 interface to a LAN.
Ethernet crossover cable
Category 5 10/100Base-T Ethernet cable
For a list of standard AccessGate cable requirements, refer to Cable requirements on page 48.
74
NMS Communications
The following illustration shows the cable requirements for AccessGate eight-trunk variants in redundant configurations at BTS locations:
Redundant pair a T1/E1 crossover cables a Spare device T1/E1 crossover cables Protected device a T1/E1 crossover cables
BTS
1 2 3
Service trunks
5 6 7 8
EN2
1 2 3 4
b
EN2
5 6 7 8
Backhaul trunks
To BSC
Ethernet crossover cable
AccessGate redundant configuration cable requirements: BTS
NMS Communications
75
AccessGate redundant failover

In AccessGate redundant configurations, two AccessGate devices reside in specific locations with regard to each other. Each device is configured to operate in a specific role within the configuration: protected or spare. AccessGate redundancy roles are not interchangeable. A spare device cannot assume the role of a protected device with its own backup device, and a protected device cannot assume the role of a spare and act as a backup for another device. AccessGate 1+1 redundancy is implemented by configuring trunk traffic through a pair of AccessGate devices in a serial manner. Redundant 1+1 configurations use the AccessGate relay bypass feature to switch individual devices in and out of path. Only one device is in-path at any one time. For information about the trunk mapping schema used to direct trunk traffic through the redundant configuration, refer to Trunk mappings in redundant configurations on page 77. AccessGate devices in redundant configurations can operate in either of two modes: Active mode: The device performs backhaul optimization tasks. Standby mode: The device transfers data without performing backhaul optimization processing.
Initially, the protected device is active and the spare device is in standby. During the failover process, the spare device goes into active mode and the protected device goes into standby mode until recovery occurs. The following illustration shows an AccessGate 1+1 redundant configuration at a BTS location that includes two eight-trunk devices performing 3:2 backhaul optimization:
Redundant pair AccessGate spare device
Interconnect cables
BTS
Service trunks
AccessGate protected device 1 2 3 4

Backhaul trunks
1 2 3 4
5 6 7 8
5 6 7 8
To BSC
Normal operation
Redundant pair AccessGate spare device 1 2 3 4 5 6 7 8

Interconnect cables
BTS
Service trunks
AccessGate protected device 1 2 3 4 5 6 7 8
Backhaul trunks
To BSC
Failover
76
NMS Communications
Trunk mappings in redundant configurations

This topic provides information about AccessGate 1+1 redundancy relay bypass trunk mappings used for cabling trunks on the following AccessGate variants: AccessGate sixteen-trunk variants AccessGate eight-trunk variants
AccessGate sixteen-trunk variants The following illustration shows trunk mappings for AccessGate sixteen-trunk variants in redundant configurations:
[1] [2] [3] [4] [9] [10] [11] [12] AccessGate 1000 16 trunks [Spare] [13] [14] [15] [16] [1] [2] [3] [4] [5] [6] [7] [8] AccessGate 1000 16 trunks [Protected] [9] [10] [11] [12] [13] [14] [15] [16]
Service
[5] [6] [7] [8]
Backhaul
AccessGate eight-trunk variants The following illustration shows trunk mappings for AccessGate eight-trunk variants in redundant configurations:
[1] [5] [1] [5]
[2]
[6] AccessGate 1000 8 trunks [Spare]
[2] AccessGate 1000 8 trunks [Protected]
[6]
Service
[3]
[7]
[3]
[7]
Backhaul
[4]
[8]
[4]
[8]
NMS Communications
77
Setting up an AccessGate redundant configuration

This topic describes the procedure for installing, configuring, and cabling AccessGate devices in redundant configurations.
Caution: AccessGate devices that you set up in redundant configurations must be running the same version of the AccessGate firmware. If the protected and spare devices are not running the same firmware version, the redundant failover process will not take place appropriately.
To install and configure pairs of AccessGate devices in a 1+1 redundant configuration, perform the following steps:
Step 1 Protected device Install the protected device according to the following instructions: Spare device Troubleshooting Perform hardware diagnostics as described in Configuring and verifying with the AccessGate CLI on page 45.
Installing AccessGate on page 34 Grounding AccessGate on page 37 Installing the power connector on page 43 Install the spare device according to the following instructions:
Installing AccessGate on page 34 Grounding AccessGate on page 37 Installing the power connector on page 43
Perform hardware diagnostics as described in Configuring and verifying with the AccessGate CLI on page 45.
Connect an Ethernet crossover cable from the Ethernet 2 connector on the AccessGate protected device to the Ethernet 2 connector on the AccessGate spare device. Configure the protected device and set the AccessGate redundancy role to PPROTECTED, as described in the AccessGate Configuration Manual. Configure the spare device, making sure to set the AccessGate redundancy role to SPARE and to set the device type (BSC or BTS) to the same setting as the protected device. For more information, refer to the AccessGate Configuration Manual.
78
NMS Communications
Step 6
Protected device (BSC only) Connect an Ethernet straight cable from the Ethernet 1 connector on the AccessGate protected device to the LAN as described in Connecting Ethernet cables on page 50.
Spare device
Troubleshooting Use AccessView to observe the AccessGate devices in the configuration to see if the configuration is in redundant mode.
(BSC only) Connect an Ethernet straight cable from the Ethernet 1 connector on the AccessGate spare device to the LAN as described in Connecting Ethernet cables on page 50. Connect T1/E1 crossover cables between the appropriate trunk connectors on the AccessGate protected device and the AccessGate spare device. For more information, refer to Trunk mappings in redundant configurations on page 77. Use AccessView to observe whether trunk alarms are resolved for links used to interconnect the two AccessGate devices.
Connect straight T1/E1 trunk cables from the backhaul interface to the appropriate trunk connectors on the AccessGate protected device. For more information, refer to Trunk mappings in redundant configurations on page 77.
10
Connect straight T1/E1 trunk cables from the service interface to the trunk appropriate connectors on the AccessGate spare device. For more information, refer to Trunk mappings in redundant configurations on page 77.
Use AccessView to observe whether trunk alarms are resolved for links used to connect the AccessGate devices to the backhaul and service interfaces.
11
(Optional) Connect call generation tools to the backhaul and service trunks and test the redundant configuration by forcing a failover. For more information, refer to the AccessGate Configuration Manual. Enable the flow of data through the AccessGate redundant configuration. Use AccessView to observe whether any alarms occur.
12
For information about configuring AccessGate with the AccessGate command line interface, refer to the AccessGate Configuration Manual. For information about using AccessView, refer to the AccessView 3.0 User's Manual.
NMS Communications
79
Redundancy rules of operation

The following rules apply to AccessGate 1000 1+1 redundant configurations: AccessGate devices in redundant configurations must be connected by an Ethernet cable (that is, from Ethernet port 2 on spare to Ethernet port 2 on protected). The spare device monitors the health and configuration of the protected device through this cable. After a pair of AccessGate devices is configured, installed, and connected in 1+1 redundant configuration, their roles do not change. During failover and recovery they can switch between active and standby mode. However, even when the protected device or spare device is replaced, the replacement device assumes the role of the one before it. Redundancy master control resides on the spare device, which automatically triggers redundant failover if: o o The protected AccessGate device produces a critical alarm. The spare device loses contact with the protected device for more than 60 seconds.
While the spare device is in active mode, if it detects that the protected device returned to service, the spare device automatically updates the protected device with the last configuration retrieved from the protected device (before the failover). Both the AccessGate protected device and AccessGate spare device must be running the same version of the AccessGate firmware (version 2.1 or above) if they are not in failover. The firmware cannot be updated during the failover process. It can however be updated during the recovery process. During failover, any configuration changes to the spare device are carried over to the protected device when it returns to service. In addition, if the firmware is changed on the spare device while it is in active mode, the new firmware is cloned to the protected device when it returns to service. The two AccessGate devices installed in a redundant 1+1 configuration must contain the same number of T1/E1 trunks and DSPs. The number of service trunks in redundant configurations cannot exceed the number of trunks that can be relay bypassed on the active device. Therefore, in AccessGate eight-trunk variants, a maximum of four service trunks are available. In AccessGate sixteen-trunk variants, a maximum of eight service trunks are available. The protected device resides on the side of the configuration closest to the backhaul trunks. The spare device resides on the side of the configuration closest to the service trunks. During the AccessGate failover process, calls may be dropped.
80
NMS Communications
10
Step 1
Replacing equipment
Equipment replacement overview

An AccessGate 1000 device at a BSC location and an AccessGate 1000 device at a BTS location are physically identical. The only difference between the two is how the firmware is configured. When an AccessGate 1000 device is shipped from the factory, it is configured to function as a BSC device. To replace an AccessGate 1000 device at a BSC or at a BTS site, follow these steps:
Description Reroute any data traffic that will be lost during the replacement or schedule the replacement at a time in which no data traffic will be affected. Unpack and inspect the replacement AccessGate 1000 equipment and assemble the required tools. For more information, refer to... Network administrator at your site. Unpacking and inspecting the equipment on page 25 Required tools on page 23 3 At the fuse or circuit breaker panel, unplug the fuse or open the circuit breaker to turn off the power for the AccessGate 1000 device that you are replacing. Remove the AccessGate 1000 device that is installed in the frame and set it aside. If applicable, attach the side-mounting guides to the replacement device. If applicable, secure the panel extenders to the replacement device. Install the replacement AccessGate 1000 device into the frame. Connect the ground cable, alarm cables, and Ethernet cables. Insert the power input connector into the device power connector on the front or rear panel. Insert the appropriate fuse or close the circuit breaker to restore power. Connect the serial port cable from a PC or laptop computer and run hardware diagnostics with the AccessGate command line interface. Network administrator at your site. Removing an AccessGate 1000 device on page 83 Assembling the rear support kit on page 33 Assembling the panel extender mounting kit on page 32 Installing AccessGate on page 34 Cable connection overview on page 47 Installing the power connector on page 43 Installing the power connector on page 43 Connecting a serial port cable on page 49 Configuring and verifying with the AccessGate CLI on page 45 Configuring a replacement device on page 85
4 5 6
7 8 9 10 11
12
Configure the replacement device using the same parameters as those of the associated peer. Note: The replacement device arrives from the factory configured as a BSC device.
NMS Communications
81
Replacing equipment
Step 13
Description Connect T1 or E1 trunk cables to the AccessGate trunk connectors. These trunk connections (the trunks allocated for backhaul, service, and inactive trunks) must match those set up on the device you removed. Verify backhaul communications between the AccessGate BSC and BTS devices. Ensure that all alarms are cleared.
For more information, refer to... Connecting trunk cables on page 55
14
Configuring and verifying with the AccessGate CLI on page 45 AccessGate Configuration Manual and AccessGate SNMP Administration Manual
15
82
NMS Communications
Replacing equipment
Removing an AccessGate 1000 device

Complete the following steps to remove an AccessGate 1000 device from an existing installation:
Step 1 Action At the fuse or circuit breaker panel, unplug the fuse or open the circuit breaker to turn off the power for the AccessGate 1000 device that you are replacing. Warning: Unplug the fuse or open the circuit breaker before disconnecting the power cable. Once the power cable is reconnected to the device, you can enable the power source.
2 3
Using a metric slotted screwdriver, loosen the slotted head screws on both sides of the power input connector of the front or rear panel. Remove the power input connector from the AccessGate power connector.
- +- +
AccessGate power connector
Power input connector
Disconnect the following cables from the AccessGate 1000 front or rear panel. Record the location of the cables in relation to the device connectors.
Ground cable Ethernet cables Alarm cables Trunk cables
With a #1 Phillips screwdriver, loosen and remove the mount screws that secure the AccessGate device to the frame. If rear supports are not used, be sure to support the device when removing the screws.
NMS Communications
83
Replacing equipment
Step 6
Action Supporting the AccessGate device with both hands, slide the device from the frame and set aside.
#1 Phillips
Screws
84
NMS Communications
Replacing equipment
Configuring a replacement device

An AccessGate 1000 device at a BSC site that is linked to an AccessGate 1000 device at a BTS site must use compatible configuration schemes to exchange data successfully. When replacing an AccessGate device, you must change the configuration parameters of the replacement device to match the parameters of its peer. When an AccessGate device arrives from the factory, it is configured for use in a BSC site. If you are replacing an AccessGate BTS device, you can change the device type from BSC to BTS during the configuration process. Before configuring a replacement device, have the following information available: Most recent configuration settings for the pair of AccessGate devices with which you are working. Unique IP address(es) associated with the replacement device, when applicable. If the Ethernet IP address of the replacement device is a fixed IP address, you also need the network mask and default gateway route for the interface.
To change the AccessGate device configuration and establish communications between the replacement device and its associated peer, perform the following steps:
Step 1 Action Connect a serial port cable from a PC or laptop computer to the serial port connector on the replacement device. For more information about establishing a serial port connection, refer to Connecting a serial port cable on page 49. Start a terminal emulator application on the computer. Refer to Computer requirements on page 24 for information about appropriate terminal emulator settings. The terminal emulator program displays the AccessGate command line interface main menu. Select Configure gateway from the main menu. The command line interface displays options for setting configuration parameters. These options differ depending on whether you are configuring the device for E1 or T1 operation. 4 Using device configuration parameters recorded on a worksheet or from a configuration snapshot, and specifying the unique Ethernet IP address of the replacement device, respond to the command line interface prompts. Configure the replacement AccessGate device so its configuration matches that of its peer device. Approve the new settings. The command line interface resets and restarts the device with the new parameters. 6 Verify connectivity between the AccessGate BSC and BTS device. Refer to Configuring and verifying with the AccessGate CLI on page 45 and Global installation recommendations on page 29 for more information. If the firmware running on the AccessGate BSC and BTS devices does not match exactly, upgrade the firmware on both devices (as described in the AccessView 3.0 User's Manual) or if the devices are in-path, clone the firmware from one device to another (as described in the AccessGate Configuration Manual). Alternatively, reconfigure the BTS temporarily as a BSC and upgrade the firmware to match the true BSC AccessGate using the web interface. Once the firmware versions in both units match, reconfigure the temporary BSC device back to a BTS device.
NMS Communications
85
Replacing equipment
Replacing a protected device in a redundant configuration

If a protected device in an AccessGate redundant 1+1 configuration fails, the spare device assumes all processing tasks of the failed device. You can replace the protected device with only a momentary lapse of service.
Caution: Because devices that have been previously installed in redundant configurations can retain setting and state information that can interfere with the device's operation in a new configuration, NMS recommends that you restore factory default settings on any previously installed devices before configuring and installing them for redundant operation.
Replacing the protected device To replace the protected device in an AccessGate 1+1 redundant configuration, perform the following steps:
Step 1 2 3 4 Action Disconnect the Ethernet crossover cable from the Ethernet 2 connector on the AccessGate protected device to the Ethernet 2 connector on the AccessGate spare device. Power down and remove the protected AccessGate device as described in Removing an AccessGate 1000 device on page 83. Install a new AccessGate protected device as described in Installing AccessGate on page 34 and Installing the power connector on page 43. Configure the replacement device as described in the AccessGate Configuration Manual. The following configuration requirements apply to the replacement device: Configuration setting Firmware Gateway type Redundancy setting 5 6 Description No requirement. The replacement device firmware is automatically upgraded during the recovery process Is the same as the protected device. Set to PROTECTED.
Connect an Ethernet straight cable from the Ethernet 1 connector on the AccessGate protected device to a LAN as described in Connecting Ethernet cables on page 50. Connect T1/E1 crossover (interconnect) cables between the new protected device and the spare device as described in Setting up an AccessGate redundant configuration on page 78 and connect T1/E1 cables as necessary to the protected device. Connect an Ethernet crossover cable from the Ethernet 2 connector on the AccessGate protected device to the Ethernet 2 connector on the AccessGate spare device. The spare device automatically updates the active firmware running on the protected device and also updates any necessary configuration settings. During this process (which can take several minutes), service is not affected because the spare device continues to perform AccessGate backhaul optimization tasks. When the firmware update and configuration process is complete on the new protected device, the protected device goes into active mode and assumes all AccessGate backhaul optimization processing. The spare device reverts to standby mode.
For information about configuring AccessGate with the AccessGate command line interface, refer to Configuring and verifying with the AccessGate CLI on page 45.
86
NMS Communications
11
Specification Height Width Depth Weight
Compliance, regulatory, and reference information
Physical characteristics
AccessGate 1000 equipment has the following physical characteristics:
Value 1.74 in. (44.20 mm) 17.22 in. (437.00 mm) Front mounting bracket to rear ground studs: 11.33 in. (287.54 mm) Front ground studs to rear ground studs: 11.72 in. (297.38 mm) 16 trunk front I/O: 9.04 lbs (4.10 kg) 16 trunk rear I/O, 9.00 lbs (4.08 kg) 8 trunk front I/O: 9.04 lbs (4.10 kg) 8 trunk rear I/O: 9.00 lbs (4.08 kg) 19 in. (23 in. with panel extender kit) Front mounting brackets. Rear vertical support bracket available. 200 LFM total (metric 61 LMM) Airflow direction right to left Cooled by four internal fans
Enclosure rack size Mounting points System cooling
NMS Communications
87
Electrical requirements
This topic provides the following information: DC input requirements Overcurrent protection requirements Power requirements Ground requirements
DC input requirements The following tables provide DC input requirements for AccessGate 1000 devices:
Voltage 24 V -48 V Current 5A 3A Wattage 40 W 70 W
Configuration Typical Maximum
Overcurrent protection requirements Provide an overcurrent protection device as part of each AccessGate 1000 installation. Include a 3 A fuse (for a -48 V power source) or 5 A fuse (for a 24 V power supply) in the negative supply conductor between the DC power source and the AccessGate 1000 device. Power requirements AccessGate 1000 equipment has two redundant power feeds and requires a pair of cables to provide a 24 V or -48 V DC power source. Connect both power feeds, even if power originates at the same physical source; otherwise the equipment will remain in alarm. Design wiring from the power distribution point for an IR drop of less than 0.75 V. The following illustration shows the power feeds for an AccessGate 1000 device:
88
NMS Communications
Power source (single or separate feeds)
AccessGate
_ B (left) + _ A (right) +
The following requirements apply to AccessGate 1000 power cables: 12 AWG or heavier wire gauge. Cables must be consistent with fire-spread characteristics for the deployment location: Plenum ANSI/UL910 Riser - ANSI/UL 1666 (requirement found in ANSI T1.307)
Cable construction must meet appropriate IPC specifications.
Ground requirements AccessGate 1000 equipment must be connected to the earth-to-frame ground. The recommended safety grounding points are the two ground studs provided on the AccessGate 1000 device on the front and rear panel. Installing a ground lug with attached ground cable provides a ground connection for the device.
Ground lug
Cables used to provide a ground connection for AccessGate 1000 must meet the following requirements: Cable must be green or green with yellow tracer. Per NEC2002, no ground conductor for communications equipment shall be less than 14 AWG. Cables must be consistent with fire-spread characteristics for the deployment location: Plenum ANSI/UL910 Riser - ANSI/UL 1666 (requirement found in ANSI T1.307) Cable construction must meet IPC specifications.
NMS Communications
89
Environmental requirements
Install AccessGate 1000 equipment in an environment within the following conditions:
Specification Operating temperature range Operating humidity range Maximum operating altitude Flammability rating Value 14 to 149 F (-10 to 65 C) 10% to 90% relative humidity non-condensing 10,000 ft (3,410 m) UL94V-0
90
NMS Communications
Compliance and regulatory certification

NMS Communications obtains board-level approvals certificates for supported countries. In addition to the approval obtained by NMS for the equipment and its associated software, some countries require a system-level approval before connecting the system to the public network. To learn what approvals you require, contact the appropriate regulatory authority in the target country. EMC
Country US Canada EU Standard FCC Part 15 Class A with shielded Telecom cables and STP Ethernet cables IECS-003 with shielded Telecom cables and STP Ethernet cables EN55024:1998 A1:2001 with shielded Telecom cables and STP Ethernet cables
Safety
Country US Canada EU Standard FCC Part 68, T1A-968-A CSO3 EN 60950-1:2001
Telecom
Country US Canada EU Standard FCC Part 68 CS03 Issue 8 TBR 12/A1, TBR 13 G.703 (10/98) and G.704 (10/98) for both 75 ohms and 120 ohms
EU R&TTE statement This product is intended to be connected to the following public telecommunication networks: Euro-ISDN Primary Rate Access in all EU countries. 2048 kbit/s 75 ohm or 120 ohm digital structured or unstructured ONP leased line in all EU countries.
A copy of the R&TTE Declaration of Conformity is shipped with the product.
NMS Communications
91
Reference documents
Refer to the following documents for additional information about the standards associated with AccessGate 1000 equipment: GR-1089 Electromagnetic Compatibility and Electrical Safety GR-63 CORE Physical Protection GR-78-CORE Generic Requirements for the Physical Design and Manufacture of Telecommunications Products and Equipment ETS 300-019 Environmental conditions and environmental tests for telecommunications equipment ETS 300-386 Telecommunication network equipment; Electro Magnetic Compatibility (EMC) requirements UL60950 Underwriters Laboratories Safety of Information Technology Equipment IPC/WHMA-A-620 Class 2 National Electrical Code Handbook - NEC2002
92
NMS Communications
12
Glossary
A
Abis: The communication interface between a base transceiver station (BTS) and a base station controller (BSC) in a mobile communications network. aggregation size: A measure of the minimum or maximum interval of data (in ms.) obtained from each channel to fill each IP packet. AIS: Alarm indication signal. A signal that replaces a normal traffic signal when a maintenance alarm indication is activated. Ater: The communication interface between a remote BSC and a TRAU in a mobile communications network. Auto: A mode of operation in which the AccessGate device remains in bypass mode until it detects its AccessGate device peer. When it detects its peer, the AccessGate device transitions to in-path mode.
B
backhaul trunk: E1 or T1 trunks connected to an AccessGate 1000 device that transfer compressed, aggregated cell traffic between a BTS (or node B) and a BSC (or RNC). bandwidth: A measure of capacity of communications media. Greater bandwidth enables communication of more information in a given period of time. Bandwidth is generally described either in terms of analog signals in units of Hertz (Hz) or in terms of digital signals in units of bits per second. BITS clock: Building-integrated-timing-supply. A master timing supply for an entire building that provides the master clock for any ancillary equipment. The BITS supplies DS1 and/or composite clock timing references for synchronization to all other clocks and timing sources in the building. BSC: Base station controller. BTS: Base transceiver station. burst: Activity that generates bursts of high data traffic rather than constant demand. burst size: Maximum number of bits that can be transferred over a link during a specified time interval. For AccessGate the maximum burst size is defined in kbit/s. bypass: A device state in which the AccessGate device transfers data it receives at a limited capacity, but does not process the data.
NMS Communications
93
Glossary
C
clear channel: Channel that passes through the system unmodified for the exclusive use of one entity.
D
default gateway: A computer network that serves as an access point to another network. The router that all packets are sent to when the sending device does not have the address of the destination device. DHCP: Dynamic host configuration protocol. A protocol for assigning dynamic IP addresses to devices on a network. downlink: The direction of data transfer that carries data from the network towards the mobile customer or handset.
E
EDGE: Enhanced data GSM environment (EDGE). An extended and enhanced version of GPRS that enables data to be delivered at rates up to 384 Kbps on a broadband. EMS: Element management system.
F
forced bypass: A state in which the AccessGate device transfers data without processing it and does not begin processing data until explicitly commanded to transition to Auto mode.
G
GPRS: General packet radio service. A GSM data transmission technique that does not set up a continuous channel from a portable terminal for the transmission and reception of data, but transmits and receives data in packets.
H
HDLC: High-level data link control. An ISO communication protocol in the data link layer that delineates the beginning and end of GSM and GPRS signaling frames.
I
IMA: Inverse multiplexing over ATM. A physical layer in which a high-speed stream of ATM cells is broken up and transmitted across multiple T1/E1 links, then reconstructed back into the original ATM cell order at the destination. in-path: The normal operating condition for AccessGate 1000 in which the device detects its associated peer (BSC or BTS site) and processes the data that passes between them.
94
NMS Communications
Glossary
Iub: The interface between a Node B and an RNC. 3G equivalent of GSM Abis interface.
J
jitter: Packet delay variation that can impact the quality of the voice conversation. jitter buffer: A software process that eliminates jitter caused by transmission delays. As the jitter buffer receives voice packets, it adds small amounts of delay to the packets so that the received packets can be transferred in the correct order.
L
LAPD: Link Access Procedure on the D channel. ISDN data link layer protocol for the D channel as defined by ITU-T Recommendations Q.920 and Q.921. LAPD is used for signaling and management on Abis links. LED: Light emitting diode. LOF: Loss of frame. An error condition indicating that the receiving equipment has lost frame delineation. LOMF: Loss of multi-frame alignment. LOS: Loss of signal. An error condition indicating that the receiving equipment has lost the received signal.
M
maximum data rate: Maximum number of bits of information that can be transmitted per second in a data transmission link. Typically expressed as megabits per second. maximum packet size: Maximum size, in bytes, of IP packets transferred over AccessGate backhaul connection. MIB: Management information base. An SNMP collection of objects that represent a managed node. Physically, a list of parameters. Logically, a table with rows of parameters. MSC: Mobile switching center. MSO: Mobile switching office.
N
NAT: Network Address Translation. An Internet standard that enables a local-area network (LAN) to use one set of IP addresses for internal traffic and a second set of addresses for external traffic. Nm: Newton meter. A unit of measure used to describe the torque applied to a screw or nut. Node B: The element in a UMTS network which interfaces with the mobile station, analogous to a BTS in a GSM network.
NMS Communications
95
Glossary
O
OAM frames: NMS proprietary frames used to carry device control information over the backhaul link between the AccessGate 1000 BSC device and the AccessGate 1000 BTS device. operator IP traffic: IP traffic that originates from secure operator equipment, for example a third party EMS system located at the cell site, surveillance equipment, or an IP node located at a cell site. overflow: A condition in which buffered information (for example, a jitter buffer) is filled to its capacity when another packet arrives, and consequently the following packet cannot be enqueued.
P
PCU: Packet control unit. Element of the base station that allocates resources for the GPRS packet transmission over the air interface. PCU frames: 20 ms frames containing GPRS or Edge date.
Q
QoS: Quality of service. Term that incorporates bandwidth, latency, and jitter to describe a network's ability to customize the treatment of specific classes of data.
R
RAI: Remote alarm indication. RNC: The element which controls the Node Bs within a UMTS network. It is roughly analogous to a BSC in a GSM network.
S
sequence error: An error condition in which an IP packet is received out of sequence. service trunk: E1 or T1 trunks connected to an AccessGate 1000 device that transfer Abis, Ater, or Iub data to a BSC or BTS devices. The term is used to distinguish trunks bearing Abis, Ater, or Iub data from trunks used to transfer backhaul data. signaling 16: Statistic category indicating the channels carrying signaling frames at 16 kbit/s. signaling 32: Statistic category indicating the channels carrying signaling frames at 32 kbit/s. signaling 64: Statistic category indicating the channels carrying signaling frames at 64 kbit/s. silence frames: Statistic category indicating the number of frames containing silence that are transferred within a specific period of time.
96
NMS Communications
Glossary
static IP route: An IP route that a network administrator manually adds to the IP routing table. subchannel: Subdivision of the E1 or T1 channels received by an AccessGate device into 16 kbit/s or 8 kbit/s streams. subnet mask: A local bit mask (set of flags) that specifies which bits of the IP address specify a particular IP network or a host within a subnetwork. An IP address of 128.66.12.1 with a subnet mask of 255.255.255.0 specifies host 1 on subnet 128.66.12.0. The subnet mask determines the maximum number of hosts on a subnetwork.
T
TCU: Transcoder unit. In Ater networks, a compressor and converter component that processes traffic that comes from the mobile users before and after the traffic goes to the base station controllers. TDM: Time division multiplexing. . A type of digital multiplexing in which two or more apparently simultaneous channels are derived from a given frequency spectrum, i.e., bit stream, by interleaving pulses representing bits from different channels. timeslot: The interval in which each channel broadcasts on a TDM bus or network. It specifies a particular 64 kbit/s subdivision of a TDM bus stream. Timeslots number from zero (0) to n where n is stream dependent. TRAU: Transcoder and rate adaptation unit. An entity that performs a transcoding function for speech channels and RA (rate adaptation) for data channels. TRX: A transceiver in a BTS.
U
unavailable seconds: Statistic category indicating the number of seconds for which the monitored entity is unavailable. underflow: A condition in which buffered information (for example, a jitter buffer) is empty when the source needs to supply data to another entity. uplink: The direction of data transfer that carries data from the mobile customer or handset towards the network.
V
voice frames: Statistic category indicating 20 ms frames containing voice data.
NMS Communications
97
Index
A AccessGate 1000 9 eight-trunk variants 16 electrical requirements 88 environmental requirements 90 equipment list 25 installation overview 27 physical characteristics 87 replacement overview 81 sixteen-trunk variants 14 AccessView application 12 installation sequence 29 ACO switch 19 alarms 48 cable requirements 48 connecting cables 52 connector pinouts 52 altitude 90 assembling the power input connector 40 B backhaul links 9 AccessGate 1000 product description 9 connecting Ethernet cables 50 backhaul trunks connecting cables 55, 59 base station controller (BSC) 9 base transceiver system (BTS) 9 BITS clock 63 blinking trunk LEDs 20 brackets 32, 33 BSC 9 installation procedure 27 C cables 47 BITS clock 63 ground 37 power input connector 40, 43 requirements 48 strain relief housing 41 cabling requirements 74 clocking 18, 63 command line interface 24 computer requirements 24 configuring and verifying with the AccessGate CLI 45 Verifying with the web interface 46 compliance information 91 computer requirements 24 connectivity 50 connectors 18 crimping tool 23 current 88 D DB-9 18 connecting alarm dry relay contacts 52 pinouts 52 installation sequence 29 replacing 81 BTS 9 installation procedure 27 installation sequence 29 private subnet 50 replacing 81 bypass mode trunk allocation 67
NMS Communications
99
Index
deployment considerations 85 E electrical requirements 88 environmental requirements 90 equipment list 25 Ethernet 24 cable requirements 48 connecting cables 50 pinouts 50 RJ-45 connectors 50 extending a device 32 F flammability 90 frames 32 G ground cable 37 grounding a device 37 H hex-socket ratchet 23 humidity 90 I inspecting the equipment 25 installation preparation 27 installation sequence 29 installing a device 34 assembling panel extenders 32 assembling rear supports 33 equipment list 25 grounding 37 installation sequence 29 installation summary 27 installing a power source 39 overview 31 preparing for installation 27 prerequisites 23, 48 tools 23 unpacking and inspecting equipment 25
installing a power source 39 IP backhaul 9, 50 L LEDs 20 M mobile switching offices (MSO) 9 N NMS RJ-45 18, 55, 59 P panel extender brackets 32 physical characteristics 87 physical interfaces 18 power 39 power connector 40 assembling 40 cables 39 installing 43 strain relief housing 41 tools 39 power source installation 39 power supply 40 preparing for installation 27, 31 protected device 86 R ratchet 23 rear mounting brackets 32 rear support brackets 33 recording configuration parameters 29 redundancy 73 failover 76 replacing a protected device 86 rules of operation 80 setting up 78 reference documents 92 regulatory certification 91 removing a device 83 replacing equipment 81 RJ-45 18, 50
NMS Communications
100
Index
RJ-48C 18, 55, 59 S serial port 48 cable requirements 48 connecting cables 49 connectors 18 establishing a connection 49 pinouts 49 service trunks configurations 55, 59 connecting cables 55, 59 strain relief housing 41 T terminal emulator settings 24 terminology 9, 12 tools 23 trunk mapping 65, 66, 77
trunks assignments 67 cable requirements 48 connecting cables 55, 59 manually assigning virtual gateway trunk connections 68 U unpacking the equipment 25 V variants 14, 16 verifying an installation 45, 46 virtual gateways 12, 68 W web browser 45 verifying an installation 46 verifying connectivity 50
NMS Communications
101

13 AccessGate1000InstallationManual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

13 AccessGate1000InstallationManual

Uploaded by

Copyright:

Available Formats

AccessGate 1000 Installation Manual

100 Crossing Boulevard Framingham, MA 01702-5406 USA www.nmscommunications.com

AccessGate 1000 Installation Manual

AccessGate 1000 Installation Manual

AccessGate 1000 Installation Manual

Overview of AccessGate 1000

AccessGate 1000 product description

Circuit switched network T1/E1 links AccessGate 1000 T1/E1 links

Overview of AccessGate 1000

AccessGate 1000 Installation Manual

Packet switched network Ethernet link AccessGate 1000 T1/E1 links

AccessGate 1000 Installation Manual

Overview of AccessGate 1000

AccessGate Virtual gateways

Overview of AccessGate 1000

AccessGate 1000 Installation Manual

TCU device Backhaul AccessGate TRAU MSC

RNC device Backhaul AccessGate RNC

AccessGate 1000 Installation Manual

Overview of AccessGate 1000

Explicit configuration to enter into a bypass state

Protected and unprotected trunks

Overview of AccessGate 1000

AccessGate 1000 Installation Manual

AccessGate 1000 sixteen-trunk variants

AccessGate Power connector Alarm connector Ground studs

Serial port connector

AccessGate 1000 Installation Manual

Overview of AccessGate 1000

Serial port connector

BITS clock connector

Overview of AccessGate 1000

AccessGate 1000 Installation Manual

AccessGate 1000 eight-trunk variants

AccessGate Power connector Alarm connector Ground studs

Serial port connector

AccessGate 1000 Installation Manual

Overview of AccessGate 1000

Serial port connector

VISUAL ETHERNET 2 1 AUDIBLE FAULT STANDBY OK

Overview of AccessGate 1000

AccessGate 1000 Installation Manual

16 trunk rear I/O 8 trunk front I/O 8 trunk rear I/O

AccessGate 1000 Installation Manual

Overview of AccessGate 1000

Overview of AccessGate 1000

AccessGate 1000 Installation Manual

Status LEDs provide the following indications:

Trunk LEDs provide the following indications:

AccessGate 1000 Installation Manual

Overview of AccessGate 1000

These LEDs provide the following indications:

The AccessGate 1000 ACO LED provides the following indications:

For more information, refer to ACO switch on page 19.

Preparing for installation

Attaching a ground cable to the ground lug.

Preparing for installation

AccessGate 1000 Installation Manual

AccessGate 1000 Installation Manual

Preparing for installation

Unpacking and inspecting the equipment

Preparing for installation