Motorola
1303 E. Algonquin Rd.
Schaumburg, IL
60196 USA
www.motorola.com/mesh
847-576-5000
Version 1A
September 2008
This page intentionally left blank.
ii
Copyrights
The Motorola products described in this document may include copyrighted Motorola computer programs. Laws in the
United States and other countries reserve for Motorola certain exclusive rights for copyrighted computer programs.
Accordingly, any copyrighted Motorola computer programs contained in the Motorola products described in this
document may not be copied or reproduced in any manner without the express written permission of Motorola.
Furthermore, the purchase of Motorola products shall not be deemed to grant either directly or by implication,
estoppels or otherwise, any license under the copyrights, patents or patent applications of Motorola, except for the
normal nonexclusive, royalty-free license to use that arises by operation of law in the sale of a product.
Disclaimer
Please note that certain features, facilities and capabilities described in this document may not be applicable to or
licensed for use on a particular system, or may be dependent upon the characteristics of a particular mobile
subscriber unit or configuration of certain parameters. Please refer to your Motorola contact for further information.
Trademarks
Motorola, the Motorola logo, and all other trademarks identified as such herein are trademarks of Motorola, Inc. All
other product or service names are the property of their respective owners.
Procedure 9-1 Enabling IP Directed Broadcast...................................................................................9-1
xiii
This page intentionally left blank.
xiv
Chapter 1: System Overview
Chapter 1: System Overview
.............................................
.
.
Motorola’s MOTOMESH Duo is a high performance, 802.11 a/b/g meshed Wi-Fi solution
designed to meet strict cost per square mile and ROI targets. MOTOMESH Duo is part of the
MOTO wi4™ portfolio of broadband wireless access technologies, and delivers a new level of
economic flexibility and investment protection to municipalities and service providers.
MOTOMESH Duo leverages Motorola’s field proven, MeshConnex™ routing engine and One
Point Wireless Management™ system to meet the challenges of demanding multi-use
networks. Its small size, minimal visual impact and low power consumption increases
mounting location flexibility and enables rapid deployment. MOTOMESH Duo devices are
available in three different radio configurations:
Chapter
1
• 2.4 / 5.4 GHz (single mesh)
• 2.4 / 5.8 GHz (single mesh)
• 2.4 / 4.9 GHz (dual mesh)
MOTOMESH Duo devices can be deployed in a variety of meshing configurations depending
on the radio configuration ordered:
•2.4 GHz client access / 2.4 GHz meshing – In this configuration the second radio is
disabled and the 2.4 GHz radio is used for client access and for inter-nodal meshing.
•2.4 GHz client access / 5.4 GHz meshing – In this configuration the 2.4 GHz radio
is used for client access and the 5.4 GHz radio is used for inter-nodal meshing.
•2.4 GHz client access / 5.8 GHz meshing – In this configuration the 2.4 GHz radio
is used for client access and the 5.8 GHz radio is used for inter-nodal meshing.
•2.4 GHz client access / 2.4 GHz meshing | 4.9 GHz client access / 4.9 GHz
meshing – In this configuration the 2.4 GHz radio is used for client access and inter-
nodal meshing. The 4.9 GHz radio is also used for 4.9 GHz client access and internodal meshing. This configuration is referred to as Dual Mesh.
MOTOMESH Duo devices can also be ordered in AC and DC versions.
1-1
Chapter 1: System Overview
All MOTOMESH Duo 2.1 Infrastructure Devices require professional
installation to ensure the installation is performed in accordance with
Motorola installation standards and that regulatory requirements are met.
MOTOMESH Duo 2.1 Network Components
.............................................
.
.
A MOTOMESH Duo 2.1 network is comprised of the following components.
• Intelligent Access Points (IAPs)
• Mesh Wireless Routers (MWRs)
• Supporting networking equipment
Intelligent Access Point
A MOTOMESH Duo device can function as an IAP (gateway) or an MWR. All MOTOMESH
Duo devices ship from the factory as IAPs. If an IAP does not detect a wired connection it
will convert to an MWR thus removing itself as a valid gateway to the wired network. This
prevents routing holes from forming in the network. IAPs (functioning as MWRs) will still
participate in the mesh and will forward traffic to an alternative IAPs (gateways). A node can
also be specifically set as an IAP or an MWR using the One Point Wireless Manager™
application or the device webpage.
Intelligent Access Points:
• Support 802.11 a/b/g Wi-Fi client access.
• Support all 802.11 client security methods (open, WEP, WPA/WPA2 RADIUS,
WPA/WPA2 PSK).
• Support 15 Virtual Access Points per radio for client access.
• Support Dynamic Route Selection via the MeshConnex™ routing engine.
• Support Automatic Load Balancing.
• Support 128bit AES encrypted Secure Mesh inter-nodal links.
• Are equipped with two Ethernet interfaces one of which can source standards
based 802.3af Power over Ethernet (PoE) (to power an external IP enabled
device such as a surveillance camera) or Canopy PoE to power Motorola
Canopy subscriber modules.
• Offer fast and easy deployment via a pivot mounting bracket.
• Designed with a rugged NEMA 4 outdoor enclosure.
1-2
Chapter 1: System Overview
With the addition of each IAP additional network capacity is added.
Mesh Wireless Router
When a MOTOMESH Duo device operates as a Mesh Wireless Router (MWR), its primary
function is to seed and extend the range between IAPs and wireless clients while
simultaneously increasing the spectral efficiency of the network.
Mesh Wireless Routers:
• Range extension for all other network devices.
• Support 802.11 a/b/g Wi-Fi client access.
• Support all 802.11 client security methods (open, WEP, WPA/WPA2 RADIUS,
WPA/WPA2 PSK).
• Support 15 Virtual Access Points per radio for client access.
• Support Dynamic Route Selection via the MeshConnex™ routing engine.
• Support Automatic Load Balancing.
• Support 128bit AES encrypted Secure Mesh inter-nodal links.
• Are equipped with two Ethernet interfaces one of which can source standards
based 802.3af Power over Ethernet (PoE) to power external IP enabled devices
such a surveillance camera. This allows a network of IP-enabled devices to be
directly addressed, accessed and managed over the network.
• Offer fast and easy deployment via a pivot mounting bracket.
• Designed with a rugged NEMA 4 outdoor enclosure.
Supporting Networking Equipment
Additional networking infrastructure is required to support a MotoMesh Duo network. This
includes an enterprise grade server to provide network services such as DHCP and DNS, as
well as host the MotoMesh Duo management software (One Point Wireless Manager™. A
RADIUS server may also be present. Switching and routing network equipment is also
required. Our small system reference design utilizes a single Layer 3 switch which provides
switching and routing within the same device.
1-3
Chapter 1: System Overview
Figure 1-1 2.4 / 5.8 GHz Mesh Network Example
Internet
Internet
RADIUS
Wireless Manager
Wireless Manager
RADIUS
Layer 3 Switch
Layer 3 Switch
Backend Network
Backend Network
2.4 GHz
2.4 GHz
Client
Client
Access
Access
5.8 GHz
5.8 GHz
Mesh
Mesh
MWR
MWR
IAP
IAP
2.4 GHz
2.4 GHz
Client
Client
Access
Access
5.8 GHz
5.8 GHz
Mesh
Mesh
MWR
MWR
5.8 GHz
5.8 GHz
Mesh
Mesh
MWR
MWR
2.4 GHz
2.4 GHz
Client
Client
Access
Access
1-4
Chapter 2: Network Setup
Chapter 2: Network Setup
.............................................
.
.
Small System Reference Design
This section details a small system reference design. By understanding the small reference
design one can apply these details to larger networks. A small system reference design is
defined as a network in which the network servers and associated networking hardware are
located at a central location. Wireless or wired bridging may be used to provide connectivity
between the Intelligent Access Points and the switch / router backend.
Chapter
2
Our small system reference design has the following attributes:
• Support for at least 20 IAPs (gateways).
• All IAPs and MWRs will utilize DHCP for network addressing.
• The Network will be configured and managed with the One Point Wireless
Manager™ application residing on a RedHat ES 4 Linux server.
• A Windows 2003 RADIUS server will provide authentication for Secure Mesh.
• The standard small network design does not include server or network hardware
redundancy.
Network Requirements
.............................................
.
Network Servers
There are two network servers used in the small system reference design. The following is
the recommended hardware configuration for these two servers. Variations from the
recommended hardware configuration may result in inadequate system performance.
•Enterprise grade server (e.g. Hewlett-Packard ProLiant DL360-G5 3.00GHz
Server)
• Minimum 2 GB of RAM
• (2) 36.4 GB 15K RPM SCSI Hard Disk Drives
2-5
Chapter 2: Network Setup
Figure 2-1 HP DL360 G5 server
• Monitor
• Keyboard
• Mouse
These requirements are an approximate estimate intended to allow for
maximum scalability while supporting rapid system response time. As a
minimum, we recommend 2 GB of system memory and redundant hard
drives with a hardware RAID controller of server quality.
One Point Wireless Manager Server
• The One Point Wireless Manager™ server in our reference design server hosts
the One Point Wireless Manager™
configuration and network management. DHCP and DNS will also be configured
on this server and are part of the Linux operating system.
RADIUS - (Optional)
•The Windows 2003 server is optional and is used to support EAP-TTLS Secure
Mesh. Juniper’s Steel Belted Radius application will be configured on the
Windows 2003 server since it supports EAP-TTLS based authentication. The
Windows 2003 Server also provides certificate services which will be used to
generate certificates to support EAP-TTLS. Our RADIUS server could also be
used for certificate based 802.11 client authentication and or store 802.11 client
usernames and passwords. A RADIUS server for Secure Mesh is not required if
PSK Secure Mesh is used instead.
application. This application provides device
2-6
Chapter 2: Network Setup
EAP-TTLS Secure Mesh
The MotoMesh 2.1 architecture provides a set of features designed to help network operators
secure the mesh network. These security features can help to protect the mesh network from
intruders and attackers.
It is important to distinguish between the security provided by the MotoMesh architecture
(Secure Mesh) and the security features provided for standard 802.11 clients (e.g. laptops,
mobile Wi-Fi devices, etc.). Mesh Security applies between all of the mesh-enabled devices
that form the mesh network. 802.11 client security (e.g. WEP, WPA-PSK, etc.) is completely
independent of mesh security and is detailed in the WMS Administrator’s Guide.
EAP-TTLS Secure Mesh uses Public Key Infrastructure (PKI) certificates to authenticate the
network infrastructure, a RADIUS server, and a unique user ID and password to uniquely
authenticate each mesh device. EAP mode supports MIC codes and encryption, where
available. EAP mode supports centralized control of per-device authentication credentials by
the RADIUS server, so a compromised device's credentials can be individually revoked
without having to change keys on other devices. Session keys are automatically derived
based on the EAP authentication and rolled periodically at a rate controlled by the RADIUS
server. EAP mode is recommended for medium- or large-sized networks or any network that
requires per-device authentication or centralized control over credentials. EAP mode
requires the "R0 Key Holder" (R0KH) service. The R0 Key Holder service acts as a key
cache, speeding up key generation for devices that already have a valid session key from the
RADIUS server, similar to the R0 Key Holder defined for 802.11r. The R0KH service is
included as part of the Linux environment setup.
Secure Mesh can also be configured to use PSK thus eliminating the RADIUS requirement. Please
see the WMS Administrator’s Guide for detailed steps.
Network Device Ethernet Interconnectivity
This section describes the Ethernet connectivity of the small system reference design. Please
note the specific ports used as the software configuration of the equipment assumes the
stated interconnectivity.
Figure 2-2 Ethernet connectivity between network servers and 3750 L3 Switch
Port 1
Port 2
Ports
3-4
The One Point Wireless Manager server is connected to Port 1 of the L3 Switch.
The RADIUS server is connected to Port 2 of the L3 switch.
Ports 3 and 4 on the L3 switch can be used to connect to other network devices e.g. gateway
router
Ports
5-24
Ports 5-24 will be used for connections to IAPs.
2-7
Chapter 2: Network Setup
IP Addressing Plan
Table 2-2 shows the network IP plan for our small system reference design. Four VLANs will
be utilized in our network design (VLAN 1, 24, 31, and 49) each representing a different IP
subnet:
These VLANs are configured in the Cisco Layer 3 switch. A detailed switch configuration is
included in Appendix A.
IP Address Host
• VLAN 1 (10.1.0.0/16 network)
• VLAN 24 (10.24.0.0/16 network)
• VLAN 31 (172.31.0.0/16 network)
• VLAN 49 (10.49.0.0/16 network)
Table 2-1 Core IP Network Plan
172.31.0.2/16
10.1.0.1/16
10.24.0.1/16
10.49.0.1/16
172.31.0.20 One Point Wireless Manager Server
172.31.0.30 to 172.31.255.254 Reserved for other network services servers (VLAN 31)
The table 2-3 lists the address pools that will be configured to support our network. These
address pools are configured on One Point Wireless™ Manager
is available from Motorola that will configure the Linux server with these defaults.
VLAN 1 (Native)
VLAN 1 Address Pool / Untagged devices
DHCP Pool 10.24.0.30 – 10.24.255.254
VLAN 24 (IAP and MWR device addresses)
VLAN 24 Address Pool
2-8
Chapter 2: Network Setup
IP Address Host
DHCP Pool 10.49.0.30 – 10.49.255.254
Layer 3 Switch
Overview
The standard small system reference design includes a Cisco 3750 L3 Switch which supports
20 Intelligent Access Points (IAPs). Four switch ports (ports 1-4) are also available for
network servers such as the One Point Wireless Manager™ server and RADIUS. IAPs are
connected to L3 switch (ports 5-24) via one of three methods:
• Direct Ethernet
• Connection via a wireless bridge (Motorola Canopy™ System)
• Connection via a wireline media converter (e.g. Ethernet over Fiber media
converter)
VLAN 49 (802.11 clients)
VLAN 49 Address Pool
Figure 2-3 Cisco 3750 L3
SYST
RPS
MASTR
STAT
DUPLX
SPEED
STACK
MODE
The Cisco 3750 router provides the following services:
•Routing between the wireless subnets 10.1.0.0 /16, 10.24.0.0/16, 10.49.0.0/16,
and the server network 172.31.0.0/16 (e.g. inter VLAN routing between VLANs
1, 24, 31, and 49).
•DHCP relay from the wireless subnets to the DHCP server running on the One
Point Wireless server 172.31.0.20.
•802.1Q VLAN tag recognition enabling the support of a trunked set of VLANs
terminating on a single physical interface
IP Directed Broadcasts
1234567891011
1X
2X
Catalyst 3750
12
11X
12X
1314151617181920212223
13X
14X
24
23X
24X
SERIES
12
By default, the 3750 Switch drops IP directed broadcasts; thus preventing them from being
forwarded. The One Point Wireless Manager™ application utilizes SNMP broadcasts for
automatic network discovery. We have enabled IP directed broadcasts in the 3750 L3 switch
2-9
Chapter 2: Network Setup
in order to prevent the switch from dropping these discovery packets. See Appendix A for
detailed steps on how to configure the IP directed broadcast feature on the 3750 L3 switch.
VLAN Setup
The L3 network switch provides the ability to segment management and user traffic using a
combination of VLAN tagging and firewall access control rules, see Figure 2-4. In the small
system reference design the L3 switch has been configured with the following 4 VLANs each
representing a different IP subnet per our IP plan:
• VLAN 31 is configured on Ports 1-4. Ports 1-4 are access ports only (non-tagged)
• VLAN 1 is the native VLAN of the L3 switch by default. Ports 5-24 have been
and are used by network servers such as the One Point Wireless Manager™
(172.31.0.20/16) and RADIUS. VLAN 31 has the address of 172.31.0.2/16. Note
how the second octet of the IP address (31) is aligned with the VLAN number. This
has been done to simplify the IP design.
configured as trunked ports and have VLAN 1 in their allowed VLAN list. VLAN 1 has
the IP address of 10.1.0.1/24. It has been configured to support non VLAN capable
devices such as cameras and other IP devices. This VLAN is also configured with an
IP helper address of 172.31.0.20 (The address of the Wireless One Point Manager™
server) to service any DHCP requests received on this VLAN.
server
• VLAN 24 is also included in the allowed VLAN list on ports 5-24. VLAN 24 has the
address of 10.24.0.1/16. VLAN 24 has been configured to be used as a
management VLAN. The management VLAN is used to communicate management
data from the One Point Wireless Manager™
VLAN is also configured with an IP helper address of 172.31.0.20 (The address of
the Wireless One Point Manager™ server) to service any DHCP requests received
on this VLAN.
• VLAN 49 is also included in the allowed VLAN list on ports 5-24. VLAN 49 has the
address of 10.49.0.1/16. VLAN 49 has been configured to be used by wireless
clients. As mentioned previously a MOTOMESH Duo device supports up to 15
Virtual Access Points (VAPs) per radio. Each VAP can be configured to have a
unique VLAN. Thus, in this example, VLAN 49 has been created to support a client
VAP. Note that this VLAN tag will be stripped off prior to data being sent to client
devices (VLAN tag stripping is on by default on client VAPs). Traffic that originates
from a client would be tagged with VLAN 49. This VLAN is also configured with an IP
helper address of 172.31.0.20 (The address of the Wireless One Point Manager™
server) to service any DHCP requests received on this VLAN.
application to IAPs and MWRs. This
2-10
Chapter 2: Network Setup
Figure 2-4 L3 Switch for MOTOMESH Duo 2.1 - VLAN View
Catalyst 3750
1234567891011
SYST
RPS
MASTR
STAT
DUPLX
SPEED
STACK
MODE
1X
2X
12
11X
12X
1314151617181920212223
13X
14X
24
23X
24X
SERIES
12
VLAN Examples
In order to better understand how VLANs are used in our small system reference design let’s examine
how traffic traverses these VLANs. In the example below the One Point Wireless Manager
connected to port 1 and our IAP is connected to port 18. Management VLAN 24 has been configured on
our IAP as well as DHCP. When the IAP is powered on it obtains an IP address in the follow steps:
1. The IAP requests an IP address via DHCP. This request is sent over VLAN 24.
2. The 3750 switch receives the DHCP request on Port 18 which is configured to accept packets on
VLAN 24. VLAN 24 is configured on the L3 switch to forward DHCP requests to the One Point
Wireless Manager
Point Wireless Manager server
™ server via the configured IP helper address 172.31.0.20. Since the One
™ is connected to port 1, and ports 1-4 are a part of untagged
VLAN 31, the tag is removed and the DHCP request is forwarded out port 1 to the One Point
Wireless Manager
™ server.
™ server is
2-11
Chapter 2: Network Setup
3. The DHCP server observes that the request originates from the 10.24.0.0/16 network. It answers
this request with a 10.24.X.X/16 IP address. Please recall that this DHCP pool has been
configured on the DHCP server running on the One Point Wireless Manager
™ server.
4. The 3750 switch receives this reply and forwards it out back on VLAN 24 to the IAP.
Figure 2-5 VLAN Example 1
Wireless Manager
Wireless Manager
172.31.0.20
172.31.0.20
3
3
Layer 3 Switch
Layer 3 Switch
2
2
VLAN 24 10.24.0.1
VLAN 24 10.24.0.1
IP helper address 172.31.0.20
IP helper address 172.31.0.20
Catalyst 3750
SERIES
Catalyst 3750
12
1234567891011
1234567891011
1X
SYST
SYST
RPS
RPS
MASTR
MASTR
STAT
STAT
DUPLX
DUPLX
SPEED
SPEED
STACK
STACK
MODE
MODE
1X
2X
2X
12
11X
11X
12X
12X
1314151617181920212223
1314151617181920212223
13X
13X
14X
14X
24
24
23X
23X
24X
24X
SERIES
12
12
4
4
In our next example
1
1
IAP
IAP
Management
Management
VLAN 24
VLAN 24
In the next example an 802.11 client has associated to a virtual access point on our IAP. The DHCP
exchange is as follows:
1. The client sends a DHCP request.
2. The IAP tags this request with VLAN 49 and forwards it to the 3750 switch.
3. The 3750 switch receives the DHCP request on Port 18 which is also configured to accept
packets on VLAN 49. VLAN 49 is configured on the switch to forward DHCP requests to the One
Point Wireless Manager
One Point Wireless Manager
untagged VLAN 31, the tag is removed and the DHCP request is forwarded out port 1 to the One
Point Wireless Manager
™ server via the configured IP helper address 172.31.0.20. Since the
™ server is connected to port 1, and ports 1-4 are a part of
™ server.
2-12
Chapter 2: Network Setup
4. The DHCP server observes that the request originates from the 10.49.0.0/16 network. It answers
the request with a 10.49.X.X/16 IP address. Please recall that this DHCP pool has been
configured on the DHCP server running on the One Point Wireless Manager
™ server.
5. The 3750 switch receives this reply and forwards it out back on VLAN 49 to the IAP.
6. The IAP strips off the VLAN tagged and sends the reply to the client.
Figure 2-6 VLAN Example 2
4
Wireless Manager
Wireless Manager
172.31.0.20
172.31.0.20
4
3
3
Layer 3 Switch
Layer 3 Switch
VLAN 49 10.49.0.1
VLAN 49 10.49.0.1
IP helper address 172.31.0.20
IP helper address 172.31.0.20
12
1234567891011
1234567891011
1X
SYST
SYST
RPS
RPS
MASTR
MASTR
STAT
STAT
DUPLX
DUPLX
SPEED
SPEED
STACK
STACK
MODE
MODE
1X
2X
2X
12
11X
11X
12X
12X
1314151617181920212223
1314151617181920212223
13X
13X
14X
14X
Catalyst 3750
SERIES
Catalyst 3750
24
24
SERIES
23X
23X
12
12
24X
24X
5
5
2
802.11
802.11
Client
Client
1
1
Virtual Access Point configured
Virtual Access Point configured
2.4 GHz
2.4 GHz
To use VLAN 49
To use VLAN 49
2
IAP
IAP
6
6
MOTOMESH Duo Device Defaults
MOTOMESH Duo devices come from the factory with the following default settings:
2-13
Chapter 2: Network Setup
• All devices are IAPs
• DHCP enabled
• VLAN support enabled
• Management configured as VLAN 4095. A management VLAN of 4095 means
• Backhaul detection on – If a MOTOMESH Duo device does not detect a wired
untagged. Thus when a MOTOMESH device requests an IP address for the first time
the DHCP request will come in as untagged and will be serviced by VLAN 1. Thus
the device will receive a 10.1.X.X/16 address (e.g. if the small system reference
design defaults are used). The management VLAN can then be changed to another
VLAN e.g. VLAN 24 used in the reference design. (The management VLAN would
be changed to VLAN 24 and the device rebooted. The device would then get a
10.24.x.x address).
backhaul connection it will convert itself from an IAP to an MWR. The Backhaul
detection feature is comprised of active ping and link layer detection. By default, the
IAP will ping the gateway address received in the DHCP reply. If an IAP is statically
configured then an IP address will need to be entered into the backhaul detection
settings (in the One Point Wireless Manager™ application or via the webpage
interface) for the Backhaul Detection feature to operate correctly. Improper
configuration will lead to the IAPs configuring themselves to operate in degraded
mode which is an IAP acting as an MWR.
If an IAP is addressed via DHCP, the gateway address received in the DHCP reply
will be used as the logical address the IAP will ping for logical backhaul detection.
If the IAP is statically configured a valid “pingable” IP address must be configured
in the backhaul detection settings or the IAP will enter degraded status and
operate as an MWR.
Preparing the One Point Wireless Manager Server
This section describes the procedure for the installation of Red Hat Enterprise Linux ES
Version 4, Update 5 (retail box) in a configuration suitable for use with the One Point Wireless
Manager™ application in our small system reference design. While other versions of Red Hat
Linux or another Linux distribution may be suitable to use, discussion of support for other
versions is outside the scope of this section.
2-14
Chapter 2: Network Setup
If you choose another version of Red Hat Linux or an alternate distribution, the
content of this manual should only be used as general guidelines for the
installation process.
Minimum Software Requirements
The following table lists the software versions required to support the One Point Wireless
Manager™ application on the Linux platform.
Table 2-3 Software Requirements for One Point Wireless Manager
Device Software Revision
Red Hat Enterprise Linux ES 4.0 Update 5
Java Runtime Environment 1.6 or higher (included with Wireless Manager application)
MySQL 5.0.40 (included with Wireless Manager application)
Red Hat Linux Installation
Starting the Red Hat Enterprise Linux ES Installation
The MOTOMESH 2.0 One Point Wireless Manager™ application is designed to run on a 32bit version of the Red Hat operating system. If supported by the BIOS settings, booting with
the Red Hat Enterprise Linux ES CD inserted will initialize the installer. If this is not the case,
you may have to configure your server BIOS to boot from removable media first. Refer to
your server documentation for information on changing BIOS settings. The following section
describes how to install RedHat Linux using our reference design defaults.
You must install the 32-bit version of the Red Hat OS.
Installation of Red Hat Enterprise Linux ES
Complete Procedure 2-1 to install the Red Hat Linux ES software.
Procedure 2-1 Red Hat Enterprise Linux ES Installation on HP DL360 G5 Server
Insert the first Red Hat Enterprise Linux ES install CD and reboot the server. The system
1
should boot up to the following screen:
[F1-Main] [F2-Options] [F3-General] [F4-Kernel] [F5-Rescue ] boot:
2-15
Chapter 2: Network Setup
A Press the Enter key to begin the installation in graphical mode. If no key is pressed, the
2
system will auto launch in 60 seconds.
The following prompt will appear:
3
To begin testing the CD media before installation press OK. Choose Skip to skip the media test
and start the installation.
Choose Skip.
The Welcome to Red Hat Enterprise Linux screen will be displayed. Click on the Next
4
button.
Select the appropriate Language Selection setting and click on the Next button.
5
Select the appropriate Keyboard Configuration setting and click on the Next button.
6
If you are installing from other than the retail boxed set, you may be prompted to
perform a media check. While this step is time consuming, it ensures a successful
installation.
7
8
9
10
11
Select Automatically Partition and click on the Next button.
Select Remove all partitions on this system.
This setting will erase any and all existing operating systems and
data.
Use the default drive that is highlighted under Select the drive(s) to use for this installation.
Make sure that Review is checked at the bottom of the page. This allows you to view and
change the automatic partitioning results. Click on the Next button. Click Yes in the Warning
dialog box that appears.
It is recommended that the user create a separate /var partition for storing log files and
databases. This ensures that the files to be created will not fill up all available space on the
system partitions and will also help prevent fragmentation in the file system.
Click on the New button. A dialog box will pop up to create a new partition. Enter or verify the
following parameters:
Mount Point: /var
File System Type: use the default setting
Allowable Drives: use the default setting
Size (MB): 10000
Additional Options: Fixed Size
12
13
Click on the OK button. Check the partitions display to ensure that the new /var partition was
created. Click on the Next button.
The default Boot Loader Configuration will already be correct. Click on the Next button.
2-16
Loading...
+ 105 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.