Using the NISH client in 1:n manager mode

Prerequisites

Review the following requirements before using the NISH client in 1:n manager mode.

A working NISH manager with known IP address and port number are required; see NISH manager.
If the NISH manager is on a different host from the NISH client, the firewall permissions between the NISH client and the NISH manager must be set correctly.

To use the NISH client in 1:n manager mode, perform the following steps:

Procedure

Execute the nish command from the command line, providing the IP address and port number to which the NISH manager service is bound:
nish [OPTIONS] [-s local-schema-file] -maddress:port

You can specify the IP address and port number of the NISH manager with the --manager option or -m flag, in a NISH rc file or in an environment variable; see NISH rc files.
Note: If the IP address and port number of the NISH manager are defined in environment variables or in a NISH rc file, you can enter the nish command without these arguments. The arguments defined using environment variables or in the NISH rc file must be supported in the current mode of operation. If arguments for another mode of operation are defined, the NISH client fails and returns an error.

The local schema file contains the details of the locally defined NISH MD-CLI schema; see Local schema file. For information about the other options, see Command options.

In the following example, the local schema file is absent and the NISH manager service is bound to IP address 127.0.0.1 (the localhost) and port number 57400:
```
[root@server ~]# nish -m 127.0.0.1:57400
```
Navigate and operate in NISH manager mode using the same methods used in NISH static mode.

The navigation and operation of NISH in manager mode is the same as in static mode. The NISH client makes direct connections to the nodes and traverses into them within the NISH MD-CLI; see Using the NISH client in 1:n static mode.

When the NISH client starts in manager mode, it makes a gRPC connection to the NISH manager service and obtains the inventory of nodes. The NISH manager uses an ON_CHANGE gRPC streaming method to ensure the inventory of nodes is continually updated.