Category Archives: Networking

Wan Acceleration Appliances

Posted on by — No Comments ↓

There are some really good products out there in the market at the moment…

Exinda – low cost, really good QOS / prioitisation and visibility. Falls short on acceleration (at the moment)
Riverbed – One of the key players in the acceleration market. Optimized algorithms for specific traffic.
Silver Peak – Relatively new, work well as a capture all acceleration device with QOS / prioritisation included.

One to watch – traffic squeezer. I’m always a fan of open source getting into new technologies, and this project seems to be a good start. Its still early days but I’m hopeful this will take off and become a contender in the future ahead.

A few of the above vendors actually have a virtual version of their appliance. Depending on your current investment in virtual infrastructure this may or may not be a good idea. I’m still a fan of dedicated hardware, but in some cases the redundancy provided by a virtual infrastructure can out way the potential performance gains.

Cisco VTP on HP Switches?

Posted on by — No Comments ↓

 

Want to propergate vLan information across multiple switches?

Easy in the Cisco world…  Just use VTP – configure a server switch and  your away… (it also has its risks if you introduce another server switch with a lower ID)

What does HP have?  — GVRP (MVRP newer iteration).

http://en.wikipedia.org/wiki/Multiple_Registration_Protocol

Multiple VLAN Registration Protocol (MVRP), which replaced GARP VLAN Registration Protocol (GVRP), is a standards-based Layer 2 network protocol, for automatic configuration of VLAN information on switches. It was defined in the 802.1ak amendment to 802.1Q-2005.

MSTP – nice blog on its inner workings here – http://blog.ine.com/2010/02/22/understanding-mstp/

 


HP Blade Switch – enable crossover

Posted on by — No Comments ↓

HP GbE2c Ethernet Blade Switch for HP c-Class BladeSystem User Guide
Click here to view the “HP GbE2c Ethernet Blade Switch for HP c-Class BladeSystem User Guide” (http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c00701541/c00701541.pdf)
HP GbE2c Layer 2/3 Ethernet Blade Switch for c-Class BladeSystem User Guide
Click here to go to the “HP GbE2c Layer 2/3 Ethernet Blade Switch for c-Class BladeSystem User Guide” (http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c00865010/c00865010.pdf)

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00700745/c00700745.pdf

Crosslinks

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00816246/c00816246.pdf

P4000 / Lefthand and Windows DSM (MPIO)

Posted on by — No Comments ↓

Steps to setup MPIO round robin and DSM with P4000 / Lefthand nodes

This example is windows 2008 with 2 x 1gbit nics

  1. Install HP DSM driver onto windows 2008  (this should also install MPIO feature on windows 2008)
  2. Setup 2 x IP’s on windows host – storage subnet (used with MPIO)
    1. Confirm you can ping target from both (enable one at a time – ensure there is no routing on your other nics)
  3. Provision storage and allow server read / write access to windows server (via initiator name)
  4. Open iSCSI on windows 2008
  5. Put in IP of target in discovery tab
  6. On first tab confirm that iSCSI drive is presented to host
  7. Click “connect” – check both auto-connect and use MPIO
    1. click advanced – chose MS iSCSI initiator, choose first IP and target IP. Click o.k. / o.k
    2. click advanced – chose MS iSCSI initiator, choose second IP and target IP. Click o.k. / o.k
    3. Repeat above per additional Nic
  8. Confirm via “devices” that there is x (as many targets as nics) targets per disk
    1. Within devices choose MPIO – change from vendor specific to “round robin”
      1. Note : read / write access to LUN is required when using “round robin” MPIO opposed to the default “vendor specific” which works with read only access. Else you will get an error – “not supported”
    2. Repeat above per “device”
  9. Confirm on Lefthand / P4000 CMC that the LUN has one connection per initiator Nic, and that each connection also has its DSM children (visible in CMC if working).

Confirm that the connection are as expected…

Run some disk benchmark utilities (iometer) and check that traffic is travelling over all the nics you have setup above. You can just use windows builtin task manager to do this.

Check that the right amount of connections are on the CMC for that particular LUN and initiator.  So if you had 3 nodes via 2 initiator nics you would actually have 8 active connections in total (1 per nic (2) and an additional for every nic to each nodes (6))

Note : There are some reported issues with DMS and data corruption. Although i have not seen this myself please be diligent when it comes to data backup esp when production data is involved.