Symantec 10521148 Implementation Guide - Page 184

Connecting the Imaging Server to the appliance, On the 7120

Page 184 highlights

176 Re-imaging and unconfiguring Setting up an Imaging Server 5 The scripts checks that the dhcp, nfs, xinetd, and mknbi RPMs are installed. If one or more are not installed, it prompts you with the message: Please go install RPM from /mnt/cdrom/home/bto/tools. 6 To install a missing RPM, use the following commands: cd tools ls rpm -i where is the file name of the RPM to install. 7 If more RPMs need to be installed, repeat the command: rpm -i where is the file name of the next RPM to install. 8 When all RPMs are installed, type these two commands to run the script again: cd /mnt/cdrom/home/bto ./install-bto 9 The script copies the following files from the CD into these locations: /etc/dhcpd.conf /etc/xinetd.d/tftp 10 The script starts the dhcpd, xinetd, and nfs services that will be needed during imaging. 11 The script copies all files from /mnt/cdrom/home/bto into the /home/bto directory on the Imaging Server. The Imaging Server is now ready to image an appliance. Connecting the Imaging Server to the appliance On the 7120, you can use the provided 10/100 Base-T crossover cable to connect the Imaging Server directly to your appliance, or you can connect through a hub or switch using two regular Ethernet cables. On the 7160 or 7161, the interfaces used for imaging will automatically sense whether a crossover or regular connection is needed, and will handle either. You do not need to use a crossover cable for these appliance models. Port 0 on the 7161 is a fiber interface rather than a copper one. You will need to use a media converter unless the interface on the Imaging Server is fiber as well. See the following sections: ■ Connecting the Imaging Server to a 7120 ■ Connecting the Imaging Server to a 7160 ■ Connecting the Imaging Server to a 7161

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214

176
Re-imaging and unconfiguring
Setting up an Imaging Server
5
The scripts checks that the dhcp, nfs, xinetd, and mknbi RPMs are installed.
If one or more are not installed, it prompts you with the message:
Please go install <rpm name> RPM from /mnt/cdrom/home/bto/tools.
6
To install a missing RPM, use the following commands:
cd tools
ls
rpm -i <rpm file name>
where
<rpm file name>
is the file name of the RPM to install.
7
If more RPMs need to be installed, repeat the command:
rpm -i <rpm file name>
where
<rpm file name>
is the file name of the next RPM to install.
8
When all RPMs are installed, type these two commands to run the script
again:
cd /mnt/cdrom/home/bto
./install-bto
9
The script copies the following files from the CD into these locations:
/etc/dhcpd.conf
/etc/xinetd.d/tftp
10
The script starts the dhcpd, xinetd, and nfs services that will be needed
during imaging.
11
The script copies all files from /mnt/cdrom/home/bto into the /home/bto
directory on the Imaging Server.
The Imaging Server is now ready to image an appliance.
Connecting the Imaging Server to the appliance
On the 7120, you can use the provided 10/100 Base-T crossover cable to connect
the Imaging Server directly to your appliance, or you can connect through a hub
or switch using two regular Ethernet cables.
On the 7160 or 7161, the interfaces used for imaging will automatically sense
whether a crossover or regular connection is needed, and will handle either. You
do not need to use a crossover cable for these appliance models.
Port 0 on the 7161 is a fiber interface rather than a copper one. You will need to
use a media converter unless the interface on the Imaging Server is fiber as well.
See the following sections:
Connecting the Imaging Server to a 7120
Connecting the Imaging Server to a 7160
Connecting the Imaging Server to a 7161