Configure TCP/IP when the operating system is in restricted state

Use the method outlined in this topic if you need to run TCP/IP while the operating system is in restricted state.

Situation

As the network administrator, you need to obtain backup status reports for your server. When you are running backup procedures, the operating system must be in restricted state to prevent users from changing any configuration. Because you are remote, you access status reports using a personal digital assistant (PDA) device (or any TCP/IP networking device). The PDA uses a sockets-enabled application that requires an active TCP/IP interface available to communicate with the server. To allow this communication, you must first start TCP/IP using special parameters. After you start TCP/IP, you will need to start a specific TCP/IP interface to allow access to the system. The information below provides more detail.

Restrictions

The following restrictions apply when the operating system is running in restricted state:

Cannot start TCP/IP servers (STRTCPSRV CL command), since they require active subsystems.
Can only start one interface for a specific line type (Ethernet, token-ring, or DDI) that is not attached to a network server description (NWSD) or a network interface description (NWID).

Configuration steps

Start TCP/IP using special parameters.
When the iSeries™ system is in restricted state, process the following command from the command line interface: STRTCP STRSVR(*NO) STRIFC(*NO) STRPTPPRF(*NO) STRIP6(*NO). These are the only parameters accepted when the operating system is in restricted state. The above command will start TCP/IP; however, it will not and cannot start TCP/IP application servers or IP interfaces.
Start a specific TCP/IP interface. After you start TCP/IP in restricted state, you can start the specific interface needed for your sockets-enabled application.
1. Verify that the interface you want to start uses a line description of *ELAN, *TRLAN, or *DDI.
  To view the line type for your interface, at a command line interface enter CFGTCP and select option 1 (Work with TCP/IP interfaces).
2. Verify that the interface is not attached to an NWID or NWSD. Any other attempts will prompt an error message.
  To verify the interface is not attached to an NWID or NWSD, from a command line interface enter DSPLIND abc (where abc is the name of your line description). Verify that the Resource name is not *NWID or *NWSD.
  Note: If the interface is attached to an NWID or NWSD, then it is recommended you select a different interface.
3. Finally, start the interface. At a command line interface, enter the following: STRTCPIFC INTNETADR('a.b.c.d'). Replace a.b.c.d with your interface IP address.
  Note: Verify that STRTCPIFC INTNETADR(*AUTOSTART) is not specified.
Verify that the interface is active.
Ping the specific interface for your application. There are very few TCP/IP related utilities that will operate in restricted state. However, ping and netstat can be used. For more information about using the ping and netstat commands, review Tools to verify your network structure within TCP/IP troubleshooting.