Solved

Documentation for steps to validate Hyperscale 1.5 that was configured already

  • 17 September 2021
  • 7 replies
  • 48 views

Badge +5

Hello,

 

I have HS 1300 ( HS 1.5) appliance deployed couple of years ago which came up with the RHEL 7.4.

unfortunately the folks who involved during deployment has left the organization and no where the infromation maintained except the login credentials do we have any documentation link or steps to be followed to gather the information like below

 

ports details 

bonds details ( which ports been part of bond)

and disk details , etc

 

 

 

 

icon

Best answer by Mike Struening RETIRED 7 October 2021, 20:12

View original

7 replies

Userlevel 7
Badge +23

Hi @Srikanth K !

Here are some details to start:

Disk details:

https://documentation.commvault.com/commvault/v11/article?p=104617.htm

For the bonding and ports/IPs used, I might be able to find the original document used to collect any IPs, used (but that assumes nothing has changed, which they likely have not) if we can’t get you the info in a better way.

I’ll find out how you can call up these items in the environment and get a response here.

Userlevel 7
Badge +23

@Srikanth K , I have answers for you!

When the install was done, they saved the config files for reference:

https://documentation.commvault.com/11.24/expert/117200_saving_configuration.html

If you can’t find them, you can restore them:

https://documentation.commvault.com/11.24/expert/117255_restoring_saved_configuration.html

Let me know if that answers your questions.

Badge +5

Thanks Mike, I got the saved configuration seams we have multiple VLAN using but the bond files not letting me give idea on which ports are been part of the bond.

 

Thanks

Srikanth K

Userlevel 7
Badge +23

@Srikanth K , send me a pm with your Account Name and when the appliance was configured.  I may be able to track down the configuration document.

Badge +5

Thanks Mike!

Userlevel 7
Badge +23

Thanks!  I replied to the pm.

Userlevel 7
Badge +23

Updating thread.  Details can be pulled via Linux networking commands.

Reply