3.1.2 Matrix Server SLES9 Release Notes

PolyServe Matrix Server Release Notes 17

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.

10828 Configuring unicast via mxconfig or the Management Console

does not work

The configuration option to change the “Matrix Administrative

Traffic Protocol” does not work. Matrix Server uses multicast

mode when it starts up and will automatically fail over to using

unicast messages if multicast failures are detected.

If necessary, you can manually configure Matrix Server to use

unicast when the product is started. To do this, you will need to

edit the /etc/opt/polyserve/mxinit.conf file and then restart Matrix

Server on each server.

Defect

Description