Kiril at 13:23, 27 January 2011

2011-01-27T13:23:20Z

Kiril at 13:21, 27 January 2011

2011-01-27T13:21:34Z

Root: New page:
Switch Management

The cluster is connected via two Cisco Catalyst 3560G switches. The ingress bandwidth on...

2010-08-18T10:44:27Z

New page: Switch Management The cluster is connected via two Cisco Catalyst 3560G switches. The ingress bandwidth on...

New page

Switch Management
The cluster is connected via two Cisco Catalyst 3560G switches.
The ingress bandwidth on any physical port can be configured to any value between
8kb/s and 1Gb/s. The switches are connected to each other via a gigabit sfp
cable.
As the <a href="Specs.html">Cluster Specifications</a>
show, each node has two Network Interfaces, each with its own IP Address. Each
eth0 is connected to switch 1, and each eth1 is connected to switch 2. Which
topology you wish to use will determine which IP address you should use when
referring to each machine. 
 
Switch Access
The switches can be accessed through telnet from any machine
on the cluster network. Type 
telnet 192.168.21.252 for switch1 or telnet 192.168.21.253 for switch2, and
the switch should prompt for a password. For the password, email brett becker.
 
Switch Configuration
 
For example, we will demonstrate how to limit the bandwidth of the connection
between hcl01 and hcl02 to 100Mbps: 
----------------------------------- 
hcl02 $> telnet 192.168.21.252 
     Trying 192.168.21.252... 
     Connected to 192.168.21.252 (192.168.21.252). 
     Escape character is '^]'.
    User Access Verification
Password: <enter password> 
hclswitch1>enable 
     Password: <enter password> 
hclswitch1#configure terminal 
     Enter configuration commands, one per line. End with CNTL/Z. 
hclswitch1(config)#policy-map example 
hclswitch1(config-pmap)#class ipclass1 
hclswitch1(config-pmap-c)#police 100000000 800000 exceed-action drop 
hclswitch1(config-pmap-c)#exit 
hclswitch1(config-pmap)#exit 
hclswitch1(config)#interface gigabitEthernet0/3 
hclswitch1(config-if)#service-policy input example 
hclswitch1(config-if)#exit 
hclswitch1(config)#interface gigabitEthernet0/4 
hclswitch1(config-if)#service-policy input example 
hclswitch1(config-if)#exit 
hclswitch1#show policy-map 
   Policy Map example 
    Class ipclass1 
     police 100000000 800000 exceed-action drop 
hclswitch1#exit 
     Connection closed by foreign host.
