H3C MSR Series User manual

H3C MSR Series Routers
OAP/OAPS V2 Module Customization User Guide
Hangzhou H3C Technologies Co., Ltd.
http://www.h3c.com
Document version: 6PW101-20120619

Copyright © 2011-2012, Hangzhou H3C Technologies Co., Ltd. and its licensors
All rights reserved
No part of this manual may be reproduced or transmitted in any form or by any means without prior
written consent of Hangzhou H3C Technologies Co., Ltd.
Trademarks
H3C, , Aolynk, , H3Care,
, TOP G, , IRF, NetPilot, Neocean, NeoVTL,
SecPro, SecPoint, SecEngine, SecPath, Comware, Secware, Storware, NQA, VVG, V2G, VnG, PSPT,
XGbus, N-Bus, TiGem, InnoVision and HUASAN are trademarks of Hangzhou H3C Technologies Co.,
Ltd.
All other trademarks that may be mentioned in this manual are the property of their respective owners
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Environmental protection
This product has been designed to comply with the environmental protection requirements. The storage,
use, and disposal of this product must meet the applicable national laws and regulations.

Preface
The H3C MSR Series Routesr OAP/OAPS V2 Module Customization User Guide describes hardware
specifications of OAP/OAPS V2 modules, configuration procedures for customizing the OAP/OAPS V2
modules, and how to install the operating system of an OAP/OAPS V2 module.
This preface includes:
•Audience
•Conventions
•About the H3C MSR documentation set
•Obtaining documentation
•Technical support
•Documentation feedback
Audience
This documentation is intended for:
•Network planners
•Field technical support and servicing engineers
•Network administrators working with the OAP/OAPS V2
Conventions
This section describes the conventions used in this documentation set.
Command conventions
Convention Descri
p
tion
Boldface Bold text represents commands and keywords that you enter literally as shown.
Italic Italic text represents arguments that you replace with actual values.
[ ] Square brackets enclose syntax choices (keywords or arguments) that are optional.
{ x | y | ... }
Braces enclose a set of required syntax choices separated by vertical bars, from which
you select one.
[ x | y | ... ]
Square brackets enclose a set of optional syntax choices separated by vertical bars, from
which you select one or none.
{ x | y | ... } *
Asterisk marked braces enclose a set of required syntax choices separated by vertical
bars, from which you select at least one.
[ x | y | ... ] *
Asterisk marked square brackets enclose optional syntax choices separated by vertical
bars, from which you select one choice, multiple choices, or none.
&<1-n> The argument or keyword and argument combination before the ampersand (&) sign can
be entered 1 to n times.
# A line that starts with a pound (#) sign is comments.

Symbols
Convention Descri
p
tion
WARNING An alert that calls attention to important information that if not understood or followed can
result in personal injury.
CAUTION An alert that calls attention to important information that if not understood or followed can
result in data loss, data corruption, or damage to hardware or software.
IMPORTANT An alert that calls attention to essential information.
NOTE An alert that contains additional or supplementary information.
TIP An alert that provides helpful information.
Network topology icons
Represents a generic network device, such as a router, switch, or firewall.
Represents a routing-capable device, such as a router or Layer 3 switch.
Represents a generic switch, such as a Layer 2 or Layer 3 switch, or a router that supports
Layer 2 forwarding and other Layer 2 features.
Represents an MSR router that has an OAP/OAPS V2 module installed.
Port numbering in examples
The port numbers in this document are for illustration only and might be unavailable on your device.
About the H3C MSR documentation set
The H3C MSR documentation set includes:
Cate
g
or
y
Documents Pur
p
oses
Product description and
specifications
MSR 900 Routers
Marketing brochures
Describe product specifications and benefits.
MSR 20-1X Routers
Marketing brochures
MSR 20-2X[40] Routers
Marketing brochures
MSR 30 Routers
Marketing brochures
MSR 50-40[60] Routers
Marketing brochures
Hardware specifications
and installation
MSR 900 Routers
Installation guide Provides a complete guide to hardware installation
and hardware specifications.
MSR 20-1X Routers
Installation guide

