Specifications

Management Module Anomalies
Management Module SRN 6.0 Rev 0 Page 28
Problem 4: If you try to use the Find view to find the Fore_SONET_App by
Model type, the lower portion of the Device view is blank or shows incorrect
information.
Solution: Do not use the Find view for this purpose; use the conventional
methods of accessing the Device view.
Problem 5: Attempts to model a ForeSwitch as a GenSNMPDev show the
model type as a ForeSystems Workstation, eventually changing to a
ForeSys RT router model type. After navigating into the Device Topology or
the Application views, ForeUserApp icons appear within the views.
Solution: This is a firmware problem
Problem 6: For the ForeRunner, the ATM_Network Model appears in the
Link Information view as a port model instead of as a network model. The
model correctly appears as a network model in the Topology view.
Solution: This problem will be fixed in a future release.
Problem 7: Modeling a ForeRunner with LANE services, followed by
modeling a client within a LANE network and attempting to use ATMDisc
results in the client not connecting to the ATM network or to the
ForeRunner management module.
Solution: This problem will be fixed in a future release.
Problem 8: A yellow alarm occurs if multiple ForeWorkstations are
modeled in SPECTRUM. The alarms only appear on ForeWorkstation
models using an older (previous) version of the Fore adaptor card.
Solution: Install FORE’s ATM adapter card software, the
Solaris_5.0.0.5_28757.tar version or later.