Specifications

Patches Issued After the CS1/MMS1 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-28 CS3 and MMS3
scheduled intervals. You have to reset the Background Discovery in
order for it to start running again. This has been resolved by changing
Background Discovery to only reset every time the SpectroSERVER is
shut down.
Customer states that, under 4.0Rev3, although the SNMP get packet
that was issued on behalf of an active GIB view did exceed the max
length that his agent was capable of handling, the DCM did
successfully process all of the data:
1. Through an arbitration type process the DCM removed attributes
that were roughly equal to 25% of the total packet size during each
iteration, until it finally sent a packet that was small enough to be
processed by the Liebert Agent.
2. The remaining attributes were then packed into subsequent
packets and sent to the agent for processing.
3. The successful packets were reused by the DCM, rather than
having to repeat the arbitration process for each refresh cycle of
the GIB.
When moving to 5.0 the customer has reported that the way in which
the DCM processes packets which are too large for the agent has
changed markedly:
1. The arbitration process uses a ~10% reduction factor in each
iteration.
2. The remaining attributes are dropped and not resent.
This has been resolved by restoring the old behavior.
Support has been added for the Catalyst wsx5030 board.
A memory leak occurs on every poll of a port's Internal_Link_Status
when LivePipes is turned on. The default polling interval is 1 minute
for each port in the database with Live Pipes enabled, which can
become a severe memory issue for customers who use LivePipes.
Bringing up the I/O Statistics View from the VNM Performance View
causes the following errors to appear in the VNM.OUT:
Cs_get_diskio: kstat_read: No such device or address
Cs_get_diskio: kstat_read: No such device or address