Network Design for a Dial NMS Case Study
Configuration Design Parameters
Table 6 Dial NMS Software and Management System Requirements (continued)
Software and Management Systems | Purpose |
|
|
CiscoSecure Unix, version 2.3(3) | • Authenticates, authorizes, and accounts for dial access |
| clients in each POP by using RADIUS. |
| • Authenticates, authorizes, and accounts for router |
| administrators in the NOC by using TACACS+. |
| • Uses AAA accounting records to collect performance |
| data, fault data, and track router configuration changes. |
|
|
War Dialer | Runs performance tests by using a dial simulator and |
| client PCs. |
|
|
Configuration Design Parameters
Before THEnet can implement and operate the dial NMS, several design parameters must be defined by the network engineers and operators.
Each dial POP requires enough IP address space for the POP to grow to its maximum size. For THEnet, each POP must support up to 50,000 lines. Therefore, an entire class B network is initially assigned to each POP.
Figure 7 IP Subnetting Diagram for the THEnet
POP #1
172.21.0.0/16
Access
NOC
Device ID
IP pool
Firewall
| PSTN | Intranet |
| WAN | |
Modems |
| |
|
|
Clients |
|
POP #2 | Access |
172.22.0.0/16 |
|
Firewall
35229
Device ID
IP pool
Internet
To simplify IP address management, each POP uses a similar IP subnetting plan.
Basic Dial NMS Implementation Guide
!!
