Transcend Enterprise Manager for Windows.
User Guide Volume 2

About This Guide 
 
Introduction 
This guide describes how to manage different network devices using Transcend Enterprise Manager for Windows®. See Volume 1 of this guide for information about installing and the general use of Transcend Enterprise Manager. 
NOTE: If the information in the release notes shipped with your product differs from the information in this guide, follow the release notes. 
How to Use This Guide 
The following table shows where to find specific information. 
 
If you are looking for:	 Turn to:	 
Information on managing devices	 Chapter 1 	 
Information on managing special device features 	 Chapter 2	 
Information on managing ports	 Chapter 3	 
Information on gathering statistics	 Chapter 4	 
Information on managing NETBuilder	 Chapter 5	 
Information on monitoring NETBuilder	 Chapter 6	 

  
Conventions 
The following tables list conventions that are used in this guide. 
 
Convention	 Description	 
"Enter" vs. "Type"	 When the word "enter" is used in this guide, it means type something, then press the Return or Enter key. Do not press the Return or Enter key when an instruction simply says "type."	 
Text represented as screen display 	 This typeface is used to represent displays that appear on your terminal screen, for example:

NetLogin:	 
Text represented as commands	 This typeface is used to represent commands that you enter, for example:

SETDefault !0 -IP NETaddr = 0.0.0.0	 
Keys	 When specific keys are referred to in the text, they are called out by their labels, such as "the Return key" or "the Escape key," or they may be shown as or  

If two or more keys are to be pressed simultaneously, the keys are linked with a plus sign (+), for example:

Press 	 
Italics	 Italics are used to denote new terms or emphasis.	 

  
 
Icon	 Type	 Description	 
	 Information Note	 Information notes call attention to important features or instructions.	 
	 Caution	 Cautions contain directions that you must follow to avoid immediate system damage or loss of data.	 
	 Warning	 Warnings contain directions that you must follow for your personal safety. Follow all instructions carefully. 	 

  
Related Publications 
The list below shows other guides and publications you may want to refer to while using Enterprise Manager: 
·For information about the general operation of Enterprise Manager, see Volume 1 of this guide. 
·For information about installing and using the devices that can be managed by Enterprise Manager, see the relevant device section of this guide. The individual manuals you may want to refer to are listed in each part of this guide. Alternatively you can look at the on-line documentation provided on the CD-ROM. 
·For information about managing PC adapters, see the Transcend WorkGroup PC Links User Guide. 
·For information about using RMON tools, see the Transcend LANsentry Manager for Windows User Guide. 
·For information about installing and using the on-line documentation, see 3Com On-Line Documentation . 
 
 1 Managing Devices 
This chapter contains the following topics 
·What Can You Manage? 
·Viewing the Device Status 
·Setting Up Management for a Device 
·Grouping Devices into a SuperStack II View 
·Setting Up a Virtual LAN 
·Resetting and Initializing a Device 
·Upgrading the Management Agent Software 
·Displaying Detailed Information About a Device 
·Setting Up a Resilient Link Pair 
·Using a Device to Monitor Your Network 
·Configuring Ethernet Switching Options 
·Viewing FDDI Ring Parameters 
·Working with Alarms 
·Setting Up Security 
What Can You Manage? 
The following matrix shows the management features supported for each device. 
 
Management Features	 SuperStack II	 	 	 
	 Hub 10	 Hub 100	 Hub TR	 Switch 1000	  Switch 2200	 Switch 3000	 LinkSwitch 500	 LinkSwitch 1200	 
View the device status	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 
Set up management for the device	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 
Group devices into a SuperStack	 Ö	 Ö	 	 Ö	 Ö	 Ö	 	 	 
Set up a Virtual LAN	 	 	 	 Ö	 	 Ö	 	 	 
Reset and initialize	 Ö	 Ö	 Ö	 Ö	 	 Ö	 	 	 
Upgrade the management agent software	 Ö	 Ö	 Ö	 Ö	 	 Ö	 	 Ö	 
Display detailed information about a device	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 
Set up a resilient link pair	 Ö	 	 	 Ö	 	 Ö	 	 	 
Use the device to monitor your network	 Ö	 Ö	 	 Ö	 	 Ö	 	 	 
Configure Ethernet switching options	 	 	 	 Ö	 	 Ö	 	 Ö	 
 
View FDDI ring parameters	 	 	 	 	 	 	 	 Ö	 
Set up alarms	 Ö	 Ö	 	 Ö	 	 Ö	 	 	 
Set up security	 Ö	 	 	 Ö	 	 	 	 	 

  
Hub 10 includes: 
SuperStack II Hub 10, LinkBuilder 10BTi, LinkBuilder TP/8i, LinkBuilder FMS, LinkBuilder FMS II, LinkBuilder FMS II Bridge Management Module 
Hub TR includes: 
SuperStack Hub TR, LinkBuilder FMS TR 12/24, LinkBuilder TR Series, LinkBuilder Focus, LinkBuilder FMS TR Management Module 
Switch 1000 includes: 
SuperStack II Switch 1000, and LinkSwitch 1000 
Switch 2200 includes: 
SuperStack II Switch 2200, LinkSwitch 2200 
Switch 3000 includes: 
SuperStack II Switch 3000 FX, SuperStack II Switch 3000 TX, LinkSwitch 3000, LinkSwitch 3000TP 
NOTE: If you are managing a device using a dialog box that does not display all the fields described in this manual, it is because that particular feature is not supported for the device.

Office-
Connect
Hub/8TPM	 LinkBuilder	 LANplex 2016	 LANplex 2500	 LANplex 6000	 Management Features	 
	 FDDI WorkGroup Hub	 ECS	  MSH	 	 	 	 	 
Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 View the device status	 
Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Set up management for the device	 
	 	 	 	 	 	 	 Group devices into a SuperStack	 
	 	 	 	 	 	 	 Set up a Virtual LAN	 
Ö	 	 Ö	 Ö	 	 	 	 Reset and initialize	 
Ö	 	 Ö	 Ö	 	 	 	 Upgrade the management agent software	 
Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Display detailed information about a device	 
Ö	 	 Ö	 Ö	 	 	 	 Set up a resilient link pair	 
Ö	 	 	 	 	 	 	 Use the device to monitor your network	 
	 	 	 	 	 	 	 Configure Ethernet switching options	 
	 Ö	 	 Ö	 	 	 	 View FDDI ring parameters	 
 
Ö	 	 	 Ö	 	 	 	 Set up alarms	 
Ö	 	 Ö	 Ö	 	 	 	 Set up security	 

  
NOTE: The names of some of the 3Com device icons have changed. A summary of the old and new names is given in Table 1-2. 
Viewing the Device Status 
Color-coded device icons enable you to quickly check the status of a device on your system. Table 1-1 shows the device icon color-codes. 
 
Table 1-1   Icon Colors	 
Color	 Meaning	 
Green	 The device is operating normally.	 
Yellow	 The device has unacknowledged messages for minor events. Examples of minor events are: access by management, link state recovered, and port unpartitioned.	 
Orange	 The device has unacknowledged messages for major events. Examples of major events are: security violation, port jabber, local configuration change, loss of link, and port partition.	 
Red	 The device has stopped communicating.	 
Blue	 The device is not configured within Enterprise Manager. To configure a hub, see Setting Up Management for a Device	 

  
If a device has more than one unacknowledged event, the color of the icon represents the most severe event. 
Some of the 3Com icons for your devices have changed their name. The table below will help you to find the new names for your old device icons. If your device is not listed below then the icon name has not changed. 
Table 1-2 3Com Device Icon Name Changes 
 
New Name	 Old Name	 Devices Affected	 
Hub 10 	 FMS 	 SuperStack II Hub 10, LinkBuilder 10BTi, LinkBuilder TP/8i, LinkBuilder FMS, LinkBuilder FMS II, LinkBuilder FMS II Bridge Management Module	 
Hub TR 	  FMS TR 	 SuperStack Hub TR, LinkBuilder FMS TR 12/24, LinkBuilder TR Series, LinkBuilder Focus, LinkBuilder FMS TR Management Module	 
Switch 1000	 LinkSwitch1000 	 SuperStack II Switch 1000, LinkSwitch 1000	 
Switch 2200	 LinkSwitch2200	  SuperStack II Switch 2200, LinkSwitch 2200	 
Switch 2700	 LinkSwitch2700	 SuperStack II Switch 2700, LinkSwitch 2700	 
Switch 3000	 LinkSwitch3000	 SuperStack II Switch 3000 FX, SuperStack II Switch 3000 TX, LinkSwitch 3000, LinkSwitch 3000TP	 
NETBuilder 	 NetBuilder  Remote Office 	 NETBuilder 2xx, 4xx series	 

  
Setting Up Management for a Device 
Before you can manage a device, you need to provide Enterprise Manager with information about it. Most of the information is provided by the Autodiscovery process or is set by default if you have made no changes to the device's configuration. If you added the device to your network map using the Nodes dialog box, you have to enter this information yourself. 
Enterprise Manager needs to be provided with the following: 
·Device name used in the subnetwork view 
·IP and/or IPX address of the device 
·Subnet mask and default gateway IP address 
·Request/response parameters 
·Whether or not heartbeat traps or poll node should be enabled 
·SNMP community strings used by the device 
If the device was found by Autodiscovery using IPX, you can configure the IP information for the device. Before configuring a device, it must be powered up with its agent running. 
Device Configuration 
To display the Configuration dialog box and view or set the configuration parameters: 
1On your network map, select the device you want to configure. 
2From the Configure menu, select Device/Subnetwork. 
3In the Configuration dialog box (shown in Figure 1-1), change or enter any of the configuration information as described in the remainder of this section. 

FIG 
Figure 1-1 Device Configuration Dialog Box 
Device Shows the following: 
·Name - Provides a box for you to type a name for the device. Use a descriptive name, such as Accounts. The name can be up to 15 characters long. 
Network Shows the following: 
·IP Addr - Shows the IP address of the device. If you change the IP address of a device, Enterprise Manager warns you that changing the IP address causes the device to restart. If you want to change the IP address so that the device is on a different subnetwork, you must delete it from the current subnetwork, add it to the new subnetwork and enter the new IP information. 
·Subnet - Shows the subnet mask for the device. 
·Gateway - Provides boxes for you to type the IP address of the router used by the device to communicate with other networks. 
·IPX Addr - Shows the IPX address of the device. 
Request/Response Shows the following: 
·Timeout - Sets the time limit in seconds for the device to respond to an SNMP request. 
·Number of Retries - Sets the number of retries following the timeout of an SNMP request. 
Increasing these values prevents inaccurate No Response messages as the device has more time to respond to the management station if the network is busy. 
Actions Shows the following: 
·Heartbeat Trap Enable - Selects whether to periodically send heartbeat traps to Enterprise Manager to indicate that the device is alive and can be communicated with. We recommend that this option is disabled and the Poll Node option used instead. 
·Setup Trap Table - Adds the IP/IPX address of Enterprise Manager PC to the device's trap table. The trap table contains the addresses of network managers to which traps are sent. Click on this button to receive traps from the device. 
Poll Node Selects whether the device is polled by Enterprise Manager. You must select Poll Node to enable Enterprise Manager to discover the status of the device. If you do not select Poll Node, Enterprise Manager cannot change the color of the device icon to indicate the status of the device. For example, if the device stops communicating the hub icon does not change color to red. 
We recommend that Poll Node is used in preference to Heartbeat Trap Enable. 
SNMP Community Strings 
Community strings are used by the device to validate requests from Enterprise Manager. If the community strings used by Enterprise Manager are different to those set up on the device, you cannot communicate with the device. 
To change the community strings used by Enterprise Manager to communicate with a device: 
1Select the device for which you want to change the community strings. 
2From the Configure menu, choose Device/Subnetwork. 
3In the Configuration dialog box, from the Authorize menu, choose Community Names. 
4In the Community Name dialog box, enter the new community string in the box. 
NOTE: This option does not change the community string on the device. You must change the community string on the device using local management to match that used by the Enterprise Manager to be able to communicate with it. For more information about setting up community strings on a device, refer to the appropriate device manual. 
Grouping Devices into a SuperStack II View 
The SuperStack system gives you a cost-effective connectivity solution for local, wide-area and SNA networks. With SuperStack, you can combine diverse technologies and network services in one stacked system and manage it from a single device view window. 
When you group devices into a SuperStack View, Enterprise Manager displays them as a single stack. You can choose which of the supported devices on a subnet to group together and in which position within the stack they appear. When you double-click on any of the SuperStack devices on your network map, Enterprise Manager displays that device and all others in the stack. 
You can manage devices that form a SuperStack View in exactly the same way as any other devices on your network, however you can now manage them all from within one device view window. For example, if you have a created a SuperStack View that comprises two Hub 10's and a Switch 1000, when you double-click on Switch 1000 icon on your network map, Enterprise Manager displays a window with all three devices in the SuperStack. Managing the devices is the same as if they were in individual windows, that is, Enterprise Manager displays the port configuration dialog boxes if you double-click on a port and the device configuration dialog boxes if you double-click on another part of the device. 
NOTE: When you double-click on a NETBuilder 22x or 42x device in a SuperStack, Enterprise Manager displays the NETBuilder device view window. For more information on managing NETBuilders, see Chapter 5. 
The example SuperStack View in Figure 1-2, shows a Hub 10, Switch 1000 and Switch 3000. 

FIG 
Figure 1-2 SuperStack View 
If you have not configured any SuperStack Views on a subnet, Enterprise Manager creates one view by default called Initial Stack. This contains all the SuperStack devices on a subnet. You can edit this default view to create views that match your particular network configuration. 
NOTE: If you have more than eight SuperStack devices on a subnet, Enterprise Manager creates the Initial Stack with the first eight SuperStack devices it finds during Autodiscovery. 
To edit a SuperStack View: 
1Select a SuperStack device on your network map. 
2From the View menu, select SuperStack Configure. 
3In the SuperStack Configure dialog box (shown in Figure 1-3), select a SuperStack then click Edit. 

FIG 
Figure 1-3 SuperStack Configure Dialog Box 
4In the SuperStack Edit/Create dialog Box (shown in Figure 1-4), select devices in the Available or Members lists and use the Add and Remove buttons to define the devices which form the view. 

FIG 
Figure 1-4 SuperStack Edit/Create Dialog Box 
In the SuperStack Edit/Create dialog box: 
SuperStack Name Provides space for you to enter a name for the SuperStack. The name can be up to 15 characters long. 
Launch Preference Determines which view Enterprise Manager displays when you double-click on a SuperStack device on the network map: 
·SuperStack View - Displays the device and all the other devices configured to be part of the SuperStack. 
·Device View - Displays only the selected device. 
·View Chooser - Displays a dialog box that enables you to choose either the SuperStack view or device view each time you double-click on the device. 
Available Lists the devices on the subnet that are not part of any SuperStack. A device can only be a member of one SuperStack at a time. 
Members Lists the devices on the subnet that form part of the current SuperStack. You can create a SuperStack with up to eight devices. 
Add Moves any selected devices in the Available list to the Members list. 
Remove Moves any selected devices in the Members list to the Available lists. 
Move Moves the selected device in the Members list up or down. You can use the Move buttons to alter the position in which a device is displayed in the SuperStack view. 
Setting Up a Virtual LAN 
Setting up Virtual Local Area Networks (VLANs) provides you with more efficient network operation and less time-consuming network administration. 
A VLAN is defined as a group of location- and topology- independent devices that communicate as if they are on the same physical LAN. This means that LAN segments are not restricted by the hardware which physically connects them; the segments are defined by flexible user groups that you create using software. 
With VLANs, you can define your network according to: 
·Organizational groups: For example, you can create one VLAN for the Marketing department; and another for Finance. 
·Hierarchical groups: For example, you can create one VLAN for Directors, another for Senior Managers and another for Supervisors. 
Benefits of VLANs 
Implementing VLANs on your network has three main advantages: 
·It eases the change and movement of devices on IP networks 
With traditional IP networks, network administration personnel spend much of their time dealing with moves and changes. If users move to a different IP subnet, the IP addresses of each workstation must be updated manually. 
With a VLAN setup, if a workstation on VLAN 1 is moved to a port in another part of the network, the network administrator only needs to configure the new port to belong to VLAN 1. 
·It helps to control traffic 
With traditional networks, congestion can be caused by broadcast traffic which is directed to all network devices whether they require it or not. VLANs increase the efficiency of your network because each VLAN can be set up to contain only those devices which need to communicate with each other. 
·It provides extra security 
Devices within each VLAN can only communicate with devices in the same VLAN. If a device in VLAN 1 needs to communicate with devices in VLAN 2, the traffic must cross a router. 
The example in Figure 1-5 shows a network configured with three port-based VLANs - one for each of the departments who access the network. The membership of VLAN 1 is restricted to ports 1, 2, 3, 4 and 5 of Switch A; membership of VLAN 2 is restricted to ports 4, 5, 6, 7 and 8 of Switch B while VLAN 3 spans both Switches containing ports 6, 7, 8 of Switch A and 1, 2, 3 of Switch B. 
The example in Figure 1-5 shows each VLAN as a single broadcast domain - LAN segments not constrained by their physical location. 

FIG 
Figure 1-5 The Concept of VLANs 
The logical equivalent to the example in Figure 1-5 is shown in Figure 1-6: 

FIG 
Figure 1-6 Logical Layout of VLANs 
VLANs and the Switch Units 
The Switch 1000 and Switch 3000 support port-based VLANs, where a VLAN consists of a set of switch ports. Each switch can support up to 16 VLANs. Each switch port can only belong to one VLAN at a time, except for the Virtual LAN Trunk (VLT) port which belongs to all 16 VLANs. If you need to configure more than 16 VLANs for your network, additional VLANs can be connected through a router. 
Virtual LAN Trunk 
A Virtual LAN Trunk is a connection between Switch units which carries traffic for multiple VLANs. For further details on VLTs, see Connecting Common VLANs Between Different Switches and Creating a VLT 
The Default VLAN 
In any network setup, VLAN 1 is the Default VLAN. 
NOTE: The Default VLAN is the only VLAN which allows Enterprise Manager to access the management agent of the unit. On a new Switch, all the ports belong to VLAN 1. If the devices attached to a port should belong to another VLAN, you must use Enterprise Manager to configure the port in the required VLAN. 
Building VLANs 
A VLAN can comprise a single Switch 1000, or a complex network of Switch 1000s, Switch 3000s and routers each with their associated devices. Regardless of complexity, VLANs are built up from two basic building blocks: 
·Switch to Switch Connections between devices on the same VLANs 
·Switch to Router Connections between devices on different VLANs 
NOTE: Connections between devices in a VLAN must be configured starting with furthest and then next nearest. The furthest device is that which has the greatest number of physical connections between it and the Transcend Network Management platform. 
Connecting Different VLANs Together 
If the devices in a VLAN need to communicate with devices in a different VLAN, each VLAN requires a connection to a router. Communication between VLANs can only take place if they are connected to the router. A VLAN not connected to a router is isolated. 
In the Switch 1000, VLANs are connected to routers using backbone ports. Backbone ports operate as follows: 
·Addresses received on backbone ports are not stored in the Switch Database. 
·Frames with unknown addresses are forwarded to the backbone ports. 
You will need to specify one backbone port for each VLAN connected to the router. For details on configuring a backbone, see Specifying a Backbone Port on a Switch 1000. 
Connecting Common VLANs Between Different Switches 
In the Switch 1000, VLANs are usually connected to other Switch 1000/3000 units using backbone ports. Similar to router connections, you require one backbone port per VLAN. To make the Switch-to-Switch communication connections more cost-effective, both Switch 1000 and Switch 3000 allow you to specify that one port forms part of a Virtual LAN Trunk and carries traffic for multiple VLANs, for further details, see Creating a VLT. If a backbone port is configured to be part of a VLT, you only need one Switch-to-Switch connection for all the VLANs. 
NOTE: VLTs can only be used for links between Switch 1000 and Switch 3000 units. You cannot use VLTs for Switch-router links. 
If you configure a backbone port on one VLAN as a VLT, that backbone port will become a backbone port for all the VLANs on the switch - even if they had no backbone port before. If you subsequently disable the VLT function on that port, the port will become the backbone port for the default VLAN (VLAN 1) and all other VLANs lose their backbone ports. 
Using Non-routable Protocols 
If you are running non-routable protocols on your network (for example, DEC LAT or NET BIOS), devices within one specified VLAN will not be able to communicate to devices in a different specified VLAN. 
Using Unique MAC Addresses 
If you connect a server with multiple network adapters to the switch, we strongly recommend you configure each network adapter with a unique MAC address. 
Example 1 
The example shown in Figure 1-7 illustrates a simple VLAN configuration with a single Switch 1000 whose ports are divided between two VLANs. VLAN 1 is able to talk to VLAN 2 using the backbone port connection between each VLAN and the router. 

FIG 
Figure 1-7 VLAN Configuration with a Single Switch1000 and Router 
By default all ports are configured as belonging to VLAN 1. Therefore, only the VLAN 2 ports and the backbone ports for VLANs 1 and 2 need be configured. 
To set up this configuration: 
1Open the VLAN Configuration panel. 
2From the VLAN list, select VLAN 1. 
3From the VLAN 1 Member list select the port you wish to configure as the VLAN 1 backbone and check the Backbone box. 
4From the VLAN list, select VLAN 2. 
5From the Available list, select the required ports and click ADD. 
6From the VLAN 2 Member list select the port you wish to configure as the VLAN 2 backbone and check the Backbone box. 
7Click OK. 
This configuration is equivalent to the logical layout given below: 

FIG 
Figure 1-8 Example 1 Equivalent Logical Layout 
Example 2 
The example shown in Figure 1-9 illustrates two VLANs spanning two Switch 1000 units. Ports within the same VLAN which span the two Switches communicate via the VLT. VLAN 1 is able to talk to VLAN 2 using the backbone port connection between each VLAN and the router. 

FIG 
Figure 1-9 Two Switch 1000s, Two Servers and Router 
By default all ports belong to VLAN 1. The furthest switch must be configured first and then the nearer. To set up this configuration: 
1Configure VLT between Switches. 
aSelect a port on the furthest Switch. 
bOpen the Port Configuration dialog box and select Information. 
cEnable VLAN Trunk, click OK and close the Port Configuration dialog box. 
You will not be able to communicate with the furthest device until the VLT is configured in the nearest device. 
dSelect connecting port on the nearer Switch and repeat steps 1a to 1d. 
2Move required ports to VLAN 2. 
aOpen the General Information dialog box and click VLANS. 
bFrom the VLAN list select VLAN 2. 
cFrom the Available list select the ports to be moved to VLAN 2, click ADD and then OK. 
dSelect the nearer Switch and repeat steps 2a to 2c, ensuring that port 26 is one of the selected ports. Port 26 is the server port. 
3Configure a backbone for both VLAN 1 and VLAN 2. 
aSelect the nearer Switch. 
bOpen the General Information dialog box and click VLANS. 
cFrom the VLAN list select VLAN 1. 
dFrom the Members list select a port, check the Backbone box and click OK. 
eFrom VLAN list select VLAN 2 and repeat step 3d. 
NOTE: The above backbone ports must not be in VLT mode. 
4Connect Servers 
This configuration is equivalent to the logical layout given below: 

FIG 
Figure 1-10 Example 2 Equivalent Logical Layout 
Example 3 
The example shown in Figure 1-11 illustrates two VLANs spanning three Switch 1000 units. Each Switch 1000 connects into a Switch 3000 via a VLT. The attached router allows the two VLANs to communicate with each other. 

FIG 
Figure 1-11 VLAN Configuration with a Switch 3000 as a Basement Switch 
To set up this configuration: 
1Configure VLTs between Switch 1000s and the Switch 3000. For details, see Creating a VLT. For each Switch 1000: 
aSelect Port 26. 
bOpen Port Configuration Dialog and select Information. 
cEnable VLAN Trunk, click OK. 
dSelect connecting port on Switch 3000 and repeat steps 1a to 1c. 
2Move required ports on all Switches to VLAN 2. For details, see Moving a Port Between VLANs. For each Switch 1000 and 3000: 
aOpen the General Information dialog box and click VLANS. 
bFrom the VLAN list select VLAN 2. 
cFrom the Available list select the ports to be moved to VLAN 2, click ADD and then OK. 
NOTE: Ensure that the ports on the Switch 3000 connecting to the router are configured for the required VLAN. For details see the Switch 3000 User Guide accompanying your Switch 3000 . 
3Connect servers ensuring that they are connected to the appropriate VLAN. 
This configuration is equivalent to the logical layout given below: 

FIG 
Figure 1-12 Example 3 Equivalent Logical Layout 
Configuring a Virtual LAN 
A VLAN is configured at two levels: 
·Device Level This allows you to move ports from one VLAN to another, change VLAN names, and specify backbone ports. Device level changes are made to VLANs through the VLAN Configuration dialog box. 
·Port Level This allows you to specify VLTs. For further details, see Creating a VLT. 
To display the VLAN Configuration dialog box: 
1Double-click on part of the front panel of the device that is not a port. 
2In the General Information dialog box , click VLANS category, shown in Figure 1-13). 
NOTE: The VLAN configuration of a switch is not changed until you click OK 
Moving a Port Between VLANs 
To move a port between VLANs: 
1Select from the VLAN list the VLAN to which the port is to be moved. 
2From the Available list select the ports which are to be moved to the VLAN, then click ADD. 
Specifying a Backbone Port on a Switch 1000 
Backbone ports enable communication between devices. In the VLAN panel: 
1From the VLAN drop-down list, select the VLAN to which the port belongs. 
2Select the port from from the Members list. 
3Check the Backbone box. 

FIG 
Figure 1-13 General Information with VLAN Configuration Panel14 
NOTE: If the Switch already has a VLT backbone, then this is the backbone for all VLANs. The VLT backbone must be removed before any other backbones can be configured. For further details, see Creating a VLT. 
For details on Switch port settings, see Switch 1000, Switch 3000 . 
Changing a VLAN's Name 
The VLAN name can be used to reflect the department or user group. To change the name of a VLAN: 
1From the VLAN drop-down list, select the VLAN which is to be renamed. 
2Click Edit Name. 
The Edit VLAN Name dialog box appears, shown in Figure 1-14. 

FIG 
Figure 1-14 Edit VLAN Name Dialog Box 
3Enter the VLAN's new name and select OK. 
In the VLAN Configuration panel: 
Ports are color-coded as follows: 
·White - The port is a regular port. 
·Green - The port is a backbone port. 
·Blue - The port is a VLAN Trunk port. 
·Yellow - The port is a VLAN Trunk-backbone port 
Available Lists the ports on the switch which are not members of the selected VLAN, and includes members of other VLANs 
VLAN Lists the VLANs that are configured on the switch. You can define up to 16 VLANs. All ports belong to VLAN 1 by default. 
Member Lists the ports that are members of the currently selected VLAN. 
ADD Adds the ports selected in the Available list to the current VLAN. 
Undo Returns the ports to the VLANs they were in when the dialog box was opened. When you click OK, the changes to the VLAN configuration are written to the switch and cannot be reversed using the Undo button. The Undo button is only active when the port that was added to the VLAN is selected. 
To remove a port from a VLAN after you have clicked OK, you must re-open the dialog box, select a different VLAN and make the port a member of that VLAN using the ADD button. 
Edit Name Displays the Configure VLAN Name dialog box, which enables you to change the name of the selected VLAN. 
Backbone (Switch 1000 only) Specifies whether the port selected in the Members list is a backbone port. A backbone port is a port that is configured so that it can connect a VLAN to the rest of your network; that is, the Switch does not learn addresses from packets received on that port. Any port in a VLAN can be designated as the backbone port for that VLAN. For small networks, you may not require a backbone port. 
Creating a VLT 
A VLAN Trunk (VLT) is a link which carries traffic for multiple VLANs between switches. Traditionally, one port is required on each device for each LAN to communicate with devices on the same LAN but on different switches. By using a VLT between two Switches then only one port need be configured on each. The furthest Switch is configured first because communication is lost between the two devices until the VLT is configured at both ends of the connection. VLTs are configured using the Switch Port dialog box, shown in Figure 1-15. 

