VOS_SETADDRS(1)

πŸ’– VOS_SETADDRS ✨

okay so bestie, welcome to VOS_SETADDRS(1) β€” it lives in the AFS Command Reference section of your man pages, and it's basically the "change my @ real quick" button for a file server's VLDB entry πŸŽ€


πŸ¦‹ NAME

vos_setaddrs β€” sets brand new addresses for a file server's entry in the VLDB πŸ’…


🌸 SYNOPSIS

vos setaddrs -uuid <UUID of server>
    -host <IP address>+
    [-cell <cell name>] [-noauth] [-localauth]
    [-verbose] [-encrypt] [-noresolve]
    [-config <config directory>]
    [-help]

vos seta -u <UUID of server>
    -ho <IP address>+
    [-c <cell name>]
    [-noa] [-l] [-v] [-e] [-nor]
    [-co <config directory>]
    [-h]

✨ DESCRIPTION

The vos setaddrs command sets the IP addresses for a server entry in the Volume Location Database (VLDB). You give it one or several IP addresses, and here's the tea: all the existing addresses in that VLDB server entry get replaced by whatever new addresses you put on the command line. Not appended. Replaced. poof πŸ’€

And if you need to hunt down the UUID for a server entry? Run vos listaddrs -printuuid and it'll show you every VLDB server entry with its UUID. iykyk 🫢


⚠️ CAUTIONS

okay so normally β€” and I mean normally β€” the best way to change a server entry's registered addresses is to restart the File Server process after you change that server's network configuration, and possibly after you change the NetInfo and NetRestrict files for that server too. Go read NetInfo(5) and NetRestrict(5) for the whole story on configuring the File Server so it registers the correct set of addresses.

This command can change the registered addresses without restarting the File Server, but heads up: the next time the File Server gets restarted, it will register all of its known addresses again. So before you ever use this command, always make sure the File Server configuration is correct for whenever it is next restarted. no exceptions bestie πŸ™ˆ

πŸ’€ Setting the wrong addresses will make the volumes on that file server unreachable from AFS clients. Literally unreachable. We don't want that energy.

And for the history girlies: this command was introduced in OpenAFS 1.5.74, but it can be used with any version of the Volume Location Server. periodt πŸ‘‘


πŸ’… OPTIONS

  • -uuid <UUID of server> β€” the unique ID, exactly as vos listaddrs -printuuid hands it to you.
  • -host <IP address>+ β€” the new list of IP addresses for the File Server. give it one, give it many, she's flexible πŸ’–
  • -cell <cell name> β€” names the cell in which to run the command. Do not combine this argument with the -localauth flag. More deets in vos(1).
  • -noauth β€” assigns the unprivileged identity anonymous to the issuer. Do not combine this flag with the -localauth flag. More deets in vos(1).
  • -localauth β€” constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The vos command interpreter then presents it to the Volume Server and Volume Location Server during mutual authentication. Do not combine this flag with the -cell argument or the -noauth flag. More deets in vos(1).
  • -verbose β€” produces a detailed trace of the command's execution on the standard output stream. Skip it, and only warnings and error messages show up. πŸ™ˆ
  • -encrypt β€” encrypts the command so the operation's results aren't transmitted across the network in clear text. Available in OpenAFS versions 1.4.11 or later and 1.5.60 or later. πŸ”₯
  • -noresolve β€” shows all servers as IP addresses instead of the DNS name. Super useful when the server address is registered as 127.0.0.1, or when you're dealing with multi-homed servers. Available in OpenAFS versions 1.4.8 or later and 1.5.35 or later.
  • -config <configuration directory> β€” sets the location of the configuration directory to use. Defaults to /etc/openafs β€” except if -localauth is specified, in which case the default is /etc/openafs/server. This option lets you use alternative configuration locations for testing purposes. 🧚
  • -help β€” prints the online help for this command. All other valid options are just ignored. iconic.

🌈 EXAMPLES

The following command sets addresses 192.12.107.214 and 10.47.11.17 for the UUID 008f157e-bad0-157c-0ffee-357c4d1faa77:

% vos setaddrs -uuid 008f157e-bad0-157c-0ffee-357c4d1faa77 \
    -host 192.12.107.214 -host 10.47.11.17 -verbose
vos: Changed UUID with addresses:
UUID: 008f157e-bad0-157c-0ffee-357c4d1faa77
192.12.107.214
10.47.11.17

ate that πŸ’…βœ¨


πŸ‘‘ PRIVILEGE REQUIRED

The issuer must be listed in the /etc/openafs/server/UserList file on each database server machine. no shortcuts, bestie.


πŸ”— SEE ALSO

CellServDB(5), NetInfo(5), NetRestrict(5), UserList(5), sysid(5), fileserver(8), vos(1), vos_listaddrs(1), vos_remaddrs(1)


KTH 2010. All Rights Reserved.

This documentation is covered by the IBM Public License Version 1.0.


and that's the whole page, bestie 🫢 this OpenAFS drop is dated 2026-07-27, and it's the VOS_SETADDRS(1) girlie herself. go set those addresses (correctly, please) πŸ’œπŸŒΈπŸ¦‹

πŸ“¦ where this page comes from