hcl02 $> 
----------------------------------------
In the above example, we telnet to the switch and enter the
password. We then type “enable” and enter the password again. Then
we type “configure terminal” to bring us into config mode. We then
create a new policy-map named “example” We bind this policy-map
to class “ipclass1”. ipclass1 is a class that incorporates all ports
on the switch. PLEASE DO NOT REMOVE THIS CLASS! We then enter the key statement
police 100000000 800000 exceed-action drop. This tells the switch that this
policy-map is to limit the bandwidth to 100Mbps, with a bucket burst of 80000,
and if the rate is exceeded packets are to be dropped. We then exit policy-map
configuration and enter interface gigabitEthernet0/3. This is the port that
is connected to hcl03. We then attach the policy-map “example” to
this interface. We then do the same for port gigabitEthernet0/4 which is connected
to hcl04. The policy-map is then viewed using the show command to ensure that
it is correct. 
This example demonstrates an important fact about the cluster.
hcl01’s eth0 (192.168.21.3) is connected to port gigabitEthernet0/1 on
switch1. Similarly, hclx’s eth0 (192.168.21.x+2) is connected to gigabitEthernet0.x
on switch1. 
Further, hcl01’s eth1 (192.168.21.103) is connected to gigabitEthernet0/1
on switch2. Similarly, hclx’s eth1 (192.168.21.100+x+2) is connected to
gigabitEthernet0/x on switch2. 
The table below shows this comprehensively. 
<div align="center">
<table width="53%" border="1" cellpadding="0">
<tr>
<td width="20%">Machine</td>
<td width="23%">IP Address</td>
<td width="26%">Switch1 Port</td>
<td width="31%">Switch2 Port</td>
</tr>
<tr>
<td>hcl01</td>
<td>192.168.21.3</td>
<td>gigabitEthernet0/1</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl01_eth1</td>
<td>192.168.21.103</td>
<td>N/A</td>
<td>gigabitEthernet0/1</td>
</tr>
<tr>
<td>hcl02</td>
<td>192.168.21.4</td>
<td>gigabitEthernet0/2</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl02_eth1</td>
<td>192.168.21.104</td>
<td>N/A</td>
<td>gigabitEthernet0/2</td>
</tr>
<tr>
<td>hcl03</td>
<td>192.168.21.5</td>
<td>gigabitEthernet0/3</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl03_eth1</td>
<td><div align="left">192.168.21.105</div></td>
<td>N/A</td>
<td>gigabitEthernet0/3</td>
</tr>
<tr>
<td>hcl04</td>
<td>192.168.21.6</td>
<td>gigabitEthernet0/4</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl04_eth1</td>
<td>192.168.21.106</td>
<td>N/A</td>
<td>gigabitEthernet0/4</td>
</tr>
<tr>
<td>hcl05</td>
<td>192.168.21.7</td>
<td>gigabitEthernet0/5</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl05_eth1</td>
<td>192.168.21.107</td>
<td>N/A</td>
<td>gigabitEthernet0/5</td>
</tr>
<tr>
<td>hcl06</td>
<td>192.168.21.8</td>
<td>gigabitEthernet0/6</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl06_eth1</td>
<td>192.168.21.108</td>
<td>N/A</td>
<td>gigabitEthernet0/6</td>
</tr>
<tr>
<td>hcl07</td>
<td>192.168.21.9</td>
<td>gigabitEthernet0/7</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl07_eth1</td>
<td>192.168.21.109</td>
<td>N/A</td>
<td>gigabitEthernet0/7</td>
</tr>
<tr>
<td>hcl08</td>
<td>192.168.21.10</td>
<td>gigabitEthernet0/8</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl08_eth1</td>
<td>192.168.21.110</td>
<td>N/A</td>
<td>gigabitEthernet0/8</td>
</tr>
<tr>
<td>hcl09</td>
<td>192.168.21.11</td>
<td>gigabitEthernet0/9</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl09_eth1</td>
<td>192.168.21.111</td>
<td>N/A</td>
<td>gigabitEthernet0/9</td>
</tr>
<tr>
<td>hcl10</td>
<td>192.168.21.12</td>
<td>gigabitEthernet0/10</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl10_eth1</td>
<td>192.168.21.112</td>
<td>N/A</td>
<td>gigabitEthernet0/10</td>
</tr>
<tr>
<td>hcl11</td>
<td>192.168.21.13</td>
<td>gigabitEthernet0/11</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl11_eth1</td>
<td>192.168.21.113</td>
<td>N/A</td>
<td>gigabitEthernet0/11</td>
</tr>
<tr>
<td>hcl12</td>
<td>192.168.21.14</td>
<td>gigabitEthernet0/12</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl12_eth1</td>
<td>192.168.21.114</td>
<td>N/A</td>
<td>gigabitEthernet0/12</td>
</tr>
<tr>
<td>hcl13</td>
<td>192.168.21.15</td>
<td>gigabitEthernet0/13</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl13_eth1</td>
<td>192.168.21.115</td>
<td>N/A</td>
<td>gigabitEthernet0/13</td>
</tr>
<tr>
<td>hcl14</td>
<td>192.168.21.16</td>
<td>gigabitEthernet0/14</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl14_eth1</td>
<td>192.168.21.116</td>
<td>N/A</td>
<td>gigabitEthernet0/14</td>
</tr>
<tr>
<td>hcl15</td>
<td>192.168.21.17</td>
<td>gigabitEthernet0/15</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl15_eth1</td>
<td>192.168.21.117</td>
<td>N/A</td>
<td>gigabitEthernet0/15</td>
</tr>
<tr>
<td>hcl16</td>
<td>192.168.21.18</td>
<td>gigabitEthernet0/16</td>
<td>N/A</td>
</tr>
<tr>
<td>hcl16_eth1</td>
<td>192.168.21.118</td>
<td>N/A</td>
<td>gigabitEthernet0/16</td>
</tr>
</table>
</div>

 
Limiting the bandwidth between the two switches is similar to
the above example, but on switch1, Interface gigabitEthernet0/25 should be assigned
the desired policy-map. Then on switch2, the same should be done. 
 
