O9500 and

AM3440 IN-Band
Application

1
Application Diagram

E1/T1
PDH Cloud AM3440#2

O9500#1

O9500#2 NMS Server

IP
E1/T1

PDH Cloud RT-A

AM3440#1
LAN1
Network
Conceptual Diagram
IB

E1/T1
Note* AM3440#2

IB
(Router)

O9500#1
DCC DCC
(Router) (Router)

DCC DCC
(Router) (Router)
O9500#2
Note*2 IB

IB
E1/T1

RT-A
(Router)
WAN1 LAN1
Note*1
WAN2

3
 Network Planning
IN-Band Port1 TS1 to Trib-11 Port1 TS1 10.4.1.1/24
IB

E1/T1
10.4.1.2/24 Note* AM3440#2

IB
(Router) Slot 1 Port 1 TS1 to IN-Band

O9500#1
DCC DCC
(Router) (Router)
192.167.1.2/24 192.167.1.2/24

Slot C Port 1TS1 to IN-Band PC:192.168.14.24/24

192.167.1.1/24 192.167.1.1/24
DCC DCC 10.4.3.1/24
(Router) (Router)
O9500#2
IB
E1/T1(Slot 1)

RT-A(Slot C)
IB
10.4.3.2/24
(Router)
WAN1 LAN1: 192.168.14.220/24
10.4.2.2/24

IN-Band Port1 TS1 to Trib-11 Port1 TS1 WAN2

10.4.2.1/24
Slot C Port 1 TS2 to Slot1 Port 1 TS1 4
Note*1
High-speed 16E1/T1 or Low-speed QuadE1

On O9500, either High-speed 16E1/T1 or Low-speed QuadE1 can be the

choice to connect with AM3440 Quad E1; however the QuadE1 would be the
best choice to simplify the O9500 configuration.
For Low-speed Quad E1, it is very simple that IN-Band port just directly
cross connect to the QuadE1.
For High-speed 16E1/T1, the VTE channel must be applied to intermediately
cross connect between High-speed 16E1/T1 and IN-Band port.

5
Note*2
Operational Mode of DCC

In this IN-Band application, since the IN-BAND of O9500 is configured as

Router mode using RIP II Routing Protocol, then it is necessary for O9500
DCC interface to be in Router mode using RIP II as well.
This is because for the RIP Routing Mechanism, the device will broadcast
the RIP Routing Table to its all RIP-enabled Router interfaces. Thus if only
O9500-IN-Band port is RIP-enabled and O9500 DCC is in Bridge mode, then
only the IN-Band port on the O95000 is aware of the RIP Routing Table and
cannot pass this RIP Routing Table to another O9500 IN-Band port via its
own DCC.
This implies, if IN-Band of O9500#1 and O9500#2 are configured as RIP-
enabled Router interface and both DCC are in Bridge mode, then NMS
Server in this case can only access O9500#2 IN-Band, O9500#2 DCC and
O9500#1 DCC, but never O9500#1 IN-Band.

6
Introduction to
O9500 IN-Band

7
IN-Band Channel

8
IN-Band Channel Bandwidth
How many bandwidth of IN-Band on O9500?

There are 16 IN-Band ports are available on a O9500 XCU card, and these
16 ports are allocated with total 32 timeslot for flexible bandwidth utilization,
note that there is no limitation of how many timeslots can be assigned to a
single IN-Band port.

9
IN-Band Channel Bandwidth

10
Introduction to
AM3440 IN-Band

11
AM3440 Management Interfaces

The SNMP agent on AM3440 has two network

interfaces, LAN and WAN.
LAN interface is actually the physical SNMP Port
on the AM3440 controller and can be used for
Out-of-Band Management.
LAN WAN interface is a 64K channel that can be cross
(SNMP) connected to a Router WAN interface or a E1/T1
timeslot and require a counter WAN interface to
SNMP Agent talk to; since the 64K of user traffic will be used
thus it is so called IN-Band Management.
WAN
(IB)

AM3440 unit

12
Configuration
Procedure

13
14
 Headline

Content

15