Updating the Assure MIMIX for AIX configuration on the secondary production server - assure_mimix - assure_mimix_for_aix

Updating the Assure MIMIX for AIX configuration on the secondary production server - assure_mimix - assure_mimix_for_aix - 6.0

Assure MIMIX for AIX Guide

Product type

Software

Portfolio

Integrate

Product family

Assure

Product

Assure MIMIX™ Software for AIX

Version

6.0

ft:locale

en-US

Product name

Assure MIMIX for AIX

ft:title

Assure MIMIX for AIX Guide

2025

First publish date

2003

ft:lastEdition

2025-10-08

ft:lastPublication

2025-10-08T06:18:25.453000

Changes that you make to an Assure MIMIX for AIX Configuration do not automatically propagate to the secondary PowerHA production server.

Perform the following steps to update the Assure MIMIX for AIX configuration on the secondary production server.

On the secondary production server, delete the Primary and Failover Context IDs for the replication group that was changed.

To delete the Primary Context ID execute:
```
/usr/scrt/bin/scsetup -XC1
/usr/scrt/bin/scsetup -RC1
/usr/scrt/bin/sccfgd_delcfg 1
```
Log file or path (/usr/scrt/archive/sccfgd_delcfg.1.add) does not exist0518-307 odmdelete: 296 objects deleted.0518-307 odmdelete: 1292 objects deleted.0518-307 odmdelete: 178 objects deleted.0513-083 Subsystem has been deleted.

To delete the Failover Context ID execute:
```
/usr/scrt/bin/scsetup -XC17
/usr/scrt/bin/scsetup -RC17
/usr/scrt/bin/sccfgd_delcfg 17
```
Log file or path (/usr/scrt/archive/sccfgd_delcfg.17.add) does not exist0518-307 odmdelete: 296 objects deleted.0518-307 odmdelete: 1292 objects deleted.0518-307 odmdelete: 178 objects deleted.0513-083 Subsystem has been deleted.
On the primary production server, create a file with the Primary Context ID configuration.
```
odmget -q ContextID=1 SCCuObj SCCuAttr SCCuRel >/tmp/C1.cfg
```
Copy this configuration file to /tmp on the secondary production server.
On the primary production server, create a file with the Failover Context ID configuration.
```
odmget -q ContextID=17 SCCuObj SCCuAttr SCCuRel >/tmp/C17.cfg
```
Copy this configuration file to /tmp on the secondary production server.
On the secondary production server use rthostid to obtain its HostId.
```
/usr/scrt/bin/rthostid
```
Sample output: 9C5FE66FB

On the secondary production server edit the production HostId stanza in the /tmp/C<Primary Context ID>.cfg file. Replace the contents of the ObjectAttributeValue field with the output from the rthostid command.

SCCuAttr:
ObjectName = "production"
ConfigObjectSerial = 15
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "9C5FE66FB"
ObjectAttributeType = "ulong"
SerialNumber = 15006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 1

On the secondary production server edit the backup HostId stanza in the /tmp/C<Failover Context ID>.cfg file replacing the content of the ObjectAttributeValue field with the output from the rthostid command.

SCCuAttr:
ObjectName = "backup"
ConfigObjectSerial = 4
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "9C5FE66FB"
ObjectAttributeType = "ulong"
SerialNumber = 4006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 17

On the secondary production server, use sccfgd_putcfg to load the configurations onto the node.
```
/usr/scrt/bin/sccfgd_putcfg 1 /tmp/C1.cfg
/usr/scrt/bin/sccfgd_putcfg 17 /tmp/C17.cfg
```
On the primary production server, use es_ha_config to display the device major number assigned to the Primary Context ID.
```
/usr/scrt/bin/es_ha_config 1
```
Current major number: 82
On the secondary production server, use es_ha_config to display the device major number assigned to the Primary Context ID. If the major number displayed matches the major number displayed on the primary production server no additional changes are needed, otherwise proceed to step 11.
```
/usr/scrt/bin/es_ha_config 1
```
Current major number: 83
On the secondary production server, use /usr/sbin/lvlstmajor to obtain a list of unused device major numbers. If the major number assigned to the Primary Context ID on the primary production server is available in the displayed output, proceed to step 11, otherwise proceed to step 12.
```
lvlstmajor
```
```
51,54,57,61,65,69,82...
```
On the secondary production server, use es_ha_config to configure a device major number for the Primary Context ID. Use the same device major number that is assigned to the Primary Context ID on the primary production server.
```
es_ha_config <Primary ContextID> [NewMajorNumber]
```
For example, execute:
```
es_ha_config 1 82
```
The Primary Context ID is 1, and the new device major number 82, is assigned to the Primary Context ID on both production servers.
If the device major number assigned to the Primary Context ID on the primary production server is not available on the secondary production server, then an outage is required to reconfigure the device major number on both the Primary and Secondary PowerHA Production servers.