Advertisement
In this case study, THEnet initially sends syslog data across WAN links to the NOC. The WAN links are
designed to support a large network capacity in a metropolitan area. Collecting syslog locally in each
POP is a future design consideration.
To design the dial NMS for the two POPs and the NOC, the network engineers at THEnet defined these
hardware requirements:
4 Cisco AS5800
Two access servers in each POP to provide access in to the Internet from the
access servers
PSTN. Cisco IOS Release 12.0(7)T is installed in each access server.
2 backbone
Enables management data streams to enter the NOC.
gateways
Routes traffic to the intranet WAN and the Internet.
2 Cisco 2511 OOB
Accesses the console ports in the Cisco AS5800s by using out-of-band (OOB)
console servers
management lines.
3 AAA servers
One server in each POP to authenticate, authorize, and account for dial access
clients by using RADIUS.
One server in the NOC to authenticate, authorize, and account for router
administrators by using TACACS+.
1 Cisco PIX firewall Protects the NOC by filtering the devices that can access management services,
such as TACACS+, RADIUS, syslog, and SNMP.
3 Sun Ultra 10
Operates the dial NMS inside the NOC. Solaris version 2.6 is used.
workstations
The following capacity-planning calculations were made to determine the number of required lines and
Cisco AS5800s for the next five years.
Basic parameters:
There are 23 available bearer channels per PRI line
There are 28 PRI lines per T3 card (644 channels)
Each Cisco AS5800 has two T3 cards
There are 1288 available bearer channels per dual T3 Cisco AS5800
10:1
50,000
10:1
100,000
10:1
1,000,000
5000
5000 lines / 1288 = 3.88 chassis
10,000
10,000 lines / 1288 = 7.76 chassis
100,000
100,000 lines / 1288 = 77.64 chassis
4 AS5800s
8 AS5800s
78 AS5800s
Advertisement
