|
|
This case study describes how two companies set up basic modem IP services by using Cisco AS5x00 network access servers.
The two companies
This case study
![]() |
Note The term Cisco AS5x00 refers to the Cisco AS5300 and AS5800 network access servers. Although this case study uses two specific companies as examples and seems very specific at times, the principles in this case study can be applied on a general level. |
The following two companies are used in the case study:
Both companies
This case study describes how to set up one network access server (NAS). Setting up the following components is outside the scope of this document:
Both companies answer a planning questionnaire. Based on their design choices, both companies create a network-service definition.
The dial questionnaire in Table 1-1 shows the following:
| Design Questions | Design Options | Maui Onions' Design Choices | THEnet's Design Choices |
|---|---|---|---|
What is the user-growth projection for the next 5 years.1 |
| 500 users 1,000 users 2,000 users | 5,000 users 20,000 users 1 million users |
What is the user-to-line ratio during busy hours? |
| 15:1 | 10:1 |
What access media is used for the dial services? |
| Yes No | Yes No |
What type of remote devices will be supported? |
| Yes No No No No | Yes No No No No |
What operating systems will be supported? |
| Yes Yes Yes No No | Yes Yes Yes Yes Yes |
Will you support dial-in modem services? |
| Yes
| Yes
|
Rank these technology priorities. |
| #1 #2 #3 | #2 #3 #1 |
When users connect to modems, what access service will they use? |
| Yes Yes No | Yes Yes No |
Will you support multilink? If yes, will you scale to a stacked multi-chassis solution? |
| No | Yes. A stacked solution. |
Will you support PPP timeouts (accounting)? |
| No | No |
For the short term, where are the users' passwords stored? | |||
In the long term, will you use a AAA server? If yes, what protocol will you use? |
| Yes TACACS+ | Yes RADIUS |
Will users be allowed to change their own passwords? If yes, how? |
| Yes EXEC shell | Yes CiscoSecure web page |
Will the access network use an external authentication database such as SecureID, Windows NT, or Novell NDS? |
| Yes | No |
Will you support per-user attribute definitions (authorization)? |
| Yes | No |
Do you have an existing accounting system to monitor call-detail records? |
| No | Yes |
Are you running an existing network management system? |
| No | No |
| 1Three months = current deployment requirement. One year = current design plan requirement. Five years = future scalability plan requirement. |
Based on the design choices in Table 1-1, each company creates its own network-to-user service definition. Table 1-2 provides the definition for each company.
| Maui Onions' Requirements | THEnet's Requirements |
|---|---|
Line requirements1 for the next 5 years:
| Line requirements for the next 5 years:
|
Analog lines and modems. | Analog lines and modems. |
Supported operating systems: Windows 95, 98, and NT. Maui Onions controls the client types used by its employees. | Supported operating systems: Windows 95, 98, NT, UNIX, and MacOS. THEnet offers Internet access to all client types. |
AAA is the highest technology priority. | V.90 modem performance is the highest technology priority. |
Dial-in only support. | Dial-in only support. |
EXEC shell and PPP session support. | EXEC shell and PPP session support. |
No multilink PPP support. | Multilink PPP support in a stacked solution for deployment in a future phase of this project. |
PPP timeouts will not be supported. | PPP timeouts will not be supported. |
Remote AAA TACACS+ server to store users' passwords. Users can change their passwords by using the EXEC shell. | |
Per-user attribute definitions (authorization) are supported. | Per-user attribute definitions are not supported. |
A network element management server is needed. | A network element management server is needed. |
| 1The line requirement is calculated by dividing the number of users by the user-to-line ratio during busy hours. |
The network service definition for each company is different:
Figure 1-3 shows the devices that are used to build both dial-up access environments. One recommended topology is used for both companies.
Both companies have similar network topologies. The hardware elements and software releases are described in the following tables.
| Element | Purpose | Maui Onions | THEnet |
|---|---|---|---|
Remote clients and analog modems | To access the IP backbone through the PSTN. | PCs | PCs, Macs, UNIX workstations |
Cisco AS5x00 NAS | To terminate modem calls and Point-to-Point Protocol (PPP) sessions. | Cisco AS5300 | Cisco AS5800 |
PRI lines | To provide high throughput (64K) for digital and analog calls. In general, T1 and T3 trunks can be ISDN PRIs or channelized T1s. | T1 trunks | T3 trunks |
Network element management server | To maintain and monitor the NAS. | NTP, syslog, SNMP | |
Remote AAA server | To perform basic user authentication. | TACACS+ | RADIUS |
Default gateway | To forward packets to the IP intranet and Internet. | Router | Router |
Internet firewall | To protect the IP intranet from intruders and hackers. | Cisco PIX | Cisco PIX |
Edge router | To provide connectivity between the access subnet and the IP backbone. | Router | Router |
| 1Network Time Protocol 2System logs (logging) 3Simple Network Management Protocol |
To obtain the latest Cisco IOS features and bug fixes, the access servers are upgraded to the following software releases:
| Hardware | Start with | Upgrade to |
|---|---|---|
Cisco AS5300 | Cisco IOS Release 11.3(7)AA MICA portware 2.6.2.0 | Cisco IOS Release 12.0(5)T MICA portware 2.7.1.0 |
Cisco AS5800 | Cisco IOS Release 11.3(9)AA2 MICA portware 2.6.2.0 | Cisco IOS Release 12.0(4)XL1 MICA portware 2.6.2.0 (same) |
Use a mature Cisco IOS release whenever possible. For example, a mature release is 12.0(10)T not 12.0(1)T. Maintenance release 10 is more mature than maintenance release 1. During the development of this document, the most mature releases available are 12.0(5)T and 12.0(4)XL1.
Before the equipment is deployed at the customer sites, both companies define the following configuration design parameters:
![]() |
Note This case study uses private RFC 1918 IP addresses. For more information, refer to the following URL: http://www.ietf.org/rfc/rfc1918.txt |
For Maui Onions and THEnet, Table 1-5 through Table 1-7 describe the following:
| Network Name | Assigned Subnet | Description |
|---|---|---|
Headquarters Block | 172.22.0.0/171 | The block of IP addresses reserved for the devices inside the corporate network. |
Remote block | 172.22.128.0/17 | The block of IP addresses reserved for the incoming remote-node modem clients. |
Hq-access | 172.22.66.0/26 | The headquarter's access Ethernet subnet. All the access devices are directly connected to this subnet. If additional access servers and POP-management devices are needed, they are assigned to this IP subnet. This approach simplifies network design. |
NAS loopback 0 | 172.22.99.0/24 | Identifies the router with a unique and stable IP address for network management purposes. One IP address from a common address block is assigned to each network device. This technique enables the network operations center (NOC) to more easily perform security filtering. One class C subnet that used to identify devices can support 254 distinct nodes with unique loopback IP addresses. |
NAS loopback 1 | 172.22.90.0/24 | Used to host a pool of IP addresses for the remote nodes. In this way, one route is summarized and propagated to the backbone instead of 254 host routes. Setting up interior gateway protocols (IGP) is outside the scope of this document. For example, OSPF and EIGRP. |
| 1The /17 means there are 17 bits in the subnet mask. For /26, there are 26 bits in the subnet mask and so on. |
![]() |
Note A simple IP address strategy is used for this case study. Scaling IP addresses is outside the scope of this document. |
| Device | Parameters |
|---|---|
5300-NAS | |
Interface ethernet 0 | 172.22.66.23 255.255.255.0 |
Interface loopback 0 | 172.22.99.1 255.255.255.255 |
Interface loopback 1 | 172.22.90.1 255.255.255.0 |
IP local address pool | 5300-NAS = 172.22.90.2 through 172.22.90.97 5800-NAS = 172.22.90.2 through 172.22.90.254 |
Primary and secondary name servers | 172.22.11.10 |
Default gateway | 172.22.66.1 |
mauionions.com | |
Network element management server (NTP, SNMP, syslog) | |
Read only (RO) = poptarts Read write (RW) = pixysticks |
| Item | Value | Description |
|---|---|---|
4085551234 | Telephone numbers assigned to the T1 trunks. These numbers are used for:
| |
5ESS | The telco's switch type that connects to the T1 PRI trunks. In this case study, the T1 trunks are not using channel associated signaling (CAS). | |
Framing type |
| Defines the control bits and data bits. |
Line code type |
| An encoding method used to allow synchronous data to be transmitted in a compatible format. |
Test call login | username = dude | Username password for sending test calls into the NAS. |
Table 1-8 describes the deployment and operation task strategy used in this case study. Maui Onions and THEnet use a common strategy.
| Section | Task | Description |
|---|---|---|
| ||
| ||
| ||
| ||
| ||
Enabling the following management protocols as part of commissioning a dial access service:
| ||
Inspecting the Final Running Configuration for the Cisco AS5300 and AS5800 | Referencing and editing full-function Cisco IOS NAS configurations. |
![]()
![]()
![]()
![]()
![]()
![]()
![]()
Posted: Mon May 22 13:02:31 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.