Specifications

9032277-04 Software Superseded by CS3/MMS3
5-95
Patches Issued Since the CS2/MMS2 Release
intel will set the AlarmOnLinkDown attribute to "Never" to suppress
the critical alarms which are otherwise asserted.
b. New NPC scenarios involve a variable, router and router port on
the host side of the connection, the answering side. The current
modeling only works with the specification of a specific single port.
With the exception of accurate fault isolation, the entire Dial Backup
management can be obtained by monitoring the remote router. This
leads to the solution of simply modeling the remote side of the
dialback in those cases where the host port/router is unspecified.
To recover the fault isolation accuracy, non-resolved connections
between the dialup_Link model and each potential host router will be
monitored. If the remote router is unreachable, and any one of the
potential host routers is reachable, then a dialup_link alarm will be
asserted. If no potential host router is reachable, then it is assumed
that the dialup_link model is downstream of the point of failure.
c. New scenarios involve the backup of a group of ports on a router by
a single dial backup port on the same router. That is, only when all
interfaces in the backed up group are down will the backup be used.
The Primary IFConfig will be updated.
--
The problem is Fault Isolation is not working properly. In a FDDI
ring, devices connected to Unmanaged DAS models turn grey upon
loss of contact. Also, SmartSwitch routers connected to a DAC device
modeled as a non-manageable FDDI model will turn grey upon loss of
contact. A user will never be notified with an alarm that the device
has gone down. The DAS and DAC models remain blue because they
are not managed (i.e. usually belonging to an ISP). The explanation to
this problem is - When a device is connected to a DAS model and the
device shows loss of contact (the DAS model is it's only neighbor), the
fault cannot be isolated since the DAS model cannot be contacted via
SNMP. Therefore, the model goes grey and not red. Even though the
DAS model is "UP" and can be pinged, it is not "SNMP UP".
The resolution is SPECTRUM Fault Isolation will cause a device to
completely ignore GenFDDIMac_NM and GenTRStn_NM models as
it's neighbors. It will be as if they aren't even connected. This solution
is exclusive to SPECTRUM 5.0rev1.
--