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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

If you do not receive this response, check the state of CNS and TCP/IP on the MCP. If<br />

TCPIP reports that it is currently “Networking,” query the TCPIP IDENTITY of the MCP<br />

using the following command:<br />

NW TCPIP IDENTITY<br />

The first identity in the response should be similar to:<br />

IPADDRESS 192.168.16.5 / 255.255.255.252<br />

NP-DEVICE 210, LINEID 0,<br />

PHYSICAL ADDRESS HEX 08000B002100<br />

AUTOCONFIGURATION FALSE,<br />

DUPLICATEADDRESSDETECTIONTRANSMITS 0,<br />

VISIBLE - ,<br />

If the IP address is different but the NP-DEVICE and LINEID match, then there might be a<br />

mismatch in the IP address of the MCP Environment and the EVLAN adapter definition in<br />

the I/O engine. Refer to Table 3–4 for comparison with default IP address and Line ID<br />

values.<br />

If the Physical Address is all zeroes (000000000000), the TCPIP connection is closed.<br />

Determine the reason that the TCP/IP connection is closed using the NW CONN<br />

command on the Connection Group and the Component Connection associated with the<br />

appropriate NP based upon Table 3-3.<br />

If the IP address is correct and the Physical Address is correct, check the configuration of<br />

the EVLAN adapter in the I/O engine. Issue the command IPCONFIG −ALL from the same<br />

command prompt you used to enter the PING command. You should see an adapter in the<br />

resulting list that appears similar to the following:<br />

Ethernet adapter Local Area Connection 29:<br />

Connection-specific DNS Suffix . :<br />

Description . . . . . . . . . . . : Unisys Network Services EVLAN Adapter<br />

Physical Address. . . . . . . . . : 08-00-0B-06-22-59<br />

DHCP Enabled. . . . . . . . . . . : No<br />

Autoconfiguration Enabled . . . . : Yes<br />

IPv4 Address. . . . . . . . . . . : 192.168.16.6(Preferred)<br />

Subnet Mask . . . . . . . . . . . : 255.255.255.252<br />

Default Gateway . . . . . . . . . :<br />

NetBIOS over Tcpip. . . . . . . . : Enabled<br />

The IP address should be the IOE address for the EVLAN adapter from Table 3-3, or an<br />

alternate value assigned by the client within the same subnet as the MCP IP address for<br />

that line. If it is not, re-configure the IP Address of the EVLAN using the MCP Console<br />

<strong>System</strong> Editor.<br />

If the addresses are correct but the PING command still does not work, contact your<br />

Unisys representative for further assistance.<br />

MCP Operations Interface Summary<br />

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

This topic summarizes the data types, EVLAN and MCP network adapter attributes, and<br />

MCP commands related to Network Services and ClearPath MCP networking operations.<br />

8222 3694–000 4–23

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

Saved successfully!

Ooh no, something went wrong!