Solution:
Controllers configured to communicate over TCP/IP can sometimes encounter various errors if the configuration is not followed as described in the Perle TCP/IP white paper configuration guide.
If the controller is installed and is operational in an existing network or the controller is being installed for the first time you can encounter similar errors.
If the controller stops responding check the front panel of controller for messages, there are easy ways to determine from the error the best way to tackle the problem and find a quick solution.
The most common reported error displayed on the front LED is:
410|| 00 0056
This message is generated when any of the following conditions occur.
1) The controller IP address configured is incorrect.
2) The AS/400 IP address configured in the controller is incorrect or configured for a different as/400.
3) The route has changed in the Router, or removed from the AS/400
4) The remote router has a lock on the controller's MAC address. Flush the ARP table or reboot router.
5) The controller’s IP address is shared with another device on the network.
6) DHCP has been configured and the scope was not configured to exclude the static IP Address assigned to the controller.
7) The network card in the controller is not inserting into the network
the led on the Ethernet card or hub does not light up.
8) The led is off on the Ethernet card, but lights up on the Ethernet hub or switch.
9) ICMP (ping) is being filtered in your firewall.
The above list is some of the most common error conditions.
If you suspect the IP address is the problem, the information can be retrieved from the controller using the front panel and keypad.
To check the addresses press the Request (i) button then type 202 on the keypad then Enter.
The controller will display two rows of letters and numbers.
The Top row is the Name configured in the controller
the bottom row will display the first part of the configuration.
The starting numbers in the LCD can changed based on the type of configuration,stored in the controller.
Please refer to the controller Diagnostic Guide for complete details on all the numbers sequences and its meaning.
For this example Ethernet is assumed.
To retrieve the IP address, from the selected function of [ I 202 ] use the Up arrow keys to move through the menus, continue pushing the UP Arrow key until P1 is reached, to determine the addresses see the following .
202-P1 II xxx.xxx (this is the first half of the 594 IP address.
202-P2 II xxx.xxx (this is the last half of the 594 IP address. (I.e. ,192.168.1.1) Is the controller
202-P3 II xxx.xxx (this is the first half of the AS/400 IP address.
202-P4 II xxx.xxx (the last half of the AS/400 IP address. (i.e,192.168.3.1) The as/400
202-P5 II xxx.xxx (this is the first half of the network (subnet) mask
202-P6 II xxx.xxx (the last half of the (subnet) mask. (i.e, 255.255.255.0) The network mask
202-P7 II xxx.xxx (this is the first half of the default gateway
202-P8 II xxx.xxx (the last half of the default gateway.(i.e 192.168.1.254) The IP address of Router
The information retrieved, is the stored or running configuration transferred to the controller. Any errors in the configuration will require the configuration modified and restored to the controller.
If the IP address is correct, try to ping the IP address of the controller from a local PC, if the controller responds, the router requires the ARP table flushed at the remote router.
If the network administrator is not available rebooting the router will also resolve this problem.
Another common condition is the controller has no messages and none of the workstations have the AS/400 session.
Typically in a new install there are two common mistakes.
1) The IP address is not configured in the host table. or if the entry was added an error was made in the entry.
2) The local location name of the controller is not added to the configuration list.
1) If the IP address or the host name was omitted or an error in the name or IP address was made in the host table, the message the AS/400 will display in the Qsysopr messages will read.
"Session start request failed check the mode description."
To correct this error on the AS/400
Enter the command Cfgtcp then select option 10, check the host table for the IP address and host name of the controller, remove and re-enter and confirm the spelling and format of entry.
The host table entry must follow a predetermined format
1) IP address of controller (this was assigned during the twinax configuration.)
2) Controller name configured (i.e C594E1)
3) The as/400 network name.. (APPN)
4) the IBM sna suffix. (SNA.IBM.COM)
Note: Short form names will not resolve the sessions.
The syntax for the Host table is:
192.168.1.1 C594E01.APPN.SNA.IBM.COM
2) If the RMTLOCNAME is missing from the configuration list, the message in qsysopr will read.
"Route to location not found."
To resolve the route problem.
1) Work with the Appc controller descriptions and check the remote location name.(WRKCFGSTS *CTL)
2) Work with the configURATION list wrkcfgl, check the Qappnrmt list for entry.
The list is as follows
Configuration List. . : QAPPNRMT Configuration list Type: *APPNRMT ------------------------------------------------------------ Remote Local Remote Control Remote Network Location Control Point location ID Point Net ID ------------------------------------------------------------ C594E01 *NETATR *NETATR ANYNTCTL *NETATR
|