Ontap Vif miscellany

A few things about networking on a FAS2050.

The FAS2050 has two ports per controller: e0a and e0b. There is a management port (with a wrench symbol) but I can find no trace of this from the software side of things.

From controller 1 I deleted all the vifs so that I would have to learn to recreate them via SSH. On the switch each port that the Netapp is plugged into is configured as follows:

interface FastEthernet0/2
 switchport trunk allowed vlan 100,302,303
 switchport mode trunk
 spanning-tree portfast

I decided that I ought to aggregate the two ports so I ran this command:

vif create multi dennis e0a e0b

The multi could have also been "single" or "lacp". Multi and LACP are forms of aggregation whereas single is an active / passive arrangement. I could have also added a "-b" switch to specify the type of balancing (IP, port, MAC or round robin - I think IP is default).

I then created the VLANs to correspond with the switch port settings:

vlan create dennis 100 302 303

I then decided I didn't need VLAN 302 and 303 for this test:

vlan delete dennis 302 303

Finally, I had to assign an IP address to the new interface. Hence:

ifconfig dennis-100 10.10.10.54 netmask 255.255.0.0

DR Server Migration

The great virtualisation project mentioned in the last post hasn't really kicked off as I had envisioned and no hardware has made an appearance yet! From the outset this blog has been a roller coaster ride of exciting facts so apologies to my avid readers for the delay here.

Had a simple server move to do yesterday. We moved a switch, a storage server and its associated SAS-attached storage and an ESXi server from one data center to another. A NetApp FAS2050 was decommissioned and lies unused on our server room floor.

The decommisioned 2050 was the snapmirror target but was replaced by a hosted "vFiler". I intend on powering up the old one soon, but what do I have to do to it beforehand? Delete snapshots, that's what:

Show all snapshots on the current controller:
 
snap list

Show the status of the various snapmirrors:

snapmirror status

Delete a particular snapshot:

snap delete [volume_name] [snapshot name]

One of the snapmirrors to the decommisioned SAN was "busy" and so the snapshot could not be deleted. I used

snapmirror abort [source_filer]:[volume_name] [destination_filer:volume_name]

But it told me that it was already idle. So how could I delete a snapshot that was supposedly busy (but was not apparently involved in a snapmirror)?

Well it turns out that that volume was being snapmirrored to the new hosted vFiler and this was causing a lock. I'm not sure, since there are two snapshots for that volume, one for the old destination and one for the new destination, why this would happen but there you go.