CiscoWorks Service Level Manager

Netsys Topology

Document ID: 15177

Updated: Oct 13, 2005


Related Information
Related Cisco Support Community Discussions

Q: What should I do if mouse functions aren't working in the Topology?

A: This can happen when the keyboard Num Lock key or Scroll Lock key is engaged. Disable the lock, then try the mouse functions again.

Q: What are the differences between the map views? What do the colored squares in the "Campus" View represent?

A: The "Campus" Topology view is intended to represent a logical network layout. Each campus consists of routers interconnected only by (Token Ring, FDDI, Ethernet) networks. Campus boundaries are determined by Serial Links, and shown as colored regions on the map. Each campus is labeled based on the most common first three characters of router hostnames in that campus. The "By-Name" view is a campus view in which routers whose names start with the same first two letters are grouped in the same campus.

The "Flat" view, rather than combining devices into campuses, displays them evenly distributed throughout the map. This dispersion makes the Flat view useful for looking at small-to-medium sized networks (up to 75 routers), as well as for displaying Round Trip paths. For very large networks (over 200 routers), the Flat view will take some time to produce when first selected, although subsequent switching between views will be much faster. See the How large a network can NSM model? Does performance change with network size? question for more information.

The "RSRB" view is a logical representation of ring groups, virtual ring groups, and associated routers within a SNA or Token Ring network.

The "OSPF" and "OSPF-Areas" views are logical displays of routers and networks making up the "OSPF" network, where devices are grouped by OSPF area and process ID, or by OSPF area only, respectively.

Q: In the AppleTalk View, why do some campus names begin with "z_" and others begin with "zb_"?

A: If a router has all of its interfaces in the same primary zone, it will appear in a "z_" campus. If a router has interfaces assigned to different primary zones, it will be assigned to a "zb_" (zone border) campus.

Q: How does Netsys Service Manager (NSM) determine the router type?

A: It is difficult to determine router type simply by looking at the configuration file. In NSM 3.x, if the tool sees a "/" in an interface, it assumes the router is a Cisco 7000. The data.router_types file in the baseline can be edited to specify specific router types (look at the example in the perf.tutorial baseline). NSM will pick up the router type from data.router_types before generating the integrity check report. Additionally, the router types can be set in a new scenario by selecting Display Parameters -> Router Parameters -> Global Mib Info. Save the changes with the Save Performance Data option.

I NSM version 4.1, the "Run Service Management Collection & Web Reports" wizard allows you to collect Cisco router types.

Q: How does NSM model line speed?

A: The software uses the bandwidth statement from the router configuration. If that is not present, it uses the default bandwidth for the interface.

Q: I know I have parallel WAN links between two routers, but why can I only see one?

A: Parallel WAN links are drawn as one in the topology to reduce congestion. You can identify parallel WAN links by selecting the Parallel WAN Links option in the "Find Device" window.

Q: Can I view primary links only in the topology?

A: There is a "Secondary LANs" toggle switch under the Show menu in the topology window. Use this feature to omit/include secondary links.

Q: What does the thickness of serial links (as drawn in the Topology) represent?

A: The different link widths in the Topology show the corresponding bandwidth of that serial line. There are five possible widths, one for each of the following bandwidth ranges:

  • 1-200

  • 200-500

  • 500-1000

  • 1000-2000

  • 2000+

The wider the line, the higher the bandwidth. If two different bandwidths are indicated in the routing configuration files, the lower one is used.

Q: Why would an interface with assigned IP address be left unconnected?

A: If an interface is assigned an IP address that is identical to the subnet address, the interface is left unconnected (that is, a link between the interface and the subnet to which it is connected is not created.)

Another possible cause is that the other router's configuration may be missing in the baseline.

Q: Are all bridging routers modeled?

A: No, not all bridging routers are modeled. NSM models SRB, RSRB, and DLSw+ bridging routers, which may result in unnecessary integrity checks during the integrity check report as well as a cluttered or inaccurate topology.

Q: When I print a Topology, I get an "Output to device successful" error message but nothing comes out on the printer.

A: When printing a topology, the print process outputs an "Output to device successful" message even if an error external to the application has occurred. Some things to check are:

  1. The topology is printed as a PostScript file, so printing requires a PostScript printer.

  2. In the Print window, make sure that the device input field has the complete and correct lp command (such as lp -Pprinter1). The correct lp command is the same one you would use at the command line to print a file.

Q: How can I print the topology if I don't have access to a PostScript printer?

A: You can save the topology to a file, FTP the file to a PC, and use the MS-DOS print command to print the file.

Related Information


Updated: Oct 13, 2005
Document ID: 15177