Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 1 results
    • Volume Group marked as unsecure after controller reboot
      https://kb.netapp.com/on-prem/E-Series/SANtricity-OS-KBs/Volume_Group_marked_as_unsecure_after_controller_reboot
      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: Seq:20 / RAID 5 / VGComple...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: Seq:20 / RAID 5 / VGCompleteState / TLP:F / DLP:T / SSM:T / ActDrv:12 / InActDrv:0 / VolCnt:2 / Secure:FIPS_ENABLED / DULBE:No After reboot both controllers marked the Volume Group as None Secure: Seq:20 / RAID 5 / VGCompleteState / TLP:F / DLP:T / SSM:T / ActDrv:12 / InActDrv:0 / VolCnt:2 / Secure:No / DULBE:No