Volume Group marked as unsecure after controller reboot
- Views:
- 9
- Visibility:
- Public
- Votes:
- 0
- Category:
- e-series-systems
- Specialty:
- esg
- Last Updated:
- 4/1/2025, 6:48:45 PM
Applies to
Issue
- After controllers rebooted; a single volume group went from a secure to non secured state.
- Pre-reboot
vdmShowVGInfo
shows volume group from both controllers as FIPS Enabled:
Controller A
Seq:20 / RAID 5 / VGCompleteState / TLP:F / DLP:T / SSM:T / ActDrv:12 / InActDrv:0 / VolCnt:2 / Secure:FIPS_ENABLED / DULBE:No
BlockSize:512 / LPE:3 / DBF:2 / PI Capable:T - 2 / Label:VolumeGroup / VGWwn:xxxxxxxxxxxxxxxxxxx / RsvdSpace: 5 (GB)
Controller B
Seq:20 / RAID 5 / VGCompleteState / TLP:F / DLP:T / SSM:T / ActDrv:12 / InActDrv:0 / VolCnt:2 / Secure:FIPS_ENABLED / DULBE:No
BlockSize:512 / LPE:3 / DBF:2 / PI Capable:T - 2 / Label:VolumeGroup / VGWwn:xxxxxxxxxxxxxxxxxxxxxxx / RsvdSpace: 5 (GB)
- After reboot both controllers marked the Volume Group as None Secure:
Controller A
Seq:20 / RAID 5 / VGCompleteState / TLP:F / DLP:T / SSM:T / ActDrv:12 / InActDrv:0 / VolCnt:2 / Secure:No / DULBE:No
BlockSize:512 / LPE:3 / DBF:2 / PI Capable:T - 2 / Label:VolumeGroup / VGWwn:xxxxxxxxxxxxxxxxxxxxxxx / RsvdSpace: 5 (GB)
Controller B
Seq:20 / RAID 5 / VGCompleteState / TLP:F / DLP:T / SSM:T / ActDrv:12 / InActDrv:0 / VolCnt:2 / Secure:No / DULBE:No
BlockSize:512 / LPE:3 / DBF:2 / PI Capable:T - 2 / Label:VolumeGroup / VGWwn:xxxxxxxxxxxxxxxxxxxxxxx / RsvdSpace: 5 (GB)