Specifications

Problems Resolved in CS3
CS3 Software Characteristics Software Release Notice for 5.0rev1
3-6 CS3 and MMS3
The resolution was to change the MAPAPI object, CsPackedVib, so
that pipes would not be lost in the above scenario.
13. The problem was that duplicate events were being created when a
primary and secondary SpectroSERVER were using the same
Archive Manager. The secondary server was configured with the
secondary_polling flag set to TRUE so that the secondary server
was ready when the switchover to the secondary server occurred.
The result was that both the primary and secondary servers
generated Contact Lost events when a device went down.
The resolution was to change the code so that the secondary server
will drop all events once they have been used to trigger inference
handlers and generate alarms. A flag ("drop_secondary_events",
default=TRUE) was added that allows administrators to override the
aforementioned functionality. The flag may be defined in the .vnmrc
file, but by default, the .vnmrc file will not contain the flag.
14. The problem was that MALT was not acknowledging "Existing
Connections" even though the connected device was modeled in
the database and was physically connected to another device in
the database.
The resolution was to change the MALT code so that the "Existing
Connections" box would be acknowledged when a device is modeled in
the database and physically connected to another device in the
database.
15. The problem was that the Enterprise Alarm Manager was not
launching for a user who did not have permissions to do a "Find"
on the VNM model (i.e., a Read-Only user).
The resolution was to allow the Enterprise Alarm Manager to be
launched for a Read-Only user without having to change the
community string of the user model.