Paradyne 3166 CSU, 3166 DSU IP Networking Address Scenario F

F-1
3166-A2-GB20-10 November 1998
IP Networking Address Scenario F
Overview
This appendix describes a means of configuring 31xx Series devices in an
Internet Protocol (IP) network to provide SNMP or Telnet connectivity. Since there
are many possible network addressing schemes, this appendix describes an
addressing scheme for typical customer network management system (NMS)
scenarios. This appendix is not intended to be an IP addressing or routing
tutorial, and a basic understanding of IP and 31xx Series devices is assumed.
The following notes apply to these scenarios:
31xx devices besides the Model 3166 include:
— Model 3160 (2-port standalone)
— Model 3161 (carrier-mounted card used with auxiliary backplane)
— Model 3162 (2-port standalone)
— Model 3164 (4-port standalone)
— Model 3165 (1-port standalone)
Connections to remote devices may be via EDL (for the Model 3166 and
2-port and 4-port DSU/CSUs) or FDL; however, the FDL is only available on
full T1 links (not fractional T1s). Check with the service provider to be sure
that the FDL is end-to-end (i.e., not terminated at an intermediate point within
the network).
Interconnected 31xx Series devices automatically pass routing information
between them; however, a static route to the subnet(s) must be set in the
routing table of the NMS host. This route uses the 31xx Series device
connected to the LAN (via the LAN Adapter), or the NMS (via a direct PPP or
SLIP connection) as a gateway to the subnet(s). In all instances, the
addressing scheme presented works for both the LAN and the direct
connections.
Although routing table entries are maintained automatically by 31xx Series
devices, without the need for user configuration, only a maximum of 100
routes is supported for a given device.