AAA, NAC, Guest Access & BYOD

How to drop a subscriber node properly from the CLI
Requirement:

How to drop a subscriber node properly from the CLI  (appadmin login)?

 



Solution:

 

We have a supported command in CLI through appadmin login:

# cluster drop-subscriber

But we have to use this command with correct parameters as recommended by Aruba.

We have to specify parameter -i to specify the subscriber's MGMT IP address which need to be dropped.

# cluster drop-subscriber -i <IP Address>

Note:  Without using the parameter -i will make the current node to get dropped from the cluster, if the node is a subscriber.

Similarly, we can use other required parameters as per the requirement.

-f              -- force drop a node even if it is down
-s              -- do not reset the database on the dropped node
-b              -- skip generating a backup before this operation



Configuration:

Login to the CLI  with the username as appadmin and your cluster password as password.

Run the following command to see the list of nodes in the cluster:

 

[appadmin@CPPM]# cluster list

Publisher  : Management port IP=10.17.164.156   Data port IP=None  [local machine]
Subscriber : Management port IP=10.17.164.233   Data port IP=None

 

If we try to drop the subscriber node without using the parameter -i, server would try to drop itself from the cluster. if the node is subscriber, it will get dropped.

We would get below error in case we try on a Publisher's CLI:

[appadmin@CPPM]# cluster drop-subscriber 10.17.164.233
INFO - Request to drop local node
ERROR - Cannot drop publisher node
ERROR - Dropping node with management IP=None failed.

Always remember to use the parameter -i to specify the required  subscriber node's management IP address.

Format:

#drop-subscriber [-f] [-i <IP Address>] [-s] [-b]

 

-f              -- force drop a node even if it is down

-i <IP Address> -- management IP Address of the node to be dropped.
                       If not specified the current node is dropped from
                       cluster, if the node is a subscriber
-s              -- do not reset the database on the dropped node
-b              -- skip generating a backup before this operation

    Default action is to drop the current node from cluster (if the node is subscriber).
    When run on publisher, the command can be used to drop any node in the cluster



Verification

 

Able to drop the desired node from the CLI successfully by using the command with correct format.

[appadmin@CPPMVM1]# cluster drop-subscriber -i 10.17.164.233 -s -b
INFO - Removed node entry from database
INFO - Notified publisher that subscriber node is deleted
INFO - Attempting remote drop of the subscriber node...
INFO - 10.17.164.233: - Stopping services
INFO - 10.17.164.233: - Starting services
INFO - 10.17.164.233: - Restarting Policy Manager admin server

 

 

Version History
Revision #:
2 of 2
Last update:
‎03-17-2017 04:47 PM
Updated by:
 
Labels (1)
Contributors
Search Airheads
Showing results for 
Search instead for 
Did you mean: 
Is this a frequent problem?

Request an official Aruba knowledge base article to be written by our experts.