Creating a cluster in a secure VLAN network
Create a cluster with servers that
are found in the same secure VLAN network.
Note that it
is up to the system administrator to ensure that each VLAN ID is not
shared across clusters.
Procedure
- Configure the SNMP setting on your network switches. See more on Configuring the SNMP setting on your network switch.
- Configure switch connection ports to allow VLAN access
across all switches in the VLAN network. For example,
assume port 1 on switch1 is connected to port 2
of switch2.
- Set up the following configuration on port 1:
RS G8052(config)#interface port 1 RS G8052(config-if)#tagging WARNING: IP interface 1 and IP interface 48 have overlapped subnets. RS G8052(config-if)# RS G8052(config)#show interface information Alias Port Tag RMON Lrn Fld PVID NAME VLAN(s) ------- ---- --- ---- --- --- ----- -------------- ---------- 1 1 y d e e 1 1 2 2 n d e e 1 1 3 3 n d e e 1 1 4 4 n d e e 1 1 5 5 n d e e 1 1 6 6 n d e e 1 1 7 7 n d e e 1 1 - Set up the following configuration on port 2 on switch
2:
RS G8052(config)#interface port 2 RS G8052(config-if)#tagging WARNING: IP interface 2 and IP interface 48 have overlapped subnets. RS G8052(config-if)# RS G8052(config)#show interface information Alias Port Tag RMON Lrn Fld PVID NAME VLAN(s) ------- ---- --- ---- --- --- ----- -------------- ---------- 1 1 n d e e 1 1 2 2 y d e e 1 1 3 3 n d e e 1 1 4 4 n d e e 1 1 5 5 n d e e 1 1 6 6 n d e e 1 1 7 7 n d e e 1 1
- Set up the following configuration on port 1:
- Create a VLAN. For example, create a VLAN
with ID 11:
RS G8052(config)#vlan 11 VLAN number 11 with name "VLAN 11" created. WARNING: IP interface 1 and IP interface 48 have overlapped subnets. Warning: VLAN 11 was assigned to STG 11. RS G8052(config-vlan)#enable WARNING: IP interface 1 and IP interface 48 have overlapped subnets. RS G8052(config-vlan)#exit RS G8052(config)#write Copy running configuration to startup configuration RS G8052(config)# - Define switches in Platform
Cluster Manager Community Edition.
- Add a switch object into the switches table on the Platform
Cluster Manager Community Edition management
node with root privilege. The switch object must specify the switch
hostname, SNMP version, and authentication information.
# tabedit switches #switch,snmpversion,username,password,privacy,auth,linkports,sshusername, sshpassword,protocol,switchtype,comments,disable "switch1","3","pcm","password",,"md5",,,,,,, "switch2","3","pcm","password",,"md5",,,,,,, - Add the IP address of the switch to /etc/hosts:
# echo "192.168.1.1 switch1" >> /etc/hosts # echo "192.168.1.2 switch2" >> /etc/hosts
- Add a switch object into the switches table on the Platform
Cluster Manager Community Edition management
node with root privilege. The switch object must specify the switch
hostname, SNMP version, and authentication information.
- Create a node information file that specifies the switches
that are used. The node information file must specify the switch name,
port number, and network interface. Note: Both the provisioning NIC and the NIC that belong to the VLAN must be specified. In the case where two NICs are used for a node, ensure that the switch is listed twice in the node information file.For example:
For more examples, see more on the Node information file.__hostname__: switches=eth0!switch1!1,eth1!switch1!2,eth2!switch2!1 - Using the node information that is created in the previous
step, import nodes into the system. See more on Adding nodes using a node information file. Note: Nodes that are added to the system, are only available to use after provisioning is completed.
- Create a secure VLAN network in the Web Portal. Make sure to define the VLAN ID as specified in step 3. See more on Adding an IP pool.
- Define a network profile that uses the newly created secure VLAN network. See more on Adding a network profile. Make sure that the VLAN network is associated to one ore more of the non-provisioning interfaces to which the VLAN is configured to.
- Create a cluster template that uses the secure VLAN network. The cluster template must use a network profile that specifies the secure VLAN network. See more on Creating a cluster template for a secure VLAN network.
- Publish the cluster template to make it available for use. See more on Publishing a cluster template.
- Finally, create the cluster from the published cluster template. See more on Publishing a cluster template.