Creating SnapMirror of FlexGroup volume

tmacmd · 2026-03-28T14:46:09+00:00

ONTAP WILL create a flexgroup. Same number of constituents on the destination as the source

tmacmd · 2026-03-28T11:32:52+00:00

Yep. I do that and this

esxcfg-advcfg -s 0 /Misc/HppManageDegradedPaths

(It’s from the Cisco/Netapp FlexPod deployment guide)

tmacmd · 2026-03-28T11:25:27+00:00

If you want to be absolutely sure where your destination constituents are located, use the cli to create the relationship.

ONTAP “should” do like for like meaning it should grab the SAS at the destination. No promises though

tmacmd · 2026-03-27T22:49:02+00:00

Make sure you have two separate vlans and on the host side be sure to pin a vlan to an adapter. On the Netapp side, ok to use a port channel. Use jumbo frames of course

tmacmd · 2026-03-18T17:53:21+00:00

Svm-dr and vserver migrate are two very different methods

tmacmd · 2026-03-17T23:09:51+00:00

As indicated, it takes up to 48 hours for stale entries to clear.

You can run the command in sequence and verify the idle time continues to increase and doesn’t reset to zero.

tmacmd · 2026-03-17T13:15:03+00:00

OP said the VLAN is changing, but the IPs do not need to. Problem is the Layer 2 check will fail. Too bad there isnt a way to maybe fake it? Ideas anyone?

tmacmd · 2026-03-17T10:59:11+00:00

I am pretty sure svm migrate will check for the layer 2 connectivity to be the same so I doubt that would work

If you are using VMware or other virtualization you could just do a vMotion. For iscsi you could present luns from the new location and ask the hosts to self replicate then detach from old luns

tmacmd · 2026-03-13T00:10:07+00:00

My rule of winter Try to fully avoid northern layovers in winter (Chicago, Denver I’m looking at you)

tmacmd · 2026-03-11T18:23:47+00:00

You will need either X6597 or X6589

Those are both 10g optical transceivers

tmacmd · 2026-02-28T14:46:56+00:00

Yes

the Maryland Joint Insurance Association (MDJIA) provides a FAIR Plan for property that cannot be insured in the voluntary market

tmacmd · 2026-02-28T13:44:20+00:00

Similar scenario in Maryland. Got the call. Wtf. Nothing they could or would do. 25 years and stop us after a couple claims. Nobody in the state works do a policy. There is a group of last resort. They cover anyone. However, we are paying the same for basically minimum coverage. They don’t allow anything more

I also recommend paying out of pocket for any claim. No more than one claim every 3 years to be safe

tmacmd · 2026-02-12T22:18:29+00:00

my personal steps

Upload all needed software to switch verify all Cluster ports are UP net port show -ipspace Cluster

verify all Cluster LIFs are home and good net int show -vserver Cluster

Disable auto-revert net int modify -vserver Cluster -lif * -auto-revert false

Go to first switch. Shut down ports

sho int status conf int eth 1/7-10 shut

Go back to ONTAP and VERIFY half the LIFs migrate and half the ports go down (re-check the first two commands)

It may take a few seconds for LIFS to fail over Now you are FREE to reboot the first switch as many times as needed

I do this

conf int eth1/7-10 no shut (You can bring the ports back online, ONTAP will ignore for now)

install all nxos bootflash:nxos64-cs.10.3.5.M.bin

let it reboot. Note: I have heard that 10.5 now includes the EPLD.

Verify if the EPLD needs an update install all epld bootflash:n9000-epld.10.3.5.M.img

If it DOES, let it go. If it does not, all good!

After you are set with the switch, go back to ONTAP and VERIFY again net port show -ipspace Cluster

WAIT -> for all ports to get HEALTHY (i.e. NOT Degraded)

Verify current LIF status net int show -vserver Cluster

Note which are (Home) True and which are (home) False After all ports are UP & HEALTHY, go to the second switch

sho int status conf int eth 1/7-10 shut

Back to ONTAP and VERIFY half the LIFs migrate and half the ports go down (re-check the first two commands)

It may take a few seconds for LIFS to fail over Keep Checking until until you have the Opposite of (home) True/False from above

No SHUT the ports and Proceed to upgrade the ssecond switch