FIG 
Figure 1-15 Switch Port Dialog Box 
To establish a VLT: 
1Configure the furthest port 
aDouble-click on the required Switch port, the Switch Port Dialog box is displayed. 
bEnable VLAN Trunk and click OK 
2Configure the port on the nearer unit. Repeat steps a and b above. 
Resetting and Initializing a Device 
Resetting a device simulates switching it off and on. You may want to reset a device if you want to return it to its previous set up. 
To reset a device: 
1Select the device you want to reset. 
2From the Configure menu, choose Device/Subnetwork. 
3In the Configuration window, from the Restart menu, choose Reset. 
Enterprise Manager asks you to confirm the reset. 
Initializing a device causes parameters on the device, to be returned to factory settings. You may want to initialize a device if resetting it does not return it to a manageable state. 
CAUTION: Initializing a device removes all configuration information such as resilient links and passwords. Passwords are not reset on the Hub TR. The IP parameters are retained to ensure you can continue communicating with the device. After you initialize an ECS you must re-enter the IP parameters via the ECS local management interface. 
To initialize a device: 
1Select the device you want to initialize. 
2From the Configure menu, choose Device/Subnetwork. 
3In the Configuration window, from the Restart menu, choose Initialize. 
Enterprise Manager asks you to confirm the initialization. 
Upgrading the Management Agent Software 
Enterprise Manager provides you with the latest versions of the management agent software for devices available at the time of release. You can use Enterprise Manager to upgrade management agents in the devices on your network. If a more recent version of the management agent software is available, it can be obtained from the 3Com Bulletin Board Services. 
NOTE: You can use the Software Upgrade Manager to upgrade several devices of the same type (for example, several Hub 10's). See "Using the Software Upgrade Manager" for more information. 
To upgrade the management agent software: 
1Select the device for which you want to upgrade the agent software. 
2From the Configure menu, choose Device/Subnetwork. 
3In the Configuration window, choose the Upgrade menu. 
4In the Software Upgrade dialog box (shown in Figure 1-16), enter the name of the agent software file with which you want to update the agent. 
NOTE: Upgrading the LinkSwitch 1200 management agent software is performed using Telnet. See "Upgrading the LinkSwitch 1200" for more information 
In the Software Upgrade dialog box: 
Device Name Shows the name of the device on your network. 
Software Shows the version number of the current agent software. 
Hardware Shows the version number of the hardware. 
IP Address Provides a box for you to type the IP address of the PC to be used as the server from which the agent software is updated. The default is the IP address of the PC running Enterprise Manager. 

FIG 
Figure 1-16 Software Upgrade Dialog Box 
File Name Provides a box for you to type the name of the file with which you want to update the agent software. The prefix of the required file type for the device you are upgrading is already displayed in this field. 
Browse Displays a dialog box which you can use to specify the drive, directory, and filename of the new software agent. 
You can use the Browse button to see the files that are available. The file you select must be in the C:\TRANSCND\UPGRADE directory. If it is not, you must copy it to this directory before upgrading. 
Upgrading the LinkSwitch 1200 
Upgrading the LinkSwitch 1200 management agent software is performed using Telnet: 
1In the Software Upgrade dialog box for LinkSwitch 1200, click Telnet and complete the login to the device. 
2Upgrade the management agent software as described in the LinkSwitch 1200 User Guide (DUA1664-0AAA0x). 
3Initialize the LinkSwitch 1200 using Telnet. 
4Exit the Telnet session and return to Enterprise Manager. 
Using the Software Upgrade Manager 
Enterprise Manager can upgrade the software running on one or more supported devices. You can upgrade software on any number of devices in a single operation, provided the following conditions are met: 
·All devices to be upgraded in a single operation are of the same type (for example, all are Hub 10's). 
·All devices to be upgraded simultaneously are in the same group. 
NOTE: The upgrade function is available for all supported devices with more than one software version available. 
To upgrade device software: 
1In the subnet view, select any one supported device of the type you want to upgrade. 
2From the View menu, choose Distribution. 
Wait for the 3Com Upgrade Manager window to appear, as shown in Figure 1-17. 

FIG 
Figure 1-17 3Com Upgrade Manager Window 
The 3Com Upgrade Manager window lists all devices that are of the same type and on the same subnetwork as the one you selected. Devices that are not running the latest software registered to the Transcend management platform are selected automatically. 
NOTE: The 3Com Upgrade Manager polls all devices and upgrades its status display at start-up and during upgrading/baselining. To poll all devices again and refresh the display manually, choose Refresh Device Database from the File menu. 
3Select all devices you want to upgrade. Leave unselected those devices you do not want to upgrade. 
Click to select a device; click again to deselect the device. You can select all devices by choosing Select All from the Edit menu. You can deselect all devices by choosing Deselect All from the Edit menu 
Double-clicking an item in the 3Com Upgrade Manager window displays a Status window for that item. The Status window contains a log of the upgrade process for that device. 
4When all items to be upgraded are selected, select Upgrade from the Operation menu or click on the Upgrade icon in the toolbar (the toolbar icons are described in Table 1-3). 
 
Table 1-3   Icon Descriptions	 
Icon	 Name	 Description	 

FIG	 Upgrade Icon	 Starts the upgrade process for the selected device or devices. Clicking the Upgrade icon is equivalent to selecting Upgrade from the Operation menu.	 

FIG	 Print Icon	 Prints the upgrade summary information for the selected device or devices. Clicking the Print icon is equivalent to selecting Print from the File menu.	 

  
The Package Name Selection window appears now. The list of available software upgrade packages depends on the type of device selected. Figure 1-18 shows the software package list for FMS stackable hubs.
FIG 
Figure 1-18 Package Name Selection Window 
5Select the desired software package and click OK to display the Upgrade Confirmation window shown in Figure 1-19. 

FIG 
Figure 1-19 Upgrade Confirmation Window, FMS 
6Check that you have selected the correct device and software package, and then click OK. 
The Upgrade Progress window appears as shown in Figure 1-20.
FIG 
Figure 1-20 Upgrade Progress Window 
The Upgrade Progress window displays the following information: 
·The device that is currently being upgraded 
·The number of devices that have been upgraded completely 
·The number of devices remaining to be upgraded (this number includes the device currently being upgraded) 
·The estimated time remaining to complete upgrading all of the selected devices 
·A meter displaying the percentage of the upgrade process (for all selected devices) that is complete 
NOTE: You can cancel the upgrade operation at any time by clicking Cancel in the status window. The operation is canceled as soon as the device currently being upgraded is completed. 
In the 3Com Upgrade Manager window, which remains visible throughout the upgrade procedure, the device icons change colors to indicate each device's current status, as described below: 
Green Device upgraded successfully. 
Black The device was selected for upgrade but the upgrade process is not yet complete. 
Yellow Enterprise Manager cannot access the device (community string mismatch). 
Blue There is no response from the device. 
Red The upgrade operation failed. 
White The device is not selected for upgrade. 
7Double-click any item in the 3Com Upgrade Manager window to display a Status window for the device currently being upgraded. 
The Status window contains information from the upgrade log for that device as it appeared when the device was double-clicked. Information is not updated unless you close the Status window and open it again by double-clicking the device for which you want a status report. Click OK to close the Status window. 
8Close the Upgrade Manager utility by choosing Exit from the File menu. 
Displaying Detailed Information About a Device 
Enterprise Manager enables you to display detailed information about devices on a subnet. 
To display this information: 
1Double-click on part of the front panel of the device that is not a port. 
2In the General Info dialog box, select ID or MIB II from the Category box. 

FIG 
Figure 1-21 Device ID Dialog Box 
In the Identification panel shown in Figure 1-21: 
Name Shows the name of the device used by Enterprise Manager. 
Network Shows the name of the subnetwork of which the device is part. 
IP Addr Shows the IP address of the device. 
IPX Addr Shows the IPX address of the device (if applicable). 
MAC Addr Shows the MAC address of the device. 

FIG 
Figure 1-22 Device MIB II Dialog Box 
In the MIB II panel shown in Figure 1-22: 
sysDescr Shows the system description supplied by the Management Agent software. 
sysObjectId Shows the SNMP object identifier for the device's Management Agent software. 
sysUpTime Shows the time that has elapsed since the last reset. 
sysContact Provides a box for you to type name of the person who can be contacted in the event of a problem with the device. 
sysName Provides a box for you to type the name of the device. You can use the Preferences dialog box from the File menu to specify that the name of the device used by Enterprise Manager is derived from this field when Autodiscovery builds your network. 
sysLocation Provides a box for you to type the location of the device. 
sysServices Shows the services that the device supports. 
Setting Up a Resilient Link Pair 
You can protect a critical communication link against failure by ensuring that if the main communication link fails, a standby duplicate link immediately and automatically takes over the task of the main link. Each main and standby link pair is referred to as a resilient link pair. You should consider setting up a resilient link pair to protect inter-repeater or backbone connections. 
The resilient link pairs can be set up to use ports on the same, or different units in the stack (using ports on different units prevents the loss of both links if a single unit fails). The ports can be connected to the same or different media, and the devices at the end of the resilient link can be at different locations. 
Figure 1-23 shows you how a resilient link pair protects an inter-repeater connection. The main link connects Stack A, unit 4, port 1, to the crossover port of Stack B, unit 3, forming an inter-repeater connection. If this link fails, the standby link connects Stack A, unit 2, port 6 to the crossover port of Stack B, unit 2, maintaining the inter-repeater connection. 

FIG 
Figure 1-23 Example of Resilient Links 
When you set up a resilient link pair, you must follow these rules: 
·A resilient link pair can only be set up on ports connecting to fiber and twisted pair cable types. 
·A resilient link pair can only be set up if neither of the ports already form part of another resilient link. 
·Full Security (Disconnect Unknown Device) must not be set up on either the main or standby port. For more information about security configuration, see "Setting Up Security for Ports". 
·For SuperStack II Hub 10 and LinkBuilder FMS: 
·The main link can be on either a Hub 10 or FMS unit 
·The standby link must be set up on a Hub 10 unit, and the Disable on Boot switch on the unit must be set to Disable. 
·Up to 16 resilient link pairs can be set up for each stack. 
·For Switch 1000, Switch 3000, and OfficeConnect Hub/8TPM: 
·The main and standby ports must be on the same unit. 
·Up to 13 resilient link pairs can be set up on a 24 port Switch 1000. 
·Up to 7 resilient link pairs can be set up on a 12 port Switch 1000. 
·Up to 4 resilient link pairs can be set up on a Switch 3000, Switch 3000 TP, and OfficeConnect Hub/8TPM. 
·A backbone port on a Switch 1000 can be configured as a main port in a resilient pair; if a resilient backbone fails, the standby port is immediately configured as a backbone before any communication is carried out. A backbone port cannot be configured as a standby port. 
·For LinkBuilder ECS and MSH: 
·The standby link must be set up on a module with the Disable on Boot jumper set to Disable. 
·Up to 16 resilient link pairs can be set up for each chassis. 
·A resilient link pair can only be set up on modules connected to the same backplane. 
To set up a resilient link pair: 
1Double-click on part of the front panel of the device that is not a port. 
2In the General Info dialog box, choose the Resilience category. 
3In the Resilience panel (shown in Figure 1-24), click on Create. 
4In the Create Resilient Pair dialog box, choose the unit and port for the main link and the unit and port for the standby link. 
When you have created a resilient link pair, its entry in the resilience table is color-coded as follows: 
·Green - Main port enabled and repeating traffic. 
·Yellow - Standby port enabled and repeating traffic. 
·Red - Main and Standby ports failed. 
In the Resilience panel: 
Main Shows the unit and port number of the main link. 
Standby Shows the unit and port number of the standby link. 
Link State Shows whether the resilient link pair is operational or not. When operational either the main port or the standby port can repeat traffic. 
Main State, Standby State Shows whether the main or the standby link is the active link in the resilient link pair. 
Create Displays a dialog box which you can use to choose the main and standby links in the resilient link pair. 

FIG 
Figure 1-24 Resilience Status 
Delete Removes the resilient link pair from the table when an entry in the resilience table is selected. If you delete an entry in the resilience table, the current active link remains enabled and the current standby link disabled. 
NOTE: If the main link fails and the standby link takes over and you subsequently solve the problem with the main link, the standby link continues to be active and the main link continues to be disabled. If this happens, you can do one of the following: 
·Delete the link from the resilience table and create a new resilient link pair with the currently active link as the main link. 
·Use Telnet to log into the device and switch over the main and standby links. 
Using a Device to Monitor Your Network 
When Enterprise Manager monitors a device on your network it must periodically poll the device to discover its status. You can minimize this overhead for Enterprise Manager by using the management agent on one device to monitor other devices, and to notify Enterprise Manager if they stop or restart communications. 
This facility also allows you to monitor devices that are otherwise not directly manageable, such as workstations and network printers. However the device icon does not change color if the monitored device stops communicating, an event is shown in the event log. 
To use a device to monitor your network: 
1Double-click on part of the front panel of the device that is not a port. 
2In the General Info dialog box, choose the WorkGroup category. 
3In the WorkGroup Monitor panel (shown in Figure 1-25), click Add. 

FIG 
Figure 1-25 WorkGroup Monitor 
4In the Add/Edit Remote Poll dialog box (shown in Figure 1-26), enter the IP and/or IPX address of the device which is to be monitored. 

FIG 
Figure 1-26 Add Remote Poll Dialog Box 
5Choose the poll rate at which the device is to be monitored. 
If the device is critical to the performance of your network, select a frequent poll rate. If the device is not important or on a remote network you can select a less frequent poll rate. 
6Select whether monitoring of this device is to be enabled or disabled. 
You can create up to 10 polling sessions all of which can be enabled. You can keep disabled sessions for future use. 
In the WorkGroup Monitor panel: 
Address Shows the addresses of the monitored devices. 
Rate Shows the frequency at which the device is polled. 
Round Trip Shows the time taken for the device to respond to the last poll. 
Information Shows the number of routers through which the device communicates with the monitored device or any other information gathered during the poll. 
Entries are color-coded as follows: 
·Green - Device being polled and communicating 
·Red - Device being polled but is not communicating 
·Blue - Device not being polled 
You can edit or delete a Remote Poll by selecting it from the dialog box and clicking on the appropriate button. 
Configuring Ethernet Switching Options 
The switching options for the Switch 1000 and Switch 3000 allow you to enable or disable PACE (Priority Access Control Enabled). Enabling PACE increases network performance, especially if you are running multimedia applications. 
The rules for enabling PACE are: 
·PACE should only be enabled on ports that connect to a device with a single MAC address, such as an end-station, switch, bridge or router 
·You should not enable PACE on a port connected to a repeater 
·If you have PACE-equipped devices at both ends of a link, PACE should be enabled on one of devices only 
You can also select the forwarding mode and specify the ageing period for the address table in the unit. 
The switching options for a LinkSwitch 1200 allow you to control the types of frames forwarded to each port, determine the action taken when a loop is detected and specify the ageing period for the address table in the unit. 
To configure the Ethernet switching options: 
1Double-click on part of the front panel of the device that is not a port. 
2In the General Information dialog box, select Switching from the categories list. 
3In the Switching Configuration panel (shown in Figure 1-27 and Figure 1-28), configure the device as described in the remainder of this section. 
Switch 1000, 3000 

FIG 
Figure 1-27 Ethernet Switching Dialog Box (Switch 1000 and Switch 3000) 
PACE Default for Unit Determines whether PACE is enabled or disabled as default for ports on the switch. A port with Use Unit Default selected (see "Configuring a Switched Ethernet Port") has its PACE setting determined by this field. 
Forwarding Mode Allows you to set the forwarding mode for the switch: 
NOTE: Store and Forward is the only mode supported for Switch 3000. 
·Intelligent - The switch monitors error traffic on the network and changes the forwarding mode accordingly. If less than 18 errors per second are detected then it operates in Fast Forward. If more than 18 errors per second are detected then the switch operates in Store and Forward until the rate returns to zero. 
·Fast Forward - Frames are forwarded as soon as the destination address is received and verified. The forwarding delay or latency for all frames in this mode is 40µs but with the lack of checking time, error frames are propagated onto the network. 
·Fragment Free - A minimum of 512 bits of the received frame is buffered prior to the frame being forwarded. This ensures that collision fragments are not propagated through the network. The forwarding delay, or latency, for all frames in this mode is 64µs. 
·Store and Forward - Received packets are buffered in their entirety prior to forwarding. This ensures that only good frames are passed to their destination. The forwarding delay for this mode varies between 64µs and 1.2ms, depending on frame length. In this mode the latency, measured as the time between receiving the last bit of the frame and transmitting the first bit, is 8µs. 
Ageing Timer Specifies the ageing time for all non-permanent entries in the Switch Database (SDB). 
LinkSwitch 1200 

FIG 
Figure 1-28 Ethernet Switching Dialog Box (LinkSwitch 1200) 
Forward Frames These options allow you to control the types of frames forwarded to each port: 
·Source Routing Frames - When checked, allows source routing frames to be forwarded to other ports. 
·Multicast Frames - When checked, allows multicast frames to be forwarded to other ports. 
Loop Detection Determines the action taken when a loop is detected. It can be one of the following: 
·No Action 
·Shutdown Port Only - Shuts down the port on which the duplicate address appeared. This is the recommended setting as it allows the devices not involved in the loop to continue communicating. 
·Shutdown All Ethernet Ports - Shuts down all Ethernet ports and leaves the FDDI port operational. 
·Shutdown All Ports - Shuts down both the FDDI and Ethernet ports. 
Address Table There are two options: 
·Ageing Timer - Allows you to set a time in seconds (min 0/max 43200) after which non-active addresses are removed from the filtering database. Addresses removed from the filtering database are relearned as soon as the station retransmits. 
·Periodic IP Echo - When checked, the LinkSwitch broadcasts IP echo frames onto the subnetwork which causes inactive stations to respond so that their addresses remain in the address table and are not aged out. 
Viewing FDDI Ring Parameters 
To view the FDDI ring parameters: 
1Double-click on part of the front panel of the device that is not a port. 
2In the General Information dialog box, select FDDI from the categories list (shown in Figure 1-29). 

FIG 
Figure 1-29 FDDI Ring Configuration 
In the dialog box: 
FDDI Ring Shows the Ring State and the Configuration State. See Table 1-4 and Table 1-5 for an explanation of each of these states. 
Target Token Rotation Time Shows the following: 
·Operational - This is the negotiated Target Token Rotation Time resulting from the bidding process between FDDI stations during ring initialization. This value cannot be changed. 
·Max allowed - This is the maximum length of time allowed for a token to move around the ring. This value cannot be changed. 
·Min Allowed - This is the minimum length of time allowed for a token to move around the ring. This value cannot be changed. 
·Requested - This shows the current requested Token Rotation Time for this station. 
·Valid Transmission Time - Shows the time in milliseconds in which the station must receive a valid frame or token. 
 
Table 1-4   Ring State	 
Ring State	 Meaning	 
Isolated	 The initial ring state.	 
Non-Operational	 The MAC is participating in ring recovery and the ring is not operational.	 
Operational	 The ring is operating normally and passing data.	 
Detected Problems	 The ring has not been operational for a specified period.	 
Non Op Dup	 The address of the MAC duplicates the address of another MAC on the ring. The ring is not operational.	 
Operation Dup	 The address of the MAC duplicates the address of another MAC on the ring. The ring is operational.	 
Directed	 The MAC is sending beacon frames notifying the ring of a stuck condition.	 
Trace Recovery	 Ring Management has discovered a stuck beacon condition and is initiating a trace to recover.	 

  
 
Table 1-5   Configuration State	 
Configuration State	 Meaning	 
Isolated	 The MAC or port is not inserted into any path.	 
Wrap_A	 The secondary path is wrapped to the A port.	 
Wrap_B	 The primary path is wrapped to the B port.	 
Wrap_S	 The primary path is wrapped to the S port.	 
C_Wrap_A	 The primary and secondary paths are joined internally to the station and wrapped to the A port.	 
C_Wrap_B	 The primary and secondary paths are joined internally to the station and wrapped to the B port.	 
C_Wrap_S	 The primary and secondary paths are joined internally to the station and wrapped to the S port.	 
Operational (Thru)	 Normal FDDI operating state.	 

  
Working with Alarms 
Alarms are simple to configure and can be easily modified using Alarm Manager. They can be used to enhance your network performance and prevent network downtime. 
An alarm allows you to set thresholds on various statistics monitored by a device. You can specify the action to be taken if the threshold is exceeded. Alarms are powerful tools which, when configured correctly, can be used to prevent inconvenient or even catastrophic network failure. Their main advantage lies in the fact that you can specify at exactly which point the action will take place. They can therefore be tailored to suit the normal operating conditions of your network. In addition alarms can be used for network planning and long term analysis; for example, study of network traffic can determine whether your network is nearing capacity and whether or not it needs to be expanded. 
Alarm Manager can be used to create and delete alarms as well as configuring existing ones. The alarms are stored by the device. This has the following advantages: 
·Network bandwidth is not used to poll the device for information unnecessarily. The alarm is monitored by the device. 
·The accuracy and responsiveness of the alarm is increased as all computations are carried out locally by the device. 
An alarm is associated with a counter on the device. A counter records the number of times a specific event occurs on a device. An event could be the detection of an error frame or network traffic. The rate at which the counter increments is sampled a number of times within a given time period from which an average is calculated. This determines the rate of increase/decrease for this counter. The averaged value is the value of the alarm. 
This value is used to indicate that your network is operating within normal limits or that an exceptional operation condition has occurred. If an exceptional operating condition means that a user-defined threshold is exceeded, the alarm can be set to cause an action to take place. The type of actions that are available for you to set up are dependent on the type of device to which the alarm is applied. 
Typically an action could be: 
·Send a trap to the WorkGroup Manager causing an event to be added to the event log 
·Disable a port 
You can specify that no action is taken if you are carrying out a trend analysis. 
How do Alarms Work? 
The Alarm Manager creates a new alarm in the alarm table of the selected device. When an alarm is created, two thresholds are specified: a rising threshold and a falling threshold. A rising alarm is generated when the alarm value rises above the rising threshold. Similarly, a falling alarm is generated when the alarm value falls below the falling threshold. 
Alarms use a hysteresis mechanism to ensure that events are not raised due to small fluctuations around the threshold value. This mechanism is illustrated in Figure 1-30. 

FIG 
Figure 1-30 Alarm Event Generation 
After a rising alarm is generated, the alarm value must fall below the falling threshold before another rising alarm is generated. For falling alarms the rule is reversed. 
The Alarm Manager uses the alarm part of the SNMP RMON MIB as described in RFC1271. The Alarm Manager has the ability to auto-calibrate the threshold values of an alarm and the ability to specify an action if an alarm threshold is exceeded (see the next section Alarm Calibration). 
Alarm Calibration 
When you first configure an alarm, you may not know the point at which you want to trigger an action. To determine the right threshold for your device or network, you can create an alarm without specifying an action. By monitoring the levels of activity, you can determine the normal operational bounds of your device or network, and then set your threshold levels at the point where normal values are exceeded. 
Alarm Manager provides auto-calibration facilities. The default threshold values are taken from the Alarm Manager configuration files but can be subsequently updated once the alarm is active. 
Using Alarms to Protect Your Network 
The example below shows how you can use alarms to detect excessive network load. 
You can create an alarm associated with the Broadcast Frame Counter for a port on a device. The Broadcast Frames Counter measures the number of broadcast frames received by the port. You should configure the alarm to measure the averaged rate for the Broadcast Frames Counter and set the action to disable the port if the average exceeds the threshold you have defined. Disabling the port protects your network from being flooded by broadcast frames and therefore prevents a broadcast storm. 
Starting the Alarm Manager 
You can access Alarm Manager on either a device or per-port basis. 
To access the Alarm Manager to configure Alarms for a device: 
1Double-click on part of the device front panel that is not a port. 
2In the General Info dialog box, choose the Alarms category. 
The Assigned Alarms list displays the alarms configured for the selected device and shows their current value and peak value (if supported by the device), as shown in Figure 1-31. 

FIG 
Figure 1-31 Alarm Manager Dialog Box 
NOTE: Configuring alarms for a port is described on page 3-38. 
Each alarm is color-coded to show its state. The different states are shown in Table 1-6. 
Table 1-6   Alarm states	 
Alarm Color	 State	 
Green	 The alarm is on and is being monitored by the device.	 
Red	 The threshold value for this alarm has been exceeded.	 
Blue	 The alarm is off or being configured by another management station.	 

  
Filtering Alarms 
For some devices you may have created a large number of alarms, particularly if the device has many ports or is critical to the performance of your network. You can filter the display of the Assigned Alarms to allow you to easily locate an alarm you want to work with. There are two fields in the Filter panel of the Alarm Manager dialog that allow you to do this: 
Category Allows you to select the category of alarms to be displayed in the Assigned Alarms list. The categories available in the drop-down list depend on the type of device. All devices support All Categories. 
If you set the category to Index, you can enter the Index number of the alarm that is used in the Alarm Table in the device's MIB. 
The alarm index is displayed next to an event in the Event Log. If you filter by Index, this allows you to locate an alarm that generated an event. 
Search Pattern Allows you to filter the Assigned Alarms list by typing a text string in the field. Only the alarms containing the specified text string are then displayed in the Assigned Alarms list. The Search Pattern works in conjunction with the Category selected above. You can use the wildcard character * (asterisk) to represent any number of characters in your Search pattern. 
Alarm Operations 
To work with an existing alarm, select the alarm from the Assigned Alarms list and click on one of the buttons described below. 
To create a new alarm, see the next section "Adding an Alarm". 
On Turns the selected alarm on if it is turned off. 
Off Turns the selected alarm off if it is turned on. 
Not all devices support alarms being turned Off. This button is grayed out if the option is not supported. 
Delete Deletes the selected alarm and removes it from the Assigned Alarms list. 
Calibrate Automatically sets the alarm's threshold and recovery values. It does this using a percentage of the alarm's peak value. The percentage is pre-defined in the device's alarm configuration file and cannot be changed. 
NOTE: Not all devices support peak value. In this case the calibration is made against the current value of the alarm and not its peak value. 
Refresh Updates the selected alarm(s) in the Assigned Alarms list to show the latest current and peak values. 
Properties Opens the Alarm Properties dialog box shown in Figure 1-32 and allows you to configure an alarm to best suit your device or network conditions. 
See the section "Setting Alarm Properties"for information about using this dialog box. 
Setting Alarm Properties 
The Alarm Properties dialog box allows you to set and alter the properties of one or more alarms. It contains the following: 
Name Displays the name of the selected alarm. 
State Shows the current state of the alarm. 
Current Value Shows the current value for this alarm. 
Peak Value If the device supports peak value, displays the Peak Value for this alarm since it was created or reset. 
Threshold Level (Rising Threshold) Lets you specify the value at which the alarm's threshold event is triggered. This threshold is the point at which it is determined the network is no longer operating correctly. Usually an action needs to be taken and you need to know that the threshold has been exceeded. 
Recovery Level (Falling Threshold) Lets you specify the value at which the alarm's recovery event is triggered. The recovery point is used to prevent the alarm from repeatedly triggering if the alarm crosses the threshold level several times in rapid succession. Once a recovery level is set, the alarm is not re-triggered until the recovery point is reached as shown in Figure 1-30. 
Threshold Event Determines what action is taken if the alarm exceeds the threshold. Choose an event from the drop-down list. 
Recovery Event Determines what action is taken when the recovery level is reached. Choose an event from the drop-down list. 
Sampling Period Type in or use the buttons to set the sample period. The minimum value is 1 second; the maximum 999 hours, 59 minutes and 59 seconds. 
OK Modifies the selected alarm. Only the properties that you have changed are written to the device. 
Cancel Closes the Alarm Properties dialog box without making any changes. 

FIG 
Figure 1-32 Alarm Properties Dialog Box 
Details Opens the Alarm Details dialog box. This dialog box displays detailed information about the alarm for users experienced in using the Alarm MIB. It shows the following: 
·Name - The name of the alarm. 
·Table Index -The entry index in the device's alarms table. 
·MIB Object - The MIB name of the statistic for the selected alarm. 
·Object ID - The complete MIB object ID in dot delimited numeric format. 
·Owner - The name of the person or management station that created the alarm. 
Adding an Alarm 
When you create a new alarm, the alarm is created with default properties as defined in the device's configuration file. You can change the alarm's properties to make it more effective for your device or network. See "Alarm Operations" for more information. 
To add a new alarm for a device: 
1In the Alarm Manager dialog box, click on the New button. 
The New Alarm dialog box opens. 
2Select the category of alarm to be added from the Available Categories List. 
If you apply a category filter in the Alarm Manager dialog box, the same category is selected in the New Alarm dialog box. If you do not want to add this category of alarm, select another category. 
All categories of alarm are displayed for the selected device. The selected category determines which available statistics are displayed. Each time the category is changed, the Available Statistics list is updated accordingly. 
3Select the statistics counter to be monitored for the new alarm from the Available Statistics list. 
The selected statistic determines which Available Instances are displayed. 
4Select an instance or instances to which this alarm should be applied. An instance can be the whole device or an individual module or port. 
5Click Add. 
The alarm is added to the Assigned Alarms list and set to On. 
6Add any other alarms you require for this device or click Close to exit the New Alarm dialog box. 

FIG 
Figure 1-33 New Alarms Dialog Box 
Setting Up Security 
The security features provided allow you to protect sensitive information on your networks and prevent unauthorized use of the network. You can set up security features for a whole device, or just for particular ports. 
There are two main ways of protecting your network. 
·Disconnect Unauthorized Device (DUD) - also known as Disable on Intrusion 
·Need to Know (NTK) - also known as Data Privacy 
You can set up Disconnect Unknown Device and Need to Know using WorkGroup Manager on the following devices: 
·SuperStack II Hub 10 (running management agent version 3.0 or later) 
·SuperStack II Switch 1000 
·LinkBuilder MSH (running management agent version 4.0 or later) 
·OfficeConnect Hub/8TPM 
For Hub 10 and MSH running earlier versions of their management agents, and for LinkBuilder ECS and LinkBuilder TP/8i, a subset of the security features described in this section is available on a per-port basis only. 
Disconnect Authorized Device 
Even if you disable all unused ports it can be difficult to prevent unauthorized users from accessing the network by connecting devices to enabled ports normally used by other devices. WorkGroup Manager lets you configure each port to have an authorized address or addresses that are permitted to transmit to the network. 
Once configured, the device examines the source address of each incoming frame. If an unauthorized device address is encountered, an action can be taken. In most cases the action taken is to disable the port. However, if several devices are authorized to access that port you may not want to disable it. Instead you can send an event to WorkGroup Manager to inform you of the unauthorized device on your network. 
Need To Know 
Ethernet is essentially a broadcast technology. You would not shout confidential information across a crowded office for everyone to hear. Yet that is exactly what the LAN does. Private data is sent to every station on the LAN and with the correct equipment the data can be received and decoded by anyone. 
When you enable Need to Know the device checks the destination address of each frame and only allows the device to which the frame is addressed to see the original data. Every other device connected to the hub or switch sees a frame in which the original data has been overwritten. 
Need to Know provides ideal baseline security and can be implemented easily. You do not need special Ethernet adapters. You can configure the hub to learn the address or addresses of devices connected to a port or you can enter authorized addresses for each port using WorkGroup Manager. 
Unit Level Security 
To configure security for a device: 
1Select the device for which you want to configure security. 
2From the View menu, select General Info. 
3In the General Info dialog box, choose the Security category. 
4In the Security panel (shown in Figure 1-34), configure the security features for each port. 
5Click OK when the security setup is complete. Any changes only take effect when you click OK. 
NOTE: Setting up security on a per-port basis is described in"Setting Up Security for Ports" . 

FIG 
Figure 1-34 Unit Level Security Configuration Dialog Box 
In the Security Configuration dialog box: 
Port Selection Panel Shows the following: 
·Available - This list box shows the ports in the stack identifying them by unit number, port number and media type. Click on a port to select it from the list. Multiple selections are made in the standard MS-Windows way. 
·Selected - Shows the ports selected to be configured. Click on a port to select it from the list. Multiple selections are made in the standard MS-Windows way. 
·Select - Clicking on this button adds the selected port. 
·- Clicking on this button removes the selected ports from the Selected list to the Available list. 
·All - Adds all the available ports to the Selected list. 
·- Removes all the selected ports from the Selected list. 
Disconnect Unknown Device Allows you to configure the learning and security mode of the selected port(s). 
·No Restriction - Disables all security and learning features. 
·Continually Learn - All addresses transmitting to this port are valid and are stored in the port address table. 
·Full Security - Learning is disabled and only the address entered as a valid address for this port is allowed to transmit to this port. 
·Auto Learn - The port learns the MAC address(es) of the devices transmitting to this port and stores them permanently in its address table. The maximum number of addresses learned by the port(s) is determined by the value shown in the No. of Addresses field. Once the table is full, the port automatically switches to Full Security mode. 
·Disable on Intrusion - Compares the source address of a frame received on the port to the authorized address(es) of the device(s) attached to it. If the source address of the incoming frame does not match an authorized address for this port, the port is disabled. 
·No. of Addresses - Shows the number of addresses that can be authorized to transmit to this port and stored in the address table. 
Need To Know Allows you to configure which frames are forwarded to the selected port(s). These options are grayed out if the port does not support configurable NTK. 
·Disabled - All frames are forwarded. 
·Enabled - The port examines the destination address of the frame. If it matches an authorized address for the port it is forwarded. If it does not, it is discarded. 
·Allow Broadcasts - In addition to Enabled, allows broadcast frames to be transmitted to the port. 
·Allow Broadcasts and Multicasts - In addition to Enabled, allows broadcast and multicast frames to be transmitted to the port. 
NOTE: The Switch 1000 implements permanent Need To Know because it only passes data to a port on which the addresses device resides. Therefore, Need To Know parameters are not configurable on the Switch 1000. 
 2 Managing Special Device Features 
This chapter describes management features specific to only one type of device. It also describes three Enterprise Manager utilities that can help you manage devices. It contains the following topics: 
·Special Features for OfficeConnect Hub/8TPM 
·Special Features for ECS 
·Special Features for MSH 
·Special Features for LANplex and Switch 2200 
·Using the MIB Browser 
·Using the BOOTP Server 
·Using the TFTP Server 
Special Features for OfficeConnect Hub/8TPM 
In addition to the device management features for the Office Connect Hub/8TPM described in Chapter 1 you can: 
·Manage the Alert LED on the unit front panel 
·Configure the modem dial out settings 
·Configure the serial port 
Managing the Alert LED 
The Alert LED can warn you of potential problems with your network. Enterprise Manager allows you to: 
·Test the Alert LED 
·Configure the conditions that cause the Alert LED to light 
·View what conditions have caused the Alert LED to light 
You can configure the Alert LED to light for: 
·Incorrect configurations - If there is a network loop due to an incorrect configuration in your network, a port partitions. The coaxial port automatically partitions if it is not used. 
·Security Violations - If an unsuccessful login attempt occurs, or a device that is not known to your hub tries to communicate with it, a violation occurs. This may be due to someone trying to gain unauthorized access to your network. 
·Poll Failures - If your hub has been configured to monitor a device, it periodically polls it for information. If the device fails to respond, the failure is seen by the hub. 
·Network Errors/Utilization- If the network has a high volume of communication, or there is a large amount of errors with the communication, it could be due to too many devices on your network or an incorrectly configured device. 
By default, the Alert LED is configured to light if a 10BASE-T port is partitioned or if there is high network utilization (over 80%). 
To configure the Alert LED: 
1Select the device from your subnetwork display. 
2From the Configure menu, select General Info. 
3In the General Info dialog box, choose Alerts. 
4In the Alerts panel (shown in Figure 2-1), configure the conditions for the Alert LED. 

FIG 
Figure 2-1 Alerts Dialog Box 
If the Alert LED is already lit, the conditions that caused it to light are displayed in red. The other conditions are displayed in green. 
In the Alerts dialog box: 
The alert field names are color-coded as follows: 
·Green - No alert has occurred. 
·Red - An alert has occurred. 
Once an alert has occurred and the field name has lit red, it will not return to green until the associated Ack button has been clicked to acknowledge the event. 
Alert LED Test Allows you to test the Alert LED on your hub. To test the Alert LED, click Enable and then click OK. When you have completed the test, click Disable and then click OK so that the Alert LED reflects the current alert condition of the device. 
UTP Port Partition Allows you to specify whether the Alert LED lights when a UTP port becomes partitioned, which happens if a network loop or fault occurs on that segment. 
Coax Port Partition Allows you to specify whether the Alert LED lights when the coaxial port becomes partitioned, which happens if a network loop or fault occurs on that segment. 
Login Violation Allows you to specify whether the Alert LED lights if a login violation occurs, which happens if a user attempts to login to your hub using the VT100 screens with an invalid username/password combination three times. 
Port Security Violation Allows you to specify whether the Alert LED lights when a port security violation occurs, which happens if an unauthorized device attempts to communicate using your hub. 
Authentication Failure Allows you to specify whether the Alert LED lights when an authentication failure occurs, which happens if a user attempts to access information in your hub using an invalid community string. 
Remote Poll Failure Allows you to specify whether the Alert LED lights when a remote poll failure occurs, which happens if a remote device fails to respond to a remote poll from your hub. 
Network Utilization Allows you to specify the level of network utilization which causes the Alert LED to light. The specified levels are as follows: 
·High - 80% network utilization 
·Med - 50% network utilization 
·Low - 12% network utilization 
Network Error Rate Allows you to specify the level of network errors which causes the Alert LED to light. The specified levels are as follows: 
·High - 100 errors per 10 000 frames 
·Med - 10 errors per 10 000 frames 
·Low - 1 error per 10 000 frames 
Ack Resets the color of the alert field name to green, and re-reads the status of the alert from the hub. 
Configuring the Modem Dial Out Settings 
You can configure the hub to inform an IP/IPX-based network management application (for example, Enterprise Manager) if the network is operating incorrectly. This feature works over a special modem link. 
To set up the modem link, you must also: 
·Set up the modem, see the OfficeConnect User Guide (DUA1671-0AAA0x). 
·Configure the hub's serial port for modem use, see "Configuring the Serial Port". 
When you have set up the modem link, it is operational and capable of carrying generated messages (traps) from the hub to the management station running the IP/IPX-based network management application. For information on traps, see "Configuring an Ethernet Port". 
To configure the modem dial out settings: 
1Double-click on part of the front panel of the device that is not a port. 
2In the General Info dialog box, choose the Dial Out category. 
3In the Dial Out panel (shown in Figure 2-2), enter the modem dial-out information and click on OK. 

FIG 
Figure 2-2 Dial Out Dialog Box 
In the Dial Out dialog box: 
Dial Out Shows the following: 
·Mgmt Modem Phone Number - Allows you to enter the telephone number of the management station's modem. 
·Dial Sequence - Specifies how the Mgmt Modem Phone Number is dialed in order to establish a connection with the management station's modem. Enter the sequence or click on Default to automatically generate one. 
·Default - Generates the Dial Sequence for you, based on the Mgmt Modem Phone Number. The generated sequence is a common sequence that works for a large number of modems. 
Login Shows the following: 
·User Name - Allows you to enter the user name used by the management station's modem. This is used to generate a default Connect Sequence based on the modem's control sequences. 
·Password - Allows you to enter the password used by the management station's modem. This is used to generate a default Connect Sequence based on the modem's control sequences. 
·Connect Sequence - Specifies the connect sequence used to establish a data switch connection with the management station's modem. Enter the sequence or click on Default to automatically generate one. 
·Default - Generates the Connect Sequence for you, based on the User Name and Password. 
NOTE: The generated sequence works for the Telebit Netblazer, AccessBuilder, and may work for other modems. Check the Control Sequence for the modem you are using. 
Logout Shows the following: 
·Disconnect Sequence - Specifies the control sequence used to terminate a data switch connection. Enter the sequence or let the modem automatically generate one. 
NOTE: A Disconnect Sequence is not required for the Telebit Netblazer and AccessBuilder. 
Configuring the Serial Port 
The serial port is already correctly configured by default for direct connection to a management station (terminal). Only alter these default settings if you are connecting a modem to the serial port. 
CAUTION: Do not change any of these settings unless you fully understand what you are doing. Incorrect settings may lock you out from the serial port of the hub when you select OK, and you will have to contact your supplier for information on recovering management communication. 
To configure the hub's serial port: 
1Double-click on part of the front panel of the device that is not a port. 
2In the General Info dialog box, choose Serial. 
3In the Serial panel (shown in Figure 2-3), enter the serial port information. 

FIG 
Figure 2-3 Serial Port Dialog Box 
NOTE: If you are unsure of the correct settings to use, refer to the manual for your terminal or modem. If you change the settings by accident, return them to their default settings. 
In the Serial dialog box: 
Serial Connection (Default - Terminal) Specifies what you are connecting directly to the serial port. If you are connecting a modem, select Modem, otherwise leave as Terminal. 
Flow Control (Default - None) Selects the flow control option that corresponds with your terminal or modem. 
NOTE: RTS/CTS Bidirectional must be selected for the modem dial-out feature to work. 
Speed (Default - 9600) Selects the baud rate for your terminal or modem. The hub can automatically configure the speed of its serial port to match that of the connected terminal or modem. To do this, select Auto Config. 
Special Features for ECS 
In addition to the device management features for the ECS described in this chapter you can: 
·Isolate a module from the backplane 
·Enable access to the ECS from other management stations 
Isolating a Module 
You can use Enterprise Manager to isolate a module from the Ethernet backplane. Repeater modules connected to the Ethernet backplane form a single logical repeater. 
To isolate or reconnect a module to the Ethernet backplane: 
1Double-click on the ECS icon to display the representation of the chassis. 
2On the ECS mimic, double-click on the module which you want to isolate. 
3In the ECS Module dialog box, select Backplanes, as shown in Figure 2-4. 
4Click Isolated to isolate the module. 
In the Ethernet Configuration panel: 
Isolated Check to isolate the selected module from the ECS backplane. 
NOTE: The ECS Management Module must be connected to the Ethernet backplane. This connection cannot be changed. 

FIG 
 
Figure 2-4 Module Isolation 
Enabling Access to Other Management Stations 
You can set up the ECS using Enterprise Manager so that other management stations can manage the ECS. This can be useful if the ECS is on a remote site and you want to allow a local SNMP-based management station to manage the ECS. 
1Select the ECS from the subnetwork view. 
2From the View menu, choose General Info. 
3Select ECS SNMP as shown in Figure 2-5. 
In the SNMP Options dialog box: 
Authentication Traps Enabled Allows you to select whether Authentication Traps are sent to the Enterprise Manager workstation. 
Secure Traps Enabled Allows you to select whether Security traps are sent to the Enterprise Manager workstation. 
OK Actions any changes. 
Cancel Abandons any changes. 
Refresh Updates the table entries in the dialog box. 
Adding an Entry 
To add a management station to the table. 
1Click Add. 
The Management Table Entry dialog box opens. 
2Type the IP address of the management station. 
3Select the access level for the management station. 
This will be one of Monitor, Secure-Monitor, Manager or Specialist. For more information about these access levels, see the guide, How to Install and Use the LinkBuilder ECS Management Module (DUA1203-0AAA0x). 

FIG 
Figure 2-5 SNMP Details Dialog Box 
Editing an Entry 
To edit an entry in the table. 
1Select the entry in the table. 
2Click Edit. 
The Management Table Entry dialog box opens. 
3Make any changes required and click OK. 
Deleting an Entry 
To delete a management station from the table. 
1Select the entry in the table. 
2Click Delete. 
Special Features for MSH 
In addition to the device management features for the MSH described in this chapter you can: 
·Display the modules connected to a backplane 
·Select the backplane connection for a module 
·Display detailed information about a module 
·Configure a Token Ring RingBuilder Module 
Displaying the Modules Connected to a Backplane 
Enterprise Manager allows you to find out which modules are connected to each of the backplanes in the MSH chassis. There are three Ethernet backplanes, five Token Ring backplanes and three FDDI backplanes. 
To display the modules connected to a backplane: 
1Double-click on the MSH icon to display the representation of the chassis. 
2On the MSH mimic, click on the selector button for the network type or on Isolated for the type of modules you want to view. 
3Select the backplane for which you want to display the connected modules from the ribbon menu to the left of the chassis. 
Enterprise Manager highlights the modules connected to the selected backplane, as shown in Figure 2-6. 

FIG 
Figure 2-6 MSH Backplane Connections 
Selecting the Backplane Connection 
You can use the Enterprise Manager to select the backplane to which a module is connected, or to isolate a module. 
To select the backplane connections: 
1Double-click on the MSH icon to display the representation of the chassis. 
2On the MSH mimic, double-click on the module for which you want to select the backplane connections. 
3In the MSH Module dialog box, select the Backplane category. 
4In the Backplane Connections panel (as shown in Figure 2-6) select the backplanes to which you want the module connected. If you do not check any of the boxes, the module is isolated from all backplanes. 
When selecting a backplane consider the following: 
Ethernet backplanes 
·The MSH Management Module can be connected to any backplane, but there must be a path between the Management Module and the PC running Enterprise Manager. 
·The 4 Port Ethernet Bridge module must be connected to all three Ethernet backplanes. 
·ECS modules can be connected to any of the backplanes, however full statistics gathering is available only for ECS modules connected to Ethernet backplane 1. 

FIG 
Figure 2-7 MSH Backplane Selection For Fast Ethernet 
Fast Ethernet backplanes (Switch 1005 only) 
·A maximum of two Fast Ethernet modules can be connected to the Fast Ethernet backplane at any one time. In third or subsequent modules the Fast Ethernet backplane option is disabled and one of the other modules must be isolated from the backplane before another can be connected. 
·Slot Path is not implemented in this release. 
FDDI backplanes 
·You cannot change the backplane connection for the FDDI 4 Port Fiber, FDDI 6 Port UTP, or FDDI RingBuilder modules as the connection is determined by a jumper link on the module. 
·If the LinkSwitch 1200 is not fitted in the MSH chassis immediately to the right of an FDDI RingBuilder module, all the check boxes are grayed out and you cannot select the backplane. 
·If the LinkSwitch 1200 is fitted immediately to the right of the RingBuilder module in the MSH chassis but the RingBuilder module is isolated, all the check boxes are grayed out and you cannot select the backplane. 
·If the LinkSwitch 1200 is fitted immediately to the right of the RingBuilder module in the MSH chassis and the FDDI RingBuilder module is not isolated, only the backplane to which the FDDI RingBuilder module is connected is available for selection. 
Token Ring backplanes 
·To form a Token Ring you must first install and configure a Token Ring RingBuilder Module. The RingBuilder builds and maintains the ring. Only one RingBuilder can be attached to a Token Ring. Until you have attached a RingBuilder to a Token Ring you cannot attach a Token Ring MAU module to that Token Ring. When attaching MAU modules to a Token Ring, any rings that do not have a RingBuilder Module present on the network are grayed out. 
·If you select a RingBuilder Module to attach to a Token Ring, you cannot connect to any rings that already have a RingBuilder Module present. Any Token Rings that already have a RingBuilder Module present on the ring are grayed out. 
·If you select a Token Ring Bridge Module you can only attach to an existing ring. A bridge can be connected to zero, one or two Token Rings. If two rings are already selected and you try to attach to a further ring, the Token Ring with the highest number is automatically disconnected and the Bridge attached to the new ring. 
Display Detailed Information About a Module 
The MSH mimic displays an accurate representation of the selected chassis, showing the types of module and (where supported) a color-coded representation of port status. Enterprise Manager also enables you to display detailed information about a selected module. 
To display detailed information about a module: 
1Double-click on the MSH icon to display the representation of the chassis. 
2On the MSH mimic, double-click on the module for which you want to display the detailed information. 
3In the MSH Module dialog box, select Information from the Categories box, as shown in Figure 2-8. 

FIG 
Figure 2-8 MSH Module Information 
In the Module Information panel: 
Description Shows a description of the module, usually stating the number of ports, media type and whether it is an Ethernet, Token Ring, or FDDI module. 
Address Shows the MAC and/or IP address of the module where appropriate. 
Software Version Shows the version number of the current module software where appropriate. 
Hardware Version Shows the version number of the module. 
Power Requirements Shows power requirement of the module in watts. 
Telnet Starts a Telnet session with the module. You can do this if the module has its own IP address and the module provides a Telnet interface. 
RMON Starts LANsentry which provides Remote Monitoring of Network devices. For further details on RMON, see Using the RMON Tools . 
NOTE: You must configure Enterprise Manager to use Telnet using the Preferences command from the File menu. 
Configuring a RingBuilder Module 
Each Token Ring network requires one RingBuilder Module to control and monitor the ring. 
To configure a RingBuilder Module and view or change the status of the Ring/Ring Out lobes: 
1Double-click on the MSH icon to display the representation of the chassis. 
2On the MSH mimic, double-click the RingBuilder Module you want to configure. 
3In the MSH Module dialog box, select Token Ring, as shown in Figure 2-9. 
4Configure Ring In, Ring Out, RingBuilder Mode and DRI values as described below. 

FIG 
Figure 2-9 MSH RingBuilder Configuration 
In the MSH Module dialog box: 
Data Rate Shows the operating speed of the Token Ring network to which this RingBuilder Module is attached. It can be one of 16Mbps, 4Mbps, 1Mbps or Unknown. The speed of the ring cannot be changed by management commands. Refer to the documentation supplied with the RingBuilder Module. 
Main Ring State Shows whether or not the main ring is communicating. See Table 2-1 for an explanation of each of these states. 
Backup Ring State This information is available if the optional MAC2 is present on the RingBuilder Module. There are two pieces of information. The first shows the state of the ring. See Table 2-1 for an explanation of each of these states. The second shows either Active or Standby. Active means that the main ring has wrapped and the backup ring is now in use. Standby means that the main ring is operational. 
 
Table 2-1    Ring State	 
Ring State	 Meaning	 
Normal	 The ring is operating normally.	 
Beaconing	 Indicates that there are beacon frames on the ring. The ring has been broken or a station thinks the ring is broken. Beacon frames are also generated when a ring station is set to operate at the wrong speed for the ring to which it is connected (i.e. 4Mbps on a 16Mps ring).	 
Soft Error	 Indicates intermittent faults that temporarily disrupt normal operation of the ring. This state can be caused by a token ring adapter entering or leaving the ring. This state should only exist temporarily.	 
Fault	 Indicates a more permanent fault. Check the station connections and any external connections to the Token Ring.	 

  
Ring In and Ring Out Let you view the status of and configure the Ring In and Ring Out lobes. You can carry out the following: 
·Enable or Isolate the Ring In/Out link. 
·Turn Fault Tolerance On or Off. This lets you set the Ring In and Ring Out lobes into different operational states. If the lobe is enabled and Fault Tolerance switched on, the lobe is set to detect a phantom current. If the phantom current is detected the lobe is set to Open. If the phantom current cannot be detected the lobe is set to Wrapped. 
·View the Media Type connected to this lobe. 
·View the Link State of the lobe. This is either Inserted or Bypassed. If the lobe has been Bypassed the external connections to the Token Ring are no longer operational. 
·View the Recovery State of the lobe. This is either OK or Auto-Isolated. 
CAUTION: Isolating main ring connections can result in loss of communication with your network management workstation. 
RingBuilder Mode Lets you select whether the RingBuilder Module is inserted into the main path of the external ring or whether it is isolated from the external ring. 
·External Ring connects the RingBuilder Module to the external ring. 
·Internal Ring isolates the internal ring from the external ring but allows the RingBuilder to provide re-timing for the external ring if connected. 
DRI Lets you view the current setting of the Distributed Recovery Intelligence (DRI) option and change it if required: 
·Off - Disables DRI. 
·On - Automatic Reset - Enables DRI and specifies that any station removed from the ring is allowed back in automatically when the error condition clears. 
·On - Manual Reset - Enables DRI and specifies that any station removed from the ring must be manually inserted by a management station. 
Special Features for LANplex and Switch 2200 
In addition to the device management features for LANplex and Switch 2200 described in this chapter you can: 
·Configure bridging 
·Display detailed information about the modules in the system 
·Display the power supply status 
An Overview of Bridging Concepts 
The following sections briefly describe the concepts of Transparent, Source Routing and Source Routing Transparent (SRT) bridging. For more information see the manuals that accompany the hardware, or contact 3Com Education Services for details on the Bridging And Routing self-study guide. 
Transparent Bridging 
An 802.1d bridge allows two or more LANs to be interconnected and to communicate as if they were one LAN. The bridge listens to packets on the attached LANs and forwards packets from one LAN to another. A packet is never transmitted onto the LAN from which it was sourced. 
Transparent bridges remain transparent to the network segments, treating them as one overall network. The main operations of a transparent bridge are learning, filtering and forwarding. These operations are IEEE 802.1 bridge features and enable it to control the flow of traffic to each network segment. 
Devices send information as frames. The two main types of frame are 802.3 and Ethernet. 
Every time the bridge receives a frame, it looks at the source address and destination address. If the bridge has not previously received a packet on that port from the device, it learns the source address by adding it to a list of device addresses connected to the port. The bridge then compares the destination address to the address lists for all the ports on the bridge. If the destination address appears on the address list of a port that did not receive the packet, the bridge forwards (duplicates) the packet to that port. If the destination address appears on the address list of the same port that received the packet, the bridge filters (discards) the packet. If the destination address does not appear on any of its address lists, the bridge passes it on to all but the receiving port, called flooding. The bridge can now effectively control network traffic by forwarding packets only to relevant network segments. 
The bridge performs ageing on address list entries. If a port has not received a packet from a device within a configured time (the ageing time), the device's address is removed from the port's address list. This helps the bridge to efficiently remember devices that communicate frequently without having to cope with devices that communicate infrequently or are no longer there. 
Because the bridge continually learns new addresses and ages out old addresses, it does not have to be reconfigured or initialized when a device is added to the network. 
Express Switching 
In Express switching mode, one of the bridge ports is designated as the backbone port. A unicast frame is forwarded from the backbone port only if the bridge has learned the destination address on another port. Conversely, a multicast frame is forwarded to the backbone port only if the destination address has not been learned on another port. As a result, there is no flooding of frames to unknown addresses. 
Source Routing 
In source routing the originating station chooses the route that a frame takes. It sets a bit called the Routing Information Indicator (RII) in each frame transmitted and also includes all the necessary information to select a route in the frame's Routing Information field. 
To start a new session, all stations use a process called route discovery. This process allows an end station to find the optimal route across the LAN to reach another station on the network. 
Route discovery is accomplished using two types of frame: spanning tree explorer (STE) frames, and all route explorer (ARE) frames. ARE frames cross all possible paths to reach a station, STE frames only take a single path. As these frames cross a bridge, the bridge adds its own bridge number and the numbers of the rings attached to it to the frame's Routing Information field. Once exploratory frames have been exchanged between the originating station and the destination station, the originating station receives frames whose Routing Information field contains enough information to allow the originating station to specify the route in subsequent frames. 
Source Routing Transparent 
When the bridge is operating as an SRT bridge it is capable of routing frames either using source routing, or transparently. The end stations attached to the bridge can only communicate if they are using the same type of routing. So an end station that uses source routing cannot communicate with an end station that is operating transparently. The bridge however processes either type of frame. 
When a frame arrives at the bridge it examines the RII bit for the frame. If this is set, the frame undergoes processing for source routing. If it is not set then the transparent routing mechanism is used instead. 
Configuring Bridging 
You can configure an Ethernet or Token Ring bridge to run in one of several different modes. 
Configuring Ethernet Bridging 
Ethernet bridge can run in either: 
·IEEE 802.1d bridging mode 
·Express Switching mode 
By default, the bridge is set to run in 802.1d bridging mode. 
Configuring Token Ring Bridging 
A Token Ring bridge can run in one of four different modes: 
·802.1d Transparent 
·802.1d SRT 
·802.1d SR 
·IBM SR 
NOTE: Token Ring Bridging is only supported in LANplex 6000 devices, it is not supported in either the Switch 2200 or LANplex 2500. Only Ethernet bridging is supported in the Switch 2200 or LANplex 2500. 
To configure a bridge: 
1Double-click on part of a bridge module that is not a port. 
2In the General Info dialog box, choose the Bridging categ1ory. 
3In the Bridging panel (shown in Figure 2-10 and Figure 2-11), configure the bridge parameters as described in the remainder of this section. 
In the Bridging panel: 
Bridge Mode Selects a bridging mode, options depend upon whether the bridge is Ethernet or Token Ring, see previous page for available modes. 
Address Table Size Shows the size of the address table for the bridge. 

FIG 
Figure 2-10 Ethernet Bridge Configuration Dialog Box 
Address Threshold Selects the reporting threshold for the total number of Ethernet addresses known to a particular switching module. When this threshold is reached, the SNMP trap addressThresholdEvent is generated. Setting the Address Threshold to greater than the Address Table Size disables the generation of addressThresholdEvent because the limit will never be reached. 
IP Fragmentation Selects whether IP fragmentation is enabled or disabled. When IP fragmentation is enabled, large FDDI packets are "fragmented" into smaller packets. This allows FDDI and Ethernet stations connected to the switch to communicate using IP even if the FDDI stations are transmitting packets that would typically be too large for the bridge. 
Multicast Limit Selects the maximum number of multicast frames per second that can be received. The default is zero, which indicates that there is no limit to the number of multicast frames. 
Bridge Backbone MAC (Ethernet modules only) When Express Switching is selected, shows the port on the module that is the backbone port. 

FIG 
Figure 2-11 Token Ring Bridge Dialog Box 
Source Route Ring Number (Token Ring modules only) Specifies the segment to which the port is connected. If you change this number then the source route ring number is updated for all Token Ring switching modules connected to the same backplane. 
Source Route Bridge Number (Token Ring modules only) Identifies the source routing bridge to which the port belongs. When a source route bridge number is assigned to one of the bridge ports on a Token Ring bridge it is propagated to all other bridge ports within that bridge. 
Token Ring Translation (Token Ring modules only) Specifies whether or not the embedded MAC addresses are byte conjugated in order to convert them from Token Ring format to native FDDI format. 
Displaying Detailed System Information 
Enterprise Manager enables you to display detailed information about a switching hub which includes the software and hardware revisions and the type and location of modules. 
To display the system information: 
1Select the switch that you want to display the system information for. 
2From the View menu, select General Info. 
3In the General Info dialog box, choose System. 
Enterprise Manager displays the System panel, as shown in Figure 2-12. 
In the System panel: 
System Software Revision Shows the revision number of the system software. 
System Hardware Revision Shows the revision number of the system hardware. 
SNMP Agent Revision Shows the revision number of the SNMP software agent. 
Current SNMP Mode Shows the current SNMP configurations for the SNMP mode. The SNMP mode will be either Single Agent or Multi-agent. 
Location Shows the number of the slot within the chassis or option module position number. 
Module Type Shows the type of module in the slot. 
Board Status Shows the status of the module. The module status will be either Not Present, Testing, Offline, Online, or Over-Temperature. 
Hardware Revision Shows the revision number of the module. 

FIG 
Figure 2-12 System Dialog Box 
Displaying the Power Supply Status 
Enterprise Manager enables you to monitor the status of the power supply and fan for a switching hub. 
To display the power supply status:1 
1Select the switch which you want to display status information for. 
2From the View menu, select General Info. 
3In the General Info dialog box, choose Status. 
Enterprise Manager displays the Status panel, as shown in Figure 2-13. 
In the Status panel: 
PSU Status Shows the status of the power supply unit(s). The status will be either OK or a combination of: 
·AC Failure 
·+5 Failure 
·+12 Failure 
·Over Temperature 
Fan Status Shows the status of the fan. The status will be either OK, Failed, or Unknown. 
Temperature Shows the system temperature as either OK, Over Temperature, or Unknown. 

FIG 
Figure 2-13 Power Supply Status Dialog Box 
Using the MIB Browser 
Enterprise Manager provides a MIB browser that enables you to view and change selected MIB object information for a device. You can use it to view and change MIB objects which are not displayed by the graphical interface. 
To display MIB object information: 
1Select the device for which you want to view or change the MIB object information. 
2From the View menu, choose MIB Tree. 
Enterprise Manager displays the MIB Tree selection dialog box, as shown in Figure 2-14. 
3In the MIB Tree selection dialog box, from the Available Groups list, select the groups of MIB objects which you want to view information for, and click Add. 
The chosen groups appear in the Selected Groups list. If you decide not to view one of the groups in the list, select it and click Remove. These groups are used for subsequent sessions unless you reconfigure the active display (see below). 
4You cannot change the Polling Status or the Polling Interval. 
5Click OK. 
Enterprise Manager displays the MIB attributes and values in the MIB Tree window, as shown in Figure 2-14. 
In the MIB Tree window, you can double-click on attributes that have the value Table Object to display a further table which provides more information about the attribute. You can change values colored magenta. 
CAUTION: You must have a good knowledge of the MIB before making any changes. Changing some values can adversely affect the performance of the device and your network. 
NOTE: The MIBs supplied with Enterprise Manager are placed into a single database, therefore the majority of MIB objects may not be supported by a device. By default, only MIB II is compiled into the database. To view the entire database, you need close down Enterprise Manager and run the batch file ALLMIBS.BAT from DOS. To view the MIB II database only, run the batch file MIB2MIBS.BAT. 

FIG 
Figure 2-14 The MIB Browser 
If you want to change the groups for which you are viewing MIB objects, select the MIB Tree window and choose Active Display Window from the Configure menu. Enterprise Manager displays the MIB Tree selection window which you can use to add or remove groups. 
Supported MIBs 
The MIBs listed in the following table are provided as part of Enterprise Manager. MIBs compiled for use with Enterprise Manager can be downloaded from 3Com Bulletin Board services. MIBs added after this guide is sent to print are listed in the Release Notes. 
 
Base MIBs	 
RFC1155.SMI - SMI items	 
RFC1212.SMI - OBJECT-TYPE macro	 
RFC1215.SMI - TRAP-TYPE macro	 
RFC1213.MIB - MIB-II	 
RFC1215.TRP - SNMP generic traps	 
RFC1229.MIB - if Extensions	 
RFC1231.MIB - Token Ring	 
RFC1243.MIB - AppleTalk	 
RFC1253.MIB - OSPF	 
RFC1271.MIB - RMON	 
RFC1284.MIB - Dot3 Ethernet-like (obsolete)	 
RFC1285.MIB - FDDI	 
RFC1286.MIB - Bridge	 
RFC1304.MIB - SMDS	 
RFC1315.MIB - Frame Relay	 
RFC1316.MIB - Character Stream Devices	 
RFC1317.MIB - RS-232 Hardware	 
RFC1318.MIB - Parallel Printer	 
RFC1354.MIB - IP Forwarding	 
RFC1398.MIB - Dot3 Ethernet-like	 
RFC1512.MIB - FDDI	 
RFC1513.MIB - Token Ring RMON	 
RFC1515.MIB - Mau	 
RFC1516.MIB - Ethernet Repeater	 
3Com MIBs	 
3COM-TEM.MIB - 3Com products MIB	 
3GENERIC.MIB - 3Com Hub MIB (FMS and MSH)	 
MSH02_10.MIB - 3Com MSH Hub	 
ECS02_30.MIB - 3Com ECS Hub	 
3C12051.MIB - 3Com ECS Bridge Line Card	 
3C12080.MIB - 3Com ECS Terminal Server Line Card	 
3C12091.MIB - 3Com ECS Remote Bridge Line Card	 
3C16640.MIB - 3Com LinkSwitch FMS & MSH	 
3C16900.MIB	 
FMS304.MIB	 
LBFDDI.MIB - 3Com FDDI WorkGroup Hub and MSH FDDI RingBuilder	 
LSVLAN.MIB	 
PRESLEY.MIB	 
RMON2_5.MIB	 
ABSRVR.MIB - 3Com AccessBuilder	 
3Com NETBuilder MIBs	 
3BRIDGE.MIB 	 
AUDL.MIB	 
DLSW.MIB	 
DVMRP.MIB	 
FILTER.MIB	 
IP.MIB	 
IP-RIP.MIB	 
IPSO.MIB	 
IPX.MIB	 
IPXPOLIC.MIB	 
LLC.MIB	 
MIP.MIB	 
PORTPATH.MIB	 
SDLC.MIB	 
SYSMIB.MIB	 
EtherLink, Token Link SoftHub and SmartAgents	 
HUB_EN.MIB	 

  
Using the BOOTP Server 
The BOOTP server allows you to automatically map an IP address to a given MAC address each time a device is started. In addition to mapping an IP address to a given MAC address, BOOTP can assign the subnet mask, default gateway and domain name server to a device. It is also possible to download machine specific information to a device to configure it on start up or to provide system resilience features. 
Using a BOOTP server avoids having to configure many devices individually. Instead you can enter the information at the Enterprise Manager workstation using the BOOTP tool. Some 3Com devices require customized boot files to enable start up and these can be invoked by correctly configuring the BOOTP server. 
The BOOTP server is installed as part of Enterprise Manager but must be started separately from Enterprise Manager. To start the BOOTP server, double-click on the BOOTP icon in the Transcend Program Group. This opens a small window with two menu options: 
·Options - This menu provides the exit command so that you can close down the BOOTP server. 
·Help - This provides on-line help. 
The BOOTP database is contained in a file called BOOTPTAB. If a device issues a BOOTP server request for which the database does not have an entry, the database must be updated. When this happens, the dialog box shown in Figure 2-15 appears. 
NOTE: BOOTP does not provide the pop-up dialog box for unknown clients that use NETBuilder BOOTP Helper extensions (see the NETBuilder Reference Guide and NETBuilder Operations Guide). Any BOOTPTAB file entries for clients that use the NETBuilder BOOTP Helper extensions must be entered manually. See BOOTPTAB Database File for more information. 

FIG 
Figure 2-15 BOOTP Pop-up Dialog Box 
Complete the fields as described below and click OK to update the BOOTPTAB file: 
Hardware Address Shows the address of the device that issued the BOOTP request. 
IP Address Type the IP address to be used by this device. 
Subnet Mask Type the appropriate subnet mask for this device. 
Default Gateway Shows the IP address of the default gateway. You should not need to modify this field. 
File Server Type the IP address of BOOTP server workstation. In this case it is the IP address of the Enterprise Manager workstation. 
Home Directory If the device uses a boot file, type the full path to the file. By default this is C:\TRANSCND\UPGRADE although you may place the file anywhere on your system. 
Boot File If the device uses a boot file, type the name of the boot file to be used. 
The default BOOTPTAB file provides support for different 3Com devices. However, you may need to edit the file directly to provide full support for some devices as the pop-up dialog box allows you only to enter a limited range of information. For information about editing the BOOTPTAB file, see BOOTPTAB Database File . You may also need to refer to the user guide supplied with the device you want to boot using the BOOTP server. 
Using the TFTP Server 
The TFTP Server allows 3Com devices on your network to access the Enterprise Manager workstation using the local management facilities to obtain new or upgraded Management Agent software. 
The TFTP server is installed as part of Enterprise Manager and is invoked when you start Enterprise Manager. However, you can also start the TFTP server independently by double-clicking on the BOOTP icon in the Transcend Program Group. This allows devices to access the Management Agent software images even when Enterprise Manager is not running. 
 3 Managing Ports 
This chapter contains the following topics: 
·What Can You Manage? 
·Viewing the Port Status 
·Configuring an Ethernet Port 
·Configuring a Switched Ethernet Port 
·Configuring an Ethernet Bridge Port 
·Configuring a Token Ring Port 
·Viewing an FDDI Port Configuration 
·Configuring Alarms for Ports 
·Setting Up Security for Ports 
·Finding the Type of Device Connected to a Port 
·Setting the Link Error Rate Thresholds 
What Can You Manage? 
The following matrix shows the port management features supported for each device. 
 
Management Features	 SuperStack II	 	 	 
	 Hub 10	 Hub 100	 Hub TR	 Switch 1000	  Switch 2200	 Switch 3000	 LinkSwitch 500	  LinkSwitch 1200	 
View the port status	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 
Configure an Ethernet port	 Ö	 Ö	 	 	 	 	 	 	 
Configure a switched Ethernet port	 	 	 	 Ö	 Ö	 Ö	 Ö	 Ö	 
Configure a Token Ring port	 	 	 Ö	 	 	 	 	 	 
View an FDDI port configuration	 	 	 	 	 	 	 	 Ö	 
Set up alarms	 Ö	 Ö	 	 Ö	 	 Ö	 	 	 
Set up security	 Ö	 	 	 Ö	 	 	 	 	 
Find the type of device connected to a port	 Ö	 Ö	 	 	 	 	 	 	 
Set the Link Error Rate thresholds	 	 	 	 	 Ö	 	 	 	 

  
Hub 10 includes: 
SuperStack II Hub 10, LinkBuilder 10BTi, LinkBuilder TP/8i, LinkBuilder FMS, LinkBuilder FMS II, LinkBuilder FMS II Bridge Management Module 
Hub TR includes: 
SuperStack Hub TR, LinkBuilder FMS TR 12/24, LinkBuilder TR Series, LinkBuilder Focus, LinkBuilder FMS TR Management Module 
Switch 1000 includes: 
SuperStack II Switch 1000, and LinkSwitch 1000 
Switch 2200 includes: 
SuperStack II Switch 2200, LinkSwitch 2200 
Switch 3000 includes: 
SuperStack II Switch 3000 FX, SuperStack II Switch 3000 TX, LinkSwitch 3000, LinkSwitch 3000TP 
NOTE: If you are managing a port using a dialog box that does not display all the fields described in this manual, it is because that particular feature is not supported for the device.

Office-
Connect
Hub/8TPM	 LinkBuilder	 LANplex 2016	 LANplex 2500	 LANplex 6000	 Management Features	 
	 FDDI WorkGroup Hub	 ECS	  MSH	 	 	 	 	 
Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 View the port status	 
Ö	 	 Ö	 Ö	 	 	 	 Configure an Ethernet port	 
	 	 	 Ö	 Ö	 Ö	 Ö	 Configure a switched Ethernet port	 
	 	 	 Ö	 	 	 Ö	 Configure a Token Ring port	 
	 Ö	 	 Ö	 Ö	 Ö	 Ö	 View an FDDI port configuration	 
Ö	 	 	 Ö	 	 	 	 Set up alarms	 
Ö	 	 Ö	 Ö	 	 	 	 Set up security	 
Ö	 	 Ö	 Ö	 	 	 	 Find the type of device connected to a port	 
	 	 	 	 	 Ö	 Ö	 Set the Link Error Rate thresholds	 

  
Viewing the Port Status 
Double-clicking on a device icon displays a new window which contains a graphical representation of the front panel of the device (which is updated every 30 seconds). Connectors such as an AUI port or transceiver module which may physically be on the rear of the device are shown on the front panel. 
 
Table 3-1   Ethernet Port Color	 
Color	 Meaning	 
Green	 Enabled and capable of repeating information to and from the network.	 
Red	 Enabled and partitioned, or enabled and link not present. Check the cabling at both the port and any devices connected to the port. Check for illegal Ethernet configurations. If the cause of the partition or link not present is corrected the port begins operating automatically.	 
Blue	 The port has been turned off either from the local management interface, or from a network management system.	 

  
 
Table 3-2   Ethernet Bridge Port Colors	 
Color	 Status	 Meaning	 
Green	 Forwarding	 When a frame is received on a bridge port, the destination MAC address is checked against entries in the filtering database. If the destination address is not listed in the filtering database, the frame is forwarded. If the destination address is listed and the destination device is on the same port as the source device, the frame is filtered. If the destination address is listed in the filtering database and the source and destination devices are on different ports, the frame is forwarded.	 
Red	 Blocking	 The bridge is only forwarding frames required by the operation of the Spanning Tree. Normal traffic is blocked to prevent more than one active path existing in the network.	 
	 Listening	 The Spanning Tree topology is changing. The bridge does not learn MAC addresses as the addresses learned at this time could be inaccurate when the topology stabilizes. The bridge only forwards frames required by the Spanning Tree to configure the topology.	 
	 Broken	 One of the bridge ports is malfunctioning.	 
Blue	 Disabled	 The bridge has been turned off either from the local management interface, or from a network management system.	 

  
 
Table 3-3   FDDI Port Colors	 
Color	 Connect State	 Meaning	 
Green	 Active	 The port is incorporated into the FDDI ring.	 
	 Standby	 The port is waiting for initialization to finish before completing the requested connection. In the case of a dual homing configuration, the A port is held in Standby while the B port is Active.	 
Red	 Connecting	 Both ends of the port's requested connection are in the process of being synchronized.	 
Blue	 Disabled	 The port has been disabled by management.	 

  
 
Table 3-4   Token Ring MAU Lobe Status	 
Color	 Admin State	 Meaning	 
Green	 Enabled	 This lobe is connected to the ring and passing data.	 
Red	 Enabled	 This lobe has detected a fault and is no longer passing data. It may or may not be connected to the ring.	 
Blue	 Disabled	 This lobe has been disabled by management.	 

  
 
Table 3-5   Token Ring Ring In and Ring Out Lobes	 
Color	 Admin State	 Meaning	 
Green	 Enabled	 Open. This lobe is connected to the ring and passing data.	 
Red	 Enabled	 Wrap. This lobe has detected a fault and is no longer passing data. It may or may not be connected to the ring.	 
Blue	 Disabled	 This lobe has been disabled by management.	 

  
 
Table 3-6   MSH Token Ring Bridge Lobes	 
Color	 Backplane Connection	 
Green	 The TR Bridge is configured to use one external and one internal connection and is filtering data between a Token Ring on the MSH backplane and an external Token Ring.	 
Blue	 The TR Bridge is configured to use two internal connections and is filtering data between two Token Rings on the MSH backplane.	 

  
Redundant Power Supply Connector colored green if operational or red if there is a fault. 
Optical Bypass Connector colored green if present or gray if not present. 
Configuring an Ethernet Port 
Enabling a port allows it to repeat information to and from the network. Disabling a port prevents it from repeating information onto the network. We recommend that you disable any unused ports to prevent unauthorized use. Do not disable the port through which Enterprise Manager is communicating with the hub. 
You can configure a port so that it sends a trap to Enterprise Manager when the status of the link changes (for example, if a device is connected to or disconnected from the port), or when the port partition state changes. You can also configure a port to store the source address of frames received by the port, this enables you to detect which devices are attached to each port of a hub. 
To configure a port: 
1Double-click on the device icon to display the representation of the hub. 
2Double-click on the port you want to configure. 
3In the Port dialog box, choose the Information category. 
4In the Port Information panel (shown in Figure 3-1), select either Enable or Disable for Port State. 
If the port is part of a resilient link, you cannot enable or disable the port. You must first delete the resilient link. For more information, see "Setting Up a Resilient Link Pair". 
5Select either Enable or Disable for Link Traps, Partition Traps, and Learn Stations. 
In the Port Information panel: 
Media Type Shows the type of media connected to the port. 
Partition State Shows whether the port is on and repeating traffic, or has been automatically isolated. If the port has partitioned check the cabling at both the port and any devices connected to the port, and check for illegal Ethernet configurations. 
Link State Shows the state of the link for fiber and twisted pair ports. 

FIG 
Figure 3-1 Ethernet Port Configuration Dialog Box 
Port State Selects whether the port can repeat information to and from the network. 
Link Traps Selects whether a trap is sent when the link state changes. 
Partition Traps Selects whether a trap is sent when the partition state changes. 
Learn Stations Selects whether the source address of received frames is learned. 
Attached Station Shows the address of the device attached to this port. 
View Port These checkboxes enable you to display statistics for the port and are described in Chapter 4. 
Configuring a Switched Ethernet Port 
You can view the current Ethernet port settings and enable or disable a port as required. 
To configure an Ethernet port: 
1Double-click on the device icon to display the representation of the device. 
2Double-click on the port you want to configure. 
3In the Port Configuration dialog box, choose the Information category. 
4In the Information panel (shown in Figure 3-2, Figure 3-3 and Figure 3-4) configure the port as required. 
Switch 1000, Switch 3000 

FIG 
Figure 3-2 Switch Port Information Dialog Box (Switch 1000, Switch 3000) 
In the Switch Port dialog box: 
Media Shows the media type of the selected port. 
Status Shows whether the port is Operational or Non-Operational. 
Port State Allows you to enable or disable the port. Disabling a port prevents data from being passed to and from other switch ports. 
Link Traps Selects whether a trap is sent if the link state changes. 
PACE Allows you to enable or disable PACE (Priority Access Control Enable) for the port. If you choose Unit Default, the PACE setting is taken from that selected as the default for the device, see "Configuring Ethernet Switching Options". 
Full Duplex (100Mbps ports only) Allows you to enable or disable full duplex operation on Fast Ethernet ports. Full duplex allows frames to be transmitted and received simultaneously and, in effect, doubles the bandwidth available on a link. Full duplex also supports 100BASE-FX cable runs of up to 2km. 
NOTE: Intelligent Flow Management will not work on a port which uses full duplex. 
VLAN Trunk Allows you to enable or disable the port from forming part of a Virtual LAN Trunk (VLT). A VLAN trunk is a link which carries traffic for multiple VLANs between switches. For more information, see "Creating a VLT". 
Intelligent Flow Management Specifies whether Intelligent Flow Management (IFM) is enabled or disabled for the port. IFM minimizes packet loss, which can occur with conventional switches. 
NOTE: IFM should be disabled if the port is connected to a repeated segment where the traffic is mainly local to that segment. 
View Port The checkboxes enable you to display statistics for the port and are described in Chapter 4. 
LinkSwitch 500, LinkSwitch 1200, 

FIG 
Figure 3-3 Switch Port Information Dialog Box (LinkSwitch 500, LinkSwitch 1200) 
In the Switch Port dialog box: 
Media Shows the media type of the selected port. 
Port State Allows you to enable or disable the port. Disabling a port does not affect traffic on the attached Ethernet segment. It simply prevents data from being passed to and from other switch ports. 
Status (LinkSwitch 500 only) Shows whether the port is Operational or Non-Operational. 
Link State (LinkSwitch 1200 only) Shows the Link State value. This can be one of the following: 
·Active - The port is enabled and the link present. 
·Inactive - The port is enabled but no traffic has been detected. 
·Ready - The port is enabled but the link is absent. 
·Disabled - The port has been disabled by management. 
·Shutdown - An error or loop condition has been detected and a shutdown has occurred. The action on loop detection can be configured. See the earlier section "Configuring Ethernet Switching Options" for more information. 
·Other - An unknown fault type has been detected. 
Broadcast Storm Filter (LinkSwitch 1200 only) If this is enabled, multicast frames are filtered if they exceed a specified rate avoiding broadcast storms. 
Switch 2200, LANplex 2016, LANplex 2500, LANplex 6000 

FIG 
Figure 3-4 Switch Port Information Dialog Box (Switch 2200 and LANplex) 
In the Switch Port dialog box: 
Label Enables you to enter text as a label for the port. Labels can serve as a useful reference point and as an accurate means of identifying your ports for management. 
Media Type Shows the media type of the selected port which include: Twisted Pair, Fiber, BNC or AUI. 
Status Shows if the port is Operational (connected and passing data) or Not Operational (not passing data). 
Multicast Limit Displays and enables you to change the maximum number of Multicast frames that can be received per second by the port. 
Router IP Addr Displays and enables you to change the subnet address for the port when the port is used for routing. 
Subnet Mask Displays and enables you to change the subnet mask for the port when the port is used for routing. 
Port State Allows you to enable or disable the port. Disabling a port does not affect traffic on the individual Ethernet segment. It prevents data from being passed to and from other Ethernet segments and to and from the FDDI ring. 
View Port These checkboxes enable you to display statistics for the port and are described in Chapter 4. 
Configuring an Ethernet Bridge Port 
Enabling a bridge port allows it to transmit and receive information to and from the network. Disabling a bridge port prevents it from transmitting or receiving information. To configure the bridge port: 
1Double-click on the FMS-Bridge icon to display a representation of the FMS unit fitted with the FMS II Bridge/Management Module. 
2Double-click on the bridge port. 
3In the FMS Bridge Port Status dialog box, select either Enable or Disable for Port State. 
In the FMS Bridge Port Status dialog box: 
Spanning Tree Shows whether the spanning tree protocol is running. The Spanning Tree protocol determines how the bridge reacts in the event of a loop being detected. 
Learning Mode Shows whether the bridge is learning addresses of devices sending information on the network. 
Age Entries Shows whether entries in the filtering database are deleted after the ageing period. 
Ageing Period Shows the period after which entries in the filtering database are deleted. 
Internal Port Status/External Port Status Shows the port status as defined by the spanning tree protocol. 
Port State Selects whether the bridge port can transmit or receive information to and from the network. 
The above parameters can be changed through local management. 
Configuring a Token Ring Port 
You can configure the status and some parameters for Token Ring ports on Hub TR series hubs. You may see different dialog boxes, depending on the device you wish to view, but the functions are the same. You can also configure Token Ring ports on a LANplex 6000 Token Ring Switching Module (TRSM) by referring to Device Manager for the LANplex 6000. 
We recommend that you disable any unused ports to prevent unauthorized use. Do not disable the port through which Enterprise Manager is communicating with the device . 
In addition to the device management features for the Hub TR described in Managing Devices, you can: 
·Configure Token Ring hubs 
·Configure Token Ring stations 
Configuring Token Ring Hubs 
Transcend allows you to configure parameters and gather information about your 3Com token ring hubs. To accomplish this the application provides a series of Category dialog boxes that you access through the Hub Info and Control dialog box. Hub Info and Control is the default dialog box that appears when you double click in the Hub Expansion view. These Category dialog boxes are located on the left side of the window and include the following: 
·Hub Controls (Token Ring) 
·Cascade Controls (Token Ring) 
·Main Ring Controls (Token Ring) 
Hub Expansion View 
The Hub Expansion view (Figure 3-5) is found directly "below" the Stack view in the network hierarchy. This level provides direct access to the stations by bringing you closer to the attached devices. This view also provides access to the controls and configuration parameters of each hub and each station. This view displays a graphical representation of the hub and the attached devices. A color-coded box above each device displays the current status and corresponds to the color-code of the ports on the front panel of the hub. 
This view also provides access directly to the devices via the Station Information dialog box. 
To view the hub, proceed as follows from the Stack View: 
1Select the hub you wish to view. 
2Double click on the left mouse button. 
The Hub Expansion view appears. See Figure 3-5. 

FIG 
Figure 3-5 Sample Hub Expansion View 
The device/station icons illustrate the types of devices attached to the hub and display the port number and the address/name of the port. 
You can scroll through the attached devices by clicking on the left-right scroll bar located at the bottom of the window. The devices increment/decrement as you click left and right. 
3Select Close from the action box in the upper left corner of the screen to close the Hub Expansion view or Next to return to Stack view. 
You may also resize the view by minimizing or maximizing. 
Interpreting Station States 
Refer to the following list for determining the status of the stations. 
·Green (Enabled) - active and operational. 
·Red (Disabled) - partitioned via management software or hardware. 
·Gray (Inactive) - inactive and not operational. 
·Blue (Isolated) - isolated via management software. 
The state of the port corresponds directly to the state of the station. For example: if Port 5 is disabled (yellow) on the front panel of the hub, station 5 displays red in the expanded view. 
Viewing Hub Info And Control Dialog Box 
The Hub Info and Control dialog box appears by default whenever you either select Hub Info from the Tools menu or invoke it by clicking on the Hub Expansion view. This dialog box reports the type of hub and allows you to assign a name and record other information of the selected hub. To view the Hub Info and Control dialog box, proceed as follows: 
1Select the hub you wish to view from the Stack view or via the Agent Selection dialog box. 
2Click once with the right mouse button while pointing at the stack or select Hub Info from the Tools menu. 
The Hub Info and Control dialog box appears and displays the network address, name of the default agent for the stack, and type of hub. 
3Click OK to return or Cancel to cancel. 
NOTE: When you view the Hub Info and Control dialog box using this method, the default agent for the stack appears. However, if you need to view a specific agent in a stack you will have to find that agent (using a network address - IP or IPX - and the Agent Selection dialog box) and then invoke the Hub Info and Control box. 
Naming Your Hub 
The name field remains blank unless you choose to name your hub. The Hub Type field automatically displays the type of hub you have selected and uses that information to identify the hub with the network address. 
The Hub Notes field allows you to enter information about the hub. The default Hub ID number and the Unit number appears on the top menu bar of the Hub Info and Control dialog box. See Figure 3-6. 
To name your hub, proceed as follows: 
1Position the mouse pointer in the Hub Name field. 
2Enter a name for the hub. 
3Position the mouse pointer in the Hub Notes field to enter information about the hub. 
4Click OK to confirm your settings or Cancel to cancel. 

FIG 
Figure 3-6 Hub Info and Control Dialog Box 
Viewing the Hub Controls Dialog Box 
The Hub Controls dialog box appears when you select it from the scrollable Category list on the left side of the Hub Info and Control dialog box. See Figure 3-7. This dialog box allows you to configure the following: 
·Data Rate (4 or 16 Mbps) controls 
·Distributed Recovery Intelligence (DRI) controls. See "Setting Distributed Recovery Intelligence" Beacon Recovery (ZDL and DRI). 
·DRI Status and reset controls 
To view the Hub Controls dialog box, proceed as follows: 
1Select Hub Controls (Token Ring) from the scrollable Category list on the left side of the Hub Info and Control window. 
The Hub Controls dialog box appears. 
2Refer to the following instructions for setting parameters or click OK to return or Cancel to cancel. 
.
FIG 
Figure 3-7 Hub Controls Dialog Box 
Setting the Data Rate 
From the Hub Controls dialog box set the data rate as follows: 
1Select the Hub Controls icon from the scrollable Category list. 
The Hub Controls dialog box appears. 
2Select the data rate for the network (4 Mbps or 16 Mbps). 
NOTE: All hubs in the token ring must be set to the same data rate. Also note that changing the data rate of a Hub TR invokes the DRI feature (Beacon Recovery). This isolates all attached stations because they are seen as being set at the wrong speed. This also stops management communications. Manually set the speed of the hub on the front panel. 
3Click OK to change or Cancel to retain the data rate. 
Setting Distributed Recovery Intelligence 
The Distributed Recovery Intelligence (DRI) feature isolates hard errors (i.e. beaconing adapters) generated by stations attached to the token ring. This feature is a fault prevention tool that guarantees the integrity of the ring by eliminating potential downtime caused by faulty or misconfigured adapters. Zero Delay Lockout (ZDL) isolates nodes immediately upon sensing a misconfigured or faulty connection. This prevents the faulty node from disrupting the network beaconing errors. 
To set DRI, proceed as follows from the Hub Control dialog box: 
1Select the DRI setting you wish from the DRI Control State field: 
·Off - DRI is not operational. 
·On - Automatic Reset - DRI is on and ports reset after problem is resolved. 
·On - Manual Reset - DRI is on and ports can only be reset manually by enabling port or selecting ON-Automatic. 
2Click the appropriate button to select or deselect. 
3Click OK to set or Cancel to cancel. 
DRI Status 
The DRI Status field appears adjacent to the DRI Control State field. This field provides the following information: 
·In-recovery - DRI recovering from a fault situation. 
·Normal - DRI on and operating normally. 
·Halted - DRI halted and problem not isolated. 
DRI Reset 
The DRI Reset box provides a check box control for resetting DRI. To reset the DRI feature, proceed as follows from the Hub Controls dialog box: 
1Position the mouse pointer over the DRI Reset check box. 
2Click to select or deselect. 
3Click OK to set or Cancel to cancel. 
Setting the Cascade Controls 
The Cascade Controls dialog box allows you to enable or disable a token ring hub's cascade connection. See Figure 3-8. The cascade connection provides continuity and management between attached hubs. This dialog box allows you to configure the cascade ports to suit your workgroup's needs and provides status information. 
·Cascade Up Port allows you to enable or disable the Up cascade link. The corresponding Link Status field displays the current setting for the Up link. 
·Cascade Down Port allows you to enable or disable the Down cascade link. The corresponding Link Status field displays the current setting for the Down link. 
To set the Cascade Controls, proceed as follows from the Hub Info and Control dialog box: 
1Select the Cascade Controls icon from the scrollable Category list. 
The Cascade Controls dialog box appears. See Figure 3-8. 
2Position the mouse pointer over the Enable or Isolate button in the Cascade Up or Down Port field to enable or isolate the up or down cascade connection. 
3Click OK to set or Cancel to cancel. 

FIG 
Figure 3-8 Cascade Controls Dialog Box 
Link Status 
The Link Status field displays the current status of the Up and Down Cascade ports. This is a display-only field and cannot be changed. The status displays one of the following: 
·Inserted - cascade cable inserted and port is active. 
·Bypassed - cascade port bypassed via hub (i.e. no cable connected). 
·Isolated - cascade port isolated via management software or hardware. 
Setting the Ring In/Ring Out Ports - Main Ring Controls 
The Main Ring Controls dialog box (Figure 3-9)is a token ring-only dialog box that allows you to extend the size of the ring by adding more hubs and ports using the Ring In (RI)/Ring Out (RO) capability. In addition, this box also displays the current status of the link. The default is Enable for both Ring In and Ring Out. 
·The Ring In Link button allows you to enable or isolate the Ring In link. The Link Status field displays the current status of the Ring In link. 
·The Ring Out Link button allows you to enable or disable the Ring Out link. The Link Status field displays the current status of the Ring Out Link. 
To set the Ring In/Ring Out ports, proceed as follows from the Hub Info and Control dialog box: 
1Select the Main Ring Controls dialog box in the scrollable Category list. 
2Click once with the left mouse button. 
The Main Ring Controls dialog box appears.
FIG 
Figure 3-9 Main Ring Controls Dialog Box (Ring in/Ring Out) 
3Position the mouse pointer over the Enable or Isolate button in the Ring In or Ring Out Link field to enable or isolate the Ring In or Ring Out connection. 
The default setting is Enable for both. 
4Set the Fault Tolerance (Phantom Current) to On or not. 
5Click OK to set or Cancel to cancel. 
Configuring Stations 
This section details the steps required to configure stations. The configuration parameters are then stored as part of a permanent database. 
Assigning Station Addresses 
Each station must be assigned an identifiable address. Note that the application displays the MAC address of the device automatically. However, since these addresses are cumbersome to remember and trace, it is best to enter a more easily recognizable address. 
Addresses are stored in a database that serves as a permanent record of the attached stations and provides a quick means for accessing stations using the Find tool. Assign station addresses via the Station Information dialog box. To establish addresses from the Hub Expansion view, proceed as follows: 
1Select the station you wish to configure. 
2Double click with the left mouse button. 
The Station Information dialog box appears.
FIG 
Figure 3-10 Station Information Dialog Box 
3Enter the type of address you wish from the following choices: 
·MAC Address - a read-only field of the station's MAC address. The MAC address is provided by querying the hub's agent, which in turn supplies the address of the station. The addresses are updated periodically or can be manually updated by selecting Update from the Tools menu. This field cannot be edited, but you can remove it by pressing the Clear Address button. MAC addresses are the default. 
·IP Address - displays the station's IP address. After an address has been assigned, Transcend updates this field automatically. The Update function from the Tools menu will also update the address. Address mapping is the primary responsibility of the stack's agent. However, the NMS database will also provide this information. 
·NetWare Name - displays the station's NetWare User Name. Transcend application attempts to discover the Netware name of the station automatically and displays it in this field. The Update function from the Tools menu will also update the address. Address mapping is the primary responsibility of the stack's agent. 
·User-provided Name - a user-editable field for applying names to the selected station. 
4Click OK to confirm the address or Cancel to deny and return to the Hub Expansion view. 
The Save Changes window appears and prompts you to either save the address changes you have made or not (Yes or No). 
5Press Yes to save changes or No to deny. To view other ports, click on the port traverse buttons in the upper left corner of the dialog box. Refer to "Traversing Ports". 
Setting Station Parameters 
The Station Configuration dialog box provides access to specific configuration parameters of the selected station. Using this dialog box you can do the following: 
·Assign an icon to the station. 
·Choose address mapping. 
·Isolate/enable station port. 
To configure the above parameters, proceed as follows from the Hub Expansion view: 
1Select the station you wish to configure. 
2Double click with the left mouse button. 
The Station Information dialog box appears. 
3Select the Station Configuration icon from the scrollable Category list. 
The Station Configuration dialog box appears. See Figure 3-11. 

FIG 
Figure 3-11 Sample Station Configuration Dialog Box 
4Set the parameters you wish to configure. 
5Click OK to confirm the settings or Cancel to deny and return to the Hub Expansion view. To view other ports, click on the port traverse buttons in the upper left corner of the dialog box. Refer to "Traversing Ports". 
Selecting a Device Icon 
Each station or device on the network can be associated with a corresponding icon. The icons allow you to identify the devices quickly. To select an icon for a device, proceed as follows from the Hub Expansion view: 
1Select the station you wish to configure. 
2Double click on it with the left mouse button. 
The Station Information dialog box appears. 
3Select the Station Configuration icon from the scrollable Category list. 
The Station Configuration dialog box appears. 
4Position the mouse pointer over the drop-down menu list under the Station Icon Selection field. 
5Select a station icon from the following drop down menu list: 
·Mini 
·NetWare Server 
·PC 
·Print Server 
·Router 
·Uplink 
·Workstation 
6Drag and release to select icon. 
7Click on Change Icon button to change icon. 
The icon changes in the Station Icon Selection field and on the station. You can change this field as often as you wish, since no changes will take effect until you click on the OK button. To view other ports, click on the port traverse buttons in the upper left corner of the dialog box. 
8Click OK to set or Cancel to return to the Hub Expansion view. 
Isolating Hub Ports 
To isolate a hub port, proceed as follows from the Hub Expansion view: 
1Select the station you wish to configure. 
2Double click with the left mouse button. 
The Station Information dialog box appears. 
3Select the Station Configuration icon from the scrollable Category list. 
The Station Configuration dialog box appears. 
4Click to select as follows: 
·Enable - port is active, part of the network. 
·Isolate - port is inactive, not part of the network. 
5To view other ports, click on the port traverse buttons in the upper left corner of the dialog box. 
6Click OK to set or Cancel to return to the Hub Expansion view. 
Setting Station Auto Mapping 
Station Auto Mapping allows you to select or deselect automatic address mapping for MAC addresses. To change the address auto mapping, proceed as follows from the Hub Expansion view: 
1Select the station you wish to configure. 
2Double click with the left mouse button. 
The Station Information dialog box appears. 
3Select the Station Configuration icon from the scrollable Category list. 
The Station Configuration dialog box appears. 
4Check the Station Auto Mapping to automatically map the MAC address. 
5To view other ports, click on the port traverse buttons in the upper left corner of the dialog box. Refer to "Traversing Ports". 
6Click OK to set or Cancel to return to the Hub Expansion view. 
Traversing Ports 
You can switch ports at any time by using the port traverse buttons. To change ports, proceed as follows: 
1Select the appropriate port traverse button. 
The left arrow decrements the port number and stops at 1 (turns red). 
The right arrow increments the port number and stops when it reaches the highest port number (turns red). 
2Click once to increment/decrement the port number by one. 
The information in the dialog box title bar changes to reflect the current port. 
LinkBuilder Focus and LinkBuilder TRi models 
1Double-click on the device icon to display the representation of the unit. 
2Double-click on the port you want to configure. 
3In the Token Ring Port dialog box (shown in Figure 3-12 and Figure 3-13), choose the Information category. 
4Configure the port as required. 
In the Information panel for a port: 
Ring In Isolated/Enabled Toggle Button Shows the current state of the Ring In link and lets you isolate or enable the Ring In link. Click the button to toggle the state. The new status is displayed as soon as the device responds. 
Ring Out Isolated/Enabled Toggle Button Shows the current state of the Ring Out link and lets you isolate or enable the Ring Out link. Click the button to toggle the state. The new status is displayed as soon as the device responds. 
Lobe n Isolated/Enabled Toggle Button Lets you isolate or enable the current port. Shows the current state of the lobe. Click the button to toggle the state. The new status is displayed as soon as the device responds. 
Cascade Up Isolated/Enabled Toggle Button Lets you isolate or enable the Cascade Up link (FMS TR devices only). Shows the current state of the Cascade Up link. Click the button to toggle the state. The new status is displayed as soon as the device responds. 
Cascade Down Isolated/Enabled Toggle Button Lets you isolate or enable the Cascade Down link (FMS TR devices only). Shows the current state of the Cascade Down link. Click the button to toggle the state. The new status is displayed on the next ports cycle after the device responds. 
CAUTION: Isolating ports, main ring connections, or modules may result in a loss of communication with Enterprise Manager. 
You can view the configuration dialog box for the previous port by clicking the left-arrow next to the current lobe number. You can view the configuration dialog box for the next port by clicking the right-arrow next to the current port number. 

FIG 
Figure 3-12 Hub TR Port Configuration 
Ring In Fault Tolerance On/Off Toggle Button Lets you turn fault tolerance on or off for the Ring In link. (This can also be done using the front panel switch on the module.) 
Ring Out Fault Tolerance On/Off Toggle Button Lets you turn fault tolerance on or off for the Ring Out link. (This can also be done using the front panel switch on the module.) 
Fault tolerance refers to a process whereby a phantom current signal is superimposed on the RI/RO links to speed the detection of cable faults. If this process detects a fault, the RI/RO link is automatically partitioned in order to maintain the integrity of the ring data path. Fault tolerance should be set to On for RI/RO links bounded by 3Com equipment at both ends of the link. Fault tolerance should be set to Off for links that attach to non-3Com equipment at the other end. 
Backplane Inserted/Bypassed Toggle Button Lets you logically insert or bypass the backplane. 
CAUTION: Bypassing the backplane may result in a loss of communication with Enterprise Manager. 
Data Rate Toggle Button Lets you set the data rate to 4Mps or 16Mps. 
CAUTION: Altering the ring data rate setting for a managed hub may cause a loss of in-band management communications. 
Distributed Recovery Status Shows, to the right of the label Status: the module's state of Distributed Recovery Intelligence (DRI). Normal indicates that no problem has been detected to cause the module to go into Distributed Recovery state. In Recovery indicates that the module has entered this state. Halted indicates that the problem could not be fixed. 
Click on the Reset button to return to Normal state from the Halted state after you have fixed the problem that caused the module to enter Distributed Recovery state. 
The following DRI controls are available: 
OFF Disables DRI. 
ON (Automatic Reset) Enables DRI and specifies that any station removed will be allowed back in automatically when Phantom Current is removed. 
ON (Manual Reset) Enables DRI and specifies that any station removed must be manually reset by a management station before it is allowed back in. 
MSH Token Ring Module 
In the Information panel for an MSH Token Ring module port: 
Lobe State Allows you to Enable or Isolate the port. 
Fault Tolerance Allows you turn Fault Tolerance On or Off. Fault Tolerance is a process where a phantom current signal is superimposed on the link to speed the detection of cable faults. If this process detects a fault, the link is isolated. We recommend that Fault Tolerance is turned on where 3Com equipment is installed at both ends of the link, and turned off for links that attach to non-3Com equipment. 
Media Type Shows the type of media attached to the port. 
Connection State Shows whether the port is inserted into the ring or bypassed. 

FIG 
Figure 3-13 MSH Token Ring Port Configuration 
Recovery State Shows one of the following: 
·OK if the link is functioning normally or has been disabled by management. 
·Auto-Isolated (by DRI) when DRI is enabled on the RingBuilder Module and a fault has been detected at this port. 
·Auto-Isolated (by ZDL) when Fault Tolerance is turned on and a fault has been detected. 
Station Shows whether or not there is a powered station connected to this lobe. Request Insertion indicates that there is a powered station. Offline indicates that the station is not powered or not connected. 
LANplex 6000 Token Ring Switching Module (TSRM) 
In the Information panel for LANplex 6000 Token Ring Switching Module port: 
Label Enables you to enter text as a label for the port. Labels can serve as a useful reference point and as an accurate means of identifying your ports for management. 
Media Type Shows the media connected to the port. 
Insert Status Shows the link status for the port. This will be either Inserted or Deinserted. 
Port State Allows you to enable or disable the port. 
Port Mode Allows you to select either lobe or station. 
Port Speed Allows you to select the speed at which the port is operating. The available values are: 
·4Mb/s 
·16MB/s 
·16MB/s Early Token Release 
MAC Address Shows the physical address of the Token Ring interface. 
Receive Multicast Limit Allows you to choose the maximum number of Multicast frames that can be received per second by the port. The default value is 0, which means there is no limit on the number of Multicast frames. 
Source Routing Ring Number When Source Routing is enabled, a unique Ring number and Bridge Ring number must be assigned to each ring segment. Each TRSM has a common Source Route Bridge number which should be used as the ring number for ports. The default Bridge number is the same as the slot number that the TRSM resides. 
Viewing an FDDI Port Configuration 
Enterprise Manager enables you to view information about each FDDI port connection. 
To view FDDI port information: 
1Double-click on the device icon to display the representation of the unit. 
2Double-click on the FDDI port for which you want to display information. 
3In the FDDI Port dialog box, choose the Information category. 
In the FDDI Port Configuration dialog box (shown in Figure 3-14): 
Media Type Shows the media connected to the selected port. This can be one of the following: Fiber (Multimode), Fiber (Single-Mode1), Fiber (Single-Mode2), Fiber (Low-Cost), Unshielded Twisted Pair, Shielded Twisted Pair, or Unknown. 
Label Enables you to enter text as a label for the port. Labels can serve as a useful reference point and as an accurate means of identifying ports for management. 
Status Shows the current state of the selected port. This can be Active, Connecting, Disabled or Standby. 
PCM State Shows the physical connection management state. See Table 3-7 for an explanation of these states. 
PHY Type Shows the physical port type. See Table 3-8 for an explanation of each of these types. 
Neighbor Type Shows the physical port type of the neighboring port when the PCM State is Active. 
Port State (LinkSwtich 1200 and FDDI WorkGroup Hub only) State Allows you to enable or disable the port. 
Path (LANplex 2016, 2500, 6000 only) Shows the path for the port. 

FIG 
Figure 3-14 FDDI Port Configuration Dialog Box 
 
Table 3-7   PCM State	 
PCM State	 Meaning	 
Active	 This port is incorporated into the ring.	 
Break	 This state is the starting point for establishing a connection either when the system is powered on, the port is explicitly enabled or the port is no longer Active (such as in the case of a broken connection).	 
Connecting	 In the Connect state, the port is preparing to send connection information.	 
Join	 The information exchange between ports has been completed and the port and its neighbor can enter the Active state together.	 
Maintenance	 The port has been put into the Maint state by management. This state is used to help diagnose PHY-level ring problems.	 
Next	 The port is sending connection information to its neighboring port.	 
Off	 The port has been disabled by management.	 
Signal	 The port is receiving connection information from its neighboring port.	 
Trace	 The port is suspected of being part of a fault domain and is participating in the ring trace function to help detect the location of the fault. This state helps diagnose MAC-level ring problems.	 
Verify	 The port is in the process of entering the Active state.	 

  
 
Table 3-8   PHY Type	 
PHY Type	 Meaning	 
A	 The port in a dual attachment station or hub that attaches to the Primary In and the Secondary Out when attached to a dual ring.	 
B	 The port in a dual attachment station or hub that attaches to the Secondary In and the Primary Out when attached to a dual ring.	 
M	 A port in a hub that serves as a Master to a connected station or hub.	 
S	 A port in a single attachment station or hub designated as a Slave. A Slave port is attached to a Master port within a concentrator tree.	 
Unknown	 (Neighbor ports only) The exchange of connection information with the neighboring port has not been completed and the PHY type has not yet been identified.	 

  
Configuring Alarms for Ports 
Alarms are simple to configure and can be easily modified using Alarm Manager. They can be used to enhance your network performance and prevent network downtime. 
Alarms can be configured for the whole device, or for individual ports. How alarms work, how they can help you prevent problems on your network, and the alarm management dialog boxes are fully described in "Working with Alarms" on page 1-53. 
To access Alarm Manager to configure alarms for a specified port: 
1Double-click on the device icon to display the bitmap of the unit. 
2Double-click on the port for which you want to configure alarms. 
3In the port configuration dialog box, select the Alarms category. 
The Assigned Alarms list is automatically filtered so that only the alarms for the specified port are displayed (as shown in Figure 3-15). 

FIG 
Figure 3-15 Alarm Manager Dialog Box 
Setting Up Security for Ports 
The security features provided allow you to protect sensitive information on your networks and prevent unauthorized use of the network. You can set up security features for a whole device, or just for particular ports. 
There are two main ways of protecting your network. 
·Disconnect Unauthorized Device (DUD) - also known as Disable on Intrusion 
·Need to Know (NTK) - also known as Data Privacy 
You can set up Disconnect Unknown Device and Need to Know using WorkGroup Manager on the following devices: 
·SuperStack II Hub 10 (running management agent version 3.0 or later) 
·SuperStack II Switch 1000 
·OfficeConnect Hub/8TPM 
For Hub 10's running earlier versions of their management agents, and for LinkBuilder TP/8i, a subset of the security features described in this section is available on a per-port basis only. 
Setting up security for a whole device and how security works is fully described in "Setting Up Security" on page 1-63. 
To configure security for an individual port: 
1Double-click on the device icon to display the bitmap of the switch. 
2Double-click on the port for which you want to configure security. 
3In the Port Configuration dialog box, select the Security category. 
The Security Configuration dialog box shown in Figure 3-16 is displayed. 

FIG 
Figure 3-16 Security Configuration Dialog Box for a Port. 
Authorized Addresses Shows the following: 
·No. of Addresses - Displays the number of addresses that can be authorized for this port. The list below it shows any addresses already configured for this port. 
·MAC Address - Allows you to enter the MAC address for a device to be authorized to transmit to this port. When you have typed the MAC address, click on Add. Use the format xx-xx-xx-xx-xx-xx for the MAC address. 
·- Adds the MAC address to the Authorized Address list. 
·Remove - Removes selected addresses from the Authorized Address list. 
Disconnect Unknown Device Allows you to configure the learning and security mode of the selected port(s). 
·No Restriction - Disables all security and learning features. 
·Continually Learn - All addresses transmitting to this port are valid and are stored in the port address table. 
·Full Security - Learning is disabled and only the address entered as a valid address for this port is allowed to transmit to this port. 
·Auto Learn - The port learns the MAC address(es) of the devices transmitting to this port and stores them permanently in its address table. The maximum number of addresses learned by the port(s) is determined by the value shown in the No. of Addresses field. Once the table is full, the port automatically switches to Full Security mode. 
·Disable on Intrusion - Compares the source address of a frame received on the port to the authorized address(es) of the device(s) attached to it. If the source address of the incoming frame does not match an authorized address for this port, the port is disabled. 
·No. of Addresses - Shows the number of addresses that can be authorized to transmit to this port and stored in the address table. 
Need To Know Allows you to configure which frames are forwarded to the selected port(s). These options are grayed out if the port does not support configurable NTK. 
·Disabled - All frames are forwarded. 
·Enabled - The port examines the destination address of the frame. If it matches an authorized address for the port it is forwarded. If it does not, it is discarded. 
·Allow Broadcasts - In addition to Enabled, allows broadcast frames to be transmitted to the port. 
·Allow Broadcasts and Multicasts - In addition to Enabled, allows broadcast and multicast frames to be transmitted to the port. 
NOTE: The Switch 1000 implements permanent Need To Know because it only passes data to a port on which the addresses device resides. Therefore, Need To Know parameters are not configurable on the Switch 1000. 
When you click on OK, the operation may fail for one of the following reasons:
- The operation has timed out.
- Invalid MAC address (i.e. Multicast or Broadcast address)
- Duplicate address on another port.
If the address is on another port already and DUD set to Full Security or Autolearn, you must remove the address from the other port before assigning it to the current port. 
Finding the Type of Device Connected to a Port 
Enterprise Manager enables you to build a detailed picture of the devices on your network by providing detailed information about the devices connected to a port. Enterprise Manager gathers this information from a PC Link SmartAgent on the same subnetwork as the port. If the subnetwork does not contain a PC Link SmartAgent, you cannot access this information. To find out more about the PC Links SmartAgent, refer to the Transcend PC Link SmartAgent Software User Guide. 
You can find the type of device connected to a port either from the device or port level General Info. At Device level all devices attached to all ports are listed. At port level only the devices attached to that port are listed. 
Port Level Listing 
To find the type of device connected to a port. 
1Double-click on the device icon to display the representation of the device. 
2Double-click on the port for which you want to find the type of connected device. 
3In the Port dialog box, select End Station from the Categories box. 
4In the Attached Station panel (shown in Figure 3-17), click on PC Info. 

FIG 
Figure 3-17 Attached Station Information 
Device Level Listing 
To find the type of devices connected to a device's port. 
1Double-click on the device icon to display the representation of the device. 
2From the View menu, select General Info. 
3In the General Info dialog box, select Stations from the Categories box. 
4In the Attached Station panel (shown in Figure 3-18), click on PC Info. 

FIG 
Figure 3-18 Attached Stations Information 
In the Attached Station panel: 
Last Station Address Shows the MAC address of the last device attached to the port. This field is only applicable if you obtained the information by double-clicking on a port. 
Attached Station Changes Shows the number of times the device attached to the port has changed. This field is only applicable if you obtained the information by double-clicking on a port. 
Station Information Shows the type of device, CPU size and speed, memory size, operating system and version for device connected to the port. If nothing can be learned about the end station, the message No information is displayed. 
The View Station Congestion check box is described in "Using the Congestion Monitor". 
Setting the Link Error Rate Thresholds 
The Link Error Rate (LER) measures the quality of the link on an FDDI port. You can configure a switch to issue an alarm or disable a port if the (LER) for the port rises to an unacceptable level. 
The LER alarm threshold and the LER cut-off threshold are configured by setting the value of the exponent. The default exponent for the LER alarm is 8, which is a threshold of 10-8, that is, an alarm is generated if the Link Error Rate is more than 1 error in 10, 000,000. The default exponent for the LER cut-off is 7, which is a threshold of 10-7, that is, the connection is broken if the Link Error Rate is more than 1 error in 1,000,000. 
You should increase the exponents for the LER alarm threshold and LER cut-off threshold if the link between stations must handle higher error levels. You may need to do this if you are waiting for minor unit or cable repairs but the FDDI ring is still operational. You can decrease the exponents if you are confident of the quality of the link. 
You must always keep the exponent for the LER alarm threshold greater than the exponent for the LER cut-off threshold. 
To set the Link Error Rate thresholds: 
1Double-click on the switch icon to display the representation of the switch. 
2Double-click on the FDDI port for which you want to set the LER thresholds. 
3In the FDDI Port dialog box, choose the Link Errors category. 
4In the Link Errors panel (shown in Figure 3-19) increase or decrease the values for the LER Alarm and LER Cut-off as required. 

FIG 
Figure 3-19 Link Errors Dialog Box 
In the Link Errors dialog box: 
LER Estimate Shows the long-term average Link Error Rate for the port. 
LER Alarm Selects the error rate at which an alarm is issued. Increasing the value in this field increases the number of errors per second that are allowed before an alarm is issued. 
LER Cut-off Selects the error rate at which the port is disabled. Increasing the value in this field increases the number of errors per second that are allowed before the port is disabled. 
 4 Device and Port Statistics 
This chapter contains the following topics: 
·What Statistics Can You View? 
·Activity and Error Statistics 
·Frame Type Statistics 
·Network Traffic Statistics 
·Network Error Statistics 
·Bridge Filtering Statistics 
·Switching Statistics 
·Using the Congestion Monitor 
·Using the RMON Tools 
·Using the Network Analyzer Tool 
·Using the Traffic Matrix Tool 
·Using the Network History Tool 
·Using the Packet Capture Tool 
What Statistics Can You View? 
The following matrix shows the statistics supported for each device. 
 
Statistics	 SuperStack II	 	 	 
	 Hub 10	 Hub 100	 Hub TR	 Switch 1000	  Switch 2200	 Switch 3000	 
LinkSwitch 500	  LinkSwitch 1200	 
Activity and errors	 Ö	 Ö	 Ö	 	 	 	 	 	 
Frame types	 Ö	 Ö	 	 	 	 	 	 	 
Network traffic	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 Ö	 
Network errors	 Ö	 Ö	 Ö	 	 	 	 	 	 
Bridge filtering	 Ö	 	 	 	 	 	 	 	 
Switching	 	 	 	 Ö	 Ö	 Ö	 Ö	 Ö	 
Port congestion	 Ö	 Ö	 	 	 	 	 	 	 
RMON tools	 Ö	 	 	 Ö	 	 Ö	 	 	 
Network analyzer tool	 	 	 Ö	 	 	 	 	 	 
Traffic matrix tool	 	 	 Ö	 	 	 	 	 	 
 
Network history tool	 	 	 Ö	 	 	 	 	 	 
Packet capture tool	 	 	 Ö	 	 	 	 	 	 

  
Hub 10 includes: 
SuperStack II Hub 10, LinkBuilder 10BTi, LinkBuilder TP/8i, LinkBuilder FMS, LinkBuilder FMS II, LinkBuilder FMS II Bridge Management Module 
Hub TR includes: 
SuperStack Hub TR, LinkBuilder FMS TR 12/24, LinkBuilder TR Series, LinkBuilder Focus, LinkBuilder FMS TR Management Module 
Switch 1000 includes: 
SuperStack II Switch 1000, MSH Switch 1005, and LinkSwitch 1000 
Switch 2200 includes: 
SuperStack II Switch 2200, LinkSwitch 2200 
Switch 3000 includes: 
SuperStack II Switch 3000 FX, SuperStack II Switch 3000 TX, LinkSwitch 3000, LinkSwitch 3000TP 

 
 
Office-
Connect
Hub/8TPM	 LinkBuilder	 LANplex 2016	 LANplex 2500	 LANplex 6000	 Statistics	 
	 FDDI WorkGroup Hub	 ECS	  MSH	 	 	 	 	 
Ö	 	 Ö	 Ö	 	 	 	 Activity and errors	 
Ö	 	 	 Ö	 	 	 	 Frame types	 
Ö	 	 	 Ö	 Ö	 Ö	 Ö	 Network traffic	 
Ö	 	 Ö	 Ö	 	 	 	 Network errors	 
	 	 	 	 	 	 	 Bridge filtering	 
	 	 	 	 Ö	 Ö	 Ö	 Switching	 
Ö	 	 Ö	 Ö	 	 	 	 Port congestion	 
Ö	 	 	 Ö	 	 	 	 RMON tools	 
	 	 	 	 	 	 	 Network analyzer tool	 
	 	 	 	 	 	 	 Traffic matrix tool	 
	 	 	 	 	 	 	 Network history tool	 
 
	 	 	 	 	 	 	 Packet capture tool	 

  
NOTE: The names of some of the 3Com device icons have changed. A summary of the old and new names is given in Table 1-2. 
Activity and Error Statistics 
Enterprise Manager enables you to display the total network activity and errors seen by a port or a selected device. To display the Activity/Errors graph for a port: 
1Double-click on the port for which you want to display the activity and errors. 
2In the Port dialog box, choose the Information panel. 
3In the Port Information panel, select the Activity check box. 
To display the Activity/Errors graph for a device, as shown in Figure 4-1: 
1Select the device for which you want to display the graph. 
2From the View menu, choose Activity/Errors. 
In the Activity/Errors graph: 
Total Errors Shows the total number of errors that have occurred; it should be a small percentage of the readable frames figure. 
Runts Shows the number of frames received with octet counts less than the minimum legal size (512 bits), which were not involved in a collision. Runt frames are the result of collisions and are propagated around the network; this is a normal part of Ethernet operation. An excessive number of runts or collisions are an indication of congestion. You may need to consider segmenting your network. 
Readable Shows the number of frames received that are of valid length and have not suffered a collision or FCS error. Look for unusual increases in traffic rate; this can indicate a potential problem. 

FIG 
Figure 4-1 Activity/Errors Graph 
Broadcast Shows the number of frames received which are addressed to all devices. The number of broadcast frames is normally a small percentage of the value seen for unicast frames. A high level of broadcast frames can adversely affect network performance. 
Collisions Shows the number of frames for which a transmission collision was detected. Collisions are a normal part of Ethernet operation and occur if two or more devices attempt to transmit at the same time. A sudden sustained increase in the number of collisions can indicate a problem with a device, particularly if it is not accompanied by a general increase in traffic. On coaxial segments an increase in collisions can also indicate faulty cabling. 
The values shown in the Activity/Errors graph are per poll period, not per second. To change the poll period, see Configuring a Statistics Display in Chapter 4 of Volume 1. 
Frame Type Statistics 
Enterprise Manager enables you to display the total network frame types seen by a selected device. Any frames producing errors are not included, these are shown in the Activity/Errors graph (see "Activity and Error Statistics"). To display the Frame Types pie chart for a port: 
1Double-click on the port for which you want to display the frame types. 
2In the Port dialog box, choose the Information category. 
3In the Port Information panel, select the Frames check box. 
To display the Frame Types pie chart for a device, as shown in Figure 4-2: 
1Select the device for which you want to display the pie chart. 
2From the View menu, choose Frame Types. 
In the Frames pie chart: 
Unicast Shows the percentage of readable frames received that are addressed to a unicast (non-group) address. 
Multicast Shows the percentage of readable frames received that are addressed to a multicast (group) address. The total number of multicast frames is normally a small percentage of the value seen for unicast frames. A high level of multicast frames can adversely affect network performance. 
Broadcast Shows the percentage of frames received which are addressed to all devices. The total number of broadcast frames is normally a small percentage of the value seen for unicast frames. A high level of broadcast frames can adversely affect network performance. 

FIG 
Figure 4-2 Frame Types Pie Chart 
The values shown in the Frame Types pie chart are per poll period, not per second. To change the poll period, see Configuring a Statistics Display in Chapter 4 of Volume 1. 
Network Traffic Statistics 
Enterprise Manager enables you to display the network traffic as a percentage of the total possible traffic. To display the network traffic for a port: 
1Double-click on the port for which you want to display the network traffic. 
2In the Port dialog box, choose the Information category. 
3In the Port Information panel, select the Traffic check box. 
To display the network traffic for a device, as shown in Figure 4-3: 
1Select the device for which you want to display the graph. 
2From the View menu, choose Traffic. 
The values shown in the Network Traffic graph are per poll period, not per second. To change the poll period, see Configuring a Statistics Display in Chapter 4 of Volume 1. 

FIG 
Figure 4-3 Network Traffic Graph 
Network Error Statistics 
Enterprise Manager enables you to display the numbers of frames with errors seen by a port or a device. To display the Network Errors graph for a port: 
1Double-click on the port for which you want to display the frames with errors. 
2In the Port dialog box, choose the Information category. 
3In the Port Information panel, select the Errors check box. 
To display the Network Errors graph for a device as shown in Figure 4-4: 
1Select the device for which you want to display the graph. 
2From the View menu, choose Errors. 
In the Network Errors graph: 
FCS Errors Shows the number of frames received with checksum errors that do not have alignment errors. FCS errors are most likely caused by noise on the cable and should be a very small percentage of the total traffic. If it is not, change the transceivers or network adapters of devices connected to the stack to see if this eliminates the problem. FCS errors can also be caused by electrical interference from other cables or machinery. 
Alignment Shows the number of frames received with alignment errors (also known as framing errors). Alignment errors should be a very small percentage of the total traffic. They are likely to be caused by a fault at the transmitting device. Locate the segment and if there is only one transmitting device (for example, fibre or 10Base-T) change the transceiver or adapter to see if this eliminates the problem. 
Too Longs Shows the number of frames received that are greater than the maximum legal size (1518 octets). 
Short Events Shows the number of short events received. A short event is a transmission of less than the minimum size permitted on Ethernet. Short events can indicate externally generated noise causing problems on the network. Check the cable routing and reroute any cabling which may be affected by other noise sources. 
.
FIG 
Figure 4-4 Network Errors Graph 
Late Events Shows the number of frames for which a collision was detected after the valid packet minimum time. A late event can occur if you have a LAN that is longer than Ethernet standards allow (for example, more than four repeaters in series or excessively long segments). 
Very Long Events Shows the number of frames that caused Jabber Lock Up protection to operate. Isolate the source of the very long events. Change the transceiver or network adapter in the device to see if this eliminates the problem. 
Rate Mismatches Shows the number of frames whose timing was outside the permitted range. This may indicate a non-compliant device on your network. Isolate the source and change the transceiver or network adapter in the device to see if this eliminates the problem. 
The values shown in the Network Errors graph are per poll period, not per second. To change the poll period, see Configuring a Statistics Display in Chapter 4 of Volume 1. 
Bridge Filtering Statistics 
Enterprise Manager enables you to display the ratio of frames that have been filtered by the bridge port to those that were forwarded. When a frame is received on a bridge port, the destination MAC address is checked against entries in the filtering database. If the destination address is not listed in the filtering database, the frame is forwarded. If the destination address is listed and the destination device is on the same port as the source device, the frame is filtered. If the destination address is listed in the filtering database and the source and destination devices are on different ports, the frame is forwarded. 
To display the Bridge Filtering pie chart, as shown in Figure 4-5: 
1Select the bridge for which you want to view the filtering statistics. 
2From the View menu, choose Bridge Filtering. 
In the Bridge Filtering pie chart: 
Forward Shows the percentage of frames that were forwarded by the bridge. 
Filtered Shows the percentage of frames that were filtered by the bridge. 
If the bridge is operating effectively, the amount of filtered traffic should be generally greater than the amount of forwarded traffic. If there is consistently more forwarded traffic than filtered traffic, it indicates that all devices transmitting need a device on the other side of the bridge. Consider reorganizing the network so that devices that communicate frequently with each other are on the same side of the bridge. This will reduce the overall volume of traffic propagated through the network. 

FIG 
Figure 4-5 Bridge Filtering Pie Chart 
Switching Statistics 
Enterprise Manager enables you to display a graph showing the Switching statistics for any Ethernet or FDDI port. To display a switching graph as shown in Figure 4-6: 
1Double-click on the switch icon to display the representation of the switch. 
2Double-click on the port for which you want to view switching statistics. 
3In the Port Configuration dialog box, check the Switching checkbox. 
A pie chart is displayed showing the percentages of the frames forwarded and filtered for the selected port. 
The values shown in the Switching graph are per poll period, not per second. To change the poll period, see Configuring a Statistics Display in Chapter 4 of Volume 1. 

FIG 
Figure 4-6 Switching Graph 
Using the Congestion Monitor 
The Congestion Monitor enables you to display the ratio of frames that were transmitted immediately by a station and the number of frames whose transmission had to be delayed due to congestion on the network. The Congestion Monitor gathers this information from a PC Link SmartAgent on the same subnetwork as the hub. 
If the subnetwork does not contain a PC Link SmartAgent, you cannot access this information. To find out more about the PC Link SmartAgent, refer to the PC Link SmartAgent Software User Guide. 
To monitor the ratio of transmitted to deferred frames for a station. 
1Select the device to which the station is attached. 
2From the View menu, choose General Info. 
3In the General Info dialog box, choose the Stations category. 
4In the Attached Stations panel, select the station address from the list of devices. 
5Click on PC Info. 
6Select the Congestion check box. 
Enterprise Manager displays the Congestion pie chart, as shown in Figure 4-7. 

FIG 
Figure 4-7 Congestion Monitor 
In the Congestion pie chart: 
Transmitted Shows the proportion of frames that were transmitted immediately by the station. 
Deferred Shows the proportion of frames whose transmission was delayed due to congestion on the network. This figure should be a very small percentage compared to Transmitted Frames. If it is consistently high, it can indicate an overloaded network. 
Using the RMON Tools 
In today's high-tech computing environment the network is one of your company's major assets. Distributed computing has become the norm as a cost-effective solution to resource management and with it, the network has become the lifeline of all internal and cross-site communications. 
And yet it can still be the most difficult aspect of your computing resource to manage. The LANsentry for Windows provides a powerful yet easy-to-use means of getting the job done, utilizing standards-based RMON devices. 
Launching LANsentry 
To launch LANsentry for Hub 10, OfficeConnect Hub/8TPM, and MSH's, select a device on your network and then select RMON from the View menu. The Summary Window opens. 
Switch 1000 and Switch 3000 launch LANsentry Manager from the port level, rather than the device level. To launch LANsentry Manager for Switch 1000 and Switch 3000: 
1Double-click on the device, and then double-click on a port. 
2In the Port dialog box, check the RMON check box and click on OK. 
The Summary Window 
The LANsentry Summary window provides a high level view onto the network. By simply clicking on Config you can tell the LANsentry which remote networks to monitor. At specified intervals or sample periods LANsentry then polls remote network probes, processes the data it receives and displays it live on your screen. 
In many respects the Summary window is like a security camera. It can often be the first indication that something is wrong. 
To find out more on using LANsentry, refer to the Transcend LANsentry for Windows User Guide. 

FIG 
Figure 4-8 LANsentry Summary Window 
NOTE: The two graphs Top 10 Hosts by Packet Rate and Top 10 Hosts by Error Rate are only available for the Switch 1000 and 3000. 
Using the Network Analyzer Tool 
The Token Ring Network Analyzer tool lets you view the most important performance statistics monitored by Enterprise Manager. The dashboard style interface is set up by default to provide a quick summary of the critical status and performance information for any monitored Token Ring network. 
The Network Analyzer window displays network utilization and error levels. In addition, a list of active stations is displayed, with error counts by station. This presentation spotlights problem trends quickly and simplifies the rapid identification of problem nodes. 
The management agent modules track a number of variables that measure the performance of your LANs. The window variables are tailored to the type of LAN you choose. The Network Analyzer tool supports Token Ring network management by 3Com agents. Each managed LAN can have its own Network Analyzer window simultaneously active on the desktop, limited only by PC system constraints. Network Analyzer tools continue updating even while minimized (represented by icons on the desktop). 
The Network Analyzer tool displays summary network configuration information (such as ring speed and number of active stations) as well as two more detailed categories of information: 
·Network graphs - Display statistics based on the performance of the entire network. 
·Active Station list - Lists all active stations on the managed network together with station error information. 
The following section details information about both the Token Ring network graphs and station statistics. 
Invoking the Network Analyzer 
You can invoke the Network Analyzer tool, shown in Figure 4-9, from the external view or from the subnet view. 
From the External View 
Follow the instructions below to invoke the Analyzer tool: 
1Display the external view for the device you want to monitor. 
2Choose Analyzer Tool from the View menu. 
The Network Analyzer window appears. Note that the subnet address of the item you have chosen appears in the Network Analyzer window's title bar. 
From the Subnet View 
Follow the instructions below to invoke the Analyzer tool: 
1In the Subnet View window, click the left mouse button on the icon that corresponds to the device you want to monitor. 
The selected icon is highlighted. 
2Choose Analyzer Tool from the View menu. 
The Network Analyzer window appears. Note that the subnet address of the item you have chosen appears in the Network Analyzer window's title bar. 

FIG 
Figure 4-9 Token Ring Network Analyzer Window 
Network Analyzer Graphs 
The Network Analyzer displays three graphs as shown in Figure 4-9. The network performance statistics graphed in each graph is user selectable. 
NOTE: For more information about the Token Ring statistics, see Token Ring Statistics Explanations. 
The statistics graphed by default are: 
MAC Utilization MAC utilization as a percentage of ring congestion. 
Data Utilization Data utilization as a percentage of ring congestion. 
Total Utilization Total utilization (MAC and Data). 
Changing the Graphed Attribute 
In addition to the default choices, you can display the following graphs: 
Line Errors The number of new line errors reported in the last polling interval. 
Internal Errors The number of new internal errors reported in the last polling interval. 
Burst Errors The number of new burst errors reported in the last polling interval. 
AC Bit Errors The number of new AC Bit errors reported in the last polling interval. 
Aborted Transmits The number of new aborted transmits in the last polling interval. 
Isolating Errors The number of new isolating errors reported in the last polling interval. (i.e. Line through Aborts). 
Lost Frames The number of new lost frames reported in the last polling interval. 
Receive Congestion Errors The number of new receive congestion errors reported in the last polling interval. 
Frame Copied Errors The number of new frame copied errors reported in the last polling interval. 
Frequency Errors The number of new frequency errors reported in the last polling interval. 
Token Errors The number of new token errors reported in the last polling interval. 
Non-isolating Errors The number of new non-isolating errors reported in the last polling interval. (i.e. Lost Frames through Token Errors). 
Soft Errors The total number of new soft errors reported in the last polling interval. (i.e. Line Errors through Token Errors). 
Beacons The number of new beacons reported in the last polling interval. 
Claims The number of new claims reported in the last polling interval. 
Purges The number of new purges reported in the last polling interval. 
To change the attribute that is graphed in any of the three Network Analyzer graphs: 
1Select the attribute from the Statistics drop-down menu. 
Refer to Figure 4-9 for the location of the Statistics drop-down menu. 
The Statistics drop-down menu expands to show all available choices. 
2Click the left mouse button on the desired choice. 
Setting the Polling Frequency 
The polling frequency setting determines how often new data points are added to the graphs. The default polling interval is two seconds (that is, a new data point is added to each graph every two seconds). Available choices are in the range 2-60 seconds. 
To change the polling frequency for any of the three Network Analyzer graphs: 
1Position the mouse pointer over the button at the right side of the Polling Frequency drop-down menu above the graph to be changed and click the left mouse button. 
Refer to Figure 4-9 for the location of the Polling Frequency drop-down menu. 
The Polling Frequency drop-down menu expands to show all available choices. 
2Click the left mouse button on the desired choice. 
Using the Graph Statistics Dialog Box 
There is a Graph Statistics dialog box associated with each of the Network Analyzer graphs. The Graph Statistics dialog box allows you to do the following things: 
·View summary information related to the graph. 
·Select or deselect autoscaling for the graph. 
·View statistics collected since the graph was opened or clear (reset) the statistics counters to zero. 
·Set alarm thresholds or, if an alarm has occurred, reset the alarm trigger. 
To open the Graph Statistics dialog box shown in Figure 4-10, double-click the desired Network Analyzer graph. To close the dialog box, choose OK. 

FIG 
Figure 4-10 Graph Statistics Dialog Box 
Setting Alarm Thresholds 
You can set high- and low-limit alarm thresholds for each of the three Network Analyzer graphs. Controls for setting alarm thresholds appear in the Graph Statistics dialog box, as shown in Figure 4-10. 
A red, broken line across the graph indicates each threshold level. An alarm condition causes the corresponding graph to fill with red the region corresponding to the threshold violation. For example, a high threshold violation causes the area of the graph above the threshold violation to be filled with red, as shown in Figure 4-11. 

FIG 
Figure 4-11 Sample Alarm Condition 
When you set the alarm thresholds, you also choose the number of successive out-of-tolerance data points needed to generate an alarm condition. For example, a Successive Samples setting of 1 (the default) generates an alarm condition the first time a data point is generated that is out of tolerance, whereas a Successive Samples setting of 4 will not generate an alarm condition if three out-of-tolerance data points are generated, as long as the fourth data point is within the high- and low-limit thresholds. 
Set the alarm thresholds as follows: 
1Double-click the Network Analyzer graph for which you want to set or edit thresholds. 
The Graph Statistics dialog box appears. 
2Use one of the following methods to set the upper and lower thresholds: 
·Highlight the current High or Low threshold setting and overtype with the desired new setting. 
·Click the up and down arrows next to the High or Low data field as required to display the desired new setting. 
3Choose OK. 
If the graphed statistic is represented as a percentage (MAC, Data, and Total Utilization are represented as percentages), the threshold values entered in the High and Low fields represent highLimit x 100 and lowLimit x 100, respectively. For example, the Graph Statistics dialog box shown in Figure 4-12 shows an "Upper" value of 4000, which corresponds to a threshold setting of 40%. 
Resetting the Alarm Trigger 
After an alarm condition occurs, click the Reset Trigger button in the Graph Statistics dialog box to acknowledge and clear the alarm condition, and reset the graph so that it can generate another alarm condition. 
Active Station Statistics List 
The Active Station Statistics list displays the address and statistics for each station on the ring. The active monitor is identified with the designator "-AM" after its MAC address. 
The following is a list of the data displayed on the Active Station Statistics list. These categories appear on a drop-down menu under the Statistics menu on the Active Station portion of the window: 
NOTE: For more information about the Token Ring statistics, see Token Ring Statistics Explanations. 
Line Errors The number of line errors reported since the Active Station Statistics list was opened (or cleared). 
Internal Errors The number of internal errors reported since the Active Station Statistics list was opened (or cleared). 

FIG 
Figure 4-12 Utilization (Percentage Type) Graph Statistics Dialog Box 
Burst Errors The number of burst errors reported since the Active Station Statistics list was opened (or cleared). 
AC Bit Errors The number of AC bit errors reported since the Active Station Statistics list was opened (or cleared). 
Aborted Transmits The number of aborted transmits reported since the Active Station Statistics list was opened (or cleared). 
Isolating Errors The number of isolating errors reported since the Active Station Statistics list was opened (or cleared). 
Lost Frames The number of lost frames reported since the Active Station Statistics list was opened (or cleared). 
Receive Congestion The number of receive congestion errors reported since the Active Station Statistics list was opened (or cleared). 
Frame Copied The number of frames copied reported since the Active Station Statistics list was opened (or cleared). 
Frequency Errors The number of frequency errors reported since the Active Station Statistics list was opened (or cleared). 
Token Errors The number of token errors reported since the Active Station Statistics list was opened (or cleared). 
Non-isolating Errors The number of non-isolating errors reported since the Active Station Statistics list was opened (or cleared). 
Soft Errors The number of soft errors reported since the Active Station Statistics list was opened (or cleared). 
When a category is chosen from the list, the corresponding error count for each active station appears next to that station's ring address in the Active Stations list. The count always starts at zero and is incremented as new errors occur. You can reset all counters to zero by choosing the Clear button in the Network Analyzer window. 
To change the type of error for which counts are displayed in the Active Station Statistics list: 
1Select the Error Type from the drop-down menu. 
Refer to Figure 4-9 for the location of the Error Type drop-down menu. 
The Error Type drop-down menu expands to show all available choices. 
2Click the left mouse button on the desired choice. 
Changing the Display Order 
By default, active stations are sorted by ring address. You have the option of re-sorting the active station list as follows: 
Ascending order Sorts all stations by error count (from lowest to highest) by the selected error parameter. 
Descending order Sorts all stations by error count (from highest to lowest) by the selected error parameter. The default error parameter is total soft errors. When chosen, this selection lists the status from most to least errors. 
Ring Order (Token Ring segments only) This is the physical adjacency sequence of stations in the ring. This feature is useful for finding the nearest adjacent upstream neighbor (NAUN) address during a search for violating ring users. Errors are caused typically by the NAUN of the station causing the errors. 
To change the sort order: 
1Select the Sort Order from the drop-down menu. 
Refer to Figure 4-9 for the location of the Sort Order drop-down menu. 
The Sort Order drop-down menu expands to show all available choices. 
2Click the left mouse button on the desired choice. 
Using the Traffic Matrix Tool 
The Traffic Matrix tool displays traffic between active pairs of stations on the network. This tool provides a variety of statistics-gathering options and supplies a collated view of inter-station communications. With this tool you can analyze the network traffic loading of any station and its session partners. This type of fine detail identifies potential throughput bottlenecks and aids in designing network layout. 
Active addresses, senders, and receivers display by MAC address. In addition, traffic loads can be displayed either in packet or octet form. 
Using the freeze-run-clear feature, statistics can be locked for analysis or re-zeroed for baseline analysis. 
Invoking the Traffic Matrix Tool 
The Traffic Matrix tool appears under the View menu. Follow the instructions below. 
1Select the device in the subnetwork view with which you want to use the Traffic Matrix tool. 
2From the View menu, select Matrix. 
The Interface Selection dialog box appears. See Figure 4-13. 

FIG 
Figure 4-13 Interface Selection Dialog Box 
3Select the object you wish to view. 
4Click on RUN. 
The Traffic Matrix window appears and by default displays the Summary view of the object you select. 
Configuring the Traffic Matrix Tool 
The Traffic Matrix window provides several options for displaying the data. Follow the instructions below for configuring the Traffic Matrix tool. 
1Set the Show Most field. Position the mouse over the arrow on the right side of the menu. 
2Select one of the following display options: 
·Active addresses - Displays all active addresses on the selected segment. 
·Active Senders - Displays the stations that are sending data. 
·Active Receivers - Displays the stations that are receiving data. 
3Set the Show By field. 
4Select one of the following data types: 
·Octets - Displays the traffic in units of octets. 
·Packets - Displays the traffic in units of packets. 
5Set the Show field. 
6Select one of the following data parameter types: 
·From last clear - Displays traffic matrix data that has been gathered since the last time you cleared the counts. This setting builds a long-term view of traffic loads. 
·Over last interval - Displays traffic matrix data based solely on the most recent time interval. This setting gives a more dynamic view of the traffic trends. 
7Set the Interval field. 
8Select one of the following update time cycles for calculating the traffic matrix: 
·30 seconds 
·1 minute 
·10 minutes 
Invoking the Summary View (Traffic Matrix Data) 
After you have configured the Traffic Matrix tool, you are ready to view data between stations. When the Traffic Matrix window appears, stations on the selected network will be listed after completion of the first update interval. 
Follow the instructions below to select a specific station. 
1While pointing at an address, click to select. 

FIG
FIG 
Figure 4-14 Traffic Matrix Window 
The sample Summary screen displayed in Figure 4-14 represents an actual Traffic Matrix tool screen. This screen displays the following: 
·All active addresses on the selected LAN are displayed. 
·The basis for the count is packets. 
·The packets shown are updated from the last time they were cleared. 
·The count will be updated every 8 seconds. 
·The selected station is ranked at 002, based on the amount of traffic. 
·The address is 08004E 069C64. 
·The current count is 396. 
·Address 08004E 069C64 is communicating to 2 other stations and receiving traffic from 48 other stations. 
Invoking Detail View (Traffic Matrix Data) 
You have the ability to view the station statistics in greater detail. Double click on a station or click on the Detail button after selecting a station to bring up the Detail screen as shown in Figure 4-15. 
Follow the instructions below to view detail for a specific station. 
1Double-click on an address listing in the Traffic Matrix window, or select the Detail button. The Traffic Matrix Detail window appears, see Figure 4-15. 
This screen displays the stations that are communicating with the station selected in the Summary View window. 
This view provides more detailed information about the summary view station and the stations with which it is communicating. Each line entry represents a station that has either sent or received data with the selected station (session pair). The count field displays the traffic (represented in either octets or packets, based on set up selection). 

FIG
FIG 
Figure 4-15 Traffic Matrix Detail View 
The sample screen shown in Figure 4-15 represents an actual Traffic Matrix tool screen viewed in detail. This screen displays the following: 
·Basis for the count is packets. 
·The packets shown are updated from the last time they were cleared. 
·The count will be updated every 8 seconds. 
·Traffic to and from the station displays in columns in the center of the window (address 08004E 069C64 in the screen depicted above). 
·Each entry is ranked based on the frequency (total number of packets) of communications with the selected address (08004E 069C64). 
·The destination and/or source of the traffic. 
·Packet count of the source of the traffic. 
Traffic Matrix Control Buttons 
The Traffic Matrix screen also has three buttons which control the tool. 
·Clear - Allows you to clear the address table and zero the count. All counts and addresses are cleared and then rebuilt from the beginning by the agent. Position the mouse pointer over the Clear button and press the left mouse button. 
·Freeze - Allows you to continue or suspend polling of network data. Position the mouse pointer over the Freeze button and press the left mouse button. 
·Close - Allows you to close the window. 
Using the Network History Tool 
One of the best ways to optimize your network is to monitor long-term performance for error and traffic trends. Enterprise Manager provides a full-featured History tool that analyzes and stores the traffic patterns of any network segment where a RMON database exists. 
The management station automatically queries the 3Com agents every two hours and downloads statistics collected on a minute by minute time frame via the RMON history function in the agent. The system archives these statistics in the management station where they can be viewed over the following intervals: 
·1 week - 84 two-hour periods. 
·1 day - An expanded view of 12 two-hour periods. 
·2 hour - Displays the most recent statistics in 120 one-minute. 
The Network History tool is based on the facilities provided by the SNMP RMON History Group. On power-up, LinkBuilder agents begin collecting RMON history data for the entire network segment and storing individual sample periods in a circular buffer. Each sample period is one minute long, and the agent retains 120 of these samples in the buffer before discarding the oldest sample. As a result, the agent retains the most recent two hours of collected statistics. 
The Network History tool works by querying the associated agent every two hours and by downloading the most recent two hours of collected information. Individual sample periods within this two hour period may be graphed with the history tool. In addition, these sample periods are processed to compute the total, average, minimum and maximum values of each statistic over the two hour period. The history tool retains the processed data as a two hour sample period. 
The Network History tool saves these samples in circular disk files retaining up to 84 of the most recent samples before discarding the oldest. As a result, the tool retains the most recent week of processed data in a disk file on the management workstation. This requires approximately 14KB for each Ethernet hub/network segment. 
The Network History tool can also be configured to save statistics automatically beyond the one week period. In order to conserve the large amounts of disk space that this requires, the history tool saves each prior week's worth of statistics in a compressed archival format. The Network History tool may be configured to save up to four weeks of data. 
The size of these archive files varies depending on the activity of your network. When viewing statistics in the history tool's graphs, you may select one of the previously written archive files and decompress the data for viewing. 
Invoking the Network History Tool 
In order to gather data, a separate session of the Network History tool must be running for each Ethernet segment. To invoke the Network History tool: 
1Select a known RMON-compatible device in the subnet view. 
2Select History from the View menu. 
The History window appears. Note that when this tool is first invoked, the graphs may be empty for a few seconds. A receive counter in the upper left corner of the screen displays the count when data is being received. 

FIG
FIG 
Figure 4-16 Sample Network History Window 
Configuring the Network History Tool (Archiving) 
The Network History tool is a series of graphs that display timelines for a variety of performance and error statistics for the selected agent. The History tool connects to the agent and begins downloading statistics for the first two-hour interval. Enterprise Manager maintains one week's worth of history by default in the current disk file. If you wish to save more than one week's data at a time you must use the archive option. To archive the Network History, proceed as follows: 
1Click on the Archive menu at the top of the screen. 
A drop-down menu appears with a list of options for archiving statistics. 
2Choose an interval from one to four weeks in which to archive the statistics. If you choose not to archive, leave the setting Off. 
Configuring the Network History Tool (Time Span) 
The History Tool provides three time spans in which to view History data. To change the Time Span, proceed as follows: 
1Click on the Time Span menu at the top of the screen. 
A menu appears with a list of options for setting the time span. 
2Choose an interval in which to archive the statistics. 
Directly below the drop down menus a window displays the current interval start and end times and a record of the history. 
Viewing History Data 
The History tool gathers statistics over a two hour period by default. The time span displayed on the screen is a minimum interval of two hours. Within a two-hour interval each statistic is represented by a maximum and minimum value. The minimum value is the baseline of the graph and the maximum value is automatically set at the top of the graph range. The graph auto-scales if these limits change. 
Each graph has a shaded field which allows you to select a more limited time period to analyze via statistics counts. By default, the shaded field covers the entire displayed period. You narrow the selected time interval of any graph by moving the cursors on either end of the graph. The time interval starts with the green cursor on the left side of the graph and ends with the red cursor on the right side of the graph. The start and end times of the graph appear in the window above the graphs. See Figure 4-17. 
You have two methods for viewing History data. 
1While pointing at the red or the green dashed line (cursor), press and hold the left mouse button. 
2Drag the cursor to the desired position and release. 
or: 
1Click on one of the two arrow buttons next to the Cursor box on the window. 
The arrow button moves the selected cursor left and right. The cursor you move is the active cursor and the corresponding color appears in the box. 

FIG 
Figure 4-17 Network History Window with Detail 
Viewing Statistics 
The most detailed method for viewing statistics is in two-hour intervals; however, you may view statistics gathered over a day or a week as well. Follow the steps below: 
1To view statistics for a week, select the 1 Week option from the Time Span menu. 
2To view statistics for a day, select the 1 Day option from the Time Span menu. 
Adding or Removing Graphs 
You can view statistics in individual graphs. The graphs can be stacked in the history window. Most video displays allow at least three graphs at a time. The window opens with two graphs by default. To add graphs, follow the steps below: 
1From the View menu item in the Network History window, select Add Graph from the menu. 
A new graph appears at the bottom of the screen. 
To remove graphs, follow the steps below: 
1While pointing at the graph, click the right mouse button. 
2Choose Close from the pop-up menu. 
Viewing Statistics Collected over a Week 
To view a week's worth of statistics in two-hour increments, follow the steps below: 
1From the Time Span option menu, select 1 week from the menu. 
The displayed graphs change to reflect the data collected over the most recent week. You can also make use of the Show Totals and Show High/Low/Avg. options. The Show Totals category displays the statistic over a two-hour interval. 
The Show High/Low/Avg. category displays the maximum and minimum values for the statistic derived from the individual samples downloaded from the agent. The shaded area of the graph shows the maximum and minimum values of the statistic. The solid line represents the average of the same statistic. 
Retrieving Archived Statistics (1 week) 
You can view a previous week's worth of statistics in a graph. To do so you must select the Open Archive option from the pop-up menu. Each graph requires about 3MB of temporary disk space. Perform the following steps: 
1With the mouse pointer over the Graph, click the right mouse button to bring up the pop-up menu. 
2Select Open Archive from the menu. 
The Select Archive window appears. You can not do this if you have the Two-hour Time Span selected. 
3Select the archive you wish to open, then click on OK. 
Archived graphs remain selected until you close the individual graph. 
Displaying Updated Information 
Occasionally you may want to view the most recent data outside of the normal collected two-hour period. You query the agent on demand to update the data in the History tool via the Poll now command. 
To update the information: 
1From the View sub-menu on the History window, select the Poll now option. 
The graph updates with the most recent data. 
Using the Packet Capture Tool 
Extensive LAN-analysis is provided with Transcend's enhanced packet-capture feature. Any packet on the managed LAN, local or remote, can be captured (recorded) to assist you in understanding network traffic and isolating problems. This is a useful tool for analyzing the interaction of different stations at the protocol level. 
The basis for the Packet Capture tool is a series of filters that allow you to define packets to capture and then view captured packets using a view filter. Using a set of user-defined filters you can specify packets to view based on protocol type, packet type, or station pairs. 
Captured packets can be saved in Network General Sniffer® format for further analysis. 
Invoking the Packet Capture Tool 
Before you can use the Packet Capture feature, you need to configure a capture filter for an appropriate RMON agent. Begin by invoking the Packet Capture tool. 
1Select the device you want to monitor. 
2Choose Capture Tool from the View menu. 
The Select Interface window appears. 
3Choose an interface to view. 
If only one interface displays, the main Capture Tool window appears with the default filters in place. See Figure 4-18. 

FIG 
Figure 4-18 Capture Tool Main Window (reduced view) 
Configuring Capture Filters 
1Select a device to view. 
The Capture Tool main window appears. 
2Click on the Capture filter icon in the menu bar. 
As an alternative you can select Define Capture from the Filters menu. 
The Set Capture & View Filter dialog box appears which allows you to set the parameters for the capture and view filters. All fields are set to default values and will remain so until you change and/or save them. 

FIG 
Figure 4-19 Set Capture & View Filters Dialog Box 
3Select Data Packets for viewing. The default setting for this field is Include All which displays all data packet types. You have the following options: 
·Don't Include - Prevents viewing of all data packets. 
·Include All - Allows you to view all data packets. 
·Include Selected Below - Allows you to select specific data packets to view from the scrollable list. 
4Select the Source packet type under the Source heading. You have the following options: 
·Include Non-Source Routed - Allows you to capture only packets without Source Routing Information Fields (RIFs). These are local ring packets only. Even if source routing communications occurs on the ring, there may be local packets that do not have any RIFs. 
·Include Source Routed - Captures only packets that have RIFs. These are packets that are routed via source routing. 
·Include Both (Non-SR & SR) - Captures all packets with or without RIFs. 
5Select MAC packets for viewing. The default setting for this field is Include All MAC Packets. You have the following options: 
·Don't Include MAC Packets - Prevents you from viewing MAC packets. 
·Include All MAC Packets - Allows you to view all MAC packets. 
·Include All MAC Packets EXCEPT AMP&SMP - Allows you to view all MAC packets except Active Monitor Present (AMP) and Standby Monitor Present (SMP) packets. AMP and SMP packets are part of the normal ring sequence polling process that occurs periodically. These packet type are not of any interest normally. 
·Include MAC Packets Selected Below - Allows you to select specific types of packets to view from the scrollable list. 
6Select a Source host by clicking on the Source bar under the Host heading in the lower left corner of the screen. The Select Host dialog box appears. 

FIG 
Figure 4-20 Select Host Dialog Box 
You may select an individual source host or any hosts. Hosts are listed by address. The MAC-layer address is the default. 
7Select a Destination host by clicking on the Destination bar under the Host heading in the lower left corner of the screen. The Select Host dialog box appears. 
You may select an individual destination host or any hosts. The Token Ring architecture specification defines the functional addresses. If you select individual source and destination hosts, you have the option of viewing packets from destination to source. 
To view response packets from destination back to source select the Include Response From Destination Source box. 
8Select buffer options under the Misc. heading. You have the following choices: 
·Lock When Full - When selected captured packets fill the memory buffer until it is full. From that point on the system stops collecting packets. 
·Wrap When Full - When selected captured packets fill the allocated memory buffer in the agent until it is full. From that point on the system saves the newest captured packets and discards the oldest. This is also known as first-in/first out. 
9Select Packet Size. 
This determines how much of each packet to save. The packet size is measured in bytes from beginning to end. The system discards any bytes beyond the first portion depending on the setting. The default for this is 128 bytes which should be sufficient if you are capturing MAC-layer packets. If you plan to capture LLC-layer packets you may want to set this field to a higher value. 
10Select Buffer Size. 
This determines the maximum size of the buffer used to collect and store the captured packets. This buffer size is requested by the agent and if the agent is unable to provide this amount of memory, then the buffer is reduced. 
11Click on Save to save the settings. The Filter Saved window appears. 
12Repeat the above steps for each set of filters you desire. 
Loading A Filter Set 
Once you have defined and saved a filter set, you can then load it any time. Follow the steps below: 
1Choose Select Capture from the View menu. 
The Select A Filter window appears. Select the filter you wish and click View to view, Remove to remove, or Cancel to cancel. 
The Capture & View Filters dialog box appears. 
Starting the Capture 
You have two choices for starting a capture. 
·Green Light icon - Click on the Green light icon located in the menu bar. 
·Start Capture - Select Start from the Capture menu. 
Stopping the Capture 
You have two choices for stopping a capture. Allow a reasonable amount of time for an adequate capture to take place before stopping. 
·Red Light icon - Click on the Red light icon located in the menu bar. 
·Stop Capture - Select Stop from the Capture menu. 
Filtering Packets 
Once you have captured a packet you have the option of viewing them through a series of view filters. These filters allow you to specify the data you want to view within a packet. Begin by selecting a filter. 
You begin by selecting a filter from the saved filters. Specify the packet information you wish to view. Note that you cannot view packet information if you did not capture it during the capture filter procedure. 
Analyzing Captured Packets 
1Select a filter from the View filter list by either clicking on the View Filter menu bar icon or choosing Select View from the Capture menu. 
The Capture Tool main window appears with a list of packets that have been captured. 
2Select a packet by clicking on it. 
Initially, each packet is represented by a single line entry that includes the following: 
·Packet sequence number 
·Time of capture 
·Transmitting station identity 
·Type of packet 
3While holding down on the mouse button drag the selected packet and drop it on the lower portion of the Capture Tool main window. 
When you drag and drop the selected packet you will notice that the icon changes. As soon as the icon is in the lower half of the screen it resembles a text file. 
4Release the mouse button and the detail view of the packet appears. 
The detail view of the packets display the following information: 
For Non-MAC addresses 
·Destination address. 
·Type of packet (source-routed or non-source-routed), protocols used, frame control bytes, RIFs, and source and destination service access points (SAPs) and all the data contents in hexadecimal. 
For MAC addresses 
·Sub-vector breakdown of the packet, which can include nearest adjacent upstream neighbor (NUAN), soft error counts, physical location. 
·Packet length and bytes captured. 
5Collapse the detail view by clicking in the upper left corner of the view. 
Saving Captured Packet Files 
You may save captured files for future reference using the Save function under the File menu. With the packet capture in the detail view, follow the procedure below: 
1Select Save from the File menu. 
The Save window appears. 
2Enter the name of the file and choose the location for the file to reside. 
3Click OK. 
Changing Agents 
You can change agents to view at any time. Follow the procedure below. 
1Click on the Change Agent icon in the main menu bar. 
2Enter the IP address of the agent you wish to view. 
3Enter Community String used by agent. 
NOTE: Community strings are case-sensitive. Packet capture will not work properly if the strings do not match. 
4Click OK. 
Viewing Multiple Captures 
You can view multiple captures for comparison using the Tile function and the Show/Hide features. Follow the procedure below. 
1Select two or more packets to view and drag them into detail view. 
2Click on the Hide icon in the main menu bar. 
3Select Tile from the View menu. 
The opened detail view packets display in tile format to allow you to compare data. 
4Repeat process for each detail view packet you wish to view. 
5Click on the Show icon to return to the main Capture Tool window. 
 5 Managing a NETBuilder System 
This chapter contains the following topics: 
·What Can You Manage? 
·Using the Device View 
·Using the Configuration Dialog Boxes 
·IPX Policies Dialog Box 
·Mnemonic Filters Dialog Box 
·Accessing the NETBuilder Console Using Telnet 
What Can You Manage? 
Before Enterprise Manager can communicate with a NETBuilderâ system, the system must be configured with the following minimum information: 
IP address The NETBuilder system must have a unique IP address. If you are unfamiliar with TCP/IP addressing, refer to Appendix A in the Transcendâ Enterprise Manager for Windowsä User Guide Volume 1. 
Subnet mask You only need to enter a subnet mask if you have implemented subnetting on your network. 
SNMP The NETBuilder system must be configured for SNMP as described in the NETBuilder Family Bridge/Router Operation Guide. 
Community String The management station (PC) and the NETBuilder system must be configured with the same community string in order for the NETBuilder system to be discovered. 
The NETBuilder hardware, modules, and software that can be managed are: 
NETBuilder Hardware 
·SuperStackä II NETBuilder Bridge/Router and Boundary Routerâ 
·NETBuilder II Bridge/Router 
·NETBuilder Bridge/Router 
NETBuilder II Modules 
·All NETBuilder II modules are supported. 
NETBuilder Software 
·Version 7.x through 9.0 
All NETBuilder systems recognized by autodiscovery are represented by icons. However, only those NETBuilder systems with supported software installed are manageable using this application. NETBuilder systems not listed above will be discovered as "generic" devices and are manageable only through a Telnet session. 
All NETBuilder systems running software version 7.x or later are discovered using autodiscovery. These systems are represented by the NETBuilder II icon and are displayed in the subnetwork-level window. 
NOTE: Some NETBuilder Remote Office models are identified as SuperStack II devices in the subnetwork-level window. For example, models 22x and 4xx are shown as SuperStack II icons; however, models 20x, 3xx, and 5xx are shown as NETBuilder Remote Office icons. 
If you have difficulty discovering or displaying correct information for NETBuilder systems, check that the NETBuilder system's SNMP parameters are set correctly. For more information, refer to the NETBuilder Family Bridge/Router Operation Guide. 
Timeout Messages 
If the NETBuilder component of the Enterprise Manager loses its connection with a NETBuilder system, a timeout message appears. This message automatically disappears when the connection is re-established. If any graphs are open when a connection is lost, they are automatically closed. 
Using the Device View 
The device view is a graphic representation of the selected NETBuilder system. Figure 5-1 shows the device view for a typical eight-slot NETBuilder system. 

FIG 
Figure 5-1 Device View 
From the device view you can see which modules are in each slot of the NETBuilder chassis, and you can view the status LEDs. 
If you install a new NETBuilder module and the NETBuilder software does not support it, the application displays the message "Unsupported Module" on the bitmap representing that module. 
Opening the Device View 
The device view is used to access configuration information on individual interface modules installed in the NETBuilder chassis. 
To open the device view from the subnet window, double-click the left mouse button on a NETBuilder icon in the subnet window. 
NOTE: You can manage only one NETBuilder system at a time. If you want to view information for a different NETBuilder system, you must close the current view and return to the subnet window to select a different NETBuilder system. 
Returning to the Subnet View 
To return to the Transcend Enterprise Manager subnet view, do one of the following: 
From the File menu, choose Exit. 
or 
From the Window menu, choose Enterprise Manager. 
Getting Configuration Information from the Device View 
The NETBuilder device view contains additional information that you can access. Configuration information is available for the following items: 
·The NETBuilder chassis 
·The CEC module 
·Single-path I/O modules 
·Each physical interface of a multipath I/O module 
·Physical connectors 
To get configuration information on any item in the device view, double-click the item to display an item-specific configuration dialog box. 
Using the Configuration Dialog Boxes 
Configuration dialog boxes are the tools you use to view and change system settings for the NETBuilder system within the Transcend Enterprise Manager environment. The following configuration dialog boxes are available: 
·Info View 
·Bridge Configuration 
·Interface Configuration 
·Dial Configuration 
·ISDN Configuration 
·IPX Configuration 
·IP Configuration 
·AppleTalk Configuration 
·Frame Relay Configuration 
·Boundary Routing Configuration 
·IPX Policies 
·Mnemonic Filters 
If you get MIB access, get, or set failure error messages when using the configuration dialog boxes, the problem may be one of the following: 
·The WRITE community string does not match the string specified in the NETBuilder system. 
·The NETBuilder software does not support the service or feature you are trying to configure. 
·The selected module does not support the service or feature you are trying to configure. 
NOTE: NETBuilder applications use only one community string for both read and write operations: only the WRITE community string is passed to the NETBuilder application for all operations. 
Monitor (Display Only) Mode 
Under certain conditions, the Enterprise Manager application displays configuration dialog boxes in monitor mode. In monitor mode, you must reconfigure the bridge/router using either the console or a Telnet connection; you cannot reconfigure the bridge/router using the Enterprise Manager configuration dialog boxes. 
The following conditions cause the application to operate in monitor mode: 
·The bridge/router is using virtual ports that are not configured for Frame Relay. 
·Two (or more) primary paths are sharing a port. 
·More than two paths are sharing a port. 
·More than 48 paths exist. 
If one or more of these conditions exist, the application displays a dialog box to alert you that it is in monitor mode when you open any of the configuration dialog boxes (for example, by double-clicking an interface adapter in the graphical NETBuilder display). 
Opening the Info View 
All configuration dialog boxes are accessed using the ribbon bar at the left side of the Info View dialog box, as shown in Figure 5-2. 

FIG 
Figure 5-2 Info View Dialog Box 
You can open the Info View dialog box in any of the following three ways: 
·By double-clicking the item for which information is desired (for example, a WAN interface connector on the device view) 
·By selecting the desired item with the left mouse button and then choosing Device/Subnetwork from the Configure menu 
·By choosing Device/Subnetwork from the Configure menu without selecting any item on the device view 
Using the Info View Dialog Box 
The Info View dialog box is always the first configuration dialog box to appear. To access this dialog box, double-click an interface connector in the device view, or from the Configure menu, choose Device/Subnetwork. 
If an interface is selected, the information in the configuration dialog boxes refers to that interface. If the CEC module or a chassis is selected, the information in the configuration dialog boxes refers to the entire NETBuilder system. 
Ribbon Bar 
At the left side of the Info View dialog box, there is a ribbon bar that contains icons for configuring your NETBuilder system. Select the Info icon to view the Info View dialog box, or select one of the other icons to view the corresponding configuration dialog box. The Info icon is selected by default. 
Dialog Box Options 
The Interface Properties section contains the following read-only information: 
·Type Describes the entity for which configuration information is being displayed. If the entire NETBuilder system is selected, the hardware type is one of the supported devices. If the CEC module is selected, the hardware type is CEC. If an individual data I/O module is selected, the hardware type reflects the type of board installed, for example, Ethernet, FDDI, Token Ring, and so forth. 
·Model If the chassis is selected, the model number of the NETBuilder system is displayed, otherwise this field is empty. Applies only to SuperStack II Bridge/Router systems. 
·SW Ver Displays the version of NETBuilder software installed on the system being managed. 
·Minor Ver Displays the minor version of NETBuilder software installed on the system being managed. 
·SW Pkg Displays the software package running on the NETBuilder system. 
·Slot Displays the I/O module slot containing the module for which information is currently displayed. This data field applies only to NETBuilder II systems. The value is null if the chassis is selected or 0 if the CEC module is selected. If an I/O module is selected, the value is an integer in the range 1-4 if the device has four slots or an integer in the range 1-8 if the device has eight slots. 
·Port Applies only to I/O modules. Identifies the interface pipe through which information is transferred. If the interface connector you chose is the secondary path, the label (secondary) appears after the port name, otherwise, the label (primary) appears. 
·IP Address If either the NETBuilder chassis or the CEC module is selected and routing is enabled, the field contains the legend Multi-Net mode; if routing is disabled, the field contains the IP address of slot 0. If an individual module is selected and routing is enabled, the field contains the interface's primary IP address; if routing is disabled, the field contains the IP address of slot 0 and the legend Single Net mode. 
·Baud Displays the baud rate for which the interface is configured. 
·Status Displays Operational or Disabled. 
·Clock Displays Internal, External, or Not Applicable. 
The Configuration Properties section contains the following read-only information: 
·Routing A check box is filled for each applicable protocol or routing type: IP, IPX, AppleTalk, Boundary Routing. 
·Bridging A check box is filled for each applicable bridging method: Transparent, Source Routing, Spanning Tree, Learning, AT Formatting, Firewall. 
·WAN A check box is filled for each applicable protocol: Leased Line, Dial, Frame Relay, SMDS, X.25. 
The View Stats section contains the only user-selectable check boxes in the dialog box. Available categories are Utilization, IP, and Dial On Demand. All graphs for the selected category(ies) are displayed when you click the OK button. The same graphs can be individually displayed from the View menu. 
Other buttons: 
·OK Records your new settings. 
·Cancel Closes the dialog box without recording your new settings. 
Bridge Configuration Dialog Box 
The Bridge Configuration dialog box, shown in Figure 5-3, controls the bridge-related functions of the port that corresponds to the interface you selected from the device view. 

FIG 
Figure 5-3 Bridge Configuration Dialog Box 
Dialog Box Options 
The Bridge Configuration dialog box contains the following data fields and controls: 
The Global section contains two check boxes: 
·Bridging Enables bridging globally. 
·Spanning Tree Protocol Enables spanning tree globally. 
NOTE: The Bridging and Spanning Tree functions are called "global settings" because they apply to the entire NETBuilder system, not just to one interface. 
The Interface section contains the following selections: 
·Number Displays the port (not path) number of the currently selected interface. 
·Transparent Selects transparent mode. 
·Source Route Selects source route mode. 
·Source Route and Transparent Selects source route and transparent modes. 
·None Disables bridging. 
·Ring Number Displays the port (not path) number of the currently selected interface. This field is active when either Source Route or Source Route and Transparent is selected. Enter the token ring number for source route bridging. 
Other buttons: 
·OK Records your new settings. 
·Cancel Closes the dialog box without recording your new settings. 
Interface Configuration Dialog Box 
The Interface Configuration dialog box, shown in Figure 5-4, controls the physical interface you selected from the device view. 

FIG 
Figure 5-4 Interface Configuration Dialog Box 
Dialog Box Options 
The Interface Configuration dialog box contains the following data fields and controls: 
Some configuration operations are allowed only when the interface is enabled. To avoid error messages, make sure the interface you want to configure is enabled before attempting configuration. 
Enable and Disable Enables or disables the selected interface. 
Name Provides an area to enter a descriptive name (up to eight characters with no spaces allowed) for this interface. If, for example, the selected interface is the WAN interface through which the Eastern Sales Office is accessed, you might enter "EAST_S_O." 
Number Displays the slot number of the selected interface. 
Owner Displays the current owner of the selected interface. Click the arrow icon to display a list of available owner types. 
Baud Displays the current data speed. Click the arrow icon to display a list of the available baud rates. 
Clock Displays the type of clock currently used by the NETBuilder system. Click the arrow icon to display a list of the available clock types. The Internal value applies only to SuperStack II Bridge/Router model 32x systems and causes the bridge/router to derive both the transmit and receive clocks from the on-board clock oscillator. The External value causes the bridge/router to derive the transmit clock from either the send or receive timing clock supplied by the CSU/DSU or by the attached modem. 
Connector Displayed only if it is a WAN path and the hardware is NETBuilder or SuperStack II NETBuilder ISDN Bridge/Router. Displays the type of connector currently connected to the selected interface. Click the arrow icon to display a list of the available connector types. The X.21 connector is available only for NETBuilder software version 8.3 or greater running on SuperStack II Bridge/Router systems. 
OK Records your new settings. 
Cancel Closes the dialog box without recording your new settings. 
Dial Configuration Dialog Box 
The Dial Configuration dialog box, shown in Figure 5-5, controls the dial-related functions of the port that corresponds to the interface you selected from the device view. 

FIG 
Figure 5-5 Dial Configuration Dialog Box 
For initial service setup, modify settings one at a time until you become familiar with the various restrictions imposed by the Dial service. Proceed in this order: modify Service Detail settings and then click the OK button, modify Relation settings and then click the OK button, modify Service settings and then click the OK button. 
To change the primary/secondary relationship after initial setup, proceed as follows: unselect all services (DOD, DR, BOD), set the primary/secondary relationship, then set the line type, and then click the OK button. 
Dialog Box Options 
The Dial Configuration dialog box contains the following data fields and controls: 
The Service section contains four radio buttons: 
·No Dial Out Disables the dial service. 
·Manual Dial Enables the manual dial functions as the primary method of dial connection. Use the Dial and Hangup buttons with manual dialing. 
·Dial On Demand Enables dial-on-demand. Automatically establishes and terminates the dial connection based on packet traffic. Use the Disaster Recovery and Bandwidth On Demand check boxes with dial-on-demand. 
·Other Allows the Disaster Recovery and Bandwidth On Demand check boxes to become active. You can select one or both options. If Disaster Recovery is selected, the secondary interface establishes a connection when the primary interface loses its connection. If Bandwidth On Demand is selected, the secondary interface establishes a connection when the primary is at full utilization. When you deselect Other, the Disaster Recovery and Bandwidth On Demand check boxes are grayed out. 
The Relation section contains the following data fields and controls: 
·Interface Contains the name of the interface you selected before opening the configuration dialog box (hereafter called the "selected interface"). This information is read-only. 
·Primary and Secondary Displays the current configuration and allows you to reconfigure the selected interface as a primary or a secondary interface. 
The related interface automatically becomes the complement of the selected interface. For example, if you choose "Secondary," for the selected interface, the related interface automatically becomes the primary interface in relation to the selected interface. 
·Related Displays the name of the interface that is currently related to the selected interface. Click the arrow icon to display a list of the interfaces that are available to be related to the selected interface. 
If the selected interface is a primary interface, the related interface is by definition a secondary interface. If the selected interface is a secondary interface, the related interface is by definition a primary interface. A secondary interface inherits the port attributes that apply to its related primary interface. 
To change the primary/secondary relationship, proceed as follows: unselect all services (DOD, DR, BOD), set the primary/secondary relationship, then set the line type. 
The Service Detail section contains the following data fields and controls: 
·Number Provides an area to type the telephone number that the selected interface dials when establishing a dial-out connection. Include all necessary access codes and area codes. Type a comma to generate a pause in dialing. Type hyphens to improve readability between number groups without generating a pause in dialing. 
·Mode Displays the current mode of the selected interface. Click the arrow icon to display a list of the available modes. 
·Line Type Displays the current line type of the selected interface. Click the arrow icon to display a list of the available line types. 
·Control Displays the current control configuration of the selected interface. Click the arrow icon to display a list of the available control configurations. 
Other buttons: 
·OK Records your new settings. 
·Cancel Closes the dialog box without recording your new settings. 
ISDN Configuration Dialog Box 
The ISDN Configuration dialog box, shown in Figure 5-6, controls the ISDN-related functions of the port that corresponds to the interface you selected from the device view. 

FIG 
Figure 5-6 ISDN Configuration Dialog Box 
Dialog Box Options 
The ISDN Configuration dialog box contains the following data fields: 
Switch Type Displays the current switch type of the ISDN line connected to the selected interface. Click the arrow icon to display a list of the available switch types. These switch types are valid only if the line type specified in the Dial Configuration dialog box is set to dial or auto. The switch types listed are for Europe, Japan, North America, AT&T, and Northern Telecom, respectively. 
For information on changing the switch type, refer to the "Read Me First" document that shipped with the NETBuilder system. 
Local Dial Number Provides an area to enter the telephone number used to establish a dial-in connection with the selected interface. 
B1 Service Profile ID Provides an area to enter the B1 service profile ID provided by the switch vendor. 
B2 Service Profile ID Provides an area to enter the B2 service profile ID provided by the switch vendor. 
OK Records your new settings. 
Cancel Closes the dialog box without recording your new settings. 
IPX Configuration Dialog Box 
The IPX Configuration dialog box, shown in Figure 5-7, controls the IPX-related functions of the port that corresponds to the interface you selected from the device view. 

FIG 
Figure 5-7 IPX Configuration Dialog Box 
Dialog Box Options 
The IPX Configuration dialog box contains the following data fields and controls: 
Global IPX Allows you to choose the radio button to enable or disable IPX routing and IPX RIP on the currently selected interface. 
With NETBuilder software version 8.0, you can enable or disable the IPX Service on a per-port basis. With earlier versions of the NETBuilder software, you enabled or disabled the IPX Service for the entire system. 
Network Number Provides an area to enter the network number of the IPX network to which the selected interface is connected. 
NOTE: If you want to change an IPX network number, you must first delete the current IPX network number before entering the new one. To do this: 
1)Select the Disable radio button. 
2)Delete the IPX network number using the backspace key. Do not enter the new number yet. 
3)Click OK. 
4)Reopen the dialog box and enter the new IPX network number and click OK. 
Header Format Displays the current IPX header format. Click the arrow icon to display a list of the available IPX header formats. For more information about header formats, refer to the NETnumber parameter in the IPX Service Parameters chapter in the NETBuilder Family Bridge/Router Reference Guide. 
OK Records your new settings. 
Cancel Closes the dialog box without recording your new settings. 
IP Configuration Dialog Box 
The IP Configuration dialog box, shown in Figure 5-8, controls the IP-related functions of the port that corresponds to the interface you selected from the device view. 