Simulating Two Clusters
If you want to simulate two clusters with the cluster, the following
example should be considered.
Say we want Cluster A to be comprised of hcl01 and hcl02, and
Cluster B, to comprised of hcl03 and hcl04. We want hcl01 and hcl02 to “talk”
to each other at 10Mbps, and hcl03 and hcl04 to “talk” at 1Gbps.
Additionally, we want to restrict the link between Clusters A and B to a bandwidth
of 250Mbps. 
To accomplish this we perform the following steps:
1.) Log onto hcl01 and make sure that eth0 is active and eth1
is not. This means that the machine is connected to switch1.
2.) Do the same for hcl02 
3.) Log onto switch1, and create a policy-map to limit the bandwidth
to 10Mbps (10000000bps). Attach this policy-map to gigabitEthernet0/1 and gigabitEthernet0/2.

4.) Log onto hcl03 and perform the following steps:
 hcl03 $> /sbin/ifconfig 
This will list the active network devices. If the user before you cleaned up
after him/her self, only “lo” (the loopback interface) and “eth0”
should be listed. 
hcl03 $> /sbin/ifup eth1 (debian command is sudo /sbin/ifup eth1) 
hcl03 $> /sbin/ifdown eth0 (debian command is sudo /sbin/ifdown eth0)
This connects hcl03 to switch2, as eth1 is connected to switch2.
Then hcl03 is disconnected from switch1, as eth0 is connected to switch1. MAKE
SURE YOU ALWAYS BRING ONE INTERFACE UP BEFORE YOU BRING ANOTHER DOWN. OTHERWISE
THE MACHINE WILL BE ISOLATED WITH NO ACTIVE NETWORK DEVICES. To see what devices
are currently active, use the /sbin/ifconfig command. 
5.) The same should be done for hcl04. 
6.) Since we want these machines to talk at 1Gbps, we should
log onto switch2 and make sure that there are no policy-maps existing. 
7.) Log onto switch1 and create a new policy-map, limit it to
250000000bps and attach it to gigabitEthernet0/25. Do the same for switch2.
Done!
 
The following example shows how to delete a policy-map. YOU
SHOULD ALWAYS REMEMBER TO DELETE YOUR POLICY-MAPS WHEN YOUR JOBS ARE DONE SO
OTHER USER’S JOBS DON’T GET MESSED UP! 
-------------------------------------------------------------- 
hcl0x $> telnet 192.168.21.252 
     Trying 192.168.21.252... 
     Connected to 192.168.21.252 (192.168.21.252). 
     Escape character is '^]'.
     User Access Verification 
Password: <enter password> 
hclswitch1>enable 
Password: 
hclswitch1#show policy-map 
   Policy Map example 
    Class ipclass1 
     police 100000000 800000 exceed-action drop 
hclswitch1#config t 
     Enter configuration commands, one per line. End with CNTL/Z. 
hclswitch1(config)#no policy-map example 
hclswitch1(config)#exit 
hclswitch1#show policy-map 
 
hclswitch1#exit 
     Connection closed by foreign host.
hcl0x $> 
---------------------------------------------------------------

@@ Line 20: / Line 20: @@
 <p><font size="4">
 Here[http://www.linuxfoundation.org/collaborate/workgroups/networking/netem] is an excellent description how to introduce packet delays for outgoing traffic, which is a way to control latency.
-</p>
+</font></p>
 <p align="center"><font size="5"><strong>Switch Configuration</strong></font></p>

@@ Line 16: / Line 16: @@
    the switch should prompt for a password. For the password, email brett becker.</font></p>
 <p>&nbsp;</p>
 <p align="center"><font size="5"><strong>Switch Configuration</strong></font></p>
 <p><font size="4"><br>

HCL Cluster Network - Revision history

Kiril at 13:23, 27 January 2011

Kiril at 13:21, 27 January 2011

Root: New page: Switch Management The cluster is connected via two Cisco Catalyst 3560G switches. The ingress bandwidth on...

Root: New page:
Switch Management

The cluster is connected via two Cisco Catalyst 3560G switches. The ingress bandwidth on...