Chapter 7. NFS Startup, Shutdown, and Recovery

NFS startup performs separately and independently on each machine. The startup of an NFS component on one system does not trigger the startup of an NFS component on another system. For example, if you start the Network Lock Manager on a client, the NLM on the server will not automatically start up. For proper functioning of NFS, there is an implied order in which the daemons should be started on any given system or network.

For example, on a given server system, users should use the export command before starting the mount daemon and NFS server. On a given client system, users should start the block I/O daemons before using the mount command. In the network, the NFS server daemon must be operational on a given machine before an NFS client on another system can successfully issue any requests to that server. Similarly, the mount daemon on a given system must be operational before another machine can successfully issue a mount request to that daemon.

Administrators have the ability to start and end NFS servers and clients at any time, in any order. This action will not cause error messages to be issued. However, it is recommended that users should start and end NFS in the order that is speci®ed below for best operation.

Note: Remember not to start File Server Support/400 and NFS at the same time. Only one of these system applications can operate on AS/400 at any given time. If TCP/IP File Server Support/400 (FSS/400) is operating at the time of NFS startup, the RPC Binder Daemon (port mapper) will fail to connect to port 111. Furthermore, the RPC daemon will not be able to assign any ports to server processes. We recommend that you always use OS/400 Network File System Support.

 

 

 

Con®guring TCP/IP

You must install and properly con®gure TCP/IP prior to starting NFS support for the

®rst time. NFS uses the system con®guration to determine the local system name.

There must be an entry in the hosts table for both the ″short″ and ″long″ name,

unless you are using a Domain Name Server (DNS). Perform the following steps to

correctly con®gure TCP/IP and its options:

1.

Go to the Con®gure TCP/IP menu (CFGTCP).

2.

Select option 12 (Change TCP/IP Domain or CHGTCPDMN).

 

You can ®nd the short name in the Host name parameter. The long name is the

 

short name appended by a '.' and the Domain name (the next parameter). For

 

example, ASHOST01 is a short name, and ASHOST01.NETWORK.DOMAIN.COM is a long

 

name.

3.

Update information if needed.

 

The Host name search priority tells the system the order in which to try to

 

resolve host names. *LOCAL means to search the TCP/IP host table ®rst, and

 

*REMOTE says to use a DNS ®rst at the speci®ed IP address. If you do not

 

need to update information on this screen, press PF12.

4.

Select option 10 (Work with TCP/IP Host Table Entries).

5.

Verify that there is both a long and short host name entry for the IP address of

 

the local system. If you do not know this address, select option 1 from the

 

CFGTCP menu. Additionally, you can select one of the two following options:

© Copyright IBM Corp. 1997, 1999

65

Page 83
Image 83
IBM AS/400E manual NFS Startup, Shutdown, and Recovery, Conguring TCP/IP

AS/400E specifications

The IBM AS/400E, now more commonly known as IBM i, is a robust and versatile midrange server that has been designed to provide a comprehensive computing solution for businesses of all sizes. First introduced in the late 1980s, the AS/400 series has undergone multiple enhancements and rebranding, with the AS/400E being one of the notable iterations. This powerful platform is closely associated with IBM's commitment to reliability, scalability, and integrated business solutions.

One of the main features of the AS/400E is its highly integrated architecture that combines hardware and software into a cohesive system. This integration allows for seamless operations, reducing the complexity typically associated with managing disparate systems. The system is powered by IBM's proprietary OS/400 operating system, which has evolved into IBM i, featuring advanced capabilities like object-oriented programming, integrated database management, and security features that are essential for enterprise environments.

A key characteristic of the AS/400E is its robust database support, primarily through the use of DB2 for i. This integrated database management system enables efficient data handling and retrieval, facilitating real-time business analytics and reporting. Furthermore, the platform supports a variety of programming languages, including RPG, COBOL, and Java, making it flexible for developers who require diverse tools for application development.

The AS/400E is also known for its exceptional reliability and uptime, making it a preferred choice for critical business applications in industries such as finance, healthcare, and manufacturing. This reliability is backed by advanced error detection and correction mechanisms, as well as redundancy features that help prevent data loss and minimize downtime.

In terms of scalability, the AS/400E can effortlessly expand to accommodate growing business demands. Organizations can increase processing power by adding more resources without significant disruption. This scalability, combined with the system’s built-in virtualization capabilities, allows businesses to optimize resource usage and streamline operations.

Security is another defining feature of the AS/400E. The platform incorporates various layers of security measures, including user authentication, encryption, and comprehensive auditing capabilities, ensuring that sensitive business data is protected against unauthorized access.

Overall, the IBM AS/400E remains a powerful tool in the enterprise computing landscape, providing businesses with an integrated, reliable, and secure solution for their technological needs. Its enduring popularity is a testament to its capability to evolve with changing business requirements while maintaining its core attributes of high performance and stability.