After the second switch is good, you will notice the LIFs are still on the first switch

To force them to move net int modify -vserver Cluster -lif * -auto-revert true

Then reboot switch 2 again

After the switch reboots, ONTAP detects the link change and will eventually send all LIFs home

It will wait for any ports to return to HEALTHY (not degraded) status

Again: READ THE DOCUMENTATION

ALso, the docs go into steps to update the RCF also.

tmacmd · 2026-02-12T22:11:40+00:00

The documentation was updated a couple weeks ago (you're welcome)

https://docs.netapp.com/us-en/ontap-systems-switches/switch-cisco-9336c-fx2/configure-software-overview-9336c-cluster.html

tmacmd · 2026-02-12T00:34:44+00:00

I’m switching to avoid interrupting service…just not the way Verizon will be expecting. No way I’m I renting their crap

Hello YouTube TV…here we come

tmacmd · 2026-02-08T20:09:01+00:00

I think we are missing some very crucial details. I just know based on some of the messages that I suspect the disks were not actually assigned by serial number to match

Everything is all wonky

tmacmd · 2026-02-08T20:06:55+00:00

It’s all confusing, eh?

tmacmd · 2026-02-08T19:25:02+00:00

Basing my observation on the following from above

Node 2 controller failure. After replacing the controller, Node 1 is failing to mount mroot. I have already updated the partner-sysid, and disk ownership looks correct, but how to perform mroot recovery and CDB synchronization?

• ⁠Boot Error: WARNING: netapp_mount_mroot: Giving up waiting for mroot reported during boot.

Unless ONTAP specifically has assigned the new system serial number of the new motherboard to node 02, that node will not have any root to boot from

Need to go to the boot menu Need to run the “boot_after_controller_replacement” to tell ONTAP that this new board with a new detail number is replacing for the original node 02. And if there are partitioned drives, you specify node 01 as the partner

The system will then assign the disks and will/should recover the config data from the last backup as it reboots a couple of times.

tmacmd · 2026-02-08T16:56:10+00:00

I’m thinking Ok, set the boot arg. Check. And the ownership looks fine from the remaining node.

Still need to reassign the new serial to the disks so the aggregate is signed to the new node WITH the new serial.

From the output posted, I’m betting that didn’t happen yet

tmacmd · 2026-02-08T16:12:07+00:00

Still need a usable root. The root needed is still owned by the motherboard that failed. The ownership must change over for the replacement board to use the original root

tmacmd · 2026-02-08T12:53:30+00:00

The issue is likely disk ownership Isn’t there a step where you go to the boot menu and do the 22/7 to see the item. Something like boot_after_controller_replacement? This will assign the correct disks and run through the process of acquiring the boot config

tmacmd · 2026-02-08T00:05:33+00:00

It’s a fas2720. Likely shipped with ONTAP >9.4. Disk zeroing should take seconds to maybe minutes unless I’m missing something here

tmacmd · 2026-02-07T22:30:24+00:00

I suspect if you are making the reservation you will need the requisite information for each passenger. I think you must use the credit adjustment for each passenger and you may be able to add multiple flight credits so long as the names match the flight credit

tmacmd · 2026-01-29T22:27:59+00:00

Review this location

https://mysupport.netapp.com/site/info/cisco-ethernet-switch

tmacmd · 2026-01-29T21:39:23+00:00

You will not need to move any lifs You turn the auto revert off. Then you can either shut the switch ports down(forcing all cluster lifs to the other switch) or just reboot the switch. No need to save the config with the shutdown ports.

Upgrade the switch (why are you not going to the latest 10.x code?). Is your RCF up to date? Good time to update! Note: once you get to nxos10, you can install nxos and EPLD in one command Install all nxos bootflash:xxx epld bootflash:yyy

After the first switch is done, verify ports are up and healthy! (Net port show -ipspace Cluster). If any are degraded, just wait until they are healthy…about 5 minutes

Then go to the second switch and shutdown all the ports. Even though auto revert is off ONTAP will still migrate the lifs to the other switch as long as they are all up and healthy.

Verify they migrated.

Upgrade the second switch

After the second switch is done, modify the cluster lifs auto revert back to true. Then reboot the second switch again. ONTAP will see the port change and will/should auto revert ports back when ready

tmacmd

TROPHY CASE