3Com FMS/FMSII/10BTi/MSH Hubs Management Module Guideehealth-spectrum.ca.com/support/secure/products/Spectrum_Doc/pdf... · 3Com FMS/FMSII/10BTi/MSH Hubs ii Management Module Guide

®

3Com FMS/FMSII/10BTi/MSH HubsManagement Module Guide

Notice

Cabletron Systems reserves the right to make changes in specifications and other information contained in this document without prior notice. The reader should in all cases consult Cabletron Systems to determine whether any such changes have been made.

The hardware, firmware, or software described in this manual is subject to change without notice.

IN NO EVENT SHALL CABLETRON SYSTEMS BE LIABLE FOR ANY INCIDENTAL, INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES WHATSOEVER (INCLUDING BUT NOT LIMITED TO LOST PROFITS) ARISING OUT OF OR RELATED TO THIS MANUAL OR THE INFORMATION CONTAINED IN IT, EVEN IF CABLETRON SYSTEMS HAS BEEN ADVISED OF, KNOWN, OR SHOULD HAVE KNOWN, THE POSSIBILITY OF SUCH DAMAGES.

Virus Disclaimer

Cabletron has tested its software with current virus checking technologies. However, because no anti-virus system is 100% reliable, we strongly caution you to write protect and then verify that the Licensed Software, prior to installing it, is virus-free with an anti-virus system in which you have confidence.

Cabletron Systems makes no representations or warranties to the effect that the Licensed Software is virus-free.

Copyright © September, 1997, by Cabletron Systems, Inc. All rights reserved.

Printed in the United States of America.

Order Number: 9031395 E3

Cabletron Systems, Inc.P.O. Box 5005Rochester, NH 03866-5005

SPECTRUM, the SPECTRUM IMT/VNM logo, DCM, IMT, and VNM are registered trademarks, and SpectroGRAPH, SpectroSERVER, Inductive Modeling Technology, Device Communications Manager, and Virtual Network Machine are trademarks of Cabletron Systems, Inc.

Ethernet is a trademark of Xerox Corporation.3Com is a registered trademark of 3Com Corporation.

9031395 E3i

Restricted Rights Notice

(Applicable to licenses to the United States Government only.)

1. Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.

Cabletron Systems, Inc., 35 Industrial Way, Rochester, New Hampshire 03866-5005.

2. (a) This computer software is submitted with restricted rights. It may not be used, reproduced, or disclosed by the Government except as provided in paragraph (b) of this Notice or as otherwise expressly stated in the contract.

(b) This computer software may be:

(1) Used or copied for use in or with the computer or computers for which it was acquired, including use at any Government installation to which such computer or computers may be transferred;

(2) Used or copied for use in a backup computer if any computer for which it was acquired is inoperative;

(3) Reproduced for safekeeping (archives) or backup purposes;

(4) Modified, adapted, or combined with other computer software, provided that the modified, combined, or adapted portions of the derivative software incorporating restricted computer software are made subject to the same restricted rights;

(5) Disclosed to and reproduced for use by support service contractors in accordance with subparagraphs (b) (1) through (4) of this clause, provided the Government makes such disclosure or reproduction subject to these restricted rights; and

(6) Used or copied for use in or transferred to a replacement computer.

(c) Notwithstanding the foregoing, if this computer software is published copyrighted computer software, it is licensed to the Government, without disclosure prohibitions, with the minimum rights set forth in paragraph (b) of this clause.

(d) Any other rights or limitations regarding the use, duplication, or disclosure of this computer software are to be expressly stated in, or incorporated in, the contract.

(e) This Notice shall be marked on any reproduction of this computer software, in whole or in part.

3Com FMS/FMSII/10BTi/MSH Hubsii Management Module Guide

9031395 E3

Contents

Preface

What Is in This Guide .......................................................................................................... xiConventions ......................................................................................................................... xiiRelated SPECTRUM Documentation................................................................................ xiiiOther Related Documentation ........................................................................................... xiii

Chapter 1 Introduction

What Is in This Chapter..................................................................................................... 1-13Com FMS/FMSII/10BTi/MSH Management Module.......................................................................................................... 1-13Com FMS/FMSII/10BTi/MSH Applications .................................................................... 1-2

Accessing SPECTRUM Views from the Device Icon .................................................. 1-2Accessing Device-Specific Subviews............................................................................ 1-4

Chapter 2 Device View

What Is in This Chapter..................................................................................................... 2-13Com FMS/FMSII/10BTi/MSH Device View .................................................................... 2-1Accessing the 3Com Device Views ..................................................................................... 2-1Chassis Device View ........................................................................................................... 2-2

Logical Module Representation................................................................................... 2-4Module Menu Selections ....................................................................................... 2-5Module Configuration View................................................................................... 2-6

Module Management ...................................................................................... 2-6Module Performance View..................................................................................... 2-7

Multi-Attribute Line Graph............................................................................ 2-7Graph Properties............................................................................................. 2-7

Port Menu Selections............................................................................................. 2-8Port Configuration View........................................................................................ 2-8

Port Management............................................................................................ 2-8Address Tracking ............................................................................................ 2-9

Port Detail .............................................................................................................. 2-9Port Performance View........................................................................................ 2-10

Multi-Attribute Line Graph.......................................................................... 2-10Graph Properties........................................................................................... 2-11

Interface Device View....................................................................................................... 2-11Interface Icons............................................................................................................ 2-12

Interface Number Label/Device Topology View ................................................. 2-13IF Status Label/IF Status View .......................................................................... 2-14

iii

Chapter 2 Device View (continued)

Interface Type Labels/IF Configuration View ....................................................2-14Physical Address Label/IF Address Translation Table ......................................2-15Network Information Label/Network Information Panel ..................................2-15Gauge Label/Performance View ..........................................................................2-16Multi-Attribute Line Graph ................................................................................2-16

Graph Properties ...........................................................................................2-16Interface Options Panel..............................................................................................2-19

Find.......................................................................................................................2-19Network Information ...........................................................................................2-19Interface Description ...........................................................................................2-19

Gauge Control Panel ..................................................................................................2-19Selected Attribute ................................................................................................2-20Gauge Mode..........................................................................................................2-20Gauge Type...........................................................................................................2-22Gauge Control Panel Buttons..............................................................................2-22

Chapter 3 Configuration Views

What Is in This Chapter .....................................................................................................3-1Accessing the Device Configuration View..........................................................................3-13Com FMS/FMSII/10BTi/MSH Device Configuration View.............................................3-3

Interface Configuration Table ......................................................................................3-4Chassis Configuration View (MSH only) ...........................................................................3-5

Chassis Configuration Entry .......................................................................................3-7Chassis Services Entry...............................................................................................3-10

Chapter 4 Event and Alarm Messages

What Is in This Chapter .....................................................................................................4-1FMS/FMSII/10BTi/MSH Events and Alarms....................................................................4-1

Chapter 5 Hub Application Views

What Is in This Chapter .....................................................................................................5-1Device Application View .....................................................................................................5-2HubApp Application............................................................................................................5-4

Configuration View.......................................................................................................5-4Interface Setup View..............................................................................................5-5

Interface Setup Table ......................................................................................5-5ASCII Agent Information View .............................................................................5-6End Station View ...................................................................................................5-6EndStation Table View ..........................................................................................5-7End Station Modified Table View ..........................................................................5-8End Station Port Access Table View......................................................................5-8Security View..........................................................................................................5-9

Contents 3Com FMS/FMSII/10BTi/MSH Hubsiv Management Module Guide

Chapter 5 Hub Application Views (continued)

Security Enable Table ..................................................................................... 5-9Security Users Table View .................................................................................. 5-10Security Audit Table View................................................................................... 5-11

Fault Table View......................................................................................................... 5-12Fault Table ........................................................................................................... 5-12

Gauges Group View.................................................................................................... 5-12Gauges Table........................................................................................................ 5-12

Fields.............................................................................................................. 5-15Local SNMP View....................................................................................................... 5-15

SNMP Trap Table ................................................................................................ 5-16Poll Table View ........................................................................................................... 5-17

Poll Table.............................................................................................................. 5-17MSH Mgmt Configuration View (MSH only)............................................................ 5-20

Input Status ......................................................................................................... 5-20Led Table .............................................................................................................. 5-21MSH Mgmt MAC View........................................................................................ 5-21

Power Supply Configuration View (FMS/FMSII only) ............................................. 5-23Power Supply Table ............................................................................................. 5-23

System Loader View................................................................................................... 5-23System Loader Table ........................................................................................... 5-24

Chapter 6 Serial I/F Application Views

What Is in This Chapter..................................................................................................... 6-1Serial I/f Application: V.24 Port Config View .............................................................. 6-2

V.24 Port Configuration Table ............................................................................... 6-3Multi Repeater Application Views ..................................................................................... 6-5

Multi Repeater Configuration View...................................................................... 6-5Card Table ....................................................................................................... 6-5

Multi Repeater Port Configuration View.............................................................. 6-6Port Info Table ................................................................................................. 6-6Port Config Table ............................................................................................. 6-7

Multi Repeater Performance Views ...................................................................... 6-8Repeater Frames and Octets Table ................................................................ 6-9Repeater Error Table .................................................................................... 6-10Repeater Frame Lengths Table .................................................................... 6-12Port Config..................................................................................................... 6-14Port Traffic Levels ......................................................................................... 6-15

Mrm Resilience Application Views .................................................................................. 6-16Mrm Resilience View ................................................................................................. 6-16

Mrm Resilience Table.................................................................................... 6-16Mrm Resilience Standby Table ........................................................................... 6-18

9031395 E3 Contentsv

Chapter 7 Other Application Views

What Is in This Chapter .....................................................................................................7-1SNMP Repeater Application Views....................................................................................7-2

SNMP Repeater Performance View.............................................................................7-2SNMP Repeater Configuration View (FMS/FMSII/10BTi) ........................................7-3

SNMP Repeater Chassis Configuration View (MSH) .........................................................................................................................7-5FMS-MIB Application (FMS/FMSII/10BTi) ......................................................................7-5

Linkbuilder Configuration View ..................................................................................7-5Fields & Buttons for the 3ComFMSmibApp.........................................................7-5Fault Table View.....................................................................................................7-6

Fault Table .......................................................................................................7-6Group Config View .................................................................................................7-7

Group Table......................................................................................................7-7Media Table......................................................................................................7-7

Mau Table View......................................................................................................7-8Mau Table.........................................................................................................7-8

Security Port Application..................................................................................................7-10MSH-MIB Application (MSH only) ..................................................................................7-10

MSH-Mib Configuration View....................................................................................7-10Mau Table.......................................................................................................7-10

Ring Builder Application............................................................................................7-12Ring Builder Configuration View...............................................................................7-12

Ring Builder Table.........................................................................................7-12Ring Builder MAC Address View...............................................................................7-14

MAC Address Table .......................................................................................7-14Token Ring Application Views (MSH only)......................................................................7-15

Token Ring Configuration View.................................................................................7-15Token Ring Performance View...................................................................................7-16

TR Standard Stats Table .....................................................................................7-16Token Ring Topology View .........................................................................................7-17

Token Ring Config Table ......................................................................................7-17Token Ring Config Stats Table ............................................................................7-18

Token Ring Topology Stats View................................................................................7-19Token Ring Config Stats Table ............................................................................7-19

Index

Contents 3Com FMS/FMSII/10BTi/MSH Hubsvi Management Module Guide

9031395 E3

Figures

Chapter 1 Introduction

Figure 1-1. Using Double-Click Zones to Access SPECTRUM Views ................................... 1-3Figure 1-2. Using the Icon Subviews Menu to Access SPECTRUM Views .......................... 1-4


Figure 2-1. Hub3ComFMS/10BTi Chassis Device View ........................................................ 2-3Figure 2-2. Hub3ComMSH Chassis Device View ................................................................... 2-4Figure 2-3. Logical Module Detail ........................................................................................... 2-5Figure 2-4. Hub3ComFMS Interface Device View ............................................................... 2-12Figure 2-5. Logical Interface Icon ......................................................................................... 2-13Figure 2-6. Gauge Control Panel ........................................................................................... 2-20

Chapter 5 Hub Application Views

Figure 5-1. Partial 3Com FMS/FMSII/10BTi/MSH Application View .................................. 5-3

Chapter 6 Serial I/F Application Views


Chapter 7 Other Application Views


vii

Figures 3Com FMS/FMSII/10BTi/MSH Hubsviii Management Module Guide

9031395 E3

Tables


Table 2-1. Module Menu Selections ....................................................................................... 2-6Table 2-2. Port Icon Menu ...................................................................................................... 2-8Table 2-3. Error Breakdown Pie Chart................................................................................ 2-10Table 2-4. Interface Status Label Definitions ..................................................................... 2-14Table 2-5. Multi-Attribute Line Graph Attributes.............................................................. 2-16Table 2-6. Packet Breakdown Pie Chart.............................................................................. 2-17Table 2-7. Error Breakdown Pie Chart................................................................................ 2-17Table 2-8. Discard Breakdown Pie Chart ............................................................................ 2-17Table 2-9. Performance View Gauge Totals and Percentages Mode Attributes and Color Def- initions................................................................................................................. 2-21Table 2-10. Performance View Gauge Rates Mode Attributes and Color Definitions......... 2-21

Chapter 4 Event and Alarm Messages

Table 4-1. FMS/FMSII/10BTi/MSH Events and Alarms ...................................................... 4-1

ix

Tables 3Com FMS/FMSII/10BTi/MSH Hubsx Management Module Guide

9031395 E3

Preface

Use this guide as a reference for the 3Com FMS/FMSII/10BTi/MSH Hub management software. Before using this guide, you should be familiar with SPECTRUM’s functions and navigational techniques as described in the SPECTRUM Administrator’s Reference and the SPECTRUM Operator’s Reference.

For the purposes of this guide, 3Com FMS/FMSII/10BTi/MSH Hubs are referred to as “devices.”

What Is in This GuideThe following outlines the organization of the 3Com FMS/FMSII/10BTi/MSH Management Module Guide:

Chapter Description

Chapter 1Introduction

Introduces the 3Com FMS/FMSII/10BTi/MSH management module, model types and the major and minor applications.

Chapter 2Device View

Describes the Device View’s logical representation of a 3Com FMS/FMSII/10BTi/MSH, as well as the views available from the Device Menu.

Chapter 3Configuration Views

Describes the Device and Chassis Configuration views for the 3Com FMS/FMSII/10BTi/MSH model and the device-specific information provided.

Chapter 4Event and Alarm Messages

Contains a listing and explanation of the alarm/event messages generated in the Event Log or Alarm View for the 3Com FMS/FMSII/10BTi/MSH model type.

Chapter 5Hub Application Views

Describes the Hub Application Views for the 3Com FMS/FMSII/10BTi/MSH model and the major and minor application information provided by the views.

xi

Conventions

ConventionsThis guide uses the following conventions:

• Command names appear in bold; for example, Clear or Save & Close.

• Menu selections and buttons appear in bold; for example, Configuration or Detail.

• Buttons appear as shadowed boxeswhen introducing paragraphs describing their use; for example,

• Referenced chapter titles and section headings appear in italics.

• Referenced documents appear in bold italics.

• Menu navigation appears in order of selection; for example, Icon Subviews -> Utilities -> Application.

Chapter 6Serial/IF Application Views

Describes the Serial/IF Application Views for the 3Com FMS/FMSII/10BTi/MSH model and the minor application information provided by the views.

Chapter 7Other Application Views

Describes the miscellaneous application views for the FMS/FMSII/10BTi/MSH model and the major and minor application information provided by the views.

Chapter Description

Help

Preface 3Com FMS/FMSII/10BTi/MSH Hubsxii Management Module Guide

Related SPECTRUM Documentation

Related SPECTRUM DocumentationRefer to the following documentation for more information on using SPECTRUM:

Operator’s Reference

Administrator’s Reference

Report Generator User’s Guide

Application View Reference

Getting Started with SPECTRUM 4.0 for Operators

Getting Started with SPECTRUM 4.0 for Administrators

How to Manage Your Network with SPECTRUM

Other Related DocumentationRefer to the following documentation for more information on managing TCP/IP-based networks:

Martin, James, Kathleen Kavanagh Chapman, Joe Leben. Local Area Networks: Architectures and Implementations, 2d ed. Englewood Cliffs, NJ: Prentice Hall, 1994.

Michael, Wendy H., William J. Cronin, Jr., Karl F. Piper. FDDI: An Introduction to Fiber Distributed Data Interface. Woburn, MA: Digital Press, 1992.

Rose, Marshall T. The Simple Book: An Introduction to Management of TCP/IP-based Internets. Englewood Cliffs, NJ: Prentice Hall, 1991.

Tanenbaum, Andrew S. Computer Networks, 3d ed. Englewood Cliffs, NJ: Prentice Hall, 1996.

9031395 E3 Prefacexiii

Other Related Documentation

Preface 3Com FMS/FMSII/10BTi/MSH Hubsxiv Management Module Guide

9031395 E3

Chapter 1

Introduction

What Is in This ChapterThis chapter describes the SPECTRUM Management Module for the 3Com FMS/FMSII/10BTi/MSH Hub. It also provides the model type names assigned to the 3Com FMS/FMSII/10BTi/MSH devices in SPECTRUM. The model type names refer to the template used to specify device attributes, actions and associations for device models in SPECTRUM.

3Com FMS/FMSII/10BTi/MSH Management Module

The 3Com FMS/FMSII/10BTi/MSH Management Module supports four types of models to model the physical 3Com FMS/FMSII/10BTi/MSH device, the supported applications, and the 3Com FMS/FMSII/10BTi/MSH device’s interfaces. The models are:

• Hub3ComFMS• Hub3ComFMSII (formerly SuperStack II Hub 10)• Hub3Com10BTi• Hub3ComMSH

1-1

3Com FMS/FMSII/10BTi/MSH Applications

3Com FMS/FMSII/10BTi/MSH ApplicationsThe 3Com FMS/FMSII/10BTi/MSH hub supports both common and device-specific applications described in the SPECTRUM Application View Reference. SPECTRUM management of the ECS is based on the following common applications:

• MIB-II (SNMP2_Agent)- IP (IP2_App)- System (System2_App)- ICMP (ICMP_App)- UDP (UDP2_App)

Device-specific applications and sub-applications covered in this guide are:

• Hub Application View (3ComHubApp)- Fault Table Application- Gauges Application- Local SNMP Application- MSH Mgmt Application (MSH only)- Poll Application (FMS/FMSII only)- Power Supply Application (FMS/FMSII only)- System Loader Application

