3Com LinkBuilder FMS TR Agent Version 3.05 Release Notes

Modified: 12/17/96

Table of contents

1. Download warning

2. Feature and known issue list
2.1 New Products Supported
2.2 Adapter Lockout menu in telnet / console
2.3 Trap Based Alarms & Local Alarm Log
2.4 RMON Table Entries
2.5 RMON SR Tables
2.6 BOOTP over SR Bridges
2. 7 IP and Netware table headings removed from
RMON Agent (3C510502)
2.8 Simplified IP config & routing tables
2.9 IPX SAP Number

3. Download instructions

Appendix
Trap Table

**README.305***Warning below before downloading to agent module *****

3Com LinkBuilder FMS TR Agent Version 3.05 Release Notes
Products Covered:

FMS TR RMON Agent 3C510502 FMSTR305.SLX
FMS TR Advanced RMON Agent 3C510505 FMSTR305.XMT

***********************WARNING******************************
Standard IP communications in Source Routed (SR) environments.
When IP communications are used between the Agent and Management
station this feature is required to allow the agent to add a RIF
(Routing Information Field) to frames addressed to the management
station. The RIF is required when a Source Route bridge must be
traversed to establish communication from Agent to Manager.
WARNING:- In installations with SR bridges between the Agent
and Manger, the download of this agent image MUST be performed
from the same ring as the agent. NOTE: This is true even if
the agent has FMSTR304.XMT or FMSTR304.SLX code or
FMSTR302.XMT and FMSTR302.SLX released code. Use 'Vital Statistics'
(see below) to find the ROM version using telnet or a console
connection. In order to support standard IP transport in SR environment
both agents must be at the versions listed below:-

Adv. RMON Agent 3C510505: version 1.2 or later

RMON Agent 3C510502: version 1.2 or later

Any TFTP client can be used to download the agent code (use
BINARY mode, extend TIMEOUT to 200 seconds (to allow time boot
from EPROM and erase current agent Flash image.

N.B. SR/IP functionality is provided by agent code V3.02, 3.04 and 3.05. The prom code,
however, prior to 1.2 DOES NOT support SR/IP. Please remember that the PROM code is
ONLY used in a download at all other times 'Flash' is used.
************************************************************

The following outlines bug fixes and feature additions included
in this release of Agent code.

NEW FEATURES / CHANGES

2.1. New Product Support

This version of the code now provides support for the following devices:-

3C510511B Superstack II Hub TR 24 port
3C510510B Superstack II Hub TR 12 port

As well as existing Linkbuilder FMS TR (12 port) 3C510500, Linkbuilder FMS TR (24 port) 3C510502 and the LB FMS TR 12 3C510510and FMS TR 24 3C510511.

Any number of 3C510500, 3C510501, 3C510510, 3C510511, 3C510510B and 3C510511B can be stacked together. All RMON (3C510502) and Advanced RMON (3C510505) agents are able to manage all te above Hubs PROVIDED V3.05 is loaded on the agent.

2.2. Adapter Lockout (Ring Security) menu in telnet / console

Each FMS TR agent can provide MAC based security, this has been configurable from Transcend for some time. The additional menu choices in this version allow the user to;
a) Enable Adapter Lockout - only 'known' addresses are permitted access to ring
b) Disable Adapter Lockout - allow any address access to ring & learn 'new' addresses (default)
c) Clear known adapter address table - usefull when moving agent from ring to ring*

* address table cannot be cleared if Adapter Lockout is enabled

Adapter Lockout by default is in learn mode where all addresses are stored in NVRAM on the agent (i.e. an agent reset or download does not clear the known (allowed) list). When the user enables Adapter Lockout, all known addresses can insert / deinsert at will, any unkown address will be detected and removed. The removal relies on the 'Remove Ring Station' MAC frame which forces the specified adapter to deinsert. An alarm will be generated and sent to network management and /or logged locally. This removal does not isolate the hub port, thus a known station could use that port, also if the station is connected to a non-3Com hub it is still removed because the removal method is to force the adapter to close, not to isolate a port.

2.3. Trap based alarms

Most alarms logged using the current version of the TR Manager within Transcend are derived using polling. We have added functionality to enable it to forward a trap to any known SNMP manager when events are detected by the agent (i.e. lobe inserts, hub changes, auto-beacon removal etc). The events are split into 7 categories, each can be set to

i. Trap - Send SNMP trap to known managers
ii. Log - Log event locally (see below)
iii. Trap & Log - Both of the above
iv. none - no action

In this way some events will be reported to the managers, some logged locally and others ignored. This allows network administrators to tune the agent reporting to meet their desired needs

The new menu for configuration of traps can be found under item 13 Trap/Log configuration from the main menu. When log is selected the most recent 30 events in each category are saved. To view the event log select 6. Device Managment, 3. Display Event Log

Supported trap types

3COM TRAP PDU format

