WAAS prepositioning before moving a server

pthaynes · ‎06-02-2008

I have a server out on a remote site with a WAFS edge enabled WAE NM in that remote router. I also have a WAFS core endabled WAE in the network core. I would like to preposition files to the edge WAE before I move the server into the core if possible. When I run the preposition jobs it looks like the edge WAE detects a possible network loop and the preposition task fails after about 30 minutes. Either way it looks like the file (probably compressed and optimised via DRE) is copied over the WAN anyway. Is there an easy and efficient way to preposition files from a server to a WAE in that same site before you shift the server to the network core?

Thanks in advance,

Peter

Zach Seils · ‎06-02-2008

Peter,

What model NME are you using?

What (logs, etc.) indicate there is a loop?

Zach

pthaynes · ‎06-02-2008

Zach,

The NMEs are NME-WAE-502-K9 having a gig of memory. I believe this means they can't be a WAFS core (if that is what you were getting at). The log I am looking at is the WAFS Edge log in the web gui for the WAE. The log entries are similar to this:

2008-06-02 17:00:01,871 INFO Preposition ID 28155 started on \\myserver.domain.internal\APPS\.

2008-06-02 17:04:41,475 ERROR Possible routing loop detected: CoreFE 192.168.1.1 tries to connect to server 192.168.2.2.

2008-06-02 17:11:13,943 WARN Host 192.168.2.2:139 was not discovered, bypass period: 0 sec, number of events: 1, reason: possible routing loop

2008-06-02 17:12:17,726 ERROR Possible routing loop detected: CoreFE 192.168.1.1 tries to connect to server 192.168.2.2.

2008-06-02 17:13:27,150 WARN Host 192.168.2.2:139 was not discovered, bypass period: 0 sec, number of events: 1, reason: possible routing loop

2008-06-02 17:14:08,972 ERROR Possible routing loop detected: CoreFE 192.168.1.1 tries to connect to server 192.168.2.2.

2008-06-02 17:14:54,772 WARN Host 192.168.2.2:139 was not discovered, bypass period: 0 sec, number of events: 1, reason: possible routing loop

2008-06-02 17:15:40,363 ERROR Possible routing loop detected: CoreFE 192.168.1.1 tries to connect to server 192.168.2.2.

2008-06-02 17:17:11,796 WARN Host 192.168.2.2:139 was not discovered, bypass period: 0 sec, number of events: 1, reason: possible routing loop

Zach Seils · ‎06-04-2008

Thanks Pete. As you stated, we don't have the option to run the WAFS Core service on the NME-WAE-502. This means you'll have to do one of the following:

- Preposition from the WAFS Core in the Data Center, which means that the PP data crosses the WAN twice.

- Copy the remote site server data (or a subset of the data) through WAAS (towards the DC) using CIFS.

- Wait until the data is migrated to the DC to execute a PP job.

Zach