• Serial I/f Application (3ComserIfApp)- Multi Repeater Application (not for 10BTi)- mrmResilience Application (not for 10BTi)- port security applications

• SNMP Repeater Application (3Com1516App) FMS, (3ComRptrApp) 10BTi, (3ComchassisApp) MSH

• FMS-MIB Application (3ComFMSmib2App) FMS, (3ComFMSmibApp) 10BTi

• MSH-MIB Application (3ComMSHmibApp) • Token Ring Application (MSH only)

Accessing SPECTRUM Views from the Device Icon

The Device icon provides access to SPECTRUM views which display device-specific information. Access SPECTRUM views using double-click zones (Figure 1-1) and Icon Subviews menus (Figure 1-2).

To access the Icon Subviews menu as shown in Figure 1-2, do the following:

1. Highlight the icon.

2. From the View menu, select Icon Subviews or click the applicable mouse button (middle or right). Refer to the SPECTRUM Operator’s Reference for information on configuring your mouse.

Introduction 3Com FMS/FMSII/10BTi/MSH Hubs1-2 Management Module Guide

3Com FMS/FMSII/10BTi/MSH Applications

Accessing SPECTRUM Views from the Device Icon

Figure 1-1. Using Double-Click Zones to Access SPECTRUM Views

Model Name

SwSyn28xxx

Model Name

SwSyn28xxx

Accesses the Device Topology view, refer to Chapter 2, Device View.

Accesses the Device view, refer to Chapter 2, Device View.

Accesses the Device Topology view, refer to Chapter 2, Device View.

Accesses the Configuration view, refer to Chapter 3, Configuration Views.

Accesses the Performance view, refer to the SPECTRUM Operator’s Reference.

Accesses the Application view, refer to Chapters 5 through 7.

Accesses the Configuration view, refer to Chapter 3, Configuration Views.

Accesses the Device view, refer to Chapter 2, Device Views.

Accesses the Application view, refer to Chapters 5 through 7.

Accesses the Performance view, refer to the SPECTRUM Operator’s Reference.

9031395 E3 Introduction1-3

3Com FMS/FMSII/10BTi/MSH ApplicationsAccessing Device-Specific Subviews

Figure 1-2. Using the Icon Subviews Menu to Access SPECTRUM Views

Accessing Device-Specific Subviews

Icon subviews menus provide access to other views which display device-specific information. The icon-specific Icon Subviews menu selections are described under the applicable section within this guide. The menu selections that are common to all devices are described in the SPECTRUM Administrator’s Reference and the SPECTRUM Operator’s Reference.

To access the Icon Subviews menu using the View menu, do the following:

1. Highlight the icon.

2. From the View menu, select Icon Subviews.

To access the Icon Subviews menu using the mouse button, do the following:

1. Position the mouse pointer on the icon.

2. Click the applicable mouse button (middle or right). Refer to the SPECTRUM Operator’s Reference for information on configuring your mouse.

Go BackGo UpIcon SubviewsView PathNew ViewBookmarksView HistoryCurrent View Info...Notes...Jump by name...ZoomMap HierarchyPage

CloseNavigateAlarmsPerformanceNotes...UtilitiesZoomDeviceDevTop

ChassisInterface

View

Ctrl + b

Ctrl + c

Model Name

SwSyn28xxx

Introduction 3Com FMS/FMSII/10BTi/MSH Hubs1-4 Management Module Guide

9031395 E3

Chapter 2

Device View

What Is in This ChapterThis chapter describes the Device View for the 3Com FMS/FMSII/10BTi/MSH Management Module. Included is an explanation of menu bar access to various views used to control and monitor the device. Finally, how to use the Device View to access SPECTRUM generic views and monitor device performance is described.

3Com FMS/FMSII/10BTi/MSH Device ViewThe Device View allows you to view the logical representations of the device’s interfaces. The Device View also provides you with menu bar access to the views that monitor and control the interfaces.

Chassis Device ViewThis view displays a logical representation of the device. Figure 2-1 shows a typical FMS Chassis Device View. Figure 2-2 shows a typical MSH Chassis Device View.

2-1

Chassis Device View

Figure 2-1. Hub3ComFMS/10BTi Chassis Device View

* File View Help?

FMS of type Hub3ComFMS of Landscape VNM Host: Primary

Model Name

Contact

Description

Location

Net Addr

Prime-App

Sys Up Time

Manufacturer

Device Type

Serial Number

Hub3ComFMS

Hubba 134.141.37

3Com LinkBuilder FMS, version:4.01

4+20:08:11

1FMS-6671

0NotAu

Disab

NotOp

1

0NotAu

Enabl

Oper

2

0NotAu

Enabl

Oper

3

0NotAu

Enabl

Oper

4

0NotAu

Enabl

Oper

5

0NotAu

Enabl

Oper

6

0NotAu

Enabl

Oper

7

0NotAu

Enabl

Oper

8

0NotAu

Enabl

Oper

9

0NotAu

Enabl

Oper

10

0NotAu

Enabl

Oper

11

0NotAu

Enabl

Oper

12

0NotAu

Enabl

Oper

13

0NotAu

Enabl

Oper

14

0NotAu

Enabl

Oper

15

0NotAu

Enabl

Oper

16

0NotAu

Enabl

Oper

17

0NotAu

Enabl

Oper

18

0NotAu

Enabl

Oper

19

0NotAu

Enabl

Oper

20

0NotAu

Enabl

Oper

21

0NotAu

Disab

NotPr

22

FMS Module Icon

1BT-621

0NotAuto

Disab

NotOper

1

0NotAuto

Enable

Oper2

0NotAuto

Enable

Oper3

0NotAuto

Enable

Oper4

0NotAuto

Enable

Oper5

0NotAuto

Enable

Oper6

0NotAuto

Enable

Oper7

0NotAuto

Enable

Oper8

0NotAuto

Enable

Oper9

0NotAuto

Enable

Oper10

0NotAuto

Enable

Oper11

0NotAuto

Enable

Oper12

0NotAuto

Enable

Oper13

10BTi Module Icon

Device View 3Com FMS/FMSII/10BTi/MSH Hubs2-2 Management Module Guide

Chassis Device View

Module Icon

Figure 2-2. Hub3ComMSH Chassis Device View

Module Icon

The module icon provides gauges and information about the individual modules. An example is shown in Figure 2-3. A module can be divided into two areas: One area represents information about the module and the other area represents information about each port on the module.

* File View Help?

MSH of type Hub3ComMSH of Landscape VNM Host: Primary

Model Name

Contact

Description

Location

Net Addr

Prime-App

Sys Up Time

Manufacturer

Device Type

Serial Number

Hub3ComMSH

Hubba 134.141.37

3Com LinkBuilder MSH, version:4.01

4+20:08:11

3UTP-RJ45

7

Mau-STP11

Mau-UTP2

Std-Mgmt Oper1 EnabNotA 0

Oper2 EnabNotA 0

Oper3 EnabNotA 0

Oper4 Enab NotA 0

Oper5 Enab NotA 0

Oper7 EnabNotA 0

Oper6 Enab NotA 0

Oper8 Enab NotA 0

Oper9 EnabNotA 0

Oper10 EnabNotA 0

Oper11 EnabNotA 0

Oper12 EnabNotA 0

12

8

34567

9

1110

12

123456789

101112

IP Routing

Module Icons

9031395 E3 Device View2-3

Chassis Device ViewModule Icon

Module Menu Selections

Positioning the cursor on the Module Number or Module Type label and pressing the right mouse button on the icon accesses the Module menu (refer to Table 2-1). Positioning the cursor on any port label and pressing the right mouse button on the icon accesses the Port Icon menu (refer to Table 2-2). Menu selections are made by pressing either the right or left mouse button. The Module menu is also accessed by clicking the module to highlight it and then selecting Icon Subviews from the View menu.

Figure 2-3. Module Detail

Close Ctrl+cNavigateAlarmsPerformanceNotes...UtilitiesModule NotesModule ConfigurationModule Performance

Close Ctrl+cNavigateAlarmsPerformanceNotes...UtilitiesPort NotesPort ConfigurationPort DetailPort Performance

Module Menu SelectionsPort Menu Selections

3UTP-RJ45

Oper1 Enab NotA 0

Oper2 Enab NotA 0

Oper3 Enab NotA 0

Oper4 Enab NotA 0

Oper5 Enab NotA 0

Oper7 EnabNotA 0

Oper6 EnabNotA 0

Oper8 Enab NotA 0

Oper9 Enab NotA 0

Oper10 Enab NotA 0

Oper11 Enab NotA 0

Oper12 Enab NotA 0

1FMS-6671

0NotAu

Disab

NotOp

1

0NotAu

Enabl

Oper

2

0NotAu

Enabl

Oper

3

0NotAu

Enabl

Oper

4

0NotAu

Enabl

Oper

5

0NotAu

Enabl

Oper

6

0NotAu

Enabl

Oper

7

0NotAu

Enabl

Oper

8

0NotAu

Enabl

Oper

9

0NotAu

Enabl

Oper

10

0NotAu

Enabl

Oper

11

0NotAu

Enabl

Oper

12

0NotAu

Enabl

Oper

13

0NotAu

Enabl

Oper

14

0NotAu

Enabl

Oper

15

0NotAu

Enabl

Oper

16

0NotAu

Enabl

Oper

17

0NotAu

Enabl

Oper

18

0NotAu

Enabl

Oper

19

0NotAu

Enabl

Oper

20

0NotAu

Enabl

Oper

21

0NotAu

Disab

NotPr

22Module Number

Module Type

Port Number(double-clickingopens Port NotesView)

Port Status(double-clicking opens Port ConfigurationView)

Port Statistics(double-clickingopens Port Performance View)

Hub3ComMSH

Hub3ComFMS

Port Detail(double-clickingopens Error Breakdown pie chart view)


Chassis Device View

Module Icon

Module NumberDisplays the number of the MMAC-FNB slot to which the module is connected.

Module TypeDisplays the type of module in this MMAC-FNB slot. Table 2-1 describes the Module Icon menu.

Module Configuration View

The Module Configuration View is accessed from the Module menu for the specific module. This view provides the following module-specific information.

Module Management

This section of the Module Configuration View provides the following information.

Operational StatusIndicates the port’s operational state. The notPresent state indicates that the port is physically removed. The operational state indicates that the port is enabled and working.

Last Status ChangeContains the value of sysUpTime at the time that the operational status for this port last changed.

Port CapacityIndicates the maximum number of ports for this module.

Module Type (OID)Indicates the type of module.

Module DescriptionProvides a textual description of the device. This description includes the name and version of the hardware type, the software operating system, and the networking software.

Table 2-1. Module Menu Selections

Menu Selection Description

Module Notes Opens the Module Notes View.

Module Configuration Opens the Module Configuration View.

Module Performance Opens the Module Performance View.


Chassis Device View

Module Performance View

This view summarizes statistics corresponding to the chosen primary application as color-coded entities, and gives a statistical and graphical breakdown for NOW, Average, and Peak Value.

Multi-Attribute Line Graph

This graph appears on the left side of the Module Performance View. The graph provides a general indication of routing activity. The attributes displayed are pre-selected and use colors to represent different statistics. The colors have the following definitions:

Yellow Total Errors(The total number of errors which have occurred on all of the ports.)

Red Total Frames(The total number of frames of valid frame length that have been received on this port.)

Orange Total Octets(The total number of octets contained in the valid frames that have been received on the ports.)

Graph Properties

Provides three options for modifying the statistical presentation of the Multi-Attribute Line Graph.

Allows you to set the viewing area of the graph to begin at a specified date and time.

Allows you to specify the Y axis time scale for the graph.

Allows you to log the polled data in the database.

For more information on the Multi-Attribute Line Graph, refer to the SPECTRUM Operator’s Reference.

Scroll to Date-Time

Change Time Scale

Data Logging


Chassis Device View

Port Menu Selections

Access the Port menu by positioning the cursor anywhere on the port icon and pressing the right mouse button (refer to Table 2-2). Menu selections are made by pressing either the right or left mouse button. The Port menu is also accessed by clicking the port icon to highlight it and then selecting Icon Subviews from the View menu.

Port Configuration View

The Port Configuration View is accessed from the Port menu for the specific port. The Configuration View provides port specific information as follows.

Module/Port NumberDisplays the number representing the Module/Port on the device.

Network AddressDisplays the IP address of the Hub.

Sys UpTimeDisplays the time in seconds which the device has been active without failure.

Serial NumberDisplays the serial number of this device.

ManufacturerIdentifies the manufacturer of the device.

Device TypeProvides a hardware description of the device being modeled.

Port Management

This section of the Port Configuration View contains the following information.

Table 2-2. Port Icon Menu

Menu Selection Description

Port Notes Opens the Port Notes View.

Port Configuration Opens the Port Configuration View.

Port Detail Opens the Error Breakdown pie chart view.

Port Performance Opens the Port Performance View.


Chassis Device View

Administrative StatusThis Enabled/Disabled toggle button determines the Administrative Status.

Operational StatusIndicates the port’s operational state. The notPresent state indicates that the port is physically removed. The operational state indicates that the port is enabled and working.

Auto Partition StateIndicates that the repeater for this port has entered or left the partitioned state.

Address Tracking

This section of the Port Configuration View contains the following information.

Last Source AddressIndicates source address for the last readable frame.

Source Address ChangesIndicates the number of source address changes.

Port Detail

This selection accesses the Error Breakdown View which provides a color-coded pie chart displaying packet breakdown information for the port. Table 2-3 lists the information provided by this pie chart.

NOTE

The order of the Error Breakdown Statistic fields will differ depending on the device.


Chassis Device View

Port Performance View

This view summarizes statistics corresponding to the chosen primary application as color-coded entities, and gives a statistical and graphical breakdown for NOW, Average, and Peak Value.


Provides a general indication of routing activity. The attributes displayed are pre-selected and use colors to represent different statistics. The colors have the following definitions:

Table 2-3. Error Breakdown Pie Chart

Statistic Definition

AutoPartitions This counter is incremented by one each time the repeater has automatically partitioned any port.

DataRateMismatch This counter is incremented by one each time a packet has been received by this repeater with the data rate detectably mismatched from the local.

ShortEvents This counter is incremented by one for each carrier event whose duration is less than short event max time that is detected by the repeater.

LateEvents This counter is incremented by one each time a collision occurs after valid packet min time, a late event is counted as both a collision and as a late event.

VeryLongEvents This counter is incremented by one each time a carrier event occurs whose duration is greater than the MAU Jabber Lockup Protection time.

AlignmentErrors This counter is incremented by one for each frame with an FCS error that does have a framing error and that is of legal frame size received by the repeater.

FCSErrors This counter is incremented by one for each frame with an FCS error that does not have a framing error and which is of legal frame size received by the repeater.

FrameTooLongs This counter is incremented by one for each frame whose octet count is greater than the max frame size that is received by the repeater.

Collisions This counter is incremented by one each time the repeater state machine enters the Collision Count Increment state.

Runts This counter is incremented by one for each carrier event whose duration is greater than short event max time and less than valid packet min time and which does not suffer a collision detected by the repeater.


Interface Device View

Red Readable Frames(This counter is incremented by one for each frame whose octet count is greater than or equal to the minframesize and less than or equal to max frame size and for which FCS error is not asserted that is received by the repeater.)

Orange Readable Octets(This counter is incremented by the octet count for each readable frame received by the repeater.)


Graph Properties

The Port Performance view has the same buttons described in the Module Performance view section of this chapter (see Multi-Attribute Linegraph Buttons), and has an additional button which is described below.

Accesses the Error Breakdown View described above.

Interface Device ViewTo access Interface Device View, highlight the Hub3ComFMS device icon (as detailed in Accessing SPECTRUM Views from the Device Icon) and select Device -> Interface from the Icon Subviews menu. Figure 2-4 shows an example of the 3Com FMS Interface Device View.

Errors



Interface Icons

Figure 2-4. Hub3ComFMS Interface Device View

Interface Icons

This view displays a logical representation of each of the device’s interfaces. An interface icon represents each port on the device. Additional views for the interface can be accessed by clicking the interface icon to highlight it and selecting Icon Subviews from the File menu, or double-clicking the icon’s zones. The Port Notes facility is also accessed from the Icon Subviews menu.

The Interface icon consists of six zones, providing configuration and performance information. Figure 2-5 provides a detailed illustration of the Logical Interface Icon. Descriptions of each icon zone follow.

* File View Help?

Model Name

Contact

Description

Location

Net Addr

Prime-App

Sys Up Time

Manufacturer

Device Type

Serial Number

Find

Interface Description

Network Information AddressPhy Addr

1 ONETHERNET

8:0:4E:6:2E:7

0

2 ONSLIP

Model

Hub3ComFMS

134.177.34

Hubba

3Com LinkBuilder FMS, SW version:2.10

IP Routing

4+20:08:11

Hub3ComFMS

Primary Landscape 0x00400000 - VNM Host - 3Com of type Hub3ComFMS

Interface Icon


Interface Device ViewInterface Icons

Figure 2-5. Logical Interface Icon

a. Interface Number Label/Device Topology View

b. IF Status Label/IF Status View

c. Interface Type Label/IF Configuration View

d. IF Address Translation Table Label/Physical Address Label

e. Network Information Label/Network Information Panel

f. Gauge Label/Performance View

Interface Number Label/Device Topology View

Displays the interface number. Double-clicking this zone of the Logical Interface Icon accesses the device’s Device Topology View.

NOTES

The callouts (a through f) displayed in this illustration below identify the label and the view to which it provides double-click access. Example: Interface Label/Device Topology (DevTop) View displays the interface number and provides double-click access to the DevTop view.

The menu displayed in the illustration is the Icon Subviews menu for that Interface icon.

1 ON

ETHERNET

8:0:4E:6:2E:7

0

134.177.34

(a) (b)

(c)

(d)

(e)

(f)

Close Ctrl+cNavigateAlarmsPerformanceNotes...UtilitiesDevTopDetailIF StatusIF Configuration IF Address Translation TableNetwork Information PanelThresholdsModel Information



Interface Icons

IF Status Label/IF Status View

Displays a text label and an appropriate background color to represent the current status of the interface. Table 2-4 shows the possible interface status and their respective colors.

Double-clicking the IF Status label accesses the Interface Status View which provides the following information on the status of the interface:

Operational StatusFunctions as a read-only indicator button displaying the current operational state of the interface (ON, OFF, or Testing).