PDU Type: This is a Trap PDU.
enterprise: Identifies the network management device that generated the trap based on the value of its sysObjectID (260.1.x for our agent).
agent_addr: IP of device generating trap.
generic-trap: Type 6 for enterprise specific.
specific-trap: *See below.
time-stamp: Based on time agent last booted up to time trap was generated.
variable-bindings: *The text of the trap message, also shown below in Appdenix.

2.4. RMON Table entries

The FMS TR range has fully supported all 10 groups of RMON for Token Ring, however location of some of the entries (MIB Items) and our method for creating table entries was not fully compliant with the RMON standard. This meant that a customer using Transcend could access all the RMON information, however when accessing the FMS TR agent from other SNMP RMON browsers problems occurred. (i.e. Axon / LAN sentry could not access RMON information from an FMS TR)

This update will rectify the above problems and allow Transcend and any other RMON station to access the FMS TR Agents.

2.5. RMON SR tables

The FMS TR now fully supports and lists the Rmon Source Route (SR) tables.

2.6. Bootp over SR Bridges

The FMS TR now fully supports Bootp over SR bridges.

2.7. IP and Netware table headings

In the RMON agent (3C510502), from the main menu, 6, Device Management Menu then 2, Display active port mappings. We have removed the Netware and IP headings. This is to avoid confusion as theis agent does not support this feature. Note, however, that mac address and location are still supported.

2.8. Simplified IP config / routing table

Some confusion has existed in previous versions of Agent code concerning the;
Source Route IP Address configuration option, this was previously included for a specific configuration that has never been used. Therefore this menu choice has been removed from the console / telnet menus.
To confirm, the IP Address Cong. is where the Agent IP address should be configured for both transparent and Source Routed Environments. (The agent will first attempt to forward a frame transparently and if unsuccessful it will send a Source Routed discovery frame.)

Software Loopback (127.0.0.1) entry in IP Routing Table. This software loopback is required by the agent, previously we displayed this in the IP Routing Table in telnet / console menus, this has been hidden to avoid confusion.
NOTE:- The Software Loopback address will be displayed when viewing the IP Routing Table from Transcend or other SNMP management stations.

2.9. IPX SAP number

The FMS TR now uses the 3Com default IPX SAP number of 07D3. This was previously 0000 and caused problems when trying to filter on SAP address.

DOWNLOAD INSTRUCTIONS

FMSTR35a.EXE (for Advanced RMON Agents (3C510505)) expands to:-
FMSTR305.XMT
agent.rev
readme.305
readme.304
readme.302.

FMSTR35r.EXE (for RMON Agents (3C510502)) expands to:-
FMSTR305.SLX
agent.rev
readme.305
readme.304
readme.302

Copy these files to the directory that Transcend is installed in.
Default directories are:

For OS/2 \TRLBV3.0 or \TRLBV301

For Unix \usr\3Com\startek\agtsup

The agent.rev file is required to control agent downloads and
to determine the 'Current Version' of agent code.

FMSTR305.XMT Adv. RMON Agent 3C510505
FMSTR305.SLX RMON agent 3C510502