FIG 
Figure 5-8 IP Configuration Dialog Box 
Dialog Box Options 
The IP Configuration dialog box contains the following data fields and controls: 
Global IP Allows you to choose the radio button to enable or disable IP routing. 
Address Displays the IP address of the selected interface. Click the arrow icon to display a list of all known IP addresses. Select the desired IP address. 
To immediately add a new IP address, type the new IP address in the box and then click the Add button. To immediately delete a known IP address, select the IP address from the list and then click the Delete button. 
You can configure multiple IP addresses to an interface, but only one can be the primary address. Each time you add an IP address using this dialog box, the new IP address becomes the primary IP address. The old primary address becomes a secondary IP address. When the primary address is displayed in the Address field, the OSPF and Area ID fields are enabled. 
NOTE: If a new IP address is added to the interface with which you originally established a connection, you may lose the connection. To establish a new connection, use the newly created IP address. 
Subnet Mask Allows you to enter the subnet mask, if any. 
RIP Enables RIP on the currently selected interface when checked. 
OSPF Enables OSPF on the primary IP address when checked. 
Area ID Allows you to enter the OSPF area ID. 
OK Records your new settings (except for add and delete function, which are immediately executed). 
Cancel Closes the dialog box without recording your new settings. 
AppleTalk Configuration Dialog Box 
The AppleTalk Configuration dialog box, shown in Figure 5-9, controls the AppleTalk-related functions of the port that corresponds to the interface you selected from the device view. 

