- Cisco WAN Modeling Tools User Guide
Table Of Contents
- Cisco WAN Modeling Tools User Guide
- Contents
- Related CWM and Switch Documentation
- Obtaining Documentation
- Documentation Feedback
- Cisco Product Security Overview
- Obtaining Technical Assistance
- Obtaining Additional Publications and Information
- Cisco WAN Modeling Tools Overview
- Functionality of the NMT
- Cisco Products Supported by the NMT
- Basic Usage/Charter Functionality
- Gaps
- Data Translation Tools
- System Requirements
- Installing the NMT
- Upgrading the NMT Software
- Starting the NMT
- Removing NMT
- Installing a Cisco WAN Modeling Tools Sub-application
- Removing Sub-applications
- Troubleshooting NMT Installation
- NMT Startup
- NMT Menu Bar
- File Menu
- Display Menu
- Keyboard Commands
- Modeling Processes
- Error Checking
- Troubleshooting NMT
- General Table Information
- Sites Table
- Links Table
- Link Special Cases
- Voice Table
- Data Table
- Bursty Table
- Interface Table
- Feeder Table
- Card Table
- Groups and Network Table
- Nodes Table
- Network Settings
- Model Options
- Feeders
- Obsolete Products
- FastPAD
- Port Concentrator
- Tiered Networks
- Using the Route Command
- AutoRoute
- AutoRoute Least Cost Routing
- PNNI Routing
- Fail Analysis Command
- Build Sites Command
- Optimize Command
- NMT Command Results
- Site Report
- Link Report
- Network Summary Report
- Link Load Report
- ATM & FR Ports Report (or Bursty Data Ports Report)
- Data & Voice Ports Report (or Voice & Data Ports Report)
- Connection Routes Report
- Failed Connections Report
- Parts List Report
- Resource Report/Card Statistics Report
- PNNI Topology Report
- View Summary
- Using the Map Tool
- NMT Map Startup
- Navigating Though a Network View
- Obtaining Link Information - Physical Links
- Obtaining Link Information - Logical Links
- Zooming the Map
- Panning the Map
- Map Color Coding
- Controlling Map Displays in NMT
- NMT Map Main Menu
- Adding New Groups
- Adding Nodes to Existing Groups
- Deleting Groups
- Deleting Nodes or Groups from Existing Groups
- Saving Your Work
- Retrieving Map Data Into NMT
- Using the Map Tool with Fail Analysis
- Using the Map Tool to Analyze Traffic Levels
- Fields Addressed by CET
- Using the CET
- Other CET Commands
- Troubleshooting CET
- Remote CET Extracts
- Translating Between NMT and WANDL Formats
- NMT to Microsoft Excel
- Microsoft Excel to NMT
- Usage Review
- SSI TroubleShooting
- CND PC Import Utilities
- Index

4-34
Cisco WAN Modeling Tools Guide
OL-10426-01, Rev. A0
Chapter 4 Configuration Tables and Fields
Feeders
Modeling Explicit Feeders
To allow the NMT to model explicit feeders, enter the following information about the feeder site into
the Site table:
• link connecting the hub and feeder in the Link table
• connection interfaces in the Traffic tables (as if the node were not a feeder).
For explicit feeders, connection endpoints are the feeder nodes.
IGX and IPX nodes can be modeled as either hub or feeder nodes. The MGX 8820 can only be modeled
as a feeder. Beginning with NMT 9.2, the MGX 8820 can be an explicit feeder as well as an implicit
feeder.
The MGX 8850 is also modeled in NMT 9.2. As a feeder node, the MGX connects to the BPX. If
modeled as a feeder, The MGX 8850 node must be explicit.
MGX 8220 Feeders:
Port to Multiport
Bursty Traffic table
Fdr I/D fields (Feeder identification fields): ID values
must be assigned.
ID values can be
• Slot.Port for AUSM and CESM cards (e.g., 5.3); this
format can be used also for FRSM cards to specify
physical port (line) without specifying logical port.
• Slot.Line.Port for FRSM card (e.g., 5.2.6).
• Zero, indicating no unique port constraint.
By assigning IDs to the ports of the MGX 8220 service
module cards, you can put the connection on a particular
port.
Feeder IDs can also control port-to-multiport connections.
MGX 8220 Feeders:
Multiple Feeders at a
Site
Bursty Traffic table
Hub ID field
• All connections associated with a specific MGX
8220 should have the same hub ID throughout the
Bursty Traffic table.
• It is not necessary to use the HUB ID field for the
site at the other end of the connection.
• Hub ID values can be
— Slot.Port (e.g., 12.2)
— Zero, indicating no unique port constraint
You need to configure a site with multiple MGX 8220 feeders
only if you require connections between the feeders or if you
need to associate specific connections with specific feeders
(e.g., if the feeders are at different locations).
Assign hub IDs to identify the port of the BNI/BXM card on
the BPX switch that connects to the specific MGX 8220 edge
concentrator.
Table 4-19 Tiered Network Configurations with Implicit Feeders (continued)
Topic Required Settings Comments