IX.
Step
a)
There are two different procedures for transferring the system files:
(i) Disruptive procedure (ii) Non-Disruptive procedure
b)
c)
1
Inform end-user the following:
(i)
This action plan defaults to using an HTTP Webserver for sourcing the netboot kernel and ONTAP images.
(ii)
End-user is to download the exact version of Data ONTAP from support site to the Webserver’s root directory.
(iii)
2
Follow procedure (A), (B) and (C) in the order listed below:
A. Download 'Netboot' and 'Software' images to the "source" HTTP server
1)
Example of images: 832RC2_q_netboot.tgz and 832RC2_q_image.tgz (approx size ~300-600 MB)
*If the End-User needs assistance in locating the proper images from the NetApp Support Site,
contact
NGS
.
2)
(2)
You may need to start or restart the HTTP Service on the "source" HTTP server.
B. Configure the local interface "e0M" on the target controller
1
Attach to the console port of the TARGET node. Capture the session log file.
2
Next configure the 'e0M' port on the TARGET controller - It must have an active network cable installed.
3
If site using a DHCP server, enter :
ifconfig e0M -auto
at the LOADER prompt and skip to step 3b.
a)
b)
Page 15 of 25
FAS2500 Model : Prepare and Start the Netboot Process
Action Description
End user to download two DOT 8.x images - "Netboot image"
(<version>_q_netboot.tgz)
and "Software image"
(<version>_q_image.tgz)
for your system model and ONTAP version- from the "NetApp Support Site" to the http root folder
of the HTTP server. See the below table for the list of images.
End-user is to provide the
e0M
port IP address, the netmask for the network and a gateway IP if one is needed to configure
the
TARGET
controller
e0M
port.
Test connectivity to the HTTP server using the command:
ping <HTTP-server-IP
OR
HTTP_server_name if "dns" options were set>
If ping doesn't work,
recheck ifconfig settings and make sure the interface you configured is not on a private network or VLAN.
STOP!
and
READ
Table-3 on page 17 describes the procedures to be followed based on system configuration and status.
You may experience a service outage during a Disruptive procedure, even using it with a system in an HA
configuration.
Call
NGS if you have questions.
Note:
Other parameters such as
dns_addr, dns_domain
might be necessary for your interface.
Ex:
ifconfig e0M -addr=e0M_IP -mask=netmask -gw=gateway -dns=dns_addr -domain=dns_domain
"dns_addr"
is the IP address of a name server on your network.
"dns_domain"
is the DNS domain name.
On the "source" HTTP server, extract the contents of the 'netboot.tgz' file to the target directory by using the following
methods:
(i)
For Unix based system, extract the 'netboot.tgz file' using the command :
'tar -zxvf <version>_q_netboot.tgz'
(ii)
For Windows system, extract the 'netboot.tgz file' using
7-Zip
.
(
WinZip
does not extract the binary properly.)
Once step 2 is completed,
(1)
The target directory on the "source" HTTP server should contain the
'<version>_q_image.tgz'
file and the
'netboot'
directory.
Otherwise use the end--user provided e0M IP, netmask and/or gateway info to configure the e0M interface:
Enter:
ifconfig e0M -addr=<target-e0M_IP> -mask=<netmask> -gw=<gateway>
NOTE
LOADER-A>
ifconfig e0M -addr=10.61.83.35 -mask=255.255.255.0 -gw=10.61.83.1
Device e0M:
hwaddr 00-A0-98-73-59-2A, ipaddr 10.61.83.35, mask 255.255.255.0
gateway 10.61.83.1, nameserver not set
speed 1000 full duplex, loopback not supported
LOADER-A
LOADER-A>
ping 10.61.69.167
10.61.69.167 (10.61.69.167)
is alive
10.61.69.167 (10.61.69.167): 1 packets sent, 1 received
EXAMPLE:
Sample ifconfig using 'e0M' (
gw=gateway IP optional
)
NOTE:
"source_ip" is the HTTP server IP
serving the netboot and DOT image file
Boot Device Replacement for the FAS2500
For NetApp Authorized Service Engineers
