3.5.1 Matrix Server Release Notes

PolyServe Release Notes 16

10191 Using hostnames in .matrixrc file can cause connection delays

When servers are specified by hostname in the .matrixrc file,

long connection delays (possibly minutes per hostname entry)

can occur if there is a slow or unresponsive DNS server on the

network. During this time, the Management Console and mx

commands might be unresponsive.

10762 Simultaneous 16-node SNMP transactions to Brocade switches

can fail

Problems have been seen when a large number of servers (16)

simultaneously attempt to use SNMP to communicate with

Brocade switches. When this happens, the switch does not

respond in a timely manner to the SNMP requests. This problem

is primarily seen when exporting a configuration to all 16 nodes

at once via mxconfig.

To work around this problem, export the configuration to

smaller groups of nodes. For example, the operation will

succeed if you export to just four nodes at a time.

Intermittent alerts reporting that the switches are not

responding may also appear when multiple servers are being

started simultaneously. This is a transitory condition and should

cease when all servers are started.

10902 Management Console does not show all quota information

When displaying quota information, the Management Console

will not show extremely large values in the “percent used”

column. To see these values, use the mx quota showuser

command. You can also increase the quota for the affected user

or group to reduce the “percent used” value.

12331 mxcheck fails without an error message

If the /tmp directory is full, the mxcheck utility will fail and

Matrix Server will not start. When this situation occurs,

mxcheck should display an error message explaining that there

is insufficient space in /tmp.

Defect

Description