FIG 
Figure 5-9 AppleTalk Configuration Dialog Box 
Dialog Box Options 
The AppleTalk Configuration dialog box contains the following data fields and controls: 
Apple Talk Displays whether Apple Talk is enabled or disabled (read-only). 
Network Range Displays the current network range (read only). 
Port Zone Displays the current port zone (read only). 
OK (Grayed out). Displays an error message directing you to use a Telnet session to configure AppleTalk. 
Cancel Closes the dialog box. 
Frame Relay Configuration Dialog Box 
The Frame Relay Configuration dialog box, shown in Figure 5-10, controls the Frame Relay-related functions of the port that corresponds to the interface you selected from the device view. 

FIG 
Figure 5-10 Frame Relay Configuration Dialog Box 
Use this configuration dialog box to configure the Frame Relay Service and DLCIs to this interface. 
Dialog Box Options 
The Frame Relay Service section contains the following data fields and controls: 
·Interface Displays the name of the currently selected interface. 
·LMI Protocol Allows you to enable or disable LMI over the selected interface. Click the arrow icon to display a list of the available options. LMI allows the bridge/router to learn about all the nodes that are reachable on a particular interface. If LMI is selected, the Consortium LMI Protocol runs between the bridge/router and the data communications equipment (DCE). For more information, refer to the Frame Relay Service Parameters chapter in the NETBuilder Family Bridge/Router Reference Guide. 
The Interface-DLCI Definition section contains the following data fields and controls: 
·DLCI Allows you to enter a new DLCI number or select a previously entered DLCI number from the list. DLCI numbers must be integers in the range 16-991. For more information on DLCI numbers, refer to the Frame Relay Service Parameters chapter in the NETBuilder Family Bridge/Router Reference Guide. 
·Name Allows you to enter a name that will be associated with the DLCI number. 
·Add Allows you to enter a DLCI number to the list. 
·Delete Allows you to remove a DLCI number from the list. 
Other buttons: 
·OK Records your new settings. 
·Cancel Closes the dialog box without recording your new settings. 
Restrictions 
·The interface you are configuring for Frame Relay must be a WAN interface. If you open the Frame Relay Configuration dialog box when a non-WAN interface is selected, the dialog box control fields are disabled. In addition, the NETBuilder software must support Frame Relay. 
·You must configure and enable the Frame Relay Service before you can configure Boundary Routing over Frame Relay. 
Boundary Routing Configuration Dialog Box 
The Boundary Routing Configuration dialog box, shown in Figure 5-11, controls the functions related to Boundary Routing that corresponds to the interface you selected from the device view. 

