Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Revision History
JAugust 2011—530-027514-01, Revision 1.0.
The information in this document is current as of the date listed in the revision history.
Year 2000 Notice
Juniper Networks hardware and software products are Year 2000 compliant. The JUNOS software has no known time-related limitations
through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
READ THIS END USER LICENSE AGREEMENT ("AGREEMENT") BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE. BY
DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS
CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO BIND
THE CUSTOMER) CONSENT TO BE BOUND BY THIS AGREEMENT. IF YOU DO NOT OR CANNOT AGREE TO THE TERMS CONTAINED
HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS
REGARDING LICENSE TERMS.
1.The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer's principal office is located in the Americas) or
Juniper Networks (Cayman) Limited (if the Customer's principal office is located outside the Americas) (such applicable entity being
referred to herein as "Juniper"), and (ii) the person or organization that originally purchased from Juniper or an authorized Juniper reseller
the applicable license(s) for use of the Software ("Customer") (collectively, the "Parties").
2.The Software. In this Agreement, "Software" means the program modules and features of the Juniper or Juniper-supplied software, for
which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by
Juniper in equipment which Customer purchased from Juniper or an authorized Juniper reseller. "Software" also includes updates, upgrades
and new releases of such software. "Embedded Software" means Software which Juniper has embedded in or loaded onto the Juniper
equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment.
3. License Grant. Subject to payment of the applicable fees and the limitations and restrictions set forth herein, Juniper grants to Customer
a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the
following use restrictions:
a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by
Customer from Juniper or an authorized Juniper reseller.
b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing
units for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey
Access Client software only, Customer shall use such Software on a single computer containing a single physical random access
memory space and containing any number of processors. Use of the Steel-Belted Radius or IMS AAA software on multiple computers
or virtual machines (e.g., Solaris zones) requires multiple licenses, regardless of whether such computers or virtualizations are
physically contained on a single chassis.
c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may
specify limits to Customer's use of the Software. Such limits may restrict use to a maximum number of seats, registered endpoints,
concurrent users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the
purchase of separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide
throughput, performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits
may restrict the use of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with
other specific Software. Customer's use of the Software shall be subject to all such limitations and purchase of all applicable
licenses.
d. For any trial copy of the Software, Customer's right to use the Software expires 30 days after download, installation or use of the
Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer
may not extend or create an additional trial period by re-installing the Software after the 30-day trial period.
e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer's
enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the
Steel-Belted Radius software to support any commercial network access services.
The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase
the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.
4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees not
to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized copies of
the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the Software, in any
form, to any third party; (d) remove any proprietary notices, labels, or marks on or in any copy of the Software or any product in which the
Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper equipment sold
in the secondhand market; (f) use any 'locked' or key-restricted feature, function, service, application, operation, or capability without first
purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application, operation, or
capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the Software in any
manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i) use Embedded
Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that the Customer
did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking
to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly provided
herein.
5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper,
Customer shall furnish such records to Juniper and certify its compliance with this Agreement.
6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper.
As such, Customer shall exercise all reasonable commercial efforts to maintain the Software and associated documentation in confidence,
which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software
for Customer's internal business purposes.
7. Ownership. Juniper and Juniper's licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to the
Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance of
any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies of
the Software.
8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty
statement that accompanies the Software (the "Warranty Statement"). Nothing in this Agreement shall give rise to any obligation to
support the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support
services agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS
OF DATA, OR COSTS OR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES, OR FOR ANY SPECIAL, INDIRECT, OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THIS AGREEMENT, THE SOFTWARE, OR ANY JUNIPER OR JUNIPER-SUPPLIED
SOFTWARE. IN NO EVENT SHALL JUNIPER BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY
JUNIPER OR JUNIPER-SUPPLIED SOFTWARE. EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT
PERMITTED BY LAW, JUNIPER DISCLAIMS ANY AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED,
STATUTORY, OR OTHERWISE), INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE,
OR NONINFRINGEMENT. IN NO EVENT DOES JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK
RUNNING THE SOFTWARE, WILL OPERATE WITHOUT ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO
INTRUSION OR ATTACK. In no event shall Juniper's or its suppliers' or licensors' liability to Customer, whether in contract, tort (including
negligence), breach of warranty, or otherwise, exceed the price paid by Customer for the Software that gave rise to the claim, or if the
Software is embedded in another Juniper product, the price paid by Customer for such other product. Customer acknowledges and agrees
that Juniper has set its prices and entered into this Agreement in reliance upon the disclaimers of warranty and the limitations of liability set
forth herein, that the same reflect an allocation of risk between the Parties (including the risk that a contract remedy may fail of its
essential purpose and cause consequential loss), and that the same form an essential basis of the bargain between the Parties.
9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination of
the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related
documentation in Customer's possession or control.
10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from
the purchase of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction
shall be provided to Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All
payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in
connection with such withholding taxes by promptly: providing Juniper with valid tax receipts and other required documentation showing
Customer's payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to be
paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with all
applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any liability
incurred by Juniper as a result of Customer's non-compliance or delay with its responsibilities herein. Customer's obligations under this
Section shall survive termination or expiration of this Agreement.
11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any
applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such
restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the
Software supplied to Customer may contain encryption or other capabilities restricting Customer's ability to export the Software without
an export license.
12. Commercial Computer Software. The Software is "commercial computer software" and is provided with restricted rights. Use,
duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS
227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.
13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer with
the interface information needed to achieve interoperability between the Software and another independently created program, on
payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use
such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.
14. Third Party Software. Any licensor of Juniper whose software is embedded in the Software and any supplier of Juniper whose products
or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement,
and such licensor or vendor shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third
party software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the
extent portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for
such portions publicly available (such as the GNU General Public License ("GPL") or the GNU Library General Public License ("LGPL")),
Juniper will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to
three years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale,
CA 94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGP L at
http://www.gnu.org/licenses/lgpl.html.
15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws
principles. The provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes
arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal
courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer
with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written
(including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an
authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained
herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing
by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity
of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the
Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de
même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise. (Translation: The parties confirm that
this Agreement and all related documentation is and will be in the English language)).
This preface provides the following guidelines for using the BX7000 Multi-Access Gateway
Hardware Guide:
z Objectives on page xiii
z Audience on page xiii
z Documentation Conventions on page xiv
z List of Technical Publications on page xv
z Obtaining Documentation on page xv
z Documentation Feedback on pagexvi
z Requesting Support on page xvi
Objectives
About This Guide
Audience
This guide describes the hardware components, installation procedures, basic configuration
procedures, and basic troubleshooting procedures for the BX7000 Multi-Access Gateway. It also
explains how to prepare your site for the gateway installation, unpack and install the hardware,
power on the gateway, and perform routine maintenance. After completing the installation
procedures covered in this guide, see the BXOS Configuration Guide for information about further
BX operating system (BXOS) configuration.
This guide is designed for network administrators who install, set up, monitor, and maintain the
gateway or prepare a site for gateway installation. It is intended for the following audience:
z Customers with technical knowledge and experience with networks and network security, the
Internet, and Internet routing protocols
z Network administrators who install and manage the gateway
Personnel operating the equipment must be trained and competent; must not conduct themselves
in a careless, willfully negligent, or hostile manner; and must abide by the instructions provided in
the documentation.
Documentation Conventions
Table 1 on page xiv defines the notice icons used in this guide.
Table 1 : N ot ice I cons
IconMeaningDescription
Information NoteIndicates important features or
instructions.
CautionIndicates a situation that might
result in loss of data or hardware
damage.
WarningAlerts you to the risk of personal
injury or death.
Laser WarningAlerts you to the risk of laser
hazard.
Table 2 on page xiv defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ConventionDescriptionExamples
Bold sans serif typefaceRepresents text that you type.To enter configuration mode, type the
configure command:
cli@BX7000> configure
Fixed-width typeface
Represents output on the terminal screen.cli@BX7000> show chassis alarms
No alarms currently active
Italic typefacez Introduces important new terms.
z Identifies book names.
z Identifies RFC and Internet draft titles.
Italic sans serif typeface
Represents variables (options for which you
substitute a value) in commands or configuration
statements.
Sans serif typefaceRepresents names of configuration statements,
Table 3 on page xv lists the BX7000 Multi-Access Gateway documentation.
To configure and operate the BXOS software, use the configuration statements and operational
mode commands documented in the BXOS Configuration Guide and BXOS CLI Users Guide and Command Reference.
BXOS Configuration GuideProvides a detailed software description of the BXOS software. This guide:
BXOS CLI Users Guide and Command
Refer ence
BX7000 Multi-Access Gateway Getting
Started Guide
Provides a detailed hardware description of the gateway. This guide:
z Explains how to unpack, install, mount, access, and maintain the gateway.
z Explains the various hardware components such as power supply, chassis, and ports.
z Provides troubleshooting of the hardware-related issues.
z Explains the configuration statements used to configure various properties of the
gateway.
z Describes how to configure the basic system properties, protocols, interfaces,
pseudowires, and tunnels.
z Explains statement hierarchies and parameters used in configuration.
Provides a detailed description of all the configuration mode and operational mode
commands. This guide:
z Explains how to start the CLI and the components of the CLI.
z Contains information about the commands used to set the gateway properties (set
commands) and the commands used to view the outputs (show commands).
Provides an overview on installing the gateway. This guide:
z Explains how to quickly set up the gateway.
z Contains the basic steps to install the gateway and establish the basic gateway
connectivity.
Obtaining Documentation
To obtain the most current version of all Juniper Networks technical documentation, see the
products documentation page on the Juniper Networks web site at: http://www.juniper.net/
To order a documentation CD, which contains this guide and other Juniper Networks technical
documents, contact your sales representative.
List of Technical Publicationsxv
About This Guide
Copies of the Management Information Bases (MIBs) available in a software release are included
on the documentation CDs and at http://www.juniper.net/
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can improve the
documentation. You can send your comments to techpubs-comments@juniper.net, or fill out the
documentation feedback form at https://www.juniper.net/cgi-bin/docbugreport/. If you are
using e-mail, be sure to include the following information with your comments:
z Document name
z Document part number
z Page number
z Software release version (not required for Network Operations Guides [NOGs])
Requesting Support
Technical product support is available through the Juniper Networks Technical Assistance Center
(JTAC). If you are a customer with an active J-Care or JNASC support contract, or are covered under
warranty, and need post sales technical support, you can access our tools and resources online or
open a case with JTAC.
z JTAC policies—For a complete understanding of our JTAC procedures and policies, review the
JTAC User Guide located at
http://www.juniper.net/customers/support/downloads/710059.pdf.
z Product warranties—For product warranty information, visit
http://www.juniper.net/support/warranty/
z JTAC Hours of Operation —The JTAC centers have resources available 24 hours a day, 7 days a
week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online self-service portal
called the Customer Support Center (CSC) that provides you with the following features:
z Find CSC offerings: http://www.juniper.net/customers/support/
z Search for known bugs: http://www2.juniper.net/kb/
z Find product documentation: http://www.juniper.net/techpubs/
z Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
z Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
z Search technical bulletins for relevant hardware and software notifications:
https://www.juniper.net/alerts/
z Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
z Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE)
Tool located at https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
This chapter gives an overview of BX7000 Multi-Access Gateway. It contains the following
sections:
z BX7000 Multi-Access Gateway Overview on page 3
z Gateway System Architecture on page 3
z Hardware Components on page 4
z Advanced Clocking Module on page 13
BX7000 Multi-Access Gateway Overview
The gateway is a mobile backhaul aggregation system that supports both Ethernet and
time-division multiplexing (TDM) interfaces. It aggregates 2G TDM and 3G Asynchronous Transfer
Mode (ATM) cellular traffic streams (voice, audio, and video) from multiple cell sites and carries
the streams towards the base station controller (BSC) or radio network controller (RNC) over
emulated circuits. It allows simultaneous delivery of real-time and delay-tolerant traffic, enhancing
bandwidth utilization. In addition, it performs IPv4 forwarding.
Gateway System Architecture
The gateway can be deployed at the cell sites (base transceiver station (BTS)) and access or
aggregation hub for the cell sites. The gateway architecture separates the control operations from
the packet forwarding operations, which helps to eliminate processing and traffic bottlenecks.
The gateway architecture consists of two parts:
z Packet processor—Performs route lookups, packet forwarding, and interworking functions for
pseudowire aggregations
z Host processor—Provides Layer 3 routing services and network management
Though there are two logical parts, physically they are packaged in a single integrated chip, using
an internal fabric to communicate with each other. The packet processor and the host processor
are realized using an off-the-shelf network processor. See Figure 1 on page 4 for an overview of the
gateway architecture.
Figure 1: System Architecture of the BX7000 Multi-Access Gateway
Host Processor
Fabric
Packet Processor
The packet processor consists of four packet processing engines that perform Layer 2 and Layer 3
packet switching. It can process packets at an aggregate rate of 120 megabits per second. The
network processor promotes quick movement of packets through the gateway.
Host Processor
The host processor handles all routing protocol processes as well as the software processes that
control the gateway interfaces, the chassis components, the system management, and user
access to the gateway. These routing and software processes run on top of a kernel that interacts
with the packet processor. The host processor handles all packets that concern routing protocols,
freeing the packet processor to handle only packets that transit through the system. It also
provides different levels of system configuration and management functions, including
command-line interface (CLI), SNMP, and a NETCONF interface.
Hardware Components
This section provides the overview of the gateway’s hardware components:
z Gateway Chassis on page 4
z Front Panel on page 5
z LEDs on page 5
z T1/E1 Ports on page 6
z Ethernet Ports on page8
z Console Ports on page 11
z USB Host Port on page 12
z External Alarm Contacts on page 12
z Power Supplies on page 12
Packets in
Packet Processor
Packets out
g002900
Gateway Chassis
The chassis of the gateway is a rigid sheet metal structure that houses all the other gateway
components (see Figure 2 on page 5). The chassis measures 2.6 in. (6.7 cm) high, 17.51 in.
(44.47 cm) wide, and 9.44 in. (23.97 cm) deep (from front to the rear of the chassis) and installs in
a standard 19-in. equipment rack or in a standard enclosed cabinet.
Table 1 on page 5 summarizes the physical specifications for the gateway chassis.
Table 1: Physical Specifications
DescriptionVal ue
Chassis dimensions2.6 in. (6.7 cm) high
17.51 in. (44.47 cm) wide
9.44 in. (23.97 cm) deep (from front to rear chassis)
Gateway weightDC model: 14.1 lb (6.4 Kg)
AC model: 13.22 lb (6.0 kg)
The gateway chassis can be mounted horizontally in a rack or vertically on a wall. All the power
receptacles, input/output ports, and expansion slots are located on the front panel of the gateway.
Figure 2: Front View of the BX7000 Multi-Access Gateway
Front Panel
LEDs
The front panel of the gateway has two power supplies, 16 T1/E1 ports, two console ports, one
universal serial bus (USB) host port, five Ethernet ports, one external alarm contact, LEDs that
allow you to view the status of the gateway and the ports, and two slots for expansion (see
Figure 3 on page 5).
Figure 3: Front Panel of the BX7000 Multi-Access Gateway
Power supplies
BX 7000
CLOCK CARD
EXPANSION BAY
INTERFACE CARD
EXPANSION BAY
RJ-45 console port
USB host port
System LED
1 3 5 7 9 11 13 15
0 2 4 6 8 10 12 14
Copper ethernet ports
USB console port
T1/E1 Ports
Optical ports
External alarm
Grounding studs
Port LEDs
For more information on port LEDs, see “T1/E1 Ports” on page 6 and “Ethernet Ports” on page 8.
Hardware Components5
g002902
CHAPTER 1: BX7000 Multi-Access Gateway Overview
System LED
A tricolor system LED indicates the status of the power supplies, temperature, and conditions
based on chassis configuration such as LOS (loss of signal), Ethernet link down. A condition that
causes a change in the system LED indication also activates the corresponding alarm relay contact
on the front panel. Table 2 on page 6 describes the status of the system LED.
Table 2 : Syste m LE D
ShapeColorStateDescription
Green
On steadilyThe gateway is functioning normally,
temperature and outputs are within
range, and no alarms are present
Ye l lo w
On steadilyA non-critical or minor condition
requires monitoring—Possible causes
include one of the power supplies
removed from the gateway or high
temperature
Red
On steadilyA critical condition that can cause the
gateway to stop functioning and
requires immediate attention—
Possible causes include component
removal or failure
Off
Gateway powered down or initializing
Synchronization Status LED on the Advanced Clocking Module
The advanced clocking module has a bicolor LED to indicate the synchronization status of the
clocks. Figure 4 on page 6 shows the LED of the advanced clocking module. If the LED is green, the
advanced clocking module is locked with an input source. If the LED is amber, the advanced
clocking module is currently not locked and is either in holdover mode or free-running mode.
Figure 4: LED in the Advanced Clocking Module
LED
T1/E1 Ports
The T1/E1 ports provide connection to T1 or E1 network media types such as switches. They receive
incoming packets from the network and transmit outgoing packets to the network.Figure 5 on
page 6 shows the T1/E1 ports.
For information about the ports and connectors in the gateway, see Table 3 on page 8.
g002940
Hardware Components7
CHAPTER 1: BX7000 Multi-Access Gateway Overview
Table 3 : T 1/ E1 Po rt s
Descriptionz 16 RJ-45 ports which can be configured either as T1 or E1
Hardware featuresz 16 T1/E1 ports supporting ATM, IMA, High-Level Data
Software features
Cables and connectors16 RJ-45 connectors (one per port)—RJ-45 to RJ-45
LEDsTwo rectangular single color LEDs for each T1/E1 port
Alarms, errors, and eventsz Alarm Indication Signal (AIS, YLW)
Link Control (HDLC)
z LEDs for status indication; for more information, see
LEDs
on page 8
z T1 framing: super frame (SF) and extended super frame
(ESF)
z E1 framing: G.703
z G.704—Channel Associated Signaling Multiframe
Format
z G.704-no-crc—Basic E1 framer format without CRC
z Per-port loop timing
z Integrated support for G.703 unframed mode and G.704
Channel Associated Signaling Multiframe Format; and
G.704-no-crc
z Encapsulations:
− High-Level Data Link Control (HDLC)
− Asynchronous Transfer Mode (ATM)
− Inverse Multiplexing over ATM (ATM-IMA)
− Point-to-Point Protocol (PPP)
− Transparent (Trans)
interface cable, Category 3
Link LED
z Green is lit in the following conditions:
− Admin-state is up and there is traffic through the port
− Admin-state is up and link is up
z Green is off in one of the following conditions:
− Error in traffic
− Link is down
− Admin-state down
Error LED
z Yellow is lit in the following error conditions:
− Admin-state is up and error in traffic
− Admin-state is up and link is down
z Yellow is off during admin-state down
z Excessive zeros (EXZ)
z Loss of frame (LOF), Loss of signal (LOS)
z Controlled Slip (CS)
Ethernet Ports
Five Ethernet ports are located in the lower right of the gateway (see Figure 6 on page 9). The
Ethernet ports can be used as either data ports or management ports.
z Three (10/100/1000Base-TX) copper Ethernet ports labeled ETHERNET 0, ETHERNET 1, and
ETHERNET 2.
z Two (1000 Base-X-SFP) fiber-optic Gigabit Ethernet ports with small form-factor pluggable
transceivers (SFPs) labeled ETHERNET 1 and ETHERNET 2.
SFPs contain optical transceivers that support fiber-optic cable. Two rectangular LEDs on each
side of the copper Ethernet ports and two circular LEDs above each SFP show the link and the
status of ports. Table 4 on page 10 describes the functions of the Ethernet ports.
Note: For ETHERNET 1 and ETHERNET 2, you can connect both the copper Ethernet port and
the fiber-optic Ethernet port. However, only the copper port or the fiber-optic port can be active
at a time. If both ports are connected, the fiber-optic port will be active.
You can also use combination of these ports as follows:
z ETHERNET 1 of copper Ethernet port and ETHERNET 2 of fiber-optic Ethernet port
z ETHERNET 2 of copper Ethernet port and ETHERNET 1 of fiber-optic Ethernet port
Figure 6: Ethernet Ports
ETHERNET 0
COPPER
ETHERNET 1
COPPER
Copper Ethernet ports
ETHERNET 2
COPPER
ETHERNET 1
SFP
ETHERNET 2
SFP
ALARM
Fiber-optic Ethernet ports
g002908
Hardware Components9
CHAPTER 1: BX7000 Multi-Access Gateway Overview
Table 4: Ethernet Ports
Descriptionz 3—10/100/1000 Base-TX copper Ethernet ports that
Hardware featuresz Auto-negotiation for copper ports
Software features
Cables and connectorsz Copper (10/100/1000Base-TX): Unshielded twisted
LEDs
support Ethernet, Fast Ethernet, or Gigabit Ethernet
ports
z 2—1000 Base-X-SFP fiber-optic Gigabit Ethernet ports
z Cable crossover detection for copper ports
z High-performance throughput on each port at speeds
up to 1000 Mbps
z Full-duplex mode
z Maximum transmission units (MTUs) of up to 1500
bytes
z IP routing
z 802.1Q VLAN encapsulation support
z MPLS encapsulation support
pair (UTP), Category 5e or 6 cable, RJ-45 connector
z Use Category 5e UTP cables for copper Ethernet ports if
the installation environment requires radiated noise
immunity <= 3 V/m, conducted noise immunity <= 3 V
z Use Category 5e shielded twisted pair (STP) cables for
copper Ethernet ports if the installation environment
requires radiated noise immunity > 3 V/m, conducted
noise immunity > 3 V
z SFP: For more information on optical interface support,
see Table 5 on page 11
z Two rectangular LEDs on each side of the copper
Ethernet ports
z Two circular LEDs above each fiber-optic Ethernet port
LED activities for both the copper and the fiber-optic
Ethernet ports are as follows:
You can connect a console directly to the RJ-45 console port or to the USB 2.0 full-speed port of
the gateway. These two ports are labeled as CONSOLE (see Figure 7 on page 11).
Figure 7: Console Ports
RJ-45 console port
USB console port
z RJ-45 console port to connect the gateway to the serial port (RS-232 Port/COM port) of the PC
having console terminal session. An RS-232 serial cable with an RJ-45 connector is required.
z USB Type B console port to connect the gateway to the Type A USB port of the PC having
console terminal session. A standard USB cable with Type B connector is required.
Note: Although you can connect management devices to both console ports, only one console
port can be active at a time. If you connect to both the console ports, the USB console port will be
activated.
g002941
Hardware Components11
CHAPTER 1: BX7000 Multi-Access Gateway Overview
USB Host Port
Use the high-speed 2.0 USB host port, labeled FLASH, to connect a USB mass-storage device,
such as flash drive. The gateway uses this port to read configuration files during the initial startup.
This port supports a USB with Type A connector.
External Alarm Contacts
The gateway has four external alarm contacts (also known as potential free contacts) for
connecting the gateway to external alarm devices. The alarm relay contacts are located at the
lower right of the front panel. Whenever a system condition triggers an alarm, the alarm relay
contacts are activated which in turn activates the external alarm devices. Single core wires with a
gauge between 26-AWG and 24-AWG (0.5 to 0.8 mm2) are required to connect to external alarm
devices. For more information, see Connecting to an External Alarm Device on page 35.
The external alarm contact has eight pins that accept single core wire. Use the gauge of wire
appropriate for the external device that you are connecting. Each pair of pins adjacent to each
other, starting from the left, can be used to connect to one external alarm device. A total of four
devices may be connected to the wire-trap connector using the eight pins.
Power Supplies
The gateway contains one or two power supplies located on the left side of the front panel of the
chassis. The gateway uses either AC or DC power supplies. For both AC and DC power
configurations, the power supplies are hot-swappable when the gateway contains two power
supplies. If one power supply fails or is removed, the other power supply instantly takes the entire
electrical load without interrupting the operation of the gateway. For more information on AC and
DC power specifications, see “AC Power Specifications” on page 77 and “DC Power Specifications”
on page 78.
AC Power Supply
Each inlet requires a dedicated AC power feed. When both the power supplies are present, they
share the load almost equally within a fully populated gateway. Each power supply provides power
to all components in the gateway. Two AC power supplies provide full power redundancy. One
power supply provides full power to the gateway as long as it is operational. Figure 8 on page 12
shows the AC power supply.
Figure 8: AC Power Supply
DC Power Supply
Each DC power supply provides sufficient power to the fully populated gateway. The DC power
supplies can be either hardened or non-hardened. Two DC power supplies share power equally
within a gateway. Figure 9 on page 13 shows the DC power supply.