18.08.2013 Views

FS6200 Server System Implementation Guide - Public Support ...

FS6200 Server System Implementation Guide - Public Support ...

FS6200 Server System Implementation Guide - Public Support ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Operating the <strong>Server</strong><br />

NW BNA + <br />

2. Issue the following command to list the NPs and their state:<br />

NW NP<br />

The expected response should include status similar to the following for each<br />

configured NP:<br />

NP 210 NETWORKING VNP,<br />

Verifying Network Services Installation and Configuration<br />

Perform the following tests to verify that Network Services is correctly installed.<br />

Note: The PING operation must be performed from each I/O engine environment. Refer<br />

to Table 3–4 for default IP address and Line ID values for each I/O engine.<br />

If the EVLAN IP address was modified during MCP networking configuration, that IP<br />

address is required for the remainder of this subsection in order for this process to<br />

complete as expected.<br />

1. Enter PING 192.168.16.5 from a command prompt on the I/O engine environment<br />

and verify that you receive a response.<br />

2. Verify that the <strong>FS6200</strong> <strong>Server</strong> responds. For example<br />

Pinging 192.168.16.5 with 32 bytes of data:<br />

Reply from 192.168.16.5: bytes=32 time=10ms TTL=62<br />

If the server does not respond, continue with the following procedure “If the PING<br />

Command Is Unsuccessful.”<br />

If the PING Command Is Unsuccessful<br />

Note: If the PING command in the preceding subsection was unsuccessful, continue<br />

with this subsection. All of the assumptions from the preceding subsection apply to this<br />

one, including the Note. However, if the PING command was successful, no further action<br />

is required.<br />

The EVLAN path is not working if a PING command gets the response ″Request timed<br />

out″ for all four attempts. Verify that MCP Networking is running with the following<br />

command from an MCP ODT session:<br />

NW TCPIP STATUS<br />

The response should be similar to:<br />

TCPIP IS CURRENTLY NETWORKING(IPV4-ONLY),<br />

RIP IS CURRENTLY ENABLED/RUNNING,<br />

TCPIP SECURITY IS CURRENTLY RUNNING,<br />

SSL IS CURRENTLY TERMINATED,<br />

IPSEC IS CURRENTLY DISABLED/NOT RUNNING<br />

4–22 8222 3694–000

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!