FIG 
Figure 5-11 Boundary Routing Configuration Dialog Box 
NOTE: To configure Boundary Routing over Frame Relay, first configure Frame Relay from the Frame Relay Configuration dialog box. Then from the Boundary Routing Configuration dialog box, select the DLCI through which the NETBuilder system accesses the boundary router. 
Dialog Box Options 
The Boundary Routing Configuration dialog box contains the following data fields and controls: 
Enable and Disable Enables or disables Boundary Routing over Frame Relay. 
Interface Displays the number of the currently selected interface. (This interface is the parent port, not a virtual port.) 
Interface Owner Displays the current owner of the interface. 
DLCI Number Allows you to select a previously entered DLCI number from the list. DLCI numbers must be integers in the range 16-991. For more information on DLCI numbers, refer to the Frame Relay Service Parameters chapter in the NETBuilder Family Bridge/Router Reference Guide. (Not accessible unless the selected interface is configured for Frame Relay.) 
Interface - DLCI Name Displays the Interface - DLCI name for the selected DLCI. (Not accessible unless the selected interface is configured for Frame Relay.) 
IPX Smart Filtering Turns on IPX smart filtering when checked; turns off IPX smart filtering when unchecked. 
IP Address Allows you to enter the IP address of the local central node for the connection to the boundary router. This address is not necessary to configure Boundary Routing, but you need the IP address in order to access the boundary router by Telnet. 
Subnet Mask Allows you to enter the subnet mask for the above IP address. 
Remote IP Address Displays the IP address of the remote NETBuilder system. 
Remote LAN Type Selects the type of LAN to which the remote NETBuilder system is connected. 
OK Records your new settings. 
Cancel Closes the dialog box without recording your new settings. 
Restrictions 
You must configure and enable the Frame Relay Service before you can configure Boundary Routing over Frame Relay. 
IPX Policies Dialog Box 
You can configure IPX filters by defining a set of policies. Policies determine what can be received or advertised over a given port. Each defined policy filters packets coming from service, route, or neighbor sources. 
To display the IPX Policies dialog box displayed in Figure 5-12, from the Configure menu choose Filter then IPX Policy. 

