User`s guide

Mapping with Non-Manageable Devices
Editing GenFDDIMac Information
The RingView Modeling Process RingView for FDDI
2-4 User’s Guide
After saving your edits to the GenFDDIMac Information View, you can run
RingView again by bringing up the Information View for the FDDI LAN and
opening the RingView Tools dialog box (see Chapter 3 for illustration and
detailed instructions). The additional information provided by your edits will
allow RingView to re-map the ring and generate a more comprehensive
topology.
Figure 2-2 shows how this process would work for a partially modeled ring of
non-Cabletron devices in which each of the manageable devices supports the
1285 FDDI MIB and can thus provide RingView with the MAC address of its
upstream neighbor. As the top diagram in this example shows, the ring
consists of six nodes, two of which (Nodes 2 and 3) have
not been modeled in
SPECTRUM. The first time RingView attempts to map this ring, it obtains
the MAC address of Node 2 from Node 1 and creates a GenFDDIMac_NM
model, which is displayed as a dual-attached station (DAS). At this point,
there is no way for RingView to know about the existence of Node 3;
consequently the second diagram shows only five nodes.
The third diagram, however, shows the complete ring as it would be mapped
after the Information View for the GenFDDIMac_NM model representing
Node 2 has been edited to provide port information for Node 2 as well as the
MAC address of its upstream neighbor, Node 3. Since the edit has specified
that Node 2 has four master ports and two non-master ports, RingView can
now identify the node as a dual-attached concentrator (DAC). Once again,
since RingView knows nothing about Node 3 except its MAC address, it
creates a GenFDDIMac_NM model and assumes the node is a dual-attached
station.
In the final diagram, another edit has provided the correct port and
attachment information for Node 3, and a subsequent RingView session
displays the node as a single-attached station (SAS) and positions it off the
dual ring as an end node rather than rooted node.
Note that edits of this extent are only necessary if you require a mapping of
the physical connectivity as shown in the bottom diagram. RingView can
correctly map the token order (as in the third diagram) as soon as all MAC
addresses are determined.