Are you sure you have not misunderstood the question? If you have not, please point to the place in documentation which describes negotiated switchover due to all LIF ports down. So far documentation states the following reasons for AUSO: Node power down, Node power loss, Node panic, Node reboot. Nothing about network whatsoever.

↧

Re: vscan status on cDOT 8.3.2

November 22, 2016, 3:31 am

≫ Next: changing boot options of a 7-mode filer

≪ Previous: Re: Negociate switchover on port failed

Thanks,

I found my value but it's not very simple for know if there's new request on my AV server....

Best Regards

↧

changing boot options of a 7-mode filer

November 22, 2016, 6:56 am

≫ Next: Re: changing boot options of a 7-mode filer

≪ Previous: Re: vscan status on cDOT 8.3.2

Hello Guys,

We did a ontap upgrade version from 8.2 to 8.3 , post upgrade one of the filer is not booted up with the upgraded version . The boot_backup option worked with the newer firmware

I suspect the problem could be on the boot parameters , below are the parameters

LOADER-B> printenv

Variable Name Value
-------------------- --------------------------------------------------
CPU_NUM_CORES 4
BOOT_CONSOLE sp0a
BIOS_VERSION 8.3.0
BIOS_DATE 04/08/2014
SYS_MODEL FAS2240-2
SYS_REV D2
SYS_SERIAL_NUM 600000343200
MOBO_MODEL FAS
MOBO_REV D2
MOBO_SERIAL_NUM 9430750215
CPU_SPEED 1730
CPU_TYPE Intel(R) Xeon(R) CPU C3528 @ 1.73GHz
savenv saveenv
ENV_VERSION 1
LOADER_VERSION 4.3
ARCH X86_64
BOARDNAME SB_XIX
PRIMARY_KERNEL_URL fat://boot0/X86_64/kernel/primary.krn
BACKUP_KERNEL_URL fat://boot0/backup/X86_64/kernel/primary.krn
GX_DIAG_URL fat://boot0/X86_64/freebsd/image2/kernel
ntap.init.kernelname X86_64/freebsd/image2/kernel
FIRMWARE_URL fat://boot0/X86_64/firmware/SB_XIX/firmware.img
BIOS_INTERFACE 9FC3
BOOT_FLASH flash0a
GX_PRIMARY_KERNEL_URL fat://boot0/X86_64/freebsd/image2/kernel
GX_BACKUP_KERNEL_URL fat://boot0/X86_64/freebsd/image1/kernel
boot_ontap autoboot boot0
boot_primary setenv BOOTED_FROM PRIMARY; boot -elf64 $GX_PRIMARY_KERNEL_URL $PRIMARY_KERNEL_URL
boot_backup setenv BOOTED_FROM BACKUP; boot -elf64 $GX_BACKUP_KERNEL_URL $BACKUP_KERNEL_URL
netboot setenv BOOTED_FROM NETWORK; boot -elf64
boot_diags boot -sld -elf64 $GX_DIAG_URL $PRIMARY_KERNEL_URL
ldkern load -elf64 $GX_PRIMARY_KERNEL_URL $PRIMARY_KERNEL_URL
update_flash flash -backup $FIRMWARE_URL flash0a
version printenv BIOS_VERSION LOADER_VERSION
BT_BIOS_VERSION 8.3.0
BT_LOADER_VERSION 4.3
AUTOBOOT true
AUTOBOOT_FROM PRIMARY
AUTO_FW_UPDATE true
USE_SECONDARY true

i am not quite sure on how to change the parameters ?

Thanks

Saran

↧

Re: changing boot options of a 7-mode filer

November 22, 2016, 6:57 am

≫ Next: Re: changing boot options of a 7-mode filer

≪ Previous: changing boot options of a 7-mode filer

Use the below command

setenv AUTOBOOT true

boot_primary

↧

Re: changing boot options of a 7-mode filer

November 22, 2016, 7:01 am

≫ Next: Re: changing boot options of a 7-mode filer

≪ Previous: Re: changing boot options of a 7-mode filer

I assume you mean a different version of 8.2, b/c there is no 8.3 7-mode

↧

Re: changing boot options of a 7-mode filer

November 22, 2016, 7:06 am

≫ Next: Re: changing boot options of a 7-mode filer

≪ Previous: Re: changing boot options of a 7-mode filer

please paste the command out put of

version -b

↧

Re: changing boot options of a 7-mode filer

November 22, 2016, 7:22 am

≫ Next: Enable read reallocation on a volume?

≪ Previous: Re: changing boot options of a 7-mode filer

What told is right. There is no 7-mode on 8.3. From 8.3 the only version is c-mode.

↧

Enable read reallocation on a volume?

November 22, 2016, 8:39 am

≫ Next: Re: Enable read reallocation on a volume?

≪ Previous: Re: changing boot options of a 7-mode filer

Hi,

We're having some read latency issues on a particular volume in our environment. We can see both random- and sequential reads on the particular volume. Block size also seems to be bigger than on our other NFS datastores in our environment.

I have enabled read reallocation with the space-optimized option on the volume. Question: Do I also need to run a manually reallocation on the volume or will the volume start the reallocation in the background? Reallocate show doesn't show anything, only "This table is currently empty".

Environment:

