- Introduction
- Hardware Revision Support
- Network Management Platform Support
- Firmware Changes and Enhancements
- Supported Features
- Installation and Configuration
- Known Restrictions and Limitations
- IETF Standards and Support
- Cabletron Private Enterprise MIB Support
This document provides specific information for version 01.07.06 of firmware for the 9F426-03. It is recommended that one thoroughly review these notes prior to the installation or upgrade of this product.
Firmware Specifications:
-
Supported Hardware Revisions: All
Boot PROM Support
-
Supported Boot PROM: 01.00.06 and above
Versions other than those indicated above are not supported by this release of firmware. Please contact Cabletron Technical Support for upgrade assistance if necessary.
Network Management Platform Support
Network Management Software support for the 9F426-03:
Spectrum version 4.0Rev1
SPMA (Spectrum Portable Management
Application) version 3.0Rev0
SPEL (Spectrum Element Manager)
version 2.0Rev0
Environmental Module Firmware Support:
-
Firmware support: All
Firmware Changes and Enhancements
- CtfddiStats are now working correctly. In a previous versions of firmware the statistics were not working correctly.
- SmartTrunking is supported with this release.
-
The 9F426-03 features Local Management via the MMAC-Plus Environmental
Module (EM). The Local Management application allows the user
to monitor and control the module's IP address, subnet mask and
default gateway configuration. The default community name/console
password is public or <return>. Local Management can also
be accessed by initiating a telnet to the 9F426-03's IP address.
- The
9F426-03 allows the user to connect the three front panel connected
FDDI networks to the INB (Internal Network Bus) of the MMAC-Plus
chassis.
- The INB2 is a high speed backplane that provides a potential for 2.5 Gbps of bandwidth. The INB2 bus uses a modified TDM design to provide the maximum bandwidth available on the bus to each module. The TDM for the bus is controlled by one of the modules. The function is called the monarch. The module that will become the monarch is selected automatically with no user intervention and it is transparent to the user. However if the module that is the Monarch is removed or any other module on INB2 is removed or reset for any reason, a monarch reset will take place. The process takes approximately 1.5 seconds. During this time no traffic will traverse the INB. When a new Monarch is selected all INB receive LEDs will be solid green and then begin to blink yellow with the rate of data traversing the INB. The following table is for the operation of the INB LED's during monarch selection:
| Operation | INB Receive LED Sequence (After CPU LED is green) | INB Transmit LED Sequence (After CPU LED is green) |
| Module insertion Monarch or non-Monarch:
1.5 second LED sequence (approx.) | off
red off off green green (module operational | red
red off red red yellow blinking or off |
| Non monarch module removal: | No Change | No Change |
| Monarch removal:
1 second (approx.) | off
red
green
| red
red red yellow blinking or off |
- The default gateway
interface found in local management is user selected for the following
interface numbers:
1 -- SMB-1 This interface does
not work for the default gateway.
2 - SMB-10 This interface is connected via the EPIM port of the Environmental Module (EM).
3 - Host The host port will direct the packets to the correct interface for the default gateway address via the look up tables.Configuration of the default interface will provide the path the packet shall use to get to the default gateway address. If the default gateway is off the EM then select interface 2, otherwise select interface 3 and allow the host to find the default gateway.
Installation and Configuration
- The 9F426-03 supports software
image downloads to Flash EEPROM's for software upgrades thereby
eliminating the need to physically access the module. The download
may be done in-band, through the network, allowing remote upgrades
from a central location. There is a 3 1/2 inch diskette included
with the packaging of the 9F426-03. The disk is formatted in DOS.
This diskette has the current Flash Image for the 9F426-03 stored
on it. This is used as a back-up image for the 9F426-03 or it
may be the current image that should be downloaded into the Flash
EEPROM's of the 9F426-03. Please take time to verify the version
on the diskette matches the current version installed on the 9F426-03.
- The 9F426-03 support the following
FPIMs that must be installed prior to installing the module into
the chassis:
FPIM-00 -- Multimode Fiber, MIC connector
FPIM-01 -- Multimode Fiber, SC connector
FPIM-02 -- Unshielded Twisted Pair, RJ-45
FPIM-04 -- Shielded Twisted Pair, RJ-45
FPIM-05 -- Single Mode fiber, MIC connector
FPIM-07 -- Single Mode fiber, SC connector - The following instructions are
for configuring full duplex via SNMP:
To configure full duplex on an interface:
OID Name: ctIfDuplex
OID String: 1.3.6.1.4.1.52.4.3.3.2.1.1.5.interface #
Description: Defines the duplex mode that the interface is set to operate in. For devices that do not support this capability a read will return standard (2) and a write attempt will return "BADVALUE".-
Integer
other (1)
standard (2)
full (3)
Known Restrictions and Limitations
- Saving the IP Address in local
management will cause the Module to perform a "soft"
reset.
- In local management the frames
filtered counter will always display zero. This will be addressed
in the future.
- The INB hardware does not provide
the full complement of statistics that are available on the other
interfaces. Specifically, the only MIB-II Interface statistics
supported by the INB interface are InOctets, InDiscards, and OutOctets;
all other values are forced to zero (0). Consequently, the values
for port 1 (INB) on the "Bridge Statistics" LM screen
will always be displayed as zero (0).
- The dot1dStatic Group from the
IETF Bridge MIB is supported, however, when creating and entry
for the dot1dStaticReceivePort the only value that is allowed
is the value "0" (zero).
- The ring map could display incorrect
upstream neighbor information on rings that tend to be bouncy.
Occasionally several stations indicate that they have the same
upstream neighbor. This will be fixed in a future release.
- The following objects in the
contType group of the Container MIB are not properly initialized:
contTypeDevice
contTypeSerialNumber
contTypeContainingDevice
contTypeContainingSerialNumber - The use of a period in the password
field is prohibited. The period symbol is reserved as a special
character for Cabletron SmartSwitch products. If a period is
being used in the password currently, change it to another character
before downloading image version 1.04.11 or above.
- "Port Mirroring" is
not supported on this module even though there is a screen in
local management for this feature.
Trap Support:
-
IETF SNMP (RFC 1157)
| coldStart | generic 0 * |
| warmStart | 1 |
| linkDown | 2 |
| linkUp | 3 |
| authenticationFailure | 4 |
| enterpriseSpecific | 6 |
IETF Bridge (RFC 1493)
| newRoot | specific 1 |
| topologyChange | 2 |
IETF RMON (RFC 1757)
| risingAlarm | 1 |
| fallingAlarm | 2 |
CTRON-BDG-MIB
| bridgeStatusChanged | 769 -- 0x0301 |
CT-CONTAINER-MIB
| contLogicalChangesTrap | 1200 |
| contPhysicalChangesTrap | 1201 |
FDDI-SMT73-MIB (REF RFC 1512)
| fddiPortConnectStateChange | 1024 -- 0x400 |
| fddiMACRMTState | 1032 -- 0x408 |
| fddiMACFrameErrorRatio | 1036 -- 0x40C |
| fddiMACDuplicateMACAddress | 1037 -- 0x40D |
* Cold start traps will never
be generated because components of this product are always available
and can not be removed.
-
The following Internet Engineering
Task Force MIBs are implemented in this release:
| MIB II | RFC 1213 (System, Interfaces,
IP, ICMP, UDP, and SNMP) |
| Bridge MIB | RFC 1493 (dot1dBase,
dot1dStp, dot1dTp, and dot1dStatic) |
| FDDI | RFC 1512 |
| FIB | RFC 1354 |
| RMON | RFC 1271 (Alarms and Events) |
The firmware features implemented
in this release are compliant with the following:
SMT 7.3
Cabletron Private Enterprise MIB Support
The following Cabletron MIBs are implemented in this release:
| ct Container
Rev. 1.00.00 contType contLogical contPhysical contCommStr | ct MIB-II Extensions
Rev. 1.02.02 commonDev ctIf ctIfPort | ctron-oids-mib |
| ct Bridge
Rev. 1.04.00 ctBridgeStp | ct Download
Rev. 1.05.00 Full | ct SMT
Rev. 1.03.00 Full |
| ct Router
Rev. 1.00.01 partial nwRtrMibs nwRtrHighLevelView: nwRtrApplicationView nwRtrComponentView | ct FDDI FNB
Rev. 1.00.00 Full | ct IP Routing Services
Rev. 1.01.00 supported IP Router Component Groups: nwIpSystem nwIpForwarding nwIpEvent |
| ct FDDI Stats
Rev. 0.00.04 Full | ct Power
Rev. 1.00.00 chPower boardPower psPower termPower | ct PIC
Rev. 1.00.01 ctPicNumberEntries ctPicTable ctPicECOTable ctPicDiagTable |
| ct Environmental
Rev. 1.00.00 chEnv boardEnv psEnv | ct DLM
Rev. 1.02.01 Full |
ctActions
Rev. 1.00.00 Full |
Cabletron Private Enterprise MIBs
are available in ASN.1 format on the Internet. Indexed MIB documentation
is also available. Please contact Cabletron Technical Support
for further information.
Notice:
-
Runtime (On-line TFTP) Download
Instructions
There are two different methods
of performing a runtime (On-line TFTP) download. The first method
results in the module rebooting directly after the download has
been performed so that the new image will immediately begin running.
The second method will result in the new image being downloaded
to FLASH and not used by the module until the module is rebooted
at a later time.
At present, on-line downloads must
be performed using an SNMP MIB access tool and the following OID's
must be set:
To Perform a Runtime (On-line
TFTP) Download
OID Name: ctDLNetAddress
OID String: 1.3.6.1.4.1.52.4.1.5.8.1.18.0
Description: The IP Address of
the TFTP server to be used when an image is to be downloaded across
the network.
OID Name: ctDLFileName
OID String: 1.3.6.1.4.1.52.4.1.5.8.1.19.0
Description: The file name requested
of the server when an image is to be downloaded across the network.
OID Name: ctDLOnLineDownload
OID String: 1.3.6.1.4.1.52.4.1.5.8.1.16.0
Description: During normal operation,
this object has a value of (1). By setting this object to a value
of forceDownLoad (2), an On-line downloads will be performed.
The new image will begin operating upon the next reset of the
module. By setting this object to a value of forceDownLoadReset
(3), an On-line downloads will be performed and the board
will automatically reset upon successful completion of the download
and begin using the new image.
In any case, please monitor the
progress of the runtime download by checking the status of the
following OID:
OID Name: ctDLOperStatus
OID String: 1.3.6.1.4.1.52.4.1.5.8.1.17.0
Description: A value of (2) indicates
that a TFTP downloads request has been received but has not yet
been activated. A value of (3) indicates normal operation. A
downloads was started and has finished normally and no reset was
specified or a downloads has not been started. A value of (4)
indicates that a downloads is in progress. A value of (5) indicates
that a downloads was started but has terminated due to an error.
If you chose a forceDownLoadReset
(3) then please monitor the ctDLOperStatus OID, defined
above, until a value of (3) is observed. No other settings are
necessary! The runtime downloads should execute and complete correctly.
If you chose to perform a forceDownLoad
(2) then the board can be reset from your MIB access tool
using the following OID. The ctDLOperStatus (OID String:
1.3.6.1.4.1.52.4.1.5.8.1.17) must have a status of (3) before
resetting the module. Of course, resetting the module may be done
either manually (power cycling or reset button) or remotely through
the following OID:
OID Name: ctDLInitiateColdBoot
OID String: 1.3.6.1.4.1.52.4.1.5.8.1.3.0
Description: When written with
a (1), the boot software initiates a system reboot.
In the event that a runtime downloads is interrupted, the firmware image in flash memory will be erased. The module will continue to operate until it is either reset or powered off and then powered on-line. After either of these events, the module can only download a firmware image from a bootp/TFTP server located on the EPIM port of the EM. Although runtime downloads is a powerful network operations & firmware management feature, careful consideration should be given to both the timing (best when network usage is lowest) and network stability (when downloading over a WAN link) at the time of the planned downloads. Runtime download is supported in Cabletron's Network Management Software packages.
The purpose of switch six on the
9F426-03 dip switch bank is for forcing a flash download from
a bootp server. The first step in this process is to configure
the bootp server. Configurations of bootp servers can differ
from platform to platform and from one operating system to another.
Read the user's manual on bootp and TFTP serving for the correct
files to edit and the correct files to execute for the server.
After configuration of the bootp server the 9F426-03 can then
have the switch state changed on the dip switch bank to initiate
the bootp and TFTP requests.
WARNING: Never
adjust switch settings while the 9F426-03 has power applied to
it. Not only is this dangerous, but the change in position activates
the switch function and after you reinstall or power cycle the
9F426-03 it will initiate the request.
What happens if inadvertently
switch six is changed on the DIP SWITCH PACK?
If the state of switch 6 is changed
the 9F426-03 will begin requesting a bootp server in an attempt
to receive a flash image download. The 9F426-03s boot PROM will
initiate a bootp sequence. During this sequence the 9F426-03
requests an IP address and a filename from the bootp server.
The 9F426-03 then requests a TFTP of the file and excepts the
download of the image. The 9F426-03 will not function until the
flash image is downloaded from the bootp and TFTP server. In
the event that a bootp and TFTP were not intended at this time,
reset the 9F426-03. Resetting can be done by pushing the reset
button, power cycling the MMAC chassis, or removing the 9F426-03
from the chassis and plugging it back into the chassis. After
resetting, the 9F426-03 attempts to locate a bootp server, however,
the bootp request times out after about four minutes. After the
time out of the bootp service requests the 9F426-03 will boot
from flash memory. The 9F426-03 will take a total of about seven
minutes from the start of the reset to operation of the product.
If the 9F426-03 is power cycled again the 9F426-03 will boot
from flash memory without trying for the bootp server.
Note:
If you do not reset the 9F426-03 it will try to contact a bootp
server continuously until a bootp server is contacted and the
image is downloaded or the 9F426-03 is power cycled.
If you have any questions, call Cabletron Technical Phone Support at (603) 332-9400 or send us E-mail via the Internet. Our E-mail address is support@ctron.com.