FIG 
Figure 5-12 IPX Policies Dialog Box 
Dialog Box Options 
Filter Type Radio Buttons 
·Service Can be servers such as file or print servers. 
·Route Can be a single IPX network or a range of networks. 
·Neighbor Can be an individual neighboring node, identified by network number and MAC address. 
IPX Policies Dialog Box Table 
The IPX Policies dialog box table contains a table with four (five under some conditions) columns labeled as follows: 
·Interface Contains a box that allows you to choose any port or interface configured to route IPX. The interface identifier is discussed in "Interface Identifier Format". 
·Policy Type Allows you to select one of the following settings: Advertise, Receive, or Both. 
·Columns 3, 4, and 5 These column headings depend on the filter type selected. Available options are listed in Table 5-1 for each filter type. 
Table 5-1 Column Heading and Choices 
	 
Filter Type	 Column 3 Heading	 Column 4 Heading	 Column 5 Heading	 
Service	 Server Name	 Service Type	 	 
Options	 User defined (type in)	 File server, job server, print server, archive server, remote bridge server, advertising printer server (or enter a hexadecimal number, 1-4 digits. For more information on Service Types, refer to the Novell Service Descriptions table in the IPX Routing chapter in the NETBuilder Family Bridge/Router Operation Guide.	 	 
Route	 From Network	 To Neighbor	 	 
Options	 User defined (type in)	 User defined (type in)	 	 
Neighbor*	 RIP/SAP	 Neighbor Network	 Neighbor MAC Address	 
Options	 RIP or SAP	 User defined (type in)	 User defined (type in)	 

 , IPX Policy Dialog Box*When when both the NETBuilder system being managed is running software version 8.0or higher and the selected filter type is Neighbor, five columns appear in the table. 
Interface Identifier Format 
Information in the Interface column is displayed as follows: 
·If the interface routes or bridges Frame Relay, SMDS, X.25, or any other WAN protocol that requires the creation of a virtual port, the interface ID is presented in the format: 
: 
The virtual port name can contain up to eight characters. For example, if a virtual port named "SF_Main" is defined for interface 3, interface 3's ID will be displayed as follows:
3: SF_Main 
If the virtual port has no user-defined name, it is displayed as Port_Vn, where n is virtual port number assigned by the NETBuilder system to the virtual port. For example:
3: Port_V2 
·If the interface does not require virtual ports, the actual interface number is displayed. 
The exception is a NETBuilder II system with multiport interface adapters. In this case, the interface ID is the slot number followed by an alpha suffix denoting the position of the interface on the interface adapter card (A denotes the interface on the left, B the next interface to the right, and so forth). For example, if a three-interface card is in slot 2, the middle interface is identified as follows:
2B 
Row Section 
The row section of the dialog box contains the Add, Modify, and Delete buttons for adjusting the number of rows in the table to accommodate user-defined entries. The number of rows in the IPX Policies Dialog Box table is always one greater than the number of user-defined entries. The blank, bottom row is used to add a row to the table. 
·Add Button Allows you to enter the desired information in the blank, bottom row. Clicking the Add button updates the entire table and a new blank row appears at the bottom of the table if the SNMP set is successful. 
·Modify Button Allows you to change the current setting. The cursor remains in the table cell to be modified. Clicking the Modify button updates only the modified row if the SNMP set is successful. 
·Delete Button Allows you to delete a selected row. Click the Delete button to update the entire table, which occurs only if the SNMP set is successful. 
·Enable Button When you select any row in the table and click the Enable button, the Enable IPX Policy dialog box appears as shown in Figure 5-13. 

FIG 
Figure 5-13 Enable IPX Policy Dialog Box 
If the NETBuilder system being managed is running software version 8.0 or higher, the Action radio buttons under "Neighbor" are divided into two groups: RIP Action and SAP Action. 
Other buttons: 
·OK Records your new settings. 
·Cancel Closes the dialog box without recording your new settings. 
Mnemonic Filters Dialog Box 
The Mnemonic Filters dialog box allows you to configure and apply new IPX and bridging filters as well as to review, modify, or delete filters that are already configured on the NETBuilder system being managed. 
You can access the Mnemonic Filters dialog box from the Configure menu by choosing Filter then Mnemonic. The Mnemonic Filters dialog box is shown in Figure 5-14. 

FIG 
Figure 5-14 Mnemonic Filters Dialog Box 
Dialog Box Options 
The dialog box contains four sections of controls, which are labeled as follows: 
·Controls 
·Policy Definition 
·Filtered Packet Direction 
·Policy 
The Controls section contains the following controls: 
·Enable the filter policies Select 1st Match, All, or None. 1st Match enables the first policy that is able to filter any packet and disables all other policies. All enables all configured policies. None disables all policies. 
·Filter the following Bridge enables bridge filtering when checked. IPX enables IPX filtering when checked. 
·Unfiltered Packets Select Discard or Forward. Discard causes packets that do not match the filter criteria to be discarded. Forward causes packets that do not match the filter criteria to be forwarded. 
The Policy Definition section contains the following controls: 
·Name Select the name of an existing policy from the list box or type a new name. 
·Action Available actions include the following: Discard, Forward, Count, Sequence, priorityHigh, priorityMedium, priorityLow. There is no SNMP support for the action X.25 Profile ID, so policies that contain this action will be read-only. DodDiscard priorityHigh, priorityMedium, and priorityLow are supported in software version 8.2 and later. 
·Masks Lists the currently selected masks. Available masks are all masks currently defined for the NETBuilder system being managed. To create or modify a list of masks, click the Mask List button to display the Mnemonic Masks List dialog. 
The Filtered Packet Direction section contains the following controls: 
·Interface list selection Determines how packets are filtered through the transmitting interface. Available choices include the following: 
·all interfaces Filters are applied to all packets handled by all interfaces. 
·at List 1 Filters are applied to all packets handled by the interfaces specified in the List 1 field. 
·from List 1 Filters are applied to all packets transmitted by the interfaces specified in the List 1 field. 
·from List 1 to List 2 Filters are applied to all packets transmitted by any interface specified in the List 1 field and destined for any interface specified in the List 2 field. 
·to List 1 Filters are applied to all packets received by the interfaces specified in the List 1 field. 
·between List 1 and List 2 Filters are applied to all packets moving between any interface specified in the List 1 field and any interface specified in the List 2 field, in either direction. 
·among List 1 Filters are applied to all packets moving between any interface specified in the List 1 field and any other interface specified in the List 1 field. 
·List 1 Click this button to display the Mnemonic Interfaces List dialog box. The interfaces you specify appear in the List 1 box. 
·List 2 Click this button to display the Mnemonic Interfaces List dialog box. The interfaces you specify appear in the List 2 box. 
The Policy section contains the following controls: 
·Add Click the Add button to perform validation checks and, if those checks are successful, to send an SNMP request to update the NETBuilder system. 
·Modify The Modify button is active whenever a policy is displayed for which you have changed the contents of any field except the Name field (if you change the Name field, the Modify button becomes inactive and the Add button is active). To change a filter definition, select and change the definition before pressing the Modify button. 
·Delete To delete a filter, use the Name list box to select the desired filter name and then click the Delete button. A message box appears asking for confirmation. 
Other buttons: 
·OK Applies (using SNMP SET operations) the settings specified from the Controls section of the Mnemonic Filters dialog box. The OK button does not create or delete the filter policies. 
Mnemonic Masks List Dialog Box 
You can access the Mnemonic Masks List dialog box from the Mnemonic Filters dialog box by clicking the Masks List button. Use this dialog box to add or delete masks from the list of masks to be applied to the mnemonic filter currently being configured in the Mnemonic Filters dialog box. Up to four masks can be applied to a policy; masks to be applied are displayed in a read-only list box labeled Masks in the Mnemonic Filters dialog box. 
The Mnemonic Masks List dialog box is shown in Figure 5-15. 

FIG 
Figure 5-15 Mnemonic Masks List Dialog Box 
The Mnemonic Masks List dialog box contains two lists of masks: 
·Masks to choose from 
Masks that apply to bridged packets are prefaced with "brg"; masks that apply to routed packets are prefaced with "ipx"; user-defined masks are prefaced with "user." 
·Masks to apply 
To add a mask to the list of masks to be applied, select a mask in the Masks to choose from list and click the Add button (or double-click the selection in the Masks to choose from list). 
To delete a mask from the list of masks to be applied, select a mask in the Masks to be applied list and click the Remove button (or double-click the selection in the Masks to apply list) 
When you are finished, click the OK button to close the Mnemonic Masks List dialog box and return to the Mnemonic Filters dialog box. 
The application does not support mask creation or editing. For details on creating masks, refer to the NETBuilder Family Bridge/Router Operation Guide. 
Mnemonic Interfaces List Dialog Box 
You can access the Mnemonic Interfaces List dialog box from the Mnemonic Filters dialog box by clicking the List 1 or List 2 button. When configuring a filter in the Mnemonic Filters dialog box, use this dialog box to add or delete interfaces from the list of interfaces to which mnemonic filters will be applied. 
The Mnemonic Interfaces List dialog box is shown in Figure 5-16. 

FIG 
Figure 5-16 Mnemonic Interfaces List Dialog Box 
If you opened the Mnemonic Interfaces List dialog box by clicking the List 1 or List 2 button in the Mnemonic Filters dialog box, the interfaces you specify appear in List 1 or List 2 respectively. 
These lists, which appear in the Mnemonic Filters dialog box, contain the numbers of those interfaces to which the mnemonic filter policy being configured will apply. You can specify that only packets moving in a specified direction will be filtered (for example, packets moving from any of the interfaces in List 1 to any of the interfaces in List 2). 
The Mnemonic Masks List dialog box contains two lists of interfaces: 
·Interfaces to choose from 
·Interfaces to apply 
To add an interface to the list of interfaces to be applied, select an interface in the Interfaces to choose from list and click the Add button (or double-click the selection in the Interfaces to choose from field). 
To delete an interface from the list of interfaces to be applied, select an interface in the Interfaces to apply list and click the Remove button (or double-click the selection in the Interfaces to apply field). 
When you are finished, click the OK button to close the Mnemonic Interfaces List dialog box and return to the Mnemonic Filters dialog box. 
Accessing the NETBuilder Console Using Telnet 
The NETBuilder console is the text-based menu interface to the NETBuilder software described in the NETBuilder Family Bridge/Router Operation Guide. To perform any of the tasks available from the NETBuilder console through Transcend Enterprise Manager, refer to the next procedure. When you are done, refer to Ending a Telnet Session. 
Starting a Telnet Session 
To access the NETBuilder console from Enterprise Manager, follow these steps: 
1Configure Enterprise Manager to recognize your Telnet program. 
aFrom the File menu, choose Preferences from the subnet window. 
bIn the Preferences dialog box, type the Telnet application file name in the Misc. section (for example, TELNET.EXE). 
cClick OK. 
2From the subnet window, click the right mouse button on the desired NETBuilder system and choose Telnet Session from the menu. 
The following prompt appears on your console: 
NetLogin... 
3Log in by entering your account name. 
For example, to use the default account name, enter the following account name: 
root 
The following prompt appears on your console: 
Password: 
4Enter the password, then press the Enter key. 
If no password is assigned, press the Enter key without typing anything. 
The system prompt appears on your console: 
NETBuilder  
5To display the main menu, enter the following command: 
menu 
Ending a Telnet Session 
To end a Telnet session, follow these steps: 
1From the NETBuilder menu, press the Enter key without entering a menu selection. 
The following system prompt appears on your console: 
NETBuilder  
2Prepare the NETBuilder system to receive another Telnet-based console session by entering the following command: 
listen 
3End the Telnet session by closing the Telnet window. 
Be sure to follow this procedure when ending a Telnet session. Otherwise, you will need to directly access the NETBuilder system though a physical console connection before you can again access the console through Telnet. 
 6 Monitoring a NETBuilder System 
This chapter contains the following topics: 
·Monitoring a Single Interface or All Interfaces 
·Displaying Utilization Graphs 
·Displaying IP Graphs 
·Displaying Dial-on-Demand Graphs 
·Setting the Polling Frequency 
·Threshold Configuration and Notification versus Alarm Manager 
·Making Enterprise Manager a Read-Only Tool 
Monitoring a Single Interface or All Interfaces 
You can display utilization graphs for a single interface or for all interfaces as shown in Figure 6-1. The following conventions determine whether a single-interface or multiple-interface graphs are displayed: 
·A graph contains data for a single interface if an I/O module is selected in the device view prior to launching the graph. 
·A graph contains data for all installed interfaces if the CEC module or NETBuilder chassis is selected in the device view prior to launching the graph. 

FIG 
Figure 6-1 Displaying Data for One or All Interfaces 
Displaying Utilization Graphs 
You can monitor NETBuilder utilization with two performance graphs: 
·Peak utilization 
·Average utilization 
To display utilization graphs, follow these steps: 
1Decide whether you want to display the graph for all installed interfaces or for a single interface: 
aHighlight the CEC module or NETBuilder chassis to graph data for all installed interfaces. 
bHighlight an individual I/O module or NETBuilder chassis to graph data for one interface only. 
2From the File menu, choose Preferences then Polling Frequency. 
Verify that the polling frequency is set to 5 minutes (the default). 
3If you want to display both peak and average utilization graphs, follow these steps: 
aOpen the Info View dialog box by double-clicking the selected interface. 
bIn the View Stats section, check the Utilization check box and click the OK button. 
The graphs immediately appear. 
cMake sure that the selected interface is the active window. 
dFrom the Window menu, click Refresh to initiate another polling session. 
You may need to refresh several times so that the graph can be updated with new information. 
eTo view both graphs at once, from the Window menu, choose Tile. 
fGo to step 5. 
4If you want to display peak or average utilization graph, follow these steps: 
aFrom the View menu, choose Utilization Graphs then Peak Utilization or Average Utilization. 
The graph immediately appears. 
bMake sure that the selected interface is the active window. 
cFrom the Window menu, click Refresh to initiate another polling session. 
You may need to refresh several times so that the graph can be updated with new information. 
5When you have finished viewing the graph, close the window. 
Displaying IP Graphs 
By displaying all four types or individual IP performance graphs, you can monitor NETBuilder IP performance system-wide. The four types of IP performance graph are as follows: 
·Activity/Errors 
·Errors 
·Frame Types 
·Traffic 
Figure 6-2 shows a representative IP graph. 

FIG 
Figure 6-2 IP Activity/Errors Graph 
Data points in the performance graphs represent the change in value between successive polling intervals. 
Displaying All Four Types of IP Performance Graphs 
You can display all four types of IP performance graphs at one time. The graphs are displayed in the window format (Cascade or Tile) that was chosen most recently from the Window menu. 
To display all four types of IP performance graphs, follow these steps: 
1From the device view, double-click any I/O port. 
2From the File menu, choose Preferences then Polling Frequency. 
Verify that the polling frequency is set to 5 minutes (the default). 
3From the Configure menu, choose Device/Subnetwork to open the Info View dialog box. 
aIn the View Stats section, check the IP check box. 
bClick the OK button. 
The graphs immediately appear. 
4Make sure that the selected interface is the active window. 
From the Window menu, click Refresh to initiate another polling session. 
You may need to refresh several times so that the graphs can be updated with new information. 
5From the Window menu, choose Tile to see all performance graphs at once. 
6When you are done viewing the graphs, close the windows. 
Displaying Individual IP Performance Graphs 
To display a single performance graph from the device view, follow these steps: 
1From the View menu, choose IP Graphs and one of the following graph types: 
·Activity/Errors 
·Errors 
·Frame types 
·Traffic 
2From the File menu, choose Preferences then Polling Frequency. 
Verify that the polling frequency is set to 5 minutes (the default). 
3Make sure that the selected interface is the active window. 
From the Window menu, click Refresh to initiate another polling session. 
You may need to refresh several times so that the graph can be updated with new information. 
4When you are done viewing the graph, close the window. 
Displaying Dial-on-Demand Graphs 
By displaying all three types or individual dial-on-demand (DOD) performance graphs, you can monitor DOD performance on a single-interface basis. The three types of DOD performance graph are as follows: 
·Call statistics 
·Up time 
·Packets out 
The DOD graphs are only available for agents running software version 8.0 or later. 
Data points in the performance graphs represent the change in value between successive polling intervals. 
Displaying All Three Types of DOD Performance Graphs 
You can display all three types of DOD performance graphs at one time. The graphs are displayed in the window format (Cascade or Tile) that was chosen most recently from the Window menu. 
To display all three types of DOD performance graphs, follow these steps: 
1From the device view, double-click the interface for which you want to graph DOD performance. 
2From the File menu, choose Preferences then Polling Frequency. 
Set the polling frequency to 30-60 minutes (using long polling frequencies is the best way to monitor DOD usage). 
3From the Configure menu, choose Device/Subnetwork to open the Info View dialog box. 
aIn the View Stats section, check the Dial On Demand check box. 
bClick the OK button. 
The graphs immediately appear. 
4Make sure that the selected interface is the active window. 
From the Window menu, click Refresh to initiate another polling session. 
You may need to refresh several times so that the graphs can be updated with new information. 
5From the Window menu, choose Tile to see all performance graphs at once. 
6When you are done viewing the graphs, close the windows. 
Displaying Individual DOD Performance Graphs 
To display a single performance graph from the device view, follow these steps: 
1From the device view, double-click the interface for which you want to graph DOD performance. 
2From the File menu, choose Preferences then Polling Frequency. 
Set the polling frequency to 30-60 minutes (using long polling frequencies is the best way to monitor DOD usage). 
3From the View menu, choose DOD Graphs and one of the following graph types. 
·Call 
·Up time 
·Packets out 
4Make sure that the selected interface is the active window. 
From the Window menu, click Refresh to initiate another polling session. 
You may need to refresh several times so that the graph can be updated with new information. 
5When you are done viewing the graph, close the window. 
Setting the Polling Frequency 
The polling frequency setting determines how often the device view and active graphs are updated. To change the polling frequency, follow these steps: 
1From the File menu, choose Preferences then Polling Frequency. 
The polling frequency dialog box appears as shown in Figure 6-3. 

FIG 
Figure 6-3 Polling Frequency Dialog Box 
The current setting is displayed in minutes. You can type over the current setting or use the up and down arrow keys to increment/decrement the setting. The range is 1-60. 
2Enter the new polling frequency and click the OK button. 
Threshold Configuration and Notification versus Alarm Manager 
Thresholds and alarms are important aids to help you manage your network. The NETBuilder Manager Threshold Configuration feature offers enhanced preconfigured NETBuilder-specific monitoring and notification capabilities. 
Use the NETBuilder Threshold Configuration feature if a NETBuilder system is sending traps and you need more information to determine the cause. The NETBuilder Threshold Configuration feature allows you to monitor conditions that are not accessible through RMON or the Alarm Manager. 
The disadvantage of using the NETBuilder Threshold Configuration feature is increased network traffic because of polling. For this reason, the NETBuilder Threshold Configuration feature is recommended for troubleshooting purposes after you have narrowed the problem down to a single NETBuilder system. However, you can use this feature when monitoring dial-on-demand conditions using long polling intervals (30-60 minutes). 
The Alarm Manager (a generic, enterprise-wide RMON utility) allows you to set alarms and events to enhance network performance and prevent network downtime. The Alarm Manager can be used to configure thresholds on multiple NETBuilder systems. A threshold is set against a single event and when exceeded, a trap is sent to the management station. 
An advantage of using the Alarm Manager instead of the NETBuilder Threshold Configuration feature is that the alarms and events are generated without polling, which reduces network utilization. However, NETBuilder systems do not retain RMON configuration information when the system is powered off. You must reconfigure any alarms when you power on the system. For this reason, you may want to keep a written note of important alarms you set for each NETBuilder system. 
NOTE: You can find an overview of using alarms and detailed information about using the Alarm Manager are provided in the Enterprise Manager Utilities chapter in the Transcend Enterprise Manager for Windows User Guide Volume 1. You can access the Alarm Manager from the View menu by choosing Alarm Manager. 
Configuring Thresholds 
The NETBuilder Threshold Configuration dialog box allows you to set thresholds for various predefined events. The threshold utility notifies you of threshold violations by displaying the Threshold Notification Viewer dialog box when notification events occur. You specify the number of threshold violations that must occur before a notification event is generated. 
You can also use the Alarm Manager application to set up and modify static alarms and events on a NETBuilder system using RMON. For more information, refer to "Threshold Configuration and Notification versus Alarm Manager". 
To configure thresholds, follow these steps: 
NOTE: If you change the values in the Threshold Configuration dialog box, the new values are retained between executions. 
1Click the Enable radio button above the Events column to enable threshold monitoring. 
2Click the OK button to confirm your changes. 
For more advanced configurations, follow these steps: 
1In the device view, select the interface for which you want to configure thresholds, or select the CEC module or chassis to configure thresholds system-wide. 
2From the File menu, choose Preferences then Threshold Configuration to open the Threshold Configuration dialog box. 
The Threshold Configuration Dialog box, shown in Figure 6-4, appears. 

FIG 
Figure 6-4 Threshold Configuration Dialog Box 
NOTE: If an interface is selected, events apply to the selected interface. If the CEC module or chassis is selected, events apply to the entire NETBuilder system. 
Events for which thresholds can be configured vary by media, protocol, and service. For more information, refer to "Descriptions of Threshold Events". 
3Adjust the Threshold by selecting the field and double-clicking to get a flashing delta text pointer. 
aUse the text pointer to highlight just the characters you want to change. 
bType the desired new characters over the highlighted text. 
4Adjust the Notify setting by clicking the arrow to the right of the Notify field to display a list of available settings. 
Click the desired setting. 
5Repeat steps 3 and 4 for all event types for which you want to change threshold settings. 
Descriptions of Threshold Events 
Events are categorized into three groups: the Interfaces Group, the Internet Protocol Group, and the Dial on Demand Group. The events for each of these groups are described in the following sections: 
Interfaces Group 
Unknown Protocols The number of packets received through the interface that were discarded because of an unknown or unsupported protocol. 
Operational Status The current operational state of the interface. 
Errors In The number of inbound packets that contained errors preventing them from being delivered to a higher-layer protocol. Input errors may indicate problems with data being received, such as frames that are too large or too small, or transmission clocking problems. 
Errors Out The number of outbound packets that could not be transmitted because of errors. Output errors can be the result of problems with the physical media, such as synchronization loss on a serial link, or a problem with the sending system. 
Discards In The number of inbound packets that were chosen to be discarded even though no errors were detected to prevent them from being delivered to a higher-layer protocol. A reason for discarding a packet is to make buffer space available. 
Discards Out The number of outbound packets that were chosen to be discarded even though no errors were detected to prevent them from being transmitted. A reason for discarding a packet is to make buffer space available. 
Nonunicast In The number of nonunicast (for example subnetwork-broadcast or subnetwork-multicast) packets delivered to a higher-layer protocol. 
Nonunicast Out The total number of packets, including those that were discarded or not sent, that higher-layer protocols requested to be transmitted to a nonunicast (for example, a subnetwork-broadcast or subnetwork-multicast) address. 
WAN/Ethernet/Token Ring/FDDI/Other Media Average Utilization  Average utilization exceeds the specified percentage. 
WAN/Ethernet/Token Ring/FDDI/Other Media Peak Utilization Peak utilization is less than the specified percentage. 
WAN/Ethernet/Token Ring/FDDI/Other Media Peak Utilization  Peak utilization exceeds the specified percentage. 
Internet Protocol Group 
Routing Discards The number of routing entries that were chosen to be discarded even though the entries were valid. A reason for discarding an entry is to free-up buffer space for other routing entries. 
Address Errors In The number of input datagrams discarded because the IP address in the IP header's destination field was not a valid address. This count includes invalid addresses (for example, 0.0.0.0) and addresses of unsupported classes (for example, Class E). For devices that are not IP gateways and do not forward datagrams, this counter includes datagrams discarded because the destination address was not a local address. 
No Routes Out The number of IP datagrams discarded because no route could be found to transmit them. This counter includes any packets counted in ipForwDatagrams that meet this no-route criteria and any datagrams that a host cannot route because all of its default gateways are down. 
Header Errors In The number of input datagrams discarded because of IP header errors, bad checksums, version number mismatches, format errors, time-to-live values exceeded, errors discovered in processing IP options, and so forth. 
Unknown Protocols In The number of locally-addressed datagrams successfully received but discarded because of an unknown or unsupported protocol. 
Discards In The number of input IP datagrams that were chosen for discard even though no errors were detected to prevent them from being delivered to a higher-layer protocol. A reason for discarding a packet would be to free up buffer space. This counter does not include any datagrams discarded while awaiting reassembly. 
Discards Out The number of output IP datagrams that were chosen for discard even though no errors were detected to prevent them from being transmitted. A reason for discarding a packet would be to free up buffer space. This counter includes datagrams counted in ipForwDatagrams if these packets met the discretionary discard criteria. 
Delivers In The total number of input datagrams successfully delivered to IP user-protocols (including ICMP). 
Requests Out The total number of IP datagrams that local IP user-protocols (including ICMP) supplied to IP for transmission. This counter does not include any datagrams counted in ipForwDatagrams. 
Forwarding Datagrams The number of input datagrams for which this device was not the final IP destination. An attempt is made to find a route to forward them to their final destination. For devices that do not act as IP gateways, this counter includes only those packets that were source routed through this device, and the source route option processing was successful. 
Dial On Demand Group 
Calls Failed The total number of DOD call attempts that failed to establish a connection. 
Up Time  Generates a threshold notification if the DOD connection exceeds the specified duration. 
Viewing Threshold Violations 
The Threshold Notification Viewer dialog box appears whenever a threshold notification event occurs. To display this dialog box at any time, choose Threshold Viewer from the View menu. 

FIG 
Figure 6-5 Threshold Notification Viewer Dialog Box 
The Threshold Notification Viewer dialog box contains the following read-only data fields and controls: 
Dialog Box Options 
Event Displays the event type for which the threshold violation was reported. Each reported event corresponds to an event type specified in the Threshold Configuration dialog box. 
Interface Displays the interface, if any, for which the threshold violation was reported. 
Times Displays the number of threshold violation notification events that occurred. 
Most Recent Displays the date and time of the most recent threshold violation notification event. 
Last Value Displays the event value that existed when the most recent threshold violation notification event was generated. 
Threshold Displays the threshold setting that was in effect when the most recent threshold violation notification event was generated. 
Close Closes the Threshold Notification Viewer dialog box until the next violation occurs. 
Clear Clears the event table in the Threshold Notification Viewer dialog box. 
Making Enterprise Manager a Read-Only Tool 
You can configure the Enterprise Manager as a read-only tool that is capable of monitoring, but not managing, one or more NETBuilder systems on the network. 
The Enterprise Manager generates an error message any time you try to perform an SNMP set operation on a NETBuilder system for which the Enterprise Manager is configured as a read-only tool. 
To make the Enterprise Manager a read-only tool, follow these steps: 
1From the subnetwork-level window, select the NETBuilder system you want the Enterprise Manager to treat as a read-only device. 
2From the Configure menu, choose Device/Subnetwork. 
3In the 3Com Configuration dialog box, from the Authorize menu, choose Community Names. 
4Copy the contents of the Read Community String field to the Write Community String field. 
5Click the OK button. 
6Repeat steps 1-4 for each NETBuilder system you want the Enterprise Manager to treat as a read-only device. 
 A Devices Supported 
This appendix lists the devices supported by Transcend Enterprise Manager V5.0. It contains the following sections: 
·Hubs 
·Switches 
·NETBuilder Routers 
·Accessories 
·Obsolete Devices 
Hubs 
Transcend Enterprise Manager for Windows version 5.0 supports the following hubs. For a detailed list of the units and accessories supported, refer to the appropriate section. A list of accessories and other hubs that are supported is provided at the end of this section: 
·SuperStack II Hub 10 
·SuperStack II Hub 100 
·SuperStack II Hub TR 
·LinkBuilder TR Series 
·OfficeConnect Hub/8TPM 
·LinkBuilder FDDI Hub 
·LinkBuilder MSH Hub 
SuperStack II Hub 10 
The SuperStack II Hub 10 range consist of several manageable units that can be used singularly or connected together to form a stack. Several units can be stacked together to form a single logical repeater. See the manual supplied with the Hub 10 unit for stacking instructions. You can also include LinkBuilder FMS and 10BT/10BTi units (see Accessories on page A-15) in a stack.
FIG 
Figure A-1 SuperStack Hub 10 
You can manage the stack by installing either an FMS Management Module (3C16030) or FMS II Bridge/Management Module (3C16040) in one of the Hub 10 units. 
You can manage a hub on a network running either IP or IPX, or both. If your network is running IPX, Autodiscovery identifies the hub and adds it to the subnetwork view. You must be running the FMS Management Agent software Version 2.0 or later to access all the features described in this manual. 
Enterprise Manager supports the following units: 
·6-Port fiber - 3C16665A 
·12-Port TP - 3C16670A 
·24-Port TP - 3C16671A 
·24-Port Telco - 3C16672A 
·48-Port System Solution - 3C16674B 
·48-Port System Solution/24 - 3C16675B 
SuperStack II Hub 100 
The SuperStack II Hub 100 provides full 100Mbps connectivity to significantly boost transmission speeds. Up to eight Hub 100's can be stacked in a Class 1 Fast Ethernet topology. 

FIG 
Figure A-2 SuperStack II Hub 100 
Enterprise Manager supports the following units and accessories: 
·Hub 100TX - 3C250-TX/IA 
·Hub 100T4 - 3C250-T4 
·100BASE-TX Transceiver Module - 3C252-TX 
·100BASE-FX Transceiver Module - 3C262-FX 
SuperStack II Hub TR 
The SuperStack II Hub TR range are ideal for dynamic mission-critical Token Ring environments. In the central wiring closet, you can use Hub TR's with cascade connectors to link up to 20 hubs in one rack - supporting up to 260 users. 
Enterprise Manager supports the following units and accessories: 
·12 Port Hub - 3C510500 and 3C510510 
·24 Port Hub - 3C510501 and 3C510511 
·RMON Management Agent Module - 3C510502 
·Advanced RMON Management Agent Module -3C510505 
·Fiber RI/RO Expansion Module - 3C510503 
·Copper RI/RO Expansion Module - 3C510504 
·Copper/Fiber RI/RO Expansion Module - 3C510506 
·Redundant Power System - 3C565047 
LinkBuilder FMS II 
Enterprise Manager supports the following units: 
·6-Port fiber - 3C16665 
·12-Port TP - 3C16670 
·24-Port TP - 3C16671 
·24-Port Telco - 3C16672 
·48-Port System Solution - 3C16674A 
·48-Port System Solution/24 - 3C16675A 
LinkBuilder FMS 
Enterprise Manager supports the following units: 
·Hub 100 - 3C250-TX/I 
LinkBuilder TR Series 
The entry-level LinkBuilder TR model is an unmanaged 16-port unit. Full SNMP RMON management of up to 15 additional LinkBuilder TR hubs is provided by adding a LinkBuilder TRi Model 2 unit. 

FIG 
Enterprise Manager supports the following units: 
·TR - 3C510180 
·TRi Model 2 - 3C510181 
OfficeConnect Hub/8TPM 
The Office Connect Hub/8TPM (3C16710) is ideal for creating a small network. It is compact and attractively designed for desktop use. A single OfficeConnect hub allows you to create a small network with up to eight workstations. 

FIG 
Figure A-3 Hub/8TPM 
LinkBuilder FDDI Hub 
The LinkBuilder FDDI Hub provides an affordable way to open up a 100Mbps bandwidth pipeline to devices such as servers and workstations, allowing you to eliminate throughput bottlenecks and improve performance. 
Enterprise Manager supports the following units: 
·FDDI Base Unit - 3C780 
·FDDI Management Module - 3C781 
·FDDI UTP Module - 3C784 
·FDDI STP (SDDI) Module - 3C783 
·FDDI Fiber-Optic Module - 3C782 
·FDDI Fiber and CDDI Module - 3C785 
LinkBuilder MSH Hub 
The LinkBuilder Multi-Services Hub (MSH) is an 11-slot chassis-based hub that can connect large, mixed technology, mixed media LANs and can be managed if you install an MSH Management Module (3C18500) in the chassis. With MSH you can connect up to 10 managed Ethernet, five managed Token Ring, or three FDDI Enterprises. Alternatively you can interconnect up to three Ethernet and five Token Ring WorkGroups across the backplane. 

FIG 
Figure A-4 MSH Hub 
To manage all the features described in this manual you must have a LinkBuilder MSH Management Module running agent software version 4.1 or later. 
Intelligent modules have their own IP address. When these modules are discovered by Enterprise Manager they are represented by an MSH module icon. When Autodiscovery searches your network for devices, it treats each device with an IP or IPX address as a separate entity, so even though these modules are housed in an MSH chassis they are also shown separately on your network map (this enables you to work with an MSH chassis and intelligent modules that are on different networks). Double-clicking on an MSH module icon has no effect. 
Enterprise Manager supports the following units: 
·MSH Chassis - 3C18040 
·MSH Chassis with FDDI Backplane - 3C18041 
·MSH Management Module - 3C18500 
·13-Port 10BASE-T Repeater Module - 3C18120A 
·12-Port 10BASE-T Repeater Module - 3C18121A 
·24-Port 10BASE-T Repeater Module - 3C18122A 
·7-Port 10BASE-T Repeater Module - 3C18124A 
·Fiber-Optic Repeater Module - 3C18135A 
·Coax Repeater Module - 3C18140A 
·Fiber-Optic Expansion Module - 3C18136 
·Coax Expansion Module - 3C18141 
·Transceiver Interface Expansion Module - 3C18146 
·4-Port Ethernet Bridge Module - 3C18600 
·UTP MAU Module - 3C18200 
·STP MAU Module - 3C18201 
·Advanced MAU Module - 3C18202 
·STP RingBuilder Module - 3C18241 
·Fiber RingBuilder Module - 3C18240 
·2-Port Token Ring Bridge Module - 3C18620 
·Token Ring RMON Probe Module- 3C18250 
·LinkSwitch 1000 Module - 3C18400 
·LinkSwitch 1000 Expansion Module - 3C18405 
·Switch 1005 Module - 3C184000 
·Switch 1005 Expansion Module- 3C184005 
·LinkSwitch 1200 Module - 3C18640 
·LinkSwitch 1200 Expansion Module - 3C18645 
·FDDI MIC Media Module - 3C18320 
·FDDI Fiber-Optic Module - 3C18300 
·FDDI UTP Module - 3C18301 
·FDDI RingBuilder Module - 3C18310 
Switches 
3Com switches enhance your network's performance by creating "microsegments" that are interconnected using a high-speed switching matrix. Microsegmenting means that a switched node does not share bandwidth with other nodes, even when they share the same port - which translates to dramatic increases in performance. 
SuperStack II Switches 
You must be running the management agent software Version 4.2.0 or later to access the features described in this manual. 

FIG 
Figure A-5 Switch 1000 With Transceiver Module 
You can manage the following SuperStack II units using Enterprise Manager: 
·Switch 1000 12-Port - 3C16901A 
·Switch 1000 24-Port - 3C16900A 
·Switch 2200 - 3C220000A 
·Switch 3000 FX- 3C16940A 
·Switch 3000 TX - 3C16941A 
Transcend recognizes the following devices but cannot manage them. 
·Switch 2700 (12 10BASE-T, 1 OC-3a ATM) - 3C220000A 
·Switch 2700 (12 10BASE-T)- 3C220001A 
LANplex 2500 
You must be running the LANplex 2500 software Version 7.0.0 or later to access the features described in this manual. 

FIG 
Figure A-6 LANplex 2500 
You can manage the following units using Enterprise Manager: 
·LANplex 2500 (1 power supply) - 3C250100 
·LANplex 2500 (2 power supplies) - 3C250200 
·Ethernet module (8 ports, 10BASE-T, RJ-45) - 3C201000 
·Ethernet module (8 ports, 10BASE-T, RJ-21) - 3C201100 
·Ethernet module (8 ports, 10BASE-2, BNC) - 3C201200 
·Ethernet module (8 ports, 10BASE-2, unterminated BNC) - 3C2012xx 
·Ethernet module (4 ports, 10BASE-5, AUI) - 3C201300 
·Ethernet module (8 ports, 10BASE-FL, FOIRL) - 3C201400 
·Fast Ethernet module (100BASE-TX, RJ-45) - 3CC200500 
·FDDI module (1 port, DAS fiber MIC) - 3C200100 
·TP-DDI module (1 port, DAS TP) - 3C200300 
·FDDI module (2 port, DAS single mode fiber MIC) - 3C200400 
LANplex 6000 
You must be running the LANplex 6000 software Version 7.0.0 or later to access the features described in this manual. 

FIG 
Figure A-7 LANplex 6004 
You can manage the following units using Enterprise Manager: 
·LANplex 6012 chassis (12 slots, 1 power supply) - 3C6012-001 
·LANplex 6012 chassis (12 slots, 2 power supplies) - 3C6012-002 
·LANplex 6004 chassis (4 slots, 1 power supply) - 3C6004-001 
·Management module, Multimode (1 MICs, 1 MAC) - 3C6311-001 
·Management module, Multimode (2 MICs, 3 MACs) - 3C6311-003 
·Management module, Multimode and Single Mode (Port A: single mode; Port B: multimode,2 MICs, 1 MAC) - 3C6311-101 
·Management module, Multimode and Single Mode (Port A: single mode; Port B: multimode,2 MICs, 3 MACs) - 3C6311-103 
·Management module, Multimode and Single Mode (Port A: multimode; Port B: single mode, 2 MICs, 1 MAC) - 3C6311-011 
·Management module, Multimode and Single Mode (Port A: multimode; Port B: single mode,2 MICs, 3 MACs) - 3C6311-013 
·Management module, Single Mode (2 MICs, 1 MAC) - 3C6311-111 
·Management module, Single Mode (2 MICs, 3 MACs) - 3C6311-113 
·FDDI concentrator module (6 master ports, multimode, SC) - 3C6202-0000 
·FDDI concentrator module (12 master ports, UTP, RJ-45) - 3C6203-0000 
·Ethernet/FDDI switching module (16 Ethernet ports, 10BASE-T, RJ-45; 2 FDDI ports to backplane) - 3C6555-016R 
·Ethernet/FDDI switching module (16 Ethernet ports, 10BASE-T, RJ-21 Telco; 2 FDDI ports to backplane) - 3C6555-016T 
·Ethernet/FDDI switching module (16 Ethernet ports, 10BASE-T, RJ-45; 2 FDDI ports, 1 to backplane, 1 to external TP-DDI SAS, RJ-45) - 3C6555-116R 
·Ethernet/FDDI switching module (16 Ethernet ports, 10BASE-T, RJ-45; 2 FDDI ports, 1 to backplane, 1 to external FDDI SAS, MIC) - 3C6555-216R 
·Ethernet/FDDI switching module (16 Ethernet ports, 10BASE-FL, ST; 2 FDDI ports to backplane) - 3C6555-016F 
·Ethernet/FDDI switching module (16 Ethernet ports, 10BASE-FL, ST; 2 FDDI ports, 1 to backplane, 1 to external TP-DDI SAS, RJ-45) - 3C6555-116F 
·Ethernet/FDDI switching module (16 Ethernet ports, 10BASE-FL, ST; 2 FDDI ports, 1 to backplane, 1 to external FDDI SAS, MIC) - 3C6555-216F 
·Ethernet/FDDI switching module (16 Ethernet ports, 10BASE-2, BNC; 2 FDDI ports to backplane) - 3C6555-016B 
·Ethernet switching module (8 ports, 10BASE-T, RJ-45) - 3C6111-618R 
·Ethernet switching module (8 ports, 10BASE-T, RJ-21 Telco) - 3C6111-618T 
·Ethernet switching module (8 ports, 10BASE-FL, ST) - 3C6111-618F 
·Ethernet switching module (4 ports 10BASE-FL, ST; 4 ports 10BASE-T, RJ-45) - 3C6111-614F 
·Ethernet switching module (8 ports, 10BASE-2, BNC) - 3C6111-618B 
·Ethernet switching module (4 ports, AUI) - 3C6111-614A 
·Token Ring switching module (TRSM) (8 Token Ring ports, STP, RJ-45) - 3C6408-000 
·Tri-media module (16 ports, 10BASE-T, RJ-45; 1 port, 100BASE-TX, RJ-45; 1 FDDI port to backplane) - 3C6555-516R 
LinkSwitch 
You must be running the management agent software Version 4.2.0 or later to access the features described in this manual.
FIG 
Figure A-8 LinkSwitch 1200 
You can manage the following LinkSwitch units using Enterprise Manager: 
·LinkSwitch 500 - 3C30500 
·LinkSwitch 1000 12-Port - 3C16901 
·LinkSwitch 1000 24-Port - 3C16900 
·LinkSwitch 1200 - 3C16640 
·LinkSwitch 2200 - 3C220000 
·LinkSwitch 2700- 3C327000 
·LinkSwitch 2700- 3C327001 
·LinkSwitch 3000 - 3C16940 
·LinkSwitch 3000 TP - 3C16941 
NETBuilder Routers 
The NETBuilder units that can be managed are: 
·NETBuilder Remote Office 
·NETBuilder MP 
·NETBuilder II 
·NETBuilder I 
NETBuilder II Modules 
·All NETBuilder II Modules are supported. 

FIG 
Figure A-9 NETBuilder II 
NETBuilder Software 
·NETBuilder 6.2 Software 
·NETBuilder 7.0 Software 
·NETBuilder 7.1 Software 
·NETBuilder 7.2 Software 
·NETBuilder 8.0 Software 
·NETBuilder 8.1 Software 
·NETBuilder 8.2 Software 
·NETBuilder 8.3 Software 
All NETBuilder devices recognized by Autodiscovery are represented by icons. However, only those NETBuilders with supported software installed are manageable using this application. NETBuilders not listed above will be discovered as "generic" devices and are manageable only through a Telnet session. 
All NETBuilder I systems running version 6.2 or later software will be discovered using the Autodiscovery feature. These systems will be displayed in the subnetwork-level window using the NETBuilder II icon. 
If you have difficulty discovering or displaying correct information for NETBuilder systems, check that the NETBuilder system's SNMP parameters are set correctly. For more information, refer to the NETBuilder documentation describing SNMP configuration. 
Accessories 
Enterprise Manager supports the following accessories: 
·AUI Transceiver Module -- 3C12060 
·Fiber Optic Transceiver Module (SMA) - 3C12061 
·TP Transceiver Module - 3C12063 
·Fan Out Transceiver Module (ST) - 3C12064 
·Fiber Optic Transceiver Module (ST) - 3C12065 
·Coaxial Transceiver Module (BNC) - 3C12066 
·FMS Bridge Management Module - 3C16040 
·Bridge Transceiver Module - 3C16060 
·Switch 1000/3000 100BASE-FX Fiber Downlink Module - 3C16920 
·Switch 1000/3000 100BASE-TX Copper Downlink Module - 3C16922 
·FDDI Fiber MIC Media Module - 3C18320 
·Redundant Power System - 3C565047 
Obsolete Devices 
Enterprise Manager supports the following obsolete devices: 
LinkBuilder FMS Units 
·FMS Coaxial Hub - 3C16250 
·FMS Fiber Optic Hub (SMA Connectors) - 3C16260 
·FMS Fiber Optic Hub (ST Connectors) - 3C16265 
LinkBuilder TP/8i 
·LinkBuilder TP/8i - 3C16181 
LinkBuilder 10BT Units 
The latest version of the LinkBuilder 10BTi agent software is version 1.3. This does not provide all the functionality available to a SuperStack II Hub 10 or FMS using version 2.1x of the agent software. For this reason, some of the dialog boxes are slightly different to those described in this manual. 
·LinkBuilder 10BT Hub - 3C621 
·LinkBuilder 10BTi Hub - 3C622 
·Single Port Media Module (BNC) - 3C623 
·Single Port Fiber Module (ST) - 3C624 
LinkBuilder Focus Chassis 
·LinkBuilder Focus 2-slot chassis - 3C510100 
·LinkBuilder Focus 5-slot chassis (Single Power Supply) - 3C510101 
·LinkBuilder Focus 5-slot chassis (Dual Power Supply) - 3C510102 
LinkBuilder Focus Modules 
·Token Ring Expansion Modules (RI/RO Copper) - 3C510154 
·Token Ring Expansion Modules (RI/RO Copper/Fiber) - 3C510155 
·Passive Token Ring Hub Module - 3C510157 
·Active Token Ring Hub Module - 3C510158 
LinkBuilder TR Stackable Hubs 
·LinkBuilder TRi Model 1 - 3C510182 
828 Series 
·828AT-5 Intelligent Multi-Station Access Unit - 3C510035 
·828AT- 6 Intelligent Multi-Station Access Unit - 3C510036 
·828AT-7 Intelligent Multi-Station Access Unit - 3C510037 
LinkBuilder Focus TR Management Agent Modules 
·RI/RO Copper - 3C510150 
·RI/RO Copper/Fiber - 3C510151 
LinkBuilder ECS 
To manage any ECS or ECS Repeater module you must have a LinkBuilder Management Module (3C1203-1) running agent software version 2.3 or later. 
Intelligent modules have their own IP address. When these modules are discovered by Enterprise Manager they are represented by an ECS module icon. When Autodiscovery searches your network for devices, it treats each device with an IP or IPX address as a separate entity, so even though these modules are housed in an ECS chassis they are shown separately on your network map (this enables you to work with an ECS chassis and intelligent modules that are on different networks). Double-clicking on an ECS module icon has no effect. 
·4 Port Coax (BNC) - 3C1201-0 
·4 Port Fiber Optic (SMA) - 3C1201-1 
·8 Port UTP - 3C1201-2 
·8 Port STP - 3C1201-3 
·Fan Out - 3C1201-4 
·Secure Fan Out - 3C12074 
·4 Port Fiber Optic (SMA) - 3C1201-5 
·12 Port 10BaseT - 3C1201-6 
·Secure 12 Port 10BaseT - 3C12076 
·6 Port Fiber Optic (SMA) - 3C1201-8 
·Secure 6 Port Fiber Optic (SMA) - 3C12078 
·6 Port Fiber Optic (ST) - 3C1201-9 
·Secure 6 Port Fiber Optic (ST) - 3C12079 
·Local Bridge - 3C1205-1 
·Terminal Server - 3C1208-0 
·Remote Bridge - 3C1209-0 
·Remote Control Module - 3C1209-1 
LANplex 2016 
You must be running the LANplex 2016 software Version 4.2.0 or later to access the features described in this manual. 
Enterprise Manager supports the following LANplex 2016 modules: 
·Ethernet module (8 ports, 10BASE-T, RJ-45) - 3C201000 
·Ethernet module (8 ports, 10BASE-T, RJ-21) - 3C201100 
·Ethernet module (8 ports, 10BASE-2, BNC) - 3C201200 
·Ethernet module (4 ports, 10BASE-5, AUI) - 3C201300 
·Ethernet module (8 ports, 10BASE-FL, FOIRL) - 3C201400 
LANplex 6000 
You must be running the LANplex 6000 software Version 4.2.0 or later to access the features described in this manual. 
Enterprise Manager supports the following LANplex 6000 modules: 
·Management module (1 DAS MIC, 1 MAC) - 3C6301-001 
·Management module (1 DAS MIC, 3 MACs) - 3C6301-003 
·Management module, Multimode and Single Mode (Port A: single mode; Port B: multimode, 1 MAC) - 3C6301-101 
·Management module, Multimode and Single Mode (Port A: single mode; Port B: multimode, 3 MACs) - 3C6301-103 
·Management module, Multimode and Single Mode (Port A: multimode; Port B: single mode, 1 MAC) - 3C6301-011 
·Management module, Multimode and Single Mode (Port A: multimode; Port B: single mode, 3 MACs) - 3C6301-013 
·Management module, Single Mode (1 DAS MIC, 1 MAC) - 3C6301-111 
·Management module, Single Mode (1 DAS MIC, 3 MACs) - 3C6301-113 
 B Token Ring Statistics Explanations 
 
Beacon 
A Beacon MAC frame is sent by a station to all stations on its local ring after it has detected a hard error. A hard error is an impairment which breaks the data path, preventing frames from properly circulating around the ring. The beacon frame contains the address of the station and its Nearest Active Upstream Neighbor (NAUN). 
Beaconing normally indicates serious hardware or cabling problems on the ring. The failure which causes the beaconing condition is usually located between the station which is generating the beacon frames and its Nearest Active Upstream Neighbor (NAUN). 
Claim Token 
A Claim Token MAC frame is sent by a station to all other stations on the ring during the token claiming process. Token claiming is the process in which stations elect an Active Monitor (AM). In a ring which is operating normally, the token claiming process should be infrequent. 
Ring Purge 
A Ring Purge MAC frame is sent by the Active Monitor (AM) to all stations on the ring when the token claiming process has completed, or when a token error is detected. 
Continuous purging of the ring, when found together with high rates of lost frame errors and token errors may indicate a problem with frame delimiter integrity. Look first upstream of stations reporting burst errors for the likely source of the problem. 
Isolating Errors: 
Isolating errors are directly associated with a particular fault domain, i.e., the reporting station, its neighbor, or the connection between them. For this reason, isolating errors are particularly useful when you are trying to locate and remove an error source. 
The five isolating errors are: 
·Line Errors Bit errors detected inside a frame or Frame Check Sequence (FCS). These errors are usually due to a marginal Signal-to-Noise Ratio (SNR) on the link upstream of the reporting node. 
·Internal Errors A recoverable error has occurred internal to the reporting station. This type of error is rare and generally not an indication of any serious condition. 
·Burst Errors The reporting station has not detected any transmission for five half-bit times. This type of error can even be detected on networks which have no traffic, since this condition does not have to occur within a frame in order to be detected. Burst errors are sometimes generated when a station enters or leaves the ring, or when a main ring link is reconfigured. Persistent burst errors may indicate faulty physical layer performance in the links or equipment directly upstream of the reporting station. 
·A/C Errors The reporting station has received an AMP or SMP frame with incorrect values for the A and C bits. Persistent A/C errors probably indicate a faulty station upstream from the reporting station. 
·Aborts A station has aborted the transmission of a frame. This is a rare error. 
Non-Isolating Errors: 
Non-isolating errors are harder to locate because the reporting station is not necessarily adjacent to the source of the problem. 
The five Non-isolating errors are: 
·Lost Frames A station transmits a frame but the frame fails to return to the transmitting station as it would if the ring were operating normally. This error is often caused by a faulty link some where in the network. 
·Receive Congestions Occur when a station is receiving or copying a frame and a frame addressed to it comes in but there is no available buffer space in which to store it. In most cases, the sending station retransmits the dropped frame, so this error is not a serious one unless it occurs at a continuous high rate. 
·Frame Copied Errors Occur when a station detects a duplicate frame addressed to itself. 
·Frequency Errors Occur when the elastic storage buffer that the Active Monitor (AM) maintains to accommodate jitter on the ring overflows, indicating an excess jitter condition. The Active Monitor reports this type of error. 
·Token Errors Occur when the Active Monitor (AM) times out while waiting to see the periodic circulation of tokens around the ring. Persistent token errors probably indicate the presence of at least one link in the network which has inadequate Signal to Noise Ratio (SNR). 
 C BOOTPTAB Database File 
This appendix contains the following topics: 
·BOOTPTAB File Entries 
·File Entry Format 
·Global Entries and Variables 
BOOTPTAB File Entries 
The BOOTP server obtains the information used in replies to BOOTP clients from the BOOTPTAB database file. The BOOTPTAB file's location is determined during installation, with the default location being C:\TRANSCEND\COMMON\DATA 
The client information that is specified within the BOOTPTAB file must be entered manually in one of two ways: 
·An unknown client sends a BOOTP request, which opens the BOOTP pop-up dialog box. From within this dialog box, the necessary information (IP address, file server address, etc.) is entered into the provided fields. 
·Client entries are made directly into the BOOTPTAB file using a text editor. 
NOTE: BOOTP does not provide the pop-up dialog box for unknown clients that use NETBuilder BOOTP Helper extensions (see the NETBuilder Reference Guide and NETBuilder Operations Guide). Any BOOTPTAB file entries for clients that use the NETBuilder BOOTP Helper extensions must be entered manually. 
File Entry Format 
The parameters specified in BOOTPTAB file entries vary depending on the client device type. However, all entries have the following general form: 
hostname:parameter1=xxx:parameter2=xxx:...parametern=xxx 
Notice that parameters and their values are delimited by colons. Parameters and values can be placed on different lines by using the back slash (\) as a "next line" indicator. For example: 
hostname:parameter1=xxx:\ 
parameter2=xxx:parameter3=xxx:\ 
parametern=xxx 
CAUTION: Because of the dual use of the back slash (either as "next line" or within directory paths), care should be taken when using this character. 
The following is an example of a possible client entry that might appear in the BOOTPTAB database file: 
nbii4:ht=ethernet:ha=0800203268E:\
ip=192.47.123.17:sm=255.255.255.0:\
gw=192.47.123.109:fs=132.34.213.15:bf=boot.29k 
Where nbii4 is the hostname, ha is the BOOTP client's MAC address, ip is the IP address to be provided to the client, sm is the subnet mask to be supplied to the client, gw is the client's default gateway IP address, fs is the IP address of the file server from which the client should retrieve its files, and bf is the name of the client's boot files. 
Other examples are contained within the default BOOTPTAB file. 
Parameters and Their Values 
The following table lists valid BOOTPTAB file parameters, their values, and their syntax: 
NOTE: Many of these parameters are not used by 3Com devices, and have been included for reasons of compatibility and compliance with the BOOTP standard. 
 
Name	 Parameter	 Value	 Syntax	 
hostname	 The full domain name of the BOOTP client device.	 ASCII string	 Any valid string.	 
hd	 The home directory within which boot files and configuration files for the client are located	 ASCII string	 Specifies a directory path. The leading back slash (\) refers to the directory that was specified during installation as the directory to contain boot and configuration files, and not the root directory of the hard disk. 

The default is C:\TRANSCND\UPGRADE.	 
bf	 Boot file name	 ASCII string	 Any valid file name.	 
cs	 Cookie Server	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
ds	 Domain Name server	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
gw	 Default gateway	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
ha	 Hardware (or MAC) address	 Numeric value	 Hexadecimal value (should not be prefaced by 0x).	 
ht	 Hardware type	 ASCII string	 Can be: "ethernet", "token ring," or "FDDI". Not case sensitive. 	 
im	 Impress network image server	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
ip	 Host IP address. The address to be provided the BOOTP client.	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
lg	 Log server	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
lp	 LPR server	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
ns	 IEN-116 name server	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
rl	 Resource location protocol server	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
sm	 Subnet mask	 Valid IP subnet mask	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
tc	 Template host. Used within the BOOTPTAB file to specify a variable.	 ASCII string	 See following section.	 
to	 Time offset to be used as time out value by the client	 numeric value	 Seconds.	 
ts	 Time server	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
fs	 File server for boot and configuration files*	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
bh	 BOOTP Helper address*	 IP address	 Four octet dotted decimal number, or hexadecimal number if prefaced by 0x.	 
hh	 BOOT Helper interface type*	 ASCII string	 Can be: "ppp" or "frame". Not case sensitive. 	 
ci	 BOOTP Helper Caller ID*	 Numeric value	 The frame relay DLCI of the BOOTP Helper.	 
hp	 BOOTP Helper port number*	 Numeric value	 Any valid NETBuilder router port number.	 

 * 3Com vendor extension for use with BOOTP Helper. See NETBuilder Operations Guide and NETBuilder Reference Guide. 
Global Entries and Variables 
The BOOTPTAB file allows you to group parameters and their values within variables. This allows variable names to be used within device entries. This is useful if, for instance, you need to create a large number of entries for devices that share common parameters and values. 
For example, several devices use the same subnet mask, hardware type, home directory, domain name server, time server, and time offset value. It is possible to define a variable that contains these values. We define this variable (and call it "my-var") as follows: 
my-var:sm=0xffffff00:ht=ethernet:hd=\:ds=129.213.14.73\ 
:ns=129.213.72.60:ts=129.213.45.72:to=18000 
Once the variable is defined, it can be used within client entries. Within the client entry the variable is identified by using the parameter tc (template host) and setting it equal to the name of the variable. The following is an example: 
nb4:tc=my-var:ha=50005A1AA0D2:ip=129.213.32.9 
nb5:tc=my-var:ha=63400772A324:ip=129.213.32.18 
nb6:tc=my-var:ha=660434AD3551:ip=129.213.32.25 
In the example above, the entries for the clients nb4, nb5, and nb6 all use the global variable my-var within their definitions. In each case, the variable is denoted as the value of tc. 
Customizing Variables 
The BOOTPTAB database file allows for additional levels of redirection within variables. This allows you to create more specific variables from a global variable. For example, we can use the variable my-var to create other variables that specify different boot file images for different clients: 
routers129:tc=my-var:bf=router.exe 
hubs129:tc=my-var:bf=hub.exe 
bridge129:tc=my-var:bf=bridge.exe 
In the example above, a new set of variables has been created by specifying a name, using tc to allow the use of my-var, and specifying a unique boot file for each variable. 
Once defined within the BOOTPTAB database file, these variables can be used within client entries. For example: 
Device21:tc=bridge129:ha=880820551A49:ip=129.213.24.71 
Device34:tc=router129:ha=880820434123:ip=129.213.71.15 
Notice that the entries for the clients Device21 and Device34 contain variables (bridge129 and router129) whose contents specify both common and unique parameter values, and whose names specify the client's device type. 
NOTE: For purposes of readability, it is a good idea to limit the number of levels of redirection that you use. 
Further examples of the use of variables are contained within the default BOOTPTAB file. 
 Limited Warranty 
HARDWARE: 3Com warrants its hardware products to be free from defects in workmanship and materials, under normal use and service, for the following lengths of time from the date of purchase from 3Com or its Authorized Reseller: 
 
Internetworking products	 One year	 
Network adapters	 Lifetime	 
Ethernet stackable hubs and Unmanaged Ethernet fixed port repeaters	 Lifetime* (One year if not registered)	 
*Power supply and fans in these stackable hubs and unmanaged repeaters	 One year	 
Other hardware products	 One year	 
Spare parts and spares kits	 90 days	 

  
If a product does not operate as warranted during the applicable warranty period, 3Com shall, at its option and expense, repair the defective product or part, deliver to Customer an equivalent product or part to replace the defective item, or refund to Customer the purchase price paid for the defective product. All products that are replaced will become the property of 3Com. Replacement products may be new or reconditioned. Any replaced or repaired product or part has a ninety (90) day warranty or the remainder of the initial warranty period, whichever is longer. 
3Com shall not be responsible for any software, firmware, information, or memory data of Customer contained in, stored on, or integrated with any products returned to 3Com pursuant to any warranty. 
SOFTWARE: 3Com warrants that the software programs licensed from it will perform in substantial conformance to the program specifications therefor for a period of ninety (90) days from the date of purchase from 3Com or its Authorized Reseller. 3Com warrants the magnetic media containing software against failure during the warranty period. No updates are provided. 3Com's sole obligation hereunder shall be (at 3Com's discretion) to refund the purchase price paid by Customer for any defective software products, or to replace any defective media with software which substantially conforms to 3Com's applicable published specifications. Customer assumes responsibility for the selection of the appropriate applications program and associated reference materials. 3Com makes no warranty that its software products will work in combination with any hardware or applications software products provided by third parties, that the operation of the software products will be uninterrupted or error free, or that all defects in the software products will be corrected. For any third party products listed in the 3Com software product documentation or specifications as being compatible, 3Com will make reasonable efforts to provide compatibility, except where the non-compatibility is caused by a "bug" or defect in the third party's product. 
STANDARD WARRANTY SERVICE: Standard warranty service for hardware products may be obtained by delivering the defective product, accompanied by a copy of the dated proof of purchase, to 3Com's Corporate Service Center or to an Authorized 3Com Service Center during the applicable warranty period. Standard warranty service for software products may be obtained by telephoning 3Com's Corporate Service Center or an Authorized 3Com Service Center, within the warranty period. Products returned to 3Com's Corporate Service Center must be pre-authorized by 3Com with a Return Material Authorization (RMA) number marked on the outside of the package, and sent prepaid, insured, and packaged appropriately for safe shipment. The repaired or replaced item will be shipped to Customer, at 3Com's expense, not later than thirty (30) days after receipt by 3Com. 
WARRANTIES EXCLUSIVE: IF A 3COM PRODUCT DOES NOT OPERATE AS WARRANTED ABOVE, CUSTOMER'S SOLE REMEDY SHALL BE REPAIR, REPLACEMENT, OR REFUND OF THE PURCHASE PRICE PAID, AT 3COM'S OPTION. THE FOREGOING WARRANTIES AND REMEDIES ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER WARRANTIES, EXPRESS OR IMPLIED, EITHER IN FACT OR BY OPERATION OF LAW, STATUTORY OR OTHERWISE, INCLUDING WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. 3COM NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR IT ANY OTHER LIABILITY IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE OR USE OF ITS PRODUCTS. 
3COM SHALL NOT BE LIABLE UNDER THIS WARRANTY IF ITS TESTING AND EXAMINATION DISCLOSE THAT THE ALLEGED DEFECT IN THE PRODUCT DOES NOT EXIST OR WAS CAUSED BY CUSTOMER'S OR ANY THIRD PERSON'S MISUSE, NEGLECT, IMPROPER INSTALLATION OR TESTING, UNAUTHORIZED ATTEMPTS TO REPAIR, OR ANY OTHER CAUSE BEYOND THE RANGE OF THE INTENDED USE, OR BY ACCIDENT, FIRE, LIGHTNING, OR OTHER HAZARD. 
LIMITATION OF LIABILITY: IN NO EVENT, WHETHER BASED IN CONTRACT OR TORT (INCLUDING NEGLIGENCE) SHALL 3COM BE LIABLE FOR INCIDENTAL, CONSEQUENTIAL, INDIRECT, SPECIAL, OR PUNITIVE DAMAGES OF ANY KIND, OR FOR LOSS OF REVENUE, LOSS OF BUSINESS, OR OTHER FINANCIAL LOSS ARISING OUT OF OR IN CONNECTION WITH THE SALE, INSTALLATION, MAINTENANCE, USE, PERFORMANCE, FAILURE, OR INTERRUPTION OF ITS PRODUCTS, EVEN IF 3COM OR ITS AUTHORIZED RESELLER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 
Some states do not allow the exclusion of implied warranties or the limitation of incidental or consequential damages for consumer products, so the above limitations and exclusions may not apply to you. This warranty gives you specific legal rights which may vary from state to state. 
GOVERNING LAW: This Limited Warranty shall be governed by the laws of the state of California. 
3Com Corporation
5400 Bayfront Plaza
Santa Clara, CA 95052-8145
(408) 764-5000
1/1/94