MSR 20-2X[40] Routers
Installation guide
MSR 30 Routers
Installation guide
MSR 50 Routers
Installation guide
MSR Series Routers
Interface Module Manual
Software configuration
MSR Series Routers
Configuration guides
Describe software features and configuration
procedures.
MSR Series Routers
Command references
Provide a quick reference to all available
commands.
MSR Series Routers Web
Configuration guides
Describe Web software features and configuration
procedures.
Operations and
maintenance
MSR Basic Series Routers
Release notes
Provide information about the product release,
including the version history, hardware and software
compatibility matrix, version upgrade information,
technical support information, and software
upgrading.
MSR Standard Series
Routers Release notes
Obtaining documentation
You can access the most up-to-date H3C product documentation on the World Wide Web
at http://www.h3c.com.
Click the links on the top navigation bar to obtain different categories of product documentation:
[Technical Support & Documents > Technical Documents] – Provides hardware installation, software
upgrading, and software feature configuration and maintenance documentation.
[Products & Solutions] – Provides information about products and technologies, as well as solutions.
[Technical Support & Documents > Software Download] – Provides the documentation released with the
software version.
Technical support
[e-mail]
http://www.h3c.com
Documentation feedback
You can e-mail your comments about product documentation to [e-mail].
We appreciate your comments.

i
Contents
OAP/OAPS module customization····························································································································· 1
Overview············································································································································································1
Boot options·······································································································································································1
Entering the BIOS menu···········································································································································1
Operating system boot options·······························································································································3
Installing a Linux operating system··································································································································3
Preparing for installation ·········································································································································3
Installation procedures·············································································································································5
Linux operating system·············································································································································8
Installing a Windows operating system··························································································································9
Automatically installing Windows XP Professional by booting from network····················································9
Installing Windows 7 Ultimate or Windows Server 2008 R2 by booting from USB disk ···························· 15
Customization based on a Linux operating system ···································································································· 16
Compiling the Linux kernel and OAP/OAPS module ······················································································· 16
Configuring Grub·················································································································································· 17
Installing the Ethernet port driver ························································································································· 18
Customization based on a Windows operating system ···························································································· 18
Logging in to Windows ········································································································································ 19
Customization guidelines······································································································································ 19
Appendix OAP/OAPS module hardware features ·································································································20

1
OAP/OAPS module customization
Overview
A Linux operating system and Windows operating system run separately on an OAP/OAPS module. You
can configure the system and services, and customize the Linux and Windows operating systems as you
do on a PC.
Boot options
Entering the BIOS menu
You can select to enter the BIOS menu to change the current system boot mode when the OAP/OAPS
module boots.
To enter the BIOS menu:
1. After the router is booted normally, reset the OAP/OAPS module by executing the oap reboot slot
slot-number command, where slot-number represents the slot where the OAP/OAPS module
resides. Then execute the oap connect slot slot-number command to log in to the OAP/OAPS
module.
NOTE:
•You can press Ctrl + D to enter the BIOS menu to select the boot mode after the OAP/OAPS module is
reset. If you do not perform any operation within five seconds after the OAP/OAPS module is reset, the
OAP/OAPS module is booted from harddisk.
•You must close the Linux operating system running on the OAP/OAPS module before executing the oap
reboot slot slot-number command. To do so, execute the poweroff command in the Linux operating
system, or press the power button on the panel of the OAP/OAPS module to turn off the module. When
the SYS LED is off, the Linux operating system running on the OAP/OAPS module is off.
<H3C>oap reboot slot 10
This command will recover the OAP from shutdown or other failed state.
Warning: This command may lose the data on the hard disk if the OAP is not being
shut down! Continue? [Y/N]:y
Reboot OAP by command.
<H3C>oap connect slot 10
Press CTRL+K to quit.
Connected to OAP!
Yukon PXE v6.71.2.3 (20110228)
(C)Copyright 2003-2011 Marvell(R). All rights reserved.
Pre-boot eXecution Environment (PXE) v2.1
(C)Copyright 1997-2000 Intel Corporation.
Initializing Intel(R) Boot Agent GE v1.3.65
PXE 2.1 Build 089 (WfM 2.0)