Administrative StatusDisplays the desired operational state of the interface (ON, OFF, Testing, or Default).

Interface Type Labels/IF Configuration View

Displays the type of device interface. Double-clicking the label accesses the Interface Configuration View, which provides the following information for the interface:

Operation StatusDisplays the current operational state of the interface (On, Off, or Testing).

Admin. StatusDisplays the desired operational state of the interface (On, Off, or Testing), selectable through the File/Update feature.

Last ChangeIndicates the System UpTime value when the interface entered its current operational state.

Table 2-4. Interface Status Label Definitions

Operational Status

Administrative Status Text Display Color

ON ON ON Green

OFF OFF OFF Blue

OFF ON OFF Yellow

Testing Testing Test Red



Network Name/AddressDisplays the network name and address of the network for which the interface configuration information is displayed.

Physical AddressDisplays the Ethernet (MAC) address of the interface.

BandwidthIndicates the estimated bandwidth of the interface, measured in bits per second. For interfaces that do not vary in bandwidth, or no accurate estimate can be made, a nominal bandwidth is provided.

Packet SizeIndicates the largest packet that can be transmitted or received by the port, measured in octets.

Queue LengthIndicates the length of the outbound packet queue, in packets.

Physical Address Label/IF Address Translation Table

Displays the Interface Index, Physical Address, and Network Address of the device interface. Double-clicking any line accesses the Interface Address Translation Table, which cross-references device IP addresses to device MAC (Ethernet) addresses for selected nodes between networks. Double-clicking any column entry opens an address-specific Address Translation Table Information View.

Sorts the columns in the table incrementally.

Locates a specified statistical entry.

Updates the table.

Network Information Label/Network Information Panel

Double-clicking this zone of the Logical Interface Icon accesses the Network Information Panel. This panel provides Name, Network Address, and subnet mask information for the interface. Any of the network information entries from this panel can be displayed on zone (f) of the Logical Interface Icon. Refer to the Interface Options Panel section of this chapter.

Sort

Find

Update



Gauge Label/Performance View

Summarizes traffic flow, in packets. Double-clicking this zone of the Logical Interface Icon accesses the Performance View for the interface. This area is also a Logical Gauge which is described in the next section. The Performance View provides routing information for this interface.


Provides a general indication of routing activity. The attributes displayed are pre-selected and use colors to represent different statistics. The colors have the following definitions:


Graph Properties

For information on Graph Properties selections, see Multi-Attribute Line Graph Buttons.

Six additional buttons are available from the Interface Performance View, as follows:

Accesses the Interface Detail View which provides three color-coded pie charts displaying packet breakdown information for the interface. This view can also be accessed using the Detail selection on the Icon Subviews menu. Table 2-6 through Table 2-8 list the information provided by these pie charts.

Table 2-5. Multi-Attribute Line Graph Attributes

Color Value

Green Load

Blue Packet Rate

Red Error

Gray Discarded

Detail



Table 2-6. Packet Breakdown Pie Chart


Delivered Packets delivered to a higher level protocol.

Transmitted Packets transmitted through this interface.

Errors Packets containing errors preventing them from being delivered to a higher level protocol.

Discards Packets discarded even though no errors were detected to make them undeliverable - such packets may have been discarded to increase buffer space.

Table 2-7. Error Breakdown Pie Chart


In Errors Packets received containing errors.

Out Errors Packets transmitted containing errors.

Table 2-8. Discard Breakdown Pie Chart


Unknown Locally addressed packets received successfully but discarded because of an unknown or unsupported protocol.

In No Resource Received packets discarded even though no errors were encountered to prevent their continued processing - such packets may have been discarded to increase buffer space.

Out No Resource Transmitted packets discarded even though no errors were encountered to prevent their continued processing. Such packets may have been discarded to increase buffer space.



Each statistic is presented as a total amount since the interface was initialized and as a percentage of overall network traffic. The Interface Performance View provides seven additional buttons as follows:

Accesses the Interface Configuration View described previously.

Accesses the Interface Threshold View. This view can also be accessed using the Thresholds selection on the Icon Subviews menu. The Interface Threshold View allows a user to set statistical thresholds on a per interface basis with the File/Update feature. Thresholds can be set for the following statistics:

• Load• Packet Rate• Error Rate• % Discarded

When a threshold is exceeded, an event is generated and the SNMP device icon turns yellow.

Accesses the Events Log which provides a history of the interface’s status at specific times.

Accesses the Alarms Manager which provides information on current alarm conditions (if any) for the interface. For more detailed information on the Events Log and Alarms View, refer to the SPECTRUM Operator’s Reference.

Accesses an additional Performance View providing information on network traffic transmitted by this interface.

Accesses an additional Performance View providing information on network traffic received by this interface.

Config

Threshold

Events

Alarms

Transmit

Receive


Interface Device ViewInterface Options Panel

Interface Options Panel

The Interface Option Panel area of the Device View (located just below the banner and just above the icons; see Figure 2-4) allows a user to modify the presentation of the Logical Interface Icon.

This panel contains the following fields:

Find

Allows a user to find a specific interface by selecting either the interface’s Physical Address, IP Address, Type, or Network Name and entering the appropriate information in the Pop-up dialog box. Once the information is entered, the corresponding area of the specific Logical Interface Icon will appear highlighted. The Find option will also look for and display other addresses in the Network Information Panel.

Network Information

Allows a user to select what interface information is displayed in the Network Information Label zone of that interface’s Logical Interface Icon. Possible selections are ADDRESS, NAME, or MASK.

Interface Description

Selecting a Logical Interface Icon displays the type of interface in the Interface Description area of the Interface Options Panel. Double-clicking the Interface Description field accesses the Interface Description Map which provides a table’s mapping interface numbers to their descriptions. This view can also be accessed by clicking the Interface Options Panel to highlight it and then selecting Inf Description Map from the Icon Subviews menu. Double-clicking a column entry in the Interface Description Map accesses the Interface Configuration View described previously.

Gauge Control Panel

The Gauge Control Panel (Figure 2-6) allows a user to change the type of statistical information presented in the Logical Gauge area of the Logical Interface Icon. To access the Gauge Control Panel, either double-click the Interface Options Panel or click the panel to highlight it and then select Gauge Control Panel from the Icon Subviews menu.



Gauge Control Panel

Figure 2-6. Gauge Control Panel

Selected Attribute

This area of the Gauge Control Panel allows a user to select the statistical attribute displayed on the Logical Interface Icon’s Gauge. The label changes color to reflect the attribute selected. Table 2-9 and Table 2-10 provide a list of the attributes and their corresponding colors.

Gauge Mode

This area of the Gauge Control Panel allows a user to select the mode presented by the Logical Gauge. Possible selections are Totals, Rates, or Percentages. The Percentages selection represents the percentage of the interface compared to the rest of the interfaces. Table 2-9 shows the displayed attributes and their color definitions if the Totals or Percentages modes are selected. Table 2-10 shows the displayed attributes and their color definitions if the Rates model is selected.

Gauge Control Panel

Gauge Mode Selected Attribute

Rate Load

Totals Load In

Percentages Load Out

Packet Rate

Gauge Type Packet In Rate

Packet Out Rate

Numeric Error Rate

Linear Error In Rate

Apply Keep Settings

Reset Close

Default


Interface Device ViewGauge Control Panel

Table 2-9. Performance View Gauge Totals and Percentages Mode Attributes and Color Definitions

Selected Attribute Color

In Errors Orange

Out Errors Orange

In Packets Blue

Out Packets Blue

Unknown Protocols Yellow

In Discards Beige

Out Discards Beige

In Octets Green

Out Octets Green

Table 2-10. Performance View Gauge Rates Mode Attributes and Color Definitions

Selected Attribute Color

Load Green

Load In Green

Load Out Green

Packet Rate Blue

Packet In Rate Blue

Packet Out Rate Blue

Error Rate Orange

Error In Rate Orange

Error Out Rate Orange

Discard Rate Beige

Discard In Rate Beige



Gauge Type

Allows you to select either a numeric or linear presentation of the Logical Gauge.

Gauge Control Panel Buttons

The following buttons are available in the Gauge Control Panel:

Applies the current selections to the Logical Gauge. The settings will not be saved.

Saves the current gauge settings while running SpectroGRAPH.

Resets back to the last Keep Settings selections.

Closes the Gauge Control Panel.

Resets back to the default attribute of In Errors.

Apply

Keep Settings

Reset

Close

Default




9031395 E3

Chapter 3

Configuration Views

What Is in This ChapterThis chapter provides descriptions of the configuration views available for the 3Com FMS/FMSII/10BTi/MSH. These views allow you to access device-specific configuration information. The following configuration views are detailed in this chapter:

• Device • Chassis

The Chassis Configuration View is available for the 3Com MSH Hub only. Other configuration views available from the Icon Subviews menu, for example, the Hub Config, Endstation Config and Poll Config, are described in Chapter 5, Hub Application Views.

3Com FMS/FMSII/10BTi/MSH Device Configuration View

The Device Configuration View provides information on the configuration and operating status of the 3Com FMS/FMSII/10BTi/MSH and allows you to modify the values of some fields.

This view provides the following information:

Device NameDisplays the unique name given to the device.

Contact StatusDisplays the contact status for the device.

3-1

3Com FMS/FMSII/10BTi/MSH Device Configuration View

Number of InterfacesDisplays the number of interfaces for the device.

Router RedundancyToggles so that Router Redundancy can be set at True or False.

Accesses the Interface Address Translation Table, which includes the fields, Interface Index, Physical Address, and Network Address. This table cross-references device IP addresses to device MAC (Ethernet) addresses for selected nodes between networks. You can sort, update, and search the table. To activate the Sort button, click a column heading. Clicking the Sort button will sort the table based on the selected column. The Find button is activated when an appropriate column is selected. A prompt for the search string will appear after clicking the Find button. The Update button will update the screen. Double-clicking any column entry opens an address-specific Address Translation Table Information View.

Reconfigures the application. A message window appears telling you the action was successful.

This view also contains the Interface Configuration Table which contains the following information.

Interface Configuration Table

The Interface Configuration Table provides port configuration information for each of the hub’s ports. You can sort, update, and search the table using the Sort, Find and Update buttons.

IndexDisplays the port number on the device.

DescriptionProvides a textual description of the interface.

TypeProvides a read-only indicator button displaying the type of hardware interface for the port.

BandwidthIndicates the bandwidth of the interface on that port.

Physical AddressDisplays the (MAC) address of the port.

Operation Status

IF Address Translation

Reconfigure

Configuration Views 3Com FMS/FMSII/10BTi/MSH Hubs3-2 Management Module Guide

Chassis Configuration View (MSH only)

Provides a read-only indicator button displaying the current operational state of the port (UP, DOWN, or TESTING). The TESTING state indicates that no operational packets can be passed.

Admin StatusProvides a read-only indicator button displaying the desired state of the interface (UP, DOWN or TESTING). The TESTING state indicates that no operational packets can be passed.

Last Change Displays the System UpTime value when the port entered its current operational state.

Queue LengthIndicates the length of the outbound packet queue, in packets.

Packet SizeIndicates the size of the packet transmitted or received on a highlighted port.

Chassis Configuration View (MSH only)The Chassis Configuration View is available for the Hub3ComMSH device only. This view provides information on the configuration of the Hub3ComMSH and allows you to modify the values of some fields.

Access the Chassis Configuration View by selecting Chassis Config from the Icon Subviews menu (see Accessing Device-Specific Subviews). This view provides the following fields and five buttons that access table views:

NameDisplays the unique name given to the device.

Hardware VersionDisplays the revision number of the hardware running on the device.

Object IdDisplays the system object ID.

Opens the Chassis Configuration Table. Double-clicking any of the column entries opens the Chassis Configuration Entry view. Table entries can be changed using the Sort, Find and Update buttons.The Configuration Table has the following fields:

TypeDisplays the type of location. Currently, there are four types of location defined:

• Module - A location of this type can take a number of different entities. They are general purpose and are often the purpose of the device.

Config Table

9031395 E3 Configuration Views3-3


• Power-Supply - Locations of this type can only contain an instance of a power supply.

• Fan - This location can only hold a fan.• Backplane - A position of this type can only contain a backplane.

LocDisplays the location type which defines a “kind” of location. Each physical entity resides at some location. Some locations are known to have special purposes, others are general and can contain one of a number of different physical entities.

System Object IdDisplays an object which is the Object ID of the entity at this location.

Service TypeIdentifies what kind of entity is present at this location. The value represents a category of entity, for example, ‘power supply’. It does not identify the specific kind of entity within that category, for this refer to the entity type.

EntityThis object is read in conjunction with service type to uniquely identify the specific physical entity. For example, the service type may indicate ‘802.3 Repeater’ while the entity type then says within this category this card is a 12 port UTP card.

HwVersionIdentifies the major and minor revision level of the entity at this location.

SwVersionDisplays a parameter which specifies the version number of program code. If the entity at this location contains a processor, there will be some program code present. The version number is a string. If an entity has no software, the value will be “None.”

ServiceIdentifies the type of entity present at this location. The value represents a category of entity; for example, 802.3 Repeater (a value of 2) or power supply (a value of 18). Service does not identify the specific kind of entity within that category.

Entity NameDisplays a text string describing the entity at this location.

PowerTakes the +5V and +12V current requirements of the entity and uses the values to obtain a power consumption requirement for the entity. A power supply will specify a negative value indicating a source of power. The value is in Watts.

PortsDisplays an object which contains the number of physical, external ports possessed by this entity. This value only applies to entities that communicate



Chassis Configuration Entry

with the management card. For other cards, a value of -1 indicates “unknown.” A value of zero indicates that this entity has no external ports.

StateEach entity in the chassis has a basic state independent of the function that entity performs within the chassis. If the agent cannot determine the state of a particular entity, then the value of this object is “unknown.”

Chassis Configuration Entry

This view contains the following fields and information:

Location TypeCurrently, there are four types of location defined:

• Module - A location of this type can take a number of different entities. They are general purpose and are often the purpose of the device.

• Power-Supply - Locations of this type can only contain an instance of a power supply.

• Fan - This location can only hold a fan.

• Backplane - A position of this type can only contain a backplane.

LocationEach physical entity resides at some location. Some locations are known to have special purposes, others are general and can contain one of a number of different physical entities. The location type defines a “kind” of location.

Sys Object IdThis object is the Object ID of the entity at this location.

Service TypeIdentifies what kind of entity is present at this location. The value represents a category of entity, for example ‘802.3 Repeater’ or ‘power supply’. It does not identify the specific kind of entity within that category, for this refer to the entity type.

Entity TypeThis object is read in conjunction with service type to uniquely identify the specific physical entity. For example the service type may indicate ‘802.3 Repeater’ while the entity type then says within this category this card is a 12 port UTP card.

Hw VersionThis string identifies the major and minor revision level of the entity at this location.

Sw VersionIf the entity at this location contains a processor, there will be some program code present. This parameter specifies the version number of that code. The



version number is a string. If an entity has no software, the value will be “None.”

Service IdEvery chassis is considered as a collection of services. Each service is implemented using the resources of one or more physical entities within the rack. For example a repeater may be implemented using 2x12 port UTP cards. A power supply by 3 modular power supply entities. The service table contains an entry for each service present in the MSH at any point in time. This object provides a valid index into the service table. By reading the service table and specifying the value of this object one can determine to which service this card belongs.

Entity NameThis object is a text string describing the entity at this location.

Power ReqThis object takes the +5V and +12V current requirements of the entity and uses the values to obtain a power consumption requirement for the entity. A power supply will specify a negative value indicating a source of power. The value is in Watts.

Number of PortsThis object contains the number of physical, external ports this entity is known to have. Note this value only applies to entities that communicate with the management card. For other cards, a value of -1 indicates “unknown.” A value of zero indicates that this entity has no external ports.

Entity StateEach entity in the chassis has a basic state independent of what function that entity performs within the chassis. If the agent cannot determine the state of a particular entity, then the value of this object is “unknown.”

Lamp TestAllows a visual test to be performed on entities contained in the rack. The state will be recorded against the card even if that entity does not actually do anything different in this state. Selections are Test-Off and Test-On.

ActionAllows a number of actions to be defined for cards in a chassis. Currently only one action is defined: reset. Invoking this operation will reset the specified card. Selection is Reset.

Opens Physical Limits View which contains the Physical Limits Table. This table contains the following:

TypeIdentifies the particular type of the facility represented by this table entry. A chassis contains a number of physical entities such as Module, Power-Supply,

Limits Table



Fan, and Backplane. Each physical entity resides in some location. A chassis can contain a number of types of locations.

LimitA chassis contains a number of physical entities such as power supplies and cards. Each physical entity resides at some location. A chassis can contain a number of types of location.For each particular type of location there is a limit to the number that may be present in the chassis.

This object identifies the actual number of locations in this chassis that exist for the specified type. Practically this is interpreted as the ‘number of power supplies’ or ‘number of slots’, etc.

Opens the Chassis Service View which contains the Chassis Service Table. Double-clicking a column entry opens the Chassis Services Entry view. The Chassis Service Table contains the following information.

IdDisplays a number representing the service in the rack.

Name Displays a test string describing the service at a particular Service Index.

The Chassis Services Entry allows you to enter an Id or Name for a specified service. The view also contains a Reset button.

Opens the Service Address View which contains the Service Address Table. This table contains the following information.

IdIdentifies the service for which this row provides address information.

IndexUsed to distinguish between multiple address for a service in the chassis.

Addr TypeA card in the chassis can have several addresses, either because of multiple stacks and/or for each relevant level in the stack(s). Each relevant address is represented in this table as a display string and a type.

MAC AddressDisplays the address as block of bytes. A MAC address occupies 6 bytes.

Service Table

Address Table



IP AddressDisplays the address as block of bytes. An IP address occupies 4 bytes.

Opens the Facility Table View. The Facility Table contains the fields Slot, Index, Type, and Connection. Double-clicking a column entry opens a different Chassis Services Entry view than the one described above.

SlotAllows access to the table for a particular card.

IndexIdentifies each entry on each card in the Facility Table.

TypeEach entry in the facility table represents an association between a physical module and one of the facilities provided by the particular configuration of this chassis. This object identifies the particular type of the facility represented by this table entry.

ConnectionDisplays an object which identifies the current assignment of this attachment point in this card.

Chassis Services Entry

This view contains the following information.

SlotAllows access to the table for a particular card.

