Coexistence of NetApp (ONTAP REST API) and NetApp Active IQ UM
The following table gives several scenarios where the NetApp REST and the NetApp Active IQ storage patterns coexist in the same environment.
Scenario N° | Client’s environment | Credential – Access method | Outcome |
|---|---|---|---|
1 | NetApp system discovered using the NetApp Direct Access method | REST API with basic authentication | A Storage Device is discovered, and then the NetApp_Storage_REST pattern is triggered to discover the NetApp system based on the distributed storage model. |
2 | NetApp system discovered using the NetApp UM Active IQ Access method | SSH/Windows + REST API with basic authentication | A Host + SI is discovered, and then the NetApp Storage Active IQ pattern is triggered to discover the NetApp system based on the distributed storage model. |
1+2 | The NetApp system already discovered by using the Direct Access method, and then the NetApp UM Active IQ Access method is provided | Initially REST credential was provided. Later, the SSH/Windows + REST credential is provided for UM Active IQ. | A new Host + SI is discovered, and the NetApp Storage Active IQ pattern is triggered. The NetApp Storage Active IQ pattern will search if a NetApp Cluster is already discovered. If so, a relationship is created between the nodes listed below and the pattern stops:
|
2+1 | The NetApp system already discovered by using the NetApp UM Active IQ Access method, and then the NetApp Direct Access method is provided | Initially, SSH/Windows + REST credential is provided for UM Active IQ. Later direct REST credential was provided. | A new Storage Device is created, and the NetApp Storage REST pattern is triggered. The NetApp Storage REST pattern will discover the entire NetApp storage system. As all the keys are the same for all the nodes, there will not be any duplicates or model change. For the NetApp volumes (File System node), since the keys are different, file systems are duplicated. Once the scan is finished, a new relationship is created between:
|
3 | The NetApp system already discovered by using the NetApp UM Active IQ Access method OR The NetApp system already discovered by using the Direct Access method | REST API with basic authentication + SSH/Windows + REST API with basic authentication (UM Active IQ user) | Irrespective of the access type (Direct or UM Active IG), if any of the provided credentials are valid, the NetApp system will be discovered based on the distributed model. Even if the Access type has been changed, the same model applies, and some data may be missing, as detailed in the table below:
|
Discovery information available based on Direct and Active IQ access methods
NetApp cluster | BMC Discovery | NetApp Direct | NetApp UM Active IQ |
NetApp Cluster | StorageSystemGroup | Yes | Yes Missing attributes: Serial.
|
NetApp Node | StorageSystem | Yes | Yes |
SVM | StorageSystem | Yes | Yes |
NetApp Node | StorageProcessor | Yes | Yes Missing attributes: Firmware, Memory. |
NetApp FC Ports | FibreChannelPort | Yes | Yes |
NetApp Aggregate | StoragePool | Yes | Yes Defect identified in current version of Active IQ where the aggregate information is not entirely collected. |
NetApp Volume | FileSystem | Yes | Yes The FileSystem node keys are different, therefore some discovered file systems may be duplicated. |
NetApp Qtree | FileSystem | Yes | Yes The Quota information is missing. |
NetApp LUN | StorageVolume | Yes | Yes Missing attributes: Thinly Provisioned. |
NetApp Shelf | HardwareContainer | Yes | Yes |
NetApp Disk | DiskDrive | Yes | Yes |
Port | NetworkInterface | Yes | Yes Missing attributes: Duplex, Negotiation. |
IP | IPAddress | Yes | Yes |