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.
<strong>System</strong> Overview<br />
These services run on the I/O engine which is located on the ISM cell.<br />
Network Processors<br />
The <strong>FS6200</strong> <strong>Server</strong> supports up to six Network Processors of type VNP per I/O engine.<br />
• The <strong>FS6200</strong> <strong>Server</strong> is preconfigured with at least two NPs.<br />
• The first NP is reserved for the EVLAN connection and the intra-platform connections<br />
to the JProcessor Specialty Engines and the ePortal Specialty Engine.<br />
The EVLAN is an emulated network interface card providing a connection between the<br />
MCP Environment and the I/O engine.<br />
The intra-platform connections provide a connection between the MCP Environment<br />
and the specialty engine environments.<br />
• There is an additional VNP for each physical NIC in the system in the default<br />
configuration. The additional VNPs are assigned the adapter ports of the NICs in the<br />
PCI Express slots.<br />
This connection allows the MCP Environment to access a NIC within the I/O engine.<br />
The MCP network adapter supports BNA and TCP/IP transfers to and from the MCP<br />
Environment.<br />
• Each NP supports up to eight MCP network adapter connections.<br />
JProcessor Specialty Engine<br />
ISM-0<br />
ISM-1<br />
The JProcessor Specialty Engine provides Java Services to applications running in the<br />
MCP Environment. The JProcessor Specialty Engine is provided on the ISM.<br />
Each ISM consists of two JProcessor Specialty Engine environments as follows:<br />
• JProcessor 1 Environment<br />
• JProcessor 3 Environment<br />
• JProcessor 2 Environment<br />
• JProcessor 4 Environment<br />
The JProcessor Specialty Engine environments run independently and provide redundancy<br />
and load balancing for Java Services.<br />
Normal systems management of the JProcessor Specialty Engine environments is<br />
performed from the MCP Environment which is consistent with how JProcessor Specialty<br />
Engine appliances are managed on other MCP systems.<br />
2–6 8222 3694–000