Forum Discussion

Nbuhunter's avatar
Nbuhunter
Level 2
8 months ago
Solved

After Vlan Tagging , Flex 5360 instances Showing storage Server down .

We planned to distribute two separate workloads across the two nodes of our FLEX 5360 HA system. For testing purposes, we implemented VLAN tagging on one node. However, this resulted in storage server failures and backup disruptions. When we migrated the instances to the non-VLAN tagged node, the storage server functioned correctly, and backups resumed as expected. We confirmed that VLAN tagging was configured correctly on both the node and the network switch. Please advise if any additional steps are necessary to achieve our goal.


  • Solution:

    After configuring VLANs on the network switch and NetBackup Flex appliance node, we need to edit the instance network settings for the management pair. This involves adding the allowed VLAN bonding interface and changing the default gateway to the new VLAN gateway. After making these changes, the specific instance will be able to access the particular VLAN using the new network route.

3 Replies

  • Hi

    Can you provide details of how you configured the VLAN tagging?
    Normally each node in a HA pair have their network configured the same so the instances can connect to the correct networks as they move over. 

    I can understand backup issues if the networking to the media server instance is problematic - due to VLAN mismatch etc. It's possible the storage server failures reported are related to the networking. 

    Cheers

     

  • I assume you are using LACP on both nodes.
    can you have connect to each flex via SSH, login to the shell and provide the network configuration.
    share result for below commands:
    #cat /proc/net/bonding/<bondName>
    #ip link show 
    Please also share screenshot of network configuration page on flex console Web

     

  • Solution:

    After configuring VLANs on the network switch and NetBackup Flex appliance node, we need to edit the instance network settings for the management pair. This involves adding the allowed VLAN bonding interface and changing the default gateway to the new VLAN gateway. After making these changes, the specific instance will be able to access the particular VLAN using the new network route.