Table of Contents
Example Network
This chapter describes the example network used in this publication to illustrate hardware configuration problems and configuration troubleshooting. The example network also describes the most common connections you need to troubleshoot and enables you to apply your own enterprise network configuration to the examples.
In a well-formed hierarchical network, there are three easily defined layers, traditionally referred to as the access, distribution, and core layers.
Each of these layers provides a different function. The layers do not need to exist in clear and distinct physical entities, but the functionality needs to exist in an enterprise network. To help understand these functional layers, the traditional layers have been modified to access or workgroup, distribution or policy, and core or backbone.
The main function of the access or workgroup layer is to connect users. Other functions represented by this layer are shared bandwidth, switched bandwidth, MAC-layer filtering, and micro segmentation. LAN switches, for example the Catalyst 5000 and Catalyst 5500 switches, exist most commonly in this layer of the network.
The distribution or policy layer performs the policy-based operations. It performs the complex, CPU-intensive calculations such as filtering, access lists, inter-VLAN routing, Group Multicast Protocol (GMP), broadcast and multicast domain definition, and address or area aggregation. This layer may also contain the local servers. ATM switches and routers reside in the distribution layer, and sometimes LAN switches may reside here as well.
The core or backbone layer is the backbone of the network. It should be high-speed and concerned mainly with switching traffic as quickly as possible. It should not get involved in "expensive" packet manipulation. ATM connections or Fast Ethernet connections, which functions as a backup, should make up the core backbone. The central servers may also be attached to the high-speed backbone in the core. ATM switches, high-speed routers, and sometimes LAN switches can be found in the core.
This section describes a fictitious network that was created to provide a narrative to describe actual problems in troubleshooting ATM switched networks.
Figure 3-1 provides a high-level overview of the campus and remote networks.
Figure 3-1: Example Network Overview

The example network in Figure 3-1 has the following components:
- A campus network of four 10-story buildings
- 1 remote sales building
- 1 telecommuter
- 4,000 employees on campus
- 4 buildings with 1,000 employees per building
- 5,000 total ports
- Microsoft NT servers and IP as the primary protocol
- Dynamic Host Configuration Protocol (DHCP) used to automatically allocate IP addresses to clients
- Approximately 100 users per wiring closet, which require approximately 50 Catalyst 5000 or Catalyst 5500 switches
- One intermediate equipment closet per building connecting buildings with the ATM distribution switches
- Fiber optic connections between wiring closets and intermediate equipment closets
- 1/2 of the users on VLAN 2, 1/2 on VLAN 3
- Network 10.0.0.0 255.255.255.0
- 254 hosts per subnet
- Spanning tree and root bridges enabled
- No single point of failure
- Workgroup servers that are connected using Layer 2 either ATM or Fast Ethernet
- Enterprise servers (e-mail, Web, and meeting scheduling) located in the administration building with the edge routers and firewall protection
- ATM switches, which provide the following:
- 155 unshielded twisted-pair (UTP) Optical Carrier 3 (OC-3) connections to servers and high-bandwidth users (computer-aided design [CAD], video, and voice) to the backbone
- 622 single-mode fiber (OC-12) connections to the core between buildings in the intermediate wiring closets creating the backbone
- T3 coaxial connections to the WAN
- Catalyst 5000 and Catalyst 5500 switches, which provide the following:
- Access and workgroup connection to individual users of the network
- Workgroup server connections
- Spanning-tree loop protection and providing network redundancy
- The remote site switch has the following:
- 500 employees
- 750 total ports
- The telecommuter switch has the following:
- Dialup connections
- ISDN
- Frame Relay
The example network contains the following physical connections:
- 155 UTP---Using permanent virtual path (PVP) and LAN emulation (LANE), connect distribution ATM switches and Catalyst 5000 or Catalyst 5500
- 622 multimode fiber and single-mode fiber---Using PVP, connect core ATM switches with tag switching enabled
- T1or E1---Using PVP, connect to WAN (AT&T, MCI, and so on) at a lower bandwidth (BW) remote site for WWW, FTP, Telnet, e-mail, and so on
- T3 or E3---Using PVP, connect to WAN at a higher BW campus for WWW, FTP, Telnet, e-mail, and so on
- T1 circuit emulation switch---Using PVP, connect to private branch exchange (PBX) or using switched virtual circuit (SVC), connect to coder-decoder (CODEC) for constant bit rate (CBR) video
- 25 Mbps---Using soft permanent virtual circuit (PVC), connect to computer-aided design/computer-aided manufacturing (CAD/CAM) users providing QoS using the following:
- 10 Mbps: video
- 5 Mbps: audio
- 5 Mbps: Unspecified bit rate (UBR) for data
- Frame Relay---Using PVC, connect to a telecommuter
- ATM inverse multiplexing---Using PVP, connect to the remote site where DS3 is too much bandwidth and T1 is too little
The example network contains the following virtual connections:
- PVPs---Connections between buildings
- PVP tunnels---Connect to the remote site through the public network to avoid signalling
- SVCs---Connect to nodes that require longer data exchanges but infrequent connections (for example, e-mail server, CAD/CAM connections)
- PVC---Connect to nodes that need quick, short access without signalling delay (for example, Domain Name System [DNS] server connections)
- Soft PVC---Connect to the UNIX network interface cards (NICs) that do not support signaling (for example, SGI workstations)
- LAN Emulation (LANE), which has the following connection types:
- LAN Emulation Client (LEC)---Typical application from Catalyst 5000 and 5500 to ATM switch
- LAN Emulation Configuration Server/broadcast and unknown server (LECS/BUS)---Configure on low usage ATM switch because the application is very CPU intensive
- Tag switching---Connect all core switches
The equipment overview of the example network, shown in Figure 3-2, shows the various equipment and the connection types of the network. Each is described in greater detail in subsequent illustrations.
Figure 3-2: Equipment Overview of the Example Network