Ontap 8.3.1

VMware vSphere 6

NFS datastore, VMDK

BR,

David T

↧

Re: Enable read reallocation on a volume?

November 22, 2016, 12:32 pm

≫ Next: Re: [CDOT] Change management IP addresses to different network

≪ Previous: Enable read reallocation on a volume?

Hello ,

ONTAP will automatically move sequentially read data into a more optimized layout. You do not need to run a manual reallocate of the volume specifically for the read reallocation feature.

Andrew

↧

Re: [CDOT] Change management IP addresses to different network

November 22, 2016, 5:17 pm

≫ Next: Can't ssh to the cluster / Can't access my cluster...

≪ Previous: Re: Enable read reallocation on a volume?

For cDOT 8.3. I had some issues finding the correct command with NetApp documentation (annoying). You can change the e0M network interface IP/subnet with the following command (Run this from console connection)

CLUSTER::> network interface show -curr-port e0M

displays entries that can be modified for the e0M management port for proper command syntax

CLUSTER::> set advance

advance command structure - approve

CLUSTER::> network interface modify -vserver VSERVER -lif LIFNAME -home-node HOMENODE -home-port e0M -address IPADDRESS -netmask NETMASK

you may have to include -force-subnet-assocation

The subnet should be created prior to moving IPs from my experience.

↧

Can't ssh to the cluster / Can't access my cluster...

November 23, 2016, 5:46 am

≫ Next: Question Regarding Total Latency and Throughput of Disk

≪ Previous: Re: [CDOT] Change management IP addresses to different network

I installed NetApp for Windows 8.3.2 Sim on Vmware Player. I was able to create a second node and join them. From my vmware player, I can see both nodes in the cluster and run CLI commands from the CLI inside the VMware Player.

HOWEVER I cannot

1.) ssh to the cluster via putty, nor can I

2.) Access my cluster (cant discover or add) to the NetApp SYSTEM MANAGER 3.1.2 that I installed on my Windows desktop. System Manager doesn't find. it. I cannot ping the IP either from a CMD prompt.

I think it's a simple fix, but I am banging my head against the wall for a fix.

Can you help me troubleshoot please. The Custer IP that is owned by the vmware is 192.168.X.20, which I set up per the NetApp 8.3.2 installation and set up guide instructions. I am a newbie to NetApp, so keep that in mind please. Thank you . AZPMTECH@YAHOO.COM.

We are runnng a production environment in a large IT organization, so I need to get this configured as soon as practical please. I can provide production (purchased) SN# offline if required. Thank you for your insight.

↧

Question Regarding Total Latency and Throughput of Disk

November 23, 2016, 6:50 am

≫ Next: Scheduled backup jobs ar failing

≪ Previous: Can't ssh to the cluster / Can't access my cluster...

I want to monitor Disk Performance for NETAPP and I am using ONTAP API. I need the following performance metrics from ONTAP API:

1)Total Latency for Disk:

We can monitor Total latency using "Operation_latency" field for Cluster-Mode Disk Performance data, but How to calculate Total Latency for 7-Mode Disk Performance data? Can we calculate it by using read/write latency? If yes then can you please give me an idea how to calculate?

2) Read Throughput and Write Throughput for Disk Performance:

Same as above, we can monitor Throughput using fields (read_data_rate and write_data_rate) for Cluster-Mode but how to calculate it for 7-Mode disk performance data?

We have read_blocks_rate and write_blocks_rate but I have tried to calculate Throughput using both this field(by multiplying block size) but it is not matching with that data_rate.

↧

Scheduled backup jobs ar failing

November 23, 2016, 6:58 am

≫ Next: Re: Scheduled backup jobs ar failing

≪ Previous: Question Regarding Total Latency and Throughput of Disk

Hi. Two weeks ago I rebuilt our NetApp FAS3270 8.1.4P9 7-mode. The purpose was to remove disk shelves to be reused at DR. By rebuilt I mean that I destroyed all aggrs, moved vol0 to a remaining aggr, removed disk shelves, reboots, and all looks good now. This filer was then going to be reused for OSSV target, as it was previously. I recreated volumes and shares (everyone full control). I ran snapvault start -S "remote_win_server:folder" FILER:/vol/volume/qtree. The initial job ran successully but hasn't run since. Note that I have not done anything with the OSSV client on the remote Windows Servers. I have a hundred or so of them that previously backed up to this filer but are not working now. Below are the snapvault options. I think they are right. I don't have support on this filer anymore so I'm depending on Google and this Community. Please let me know what you think.

CSRNETAPP03> options snapvault
snapvault.access             host=all
snapvault.enable             on
snapvault.lockvault_log_volume
snapvault.nbu.archival_snap_default on
snapvault.ossv.compression   off
snapvault.preservesnap       off
snapvault.snapshot_for_dr_backup vsm_base_only

↧

Re: Scheduled backup jobs ar failing

November 23, 2016, 6:34 am

≫ Next: Re: Can't ssh to the cluster / Can't access my cluster...

≪ Previous: Scheduled backup jobs ar failing

I also want to mention that in the snapvault log on the remote Windows servers the message is "Local TLog Backup is disabled. To re-enable, enter an interval between 5 and 55 and restart OSSV"

↧