New job, dead lab and a temporary solution. ;)

Hi !

Let’s start blogging again. 🙂 A lots of time passed since I blogged interesting things. The main reason was, I decided to change my employer. The last weeks we moved our home, too. Now my little family is living in a suite little house, with a big garden, a big garage but no more big cellar. 😉 But I will talk about this circumstance some lines later.

qskills

Today I had my first day at qSkills. This is my new employer. 🙂 I’m working as an IT Architect and Software-Engineer. My first job is to design and implement an entire new network because the current network is very outdated. Maybe the new network is based on Cisco Nexus. 😉 It’s hot stuff and my new boss loves nice and cool toys. Me too! 😉 BTW. the company earns his money with professionel trainings and they have a strong relationship with Fujitsu and NetApp. In the dedicated training datacenter (nine 47U racks!) are lot’s of nice toys installed, predominantly Fujitsu servers and many NetApps storage systems of course. A very nice playground for lot’s of tests in addition to my private lab. 🙂 A good point to talk about my home lab.

My well known home data center is DEAD ! I moved everyting into the new garage, until I can start my new home lab idea. 😉 I’m not sure if I can pay the new idea this year, because the move to the new home was very expensive and I have a wife and little daughter who needs money too. But I can wait until next year. Meanwhile I’m running a tempory solution in the new cellar which is not big enough for a 2m tall rack. But it’s enough for playing and blogging about my experience, as you can see on the last picture. 😉 That’s why I hope you visit my blog, again…. 😀

Some news…

It’s end of February and I didn’t blogged since two months. 🙁 But  the last months I had lot’s of work and prepared very important changes. I quit my current job and on 1. April 2012 I will start working in a new company. I will blog about my new employer soon. It’s an amazing company and I can’t wait starting my new job. 🙂 Last weekend I signed my new tenancy agreement and my new home is amazing, too. But there’s no more room for my home lab. That’s why I have to stop for several months playing arround with my toys. Don’t worry, I have a great idea for my new „Home Datacenter“, but I need time and of course money. 😉 Stay tuned and thank you for visiting my Blog. 🙂

Merry Xmas 2011

I wish all my readers and followers on Twitter a

Merry Xmas!

Thank you for reading and commenting all my blogs and tweets. 🙂 Now it’s time to shutdown my home lab and spent attention to my family. 🙂 My daughter Lina is one year old and 30 mins ago I give her a very big Teddy-Bear. 🙂 That was really fun and she loves her new toy.

In 2012 I will finish my M$ Hyper-V project and I plan to publish a real world Hyper-V cluster configuration. I will start with the current Hyper-V version and I plan to do the same with Hyper-V 3.0 ! 😉 A Windows SMB 2.2 file server over Infinband is on my roadmap, too. And with a little bit of luck I can get an HP EVA 4400 for my home lab. 😉

Stay tuned and I wish everybody  happy holidays! 🙂

Kind regards.
Tschokko

Merry Xmas 2011
Merry Xmas 2011

HP ProCurve Switch Mesh – My new lab network

I decided to try the HP ProCurve Switch Mesh technology in conjunction with my HP BladeSystems and HP Virtual Connect. After a week of planing, searching the Internet and reading several documents, I started to rebuild the network in my home lab. The results are amazing. Everything in my lab runs very fast and with low latency. Even the software based Core Router (Debian + Quagga) is no limitation. I tested the network performance with iperf and was able to send data thru my Mesh from one routed network to a another with 900 Mbits/s! I did the iperf test with two CentOS 6 virtual machine running one VMXNET3 NIC. The VMs are placed on different hosts, too.

Configuring the switch mesh is very simple. Disable routing and stacking and add all mesh ports with the mesh command. The vlans are added automatically to all mesh ports. Only ensure that every mesh switch knows all configured vlans.

My HP BladeSystem is connected with two LACP trunks to the switch mesh. I decided to setup VLAN tunneling  because the two connected blades running VMware ESX.The HP Virtual Connect setup was very simple and thanks to LLDP I detected a cabling error. 😉 LLDP is very useful! You can see several informations about the connected network port. That’s really cool.

Currently my mesh is connected with several 1 Gbits links, but with a little bit luck I can get some 10 GbE modules for my 3500yl switches. 😉

That’s all for today. Stay tuned. 😉

IBM Installation Manager on RHEL 6 / CentOS 6 x86_64

To solve the error

# ./install
-bash: ./install: /lib/ld-linux.so.2: bad ELF interpreter: No such file or directory

and the font display error when IBM Installation Manager is started, you need to install following packages with yum.

yum install gtk2.i686 libXtst.i686 dejavu-sans-fonts

Solaris 11 manual IPv4 & IPv6 configuration

Wooow… lot’s of changes ! Today I downloaded the brand new Oracle Solaris 11 operating system and started to install it into a VirtualBox virtual machine. Automatic network configuration is a very nice feature, but I’m a „Old-School“ guy and I prefer the manual configuration. 😉 So I tried to setup a valid network configuration for IPv4 and IPv6. I’m running several months a dual-stack configuration at home and I’m very impressed of IPv6. That’s why a proper IPv6 configuration is very important for me, because I access all my systems over IPv6 if it’s available.

