FS6200 Server System Implementation Guide - Public Support ...

Operating the Server
1. Connect the new devices and ensure that they have been discovered by the I/O
engine environment. In some cases, such as adding new LUNs to a storage system,
you must use Device Manager to scan for hardware changes outboard of each HBA
that should have new devices visible to it.
2. Use the System Editor of the MCP Console and load the active PCD.
The Adjust Resources dialog box is displayed that enables you add the new
devices.
3. Accept the additions, changing device numbers and comments if desired, and then
put the updated PCD into use on the running MCP by setting it active.
The MCP displays a message about the PCD update. Added devices are initially in the
MCP FREEd state and must be ACQUIREd to be used.
This procedure is not restricted to newly connected devices. Older devices not yet
assigned to the MCP can also be added by marking them for use by the MCP, even though
they do not appear in the Adjust Resources dialog box.
Devices cannot be dynamically moved (for example, swapping Fibre Channel cables
between HBA ports) or removed from the PCD using this procedure. These actions
require that the MCP be halted. You can dynamically FREE a device to stop the MCP from
using it, but removing the device from the PCD can only be done when the MCP is halted.
Power Cycling or Disconnecting Fibre Channel I/O Devices
If you power down or disconnect an I/O device (such as a tape drive) and then immediately
power it back on, it might become inaccessible to the I/O engine.
After powering down or disconnecting an I/O device, give the I/O engine time to detect
that the device was removed the Device Manager. Once that happens (or if it is not
removed after two minutes), it is safe to power the device on or reconnect the device. It
might then take plug and play some time to rediscover the device.
If you lose access to a device due to doing one of these actions, follow the procedure
outlined in the topic, “Troubleshooting Fibre Channel I/O Problems” in Section 7 of this
guide to attempt to recover the device.
Enabling MCP PING Commands through the Intra-
Platform Connection for JProcessors
Inbound Internet Control Message Protocol (ICMP) requests to the host of the JProcessor
environment are blocked by default. This restriction affects PING commands, which are
ICMP Echo requests. As a result, PING commands from remote computers cannot reach
the JProcessor environment, not even those sent from the MCP. Refer to “Enabling MCP
PING Commands through the EVLAN Connection” earlier in this section for information on
how to add a firewall rule to enable inbound ICMP Echo requests.
4–30 8222 3694–000