2
Test ALL Memory? Yes or No (Y/N)
*******************************************************
* *
* BIOS , Ver 1.00 *
* *
*******************************************************
Compiled date : May 09 2011, 17:08:34
CPU Type : Intel(R) Atom(TM) CPU N450 @ 1.66GHz
CPU L1 Cache : 24KB
CPU L2 Cache : 512KB
CPU Clock Speed : 1666MHZ
Memory Type : DDR2 SDRAM
Memory Size : 1024MB
Memory Speed : 667MHZ
BIOS Size : 8192KB
NAND Flash Size : 524MB
Hard Disk Size : 500.1GB
Press Ctrl+D to enter BIOS Menu...
2. Press Ctrl + D at the prompt to enter the BIOS menu.
The system provides the following BIOS boot options:
===============<BIOS-BASIC MENU(Ver 1.00)>====================
| <1> Boot from NAND Flash |
| <2> Boot from Hard Disk |
| <3> Boot from USB |
| <4> Boot from Ethernet |
| <5> Default boot device |
| <0> Reboot |
==============================================================
Enter your choice(0-5):
Table 1 BIOS boot options
O
p
tion Descri
p
tion
<1> Boot from NAND Flash Boot from the NAND Flash.
<2> Boot from Hard Disk For a FIC-OAP module, the option allows you to enter the submenu.
<3> Boot from USB Boot from the USB.
<4> Boot from Ethernet Boot from the Ethernet port. After you select this option, you enter the
submenu.
<5> Default boot device Set the default boot device.
<0> Reboot Reboot the OAP/OAPS module

3
Operating system boot options
The OAP/OAPS module has two storage media: NAND Flash and harddisk. The NAND Flash provides
the diagnosing and one-key recover functions, and the harddisk allows you to customize the OAP/OAPS
module.
If you select to boot from the harddisk on the BIOS menu, the system displays an operating system boot
option. The following describes a Linux operating system.
+--------------------------------------------------------------+
| CentOS (2.6.18-164.el5) |
| |
| |
| |
| |
| |
+--------------------------------------------------------------+
If you select to boot from the NAND Flash, the system displays the linux-ramdisk and linux-recover boot
options. The system supports both Grub and Lilo as the bootloader, and boots using Grub by default. To
diagnose hardware failure, select linux-ramdisk. To recover the failed operating system or restore the
operating system to factory defaults, select linux-recovery.
+--------------------------------------------------------------+
| linux-ramdisk |
| linux-recovery |
| |
| |
| |
| |
+--------------------------------------------------------------+
Select a boot option as needed, and then press Enter.
CAUTION:
The linux-recovery option takes effect only when the harddisk is installed with a Linux operatin
g
system.
W
hen you select this option, all the data on the operating system is lost.
Installing a Linux operating system
This task allows you to install or upgrade a Linux operating system.
The operating system installation procedures are the same for the MIM-OAPS, MIM-OAP, and FIC-OAP
modules. The following uses a MIM-OAPS as an example.
Preparing for installation
Hardware requirements
Table 2 Hardware requirements
Item Quantit
y
Remarks
PC 1 Operates as a console to log in to the router

4
Item Quantit
y
Remarks
Linux server 1
Provides DHCP and TFTP functions:
•The IP address must be 192.168.0.2.
•The DHCP and TFTP functions have been enabled.
MSR router 1 Installed with an OAP/OAPS module
Network cable and
console cable As required Connect the PC, Linux server, router, and OAP/OAPS module
Software requirements
Obtain the OAP/OAPS software from the H3C website or from the H3C technical support. The software
is a compressed file package named MSR_ICG-MOAPSV2-A5XXX.zip, which contains the following
files:
Table 3 Software requirements
File Descri
p
tion
pxelinux.cfg\default Configuration file
dhcpd.conf DHCP configuration file
hd-mim-oaps-v2-centos.tar.gz Linux operating system installation file
hd-mim-oaps-v2-centos.tar.gz.md5 MD5 file
oapv2-initrd-2.6.18-164.el5-install.img Linux Initrd file
oapv2-vmlinuz-2.6.18-164.el5 Linux kernel file
pxelinux.0 Configuration file
self_install.sh Installation script file
tftp TFTP configuration file
Copy the files needed to the corresponding directories on the Linux server:
•Copy the tftp file to the Linux server/etc/xinetd.d directory to overwrite the tftp file in this directory,
and reboot the TFTP server.
•Copy the dhcpd.conf file to the Linux server/etc directory to overwrite the dhcpd.conf file in this
directory, and reboot the DHCP server.
•Copy the other files to the Linux server/tftpboot directory.
Setting up a configuration environment
As shown in Figure 1, connect the PC to the console port on the router with a console cable, and connect
the Ethernet port on the OAP/OAPS module to the Ethernet port on the Linux server.
Figure 1 Set up a configuration environment

