General description.......................................................................................................................................2
USB Driver Installation & COM Port Setup........................................................................................................24
Installing USB driver....................................................................................................................................25
Configuring COM port................................................................................................................................29
USB CLI access ............................................................................................................................................33
Initial Device setup via USB CLI ................................................................................................................35
Initial Device setup via telnet (directly to Device) ..................................................................................38
Initial Device setup via chassis agent MMU, web-based ........................................................................41
Initial Device setup IP web-based (directly to Device) ...........................................................................44
Status LEDs...................................................................................................................................................72
FBRM/BFFG Part Numbers.................................................................................................................................109
FBRM copper-to-fiber part numbers........................................................................................................109
FBRM fiber-to-fiber part numbers ............................................................................................................112
BFFG copper-to-fiber part numbers.........................................................................................................115
BFFG fiber-to-fiber part numbers .............................................................................................................116
This manual is designed to help you find the information you need quickly. It is
structured as follows:
• Table of Contents (TOC)
• Section TOC: Shows all the major topics in the section
• Side Headings: Shows all the sub topics on each page
• Index
24-Hour Technical Support: 1-800-260-1312 International: 00-1-952-941-7600 iii
Transition Networks
Caution and warnings
Definitions
Cautions
Cautions indicate that there is the possibility of poor equipment performance or
damage to the equipment. The symbol below identifies cautions
Warnings indicate that there is the possibility of injury to person.
Cautions and Warnings appear here and may appear throughout this manual where
appropriate. Failure to read and understand the information identified by the symbol
could result in poor equipment performance, damage to the equipment, or injury to
persons.
When handling chassis Devices observe electrostatic discharge precautions.
This requires proper grounding; i.e., wear a wrist strap.
Warnings
Copper based media ports, e.g., Twisted Pair (TP) Ethernet, USB, RS232,
RS422, RS485, DS1, DS3, Video Coax, etc., are intended to be connected to
intra-building (inside plant) link segments that are not subject to lightening
transients or power faults.
Copper based media ports, e.g., Twisted Pair (TP) Ethernet, USB, RS232,
RS422, RS485, DS1, DS3, Video Coax, etc., are NOT to be connected to
inter-building (outside plant) link segments that are subject to lightening.
DO NOT install the Devices in areas where strong electromagnetic fields
(EMF) exist. Failure to observe this caution could result in poor Device
performance.
Use of controls, adjustments or the performance of procedures other than
those specified herein may result in hazardous radiation exposure.
Visible and invisible laser radiation when open. DO NOT stare into the beam
or view the beam directly with optical instruments. Failure to observe this
warning could result in an eye injury or blindness.
The FBRM and BFFG Devices are designed as standalone models, and also as slidein Devices for the Point System chassis. These Devices can be managed through
SNMP via the Focal Point software (free), Web-based management, Local SNMP,
and USB interfaces.
The CFBRM and CBFFG (chassis Devices), and SFBRM and SBFFG (standalone Devices) are designed to manage Devices remotely through the copper and fiber
ports.
The FBRM or BFFG Devices installed on a network should be configured one as the
local peer and the other as a remote peer for management.
Remote management is accomplished using OAM (Operation Administration and Maintenance) per the IEEE 802.3ah, 2004 standard. Standalone Devices can also be
managed via IP (Web-based) or Telnet.
What is OAM?
In-band
management
USB interface
Point System
mgmt interface
These Devices implement the IEEE 802.3ah standard or (OAM) in the Ethernet first
mile. OAM is a group of network management functions that provide network fault
indications, performance information, data, and diagnosis. These Devices implement
remote management via OAM as per the IEEE 802.3ah standard.
These Devices implement complete Real-Time Multi-Threaded Operating System
(RTOS) with a TCP/IP stack for in-band management.
The USB (Universal Serial Bus) type “B” serial port is used mainly to configure
Device-basic setup before installation and operation on a network.
Implements the current Point System management I
2
C interface. This allows
managing the Device via SNMP, using the existing Point System method.
The FBRM and BFFG Devices support the following management methods:
• USB CLI (Command Line Interface)
• Telnet
• MMU (Management Module Unit) chassis web-based
• IP-based (web-based directly to the Device)
USB management requires a direct connection to the Device via a computer. This
method is used to set up initially or to troubleshoot Devices in the field.
Telnet management requires that the Device be connected to a network. Then from
the CPU command line type Telnet and the Device IP address as shown as follows:
Telnet nnn.nnn.nnn.nnn(represents Device IP address).
MMU
IP-based (web-based)
The MMU (Management Module Unit) is the heart of the Point System chassis’
management capability. It has the ability to monitor and manage all its installed
Devices. The MMU communicates through the CLI presented at the serial port, or
through SNMP, Telnet CLI, and Web interface available via the Ethernet port.
The switch provides complete management through IP via an SNMP interface, webbrowser, or Telnet. The Device provides an embedded web server for web-based
management. It also offers advanced management features and enables Device
management from anywhere on the network through a standard browser, such as
Microsoft Internet Explorer or Netscape.
On the standalone SFBRM and SBFFG Devices only, the rear panel consists of a
power-barrel connector for connecting power via a power adaptor. See Figure 8.
Figure 8: SFBRM/SBFFG 1xxx-1xx Device Real Panel (Standalone Only)
Note: The Point System chassis powers the CFBRM and CBFFG chassis Devices.
The FBRM100Base-FX-to-1000Base-X and the BFFG 1000Base-X-to-1000Base-X
are the Gbit versions of the IEEE 802.3ah managed Devices. The BFFG models link
Gbit fiber connections; the FBRM models convert 100Base-Fx 100 Mbit/s to Gbit.
These Devices function generally in the same manner as copper-to-fiber FBRMs, the
difference is the way the ports are configured. See Tables 1 and 2.
FBRM/BFFG13xx-1xx fiber-to-fiber gigabit models, continued
Connectivity
The different versions of the FBRM and BFFG can be connected and set up to
manage a remote peer completely. In a mixed setup with other FBRM or BFFG
Devices, consider the connectivity scenarios in Figure 9, and the explanation that
follows:
Connection
scenario
explanation
Figure 9: Connectivity Scenarios
In Figure 9, P2 of the active local peer in both scenarios is “OAM enabled” and
“Active” by default. To manage the remote passive peer via OAM, configure P1 of
the active local peer as follows:
• Enable OAM
• Select Active mode
If the connection to the passive remote peer is made thru P2 of the active local peer,
OAM occurs without human intervention.
Note: Automatic firmware upgrades will not occur with different types of FBRM
These SFBRM SFP Devices support fiber redundancy. They have two (2) fiber SFP
ports and one (1) copper port. When you tag the fiber ports as primary and secondary
with redundancy enabled, any fault on the primary port results in the secondary port
becoming operational. There is an option for reverting back to the primary once it
has been restored, or you can continue using the secondary port—these are user
selectable features. See Figure 10.
Figure 10: SFBRMs in Redundant Mode
Explanation
With Port 3 as the secondary port in Redundancy Mode and Port 2, the primary goes
down, the following will happen:
Stage Description
A. All Physical layer and OAM configurations of Port 2 will be applied to
Port 3.
B. Port 2 is disabled, and Port 3 initialized to take over.
C. An SNMP trap is sent indicating that the ports have switched.
D. OAM reinitializes (resets all OAM counters and event logs).
E. All the dynamic MAC entries in the ATU are flushed and the active port
has to relearn the entries.
Note: If the configuration option “revert” is set, when the primary port link is
restored the session will revert back to the primary port. If the “revert’ option
is NOT SET and the primary link is restored, the secondary port remains in
operation until the user intervenes.
In this mode, the Device acts as a 3-port switch with the fiber port connected to 2
remote Devices. See Figure 11.
Figure 11: 3-Port Switch Mode
Note: In 3-port switch mode:
• Only one OAM session can be active at anytime.
• Transparent Link pass through is not applicable in this scenario. The port
link status from the Devices is received only as SNMP traps.
16
Introduction
Caution
In this section
Transition Networks
Section II:
Hardware Installation
This section describes how to install the CFBRM and CBFFG Devices into a Point
System chassis with a remotely managed SFBRM or CFBRM standalone Device.
Also, shows how to install two SFBRM Devices or two SBFFG standalone Devices
on a network, one as a local Device and the other as a remotely managed Device.
When handling chassis Devices observe electrostatic discharge precautions.
This requires proper grounding; i.e., wear a wrist strap. Failure to observe this
caution could result in damage to the chassis Device.
These are the topics:
Topic See Page
Installing CFBRM/CBFFG Devices into a point system chassis 18
Installing SFBRM/SBFFG standalone models 19
Installing copper and fiber cables 20
Connecting power (standalone models) 22
Installing CFBRM/CBFFG Devices into point system chassis
IMPORTANT
Caution
The CFBRM/CBFFG Device product family IS NOT compatible with the CPSMM200 and CPSMM-210 MGMT modules when used in a cascaded application. The
CFBRM/CBFFG can be installed in the “master” chassis with the CPSMM-200
MGMT module, but they can not be installed in a cascaded chassis using the
CPSMM-210 MGMT module.
Alternatively, the CFBRM/CBFFG can be used with the CPSMM120 MGMT
module, which does not support chassis cascading.
Wear a grounding strap and observe electrostatic discharge precautions when
installing the CFBRM/CBFFG Device into the Point System chassis. Failure
to observe this caution could result in damage to the Device.
Chassis Device
installation
To install the chassis Device into the Point System chassis, do the following:
Step Action
1. Locate an empty slot in the Point System chassis.
2. Grasp the edges of the Device by its front panel.
3. Align the Device with the slot guides and carefully insert the Device into
the installation slot.
4. Firmly seat the Device against the chassis back panel.
5. Push IN and ROTATE clockwise the panel-fastener screw to secure the
Figure 13 shows a typical installation involving two (2) SFBRM/SBFFG standalone
Devices on a network.
Figure 13: Installation with Two SFBRM/SBFFG Standalone Devices
Note: With the local active standalone Device connected to a remote standalone
passive Device and with “Mode Control” set to “Auto,” the local (active)
Device will manage the remote (passive) Device. This relationship is
established automatically.
Copper based media ports, e.g., Twisted Pair (TP) Ethernet, USB, RS232,
RS422, RS485, DS1, DS3, Video Coax, etc. are intended to be connected to
intra-building (inside building) link segments that are not subject to lightening
transients or power faults. Failure to observe this caution could result in
damage to equipment.
To install the copper cable, do the following:
Step Action
1. Locate a 10/100 or 10/100/1000Base-T compliant copper cable with
male, RJ-45 connectors installed at both ends.
2. Connect the RJ-45 connector at one end of the cable to the Device’s RJ-
45 ports.
3. Connect the RJ-45 connector at the other end of the cable to the 10/100
or 10/100/1000Base-T RJ-45 port on the other Device (switch, workstation, etc.). See Figure 15.
Transition Networks Section lll: FBRM/BFFG1 Driver Installation & COM Port Setup
Installing USB driver
USB driver
Installing USB
driver
The driver installation instructions are for Windows XP only. Installing the USB
driver using Windows 2000 is similar, but not necessarily identical to the following
Windows XP driver-installation procedure.
Note: The following USB drivers are provided with the product on a CD, also
available at
www.ftdichip.com (click on drivers): WinXP64, Win Server
2003, Win 2002, Win ME/98, Mac OS X, 9, 8, and Linux.
To install the USB driver on a computer with a Windows XP OS, do the following:
Step Action
1. Extract the driver (provided CD or from website) and place it in an
accessible folder on the local drive.
2. Plug the Device into the USB port on the PC to bring up the “found new
hardware” wizard dialog box, shown in Figure 17.
3. Select RADIO button, “No, not this time” as shown in Figure 17.
Section lll: FBRM/BFFG USB Driver Installation & COM Port Setup Transition Networks
Installing USB driver, continued
Step Action
9. After the driver installation is successful, the “finished installing” dialog
box will appear, as shown in Figure 22.
Figure 22: Finish Installing Driver Dialog Box
10. Click the FINISH button and a “found new hardware” message will
appear on the lower right side of the screen, as shown in Figure 23.
Figure 23: New Hardware Installed and Ready to Use
28
Transition Networks Section lll: FBRM/BFFG1 Driver Installation & COM Port Setup
Configuring COM port
Getting COM
port number
You need the COM port number to configure the terminal emulator. To get the COM
port number, do the following:
Step Action
1. On the desktop, right click on the “my computer” icon and select
“Device manager” to open the “computer management” window.
2. Click on “Device manager” to open the Device manager’s panel (screen
right panel) shown in Figure 24.
Figure 24: Computer Management Window
3.
Expand the Ports (COM & LPT) in the right column and write down the
USB COM port number for configuring the terminal emulator software
used for the USB Device.
There are four ways to set up the FBRM/BFFG 1xxx-1xx Devices before the Device
can be operated and managed:
• USB CLI
• Telnet
• Chassis MMU (chassis model)
• IP-based (directly to FBRM/BFFG)
The factory default IP configuration is the following:
• IP address: 192.168.1.1
• Subnet Mask: 255.255.255.0
• Gateway: 192.168.1.2
In this section
These are the topics:
Topic See Page
USB CLI access 33
Initial Device setup via USB CLI 35
Initial Device setup via Telnet (directly to Device) 38
Initial Device setup via chassis agent (MMU) web-based 41
Initial Device setup via IP web-based (directly to Device) 44
Use the ‘set’ commands to set the IP configuration through the USB port. Configure
the Device with a network IP address, subnet mask, and default gateway. Set the IP
address via USB CLI (Command Line Interface), or via DHCP (Dynamic Host Configuration Protocol), which is disabled by default.
The factory default IP configuration shipped with the Device is as follows:
• IP address: 192.168.1.1
• Subnet Mask: 255.255.255.0
• Gateway: 192.168.1.2
Note: Type “help set <command>” to display the format used to set the commands.
Set IP config
via USB CLI
To set the IP via the USB CLI, do the following:
Step Action
At the console> prompt type set ip=nnn.nnn.nnn.nnn
1.
2. Press the ENTER key to set the IP address.
At the console> prompt type set netmask=nnn.nnn.nnn.nnn
3.
4. Press the ENTER key to set the netmask.
At the console> prompt type set gateway=nnn.nnn.nnn.nnn
5.
At the console> prompt type save
6.
7. Press the ENTER key to save the new IP configuration.
The FBRM/BFFG Device provides complete management through the SNMP
interface. It supports the following standard MIBs for management, using SNMPv1:
• RFC 1213 (MIB- II)
• RFC 2819 (RMON – statistics group)
• RFC 2863 (IF MIB counters)
• RFC 3635 (Ether-like MIB counters)
• RFC 1493 (Bridge MIB objects counters)
• RFC 2674 (Bridge extension counters)
I-D: draft-ietf-hubmib-efm-mib (EFM OAM mib – the EFM hub mib is added to the
TN private tree since it has not been added to the ISO tree.) Use the provide version
shipped on the CD with your Device.
See Figure 48.
Device management via IP web-base (directly to Device)
Introduction
IP web-based
management
The FBRM/BFFG Device supports complete Web-based management for viewing
statistics and configuring the Device. See the help file on Transition Networks
website for more details about different configuration variables.
To manage the Device via the IP web-based, do the following:
Step Action
1. Open a web browser.
2. At the URL type the IP address of the Device.
3. Click the GO button to bring up the password screen, shown in Figure 56.
Enter the password (default password is “private”). 4.
Figure 56: Device Password Screen
Note: DO NOT use the browser BACK button to navigate the screens. This will
Device management via IP web-base (directly to Device), continued
OAM
configuration
The OAM configuration screen allows enabling or disabling OAM by setting the
mode to “active” or “passive.” If the remote Device is a Transition Networks
FBRM/BFFG Device, the main menu (PORT button with the remote Device connected) will show the options for managing the remote OAM peer.
The Devices are interoperable with other IEEE 802.3ah compliant Devices. Standard
OAM discovery, loopback, dying gasp, link and other critical events are supported.
The OAM configuration screen for that port will show the following:
• OAM state
• MAC address
• OUI (unique identifier)
Note: On the SFBRM1040-1xx redundant models, there can be only one (1) OAM
session at a time—the OAM enabled port is user selected. Port 2 fiber is the
default port.
OAM config
screen
To view the OAM configuration screen for non-transition networks IEEE 802.3ah
compliant Devices, do the following:
Step Action
1. Click any port VIEW button on the CFBRM/CBFFG main menu to bring
up configure screen of that port.
2. Click the OAM Config button and the screen will appear, as shown in
Figure 58.
3. You can set up OAM parameters on this screen.
Figure 58: OAM Configuration and Status Screen (OAM Config Button)
This section explains the operational status LEDs and what they indicate, along with
product features, and the three (3) methods used to upgrade the software.
Section Vl: FBRM/BFFG Software Features Transition Networks
Software feature descriptions
Note: The FBRM/BFFG Devices does not have configuration switches.
Firmware
activated
features
The FBRM/BFFG series Devices features can be configured via USB, MMU, or IP.
Table 3 explains the configurable parameters of the Devices.
Table 3: Device Software Configurable Features
Feature Description
AutoCrossWhen the AutoCross feature is active, it allows the use
(10/100Base-T or
10/100/1000Base-T)
of a straight-through (MDI) or crossover (MDI-X)
copper cable when connecting to 10/100Base-T or
10/100/1000Base-T Devices. AutoCross determines the
characteristics of the connection and configures the
Devices to link up automatically. This occurs regardless
of the cable configuration: MDI or MDI-X. (Transition
networks recommends leaving AutoCross in default
mode, “enabled.”)
Automatic Firmware
Upgrades
The Device has an automatic firmware upgrade feature.
This feature applies to a communication link between a
local peer and its remote peer Devices connected via a
fiber optic cable. If the remote passive peer Device is not
in Active Mode and a local active peer Device detects a
different firmware revision on its remote passive peer
Device, the local active Device will force a bootload
condition and download its firmware revision to its
remote passive peer Device.
Note The local Device could have a different firmware
revision (newer or older) than its remote peer. In
either case, the firmware revision on the local
Device will replace that of its remote passive
peer.
Note: The firmware of the local active peer Device
should be upgraded before the remote passive
peer Device to ensure that the correct firmware
version is on both Devices.
Transition Networks Section Vl: FBRM/BFFG Software Features
Software feature descriptions, continued
Table 3: Device Software Configurable Features (continued)
Feature Description
Auto-Negotiation This feature allows the two Devices to configure
themselves to achieve the best possible mode of
operation over a link, automatically. The Device
broadcasts its speed and duplex (full or half) capabilities
to the other Device and negotiates the best mode of
operation. Auto-Negotiation allows quick connections
because the optimal link between the Devices is
established automatically.
In a scenario where the Device links to a nonnegotiating Device, disable Auto-Negotiations. In this
instance, the mode of operation will drop to the lowest
common denominator between the two Devices; e.g., 10
Mb/s at half-duplex.
Disabling this feature allows forcing the connection to
the desired speed and duplex mode of operation.
Backup Configuration The firmware uses TFTP to upload its present
configuration onto a TFTP server, and can also
download the configuration from the TFTP server and
update its settings. This is useful when you want to
program more than one unit to the same configuration.
One unit can be programmed and that configuration can
be used to populate the other units. Care should be taken
on some settings such as IP address and VLAN settings.
This feature can be used with ‘ingress/egress’ frames. Bandwidth Allocation by
priority (ingress/egress)
It allows setting the bandwidth in varied increments,
starting at 64kps to full bandwidth.
Rate Limiting based on frame priorities can also be
configured. Each higher priority frame can be
configured to get twice the bandwidth of lower priority
frames; e.g., priority “3” frame configurations can get
twice the bandwidth of priority “2” frames.
Egress bandwidth allocation
in 64Kbits/sec increments:
• Rate limit all frames
Ingress bandwidth allocation
in 64Kbits/sec increments
with four filter selections:
• Rate limit all frames
• Rate limit multicast, flooded unicast, and broadcast
Section Vl: FBRM/BFFG Software Features Transition Networks
Software feature descriptions, continued
Table 3: Device Software Configurable Features (continued)
Feature Description
Congestion Reduction The FBRM and BFFG Devices do not forward collision
signals or error packets between collision domains,
which improves baseline network performance.
In addition, the Devices filter packets destined for local
Devices, which reduces network congestion.
Far-End Fault (FEF)
FEF is a troubleshooting feature. With FEF enabled, if
the receiver on the fiber port goes “down” on one
Device, a FEF idle pattern is sent to the other Device to
terminate data transmission. Then an SNMP trap is sent
to the administrator, identifying the fiber link loss.
If FEF is disabled, a “down” Rx link on one Device
does not transmit to its peer, the down link notification
will not be passed on.
For FEF enabled and disabled scenarios, see illustration
below.
Far-End Fault Detection
(FEFD) Fiber Ports
If FEFD is enabled when the receiver on the fiber port
goes down on one Device, it sends a far-end-fault
pattern to the other side to bring down the fiber port on
both ends. An SNMP trap will be sent to the
administrator, indicating the fiber link loss.
If FEFD is disabled, a “down” Rx link on one Device is
not transmitted to the other Device; the link down signal
will not be passed over the link.
Section Vl: FBRM/BFFG Software Features Transition Networks
Software feature descriptions, continued
Table 3: Device Software Configurable Features (continued)
Feature Description
Operation
Administration and
Maintenance (OAM,
IEEE 802.3ah-2004
standard)
Critical Event (OAM, When the link on the other port fails, the Device sends an
IEEE 802.3ah-2004
standard)
Discovery (OAM,
IEEE 802.3ah-2004
standard)
Event Notification with
Log In (OAM,
IEEE 802.3ah-2004
standard)
Note: On the SFBRM1040-1xx redundant models, there
can be only one (1) OAM session at a time—the
OAM enabled port is user selected. Port 2 fiber is
the default port.
The Device implements the IEEE OAM 802.3ah
standard for troubleshooting and remote management.
This product implements OAM on both the fiber and
twisted pair interfaces. It implements the following
OAM features:
• Discovery
• Remote Loop Back
• Exchange of configuration information and remote
firmware upgrades with organization specific PDUs
• Link status failure indication
The Device implements the draft-ietf-hubmib-efm-mib
(EFM OAM MIB). Use the version provided on the CD.
OAM critical event signal to its peer, indicating the fault
condition.
An active-state Device initiates OAM communications
by sending PDUs across the link connected to an OAM
enabled port. The Device at the other end (if OAM capable) responds to the request from the active Device
by establishing an OAM communications channel.
An OAM link event notifies its OAM peer of any symbol
or frame errors that occurred on its link. The window
used for error monitoring, along with the threshold value
are configurable. At the end of the window, if the errors
are greater than or equal to the threshold value, an OAM
event notification is sent to its peer. If the threshold is set
to zero, then at the end of each window an event
notification is sent—this acts more like an asynchronous
update of the link statistics.
Transition Networks Section Vl: FBRM/BFFG Software Features
Software feature descriptions, continued
Table 3: Device Software Configurable Features (continued)
Feature
Last Gasp/Dying
Gasp(OAM, IEEE
802.3ah-2004 standard)
Remote Loop Back
(OAM, IEEE 802.3ah2004 standard)
Description
All FBRM/BFFG Devices come equipped with a Last
Gasp/OAM Dying Gasp feature. This feature enables
the Device to store a small amount of power to enable
sending an SNMP trap to alert the management console
of a power failure. Feature benefits are the following:
• Notification of an impending power loss before it
happens
• Allows for quicker resolution of the power loss
The default action for last gasp/OAM dying gasp is to
send an SNMP Trap. If the desire is to send a dying
gasp through OAM, it must be configured through the
SNMP/Web interface. It requires choosing the port on
which to send the Dying Gasp command since both
ports are OAM capable. This feature helps
communicate with OAM peers that are not TN Devices.
OAM remote loop back can be used to test link health
by sending a loop back request from the active peer
Device to the remote passive peer Device. Once the
remote passive peer enters loop back mode, all frames
coming into that port are looped back, yet not forwarded
to other ports.
The OAM frames are still exchanged between the local
and remote peer Devices—only OAM frames get
through. The active peer Device discards the frames
coming out of its remote peer Device to prevent
flooding the network. See the illustration below.
Alternate Loop back
This feature can be used to verify end-to-end
connectivity.
OAM Exchange of
configuration
information and remote
upgrades with
organizational specific
PDUs ( IEEE 802.3ah-2004 standard)
Link Status Failure
Indications
Standard MIB Counters
Description
The remote peer Device (only if a TN
FBRM/BFFGDevice) set to passive mode can be
completely managed through the SNMP/Web
management by its active peer Device when set to
Active Mode. This is done using organizational specific
PDUs. When the active peer upgrades to a new revision
of firmware, it detects the firmware configuration of its
remote peer Device and upgrades it automatically.
If the active peer is in a chassis, the remote peer can be
managed through Point System management by the
management module unit (MMU).
Link status failure indication with OAM PDU flags
fielded and sent as an OAM critical event (refer to
57.4.2.1 of the standard).
The Device provides complete management through the
SNMP interface. It supports the following standard
MIBs for management using SNMPv1:
Transition Networks Section Vl: FBRM/BFFG Software Features
Software feature descriptions, continued
Table 3: Device Software configurable Features (continued)
Feature
Pause (flow control) and
Back Pressure
Point System
Management
Description
Pause is used to suspend data transmission temporarily
to relieve buffer congestion. If a Device needs sometime
to clear network congestion, it will send a pause signal
to the Device at the other end, then that Device will wait
a predetermined amount of time before re-transmitting
its data.
This feature reduces data bottlenecks and allows
efficient use of network Devices, preventing data losses.
The pause feature is set in Firmware mode, using the
SNMP interface. It can be set to one of four settings:
• Disable (no pause)
• Symmetrical pause
• Asymmetric TX (transmit) pause
• Asymmetric RX (receive) pause
Note: Enable the “pause feature” if available on ALL
network Devices attached to the media
Device(s), otherwise disable this feature.
Back pressure is used in half duplex mode. Back
pressure ensures the retransmission of incoming packets
when a port using half-duplex is temporarily not able to
receive in coming frames.
The slide-in Device plugs into the chassis to provide
management through the I
Section Vl: FBRM/BFFG Software Features Transition Networks
Software feature descriptions, continued
Table 3: Device Software Configurable Features (continued)
Feature
Transparent Link-Pass
Through (TLPT) and
Auto Link Restoration
Note: In the redundant
models (SFBRM1040-1xx) this feature only
works when the Device
is in redundant mode.
Description
With OAM enabled, TLPT with automatic link
restoration is available for the copper ports on the local
and remote peer Devices. When a copper port goes
“down,” the information is passed to the other Device
and the copper port on that Device will go “down.”
When the link is restored, the link on the other port is
also restored—the fiber ports remain UP. When TLPT is
disabled, if the copper port link drops it does not affect
its peer’s copper port links.
Auto Link Restoration
will restore the broken link
automatically upon correcting the fault condition.
For TLPT disabled and enabled scenarios, see the
illustrations below.
Selective Link Pass
Through
The feature monitors the fiber Rx port for signal loss. If
the fiber Rx goes “down,” the copper port stops
transmitting. See illustration below.
Transition Networks Section Vl: FBRM/BFFG Software Features
Software security feature descriptions
Table 4: Device Software Configurable Security Features
Security Feature
802.1x MAC filtering When enabled on a port, stops learning all MAC
CLI Timeout on Idle If the CLI session on USB/Telnet is idle for more than
IP access (system level/port level)
MAC addresses blocking The MAC address can be added to the static MAC
Management VLAN In a VLAN enabled network, the administrator can
SNMP access The administrator can stop all SNMP access to the
Radius authentication The Device supports authentication using the RADIUS
Description
addresses. To allow any frame with a MAC address not
in the Static MAC database access, the user needs to add
the new address or it will be discarded. This allows
filtering any unauthorized access to the network by
unknown MAC addresses.
two (2) minutes, the session will time out requiring
logging in to re-gain access to the CLI.
Any management of the system via IP can be locked at
the system level, or only on certain ports. For example
management can occur via web/SNMP only on Port 1, so
that access via other ports can be blocked.
address database with the ‘connected port’ as zero. This
will cause any frames from that MAC address database
to cause an ATU-member violation on that port,
resulting in sending a trap. This could cause excessive
traps (overload the CPU with interrupts) depending on
the traffic generated by that MAC. The user can disable
all traps by setting the Ignore SA Violation on the port
that is receiving the MAC address under Advanced Port
Configuration on the web page.
assign a VLAN as a management VLAN. This VLAN
ID will be used in all management frames. This separates
the management traffic from the data.
Device, if not used. This will prevent unauthorized
access to the system configuration, but the SNMP traps
will still be sent.
protocol. When enabled, RADIUS authentication is used
for Web login, serial port, and Telnet authentication.
The Radius server and the shared secret needs to be
configured using CLI/Web/SNMP before enabling
RADIUS authentication.
Section Vl: FBRM/BFFG Software Features Transition Networks
Software security feature descriptions, continued
Table 4: Device Software Configurable Security Features (continued)
Security Feature
Select Link-Pass
Through (LTP)
Note: In the redundant
models (SFBRM1040-1xx) this feature only
works when the Device
is in redundant mode.
USB access The USB port can be turned OFF to prevent
Username/password for
CLI
Description
When enabled, a link change on Port 2 is passed on to
Port 1 (twisted pair). For example on a 10/100BaseT-to-
100Base FX Device, when the (monitored port) fiber
goes DOWN, LPT forces the twisted pair DOWN. The
LPT Port binding allows the user to choose which port to
monitor for LPT.
unauthorized access to the system.
The username and password on the CLI (USB/Telnet) is
configurable and can be set by the administrator.
This section explains the operational status LEDs and what they indicate, along with
product features, and the three methods use to upgrade the firmware.
The FBRM series Devices are designed to operate without user intervention. Use the
status LEDs to monitor Device operation, once it has been installed in the network.
See Figure 59.
Figure 59: FBRM Device LEDs
LED status
tables
Tables 5, 6, and 7 explain the status of the power, USB, twisted pair (TP), and fiber
LEDs.
Table 5: Power and USB LEDs FBRM Devices
LEDs Color Status
Power Green ON has power/OFF no power
USB Green Blinking activity/OFF no activity
Table 6: TP Bi-Color LEDs FBRM Devices
TP LEDs Color Status
Duplex
Yellow Half duplex TPLink/activity:
ON link, BLINK activity
Green Full duplex TPLink/activity:
ON link, BLINK activity
Half Duplex/Link/Active Yellow ON Link, blinking activity
Full Duplex/Link/Active Green ON Link, blinking activity
Speed Yellow ON 10Mbs
Green ON 100Mbs
Table 7: Fiber LEDs FBRM Devices
Fiber LEDs Color Status
Link Active Green ON link, blinking activity
Duplex Green ON full, OFF half
The BFFG copper-to-fiber Gbit series Devices are designed to operate without user
intervention. Use the status LEDs to monitor Device operation, once it has been
installed in the network. See Figure 60.
Figure 60: BFFG Device LEDs
LED status
tables
Tables 8, 9, and 10 explain the status of the power, USB, twisted pair (TP), and fiber
LEDs.
Table 8: Power and USB LEDs BFFG Devices
LEDs Color Status
Power Green ON has power/OFF no power
USB Green Blinking activity/OFF no activity
Table 9: Twisted Pair Bi-Color LEDs BFFG Devices
TP LEDs Color Status
Duplex
Yellow Half duplex TPLink/activity:
ON link, BLINK activity
Green Full duplex TPLink/activity:
ON link, BLINK activity
Half Duplex/Link/Active Yellow ON Link, blinking activity
Full Duplex/Link/Active Green ON Link, blinking activity
Speed OFF 10Mbs
Yellow ON 100Mbs
Green ON 1000 Mbs
Table 10: Fiber LEDs BFFG Devices
Fiber LEDs Color Status
Link Active Green ON link, blinking activity
Duplex Green ON full, OFF half
The FBRM Gbit and BFFG Gbit fiber series Devices are designed to operate without
user intervention. Use the status LEDs to monitor media-Device operation once
installed in the network. See Figure 61.
100Base-X1000Base-X
USBLNKDPXPWRLNK
LED status
table (Gbit)
Power
LED
Fiber Link
1000Base-X1000Base-X
Power
LED
LED
Fiber Link
LED
Duplex
LED
Fiber Link
LED
Fiber Link
LED
USB LED
USBLNKPWRLNK
USB LED
Figure 61: CBFFG/CFBRM1xxx-xx Gbit Device LEDs
Tables 11 and 12 explain the status of the power, USB, link, duplex LEDs for Gbit
FBRM/BFFG Devices.
Table 11: Power and USB LEDs
LEDs Color Status
Power Green ON has power, OFF no power
USB Green Blinking activity, OFF no activity
The firmware image on the Device can be upgraded by these methods:
• TFTP protocol
• XModem
• OAM
When enabled, OAM is done automatically when the active peer detects that its
remotely managed peer is running a different version of the firmware. TFTP and
XModem are initiated by the user. All firmware upgrades are done by the
“bootloader.”
Note: The bootloader recognizes incompatible FBRM/BFFG BIN files when
upgrading. Since there are different FBRM/BFFG Device types, it is possible
that the user could download the wrong BIN file; when it receives an
incorrect file through TFTP or XMODEM, the following message will
appear on the screen:
Bootloader: Hardware and BIN file mismatch, upgrade
aborted.
XModem
method
To upgrade the firmware via XModem, do the following:
Step Action
1.
At the console prompt> type xmodemupgrade
2.
Press the ENTER key and a decision prompt will appear as shown in
Figure 62.
Console:/>xmodemupgrade
Do you wish to proceed to upgrading (y/n):_
Figure 62: Decision Prompt for Firmware Upgrades
Note: If you select “Y,” the firmware image on the targeted Device will be erased.
The Device can be upgraded remotely using TFTP. A valid IP address, subnet,
gateway, TFTP server IP address, and filename must be configured before starting
the upgrade process.
TFTP can be started in the following ways:
• ‘tftpupgrade’ command at the CLI
• On the web using Æ “Local System Configuration” Æ ‘TFTP upgrade’
[perform(1)]
• Using SNMP, set ‘sfbrm100SysTFTPCmd’ to ‘1’ (perform)
After initiating the command, the system resets to start the bootloader, and then the
tftp upgrade will start. A message will appear like the example shown Figure 64.
10/100BaseT to 100BaseFX IPBased 802.3ah Bridge
Version A
Copyright (c) 2006 Transition Networks
Reading config from flash........done
Erasing Application Memory
Set to TFTP Boot from Server nnn.nnn.nnn.nnn
OAM firmware upgrades are done by the local active peer Device to its remote
passive peer Device automatically. This occurs when the active peer Device finds that
its remote peer has a firmware revision different from its own. The active peer Device
sends a bootloader command to its remote peer. When the firmware upgrade on the
remote peer Device is completed, it will perform a “reset” to activate the new
firmware—no user intervention is required. (Active and passive peer relationships are established during configuration.)
The FBRM/BFFG Devices can have a corrupted image for a variety of reasons. If the
image is corrupt, the following will occur: The bootloader checks the CRC to make
sure the image is good; if the check fails, it will re-initiate each method (XMODEM, TFTP, OAM) in an attempt to accomplish the upgrade. The sequences is a follows:
Stage Description
A. XMODEM will re-initiate if there is no input from the console; it will try
the OAM method.
B.
OAM initiates to locate an active peer on the network to get the upgrade
image; if an active peer is not available, it will try the TFTP method.
C.
TFTP initiates a request to the TFTP server to get the upgrade image for
the Device.
D.
This process continuously loops through these upgrade methods until one
of the methods successfully upgrades the firmware image.
Admin
intervention
To do a firmware upgrade from the console, before the bootloader moves to the next
method, it waits for ‘2’ seconds for user input displaying the following message:
“Moving to XMODEM upgrade, Hit 'ESC’ to skip or ctrl-C
for CLI.”
Bootloader CLI
The “bootloader” has a CLI to configure network setting, such as the TFTP server
address, filename, and the boot method to use for upgrading the firmware.
The CLI can be started by pressing any key within ‘2’ seconds before it starts the
CRC validation, or by pressing the CTRL-C keys when it shows the following
message:
Transfer Failed
Moving to OAM, XMODEM or TFTP upgrade, Hit 'ESC' to skip/
To access the bootloader CLI to upgrade the firmware, do the following:
Step Action
1.
When “Transfer Failed” appears on the screen, within ‘2’
seconds, press the CTRL-C keys to bring up the bootloader CLI, as
shown in Figure 65.
10/100BaseT to 100BaseFX IP-Based 802.3ah Bridge
Version A [Mar 2 2006 09:56:02]
Copyright (c) 2006 Transition Networks
Reading config from flash........done.
BOOT LOADER CLI
Type 'h' for help
BOOT:>
Figure 65: Bootloader CLI
2.
At the BOOT:> prompt type the letter “h” to bring up the help screen,
shown in Figure 66.
h Display this help
p Ping a host
z Clear entire Application flash
x Set boot method as xmodem
t Set boot method as tftp
o Set boot method as OAM
s Show system information
n configure network information
r reset system
q Exit Boot CLI
BOOT:>
Figure 66: Bootloader Help Screen
Note: When y ou press the LETTER key of any command it might not appear at
the BOOT:> prompt, but the result will appear on the screen.
At the BOOT:> prompt type the letter “t” to establish TFTP as the reboot
3.
method.
At the BOOT:> prompt type the letter “s” to view system information, as
4.
shown in Figure 67.
System configuration:
IP Address : 192.251.144.150
Subnet Mask : 255.255.255.0
Default Gateway : 192.251.144.2
MAC Address : 00:c0:f2:00:d1:bc
TFTP Server address : 0.0.0.0
TFTP Filename :
BOOT:>
Figure 67: System Configuration Information
5. If system configuration parameters are entered incorrectly or missing as
shown above, at the BOOT:> prompt type the letter “n.”
6. Press the EN TER key until the desired parameter appears on the screen
(TFTP Filename []). See Figure 68.
BOOT:>
Enter the Network configuration IP Address [192.251.144.150]:
Subnet Mask [255.255.255.0]:
Gateway [192.251.144.2]:
TFTP Server IP [0.0.0.0]:
TFTP Filename []:
Figure 68: Network Configuration Screen
7. Enter the necessary data.
8. When done, press the letter “r” key to reboot the Device. The firmware
image will be burned to flash memory of the Device. When completed,
the Device will reboot and return to the Login> prompt.
This section provides basic troubleshooting information for the FBRM/BFFG Device
via a problem and corrective action table. The problems are stated in the problem
column and the action(s) to take for the problem is stated in the corrective action
column. If the corrective measures listed do not correct the problem, contact our 24Hour Technical Support department at 1-800-260-1312, International: 00-1-952-941-
7600.
These are the topics:
Topic See Page
Troubleshooting problem and corrective action table 83
Troubleshooting problem and corrective action table, continued
Problem Corrective Action
The Trap Server does not
record traps
• Ensure the Trap Server application is running. o In the Windows environment, if the “TN” icon is displayed in the
lower right corner of the monitor, then the Trap Server is running.
• SNMP traps may be blocked by a router or firewall. Consult your
Network administrator to determine if this is the case.
• The SNMP trap manager may not be configured properly. The result is
that the SNMP agent does not know the proper IP address. Use the “set”
command to configure the trap manager. Enter the following command
on a single line:
CPSMM100> set=cpsmm100SNMPTrapMgr.<cabinet serial number>.<slot number of the
MM>,ip,<new IP Address of NMS>
• Alternatively, use the “getnext” command to “get” much of this
information and then use the “set=*” command to issue the set request.
The following is an example. Enter “Super-User Mode”:
CPSMM100> su=<private community name>
[su] CPSMM>
Enter the “getnext” command:
[su] CPSMM100> getnext=cpsmm100snmptrapmgr
The response is:
SNMP: GETNEXT [192.251.144.229] id=D2EE6F3F ind=0 cpsmm100snmptrapmgr.1758208.1
1P Address [4/0x4] 192.251.144.235
Enter the set request:
[su] CPSMM100> set=*,ip,172.16.45.105
The response is:
SNMP: SET [192.251.144.229] id=D2EE6F3F ind=0 cpsmm100SNMPTrapMgr.1758208.1
IP Address [4/0x4] 172.16.45.105
Troubleshooting problem and corrective action table, continued
Problem Corrective Action
Unable to do
configuration directly
using IP based
management on Remote
Device
Chassis FBRM/BFFG
not recognized by the
chassis agent
Chassis FBRM/BFFG is
in a single-slot chassis,
but the Port 2 comes up
in OAM “Passive” Mode
with OAM Mode control
is set to ‘auto’
• If the OAM session is active, the active local peer Device sends
configuration information; if the user attempts to go directly to the
remote passive peer Device, the configuration will be overwritten by the
OAM update from the local active peer. It is advisable to always use the
local active peer Device to manage its remote passive peer Device.
WARNING: Visible and invisible laser radiation when open. Do not stare into the
beam or view the beam directly with optical instruments. Failure to observe this
warning could result in an eye injury or blindness.
WARNING: Use of controls, adjustments or the performance of procedures other
than those specified herein may result in hazardous radiation exposure.
Note: The fiber optic transmitters on these Devices meet Class I Laser safety
requirements per IEC-825/CDRH standards and comply with 21
CFR1040.10 and 21CFR1040.11.
WARNING: Visible and invisible laser radiation when open. Do not stare into the
beam or view the beam directly with optical instruments. Failure to observe this
warning could result in an eye injury or blindness.
WARNING: Use of controls, adjustments or the performance of procedures other
than those specified herein may result in hazardous radiation exposure.
1550 nm single mode
min: -5.0 dBm max: 0.0 dBm
min: -34.0 dBm max: -7.0 dBm
29 dB
1550 nm single mode
min: -0.0 dBm max: 5.0 dBm
min: -36.0 dBm max: -3.0 dBm
36 dB