A quick friday post, I am upgrading the environment at my work place, and we are putting the fantastic Nimble Storage device as our SAN for the VMware environment.
I’ve not personally installed one of these before until now, but have worked on them whilst in production and the performance from the device is unbelievable, especially when comparing the price against other competitors!
It took me around 20 mins from power on to configure the device, just enter IP’s, plug device into network ports that are already on the correct VLANs for management and iSCSI and your away.
How to create a Volume
Continue reading Nimble Storage – How to create a Volume
So last night was a busy one thanks to the HP Chassis and “fantastic” Virtual Connect system.
Bare with this article, as its part what happens blah blah, and part, how to install firmware on Virtual Connect
So the environment consists of;
HP C7000 Chassis
6 x HP BL460c Blade Servers
2 x HP VC Flex-10 Enet Module
These VC Flex modules are connected by 2 x 10GB links in a LACP trunk to Cisco 3750X stack.
The plan of work
Continue reading HP Chassis and Virtual Connect Firmware Upgrades – Don’t bother
Server 2012 now supports NIC teaming, previously you could use HP tools to achieve this in Server 2008 R2 and below, but officially it was never supported by Microsoft.
Setting up a NIC team in Server 2012 is really simple. You just need to know where your Server is plugged into first on your switches.
1. Open Server Manager, Click on NIC Teaming
2. Under tasks click new team
3. Enter your name, select your adapters, and configure your advance network settings which we will talk about later.
And click OK and we are done.
Jumbo Frames Continue reading Server 2012 R1/R2 Creating a Network Team and enable Jumbo Frames
This is just a quick one,
A customer of mine has two companies running in the same building, using the same ISP connection, as such the Firewall is essentially the core of the network. I put in this network and although its not exactly best practise, its a case of making do with what they had and could afford.
Today he logged a support ticket stating he couldnt connect between two internal different subnets any more, (192.168.x.x and 172.16.x.x)
The fix for this was inputting the command; Continue reading Cisco ASA – Allow traffic between two same security level interfaces