Skip to main content
commvault.com commvault.com
Solved

HyperScale X override Commvault tunnel port

V
Byte
Forum|alt.badge.img+1

Hi all,

My customer use a specific commvault tunnel port instead of default one. We have installed fresh HSX reference architecture in 11.32.

We have noticed that by disabling firewall on HSX node, commvault firewall is working, rather than when it’s enabled, probably due to default rule allowing the default commvault tunnel port (8403)

It’s referred on this link : https://documentation.commvault.com/2023e/essential/firewall_port_requirements_for_hyperscale_x_reference_architecture.html

Is there any way to allow a rule in firewalld to override default commvault firewall tunnel port (8403) to a specific port currently used in my customer commvault environment ?

 

Many Thanks

Vincent

 

 

Best answer by R Anwar

Hi @Vincent633 

With SP32 firewall uses a default config. In case you want to manually update, changes need to be made to /usr/lib/firewalld/services/commvault.xml.

We are coming up with option to have additional ports in newer SP release.

Regards,

View original
    Did this answer your question?

    2 replies

    R Anwar
    Vaulter
    Forum|alt.badge.img+10
    • R AnwarVaulter
    • Vaulter
    • 115 replies
    • Answer
    • July 25, 2024

    Hi @Vincent633 

    With SP32 firewall uses a default config. In case you want to manually update, changes need to be made to /usr/lib/firewalld/services/commvault.xml.

    We are coming up with option to have additional ports in newer SP release.

    Regards,

    V
    Byte
    Forum|alt.badge.img+1
    • Vincent633
    • Author
    • Byte
    • 1 reply
    • July 25, 2024

    Hi,

    Many thanks for your reply.

    We will configure back to default port.

     

    regards,

    Reply


    Most helpful members this week

    Terms & ConditionsCookie settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie settings