IP Network Addressing Scenarios
F-4
3166-A2-GB20-20
March 1999
Scenario 3
This third scenario (Figure F-3) shows a local carrier connected to remote
carriers that have remote standalones. Each carrier must be on a separate
subnet but, as in the previous scenario, the carrier-remote combination can share
a common subnet. Once again, the subnet mask is FF.FF.FF.00 for all devices. A
static route must be set up in the NMS host for each subnet: 135.18.4.0,
135.18.6.0, 135.18.20.0.
ETHERNET
135.18.6.34
496-14647-02
LAN
ADAPTER
T1
COMSPHERE 3610
COMSPHERE 3610
135.18.6.22
135.18.6.1 .
. . .
135.18.6.16
135.18.40.1
COM IP
ADDRESS:
135.18.40.4
SUBNET 135.18.40.0
SUBNET 135.18.6.0
T1
COMSPHERE 3000
135.18.20.45
COMSPHERE 3610
COMSPHERE 3610
135.18.20.23
135.18.20.1 .
. . .
135.18.20.16
SUBNET 135.18.20.0
COMSPHERE 3000
T1
T1
135.18.4.1 .
. . .
135.18.4.16
COMSPHERE 3000
SUBNET 135.18.4.0
T1
T1
Figure F-3.
Local Carrier Connection to Remote Carriers
Summary of Contents for 3166 DSU
Page 1: ...ACCULINK 3166 DSU CSU USER S GUIDE Document No 3166 A2 GB20 20 March 1999...
Page 16: ...About This Guide x 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 20: ...Introduction 1 4 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 68: ...SDCP Operation 3 42 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 102: ...SDCP Menu A 2 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 140: ...Pin Assignments D 12 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 166: ...SNMP MIB Objects E 26 3166 A2 GB20 20 March 1999 This page intentionally left blank...
Page 192: ...Equipment List I 2 3166 A2 GB20 20 March 1999 This page intentionally left blank...