IBM Storage Defender

IBM Storage Defender

Early threat detection and secure data recovery

 View Only

  • 1.  iris_cli help?

    Posted Thu June 12, 2025 02:01 PM

    We've been implementing and using local Defender DataProtect clusters in our on-prem datacenters as well as deploying ROBO images in remote locations for better protection of our environments.  All is going according to plan but I would love to get a better understanding and knowledge around the iris_cli command line options available.

    I currently have a need to "re-IP" one of those remote sites and that will involve modifying the IP configuration on the ROBO at that site.  I've been playing around with the iris_cli available options but up to now, no luck.

    This command for example, is available, but seems to be no longer supported and hence, fails.

    # cluster update-interfaces interface-ips="xx.xx.xx.xx subnet-gateway=xx.xx.xx.xx subnet-mask-bits=xx

    There is also this command, which i've tried many alterations and no go either.

    # ip config interface-name=intf_group1 interface-ips=xx.xx.xx.xx subnet-gateway=xx.xx.xx.xx subnet-mask-bits=xx

    It is most likely (hopefully), something really minor that i need to adjust but have not yet found it.

    1. Has anyone played with the iris_cli commands and would you be willing to share a few examples?
      1. Is there a REAL document somewhere that i could refer to?
    2. Does IBM "fully" support the iris_cli commands?
      1. Maybe, being a rebranded Cohesity product, some of those commands will not work in an IBM version?
    3. I've opened a case at IBM support...but no luck with them either

    Thank you for any input!

    #IBMStorageDefender #DataProtectionSoftware

    Steph



    ------------------------------
    Stephan Durand
    Manager Information Technology – Storage & Backups, Disaster Recovery & Infra *NIX
    Rona Inc
    Boucherville QC
    5145995900
    ------------------------------


  • 2.  RE: iris_cli help?

    Posted Thu August 07, 2025 09:04 AM

    Not to revive this old post, but at least add some information to it.  So, for those interested, it is actually feasible to do so, but a little cumbersome.  

    The "general" steps are as follows:

    Log into cluster and stop cluster services

Then into a secured shell, fetch cluster_config.

Within the cluster_config file, make the following changes to the IP information in the file:
a. Update the cluster_subnet ip and netmask.
b. Update the IP address under the node_vec ip and node_interface_vec ip sections.
c. Update the subnet ip information and netmask_bits if changing the subnet mask as well if needed.
d. Update the gateway if needed.
e. Update the cluster_partition_vec host_name entry if it has the IP listed.
f. Update the cluster_gateway entry if needed.
g. Update the cluster_network_vec hostname, ip and netmask_ipv4 entry if needed.
h. Update the static_route_vec next_hop entry for the default route with the new gateway ip if needed.

Then push the cluster_config to take the changes.

Once that is done, you will need to update network config to update the IP on the interface.

~/bin/network/configure_network.sh

Then reboot the ROBO to have it take effect.

    Maybe it is worth doing a little blog for this...I think I will write one up.


    Thanks to Sean at IBM support for the help.



    ------------------------------
    Stephan Durand
    Manager Information Technology – Storage & Backups, Disaster Recovery & Infra *NIX / IBMi
    ------------------------------

    Original Message


Related Content