Hello all - I'm starting out scripting on some Windows Servers that have connected LUNs, and when trying to use Get-NcHostDisk, I get this error: Get-NcHostDisk : Could not load file or assembly 'System.Security.Principal.Windows, Version=4.1.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. Is there a .NET Framework (or some other) requirement that I'm missing? I can't find any dependency info on what it may be looking for. This is running on Windows Server 2022, and I've tested with the two latest versions of the netapp.ONTAP module (9.16.1.2501 and 9.17.1.2509). Commands such as Get-NcVol work fine so I know I'm connected.
... View more
Hi All, We are currently perform NetApp trident PoC and facing challanges to apply the QoS into the PV volume below are my Trident config . # ./tridentctl get backend -n trident +------------------------+----------------+--------------------------------------+--------+------------+---------+ | NAME | STORAGE DRIVER | UUID | STATE | USER-STATE | VOLUMES | +------------------------+----------------+--------------------------------------+--------+------------+---------+ | ontapnas_100.104.5.206 | ontap-nas | 18088a47-d344-47ab-9901-73256bbd5866 | online | normal | 1 | +------------------------+----------------+--------------------------------------+--------+------------+---------+ PROD root@syssmgtridentpoc01 [17:03:31] [/opt/trident/trident-installer] (12:0) # ./tridentctl -n trident version +----------------+----------------+ | SERVER VERSION | CLIENT VERSION | +----------------+----------------+ | 25.06.0 | 25.06.0 | +----------------+----------------+ I am able to create the PV volume below is the logs. # ./tridentctl get volume -n trident +------------------------------------------+--------+---------------+----------+--------------------------------------+-------+---------+ | NAME | SIZE | STORAGE CLASS | PROTOCOL | BACKEND UUID | STATE | MANAGED | +------------------------------------------+--------+---------------+----------+--------------------------------------+-------+---------+ | pvc-c1be1751-ae0c-4c42-9e12-50b5dc025355 | 10 GiB | trident-nfs | file | 18088a47-d344-47ab-9901-73256bbd5866 | | true | +------------------------------------------+--------+---------------+----------+--------------------------------------+-------+---------+ PROD root@syssmgtridentpoc01 [17:05:22] [/opt/trident/trident-installer] (14:0) # But when I am trying to create a new PV volume having QoS applied getting the below error . Below are my storageclass and PVC yaml file # cat storageclass_qos.yaml apiVersion: storage.k8s.io/v1 kind: StorageClass metadata: name: trident-nfs-qos provisioner: csi.trident.netapp.io parameters: backendType: "ontap-nas" qosPolicy: "qos_policy" PROD root@syssmgtridentpoc01 [17:03:01] [/opt/trident/trident-installer] (10:0) # cat pvc_qos.yaml apiVersion: v1 kind: PersistentVolumeClaim metadata: name: trident-pvc-qos namespace: default spec: accessModes: - ReadWriteMany resources: requests: storage: 10Gi storageClassName: trident-nfs-qos Error Log of the failed PVC PROD root@syssmgtridentpoc01 [17:03:06] [/opt/trident/trident-installer] (11:0) # # kubectl describe pvc trident-pvc-qos Name: trident-pvc-qos Namespace: default StorageClass: trident-nfs-qos Status: Pending Volume: Labels: <none> Annotations: volume.beta.kubernetes.io/storage-provisioner: csi.trident.netapp.io volume.kubernetes.io/storage-provisioner: csi.trident.netapp.io Finalizers: [kubernetes.io/pvc-protection] Capacity: Access Modes: VolumeMode: Filesystem Used By: <none> Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Provisioning 2s (x3 over 26s) csi.trident.netapp.io_trident-controller-6594747b-plxsl_f4c31814-778c-4041-808a-6df36d0869d2 External provisioner is provisioning volume for claim "default/trident-pvc-qos" Warning ProvisioningFailed 2s (x3 over 26s) csi.trident.netapp.io_trident-controller-6594747b-plxsl_f4c31814-778c-4041-808a-6df36d0869d2 failed to provision volume with StorageClass "trident-nfs-qos": rpc error: code = Unknown desc = unknown storage class: trident-nfs-qos Normal ExternalProvisioning 0s (x3 over 26s) persistentvolume-controller Waiting for a volume to be created either by the external provisioner 'csi.trident.netapp.io' or manually by the system administrator. If volume creation is delayed, please verify that the provisioner is running and correctly registered. Verified on Net App side QoS policy is exist . nlab-100-nas::> qos policy-group show Name Vserver Class Wklds Throughput Is Shared ---------------- ----------- ------------ ----- ------------ --------- extreme-fixed nlab-100-nas user-defined 0 0-50000IOPS,1.53GB/s false performance-fixed nlab-100-nas user-defined 0 0-30000IOPS,937.5MB/s false qos_policy N1_svm01 user-defined 0 5IOPS-10IOPS true value-fixed nlab-100-nas user-defined 1 0-15000IOPS,468.8MB/s false 4 entries were displayed. nlab-100-nas::>
... View more
Hi All, We're looking at a DR test where we would delete a volume, recreate it and restore its contents from backup. We will need information about the volume properties/settings/etc. This is presumably somewhere in the nightly .7z config backup we keep but I've tried extracting that mess and can't find anything. Any guidance would be appreciated. Randy
... View more
Hi Team I'm getting below event on my OnTap which is running on 9.15.*.* "mgmtgwd.certificate.expired: A digital certificate with Fuly Qualified Domain Name (FQDN) snap, Serial Number 173B18A666E8BCBF, Certificate Authority 'snap' and type server for Vserver backup_svm has expired." As I know how to renew by my concern while renewing its giving below popup so just want to confirm if i simply renew it will it impact my OnTap Renew client/server certificate The existing certificate won't be deleted, but a copy of the certificate will be created. You should manually remap applications associated with the old certificate to be associated with the new certificate. Existing certificate name snap_173B18A666E8BCBF Please suggest
... View more
Hello all, We are deploying some new hosts in a cluster. One of the hosts fails with following message "Host is out of compliance with the image" all other hosts work fine. When I remove the component "NetApp NAS VAAI Module for ESX Server" the compliance check succeed. Any clue what else we can do? Thank you!
... View more