Digital Equipment ChannelWorks, Руководство по установке сети

Страница: 19 / 90

xix
Known Problems
The following items are under investigation:
1. The ChannelWorks Bridge operation has been verified at frequencies correspond-
ing to standard NCTA channel assignments. For optimal receiver operation avoid
using the following forward (RX) frequencies:
• 79.000 MHz
• 85.000
• 93.000
• 105.000
• 141.000
• 429.000
• 465.000 MHz
2. The LANcity Management Utility (LCM) prevents the user from entering illegal
and non-optimized Max Round Trip Delay values. However, the ChannelWorks
Bridge software does not prevent the user from entering less than optimal Max
Round Trip Delay value when performing SNMP “sets” on the enterprise specific
MIB variable lcmaxrndtripdel in the ASIC Parameters group.
3. The Support History Log does not consider an error code at two different error lev-
els as unique, which could be misleading as in the following example:
If error 0x35 is logged as a level 2 and at a later time error id 0x35 is logged at a
level 4, when displaying the Support History Log the second error as shows as a
level 2 crash.
4. The LANcity Subscriber Utility (LCS) and the LCM do not operate properly on a
66 MHz PC.
5. The PROM Monitor’s printcfg command displays an incorrect software version
value under the “Vers” heading. The “Description” heading displays the correct
software version. You can also use the SNMP enterprise specific MIB variable
lcsoftware in the Revision Levels group to view the correct software version.
6. Counters from the interface group of the MIB-II are not implemented correctly for
the serial port.
7. The IPNetToMediaTable and the atTable of MIB-II cannot be modified via SNMP.
The enterprise specific MIB variables lcmcastrx and lcbcastrx from the Sonic Stats
group are not implemented.