Specifications

9032277-04 Software Superseded by CS3/MMS3
5-77
Patches Issued Since the CS2/MMS2 Release
to:
TR_Mon_Util=((MonBitsUsedPerSecs*100)/TR_Mon_Ring_Speed)
b. WatchBitprsec - which calculates the load for Token Ring. The
formula was changed from:
MonBitsUsedPerSec=TR_Mon_Bytes_Per_Second*8
to:
MonBitsUsedPerSec=INTEGER((COUNTER_DELTA
(mp_mlayStsOctest)*8 + COUNTER_DELTA
(mp_mlayStsPkts)*8*21)/COUNTER_DELTA(TIME))
** NOTE: A factor of "21" was used to account for framing bytes vs.
17. This conforms with the original formula for 8 this watch and also
to other TR watches which calculate the same thing (i.e.
CtTokenRingApp's Watch formula "TR_SW_Load").
--
The problem was a customer had several 2E42_27RDC's with
firmware revisions 4.08.09, 5.00.06 and 5.01.03. All had the same
issue with bringing up their DevTop views. When drilling into the
DevTop view an error window was displayed with "The Device has
NOT been CONFIGURED" message. Essentially, there was no
support in SPECTRUM for the 2E42_27RDC model type.
The resolution was to add support for the 2E42_27RDC model type.
--
The problem was that ATM Discovery was crashing when performed
on the Windows_NT platform. A trace was made available through Dr.
Watson.
The resolution was to correct the function that was identified as
causing the crash.
--
Three problems were resolved. The first problem was ATM Discovery
was setting up proper associations, but they were not getting reflected
in the SpectroGRAPH views.