Start interfaces

Start the appropriate interfaces to ensure your network communication.

Your network communication might be failing because your interfaces have not been activated. Remember these tips to ensure your interfaces are functioning correctly.

Verify that your interfaces are configured and activated by using Netstat. For those interfaces you always want active, you should specify AUTOSTART (*YES). They will automatically start when TCP/IP is started.
If you are using profiles for remote access services, such as Point-to-Point Protocol (PPP) or Layer Two Tunneling Protocol (L2TP), you should verify that the profiles are active. To verify the status of the profiles, follow these steps:
1. In iSeries™ Navigator, select your iSeries server > Network > Remote Access Services.
2. Click Originator Connection Profiles or Receiver Connection Profiles depending on the type of profile you want to verify, and view the list of profiles in the right pane to verify the status. To start a profile, right-click the profile and select Start.
If you want any of the remote access services profiles to automatically start when TCP/IP is started, you should specify AUTOSTART (*YES) for those profiles. It might be useful to set the profiles to automatically start with TCP/IP in these types of situations:
- You want to have a constant dialup connection to the ISP.
- You schedule an IPL at midnight and you want the profiles to automatically start during the IPL.
Verify that the QTCPIP job is active. See Verify that necessary jobs exist for these instructions. The QTCPIP job must be active before you can start or end your interfaces.
Be aware that your line descriptions, network server descriptions, and network interface descriptions should be configured to vary on with TCP/IP. This allows these configuration objects to start at the same time TCP/IP starts. See Vary on communication lines, controllers, and devices for more information.