Troubleshooting

Migrating Exchange 2010 To Dell Advanced Infrastructure Manager Environment
Page 19
4. Identify the Fabric C NIC‘s
Upon reboot, press <Ctrl+S> to enter the Network Configuration Menus. In the lab deployment, the
NIC‘s on Fabric C or PCI bus 05:00:00 and 5:00:01 were used for SCN networking. Note these two MAC
addresses. In the MBA Configuration menus for these two C channel NIC‘s choose the boot protocol as
PXE. All the other NIC‘s can be set to the default option (None). You would also need to enter the
System Setup menu (press <F2>) and update the boot priority so that the NICs are assigned higher
priority than the local disk.
5. Inject the drivers
Using the previously identified NICs, inject the drivers using the SMU to only these NICs. Identify them
using the MAC addresses just noted.
a. Mount the iSCSI LUN that contains the OS image just copied.
b. Advanced Operations > Prepare Image for iSCSI boot > Physical PXE > OS Volume on iSCSI
LUN
o Prepare the NIC attached to fabric C1
c. Repeat Step ‗b‘ for NIC attached to fabric C2.
Creation of Personas
Create Windows Server 2008 R2 personas for both Exchange servers considering following points:
- Either create persona in trunk or access mode depending on whether you desire to have
failover capabilities for the network interfaces on the SAN booted OS image
- Provide appropriate boot parameters
o Ensure boot method to be iSCSI boot
o Provide Storage details pertaining to EqualLogic group hosting OS images
- Specify Persona DNS, Gateways and routes pertaining to Networks per Exchange server
Creation of Server Pools
Server pools provide ability of server failovers. On detecting a server failure, the controller will
retarget the persona running on the failed server to a standby server within the pool, thereby resuming
the failed server OS, with some downtime for the application running on it. Create server pools
considering following points:
- Add the discovered servers (along with the stand-by server to the pool)
- Add the created personas to the pool
Creating and Configuring AIM Networks
This section has two parts; the first part describes how to configure AIM networks, while the second
section describes how to modify the Networks per persona (Exchange server) requirements.
Create AIM Networks
An Exchange ecosystem requires the configuration of three specific networks: public (MAPI) network,
private (Replication) network, and iSCSI database network. We created one AIM network per Exchange
network with corresponding configurations and taking into consideration following points:
- Specify the network IP address and the Netmask
- Specify primary and secondary channels and VLAN ID
- Assign Personas to the network