Additional Virtualization Discussions

Configure GRID Network on RedHat Docker Implementation

chrisbethel
3,302 Views

Setup:

 

3 physical RedHat 7.3 servers utilizing docker 1.12

 

Server01 has Admin Node (AN) and Storage Node 1 (SN1)

  • Host IP 192.168.130.65 (Copper Mgmt on VLAN 130)
  • Host bonded pair IP 192.168.135.65 (fiber Ethernet data connection on VLAN 135)
    • AN IP - 192.168.130.68
    • AD GRIP IP - 192.168.135.165
    • SN1 IP - 192.168.135.167

Server02 has Gateway Node (GN) and Storage Node 2 (SN2)

  • Host IP 192.168.130.66
  • Host bonded pair IP 192.168.135.66
    • GW GRID IP - 192.168.135.66
    • SN2 GRID IP - 192.168.135.168

 

Server03 has Storage Node 3 (SN3)

  • Host IP 192.168.130.67
  • Host bonded pair IP 192.168.135.67
    • SN3 GRID IP - 192.168.135.169

 

.135.x is the GRID Network

.130.x is the MGMT Network

 

Unable to communicate and unsure if we are configuring this properly. There aren't any instructions about utilizing different networks on the Nodes and Hosts. This is requirement by our customer to have the Backup Network virtually separated from the Mgmt Network (hence the VLANs). 

 

Would like some guidance on configuration. Please feel free to ask any additional questions that may lead to a solution.

 

thanks.

1 ACCEPTED SOLUTION

chrisbethel
3,273 Views

Found that the configurations were correct, the issue seemed to reside on the switch as we were running bonded pair for the ethernet, we learned that the switchport mode needed to not be set as trunk but rather access.

 

Additionally, we found that Server02 needed the bond to be rebuilt.

View solution in original post

1 REPLY 1

chrisbethel
3,274 Views

Found that the configurations were correct, the issue seemed to reside on the switch as we were running bonded pair for the ethernet, we learned that the switchport mode needed to not be set as trunk but rather access.

 

Additionally, we found that Server02 needed the bond to be rebuilt.

Public