5
Installation procedures
To install a Linux operating system:
1. After the router is booted normally, execute the oap reboot slot slot-number command to reset the
OAP/OAPS module. slot-number represents the slot where the OAP/OAPS module resides. Then
execute the oap connect slot slot-number command to log in to the OAP/OAPS module.
NOTE:
•You can press Ctrl + D to enter the BIOS menu to select the boot mode after the OAP/OAPS module is
reset. If you do not perform any operation within five seconds after the OAP/OAPS module is reset, the
OAP/OAPS module is booted from harddisk.
•You must close the Linux operating system running on the OAP/OAPS module before executing the oap
reboot slot slot-number command. To do so, execute the poweroff command in the Linux operating
system, or press the power button on the panel of the OAP/OAPS module to turn off the module. When
the SYS LED is off, the Linux operating system running on the OAP/OAPS module is off.
<H3C>oap reboot slot 10
This command will recover the OAP from shutdown or other failed state.
Warning: This command may lose the data on the hard disk if the OAP is not being
shut down! Continue? [Y/N]:y
Reboot OAP by command.
<H3C>oap connect slot 10
Press CTRL+K to quit.
Connected to OAP!
Yukon PXE v6.71.2.3 (20110228)
(C)Copyright 2003-2011 Marvell(R). All rights reserved.
Pre-boot eXecution Environment (PXE) v2.1
(C)Copyright 1997-2000 Intel Corporation.
Initializing Intel(R) Boot Agent GE v1.3.65
PXE 2.1 Build 089 (WfM 2.0)
Test ALL Memory? Yes or No (Y/N)
*******************************************************
* *
* BIOS , Ver 1.00 *
* *
*******************************************************
Compiled date : May 09 2011, 17:08:34
CPU Type : Intel(R) Atom(TM) CPU N450 @ 1.66GHz
CPU L1 Cache : 24KB
CPU L2 Cache : 512KB
CPU Clock Speed : 1666MHZ
Memory Type : DDR2 SDRAM
Memory Size : 1024MB
Memory Speed : 667MHZ
BIOS Size : 8192KB
NAND Flash Size : 524MB

