Brian,
Snapmirror and vol copy turned out not to be an option, because the 760 is at 5.3.1; we're getting the 'volume is in transitional state, aborting' error even though the destination is offline. NDMP copy looks like the remaining method, the 760 is being upgraded to 6.2.1 and I want to duplicate the data before starting that.
Piotr,
Yes, disks and data too. %-{)# What I saw from the first attempt was no response to ping, on either side, even after doing ifconfig down/up of the e9b nic. Maybe the magic arp has leaked out the switch I was using? After connecting the original filer I had to do arp -d and ping again, before it would respond to the unix host mount request.
-----Original Message----- From: Brian Long To: Toal, Dave Cc: 'toasters@mathworks.com' Sent: 7/19/02 10:37 AM Subject: Re: arp spoof, 840 with 6.2.1
Dave,
Are you replicating the data to the F840 or just moving shelves? If you're replicating data with something like Snapmirror, you might consider the Ontap 6.X snapmirror migrate command. This alters the disk labels on the destination so you don't end up with stale NFS filehandles on all the clients (if you're using NFS). For CIFS, you don't need to worry about this.
/Brian/
Good morning. I've got a question about substituting one netapp for another, by setting the ip addresses the same and changing the ethernet cable going to the switch from one to the other.
The netapp I'm trying to bring online is the 840. The ether (mac) addresses are showing different from inconfig, and I'm wondering if there's a way to set that explicitly; I don't see it from the options listed.
the 840:
netapp-demo*> ifconfig e9b e9b: flags=48043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 206.33.27.85 netmask 0xffffffc0 broadcast 206.33.27.127 ether 00:20:fc:1e:3a:75 (100tx-fd-down) netapp-demo*>
the other netapp, a 760 running 5.3.6R1:
wesson> ifconfig e0 e0: flags=200043<UP,BROADCAST,RUNNING> mtu 1500 inet 206.33.27.85 netmask 0xffffffc0 broadcast 206.33.27.127 partner inet 206.33.27.86 (not in use) ether 00:a0:98:00:78:c5 (100tx-fd-up) wesson>
-- Dave Toal Thomson & Thomson North Quincy, MA
On Fri, Jul 19, 2002 at 12:19:14PM -0400, Toal, Dave wrote:
What I saw from the first attempt was no response to ping, on either side, even after doing ifconfig down/up of the e9b nic.
ARPs do timeout[1]. Make sure you delete ARPs both on hosts and switches -- some of the beasts do ARP caching, which may either be good or bad. Oh, make sure you (or your network manager) did not make the network supersecure by entering static ARP entries on switch ports.
p.
[1] I know, they should get overwritten with a new entry on the switch.