I work for a small software company and we just purchased our first IBM
AS/400 (9406-170) to use for testing purposes. Our software is used to
query a variety of databases and many of our customers use DB2 on the
AS/400.
Now that we have abox here in-house, Im trying to get it connected to
our internal network. I followed the steps on the IBM web site, and it
looked like I was there. I tried pinging the local IP that I had
configured, but no response from my workstation. Somewhere on the
site, it mentioned running the EZ-Setup wizard, but I cant find this
CD, nor do I know how to start it once I find it.. *sigh*
Here's what I did so far:
1) Used 'Go Hardware' to view the Communication Resources, and saw the
Ethernet Port listed as Resource CMN03, Type 2838, Stauts Operational,
Text says Ethernet Port. Above this in the list was resource LIN02
with all the same setting except Text=LAN Adpater.
2) I created a line description as instructed in the next step. Here
is every parameter on this page (I only had to type in the first 2):
Line Description: ETHLAN2
Resource Name: CMN03
Online at IPL: *YES
Vary On Wait: *NOWAIT
Local Adpater Address: *ADPT
Exchange Identifier: *SYSGEN
Ethernet Standard: *ALL
Line Speed: 10M
SSAP List:
Source Service Access Point *SYSGEN
SSAP Maximum Frame: {Blank}
SSAP Type: {Blank}
Text Description: *BLANK
3) It said that the line description was created successfully. Next
step was to configure an interface, which I did by adding one under
option 1 of the TCP/IP menu (Work with TCP/IP Interfaces) and entered
the Internet Address (192.168.16.x), Line Description of ETHLAN2 and
subment mask (255.255.255.0). I didnt touch any of the other
parameters, which are as follows:
Associated Local Interface: *NONE
Type of Service: *NORMAL
Maximum Transmission Unit: *LIND
Autostart: *YES
PVC Logical Channel Identifier: {blank}
X.25 idle circuit timeout: 60
X.25 maximum virtual circuits: 64
X.25 DDN Interface: *NO
TRLAN bit sequencing: *MSB
This adds the interface, but when I attempt to start it, it hangs for a
few seconds and says something like "Unable to determine if
'192.168.16.x' started...
I then issued the command strtcp to start TCP/IP and when i go back to
the interface menu and display the statuses, it shows this interface as
"Starting".
One other thing to note is that there is a loopback device listed above
the ethernet device with an address of 127.0.0.1 that says "Active".
It does resond to the ping test. Also, I did verify that the AS/400
has a 10Mb link light on our network hub.
Any help or pointers to online resources would be greatly appreciated.
I purchased the book "Mastering the AS/400", which looks pretty good,
but it doesnt go into any detail about configuring hardware and network
connections.
Thanks in advance,
-Ben
Welcome to the club. Your jacket will be mailed soon.... :)
> Here's what I did so far:
> 1) Used 'Go Hardware' to view the Communication Resources, and saw the
> Ethernet Port listed as Resource CMN03, Type 2838, Stauts Operational,
> Text says Ethernet Port. Above this in the list was resource LIN02
> with all the same setting except Text=LAN Adpater.
That's good..
>
> 2) I created a line description as instructed in the next step. Here
> is every parameter on this page (I only had to type in the first 2):
> Line Description: ETHLAN2
> Resource Name: CMN03
> Online at IPL: *YES
> Vary On Wait: *NOWAIT
> Local Adpater Address: *ADPT
> Exchange Identifier: *SYSGEN
> Ethernet Standard: *ALL
> Line Speed: 10M
> SSAP List:
> Source Service Access Point *SYSGEN
> SSAP Maximum Frame: {Blank}
> SSAP Type: {Blank}
> Text Description: *BLANK
I'm just grabbing at straws...
1. You didn't already have a line description of "ETHLINE" on your
system? I can't remember if the system auto configures this or not.
2. The 2838 is a 100M ethernet card. Not sure if that's causing your
problem but it would certainly give you better network response time.
3. When you created ETHLAN2 it should have "varied on" automatically.
Problably should check, though...enter "wrkcfgsts *lin ethlan2". The
"status" should say "Active" or "Varied On". Varied on in AS400 speak
means the line is available to use.
>
> 3) It said that the line description was created successfully. Next
> step was to configure an interface, which I did by adding one under
> option 1 of the TCP/IP menu (Work with TCP/IP Interfaces) and entered
> the Internet Address (192.168.16.x), Line Description of ETHLAN2 and
> subment mask (255.255.255.0). I didnt touch any of the other
> parameters, which are as follows:
> Associated Local Interface: *NONE
> Type of Service: *NORMAL
> Maximum Transmission Unit: *LIND
> Autostart: *YES
> PVC Logical Channel Identifier: {blank}
> X.25 idle circuit timeout: 60
> X.25 maximum virtual circuits: 64
> X.25 DDN Interface: *NO
> TRLAN bit sequencing: *MSB
That looks right...
>
> I then issued the command strtcp to start TCP/IP and when i go back to
> the interface menu and display the statuses, it shows this interface as
> "Starting".
Did you first issue "endtcp *immed"? You probably should recycle
TCP/IP whenever you make these type of changes.
> One other thing to note is that there is a loopback device listed above
> the ethernet device with an address of 127.0.0.1 that says "Active".
> It does resond to the ping test. Also, I did verify that the AS/400
> has a 10Mb link light on our network hub.
In order for the 400 to respond to make outside connections and allow
incoming connectinos you'll need to establish the default route on the
400. Issue the "CFGTCP" command and take option 2. The next screen
should have no entries. Enter a '1' in the option column and enter:
Route destination: *DFTROUTE
Subnet mask: *NONE
Next hop: ip address of your router
After all of this you should endtcp/strtcp.
If this doesn't work then come back and we'll try to get you up and
running.
Two words my friend:
1) YOU
2) ROCK
Heres what I found out:
I issued a CHGLINETH command that I used earlier to check the status of
ETHLAN2, and instead entered ETHLINE.
Sure enough, there is an ETHLINE listed. It was varied off so I tried
varying it on, and it said that it failed. So I checked ETHLAN2 - same
thing. Then I forgot that I had also created ETHLAN (first one I set
up) and that one was varied on. So I turned it off, and instead
decided to go with ETHLINE as that must have been autoconfigured like
you said. That one varied on fine at this point.
I created a new TCP/IP interface using ETHLINE, created the default
route and started TCP. There was briefly a message at the bottom of
the screen saying that TCP couldnt start, but then it went past that
error and started all the various TCP/IP services one by one. When
this stopped, I checked the status of the Ethernet Interfaces, and both
said "Active" for the first time.
I went to my workstation, pinged the interface and got a reply.
You hit a grand slam on the first pitch! Thank you so much!
-Ben
Did you also change the line speed to 100M?
If you have any other problems feel free to post here.
Jonas