3.A. Using Transcend for UNIX(See Note #1 below)

3.A.1. Copy FMSTR*.* and AGENT.REV to the following directory;
<path>/3Com/startek/agtsup
where <path> is the directory that Transcend is installed to
(default is /usr)

3.A.2. Start Transcend and open a 'Network View' select Download Agents
from the configuration menu, download one agent initially to check
functionality, then update all outstanding agents.

3.B. Using Transcend for OS/2

3.B.1. Install the appropriate diskette into the disk drive of the PC
running the Transcend application.

3.B.2. From the Transcend LinkBuilder TR Manager main title bar, select
Actions
Agent Support

3.B.3. Select the appropriate drive designation (a:\ or b:\)and then
"click" the LOAD FROM DISK button. (Progress of the file copy can
be monitored within the Agent Support window.)

3.B.4. When the DISK LOAD COMPLETE! message is displayed in the status
field, select the CHECK & UPGRADE AGENTS button. (Progress of the
agent check and upgrade can be monitored within the Agent Support
window).

3.B.5. When the UPGRADE COMPLETE message is displayed in the status field, insure the upgrade was successful by highlighting the agent icon, clicking the right mouse button and then select settings and download.
current rev: FMSTR305
should be displayed.

Note #1: if your network configuration includes SourceRoute bridges
between the Agent and the Transcend Management station, do not
download from Transcend. In this case the download must be performed
from the ring to which the agent is attached.

Appendix

*Provided here is a list of the categories of specific traps (1 through 7) available

Note: Text within "< >" correspond to data specific to each trap.
Tables contain all possible conditions for appropriate trap.

A.1. Lobe events

Lobe <port #> on <device id> DeInserted
Lobe <port #> on <device id> Inserted
Lobe <port #> on <device id> ISOLATED by Manager
Lobe <port #> on <device id> ENABLED by Manager
Router Port Deinserted on <device id>
Router Port Inserted on <device id>
Router Port ISOLATED on <device id>
Router Port ENABLED on <device id>
Agent MAC on plug-in Deinserted from <device id>
Agent MAC on plug-in Inserted into <device id>
Agent MAC on plug-in to <device id> ISOLATED
Agent MAC on plug-in to <device id> ENABLED

A.2. Main Ring Events

RO ENABLED on <device id> by Manager
RO ISOLATED on <device id> by Manager
RI ENABLED on <device id> by Manager
RI ISOLATED on <device id> by Manager
RO Fault Tolerance ENABLED on <device id>
RO Fault Tolerance DISABLED on <device id>
RI Fault Tolerance DISABLED on <device id>
Cascade UP Deinserted on <device id>
Cascade UP Inserted on <device id>
Cascade UP ENABLED on <device id>
Cascade UP ISOLATED on <device id>
Cascade DOWN Deinserted on <device id>
Cascade DOWN Inserted on <device id>
Cascade DOWN ENABLED on <device id>
Cascade DOWN ISOLATED on <device id>
RO DeInserted on <device id>
RO Inserted on <device id>
RI DeInserted on <device id>
RI Inserted on <device id>

A.3. Auto Isolate Hard Error Events

Lobe <port #> on <device id> AUTO-ISOLATED : Cause <See table#1 listed below>
Lobe <port #> on <device id> Re-Enabled
RO Re-Enabled on <device id>
RO AUTO-ISOLATED on <device id>
RI Re-Enabled on <device id>
RI AUTO-ISOLATED on <device id>
Cascade UP RE-ENABLED on <device id>
Cascade UP AUTO-ISOLATED on <device id>
Cascade DOWN RE-ENABLED on <device id>
Cascade DOWN AUTO-ISOLATED on <device id>
Router Port AUTO-ISOLATED on <device id>: Cause <See table#1 listed below>
Router Port RE-ENABLED on <device id>
Agent MAC on plug-in to <device id> AUTO-ISOLATED
Agent MAC on plug-in to <device id> RE-ENABLED
Error Recovery ended on <device id>
Error Recovery began on <device id>
Error Recovery process restarted <device id>
Error Recovery process halted on <device id>

A.4. Hub Configuration Events

Data Rate set to 4 MBPS on <device id>
Data Rate set to 16 MBPS on <device id>
Automatic Recovery Disabled on <device id>
Automatic Recovery Enabled on <device id>
Port Lock Set to Automatic on <device id>
Port Lock Out Set to Manual on <device id>
Agent Parse Ctrl changed from <See table#4 listed below> to <See table#4 listed below>
New <number of ports>-port SuperStack Device Detected : <device id>
Communication FAILURE to SuperStack Device <device id>
Communication Restored to SuperStack Device <device id>
RPS removed from powering <device id>
RPS detected powering <device id>
RPS status Fault on <device id>
RPS status Normal on <device id>
RIRO plug-in DISABLED in <device id>
RIRO plug-in ENABLED in <device id>
Agent card removed from <device id>
<See table#2 listed below > Agent card plugged into <device id> : Status <See table#3 listed below>
RIRO card removed from <device id>
<See table#5 listed below> RIRO card plugged into <device id>
<See table#2 listed below> Agent Card plugged into <device id> DISABLED : Status <See table#3 listed below>
RO on RIRO plug-in configured to support FIBER on <device id>
RO on RIRO plug-in configured to support COPPER on <device id>
RI on RIRO plug-in configured to support FIBER on <device id>
RI on RIRO plug-in configured to support COPPER on <device id>
Agent Roved into <device id>
Agent Roved out of <device id>
Status Change of Agent Card plugged into <device id> : <See table#3 listed below>
Over Temperature detected <device id>
Temperature returned to Normal on <device id>

A.5. Hard Error Events

Ring entered BEACONING state
Ring exited BEACONING state

A.6. Soft Error Events

Not supported in this release

A.7. MAC Address Change Events

MAC Address <Device MAC Address> mapped to device <device id>
IP Address <Device IP Address> mapped to MAC Address <Device MAC Address>
Netware Name <NetWare ID> mapped to MAC Address <Device MAC Address>

Tables

Table 1: 1 - Unknown
2 - None
3 - Phantom Error
4 - No Carrier
5 - Bad Data Rate

Table 2:
1 - RMON
2 - Advanced RMON
3 - Unknown

Table 3:
1 - Unknown
2 - Normal
3 - Disabled
4 - Test
5 - Downloading
6 - Fault
7 - NO Agent

Table 4:
1 - Unknown
2 - Parse IPX
3 - Parse Protocols
4 - Parse LLC
5 - Parse None

Table 5: 1 - Fiber
2 - Copper
3 - Dual Media
4 - No RIRO

© 3Com Corporation