What is a possible reason for this issue?

An administrator implemented SYMACLs on a VMAX3 using hardware-based Access IDs. The administrator is not able to run SYMCLI commands against the volumes belonging to a host. The volumes were originally provisioned using the host in which the host in which the administrator experienced issues.

What is a possible reason for this issue?
A . SYMAPI options file was manually modified with the wrong host ID
B . symacl Cunique Cpassphrasewas run using a different passphrase
C . Host is not in the eMgmt Access Group
D . Host network interface card was replaced

View Answer

Answer: B