I have ONTAP Select up and running on a vSphere cluster. I have a SVM created with a volume and NFS exports. The management and data interfaces are on different subnets. All the network interfaces are using one Ethernet port e0a. How do I get the data lif 's to use the other ethernet ports e0b and e0c? I'm assuming that e0a, e0b and e0c correspond to the three network adapters that I see on the node VM.
... View more
We are on AFF300 with OnTAP 9.8P2, tested a volume snapmirror & snapvault from a source cluster to a destination cluster. But looks the snapvault snapshots never created on destination. Not sure what i missed. Can someone please share your experience. Thanks in advance Confirmed we do have snapvault license on both source and destination clusters. Here is what i did. 1. peered Cluster and SVM 2. set up a XDP snapmirror relationship on a testing volume * scheduled snapshot copies on source volume policy default schedule hourly 6; daily 2;weekly 2 snapmirror label daily, weekly * protection policy: Asynchronous snapmirror lable: daily, weekly retention count: 7, 52
... View more
hi, everyone: could you help me solve the following question ? what's wrong the box ? <LR d="01May2021 04:03:22" n="B-BACKUP-SPA" t="1619813002" id="0/3762391351297" p="2" s="Ok" o="mgwd" vf="" type="1" seq="1208529" > <callhome_hm_sas_alert_major_1 subject="SAS Connectivity Monitor: DualPathToDiskShelf_Alert[50:0a:09:80:04:98:b1:c0]"/> </LR>
... View more
Hey, I’m trying to deploy ontap select 9.8 with evaluation license, 2-node small cluster for testing. I’m using external storage, vmfs luns from a physical ontap appliance. the deploy fails with the error “failed to obtain http lease for vmdk upload” and I could not find anything on the internet for that. anyone familiar with issue? btw vcenter and esx hosts are 6.5, I don’t remember the exact build number. thanks in advance,
... View more
hello all, we have a netapp storage running cdot [version: NetApp Release 9.6P3 ], we have the below issue and need to know the solution or the troubleshooting steps for it: Event: snmp.server.busy: SNMP daemon is busy serving a high rate of incoming SNMP queries. Message Name: snmp.server.busy Description: This message occurs when the SNMP daemon is busy serving a high rate of incoming SNMP queries. This might be caused by multiple SNMP clients querying the cluster or a malicious client attempting a denial-of-service attack. SNMP clients might experience delays or timeouts.
... View more
