3.4.0 Matrix Server Release Notes

PolyServe Matrix Server Release Notes 15

12050 Matrix may not start when fencing method is changed

If the fencing method is changed and all servers in the matrix

were not shut down cleanly, the matrix may not be able to start

successfully. To check for this condition and correct it if

necessary, first run the mpdump command with no options.

mpdump

Membership Partition Host Registry (Version 3):

Host ID: 10.10.180.5 fencestatus=0 fencetype=0

Fence ID:21:00:00:e0:8b:0c:12:1f::10.10.11.221 state=0

Host ID: 10.10.180.11 fencestatus=0 fencetype=0

Fence ID:21:00:00:e0:8b:05:c2:b1::10.10.11.221 state=0

Fence ID:21:01:00:e0:8b:25:c2:b1::10.10.11.221 state=0

Host ID: 10.10.180.6 fencestatus=0 fencetype=0

Fence ID:21:00:00:e0:8b:10:ee:88::10.10.11.221 state=0

If the output includes any “Host ID” entries, you will need to

clear the entries from the host registry as described below. If

there are no “Host ID” entries in the output, you do not need to

take any action.

To clear the host registry, complete these steps:

1. Save the existing membership partition data:

mpdump -F

2. Recreate the membership partitions. This command clears

the Matrix Server host registry and then recreates the

membership partitions using the data saved in step 1.

mpimport -M -F

12076 Modifications to san_snmp.cnf are not retained

When Matrix Server is upgraded from 2.7.2, any local

modifications to the san_snmp.cfg file are not moved to the new

version of the file, which has been named san_snmp.conf.

Workaround. Copy your changes from the old san_snmp.cfg file

to the new san_snmp.conf file.

Bug

Description