6
Hard Disk Size : 500.1GB
Press Ctrl+D to enter BIOS Menu...
2. Press Ctrl + D at the prompt to enter the BIOS menu.
===============<BIOS-BASIC MENU(Ver 1.00)>====================
| <1> Boot from NAND Flash |
| <2> Boot from Hard Disk |
| <3> Boot from USB |
| <4> Boot from Ethernet |
| <5> Default boot device |
| <0> Reboot |
==============================================================
Enter your choice(0-5):
3. Select 4to enter the submenu.
Enter your choice(0-5):4
===============<NETWORK BOOT DEVICE MENU>=====================
| <1> Eth0 |
| <2> Eth1 |
| <0> Exit |
==============================================================
Enter your choice(0-2):
4. Select 2to start network installation.
Enter your choice(0-2):2
Reading boot sector...Done
Switching to boot loader
…
udhcpc (v1.17.3) started
Setting IP address 0.0.0.0 on eth1
Sending discover...
Sending discover...
Sending select for 192.168.0.250...
Lease of 192.168.0.250 obtained, lease time 21600
Setting IP address 192.168.0.250 on eth1
Recreating /etc/resolv.conf
Please press Enter to activate this console.
5. Press Enter at the prompt.
BusyBox v1.17.3 (2011-02-12 09:08:53 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
/ #
6. Execute the pxe_install mim-oaps-v2 all command to start installing the software.
Use the pxe_install mim-oap-v2 all command for a MIM-OAP module. Use the pxe_install
fic-oap-v2 all command for a FIC-OAP module.
[root@localhost /root]#pxe_install mim-oaps-v2 all
Adjust system time...Ok
Get install script file...Ok

7
Start to execute install script file...
Check for install...Ok
Fdisk hard disk...Ok
Make hard disk file system...Ok
Mount hard disk...Ok
Get hd-mim-oaps-v2-centos.tar.gz file...Ok
Decompressing hd-mim-oaps-v2-centos.tar.gz file...
decompress alt.tar.gz ok
decompress bin.tar.gz ok
decompress boot.tar.gz ok
decompress dev.tar.gz ok
decompress etc.tar.gz ok
decompress home.tar.gz ok
decompress lib.tar.gz ok
decompress lib64.tar.gz ok
decompress media.tar.gz ok
decompress misc.tar.gz ok
decompress mnt.tar.gz ok
decompress opt.tar.gz ok
decompress proc.tar.gz ok
decompress root.tar.gz ok
decompress sbin.tar.gz ok
decompress selinux.tar.gz ok
decompress srv.tar.gz ok
decompress sys.tar.gz ok
decompress tmp.tar.gz ok
decompress usr.tar.gz ok
decompress var.tar.gz ok
Mount nandflash...Ok
Create grub conf file...Ok
Update grub...Ok
OAP install completed
7. Reboot the OAP/OAPS module until the operating system is started.
CentOS release 5.4 (Final)
Kernel 2.6.18-164.el5 on an x86_64
localhost login:
8. Enter the username and password root to log in to the operating system.
localhost login: root
Password:
Last login: Fri May 20 16:38:18 on ttyS0
[root@localhost ~]#
9. Execute the poweroff command. Power off the router at the prompt acpi_power_off called.
[root@localhost ~]# poweroff
Broadcast message from root Stopping sshd: [ OK ]
Stopping acseic-daemon: [ OK ]
Shutting down SMB services: [ OK ]

8
Shutting down NMB services: [ OK ]
Stopping snmpd: [ OK ]
Stopping xinetd: [ OK ]
Stopping acpi daemon: [ OK ]
Shutting down kernel logger: [ OK ]
Shutting down system logger: [ OK ]
Shutting down interface eth0: eth0: network connection down
[ OK ]
Shutting down interface eth1: [ OK ]
Shutting down loopback interface: [ OK ]
Starting killall: [ OK ]
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Saving random seed:
Syncing hardware clock to system time
Turning off quotas:
Unmounting file systems:
Halting system...
md: stopping all md devices.
Synchronizing SCSI cache for disk sda:
sd 0:0:0:0: [sda] Stopping disk
ACPI: PCI interrupt for device 0000:02:00.0 disabled
ACPI: PCI interrupt for device 0000:01:00.0 disabled
Power down.
acpi_power_off called
Linux operating system
After the Linux operating system is installed, the device boots from the harddisk when powered on next
time. The Linux operating system provides a complete root file system and customization tools such as gcc,
rpm, and vi editor, and is also enabled with some network services such as smb. You can configure the
network services on the OAP/OAPS module as you do on a PC. Table 4 describes the harddisk partitions
when the device is shipped.
Table 4 Harddisk partitions
Module Partition Mount
p
oint File s
y
stem Descri
p
tion
MIM-OAPS/MIM-OAP
/dev/sda1 / ext3 Root file system
/dev/sda2 /alt ext3
Backup partition for the root
file system, used for one key
restore.
/dev/sda3 swap swap Switching partition
/dev/sda4 /opt ext3 Data partition
FIC-OAP
/dev/md0 / ext3 (RAID1) Root file system
/dev/md1 /alt ext3 (RAID1)
Backup partition for the root
file system, used for one key
restore.
/dev/md2 swap Swap (RAID1) Switching partition

9
Module Partition Mount
p
oint File s
y
stem Descri
p
tion
Reserved Data partition
Installing a Windows operating system
The OAP/OAPS module does not have a human machine interface (HMI), so the Windows software
version must meet the following requirements:
•Supports automatic installation
•Supports Remote Desktop.
This section describes how to install Windows XP Professional and Windows 7 Ultimate and Windows
Server 2008 R2.
Automatically installing Windows XP Professional by booting
from network
Preparing for installation
Table 5 Hardware requirements
Item Quantit
y
Remarks
PC 1
Operates as a DHCP and TFTP server that has an IP address
of 192.168.0.24 in the example.
MSR router 1 Installed with an OAP/OAPS module.
Network cable/console
cable As required Connect the PC, router, and OAP/OAPS module
Table 6 Software requirements
File Descri
p
tion
Windows XP Professional CD and sequence number Operating system file
Marvell 88E8070 driver
For the internal Ethernet interface on the
MIM-OAPS/MIM-OAP module. It can be obtained
through http://www.marvell.com/support/downloads
/driverDownload.do?driverId=175&action=1
Intel 82574 drivers
For the external Ethernet port on the
MIM-OAPS/MIM-OAP module and internal Ethernet
interface on the FIC-OAP module. You need to
download the driver corresponding to your Windows
XP Professional operating system.
ris-linux-0.4.tar.gz A daemon that provides the BINL service
python-2.5.1.msi Windows XP installer for python
WindowsXP-KB838080-SP2-DeployTools-CHS.cab Windows deployment tools
tftpd32.rar TFTP server and DHCP server tools
firstrun.bat Used to start the remote desktop

10
Configuring the software
To configure the software:
1. Create the sub folder tftpboot in the root directory of disk D on your PC.
2. Copy files NTDETECT.COM, NTLDR, and STARTROM.N1_ on the Windows XP Professional
installation CD to the tftpboot directory, change STARTROM.N1_ to STARTROM.CAB, and copy the
decompressed file STARTROM.N12 to the tftpboot directory.
3. Create the configuration file winnt.sif according to the ref.chm file decompressed from
WindowsXP-KB838080-SP2-DeployTools-CHS.cab, and save it to the tftpboot directory.
The configuration file winnt.sif on the MIM-OAP/FIC-OAP module contains the following contents:
;SetupMgrTag
[Data]
AutomaticUpdates=1
AutoPartition=1
MsDosInitiated="1"
UnattendedInstall="Yes"
floppyless="1"
OriSrc="\\192.168.0.24\tftpboot\boot\I386"
OriTyp="4"
LocalSourceOnCD=1
[SetupData]
OsLoadOptions="/noguiboot /fastdetect"
SetupSourceDevice="\Device\LanmanRedirector\192.168.0.24\tftpboot\boot"
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=YES
TargetPath=\WINDOWS
FileSystem=LeaveAlone
NtUpgrade=No
OverwriteOemFilesOnUpgrade=No
UpdateInstalledDrivers=Yes
DriverSigningPolicy=Ignore
OEMPnPDriversPath="PnPDrvrs\Disk;PnPDrvrs\Net"
UnattendSwitch=Yes
[GuiUnattended]
AdminPassword="admin"
EncryptedAdminPassword=NO
AutoLogon=Yes
OEMSkipRegional=1
TimeZone=210
OemSkipWelcome=1
[Display]
BitsPerPel=32

11
Vrefresh=75
Xresolution=1024
Yresolution=768
[MassStorageDrivers]
"Intel(R) 5 Series 4 Port SATA AHCI Controller"="OEM"
[OEMBootFiles]
iaAHCI.cat
iaAHCI.inf
iaStor.sys
TxtSetup.oem
[UserData]
ProductKey="DG8FV-B9TKY-FRT9J-6CRCC-XPQ4G"
FullName="h3c"
OrgName="h3c"
ComputerName="ArranDemo"
[TapiLocation]
CountryCode=86
[RegionalSettings]
LanguageGroup=10
[SetupMgr]
DistFolder=C:\windist
DistShare=windist
[Identification]
JoinDomain=MYDOMAIN
DoOldStyleDomainJoin=Yes
[Networking]
InstallDefaultComponents=Yes
ProcessPageSections=Yes
[RemoteInstall]
Repartition=Yes
[Components]
IEAccess = Off
OEAccess = Off
WMAccess = Off
WMPOCM = Off
[GuiRunOnce]

12
"C:\Hotfixes\firstrun.bat"
[OSChooser]
Description="Windows Professional"—Standard Installation
Help="This will install Windows Professional in a standard configuration."
LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
ImageType=Flat
The configuration file winnt.sif on the MIM-OAPS module contains the following contents:
;SetupMgrTag
[Data]
AutomaticUpdates=1
AutoPartition=1
MsDosInitiated="1"
UnattendedInstall="Yes"
floppyless="1"
OriSrc="\\192.168.0.24\tftpboot\boot\I386"
OriTyp="4"
LocalSourceOnCD=1
[SetupData]
OsLoadOptions="/noguiboot /fastdetect"
SetupSourceDevice="\Device\LanmanRedirector\192.168.0.24\tftpboot\boot"
[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=YES
TargetPath=\WINDOWS
FileSystem=LeaveAlone
NtUpgrade=No
OverwriteOemFilesOnUpgrade=No
UpdateInstalledDrivers=Yes
DriverSigningPolicy=Ignore
OEMPnPDriversPath="PnPDrvrs\Disk;PnPDrvrs\Net"
UnattendSwitch=Yes
[GuiUnattended]
AdminPassword="admin"
EncryptedAdminPassword=NO
AutoLogon=Yes
OEMSkipRegional=1
TimeZone=210
OemSkipWelcome=1
[Display]
BitsPerPel=32
Vrefresh=75
Xresolution=1024

13
Yresolution=768
[MassStorageDrivers]
"Intel(R) ICH8M-E/M SATA AHCI Controller"="OEM"
[OEMBootFiles]
iaAHCI.cat
iaAHCI.inf
iaStor.sys
TxtSetup.oem
[UserData]
ProductKey="DG8FV-B9TKY-FRT9J-6CRCC-XPQ4G"
FullName="h3c"
OrgName="h3c"
ComputerName="ArranDemo"
[TapiLocation]
CountryCode=86
[RegionalSettings]
LanguageGroup=10
[SetupMgr]
DistFolder=C:\windist
DistShare=windist
[Identification]
JoinDomain=MYDOMAIN
DoOldStyleDomainJoin=Yes
[Networking]
InstallDefaultComponents=Yes
ProcessPageSections=Yes
[RemoteInstall]
Repartition=Yes
[Components]
IEAccess = Off
OEAccess = Off
WMAccess = Off
WMPOCM = Off
[GuiRunOnce]
"C:\Hotfixes\firstrun.bat"

14
[OSChooser]
Description="Windows Professional—Standard Installation"
Help=" This will install Windows Professional in a standard configuration."
LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"
ImageType=Flat
4. Create the boot sub directory in the tftpboot directory, copy the directories I386 and $OEM$ on
the Windows XP CD to the boot directory, and decompress the driver.cab file in I386 to the I386
directory.
5. Decompress Intel 82574, and copy the decompressed files e1q5132.cat, e1q5132.din,
e1q5132.inf, e1q5132.sys, e1qmsg.dll, nicco2.dll, and NicInstQ.dll and the Mavell 88E8070
driver to the directories \boot, \boot\I386, and \boot\$OEM$\$1\PnPDrvrs\Net. You must
manually create these directories and make sure the parameter settings are the same as those in
winnt.sif.
6. Create the sub directory \$OEM$\$1\Hotfixes in the tftpboot\boot directory, and copy the
firstrun.bat file to this sub directory. The firstrun.bat file is automatically executed for only once at
device startup.
7. Install python-2.5.1.msi on the PC so that the PC can support the python function.
8. Decompress ris-linux-0.4.tar.gz to D:\tftpboot\ris-linux-0.4, enter DOS mode to execute
the .\infparser.py D:\tftpboot\boot command in D:\tftpboot\ris-linux-0.4 to generate the
network interface card configuration file, and execute the .\binlsrv.py command to start the BINL
service.
9. Share the D:\tftpboot directory, with the share name tftpboot, and add Everyone and Anonymous;
enable the guest user, and leave the password blank; select Start > Control Panel > Management
Tools > Local Security Policy, expand Local Policies, click User Rights Assignment, click Deny
access to this computer from the network, and delete the guest user; select Control Panel >
Management Tools > Local Security Policy, expand Local Policies, click Security Options, enable
Let Everyone permissions apply to anonymous users; click Shares that can be accessed
anonymously, and add D:\tftpboot.
10. Enable the TFTP server and DHCP server functions. The TFTP server file is saved in the D:\tftpboot
directory, and the boot file is saved in STARTROM.N12.
Setting up a configuration environment
As shown in Figure 2, connect the PC to the console port on the router with a console cable, and to the
Ethernet port on the OAP/OAPS module through a network cable.
Figure 2 Set up a configuration environment
Router + OAP/OAPS
module
PC
192.168.0.24
Console cable
Network cable
Installation procedure
To install the Windows XP Professional operating system:
1. Follow the installation steps 1, 2, 3, and 4 in Installation procedures to boot from network. About
30 minutes later, the installation procedure is complete.