Okay, no guarantee for all following steps. But my Solaris 11 installation seems to run well with this configuration. If I did some errors, please comment. Solaris 11 has lot’s of changes!

Disable automatic network configuration:

# netadm enable -p ncp DefaultFixed

Configure a static IPv4 address and default route:

# ipadm create-ip net0
# ipadm create-addr -T static -a 10.0.2.18/24 net0/v4static
# route -p add default 192.168.100.1

Setup name services and a valid domain name:

# svccfg
svc:> select name-service/switch
svc:/system/name-service/switch> setprop config/host = astring: "files dns"
svc:/system/name-service/switch> setprop config/ipnodes = astring: "files dns"
svc:/system/name-service/switch> select name-service/switch:default
svc:/system/name-service/switch:default> refresh
svc:/system/name-service/switch:default> validate

# svccfg
svc:> select nis/domain
svc:/network/nis/domain> setprop config/domainname = "itdg.nbg"
svc:/network/nis/domain> select nis/domain:default
svc:/network/nis/domain:default> refresh
svc:/network/nis/domain:default> validate

# svccfg
svc:> select dns/client
svc:/network/dns/client> setprop config/nameserver=net_address: ( 2001:4dd0:fd4e:ff01::1 2001:4dd0:fd4e:ff02::1 )
svc:/network/dns/client> select dns/client:default
svc:/network/dns/client:default> refresh
svc:/network/dns/client:default> validate
svc:/network/dns/client:default> exit

# svcadm enable dns/client

Please note, that I configured IPv6 name server addresses! This is only possible if your DNS server has a valid IPv6 configuration.

Let’s add the important IPv6 part:

# ipadm create-addr -T addrconf net0/v6
# ipadm create-addr -T static -a 2001:4dd0:fd4e:d00f::a007 net0/v6add

The first line is needed because I don’t want to configure an IPv6 default route! This is done with my Router Advertisement daemon and Link-Local addresses.

That’s it ! My Solaris 11 installation is available thru IPv4 and IPv6. 🙂

HP BladeSystem C3000

Say Hello to Shorty ! 🙂

Shorty is running an Ubuntu OpenStack Cloud Computing environment. It is connected to a MSA2012fc storage system and a ProCurve 5406zl modular network switch. The 10 GbE uplink to the 10 GbE 4-port module is prepared, but the CX4 X2 module is missing to complete the connection. I will order the X2 module within the next weeks. 😉

One step towards Converged Infrastructure

I know my blog is very silent since several weeks. But I have lot’s of work and of course a daughter.;)

As you can imagine I have some new ideas for my home lab. 😉 And one is very exciting ! I started to rethink and rebuild my HP blade environment. Yesterday a new toy arrived. Have a look at the backside of my HP c-Class BladeSystem. You can see a very important interconnect module for a Converged Infrastructure. 😉

hpbs_interconnects

As posted below I planned to build a network upon HP ProCurve. But I noticed that I need a premium license for features like VRRP and OSPF. But these two features are neccessary for my new Home-Lab network infrastructure. I like to create a enterprise network for my systems and not a simple 192.168.x.x home network. That’s why I switched to big Cisco 6506 modular switches. Cisco isn’t cheap, but it offers all features I need. Buying 3 HP ProCurve licenses is impossible, I don’t earn so much money. Let’s say hello to my first Cisco 6506 switch. The second 6506 is below and I will receive a Sup2 engine with MSFC2 the next weeks. 😉

cisco6506

I hope you followers haven’t forget my blog. Please stay tuned! The next months will be very exciting. I’m saving money for a HP MDS 600. 😉

Kind regards
Tschokko

Preparing the rebuild of my home lab!

Lot’s of time passed since my last posting. But now I will continue blogging about my home lab. Some months ago I moved my neccessary systems to a HP MicroServer, because the running costs of a real server are enormous! After I finished setup my new home network, I decided to change the entire networking in my home lab. Until now I run the same home network subnet (192.168.x.x) for all systems. That’s not a real enterprise environment. For my home use here at my desk it’s good enough, but not for my home lab in the cellar! Today I started configuring a classic multi layered network. I’m running a HP ProCurve 5406zl modular switch as my network core. This core is connected to my home network in the first floor and to a pair of HP ProCurve 3500yl switches. The two switches represent a typical distribution layer. All connection to the core switch are L3 based. I’m running a linux router on my HP MicroServer with a RIP daemon. The linux router is my default gateway in my home network and thanks to RIP it knows all routes to the IP subnets in my home lab. I prefer OSPF, but I have no premium license for the HP ProCurve switches. That’s why I’m using RIP. It’s doing a well job, too.

Next step is the reassembly of my HP rack. I planned to unify the blade server environment and to create a full virtualized lab or should I say a cloud enabled home lab? 😉

hplab-network

Powered by WordPress. Reyl Lite designed by Quema Labs.