The engineering building in Figure 3-3, shows the following connections:
- 622 single-mode fiber connections between the ATM core switch on Floor 1 to the campus backbone
- T1 circuit emulation service (CES) access connection to CBR and QoS CODEC for the videoconference room
- 155 UTP SVC connections from the access ATM switch to the enterprise servers
- 155 UTP, multimode fiber, or single-mode fiber LANE SVCs connect distribution ATM switches in each wiring closet to Fast Ethernet access switches
Note Each Fast Ethernet distribution switch connection has a redundant link (see Figure 3-4).
Figure 3-3: Engineering Building Connections

The typical Floor 1 wiring closet of the example network, shown in Figure 3-4, shows the following connection examples:
- 622 single-mode fiber ATM core switch connections to the backbone
- 155 multimode fiber connections through LANE connecting the access switches with the ATM modules
- 25-Mbps port adapter providing 12 PVC access connections to CAD/CAM users with SGI workstations whose NICs do not support signaling
- T1 CES connection access connections to CBR and QoS video CODEC
- 155 UTP connection through LANE SVC to Fast Ethernet access switches
Figure 3-4: Typical Floor 1 Wiring Closet

The typical core switch configuration of the example network, shown in Figure 3-5, illustrates the following connections:
- 622 single-mode fiber core connection through PVC for Private Network-Network Interface (PNNI) redundancy
- 155 single-mode fiber distribution connection through PVC to ATM distribution switches within the building
Figure 3-5: Typical Core Switch Configuration

The typical distribution switch configuration of the example network, shown in Figure 3-6, shows the following connection examples:
- 155 UTP distribution connection through PVC PNNI connections between core ATM switches
- 155 UTP distribution connection through LANE SVCs to Catalyst 5000 running LECS/BUS
- 155 UTP access connection through ELAN SVCs to individual servers
- 155 UTP or multimode fiber access connection through SVC providing a CBR connection to CODEC for videoconferencing
Figure 3-6: Typical Distribution Switch Configuration to Floor 1

The administration building configuration of the example network in Figure 3-7 provides the following connections:
- 155 UTP connections using LANE SVC connections to e-mail servers, for example, that allow "bursty" traffic requiring signaling and less frequent use
- 155 UTP connections using PVC connections to DNS servers, for example, that allow short duration connections without signaling but almost constant use
- T3 connection to WAN with access filtering to Hypertext Transfer Protocol (HTTP) and other users
- 155 UTP connection to edge router or default gateway with ATM Interface Processor (AIP) installed and tag switching enabled
- T1 CES connection to PBX
- Video CBR using LANE SVC connections and T1 CES port adapter providing multicast connections to selected users
- Soft PVC from source video connection to a destination at a remote site
- PVP tunnel to the remote sales building
- Frame Relay PVC to the telecommuter
Figure 3-7: Administration Building Connections

Copyright 1989-1999©Cisco Systems Inc.