This setting allows you to specify alternate server mount interfaces for Files NFS subclients in case the main interface, identified by the filer name, encounters a mounting issue. You can define multiple alternative interfaces for each share while ensuring the share name stays the same. The configuration uses a JSON format. For example, if you have subclient content defined as `filername:/share1` and `filername:/share2`, you might specify the interfaces as follows: `{"shares":[{"name":"filername:/share1","interfaces":["alternate1a","alternate1b"]},{"name":"filername:/share2","interfaces":["alternate2a","alternate2b"]}]}`. For more readability, you can structure it as: `{ "shares": [ { "name": "filername:/share1", "interfaces": [ "alternate1a", "alternate1b" ] }, { "name": "filername:/share2", "interfaces": [ "alternate2a", "alternate2b" ] } ] }`. Alternatively, to apply the same interfaces across all shares, you can use a default entry: `{ "shares": [ { "name": "default", "interfaces": [ "alternate1a", "alternate1b" ] } ] }`.
Details
| Setting name: | AlternateServerInterface |
|---|---|
| Category: | FileSystemAgent |
| Created on: | Subclient |
| Type: | String |
| Supported versions: | 11.36 and higher |
| Requires restart: | No |