8.501 bytes

Service Hints & Tips

Document ID: MIGR-47WJ8A

Network Station - Additional Information for Twinax Units

Applicable to: World-Wide

The following document provides additional information about configuring Twinax Network Stations on an AS/400 boot server. It does not replace the IBM Network Station Manager Installation and Use book ( SC41-0664 ). You can view or download this book from the following website:

http://publib.boulder.ibm.com/pubs/html/netcom/r3.htm

Install Example for Intranet Networks

Note: This installation example is for an internal (intranet) network, his is the simplest scenario. Notice we will be using nonregistered TCP/IP addresses such as 10.10.10.1 because you will not be accessing the outside world.

1. Install Network Station Manager License Product 5648C05.
2. Start TCP/IP support on the AS/400. Type the following on the OS/400 command line: STRTCP and hit enter.
3. On the AS/400, end the DHCP server and start the BOOTP server. Type the following on the OS/400 command line: ENDTCPSVR *DHCP , STRTCPSVR *BOOTP
4. Cable the Network Station to the WSC port on the AS/400.
5. Power on the Network Station.
6. Should display messages NS0010 through NS0040.
7. Set Twinaxial Station Address Screen appears.
8. Enter your Twinax Station address.

The Network Station will force you to choose an un-used address and then it will proceed to the NS0500 message. This automatically creates a TDLC line and attaches it to the WSC. It also generates a message in the QSYSOPR MSGQ. If the DSPxx cannot connect, a TCP/IP interface was probably not added for line QTDLxxxxxx. Find the message in the message queue. This will tell you the name of the TDLC line in the form of QTDLxxxxxx.To add and start the TCP interface for that line, type the following on the OS/400 command line:
ADDTCPIFC '10.10.10.1' QTDLxxxxxx '255.255.255.192'
STRTCPIFC '10.10.10.1'

Note: Don't forget the quotes!

To verify that the interface has started GO CFGTCP, option 1, F11.

Install Scenario for external access Networks

• Obtain a valid range of IP addresses + 1 extra Range must be a complete subnet. For example:10.10.85.128 - 10.10.85.143 and 255.255.255.240 as the subnet mask, 10.10.85.128 is the subnet address, 10.10.85.129 will be the interface address, and 10.10.85.143 is the broadcast address

• Thus we can have 13 Network Stations. All addresses must be known to the AS/400's gateway. Ideal is to have a number of addresses greater than the number of Network Stations. This allows each unit to keep their IP address constant. Otherwise, shuffling of IP addresses may occur and some units may not be able to obtain IP addresses. Map extra address onto external LAN line. 10.10.85.215 will be our "extra" address. Define subnet to contain all obtained addresses. We will use subnet mask of 255.255.255.128 in our example. Remember, this subnet must contain the previous one. Add and start this interface with the following AS/400 commands:

ADDTCPIFC '10.10.85.215' TRNLINE '255.255.255.128'
STRTCPIFC '10.10.85.215'

• Create Twinaxial interface. Pick one of the subnet addresses for interface address. Subnet mask based on address range. Define extra address as the associated local interface. Add and start this interface. Allow IP datagram forwarding on the AS/400 with the following command:

CHGTCPA IPDTGFWD(*yes)

• Reboot your Network Stations. You should now be able to access other networks. Here is another example. Now, let's change the subnet mask to 255.255.255.248. This will allow only 5 NSs to connect. Power off all NSs, end interface, change subnet mask, start interface and reboot all NSs. Watch for messages in QSYSOPR MSGQ.

Twinax NVRAM Support

Unlike the Ethernet and token-ring models of Network Stations, you can leave all entries as 0.0.0.0. Twinax support will add the attached AS/400's IP address to the boot host list if:

The address is not already in the list.
And, one of the entries in the list is 0.0.0.0.

The Twinax NS will always try to boot off of the physically attached AS/400 unless all 3 boot host addresses are non-zero, and none of them are the address of the attached AS/400.

Twinax DHCP support

Configure the Twinax Subnet.
Use Operations Navigator.
DHCP class 3.4.1.
DHCP handshake as per T/R.
DHCP lease will be released immediately. All We needed was the boot file. Remember, TDLC controls the IP addresses.

Read AS/400 TCP/IP Auto configuration DNS and DHCP (SG24-5147) redbook for more information.

Error messages you may see:

• NS0711 Station address in use: Set-up utility, F8
• NS0720 No Twinaxial Activity detected: Run wrap test, check cabling
• NS07000 Twinax Timeout unable to contact host: NS sees Twinax activity, bring up does not proceed, run wrap test, check cable.
• NS0710 Twinax Timeout, host connection lost,Connection was established, but has been interrupted: Check cable, check WSC .

Useful References:

• Redbook: SG24-5147 AS/400 TCP/IP Auto configuration DNS and DHCP: Chapter 15:Configuring Twinax Network Station with DHCP

• IBM Network Station Manager Installation and Use: SC41-0664 includes new sections on Twinax model Network Station.

	Search Keywords
	Document Category	System Administration Tools, Twinax
	Date Created	15-05-99
	Last Updated	14-05-99
	Revision Date	15-11-99
	Brand	Network Computers, IBM Network Station
	Product Family	AS/400 - Network Station, S/390 VM/ESA - Network Station, S/390 OS/390 - Network Station, RS/6000 - Network Station, OS/2 Warp Server - Network Station, NT Server - Network Station
	Machine Type	8361, 8362
	Model	All
	TypeModel
	Retain Tip (if applicable)
	Reverse Doclinks and Admin Purposes