IndexEach card may have multiple entries in the Facility Table. This object provides the means of uniquely identifying each of these entries.

TypeEach entry in the facility table represents an association between a physical module and one of the facilities provided by the particular configuration of this chassis. This object identifies the particular type of the facility represented by this table entry.

The view also contains fields for updating cards:

802.3 CardThis field has a toggle button from which Isolated, Backplane1, Backplane2, or Backplane3 may be selected.

The view also has fields for 802.5 and FDDI:

• 0 = Isolated 1..0x7f A ring number

Facility Table



Chassis Services Entry

802.5 CardContains information based on the formula above.

FDDI CardContains information based on the formula above.


Chassis Configuration View (MSH only)Chassis Services Entry


9031395 E3

Chapter 4

Event and Alarm Messages

What Is in This ChapterThis chapter describes the types of events and alarms generated by the 3Com FMS/FMSII/10BTi/MSH Device.

FMS/FMSII/10BTi/MSH Events and AlarmsThis table describes the event messages appearing in the Event Log, and any corresponding probable cause messages that may be displayed in the Enterprise Alarm Manager View for the FMS/FMSII/10BTi/MSH.

Table 4-1. FMS/FMSII/10BTi/MSH Events and Alarms

Message in the Event Log Alarm View Probable Cause Message

CsEvFormat/Event00010306

{d "%w- %d %m-, %Y - %T"} - A(n) {t} device, named {m}, has been cold started. (event [{e}])

No Probable Cause Message


{d "%w- %d %m-, %Y - %T"} - A(n) {t} device, named {m}, has been warm started. (event [{e}])


4-1

FMS/FMSII/10BTi/MSH Events and Alarms


{d "%w- %d %m-, %Y - %T"} - A(n) {t} device, named {m}, has detected a communication Link Down. (event [{e}])

CsPCause/Prob00010308

Communication link is down.


{d "%w- %d %m-, %Y - %T"} - A(n) {t} device, named {m}, has detected a communication Link Up. (event [{e}])


CsEvFormat/Event0001030a

{d "%w- %d %m-, %Y - %T"} - A(n) {t} device, named {m}, has detected an Authentication Failure. (event [{e}])

CsPCause/Prob0001030a

Authorization failure. Other user is trying to connect to device with an invalid community string.

CsEvFormat/Event0001030b

{d "%w- %d %m-, %Y - %T"} - A(n) {t} device, named {m}, has detected an EGP Neighbor Loss. EGP Neighbor IP address is {0 1}.(event [{e}])

CsPCause/Prob0001030b

Lost contact with EGP neighbor.


{d "%w- %d %m-, %Y - %T"} - Device {m} of type {t} is created with an IP address already used by another model. (event [{e}])

CsPCause/Prob00010401

DUPLICATE IP ADDRESS

The model has the same IP address as that of some other model.


{d “%w- %d %m-, %Y - %T”} - Device {m} of type {t} is created with a physical/Mac address ({X 1}) already used by another model. (event [{e}])

Table 4-1. FMS/FMSII/10BTi/MSH Events and Alarms (Continued)


Event and Alarm Messages 3Com FMS/FMSII/10BTi/MSH Hubs4-2 Management Module Guide


CsEvFormat/Event00ea0013

{d “%w- %d %m-, %Y - %T”} - A(n) {t} (named {m}) Is informing the manager that the device is still operating. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} (named {m}) has had its configuration modified via the ascii agent. This may be through Telnet or the V24 port. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) device {t} (named {m}) An user “{S 1}” has attempted a login and failed three times. The cause was {T comstat 2}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) a gauge {O 1} has gone over its threshold {I 3}. The sample period was {I 5} and the number of samples used is {I 7}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) a gauge {O 1} has gone below its recovery level {I 3}. The sample period was {I 5} and the number of samples used is {I 7}. (event [{e}])




9031395 E3 Event and Alarm Messages4-3



{d “%w- %d %m-, %Y - %T”} - An {t} device (named {m}) has reported that a system load request has failed. The reason was {T slstat 1}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - An {t} device (named {m}) reports the endstation table has moved to the modified state. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - An {t} device (named {m}) reports the endstation table is full. (event [{e}])

CsPCause/Prob00ea0020

When the end-station table becomes full this trap is generated.


{d “%w- %d %m-, %Y - %T”} - An {t} device (named {m}) reports that the slot.port.index {I 2} MAU has entered or left the available state. Current state is {T maustate 1}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a new entity of service type {T service 1} has been installed at location {I 2}. The service ID is {I 5} and the entity has name {S 9} and {I 7} ports. (event [{e}])







