Identify Devices to be Guarded with IDT-Capable GuardPoints
Storage devices in Teradata clusters are known as pdisks. A pdisk is a slice of a LUN exported from the backend storage system attached to the nodes in a cluster. For example, the pdisk named /dev/pdisk/dsk304 is a symbolic link to the slice on the LUN called /dev/disk/by-id/tdmp-360080e500043092c0000b46f5c34c018-part3, as shown below:
ls -l /dev/pdisk/dsk304
lrwxrwxrwx 1 root root 70 May 18 12:21 /dev/pdisk/dsk304 -> /dev/disk/by-id/tdmp-360080e500043092c0000b46f5c34c018-part3
CTE guards the devices represented by the pdisks in the Teradata cluster. In the example above, the device that you must configure and guard as an IDT-Capable GuardPoint is /dev/disk/by-id/tdmp-360080e500043092c0000b46f5c34c018-part3.
Note
You cannot use the symbolic link name when initializing or guarding the storage devices.
To identify the disks available to the Teradata cluster and require CTE protection, look in /dev/pdisks on each node in the cluster. Any symbolic links that point to a Linux device path are the disks that should be initialized.
Caution
Do not enter the path name of the pdisk device when initializing it for guarding or in the CipherTrust Manager when you actually guard the device.
