FS6200 Server System Implementation Guide - Public Support ...
FS6200 Server System Implementation Guide - Public Support ...
FS6200 Server System Implementation Guide - Public Support ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Index<br />
initialization files, 3–9<br />
Jumbo Frames, 3–18<br />
MCP Networking values, 3–23<br />
MCP Networking values IOE-1, 3–23<br />
MCP Networking values IOE-2, 3–27<br />
sample ADAPTERS.TXT file, 3–22<br />
setting local MAC address, 3–16<br />
<strong>System</strong> Editor, 3–19<br />
TCP/IP initialization file, 3–30<br />
Networking values<br />
IOE-1 default, 3–11<br />
IOE-2 default, 3–12<br />
MCP, 3–23<br />
MCP IOE-1, 3–23<br />
MCP IOE-2, 3–27<br />
NP inquiry, 4–26<br />
O<br />
obtaining MCP Java Monitor log file, 9–19<br />
offload settings, TCP, 3–16<br />
Open Management Interface (OMI)<br />
installing and configuring, 3–33<br />
operating<br />
ePortal Specialty Engine, 5–1<br />
Operations Servcer<br />
failure scenarios, 9–8<br />
Operations <strong>Server</strong><br />
configuration, 3–33<br />
Operator Display Terminal (ODT), 2–7<br />
P<br />
password of Administrator, changing, 3–31<br />
PCD updates, 4–29<br />
PCI card BIOS/firmware updates, 8–3<br />
performing dynamic PCD updates, 4–29<br />
PING command<br />
verifying EVLAN path, 4–22<br />
PING commands, enabling<br />
for JProcessors, 4–30<br />
for MCP, 4–19<br />
platform boot progress, monitoring, 4–1<br />
Platform Console, 2–8, 4–2 , 4–3<br />
platform hardware<br />
components, 2–2<br />
monitoring boot progress, 4–1<br />
power status, 4–1<br />
powering off, 4–3<br />
powering on, 4–1<br />
restarting, 4–3<br />
shutting down, 4–2<br />
platform management card, 2–8<br />
Platform Services, 4–3<br />
policy services<br />
MCP Firmware Environment Policy, 4–6<br />
port<br />
Custom Connect Facility (CCF), 5–5<br />
power control, 4–1<br />
monitoring the platform boot progress,<br />
4–1<br />
powering off platform hardware, 4–3<br />
powering on platform hardware, 4–1<br />
restarting platform hardware, 4–3<br />
shutting down platform hardware, 4–2<br />
viewing platform hardware status, 4–1<br />
power cycling<br />
cell, 9–26<br />
Fibre Channel I/O devices, 4–30<br />
powering down cell to replace failed<br />
hardware, 9–25<br />
powering off platform hardware, 4–3<br />
powering on platform hardware, 4–1<br />
powering up cell, 9–26<br />
preparing to use<br />
Ethernet Jumbo Frames, 3–18<br />
IEEE 802.1Q VLANS, 3–17<br />
problems<br />
mapping to a Client Access Services<br />
share, 9–12<br />
Call Home, 9–4<br />
Product <strong>Support</strong> website, accessing, 9–3<br />
R<br />
reboot dump, 4–26<br />
reconfiguring<br />
VSS disks, 3–2<br />
recovering <strong>FS6200</strong> <strong>Server</strong> configuration data,<br />
9–24<br />
recovery actions, 9–24<br />
powering down cell to replace failed<br />
hardware, 9–25<br />
powering up cell, 9–26<br />
recovering <strong>FS6200</strong> <strong>Server</strong> configuration<br />
data, 9–24<br />
reinstalling the entire platform, 9–27<br />
restarting an ISM environment, 9–27<br />
restarting the ISM, 9–27<br />
reinstalling<br />
entire platform, 9–27<br />
Network Services, 8–4<br />
Index–6 8222 3694–000