IP Addressing
B-5
9161-A2-GH30-40
April 1999
Routing to Remote Access Units Using Different Subnets
In this example, T1 Access Unit A is connected to:
The NMS at the central site
Two remote T1 access units through EDL management links
The illustration shows two EDL management links, with T1 Access Units B and C
connected through one EDL management link. By configuring a different IP
address and subnet for each management link:
T1 Access Units B and C share a subnet: 135.18.3.0
T1 Access Units A and B share a different subnet: 135.18.2.0
T1 Access Units A and D share yet another subnet: 135.18.4.0
T1
Network
135.18.2.2
496-15187
LAN Adapter
135.18.3.2
135.18.4.26
Subnet 135.18.2.0
A
B
C
D
135.18.40.1
Ethernet
COM Port
IP Address: 135.18.40.3
135.18.4.1
Subnet 135.18.4.0
SNMP NMS
135.18.3.3
Subnet 135.18.3.0
135.18.2.1
Subnet 135.18.40.0
*
Physical Connection
EDL Management Link
This subnet connection can be to any of the following:
• SNMP NMS via the COM Port
• LAN adapter via the COM Port
• Terminal server via the COM Port
*
Summary of Contents for 9161 Single T1
Page 1: ...MODEL 916x 926x T1 ACCESS MUX TECHNICAL REFERENCE Document No 9161 A2 GH30 40 April 1999...
Page 34: ...Management and Control 2 6 9161 A2 GH30 40 April 1999 This page intentionally left blank...
Page 54: ...User Interface 4 10 9161 A2 GH30 40 April 1999 This page intentionally left blank...
Page 92: ...Setting Up 5 38 9161 A2 GH30 40 April 1999 Example Channel Allocation...
Page 142: ...Security 6 10 9161 A2 GH30 40 April 1999 This page intentionally left blank...
Page 252: ...IP Addressing B 8 9161 A2 GH30 40 April 1999 This page intentionally left blank...