LCTL-NODEMAP_BANLIST_ADD(8)

NAME
lctl-nodemap_banlist_add - define a range of banned NIDs for a nodemap

SYNOPSIS
lctl nodemap_banlist_add or
lctl nodemap banlist_add [--name NODEMAP_NAME] --range NID_RANGE

DESCRIPTION
nodemap_banlist_add adds a range of banned NIDs to an existing nodemap, either a normal or the default nodemap. For normal nodemaps, the banned NID range must be included into a regular NID range associated with the nodemap. For the default nodemap, the added range of banned NIDs must not conflict with any NID range defined on any other nodemap.
If the --name option is omitted, the nodemap to add the banlist to will be inferred from the existing NID ranges that include the provided ban range. If none is found, the default nodemap will be used.
Clients with NIDs that fall into the banned range will be blocked by servers, and will get 'Operation not permitted' for all requests except unmount. The banning happens as soon as the nodemap definition is propagated to the servers. As long as a client is banned, it cannot mount Lustre.

OPTIONS

--name NODEMAP_NAME
    The name of the nodemap that this banned NID range should be added to. It may be 'default' and will accept any NID not in another nodemap.

--range NID_RANGE
    The banned NID range that should be added to the nodemap. The syntax is the same as the regular NID range, as detailed in lctl-nodemap-add-range(8).

EXAMPLES
    # lctl nodemap_banlist_add --name remotesite --range 192.168.1.[1-254]@tcp
    # lctl nodemap_banlist_add --name othersite --range 192.168.2.[1-254]@tcp

AVAILABILITY
lctl nodemap_banlist_add is part of the lustre(7) filesystem package since release 2.16.56.

SEE ALSO
lustre(7), lctl-nodemap-activate(8), lctl-nodemap-add-idmap(8), lctl-nodemap-add-range(8), lctl-nodemap-banlist-del(8), lctl-nodemap-del(8), lctl-nodemap-del-idmap(8), lctl-nodemap-del-range(8), lctl-nodemap-modify(8) lctl-nodemap-new(8),