{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that an entity of service ID {I 1} at the slot.index is {I 4} has changed its facilities for its type {T etype 3} to {I 5}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a card is added to the service {I 1}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (name {m}) reports that a card has been removed from the service {I 1}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a physical entity of service ID {I 1} has changed state to {T estate 3}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the power requirements of the entities in the chassis exceed the power capacity of the power supplies. (event [{e}])


The combination of the power requirements of all the entities in the chassis has been calculated to exceed the power capacity of the power supplies present.






{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the management card temperature sensing device is reporting DANGER. (event [{e}])


Mounted on the Management Card is a temperature sensing device. This device provides three output levels. This alarm is generated when the output level is DANGER

Check the Hub for overheating, fans not working etc.


{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the status input {I 2} of name {S 3} has changed state to {I 1} (1=Open, 2=Closed). (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that port {I 2} has learned a station address {H 3}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a port {I 2} has detected a security violation. (event [{e}])


A port has detected a security violation. Check event 0x00ea0037 to find the port.


{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a port {I 2} has had its partition state changed to {I1}(1=Partitioned,2=UnPartitioned). (event [{e}])







{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a port {I 2} has had its link state changed to {I 1} (1=Present,2=Absent). (event [{e}])



d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a port {I 2} has had its Admin state changed to {I 1} (1=Enabled,2=Disabled) by a gauge. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a port {I 2} has had its Bandwidth Used threshold {I 3} exceeded. The Bandwidth used is {I 1} (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a port {I 2} has had its Errors/10000 packets threshold {I 3} exceeded. The Errors/10000 packets is {I 1} (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a port {I 2} in a resilience pair has had a change in state and the active port has been switched. The state of the main port is {I 1} the state of the backup port is {I 3} (1=Failed,2=OK,3=OK-And-Active) (event [{e}])







{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a port {I 2} in a resilience pair has had a change in state and the active port has not been switched. The state of the main port is {I 1} the state of the backup port is {I 3} (1=Failed,2=OK,3=OK-And-Active) (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a topology change has occurred in the ring at time {I 1}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the main rings state has changed to {T rstate 1}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the backup rings state has changed to {T rstate 1}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that either the main and backup rings have wrapped or that the wrap condition has been removed. The new wrap state is {I 1} (1=NotWrapped,2=Wrapped). (event [{e}])







{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a MAU port {I 2} has had a change in attach state and the admin state of the port is disabled. The new attach state is {I 1} (1=Absent,2=Present). (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the Ring In port has changed state while the mode is fail-safe. The new Ring In state is {I 1} (1=Open,2=Wrap). (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the Ring Out port has changed state while the mode is fail-safe. The new Ring Out state is {I 1} (1=Open,2=Wrap). (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a MAU port {I 2} has changed state due to operation of ZDL or DRI. The new MAU port state is {I 1} (1=Enabled,2=Disabled). If disabled the reason is {I 3} (1=None,2=Mgmt,3=ZDL,4=DRI). (event [{e}])







{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the managed agent has received a reply to a poll after a sequence of four or more unsuccessful poll. The address is {S 1} with protocol {T pprot 3}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the managed agent has not received a reply to a poll after a sequence of four un-successful polls. The address is {S 1} with protocol {T pprot 3}. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the Resilient Backup Power Supply connected to this repeater has developed a fault. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that the Resilient Backup Power Supply connected to this repeater has recovered from a fault. (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a port {I 2} has seen an unrecognized MAC address and is doing the following action {I 1} (2=Notify,3=Disconnect). (event [{e}])







{d “%w- %d %m-, %Y - %T”} - A (n) {t} device (named {m}) reports that a repeater {I 2} has had its Bandwidth Used threshold {I 3} exceeded. The Bandwidth used is {I 1} (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a repeater {I 2} has had its Errors/10000 packets threshold {I 3} exceeded. The Errors/10000 packets is {I 1} (event [{e}])



{d “%w- %d %m-, %Y - %T”} - A(n) {t} device (named {m}) reports that a card {I 2} has had its Bandwidth Used threshold {I 3} exceeded. The Bandwidth used is {I 1} (event [{e}])







9031395 E3

Chapter 5

Hub Application Views

What Is in This ChapterThis chapter describes the Hub Application (3ComHubApp) for the 3Com FMS/FMSII/10BTi/MSH devices.

This application supports the following sub-applications:

• Fault Table Application• Gauges Application• Local SNMP Application• MSH Mgmt Application (MSH only)• Poll Application (FMS/FMSII only)• Power Supply Application (FMS/FMSII only)• System Loader Application

5-1

Device Application View

Device Application ViewThis view shows the common and device-specific applications supported by this device and provides access to application-specific information.

Refer to Chapter 1, Introduction, for information on Accessing SPECTRUM Views from the Device Icon and Accessing Device-Specific Subviews.

Figure 5-1 provides an example of an Application view in the icon mode. Figure 5-2 provides an example of an Application view in the list mode.

To change the display mode, select View -> Mode -> List or Icon.

Figure 5-1 shows the part of the Application View containing the FMS Hub application icon and its sub-application icons.

Hub Application Views 3Com FMS/FMSII/10BTi/MSH Hubs5-2 Management Module Guide

Device Application View

Figure 5-1. Partial 3Com FMS/FMSII/10BTi/MSH Application View

Hub3ComFMS

Model Name

Hub

3ComHubApp

3ComHubApp

Serial If

3ComserIfApp

3ComserIfApp

Multi Repeater

3CommultiApp2

3CommultiApp2

mrm Resilience

3CommrmResA

3CommrmResAp

Fault Table

3ComfaultApp

3ComfaultApp

Gauges

3ComgaugesAp

3ComgaugesApp

Local SNMP

3ComSnmpApp

3ComSnmpApp2

SNMP-Repeater

3Com1516App

3Com1516App

Poll

3CompollApp

3CompollApp

Power Supply

3CompowerApp

3CompowerApp

System Loader

3ComsysLdApp

3ComsysLdApp2

9031395 E3 Hub Application Views5-3

HubApp Application

HubApp ApplicationThe HubApp supports the following views:

• Configuration View, which includes the following views:

- Interface Setup- ASCII Agent Information Views

• End Station View leading, which includes the following views:

- End Station Table View- Modified Table View- Port Access Table View

• Security View, which includes the following views:

- Security Users - Security Audit Log Views

Configuration View

The Configuration View is accessed by highlighting the icon and then selecting the Hub Config option from the Icon Subviews menu. It displays the following information below the header:

Last Restart TypeDisplays the reason for the last system restart. Possible reasons:

OtherCommand Management commandWatchdog Watchdog timeout expiryPower-reset Power interruptionSystem-error Reset switch was pressed or there was a system error. It is

not possible to distinguish between these two reasons.

Restart CountDisplays the number of restarts the system has undergone (power ons, reset switches or watchdog expirations).

Restart ActionDisplays a button with the restart action. Possibilities are Nochange or Restart (restart the device with its current configuration). You can update this field.

Reset ActionDisplays a button with the reset action. Possibilities are Nochange or ManDefaultReset (reset the device with the manufacturers default configuration). You can update this field.


HubApp Application

PROM SW Ver NoDisplays the PROM software version number.

Last System ErrorDisplays the last system error experienced by the system. On startup, this field is set to the last NVRAM system error code. When the system issues a trap indicating the last system error number, the NVRAM version is set to zero. Therefore, after the next restart, the field will also have a value of zero.

Heartbeat IntervalDisplays the time between successive heartbeat events sent to the management station, in seconds. An interval of 0 indicates that no heartbeat events are to be sent. You can update this field. Values between 0 and 65535 are allowed.

Displays the Interface Setup View, described below.

Displays the ASCII Agent Information View, described below.

Interface Setup View

The Interface Setup View is accessed by clicking the Interface Setup button in the Hub application Configuration View. It displays the following information below the header:

Default Router IPDisplays the IP address of the default router to be used for sending IP datagrams to remote destinations which have no entry in the IP Routing Table. This corresponds to an entry in the MIB-II IP Routing Table with a Destination field of “0.0.0.0” (the default router) which is set up from this field after a system restart.

You can update this field. Changes do not affect the IP Routing Table until after the next system reset; to change the IP Routing Table without resetting, change it directly. Update this field only if you want to make the change permanent.

Interface Setup Table

This table shows the IP address and network mask to be used in initializing the IP Address Table on each network interface after the next system restart. There is one entry per network interface and the index is equivalent to the index in the Interface Configuration Table in the Device Configuration View.

Interface Setup

ASCII Agent Info


HubApp Application

Double-clicking an entry in this table displays Interface Setup in which you can update the IP Address and Network Mask for the selected entry.

Interface Displays the index for the table entry. It is equivalent to the index in the Interface Configuration Table.

IP AddressDisplays the IP address to be used for this interface. You can update this field.

NetmaskDisplays the IP network mask to be used for this interface. You can update this field.

ASCII Agent Information View

The ASCII Agent Information View is accessed by clicking the ASCII Agent Info button in the Hub application Configuration View. It displays the following information below the header:

User Name Last Attempted LoginDisplays the ASCII string used when last attempting to login.

Login StatusDisplays the status of the last attempted login.

Time Attempted LoginDisplays the time when the last login was attempted, in hundredths of a second since system was last restarted.

End Station View

The End Station View is accessed by highlighting the icon and then selecting the Endstation Config option from the Icon Subviews menu. The End Station database maintains information concerning end station address information against device port for 802.3 repeater-type devices.

NOTES

These fields are updated by an ASCII agent such as a local terminal or a remote login.


HubApp Application

The End Station View displays the following information below the header:

Flush DatabaseDisplays a button for setting this field to Flush which clears the End Station database. Possible selections are Flush and Leave (which simply means do not flush the database).

Database StateDisplays a button set to NoChange until a change is made to the End Station database. It then displays Modified until reset to NoChange.

Displays the End Station Table View, described below.

Displays the End Station Modified Table View, described later in this section.

Displays the End Station Port Access Table View, described later in this section.

EndStation Table View

The EndStation Table View is accessed by clicking the End Station Table button in the End Station View. This table reads the entire contents of the database in end station address order. You cannot update any entries in this table.

The EndStation Table displays the following information:

Address TypeThe end station database is capable of storing information for a number of protocols, each with its own addressing format. This parameter allows access to the database indexed on address type.

IP AddressDisplays the IP address if relevant.

NOTE

The End Station database is global and applies across all repeaters in the chassis. There is no distinction between units on one repeater and those on another. Given a unit number, the manager can read the configuration values to determine the actual repeater association.

End Station Table

Modified Table

Port Access Table


HubApp Application

MAC AddressDisplays the MAC address if relevant.

SlotDisplays the number of the unit on which this address was learned.

PortDisplays the port number in the unit on which this address was learned.

End Station Modified Table View

The End Station Modified Table View is accessed by clicking the Modified Table button in the End Station View. This table is a filtered view of the end station database, showing only those entries with the Modified Flag set; that is, entries that have changed since the database was last viewed by the manager. For information about individual fields, see the descriptions for the End Station Table View. Double-click on any field in the table to access the Endstation Table Entry which provides information on the specified entry.

End Station Port Access Table View

The End Station Port Access Table View is accessed by clicking the Port Access Table button in the End Station View. This table is a filtered view of the end station database, showing only those entries that have changed since the database was last viewed. The information is indexed by Slot and Port rather than Address Type.

SlotDisplays the number of the unit on which this address was learned.

PortDisplays the port number in the unit on which this address was learned.

IndexEach port may have a number of addresses against it. This index distinguishes between these addresses and therefore is unique within each Slot/Port combination. The index is shown in ascending order (within Slot/Port combination) but need not be contiguous.

NOTE

The repeater number reported will change if the repeater within a device is moved to another device or if the unit is isolated. Also, an address is only reported once; if an address that is already present in the database is found on another port, the original record is changed and flagged as modified.


HubApp Application

Address TypeThe end station database is capable of storing information for a number of protocols, each with its own addressing format. This parameter allows access to the database indexed on Address Type.

IP AddressDisplays the IP address if relevant.

MAC AddressDisplays the MAC address if relevant.

Security View

The Security View is accessed by highlighting the icon and then selecting the Security option from the Icon Subviews menu. It displays the following information in the Security Enable Table:

Security Enable Table

This is a table of permission for access to the device from each of its interfaces. The table has five rows, one for each access level. (Users are assigned security levels in the Security Users Table View.)

Security LevelDisplays the security level, which also acts as the index for the table. Possible levels are Monitor, SecureMonitor, Manager, Specialist and Security.

CommunityThe community SNMP access permission: Enable, Disable, PermanentlyEnabled or PermanentlyDisabled. You can update this field in the Security Enable Table Entry View.

SecureThe secure SNMP access permission: Enable, Disable, PermanentlyEnabled or PermanentlyDisabled. You can update this field in the Security Enable Table Entry View.

NOTE

Double-clicking an entry in this table displays the Security Enable Table Entry View.


HubApp Application

TerminalThe local terminal access permission: Enable, Disable, PermanentlyEnabled or PermanentlyDisabled. You can update this field in the Security Enable Table Entry View.

TelnetThe Telnet access permission: Enable, Disable, PermanentlyEnabled or PermanentlyDisabled. You can update this field in the Security Enable Table Entry View.

FrontPanelThe front panel access permission: Enable, Disable, PermanentlyEnabled or PermanentlyDisabled. You can update this field in the Security Enable Table Entry View.

Security Users Table View

The Security Users Table View is accessed by clicking the Security Users button in the Security View. It is used to add users, modify their security levels and to delete users. (The default users, Monitor, Manager and Security, cannot be deleted.) The table displays the following information:

StatusIndicates the User status; Valid or Invalid. A value of Invalid means the user can no longer access the device. Default users, Monitor, Manager and Security, cannot have their status changed to Invalid. You can update this field in the Security Users Table Entry View.

NameDisplays the user name as an ASCII string. This is the index for the table and empty user names are not allowed.

LevelIndicates the user’s access level defining the scope of management this user can undertake. (The levels are the five levels in the Security Enable Table.) You can update this field but note that the access level of default users cannot be changed.

PasswordThe password required for user confirmation when access is made via the local serial port, the front panel or via Telnet. The Password field is only available in the Security Users Table Entry View; it is a write-only field.

NOTE

Double-clicking an entry in this table displays the Security Users Table Entry View.


HubApp Application

CommunityThe community string identifying the user when access is via the original community-based SNMP (RFC1157). You can update this field.

Local PartyThe local party identity of the user when access is made via secure SNMP. You can update this field.

Manager PartyThe manager party identity of the user when access is made via secure SNMP. You can update this field.

Adds an entry to the table.

Security Audit Table View

The Security Audit Table View is accessed by clicking the Security Audit Log button in the Security View. The audit log records all updates to the managed database on the device. The log is circular; that is, when it is full, the oldest entry is overwritten and this becomes the normal way of updating the table. Therefore, the audit log must be read regularly by a management device so that a more permanent record of the management history can be stored.

The audit log displays the following information in the table. You cannot update any information in the log.

IndexDisplays the index for the table. This is a value between 1 and 65535 which “wraps round” after reaching its maximum value.

TimeDisplays the time of the last update request, in hundredths of a second since the last system restart.

UserDisplays the name of the user making the request.

ObjectDisplays the object identifier of the item being updated. This includes any qualifier for the item.

ValueDisplays the new value for the item.

ResultDisplays the result of the update request as one of the following:

Success Update succeededPending Update not yet completed

Add Entry


HubApp ApplicationFault Table View

Too-big Value was rejected as too big for the itemFailed Value rejected by access functionLocked Item is locked by another managerSecurity-violation User does not have correct access level for this requestNo-such-function Item is read-onlyNo-such-item Item does not exit

Fault Table View

The Fault Table View is accessed by highlighting the 3ComfaultApp icon and then selecting the Configuration option from the Icon Subviews menu.

Modified FlagMake sure this flag is set to Clean-Read before examining the Fault Table. If it has a value of Modified, the table has been updated during the read process. Re-open the View to update the Fault Table.

Fault Table

Each entry in the Fault Table provides information about one fault.

Error NumberDisplays the number for this entry in the error log.

Time StampDisplays the time when the fault occurred, in milliseconds since startup.

Restart CountDisplays the number of restarts already made at the time of this fault.

Gauges Group View

The Gauges Group View is accessed by highlighting the 3Comgauges2App icon and then selecting the Configuration option from the Icon Subviews menu. The view comprises the Gauge Table and several fields below the table.

Gauges Table

This table allows alarms to be set up on items in the MIB. Double-clicking any of the fields within the table opens the Gauge Table Entry View.


HubApp Application

Gauges Group View

IndexDisplays the index of the entry, allocated by the Alarms Subsystem.

Object IDDisplays the Object ID and qualifier of the item to be monitored.

Item TypeDisplays the type of item: counter, unsgmeter (unsigned meter) or sgmeter (signed - positive or negative - meter). Counters will always have a positive value.

SPADisplays the number of samples used to calculate the Alarm Value. The default value is 4. If a value of 1 is used, there is no averaging and the Value field shows the most recent sample.

PeriodIndicates the number of seconds between samples. Therefore, the averaging period is the Period times the SPA.

ValueDisplays the most recently computed average. For a meter (signed or unsigned), this is the average of the samples. For a counter, the value is the average of the differences between successive samples.

Counters and unsigned meters are unsigned 32-bit values with a maximum value of 4294967295. Signed meters are signed 32-bit values and have a maximum of + or - 21474833647 divided by the value in the SPA field.

PeakDisplays the highest recorded alarm value. This will be a signed or unsigned 32-bit value (depending on the Item Type).

ThresholdDisplays the value of the alarm which causes the Gauge State to move from the Ready state to the Fired state and the Threshold Action to be taken. This will be a signed or unsigned 32-bit value (depending on the Item Type).

RecoveryDisplays the value of the alarm which causes the Gauge State to move from the Fired state to the Ready state and the Recovery Action to be taken. This will be a signed or unsigned 32-bit value (depending on the Item Type).

Threshold ActionDisplays the action to be taken when an alarm crosses the Threshold level. The default action is to send a trigger event (sendTrap). Other actions are

NOTE

Update this table using the Table Update button, not by double-clicking an entry. Before updating any of the Gauge Table fields, turn the alarm off using the Gauge State field. Turning the alarm off and on again affects the data: the sampling data, Value, Peak and Status are not lost, but any updates to the index will fail since they are read-only.


HubApp ApplicationGauges Group View

device-specific and may not be available on all devices. See the RMON Event Table for the actions supported by your device. You can update this field for the MSH hub.

Recovery ActionDisplays the action to be taken when a “fired” alarm crosses the Recovery level. The default action is to send a recovery event (sendTrap). Other actions are device-specific and may not be available on all devices.

Gauge StateDisplays the current state of the alarm. You can update this field.

OnTriggersEnabled The normal active state of an alarm. The Value is updated on every sample and if it crosses the Threshold or Recovery level, the corresponding action is taken.

OnTriggersDisabled Used when a new device or alarm is set up and the Threshold and Recovery levels have not been calibrated. The alarm runs as normal and the Value and Peak are updated. No action is taken.

Off De-activates the alarm, allowing it to be configured safely.

Deleted This invalidates the alarm. Values are no longer updated.

AutoCalibrate Setting this value updates the Threshold and Recovery fields according to the current Peak value. The State then becomes onTriggersEnabled. (You cannot set autoCalibrate when the alarm is deleted.)

After autoCalibration:

Threshold = Peak * Threshold Level Scaler

Recovery = Peak * Recovery Level Scaler

When the State is either onTriggersEnabled or onTriggersDisabled, all fields for the alarm are validated. If any of the fields is invalid, the operation will fail.

The sampling data, Value, Peak and State can be reset by setting this field to onTriggersEnabled, onTriggersDisabled or autoCalibrate when it is in either of the “on” states.

Gauge OwnerShows the entity that configured this entry. You can update this field.


HubApp Application

Fields

Table SizeDisplays the number of entries in the Gauge Table. This depends on the requirements and resources of the device. In practice the maximum will be approximately 1000.

Next Free IndexDisplays the index that must be used for the next table entry.

Threshold Level ScalerWhen the alarm is calibrated automatically, the Threshold is set to this percentage of the Peak value (Peak divided by the value in this field, times 100). You can update this field. Values between 1 and 65535 are allowed.

Recovery Level ScalerWhen the alarm is calibrated automatically, the Recovery is set to this percentage of the Peak value (Peak divided by the value in this field times 100). Values between 1 and 65535 are allowed. You can update this field.

Displays a view in which you can update an entry. Only one attribute can be updated at a time, as explained by the following field descriptions.

Configure Obj IDType in the Object ID of the entry that you want to update.

Configure ColumnSelect the attribute (column) that you want to update from the list. The entries in the list reflect the Object ID selected. Possible selections are ItemType, SamplesPerAverage, SamplePeriod, ThresholdLevel, RecoveryLevel, ThresholdAction, RecoveryAction, and GaugeState.

Config ValueType in the new value for the selected attribute.

Local SNMP View

The Local SNMP View is accessed by highlighting the 3ComSNMP2App icon and then selecting the Configuration option from the Icon Subviews menu. (The view can also be accessed from the main Icon Subviews menu by selecting Local SNMP.) This view has minor variations between devices as described in this section.

The view comprises the SNMP Trap Table and the Next Free Index field below the table.

Table Update


HubApp ApplicationLocal SNMP View

SNMP Trap Table

This table stores the destination addresses of SNMP managers that wish to receive traps from this device. Double-clicking an entry in this table displays the SNMP Trap Table Entry View in which you can update several fields. This table contains the following information.

IndexDisplays the index for this entry.

DestinationDisplays the network address of the device to which SNMP traps will be sent.

ProtocolIndicates the transport protocol to use when sending the trap is displayed: IP, IPX or None.

CommunityIndicates the SNMP community string to be used when sending the trap. You can update this field.

CategoryDisplays the 32-bit mask indicating the categories of traps in which the Destination is interested.

The value for this field is one of the following:

‘00000001’h High priority configuration traps‘00000002’h Low priority configuration traps‘00000004’h High priority security traps‘00000008’h Low priority security traps‘00000010’h Alarms and polling traps‘00000020’h Regular heartbeat traps‘00000040’h End Station Table traps‘00000080’h Reserved‘00000100’h Physical entity traps‘00000200’h Facility traps‘00000400’h Service related traps

A value of 0xFFFFFFFF enables all traps.

ThrottleDisplays the maximum rate at which the Destination is willing to receive traps (in milliseconds). You can update this field.

This is specified as the minimum interval between traps. For example, a value of 2000 will limit traps sent to one trap every 2 seconds. A value of zero indicates that no trap throttling is required, i.e., there is no maximum.

Row StatusDisplays the status of each entry. Possible status values are described below.

Fields that appear below the table are as follows:


HubApp Application

Next Free IndexDisplays the index that must be used for the next table entry.

Displays the Add SNMP Table Entry View in which you can add a new entry. Fields in which information may be entered include the Destination, Community, Category and Throttle fields described above, as well as the following:

Instance

Row StatusYou can update this field, using the following status values:

Active This status can be displayed and set.NotInService This status can be displayed and set.CreateAndGo Used only when adding entries.CreateAndWait Used only when adding entries.Destroy Deletes the entry.

Poll Table View

The Poll Table View is accessed by highlighting the 3CompollApp icon and then selecting the Configuration option from the Icon Subviews menu. (This view can also be accessed by selecting Poll Config from the main Icon Subviews menu.) The view contains the Poll Table, and the Next Free Index field and Add Entry button below the table.

Poll Table

This table is used to provide remote device monitoring facilities. It allows a table of network devices to be set up and polled once only, or regularly, by a variety of protocols. The table can be configured to inform the management station(s) of devices that are not responding to polls, or that have started to respond after a period of silence.

The minimum effort required to perform a single poll is as follows:

1. In one packet, write the Address, Rate=Once-Only and Row Status =Create&Go.

2. In the next packet, read the Trip Time.

The minimum effort requried to monitor a device is as follows:

1. In one packet, write the Address, Rate=30-seconds and Row Status =Create&Go.

Add Entry


HubApp ApplicationPoll Table View

2. Wait for traps to come in.

IndexDisplays the index for the table.

AddressDisplays the network address of the device to monitor. Typically, this is an IP, MAC or IPX address. You can update this field in the Poll Table Entry View. The following formats can be used:

• IP: nnn.nnn.nnn.nnn - dotted format• IPX: AABBCCDD:AABBCCDDEEFF - network:node

ProtocolIndicates the protocol to use to monitor the device. A default entry is made using the format of the address in the Address field. You can update this field in the Poll Table Entry View. Possible values are: Unknown, IP IPX, Learn and LLC. If the protocol is not supported or not compatible with the Address format, an error is returned when you try to set the Row Status field to Active or NotInService.

RateIndicates how often a poll packet is sent. You can update this field in the Poll Table Entry View. Possible values are Once-Only, 30-Seconds, Minute, 5-Minutes, 30-Minutes and Hour.

Once-Only The default: when the Row Status is set to Active, only one poll packet is sent. There are no re-transmissions and no traps are generated. The results are displayed in the Poll Sent and Trip Time fields. When the reply is received, the Row Status is changed to NotInService.

Other values When the Row Status is set to Active, the device is polled regularly. The results are displayed in the Poll Sent and Trip Time fields. After four unsuccessful polls, a Lost Contact trap is generated. (An unsuccessful poll is when the Trip Time is still zero when the next poll is due to be sent.) The next successful poll generates an Established Contact trap. Changing the row Status from Active, stops the polling. In particular, changing to NotInService and back to Active is a convenient way of stopping and restarting polls. The other values are 30-Seconds, Minute, 5-Minutes, 30-Minutes, Hour.

NOTE

The first row of the table is only used for once-only polls.


HubApp Application

TargetThis field is not used by the device but describes the Target type as being either a file server or another type of device. You can update this field.

Poll SentDisplays the System Up Time at which the last poll was sent to the device. A value of zero means that no poll was sent or that it could not be sent; for example, there is a protocol error.

Trip TimeDisplays the round trip time in milliseconds, of the most recent poll. A value of zero means that no reply was received. Times below one hundredth of a seconds are shown as 10 milliseconds.

InformationShows some protocol-specific information from the last poll:

IP protocol The Time-To-Live value from the packet header.

IPX protocol The number of router hops made by the poll response packet.

AlarmDisplays the alarm index from the RMON Alarm Table. The alarm indicated is being used by the Poll Table to provide timing and trap generation facilities. If this value is zero, then no alarms are associated with this table entry.

OwnerDisplays the administratively assigned name of the owner of this resource. The RMON OwnerString conventions are used to help control multi-manager situations. You can update this field in the Poll Table Entry View.

Row StatusOnly available in the Poll Table Entry View, this field controls the polling. You can update this field. Possible settings are as follows:

Read/write states Active, NotInService. (If any of the configuration parameters are changed when the status is set, polling stops and the status changes to NotReady.)

Read-only NotReady, Write-only states Create&Go, Create&Wait.

The following appear below the table:

Next Free IndexDisplays the index that must be used for the next table entry in this field.

Displays the Poll Table Entry View in which you can add table entries, set the Row Status for a new entry, and change Rates.

Add Entry


HubApp ApplicationMSH Mgmt Configuration View (MSH only)

MSH Mgmt Configuration View (MSH only)

The MSH Mgmt Configuration View is only supported by the MSH Hub device. It is accessed by highlighting the 3ComMSHMgtApp icon and then selecting the Configuration option from the Icon Subviews menu. (The view can also be accessed from the main Icon Subviews menu by selecting MSH Mgt Card.)

This view contains two fields, three tables and leads to the Mgmt MAC Table, described below.

Temp Sensor OutputDisplays the output provided by the temperature sensor on the management card: OK, Warm or Danger.

Input Status

This table provides information about, and allows configuration of, four general purpose input provided by the MSH management card. Double-clicking an entry in this field displays the Input Status Entry View in which you can update the Trap Enable and the Names for that entry.

IIndex identifying one of the four inputs.

StateEach input is a pair of wires. To provide input the two wires must be connected by an external switch; for example, a relay or micro-switch. This field shows whether the switch is Open or Closed.

Trap EnableShows whether or not the Status is being monitored. Setting this field to Enabled in the Input Status Entry View means that changes of state will be monitored. Any change from Open to Closed or vice versa will generate an SNMP Trap.

NamesThis is a string associated with the input; by default, ‘Status Input n’, where n is the number of the input. You can update this field in the Input Status Entry View to provide a more descriptive name for the use of this input.

NOTE

The value is de-bounced so that multiple closures of a ’bouncing’ relay do not cause multiple traps.


HubApp Application

Led Table

Double-clicking an entry in this table displays the Led Table Entry View in which you can update the Attention State.

SlotShows which LED (and hence card) this row of the table describes.

ColourDisplays the current color of the LED. This field is intended to be used by a physical device view application.

AttentionThis field is normally displayed with the setting of OK. Setting the value to Attention, causes the LED to become red. This is intended to be used to help identify a particular card when maintaining a large system.

Displays the MSH Mgmt MAC View, described below.

MSH Mgmt MAC View

Access this view by clicking the Mgmt MAC Table button in the MSH Mgmt Configuration View. The MSH chassis provides the ability for the management card to use either its own MAC or to share the MAC provided by another card in the chassis. At any time, there may by a number of MACs from which the management card can choose. This table provides a summary of the available MACs (including that on the management card itself) and allows the manager to select one for use.

Double-clicking an entry in this table displays the MAC Status Entry view in which you can update the Status; that is, to enable or disable a shared MAC.

SlotDisplays the card on which this MAC resides. This is the first index to the table.

IndexThis index is displayed to distinguish between MACs on the same card.

BCast AvailDescribes the ability of the MAC to send and receive broadcast packets.

Mgmt MAC Table

NOTE

The shared MAC is used to transmit and receive SNMP frames. If you select a MAC with insufficient capability, that request will be rejected.


HubApp Application

LSAP FiltDescribes the ability of the MAC to filter packets based on the contents of the LSAP field locally to the card. This can improve performance but is not required for protocol operation. If present, the management card will automatically make best use of this feature.

Type FiltDescribes the ability of the MAC to directly filter packets based on the type field, locally to the card. The type field is held in a SNAP header in IEEE networks or in the Ethernet type field. This can improve performance but is not required for protocol operation. If present, the management card will automatically make best use of this feature.

Max PDUDisplays the maximum number of data octets that can be transmitted or received using the shared MAC. When used for SNMP, it is likely that a larger PDU size will improve the performance of some management operations.

MAC AddressThis physical MAC address of this MAC.

StatusThis field is used to enable or disable a shared MAC. You can update this field in the MAC Stats Entry View. Possible settings are as follows:

Available This MAC is available to run SNMP on behalf of the management card.

Unavailable This MAC cannot be selected to run SNMP on behalf of the management card. The MAC may be in this state for a number of reasons including; insufficient resource on the card or that the shared MAC is already in use for some purpose other than SNMP.

SnmpMac This MAC is currently being used as the physical interface for management card SNMP traffic.

This is also the value to set to select a MAC to be used. (This MAC must currently be Available.) If the selected MAC is available and suitable, then the MAC currently having the setting of SnmpMac will become Unavailable. If the selected MAC does not have sufficient resources, the selection will fail and the Status will remain as previously set.

NOTE

A minimum PDU size of 474 octets is required for SNMPv1.


HubApp Application

Power Supply Configuration View (FMS/FMSII only)

Power Supply Configuration View (FMS/FMSII only)

The Power Supply Configuration View is accessed by highlighting the 3CompowerApp icon and then selecting the Configuration option from the Icon Subviews menu. (The view can also be accessed by selecting Power Supply from the main Icon Subviews menu.) The view contains the Power Supply Table and two fields.

Stack Backup PresentIndicates whether a Resilient Backup Power Supply is being used by this stack of units.

Stack Backup DataSupplies all the information about the power supplies attached to each unit in a stack. There is one octet for each unit in the stack.

Power Supply Table

This table provides the status of all power supply units in an FMS stack. Double-clicking an entry in this table displays the Power Supply Table Entry view for that entry. However, you cannot update information in either view.

IndexDisplays the unit (1-8) to which this entry applies.

RBS PresentIndicates if a Resilient Power Supply unit is attached to the unit.

RBS StatusIndicates the status of the Resilient Power Supply attached to the unit. The possibilities are as follows:

RBSNot Applicable The unit does not support Resilient Power Supplies.

RBSOK The Resilient Power Supply is functioning with no faults.

RBSFault The Resilient Power Supply has a fault.

System Loader View

The System Loader application supports the System Loader View which is accessed by highlighting the 3ComsysLdApp icon and then selecting the Configuration option from the Icon Subviews menu. (This view can also be accessed by selecting System Loader from the main Icon Subviews menu.) This view has minor variations depending on the device.

The following information is displayed:


HubApp ApplicationSystem Loader View

System Loader Table

This table is used to control the loading of new software images to the devices controlled by the management agent. By convention, the first entry in the table (Type=System) controls the loading of the device containing the management agent itself. Agents which have no subsidiary devices will have only this entry in the System Loader Table. For agents with subsidiary devices, the other entries control the loading of software into these devices. Double-clicking an entry in this table displays the System Loader Entry View in which you can update the filename and Service Address fields for that entry and initiate a download.

TypeDisplays the type of device to load. Simple agents contain only one device type which is always “system.” Subsidiary agents have the type “component.” In general, a “system” device is one which monitors and manages the operation of component devices.

InstDisplays the instance of the device type in the Type field.

StatusDisplays the status of the last system load operation requested for this device. If the download failed, the reason is displayed. Possible status settings are as follows:

“Normal” states LoadPending, LoadActive, Success and Paused

Error states FileNotFoundAccessViolationIllegalOperationUnknownTransferIDNoSuchUserNoResponseNoResourceRecLenMismatchInvalidRecTypeChecksumErrorWrongDeviceWrongHardwareVersionNoFileHeaderByteCountErrorInvalidProgAddressEraseFailedProgFailedModInvalidAddressModChecksumErrorModTimeoutModBusyModRemovedModNoResourceModFailure


HubApp Application

System Loader View

SWVersDisplays the version of the software running in this device.

HWVersDisplays the revision number of the hardware running on the device.

FilenameDisplays the name of the file which contains the software image to load, or which was last loaded. You can update this field.

Server Addr or Server IPDisplays the IP address of the host containing the Filename. You can update this field. This can be either an IP address in the standard dotted format, or an IPX address in the format aabbccdd:112233445566. An error is returned if the agent does not support the download protocol implied by the address format.

ProtocolDisplays the protocol to use when downloading the software. This is determined from the format of the address in the Server Addr field.

LoadThis field is only available in the System Loader Entry View. Always displayed as NoAction, set the value to StartDownLoad to load the new software as specified in this entry.


HubApp ApplicationSystem Loader View


9031395 E3

Chapter 6

Serial I/F Application Views

What Is in This ChapterThis chapter describes the Application Views for the following major applications for the 3Com FMS/FMSII/10BTi/MSH device:

• Serial I/F Application (3ComserIfApp)

The Serial/IF major application supports the following sub-applications and related views:

- Multi Repeater Application (not for 10BTi)- mrmResilience Application (not for 10BTi)

Figure 6-1 shows the part of the Application View containing the Serial/IF application icons and their sub-application icons.

6-1

What Is in This ChapterSerial I/f Application: V.24 Port Config View


Serial I/f Application: V.24 Port Config View

The Serial Interface application supports the V.24 Port Config View. It is accessed by highlighting the 3ComserIfApp icon and then selecting the Configuration option from the Icon Subviews menu. It contains the V.24 Port Configuration Table and the Slip Port field below the table.

Hub3ComFMS

Model Name

Hub

3ComHubApp

3ComHubApp

Serial If

3ComserIfApp

3ComserIfApp

Multi Repeater

3CommultiApp2

3CommultiApp2

mrm Resilience

3CommrmResA

3CommrmResAp

Fault Table

3ComfaultApp

3ComfaultApp

Gauges

3ComgaugesAp

3ComgaugesApp

Local SNMP

3ComSnmpApp

3ComSnmpApp2

SNMP-Repeater

3Com1516App

3Com1516App

Poll

Serial I/F Application Views 3Com FMS/FMSII/10BTi/MSH Hubs6-2 Management Module Guide

What Is in This Chapter


V.24 Port Configuration Table

This table describes the configuration parameters for the V.24 ports.

IdDisplays the Port Id and index for this table.

ConnShows whether the port is connected Locally to a terminal or terminal emulator (in which case no interface signals need to be asserted unless asserted by other management options) or Remote - to a modem (when at least DSR is required to be asserted). You can update this field in the V.24 Configuration Table View.

Auto ConDetermines if the next four parameter values are to be determined automatically (Enabled) from an initial character sequence entered by the user, or if they are to be determined by the values entered in the next four fields (Disabled).

SpeedIndicates the receive and transmit speed of the port, if Auto Config is Disabled. Different speeds for receiving and transmitting are not possible. You can update this field in the V.24 Configuration Table View.

Char SizeDisplays the character size (7 or 8 bits), if Auto Config is Disabled. You can update this field in the V.24 Configuration Table View.

Stop BitsDisplays the number of stop bits (1, 1.5 or 2), if Auto Config is Disabled. You can update this field in the V.24 Configuration Table View.

ParityIndicates the parity option to use, if Auto Config is Disabled. You can update this field in the V.24 Configuration Table View. Possible settings are as follows:

noParitySpaceParity Parity bit always zeroMarkParity Parity bit always 1OddParityEvenParity

NOTE

Double-clicking an entry accesses the V.24 Configuration Table Entry View in which you can update several fields for the selected entry.

9031395 E3 Serial I/F Application Views6-3

What Is in This ChapterSerial I/f Application: V.24 Port Config View

DSR ContDetermines whether DSR needs to be asserted for a local connection to be made, and if the connection needs to be released if DSR is seen deasserted. This field only applies to local connection types. You can update this field in the V.24 Configuration Table View.

DCD ContDetermines whether DCD needs to be asserted for a local connection to be made, and if the connection needs to be released if DCD is seen deasserted. This field only applies to local connection types. You can update this field in the V.24 Configuration Table View.

Flow Cont Indicates the flow control protocol to be used. You can update this field in the V.24 Configuration Table View. Possible settings are as follows:

NoFlowControl

XonXoff

RtsCtsFullDplx Uses the rts and cts lines as two independent signals. The DTE signals to the DCE that it is prepared to accept more data by asserting RTS; the DCE signals to the DTE that it is prepared to accept more data by asserting CTS.

RtsCtsHalfDplx Uses CTS as a response to RTS. The DCE flow controls the DTE by only returning CTS as a response to a RTS from the DTE when the DCE can accept more data. The DTE flow controls the DCE by only raising RTS when it does not want to receive any more input and dropping it when it is ready to receive more.

UpdateSet Change in this field in the V.24 Configuration Table Entry View to force the port to update its parameters.

The following field appears below the table:

Slip PortDisplays the serial port which SLIP can use to send and receive packets. If this field has a value 0xFFFF, then SLIP cannot send or receive packets. You can update this field.


Multi Repeater Application Views


Multi Repeater Application ViewsThe Multi Repeater application supports the following views:

• Multi Repeater Configuration View, leading to the Multi Repeater Port Configuration View;

• Multi Repeater Performance View, leading to several other views and pie charts.

Multi Repeater Configuration View

The Multi Repeater Configuration View is accessed by highlighting the 3CommultiApp2 icon and then selecting the Configuration option from the Icon Subviews menu. It contains the Card Table below the header.

Card Table

IDDisplays the Service ID. It identifies one of the repeaters within the chassis as the target of a request.

SlotDisplays the slot occupied by the card.

Port CapacityDisplays the number of ports that can be contained within the group (in the range 1 to 1024). This will usually be the number of ports on a module, card or board, and the port numbers will correspond to the numbers marked on the physical entity.

Card TestTests the operation of the card. Setting the value Test in the Multi Repeater Card Entry View causes the card to perform a disruptive test. The result of the test, Passed or Failed, is displayed on completion.

Disable on Boot PortsShows the ports to be disabled on power up or reset. They are determined from a hardware strap which cannot be changed via software. The value in the field is a mask containing a single bit for each port on the card. Port 1 is

NOTE

Double-clicking the ID or Slot of an entry displays the Multi Repeater Port Configuration View described in this section. Double-clicking one of the other fields displays the Multi Repeater Card Entry View for that entry in which you can set the Test field.


Multi Repeater Application ViewsSerial I/f Application: V.24 Port Config View

represented by bit 0, and so on. Ports represented by a zero bit are disabled. This field is useful for setting up resilient pairs.

MDI EnableDisplays either MDI Enable or MDI Disable. 10Base-T line cards are usually configured as MDI Disabled to link to an external network device (internal crossover). Port 1 may be configured MDI Enabled to link to another 10Base-T card (with no internal crossover).

Multi Repeater Port Configuration View

The Multi Repeater Port Configuration View is accessed by double-clicking the ID or Slot fields in the Card Table in the Multi Repeater Configuration View. It contains two tables.

Port Info Table

The Port Info Table includes the following fields:

ID Displays the repeater for which this entry contains information.

SlotDisplays the card slot on which this port resides.

IndexDisplays the port.

InterfaceDisplays the type of electrical interface made available for this port. It does not specify what the actual medium to the End Station is.

NOTE

ECS line cards show a value of Unknown because the configuration cannot be accessed via the management interface.

NOTES

Double-clicking an entry in either table displays the Multi Repeater Port Entry View.

In order for Port Resolution to work during Autodiscovery, the EST filter, if present, should be set to Forward MAC or Forward ALL on all ports for which port resolution is desired.




ConnectorDisplays the type of physical connector on the port. This is distinct from the media. For example, UTP may be connected to the port via either an RJ45 or a Telco connector.

AutoPartionedShows whether the port is currently partitioned by the repeater’s auto-partition protection. For more information on port partitioning, see Section 9 in the IEEE 802.3 Standard.

LinkShows whether there is a signal on this port. It applies equally to fiber or copper connections. This field is correct, irrespective of the Admin state (in the Port Config Table) or the AutoPartitioned field.

BootShows the default state for this repeater, after a reset. Possible states are Enabled or Disabled.

SecurityShows whether security is an available feature on this port. Only ports with security available have an entry in the Repeater Security Table.

ModuleShows whether or not the port is a modular port.

FunctionDisplays the function of the port. Possible functions are Unknown, Repeater or Bridge.

Port Config Table

The Port Config Table includes the following fields:

ID Displays the repeater for which this entry contains information.

SlotDisplays the card slot on which this port resides.

IndexDisplays the port.

AdminSetting this field to Disabled in the Multi Repeater Port Entry View disables the port. The port must then be specifically Enabled before it can send or receive data. This field takes precedence over the AutoPartitioned field. When the port is Disabled, the AutoPartitioned field is frozen until the port is Enabled. It is then set to Unpartitioned, irrespective of its previous setting.



Part EventSpecifies whether a trap should be sent if the port partition changes state (Enabled).

Link EventSpecifies whether a trap should be sent if the link state changes (Enabled).

Link PulseDetermines whether link pulse generating and monitoring is Enabled (standard) for a 10Base-T port. For other ports, this field should have a value of NotApplicable.

DUD ActionDisplays the DUD action of this port: NoAction, Notify or Disconnect. You can update this field.

Multi Repeater Performance Views

The Multi Repeater Performance View is accessed by highlighting the 3CommultiApp2 icon and then selecting the Performance option from the Icon Subviews menu. It contains three tables below the header: the Repeater Frames and Octets Table, the Repeater Error Table and the Repeater Frame Lengths Table.

Double-clicking an ID field in any of the three tables displays the Multi Repeater Card Performance View. (Double-clicking any of the other fields in the Repeater Frames and Octets Table, the Repeater Error Table or the Repeater Frame Lengths Table displays performance statistics in pie chart form.) This view contains the same fields as the Multi Repeater Performance View, as that information pertains to cards. Double-clicking a card field in any of these three tables, displays the Multi Repeater Port Performance View. Double-clicking one of the other fields displays card performance statistics in pie chart form.

The Multi Repeater Port Performance View also contains the same three tables, providing information on a port by port basis. In the following descriptions of the three tables, the explanations of a field apply equally to the Multi Repeater Performance View for the repeater, for a card, or for a port. In many cases, the count for a card or repeater is simply the sum of the numbers recorded by counters on individual ports.

NOTE

Set a value of ForwardNone for inter-repeater links to prevent the database being filled with remote information.




In addition, the Multi Repeater Port Performance View contains two more tables which are also described in this section.

Double-clicking the Port ID field in any of these five tables displays the Multi Repeater Port Information View, with a summary for the selected port from the five tables. From the Multi Repeater Port Information View, two buttons provide access to the Port Errors and Port Frame Sizes Information Views for this port. These views are useful because they display the complete index for the port, Service ID, Card and Port Index. You cannot update any information in these two views.

Action/ClearThis field is only available in the pie chart views. Setting the value to Clear zeroes all counters.

Repeater Frames and Octets Table

The Repeater Frames and Octets Table includes the following fields:

IDDisplays the repeater, card or port for the table entry.

Read FramesDisplays the number of frames received by the repeater/card/port whose octet count is greater than or equal to the minimum frame size, and less than or equal to the maximum frame size and for which there was no error.

This counter provides one of the parameters for calculating the packet error rate. The approximate minimum rollover time of this counter is 80 hours.

UnicastDisplays the number of readable frames addressed to a unicast (non-card) address seen by the repeater/card/port.

MulticastDisplays the number of readable frames addressed to a multicast (non-broadcast) address seen by the repeater/card/port.

BroadcastDisplays the number of readable frames addressed to the broadcast address ffffffffffff seen by the repeater/card/port.

Read OctetsDisplays the number of readable octets received by the repeater/card/port.

This counter provides an indicator of the total data transferred. The approximate minimum rollover time of this counter is 58 minutes.

UnicastDisplays the number of octets contained in valid frames that have been received, for which the destination was a unicast address. The approximate minimum time for rollover of this counter is 58 minutes.



MulticastDisplays the number of octets contained in valid frames that have been received in which the destination was a multicast address. The approximate minimum time for rollover of this counter is 58 minutes.

BroadcastDisplays the number of octets contained in valid frames that have been received in which the destination was the broadcast address ffffffffffff. The approximate minimum time for rollover of this counter is 58 minutes.

Repeater Error Table

The Repeater Error Table includes the following fields:


FCS ErrorsDisplays the number of frames received with an FCS error that do not have a framing or collision error and which are of a legal frame size. The approximate minimum time for rollover of this counter is 80 hours.

AlignmentDisplays the number of alignment errors, i.e., frames received with an FCS error that have a framing error and are of a legal frame size. The approximate minimum time for rollover of this counter is 80 hours. (If this counter is incremented, then the FCS Errors counter is not incremented for this frame.)

Too LongDisplays the number of frames received with an octet count greater than the maximum frame size. The approximate minimum time for rollover of this counter is 61 days. (If this counter is incremented, then neither the FCS Errors or the Alignment counters are incremented by the frame.)

Short EvntsDisplays the number of carrier events detected whose duration is less than the short event maximum time (between 74 and 82 bit times). The short event maximum time has tolerances included to allow for circuit losses between a conformance test point at the AUI and the measurement point. The approximate minimum time for rollover of this counter is 16 hours.

NOTE

A gauge can be attached to this counter to monitor broadcast storms. Action can then be taken to automatically recover normal network operation.




Short Events may indicate externally generated noise which causes the repeater to transmit runts to its other ports, or propagates a collision (which may be late) back to the transmitting DTE and damaged frames to the rest of the network.

RuntsDisplays the number of carrier events detected which obey one of the following criteria:

• Duration is greater than the short event maximum time and less than the valid packet minimum time (greater than or equal to 552 bit times and less than 565 bit times), with no collisions.

• Octet count is less than 64: the activity duration is longer than the Short Event Maximum Time, with no collisions.

The approximate minimum time for rollover of this counter is 16 hours.

TX CollDisplays (for Repeaters and Ports only) the number of Carrier Event signals for which the Collision Event signal was asserted. The approximate minimum rollover time of this counter is 16 hours.

Late EvntsDisplays the number of late events, i.e., the collisions which occurred after the valid packet minimum time. Specifically, Late Events displays events in which the CollIn(X) variable transitions to the value SQR (see section 9.6.6.2, IEEE 802.3 Standard) while the duration is longer than the late event threshold. (The late event threshold is between 480 and 565 bit times and includes tolerances to allow an implementation to build a single threshold to serve both the late event threshold and the valid packet minimum time threshold.) A late event is counted both as a collision and as a late event. The approximate minimum time for rollover of this counter is 81 hours.

NOTES

An event whose length is between 74 and 82 bit times will increment either the Short Evnts counter or the Runts counter, but not both.

The valid packet minimum time is greater than or equal to 552 bit times and less than 565 bit times and includes tolerances to allow for circuit losses between a conformance test point at the AUI and the measurement point. Therefore, a carrier event between 552 and 565 bit times may or may not be counted as a runt. Runts usually indicate collision fragments (a normal network event). However, in certain situations, usually associated with large diameter networks, a percentage of runts may exceed the valid packet minimum time.



VLong EvntsDisplays the number of carrier events whose duration was longer than the MAU Jabber Lockup Protection Timer TW3. (See sections 9.6.1 and 9.6.5 of the IEEE 802.3 Standard.) Other counters may also be incremented.

Rate MisMatcDisplays the number of packets received which meet all of the following conditions:

• There was no collision.• The duration is longer than the valid minimum packet time.• The data rate is detectably different from the local frequency. The exact

degree of mismatch is defined by the vendor.

When this event occurs other counters whose conditions are also satisfied may or may not be incremented, depending on the implementation of the particular device.

Auto PartDisplays the number of times a port has been automatically partitioned.

Total ErrorsDisplays the total number of errors which have occurred on the repeater/card/port to provide a general indication of performance. Total Errors is the sum of the following errors: FCS, Alignment, Frames Too Long, Short Events, Late Events, Very Long Events and Data Rate Mismatches.

Repeater Frame Lengths Table

The Repeater Frame Lengths Table includes the following fields:


64 OctetDisplays the number of frames (including error frames) with a length of 64 octets received by the port, or by all the ports on this card or repeater.

65-127 OctetsDisplays the number of frames (including error frames) with a length between 65 and 127 octets received by the port, or by all the ports on this card or repeater.








Bandwidth UsedDisplays a running average of the bandwidth in use, expressed as a percentage. This is calculated locally by the agent and therefore does not require processor bandwidth from the management station or occupy network bandwidth communicating with that station.

By default:

• The bandwidth is calculated approximately every 15 seconds.• In every calculation period the number of readable octets (the Read Octets

field in the Repeater Frames and Octets Table) is read.• The calculation is performed on the four most recent samples:

where:

sample (i) Number of readable octets (Read Octets field) for sample (i) minus the number of readable octets for sample (i-1).

time (i) Time between sample (i-1) and sample (i).

K Maximum bytes per unit time (i.e., the bandwidth depends on the ring speed).

A default threshold of 15% exists. If the calculated average exceeds this value, a trap is sent to the management station. Additional traps will not be sent until the average is below 10%.

Errors/10000 PackDisplays the number of errors per 10,000 packets received by a highlighted port. This field provides a running average of the bandwidth in use, expressed as a percentage. The percentage is calculated locally by the agent. Therefore, the calculation does not require processor bandwidth from the management station or occupy network bandwidth communicating with that station.

sample i( )time i( ) K×( )

---------------------------------- 1004

---------×i 1=

4

∑



By default:

• The bandwidth is calculated approximately every 15 seconds.• In every calculation period the number of readable octets (the Read Octets

field in the Repeater Frames and Octets Table) and the total errors (The Total Errors field in the Repeater Error Table) are read.

• The calculation is performed on the four most recent samples:

where:

Errors (i) Number of errors (Total Errors field) for sample (i) minus the number of errors for sample (i-1).

Frames (i) The number of readable frames (Read Frames field) for sample (i-1) minus the number for sample (i).

A default threshold of 2% exists. If the calculated average error exceeds this value, a trap is sent to the management station. Additional traps will not be sent until the average is below 1%.

Port Config

This table only appears in the Multi Repeater Port Performance View, which is accessed by double-clicking the Card field in the Multi Repeater Card Performance View.

PortIndicates the port number for this table entry.

Bandwidth UsedSee description above.

Errors/10000 PackSee description above.

Errors i( )Frames i( ) K×( )

----------------------------------------- 1000×i 1=

4

∑

NOTE

Double-clicking an entry accesses the Table Entry View. You cannot update in this view but the full description of the port, starting at Service ID down, is displayed.




Last AddressDisplays the last MAC address seen on this port.

ChangesDisplays the number of times the MAC address on this port has changed. A high number of changes indicates that this is either an inter-repeater or a multi-drop segment.

Port Traffic Levels

This table only appears in the Multi Repeater Port Performance View.

PortIndicates the port for this table entry.

Traffic LevelUsed internally by the agent to provide a running average of the bandwidth in use (Bandwidth field). Traffic Level is a dummy object.

Error FramesUsed internally by the agent to provide a running average of the error rate (Errors/10000 Pack field). Error Frames is a dummy object.

NOTE

Double-clicking an entry accesses the Table Entry View. The full description of the port, starting at Service ID down is displayed. You cannot update any fields in this view.


Mrm Resilience Application ViewsMrm Resilience View

Mrm Resilience Application ViewsThe Mrm Resilience application supports the Mrm Resilience View, leading to the Standby Map Table.

Mrm Resilience View

Access this view by highlighting the 3CommrmResApp icon and selecting the Configuration option from the Icon Subviews menu. This view contains the Mrm Resilience Table, the Flush Table field below the table and two buttons.

Mrm Resilience Table

This table allows creation and deletion of resilient pairs and provides status control and information. The entries are indexed on the repeater number and slot/port location of the main port.

A device can be configured to have a number of “resilient pairs”: 02.3 point to point connections (for example, UTP that allow two repeaters to be connected together in a resilient configuration). In such a pair, one port is the “main” port, the other the “standby” port. One of these ports is enabled and is the current active port, the other is present in case the active port fails. The device detects the failure and switches ports.

For a resilient pair definition to be valid, both ports must be on the same repeater. The standby port must be configured to be ‘disabled on boot’; that is, it must recover from a power failure in a disabled state. This prevents loops in the network.

RepeaterDisplays the repeater on which both ports are located.

Main SlotDisplays the slot number of the main port in the pair.

Main PortDisplays the port number of the main port in the pair.

NOTE

Double-clicking an entry accesses the Mrm Resilience Table Entry View in which the configuration of a resilient pair can be updated.


Mrm Resilience Application Views

Mrm Resilience View

Main StateDisplays the state of the main port:

Failed Loss of signal on the portOK Port is capable of carrying traffic but is in the standby

stateOKandActive The active port

SBY SlotDisplays the slot number of the standby port in the pair. You can update this field in the Mrm Resilience Table Entry View.

SBY PortDisplays the port number of the standby port in the pair. You can update this field in the Mrm Resilience Table Entry View.

SBY StateDisplays the state of the standby port:

Failed Loss of signal on the portOK Port is capable of carrying traffic but is in the standby

stateOKandActive The active port

Pair StateDisplays the state of the resilient pair; Invalid or Operational (all the parameters in the entry are valid). There are several reasons why the pair may be Invalid. For example, not all the information has been provided, or the resilient pair rules may no longer be valid because of a change in the configuration of the device such as moving a card.

Mod StateIndicates the Modification State of the resilient pair. You must set the Under Mod field in the Mrm Resilience Table Entry View to a value of Under-Mod before changing the configuration of a pair. The changes are not applied until this field shows the value Stable.

Pair ActionChanges the state of the pair. Setting a value of Create configures the pair using the definitions in the entry. Setting Delete removes the entry from the table and terminates operation of resilience on this pair of ports. The setting, TogglePort, swaps the currently active port if the currently non-active port has a status of OK.

Pair EnableEnables or Disables the resilient pair. When Disabled, both ports are disabled.


Mrm Resilience Application Views

The following information appears below the table:

Flush TableDisplays a button for setting this field to Flush which empties the Resilience Table. Once flushed, no resilient links are configured. New links may then be configured.

Opens the Add Resilient Table Entry View. Enter the Instance of the new pair and set the Under Mod field to Under-Mod. This creates an empty entry in the table. Double-click the entry to enter the definition.

Opens the Mrm Resilience Standby Table, described below.

Mrm Resilience Standby Table

The Mrm Resilience Standby Table is accessed by clicking the Standby Map Table button in the Mrm Resilience View. This is a read-only table which provides shortcut information to allow the translation of a port number to a corresponding main port number. This number can then be used to access the Mrm Resilience Table. Each resilient pair has two entries in the table; one for the main port and one for the standby port. (The entry for the main port returns the same port.)

This table contains the following information.

RepeaterDisplays the repeater on which the port is located.

SlotDisplays the slot number of the port.

PortDisplays the port number of the port.

TypeDisplays the type of port; Main or Standby.

Main SlotDisplays the slot number of the main port in the pair.

Main PortDisplays the port number of the main port in the pair.

Add Entry

Standby Map Table


9031395 E3

Chapter 7

Other Application Views

What Is in This ChapterThis chapter describes the Application Views for the following major applications for the 3Com FMS/FMSII/10BTi/MSH device:

• SNMP Repeater Application • FMS-MIB Application (FMS/FMSII/10BTi)• MSH-MIB Application (MSH only)• Token Ring Application (MSH only)

Figure 7-1 shows the part of the Application View containing these application icons and their sub-application icons.

7-1

SNMP Repeater Application Views


SNMP Repeater Application ViewsThe SNMP Repeater Application supports the following views:

• SNMP Repeater-specific Performance View • Configuration View

SNMP Repeater Performance View

The Performance View is the same for all four devices. It is accessed by highlighting the icon and then selecting the Performance option from the Icon Subviews menu.

Total Transmitted CollisionsDisplays the total number of transmitted collisions.

Represents the amount by which the Total Transmitted Collisions counter has changed since the GIB view was last refreshed. The update interval is normally 10 seconds.

Location Prime-App Serial Number

Hub3ComFMS

Model Name

Hub

3ComHubApp

3ComHubApp

M

3

3

m

3

3

Fault Table

3ComfaultApp

3ComfaultApp

Gauges

3ComgaugesAp

3ComgaugesApp

SNMP-Repeater

3Com1516App

3Com1516App

FMS-mib

3ComFMSmib2Ap

3ComFMSmib2Ap

Other Application Views 3Com FMS/FMSII/10BTi/MSH Hubs7-2 Management Module Guide


SNMP Repeater Configuration View (FMS/FMSII/10BTi)

The SNMP Repeater Performance View also provides a time-graph of the collision rate.

SNMP Repeater Configuration View (FMS/FMSII/10BTi)

Access the SNMP Repeater Configuration view by highlighting the 3ComRptrApp (10BTi) or 3Com1516App (FMS) icon and selecting the Configuration option from the Icon Subviews menu.


ResetThis field shows a button which is always displayed as NoReset. Updating the setting to Reset causes a transition to the Start state (see Figure 9.2 of Section 9 of the 802.3 Standard). This action includes a disruptive Self Test, and a Repeater Reset Trap which may be sent. This action does not reset the management counters, or affect ports’ administrative states.

Non Disrupt TestThis field shows a button which is always displayed as NoSelfTest. Updating the setting to SelfTest causes the repeater to perform an agent-specific, no-disruptive self-test. This action will not do the following:

• Interfere with management functions• Reset the state of the repeater or the management information about the

repeater• Inject packets into any segment• Prevent the relay of any packet

After performing the test, the health information is updated. If there has been a change, a Repeater Health trap is sent.

Operational StatusDisplays the operational state of the repeater:

Other Undefined or unknownOK No known failureRptrFailure Repeater related failureGroupFailure Group related failurePortFailure Port related failure

NOTE

Setting this field to Reset may result in the loss of packets.

9031395 E3 Other Application Views7-3


GeneralFailure Unspecified failure

The Health Text field may provide more detailed information. If there is more than one type of failure (for example, repeater failure and port failure), this field will show the failure which has the highest priority, in the following order:

RptrFailure Repeater related failureGroupFailure Group related failurePortFailure Port related failureGeneralFailure Unspecified failure

Health TextDisplays a string showing text related to the operational state of the repeater in this field. Agents may use this field to provide detailed failure information or instructions for resolving problems. The contents of the field are agent-specific.

Partitioned PortsDisplays the number of ports in the repeater whose current state meets all three of the following criteria:

• The port’s operational status is not the value “not present.”• The port’s administrative status is Enabled.• The port is autopartitioned.

Group CapacityDisplays the number of groups that can be contained within the repeater. Within each managed repeater, the groups are uniquely numbered in the range of 1 to the Group Capacity. Some groups may not be present in a given repeater, in which case the actual number of groups will be less than the Group Capacity.

Reconfigures the application.

NOTE

Generally, the group capacity will be the number of field-replaceable units (modules, cards or boards) that can fit in the physical repeater enclosure, and the group numbers will correspond to the numbers marked on the physical enclosure.

Reconfigure Application


SNMP Repeater Chassis Configuration View (MSH)

SNMP Repeater Chassis Configuration View (MSH)

In the Hub3ComMSH, highlighting the SNMP-Repeater Application Icon (3ComchassisApp) and selecting Configuration opens the Chassis Configuration View, which is described in Chapter 3, Chassis Configuration View (MSH only). This view can be accessed from the Icon Subviews menu by selecting Chassis Config.

FMS-MIB Application (FMS/FMSII/10BTi)There are two implementations of the FMS-MIB major application: 3ComFMSmibApp and 3ComFMSmib2App. The icon representing the implementation supported by your device will be displayed in the Application View.

Both implementations support a Configuration View. However, only the 3ComFMSmibApp supports a Performance View. Both views are described in this section.

Linkbuilder Configuration View

Both implementations of the FMS-MIB application support the Linkbuilder Configuration View which is accessed by highlighting the 3ComFMSmibApp icon and selecting the Configuration option from the Icon Subviews menu.

The 3ComFMSmibApp displays more fields than the 3ComFMSmib2App and provides buttons to access three tables, as described below.

Fields & Buttons for the 3ComFMSmibApp

Battery StatusDisplays the results of the start up check on the NVRAM battery condition, by both applications.

POST Results ErrorsDisplays a table of results (in both implementations) of the power on self-tests, by button indicators. If a button is depressed, there is a problem with that function. (Functions include EthernetPROM, SystemRAM, NVRAM, BatteryLOW, MFPerrors, LANCEerrors, MBGAerrors, Watchdog, UnitIds, Repeater, BusError, InterruptError and Unknown.)

Dvt EchoEnables or Disables the Echo service and is intended for test purposes only. This field is write-only.


FMS-MIB Application (FMS/FMSII/10BTi)

Bus FiFo FullDisplays the number of times the management bus was full. This field is a hardware error counter.

Bus Overflow ErrorDisplays the number of management bus overflow errors. This field is a hardware error counter.

Bus Framing ErrorDisplays the number of management bus framing errors. This field is a hardware error counter.

Bus Overrun ErrorDisplays the number of management bus overrun errors. This field is a hardware error counter.

Displays the Fault Table View described later in this section.

Displays the Group Configuration View described later in this section.

Displays the Mau Table View described later in this section.

Fault Table View

This table is displayed by clicking the Fault Table button in the Linkbuilder Configuration View. It displays the following information.

Modified FlagDisplays the status of the information in the Fault Table. This field is updated in real-time. If it shows ‘Clean-Read’, the Fault Table is up-to-date and can be read. If it has a value of ‘Modified’, the Fault Table has been updated since the table was last read. The table does not show the up-to-date values. Update the field to Clean-Read, then close and reopen the view in order to reread the table.

Fault Table

IndexDisplays the index to the Fault Table.

Error NumberDisplays the error number for this entry.

Time StampDisplays the time in milliseconds since startup when the fault occurred.

Fault Table

Group Table

Mau Group



Restart CountDisplays the number of restarts at the time of the fault.

Group Config View

This table is displayed by clicking the Group Table button in the Linkbuilder Configuration View. It displays the following two tables.

Group Table

This table shows configuration options for a given group. This table is for information only: you cannot update any information.

IndexDisplays the group within the repeater, to which this entry applies.

Port MaskThe ports which are present in this group are displayed as a bit mask. Bit 0, the least significant bit, represents port 1, bit 1 represents port 2 and so on. The bits are set as follows: a 0 indicates that the port is not present, while a 1 indicates that it is present.

Media Table

This table provides configuration and control variables for a collection of media for this repeater. Each entry describes one media card. This table is for information only: you cannot update any information.

IndexIdentifies the media card. This field is part of the index for the Media Table.

VersionDisplays the media module hardware revision number.

Card TypeDisplays the media module card type.



Mau Table View

This view is displayed by clicking the Mau Group button in the Linkbuilder Configuration View. This view provides the following information.

Mau Table

Provides MAU (Media Access Unit) information about a group of ports.

GroupIdentifies the repeater group that contains the port to which the MAU is connected.

PortIdentifies the port.

IndexDisplays the MAU described by this entry.

TypeDisplays the 10 Mb/s baseband MAU type as follows:

Other UnidentifiedUnknown Initializing (true state not yet known)AUI No internal MAU, view from AUI10Base5 Thick coax MAU as per section 8*foirl FOIRL MAU as per section 9.9*10Base2 Thin coax MAU as per section 10*10BaseT UTP MAU as per section 14*10BaseFP Passive fiber MAU as per section 16*10BaseFB Sync fiber MAU as per section 17*10BaseFL Async fiber MAU as per section 18*

* Section numbers refer to the 802.3 Standard

Admin StateThe administrative state of the MAU. You can update this field in the Mau Table Entry View. Possible values are as follows:

Other UnidentifiedUnknown Initializing (true state not yet known)Operational Powered and Connected: operates and passes signals to its

attached DTE or repeater port in accordance with its specification.

Standby Inactive but on: this state only applies to link type MAUs. It forces DI, CI and the media transmitter to idle. The Media Available is not affected.

Shutdown Sets the DI, CI and media transmitter condition to be the same as if the device/port were powered down. In this state, the Media Avail and Jabbers field may show the value Other. For an AUI, setting the value to Standby will remove power from the AUI.



Reset This value is not displayed but can be set to reset the MAU (equivalent to a power-off /power on cycle).

Setting a value of Operational, Standby or Shutdown causes the MAU to assume the appropriate state, except that setting a mixing-type MAU or an AUI to Standby causes the MAU to enter the Shutdown state.

Media AvailFor FOIRL, 10BaseT and 10BaseF MAUs, this field is equivalent to the integrity/low light state. For an AUI or coax MAU, this field indicates whether loopback is detected on the DI circuit.

The value of this attribute persists between packets for MAU types, AUI, 10Base5, 10Base2 and 10BaseFP.

For AUI, Coax and 10BaseFP MAUs, this field is only updated during non-collision transmissions. For these MAU types, the value of this field will be unknown during power-up, following a reset. Loopback will be tested on each transmission for which no collision is detected. If DI receives input with a StartUpDelay of the start of the output on DO, loopback will be detected. The value of StartUpDelay is between 15 and 25 bit times. Transition from input to output_idle on DI while output is present on DO may also be detected on loopback.

Possible settings are:

Other UndefinedUnknown Initializing, true state not yet knownPresent Link or light normal, loopback normalNotPresent Link loss or low light, no loopbackRemoteFault Remote faultInvalidSignal Invalid signal

LostMediaDisplays the number of times that the Media Avail field leaves the Available state.

Jabber StateDisplays the Jabber State:

Other Undefined: all AUI MAU types have this state.Unknown Initializing (true state not yet known)noJabber State is normalJabbering MAU is jabbering

If the MAU is in jabber state, this field displays the setting Jabbering. For AUI MAU types, it returns to the value Other.

JabbersDisplays the number of times the MAU entered the Jabbering state.


Security Port Application

Security Port ApplicationThis application contains the Physical Rack Configuration Table, described below.

MSH-MIB Application (MSH only)The MSH-MIB major application is only supported by MSH hubs. It supports the following applications:

• 3ComMSHmibApp• 3ComRingApp sub-application (supported by some MSH hubs)

MSH-Mib Configuration View

The MSH-Mib application supports the Configuration View which is accessed by highlighting the icon and then selecting the Configuration option from the Icon Subviews menu. It displays the following information in the Mau Table. Double-clicking an entry access the Mau Table Entry View.

Mau Table

Provides MAU (Media Access Unit) information about a group of ports.

GroupIdentifies the repeater group that contains the port to which the MAU is connected.

PortIdentifies the port.

IndexDisplays the MAU described by this entry.

TypeDisplays the 10 Mb/s baseband MAU type as follows:

Other UnidentifiedUnknown Initializing (true state not yet known)AUI No internal MAU, view from AUI10Base5 Thick coax MAU as per section 8*foirl FOIRL MAU as per section 9.9*10Base2 Thin coax MAU as per section 10*10BaseT UTP MAU as per section 14*10BaseFP Passive fiber MAU as per section 16*


MSH-MIB Application (MSH only)

MSH-Mib Configuration View

10BaseFB Sync fiber MAU as per section 17*10BaseFL Async fiber MAU as per section 18*

* Section numbers refer to the 802.3 Standard

Admin stateIndicates the administrative state of the MAU. You can update this field in the Mau Table Entry View. Possible values are as follows:

Other UnidentifiedUnknown Initializing (true state not yet known)Operational Powered and Connected: operates and passes signals to its

attached DTE or repeater port in accordance with its specification.

Standby Inactive but on. This state only applies to link type MAUs. It forces DI, CI and the media transmitter to idle. The Media Available is not affected.

Shutdown Sets the DI, CI and media transmitter condition to be the same as if the device/port were powered down. In this state, the Media Avail and Jabbers field may show the value Other. For an AUI, setting the value to Standby will remove power from the AUI.

Reset This value is not displayed but can be set to reset the MAU (equivalent to a power-off, power on cycle).

Media AvailFor FOIRL, 10BaseT and 10BaseF MAUs, this field is equivalent to the integrity/low light state. For an AUI or coax MAU, this field indicates whether loopback is detected on the DI circuit.

The value of this attribute persists between packets for MAU types, AUI, 10Base5, 10Base2 and 10BaseFP.

For AUI, Coax and 10BaseFP MAUs, this field is only updated during non-collision transmissions. For these MAU types, the value of this field will be unknown during power-up, following a reset. Loopback will be tested on each transmission for which no collision is detected. If DI receives input with a StartUpDelay of the start of the output on DO, loopback will be detected. The value of StartUpDelay is between 15 and 25 bit times. Transition from input to output_idle on DI while output is present on DO may also be detected on loopback.

LostMediaDisplays the number of times that the Media Avail field leaves the Available state.

Jabber StateDisplays the Jabber State as follows:

Other Undefined. All AUI MAU types have this state.Unknown Initializing (true state not yet known)noJabber State is normalJabbering MAU is jabbering


MSH-MIB Application (MSH only)Ring Builder Application

JabbersDisplays the number of times the MAU entered the Jabbering state.

Ring Builder Application

This application is supported by some MSH hubs. It supports the following views:

• Ring Builder Configuration View• Ring Builder MAC Address View

Ring Builder Configuration View

Access the Ring Builder Configuration View by highlighting the icon and selecting the Configuration option from the Icon Subviews menu.


Ring Builder Table

This table contains information about the Link Builder MSH Ring Builder module. It contains an entry for each ring builder in the chassis. Double-clicking an entry displays the Ring Builder Entry View.

Each Ring Builder has two external trunk connections by which it may be connected to other Token Ring devices capable of supporting a backup path (for example, another Ring Builder). Each external connection attaches to a dual ring cable. One of the rings is used to carry traffic in a fault-free network; the other is used as a backup. If an error is detected on the main ring, suitable stations (such as the Ring Builder itself) can wrap the active path on to the backup ring. The fault recovery is handled at the Ring In and Ring Out ports.

IDDisplays the ring builder for this table entry.

In MediaDisplays the physical media to which the Ring In port of the Ring Builder is (or could be) connected.

In ModeDetermines the state of the two external connections of the Ring Builder. You can update this field in the Ring Builder Entry View. Possible settings are as follows:


MSH-MIB Application (MSH only)

Ring Builder Configuration View

OpenRing The external connection is to be connected to the external ring. In this mode, if there is no external ring, the ring will be broken.

WrapRing The external connection will be configured to be isolated from the remote ring such that the external Ring In port is looped from the main to the backup ring.

FailSafe The Ring Builder monitors the ring signal for a phantom voltage. If this voltage is present, the external connection is placed into the OpenRing state. If it is not present, the external connection is placed into the WrapRing state. In this mode, the actual state of the connection is displayed in the In State field.

In StateIf the In Mode field is set to FailSafe, this field shows the actual state of the connection. If the In Mode field is set to another value, this field shows the same setting as the In Mode field.

Out MediaDisplays the physical media to which the Ring In port of the Ring Builder is (or could be) connected.

Out ModeControls the Ring Out port connection. See In Mode.

Out StateSee In State.

ModeAs well as controlling the external connections, the Ring Builder controls the interaction with the rest of the ring using this field. You can update this field in the Ring Builder Entry View. The following settings are allowed:

Normal The Ring Builder’s connections are determined by the states of the Ring In and Ring Out ports.

Repeater The Ring In port is connected directly to the Ring Out port internally in the Ring Builder. The external rings (main and backup) are passed straight through, while the MAUs controlled by the Ring Builder are maintained as a stand-alone ring. If either the Ring In or Ring Out port is wrapped, both ports are forced to wrap and the internal ring is unaffected.

NOTE

Not all devices support the generation of a phantom voltage and therefore the FailSafe state may not be appropriate.


MSH-MIB Application (MSH only)Ring Builder MAC Address View

TestDisplays the results of a Ring Builder test. This field is always displayed as NoTest. Setting it to Test in the Ring Builder Entry View starts a Ring Builder test in which the Ring Builder sends a frame to itself and checks whether the frame is received properly. The test does not disrupt the operation of the ring.

DRI StateDisplays the (DRI) Distributive Recovery Interface state. You can update this field in the Ring Builder Entry View. The following settings are allowed: Disabled, Enabled and EnabledwithLock.

Ring Builder MAC Address View

The Ring Builder MAC Address View is accessed by highlighting the icon and then selecting the MAC Address option from the Icon Subviews menu.


MAC Address Table

This table contains an entry for each MAC on each Ring Builder in the chassis.

Service IDDisplays the Ring Builder’s service ID. This field functions as the index for the table.

InstanceThe Ring Builder has two MACs: this field shows whether this MAC is the one for the main ring or the backup ring.

MAC AddressDisplays the MAC address for this Ring Builder/MAC combination.

NOTE

The DRI allows the active MAU to determine which of its stations are beaconing or causing problems on the ring. MAU ports are disabled one at a time, until the faulty station has been removed from the ring. The MAU port remains disabled until the station has been removed (unless the port has been enabled with locking). If DRI lock is enabled, the port will remain disabled until re-enabled by management.


Token Ring Application Views (MSH only)

Token Ring Application Views (MSH only)The Token Ring major application is supported by some MSH devices. There are no sub-applications. The following views are supported:

• Token Ring Configuration View• Token Ring Performance View• Token Ring Topology View• Token Ring Stats View

Token Ring Configuration View

The Token Ring Topology View is accessed by highlighting the icon and then selecting the Configuration option from the Icon Subviews menu.


IdDisplays an index used to select information from one of several logical devices within the same chassis.

NumDisplays the ring number (0 to 4095). The ring number is only relevant in bridged networks. When there are multiple bridged Token Ring segments, the ring number is used to determine routing information through the network. If the ring number is known, it is displayed.

SpeedToken Ring standards exist for 4 Mbps and 16 Mbps operation. If the device can determine the speed, this field displays the actual speed of the ring; otherwise it is shown as ‘Unknown’.

StateDisplays the operational state of the main ring. (If the ring is in an error state, the most severe error is displayed.) The possible states, in increasing order of severity, are as follows:

NotAvailable The state of the ring could not be determined.Normal Normal operationBeacon This state is determined by listening for beacon frames on

the network.SoftError Indicates a high rate of soft errors with respect to the

amount of traffic on the ring. This state is only displayed for devices which can monitor this error.

Fault A serious ring fault: the fault may have been patched by this device looping the main ring onto a backup ring. This state shows that the ring is in error and that the topology of the ring, as reported by any station on the ring, is not a reliable reflection of the normal topology.


Token Ring Application Views (MSH only)Token Ring Performance View

Backup StateThe operational mode of the backup ring. The possible states and their explanations are the same as for the main ring. See the State field.

Wrap StateShows whether the main and backup rings are wrapped. If they are wrapped, it does not mean that they are necessarily wrapped at this ring builder. It could be at another ring builder, an IBM CAU or some other device with dual ring capabilities.

Map ChangedIf the ring topology changes because endstations join or leave the ring, a trap is sent and this field shows the value True. (If the topology changes when the setting is already True, no further trap is generated.)

Change TimeDisplays the System Up Time when the topology last changed, whether or not the change generated a trap.

ActionShows the setting NoAction when displayed. Updating the setting to ClearRingCounters clears all the counters in this table. Setting it to ClearAllcounters also clears all the ring station statistics.

Token Ring Performance View

Access the Token Ring Topology View by highlighting the icon and then selecting the Performance option from the Icon Subviews menu.

This view displays the following information in the TR Standard Stats Table:

TR Standard Stats Table

This table contains an entry for each ring device within the physical device. Two entries may refer to the same physical ring if two logical devices are on the same ring.

Station IdDisplays the index used to identify the ring.

NOTE

You can update this field to ‘False’. This should be done after looking at the Change Time field to determine if the ring has been stable for a reasonable time. After resetting to False, the next topology change will generate a trap.



Beacon CountDisplays the number of ring state transitions from Normal to Beacon mode. The higher the rate, the less reliable the network. A gauge can be applied to this variable to measure the reliability of the network.

Soft ErrorsDisplays the number of isolating soft errors reported by stations on the ring. A high rate of errors is a good indication of a faulty network.

Active Monitor ChangesEvery operational ring has one active monitor and may be more than one standby. It is possible that a standby fails to hear from the active monitor and therefore does not become active. If this happens frequently it is a good indication that there is a problem with the network.

Displays the Token Ring Topology Stats View.

Token Ring Topology View

The Token Ring Topology View is accessed by highlighting the icon and then selecting the Ring Topology option from the Icon Subviews menu.

This view displays the following two tables.

Token Ring Config Table

This table contains information about the stations (addresses) in the local ring segment at the time the table was read. Each row in the table describes one station.

IdDisplays the parameter used to select topology information from a number of logical devices within the same chassis.

IndexDisplays the unique index within the ring topology.

MAC AddressDisplays the physical address of the station at this position.

NOTE

It is recommended that a gauge be attached to this parameter to allow local monitoring of error conditions.

Topology Stats


Token Ring Application Views (MSH only)Token Ring Topology View

MonitorShows whether this station is the active monitor or a standby. Any station can become the active monitor, as determined by an active monitor protocol. The active monitor is responsible for checking the validity of tokens and for general ring housekeeping. Each standby monitor checks whether the active monitor is present. Standby monitors are ready to become active monitors, if necessary.)

Token Ring Config Stats Table

This table contains information about the configuration of stations on the ring.


MAC AddressDisplays the physical address of the station at this position. (This is also the index for the table.)

StateShows whether the station is currently on the ring (Present).

LocationDisplays the Token Ring physical location parameter for the station.

ActionThis field is always displayed as NoAction. Updating to other settings controls the station or the entry in this table representing the station. Possible settings are as follows:

RemoveStation Send a remove station request to the management station.ClearCounters All counters for this table entry are zeroed.DeleteEntry Remove this entry from the table. This action is only

successful if the station is not currently active.ForwardTest If the station is currently in the ring, this request causes

the managed device to test the transmit and receive paths of this station. This is accomplished using the Transmit Forward MAC Frame request. When the test is complete, the managed device sends a test-response trap.

NOTE

This table contains entries for stations that have been on the ring at some time; they do not need to be on the ring right now. Entries should only be discarded if resources are required for new stations. For example, the oldest entry could be the one chosen for deletion.



Token Ring Topology Stats View


The Token Ring Topology Stats View can be accessed in two ways:

• By highlighting the icon and then selecting the Topology Stats option from the Icon Subviews menu.

• By clicking the Topology Stats button in the Token Ring Performance View.

It displays the following information in the Token Ring Topology StatsTable, below the header.

Token Ring Config Stats Table

This table contains station statistics. The statistics are entries for stations that have been on the ring at some time; they do not need to be on the ring right now. Entries should only be discarded if resources are required for new stations. For example, the oldest entry could be the one chosen for deletion.

This table provides the following information.


MAC AddressDisplays the physical address of the station at this position. (It also functions as the index for the table.)

Line ErrorsDisplays the number of line errors reported by the station. This is an isolating error (that is, an error reported by only one station and known to have occurred between this station and its upstream neighbor).

This counter is incremented when a frame or token is repeated by the station and an error bit in the frame is clear, but one of the following tests fails:

• A code violation occurs between the start and end of the packet.• The FrameCheck Sequence is incorrect.

The station sets the error bit and forwards the packet to the next station.

NOTE

Not every MSH hub can support all actions.


Token Ring Application Views (MSH only)Token Ring Topology Stats View

Internal ErrorsDisplays the number of times the station detected a recoverable internal error. This value can be used to detect a ring station that is error prone.

Burst ErrorsDisplays the number of Burst Errors.

The ring token receiver portion of the station expects to see continuous signal transitions on the input. This counter is incremented each time the station fails to see a transition for 5 half bit times. To prevent this error from being recorded on subsequent stations, the detecting station transmits idle after failing to detect a transition after 4 half bit times.

Monitor ErrorsDisplays the number of monitor errors.

On a Token Ring, the active monitor station periodically initiates an active monitor poll by sending an Active Monitor Present MAC frame. Every frame on a Token Ring contains an Address Recognized bit and a Frame Copied bit. Together, they are known as the AC bits. When a station processes a frame, it must set one or both of these bits. A station that simply forwards the frame sets neither bit (00). These bits are used in an active monitor poll as follows:

• When a standby monitor station receives an Active or Standby Monitor Present frame with the AC bits set to 00, it sets the bits to 11 and starts a timer. When the timer expires, it sends a Standby Monitor Present frame.

• When the active monitor station receives an Active or a Standby Monitor Present frame with any AC bit combination, the active poll is considered complete.

The monitor error counter is increased by a station if it receives an Active or a Standby Monitor Present frame with the AC bits set to 00, and then a Standby Monitor Present frame also with the AC bits set to 00. This indicates an error on the ring; perhaps only a configuration error, such as the active monitor being removed from the ring.

Lost FramesDisplays the number of times a station transmitted a frame and did not receive it back before the ring timer expired (that is, the frame did not go around the entire ring). This is a non-isolating error (that is, one that may be reported by several stations). Therefore, it is not possible to determine where the fault occurred on the ring.

Frame Copy ErrorsDisplays the number of times a station received a frame with its own address as the destination, but with the AC bits set to 11 (station recognized and managed to copy the frame). This means that there are two stations on the ring with the same address.




Rx CongestionDisplays the number of times the station received a packet with its own address as the destination, but could not copy the frame due to lack of resources.

Token ErrorsIncrements the counter when it receives an error condition resulting in the need to generate a token. This counter is only incremented by the active monitor station.

Frqu ErrorsDisplays the number of times the station detected an error in the frequency of the received signal.

Soft ErrorsDisplays the sum of the number of isolating soft errors detected by other counters for this station.


Token Ring Application Views (MSH only)Token Ring Topology Stats View


9031395 E3

Index
AAddress Table 3-9Admin. Status 2-14Administrative Status 2-9, 2-14AlignmentErrors 2-10ASCII Agent Information View 5-6Auto Partition State 2-9AutoPartitions 2-10
BBandwidth 2-15

CChassis Configuration View 3-5Collisions 2-10Config Table 3-5Conventions xii

DData Logging 2-7DataRateMismatch 2-10Device Topology View Label/Interface

Number 2-13Device Type 2-8Device View 2-1Device View Banner 2-11

EEnd Station View 5-6

FFacility Table 3-9FCSErrors 2-10Find 2-19FMS-MIB Application 7-5FrameTooLongs 2-10

GGauge Control Panel 2-19Gauge Control Panel Buttons 2-22Gauge Mode 2-20Gauge Type 2-22Gauges Group Configuration View 5-12Generic SNMP Device View 2-1

HHub Application 5-4Hub Application Views 5-4Hub Applications 5-1Hub Configuration View 5-4

IIF Address Translation Table 3-3IF Address Translation Table Label/Physical

Address 2-15IF Status View Label 2-14Interface Description 2-19Interface Options Panel 2-19Interface Setup View 5-5

LLast Change 2-14Last Source Address 2-9Last Status Change 2-6LateEvents 2-10Limits Table 3-8Local SNMP Configuration View 5-15Logical Interface Icons 2-12Logical Module 2-4Logical Module Representation 2-4

MManufacterer 2-8Mau Table 7-10

1

MIMNumber 2-6Type 2-6

ModuleConfiguration 2-6Notes 2-6Performance 2-6

Module Description 2-6Module Performance View 2-7Module Type 2-6Module/Port Number 2-8MSH-MIB Application Configuration

View 7-10Multi-Attribute Line Graph 2-7, 2-10, 2-16Multi-Attribute Line Graph Buttons 2-11, 2-

16

NNetwork Address 2-8Network Information 2-19Network Information Panel Label 2-15Notice i

OOperation Status 2-14Operational Status 2-6, 2-9, 2-14

PPacket Size 2-15, 3-5Performance View Label/Logical Gauge 2-16Physical Address 2-15Poll Application Configuration View 5-20Port

Admin State 2-7, 2-11, 2-15, 2-16, 2-18, 2-22

Configuration 2-8Notes 2-8Performance 2-8

Port Capacity 2-6Port Configuration View 2-8

QQueue Length 2-15

Index2

RReadable Frames 2-11Readable Octets 2-11Reconfigure 3-4Related Reading xiiiRestricted Rights Notice iiRouter Redundancy 3-3Runts 2-10

SSecurity View 5-9Selected Attribute 2-20Serial Number 2-8Service Table 3-9ShortEvents 2-10SNMP Repeater Performance View 7-2Source Address Changes 2-9Sys UpTime 2-8System Loader Configuration View 5-20

TTables

Admin Status 3-4Description 3-4Index 3-4Last Change 3-4Operation Status 3-4Physical Address 3-4Queue Length 3-4Type 3-4

TCP/IP Based Networks xiiiTrademarks i

VVeryLongEvents 2-10Virus Disclaimer i

3Com FMS/FMSII/10BTi/MSH HubsManagement Module Guide

Documents

3Com FMS/FMSII/10BTi/MSH Hubs Management Module Guideehealth-spectrum.ca.com/support/secure/products/Spectrum_Doc/pdf... · 3Com FMS/FMSII/10BTi/MSH Hubs ii Management Module Guide