spent now about three month in my new job on a single project. built on customer siteĀ enterprise environments using 3x ibm flex system enterprise chassis, ibm protecttier gateways, multiple juniper ex4xxx virtual chassis clusters, junos space and ha srx550 setups, multiple ibm storwize sans (v3700,v7000).
before
after
a new friendship ! <3 bacula !
actually i`m building a complete infrastructure from scratch; 3 * ibm 3650m3 => 2 * vmware esxi, 1 * debian stable as nfs storage, ghettoVCB to nfs, icinga monitoring for all devices, high security segmented network design, vlan trunken switching, ibm lto5 sas drive with baclua, postix/amavisd-new/postgrey/sa mta, exchange 2010 + 2k8 ad, svn / jenkins developing machine, juniper srx220h firewall and a mag2600 as vpn-ssl solution and some other stuff … day 7 …
the first time i build a icinga monitoring for a vsphere environment. before i configured only checks for esxi machines directly. love the check_esx3.pl module from op5.com. some pics from pnp4nagios:
got the system running on a debian squeeze, all packages from the main,nonfree,controb repositories. pnp4nagios is backported. so all packages are covered with security updates and the normal apt super cow power !
a new cisco 3750x !
switching fabric: 160 gbps, forwarding rate : 35,7 mpps
got an customers w2k8 r2 mgmt machine with symantec endpoint and vmware vsphere. the problem: after installing the endpoint product under vmware vsphere the performance graphs for the vm’s don`t apear and the client crashes immediately(detail: the vmware webservice services crash and cannot restart successfully). cause: both software product got webservers on board, that means port conflicts. the solution: the machine got two nics; one nic for mgmt net, one nic for a production net. i changed in the vmware tomcat config the localhost definitions to the mgmt ip because i saw that the endpoint used the other interface automatically. now the tomcat services for the vsphere installation run on a different interface and there are no more conflicts with the two webserver instances… the better solution is not to install two products with different webservers on one machine – especially under a windows server.
two ssg5`s and a mag2600 arrived for production, will do a classic ipsec vpn setup between the branches and a hopefully funky sslvpn setup … š
build a new vmware cluster for a customer:
2*ESXi 4.1@x3650M3, 1*vSphere,Essential Plus@x3650M3, 1*DS3500,2*SAN24B FC Switches. 1*TS3100 LTO5 FC Library
ignore the hp garbage …
will test these days the new junper mag ssl/vpn gateway series.
the specs read very well – lets see what it’s got …
http://www.juniper.net/as/en/products-services/security/mag-series/