fs_getclientaddrs(1) [x11r4 man page]
FS_GETCLIENTADDRS(1) AFS Command Reference FS_GETCLIENTADDRS(1) NAME
fs_getclientaddrs - Displays the client interfaces to register SYNOPSIS
fs getclientaddrs [-help] fs gc [-h] fs getcl [-h] DESCRIPTION
The fs getclientaddrs command displays the IP addresses of the interfaces that the local Cache Manager registers with a File Server when first establishing a connection to it. The File Server uses the addresses when it initiates a remote procedure call (RPC) to the Cache Manager (as opposed to responding to an RPC sent by the Cache Manager). There are two common circumstances in which the File Server initiates RPCs: when it breaks callbacks and when it pings the client machine to verify that the Cache Manager is still accessible. If an RPC to that interface fails, the File Server simultaneously sends RPCs to all of the other interfaces in the list, to learn which of them are still available. Whichever interface replies first is the one to which the File Server then sends pings and RPCs to break callbacks. fs_setclientaddrs(1) explains how the Cache Manager constructs the list automatically in kernel memory as it initializes, and how to use that command to alter the kernel list after initialization. CAUTIONS
The File Server uses the list of interfaces displayed by this command only when selecting an alternative interface after a failed attempt to break a callback or ping the Cache Manager. When responding to the Cache Manager's request for file system data, the File Server replies to the interface which the Cache Manager used when sending the request. If the File Server's reply to a data request fails, the file server machine's network routing configuration determines which alternate network routes to the client machine are available for resending the reply. The displayed list applies to all File Servers to which the Cache Manager connects in the future. It is not practical to register different sets of addresses with different File Servers, because it requires using the fs setclientaddrs command to change the list and then rebooting each relevant File Server immediately. The displayed list is not necessarily governing the behavior of a given File Server, if an administrator has issued the fs setclientaddrs command since the Cache Manager first contacted that File Server. It determines only which addresses the Cache Manager registers when connecting to File Servers in the future. The list of interfaces does not influence the Cache Manager's choice of interface when establishing a connection to a File Server. OPTIONS
-help Prints the online help for this command. All other valid options are ignored. OUTPUT
The output displays the IP address of each interface that the Cache Manager is currently registering with File Server processes that it contacts, with one address per line. The File Server initially uses the first address for breaking callbacks and pinging the Cache Manager, but the ordering of the other interfaces is not meaningful. EXAMPLES
The following example displays the two interfaces that the Cache Manager is registering with File Servers. % fs getclientaddrs 192.12.105.68 192.12.108.84 PRIVILEGE REQUIRED
None SEE ALSO
fileserver(8), fs_setclientaddrs(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 FS_GETCLIENTADDRS(1)
Check Out this Related Man Page
FS_SETCLIENTADDRS(1) AFS Command Reference FS_SETCLIENTADDRS(1) NAME
fs_setclientaddrs - Sets the client interfaces to register with the File Server SYNOPSIS
fs setclientaddrs [-address <client network interfaces>+] [-help] fs setcl [-a <client network interfaces>+] [-h] fs sc [-a <client network interfaces>+] [-h] DESCRIPTION
The fs setclientaddrs command defines the IP addresses of the interfaces that the local Cache Manager registers with a File Server when first establishing a connection to it. The File Server uses the addresses when it initiates a remote procedure call (RPC) to the Cache Manager (as opposed to responding to an RPC sent by the Cache Manager). There are two common circumstances in which the File Server initiates RPCs: when it breaks callbacks and when it pings the client machine to verify that the Cache Manager is still accessible. The list of interfaces specified with this command replaces the list that the Cache Manager constructs and records in kernel memory as it initializes. At that time, if the file /etc/openafs/NetInfo exists on the client machine's local disk, the Cache Manager uses its contents as the basis for the list of interfaces addresses. If the file does not exist, the Cache Manager instead uses the network interfaces configured with the operating system. It then removes from the list any address included in the local /etc/openafs/NetRestrict file. It records the final list in kernel memory. (An administrator must create the NetInfo and NetRestrict files; there are no default versions of them.) If an RPC to that interface fails, the File Server simultaneously sends RPCs to all of the other interfaces in the list, to learn which of them are still available. Whichever interface replies first is the one to which the File Server then sends pings and RPCs to break callbacks. To list the interfaces that the Cache Manager is currently registering with File Servers, use the fs getclientaddrs command. CAUTIONS
The list specified with this command persists in kernel memory only until the client machine reboots. To preserve it across reboots, either list the interfaces in the local /etc/openafs/NetInfo file, or place the appropriate fs setclientaddrs command in the machine's AFS initialization script. Changes made with this command do not propagate automatically to File Servers to which the Cache Manager has already established a connection. To force such File Servers to use the revised list, either reboot each file server machine, or change the NetInfo file and reboot the client machine. The fs command interpreter verifies that each of the addresses specified as a value for the -address argument is actually configured with the operating system on the client machine. If it is not, the command fails with an error message that marks the address as a "Nonexistent interface". OPTIONS
-address <client network interfaces>+ Specifies each IP address to place in the list of interfaces, in dotted decimal format. Hostnames are not acceptable. Separate each address with one or more spaces. -help Prints the online help for this command. All other valid options are ignored. OUTPUT
The message Adding <interface> confirms that each new interface was added to the Cache Manager's list. The address appears in hexadecimal format to match the notation used in the File Server log, /var/log/openafs/FileLog. EXAMPLES
The following example sets the two interfaces that the Cache Manager registers with File Servers. % fs setclientaddrs 191.255.105.68 191.255.108.84 Adding 0xbfff6944 Adding 0xbfff6c54 PRIVILEGE REQUIRED
The issuer must be logged in as the local superuser root. SEE ALSO
NetInfo(5), NetRestrict(5), fileserver(8), fs_getclientaddrs(1) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 FS_SETCLIENTADDRS(1)