Installation Guide

IBR Installation Guide

Page 28 of 38 Doc # 770-00023.1

Jan. 23, 2015

IBR supports SNMP get statements for SNMPv2-MIB, IF-MIB, and FBN-RADIO-MIB. Detailed information for

configuring SNMP is contained in the CLI Guide.

7.5 Switching & Transport

IBR supports 802.1Q (VLAN).

7.6 Data Handling

IBR supports the following OSI

Layer 2 standards:

 IEEE 802.3ab (Gigabit Ethernet);

 IEEE 802.3as (frame expansion);

 IEEE 802.1Q (VLANs).

In addition, IBR supports port mirroring to monitor port traffic.

7.7 Carrier Ethernet

IBR conforms to the following MEF

specifications:

 MEF 9 – Abstract Test Suite for Ethernet Services at the UNI

 MEF 14 – Abstract Test Suite for Traffic Management Phase 1

 MEF 19 – Abstract Test Suite for UNI Type 1

7.8 Timing & Synchronization

IBR’s system clock starts when IBR is powered up and maintains time and date based on Universal Time

Coordinated (UTC), also known as Greenwich Mean Time (GMT). The system clock can be set over the

network via NTP.

Detailed instructions for configuring IBR timing and for displaying system time and date are contained in the

CLI Guide.

7.9 Network Time Protocol (NTP)

NTP runs over User Datagram Protocol (UDP), which runs over IP. It is very efficient and typically requires

no more than one NTP packet per minute to synchronize IBR’s system clock to within one millisecond of the

NTP server’s clock.

When IBR is configured to receive NTP packets from another network device, the relationship between IBR

and that device is called an “association” and it is a server relationship, meaning that IBR will synchronize to

the other device (the “server”) and the other device will not synchronize to IBR.

By default, NTP is disabled on IBR, no NTP associations are defined, and the NTP daemon is not running.

Procedures for enabling and configuring NTP are contained in the CLI Guide.

When IBR is running NTP, IBR can be associated with more than one NTP server. Normally, IBR will

synchronize to the associated NTP server that has the lowest stratum number; that is the lowest number of

hops between the server and its clock source. A stratum 1 time server has a radio or atomic clock directly

attached, a stratum 2 time server receives its time through NTP from a stratum 1 time server, etc.

IBR will avoid synchronizing to a server whose time might not have been synchronized or to one whose time

is significantly different than the time from other associated servers, even if its stratum is lower.

When NTP is enabled on IBR, NTP time will take precedence over time provided by any other source or

method.

Open Systems Interconnection

Metro Ethernet Forum