Dell Solutions Enabler 10.0.1 Release Notes

 
cd /
./inq.AIX | more (look for no gaps in the numbers, ie.. rhdisk0,
rhdisk1, rhdisk3... - rhdisk2 is missing)
cd /usr/lpp/Symmetrix/bin
./mkbcv -a ALL
cd /
./inq.AIX | more (look for no gaps in the numbers, ie.. rhdisk0,
rhdisk1, rhdisk2... - rhdisk2 is not missing)

Hostname : ftp.emc.com
Username : anonymous

Directory: /pub/symm3000/inquiry/
File : inq.aix...[select file for your system here]

Directory: /pub/symm3000/aix/ODM_DEFINITIONS/
File : mkbcv

If you delete a PowerPath pseudo device (hdiskpower) using rmdevice -d, and then add the native device into a composite group, the device will not persist when you reboot. Also, if you delete a powerpath0 device, all of the non-visible composite group members become lost upon reboot.

The same criteria holds true for configuration change operations where BCV or SRDF device attributes are being changed. The ODM configuration will not reflect the latest changes without device re-scanning on the AIX host.

Even after a rescan on the AIX host, the former R1 devices will appear in the definedstate and new device nodes for the R2 appear in the available state. It is recommended in this case to manually delete the defined devices. On AIX machines, SYMCLI operations may fail because the storapid or storsrvd daemons run out of memory. AIX has a limit on the amount of data that a process can allocate. Therefore, if the daemon is being used heavily, the daemon may run out of memory, even when there is enough physical memory available on the system.

1. Stop all Solutions Enabler services: stordaemon shutdown all -immediate
2. Run the ldedit command (this increases the default data allocation limit of an AIX process from 256 MB to 2 GB). For storapid enter:

   /usr/ccs/bin/ldedit -bmaxdata:0x80000000
   /usr/symcli/daemons/storapid

   For storsrvd enter:

   /usr/ccs/bin/ldedit -bmaxdata:0x80000000
   /usr/symcli/daemons/storsrvd

3. Restart everything.

When experiencing memory issues could be experienced in an AIX 64-bit environment with large objects and/or a large number of extents, you should

• On IBM AIX platforms, if a physical device is a member of a volume group. In this case, AIX places a SCSI reservation on the device, which prevents symchg from opening the device properly.
• A failed device is encountered. If symchg delete fails, you must apply the command to one device at a time for all devices of the group.

For example, assume you have a port group that contains an FA that was ACLX-enabled when the backup was created. After a configuration change operation, that same FA is no longer ACLX-enabled. This port will be removed from the port group and any view that contained this group will not be restored. if either the SG or the IG within the view belong to another view that is restored, the masking data is not properly restored.

The space is limited to 64 characters. This includes the reserved token storsrvd that precedes the value specified for the create command. The maximum length of the Common Name argument is 55 characters.

Usually the library is versioned (libdevmapper.so.1.02), so it must be pointed to by the symbolic link libdevmapper.so.

Refer to Dell Knowledgebase articles 474135 and 438569 for more information.

However, when operations are performed on the local devices in a composite group with the -exact option, the exact pairing operation considers the context of the local array when performing the exact pairing of the standard and BCV devices.

When operations are performed on the remote devices in a composite groups with the -exact option, the exact pairing operation considers the context of the array and associated SRDF group when performing the exact pairing of the standard and BCV devices.

The symclone activate command takes advantage of the consistency feature.

To consistently split BCV pairs using ECA you must have either a control host where you are not running data write I/O, or a database host with a dedicated channel to perform the consistent split.

Once the symmir split -consistent command is issued, I/O to the device group is frozen and a 30 second Enginuity protection timer begins and opens an ECA window. After 30 seconds, the I/O channels are thawed, granting (pent up) operations access to the standard devices. Splits across all devices in a group are considered consistent if the BCV split execution is performed within that window. If for some unknown host or I/O channel reason, not all devices are split within the 30 second window, symmir returns the following at completion:

Consistency window was closed on some devices before the operation completed.

At this point, the final successful split outside the window is no longer considered consistent in execution across the device group. For consistency and reliability, you should re-establish the device group and then (later) attempt the consistent split again.

There are possible instances in a client/server environment that the return error message for a failed TimeFinder operation is vague or incomplete, as shown in the following example with no text after the colon: "BCV Library error is:"

When this occurs, view the SYMAPI log file on the server for the complete error message statement.

When using symmir -rrbcv to verify the states with a LDEV list, always specify the standard and target pairs. Only specifying the standard devices in the LDEV list may not return the correct result.

For example, add an alternate hostname like this when prompted by the zoscert command:

Fully qualified z/OS hostname []: a1.host.domain b2.host.domain

The first name specified is used in the Common Name field in the generated certificate. Each succeeding name or IP address is coded in a Subject Alternative Name entry in the certificate.