•August 26, 2013 • Leave a Comment
Definitely need to get back to blogging. Work has been crazy over the past year. Been doing a lot of Cisco UCS, EMC VNX, and Cisco VoIP. More to come soon
•April 16, 2012 • 1 Comment
So a few days ago we needed to do a port redirect on a server. This was a new implementation of an app server, but the link for all the clients refered to port 80. The new install listed on port 8080.
A few ideas were kicked around like installing apache to listen and do a metaredirect to the new location. Then it clicked, why not use IPtables?
Below is how we redirected port 80 to 8080
iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-ports 8080
Once completed and tested, I saved the config as follows
iptables-save > /etc/sysconfig/iptables
The above is for a RedHat Linux server. IPtables pulls its config from /etc/sysconfig/iptables file on startup.
•December 13, 2011 • Leave a Comment
So I wrote this up a long time ago and just never posted it. I have a lot more UCS stats saved on text files that I should be able to dig up. I completely forgot about this until an email yesterday.
So when it comes to maintenance, I time almost everything. I really like being able to estimate how long specific actions should take to complete. That is what this post is all about. I will be going over startup times, dissassociation, and association of service profiles on Cisco B200 M1 blades. The test was done using blades having different RAM configurations across multiple chassis.
Also to note, our blades boot from SAN to a fiber connected EMC CX4-240 Clariion. The storage on the CX4 supporting these and 10 other boot from SAN blades LUNs is as follows:
Qty 4 – 600gb 10kRPM disks setup in a RAID 10 group.
Continue reading ‘Cisco UCS B200-M1 Interaction Times 1.3(1c)’
•August 5, 2011 • 14 Comments
We received our Nimble Storage CS220G earlier this week. We are hoping for the device to fall into a tier between our EMC CX4 and standard NAS storage systems. Being that we are mostly 10gb at our datacenter, it was a definite requirement. Most other appliances around the same price point did not have any type of storage tiering, so I am also excited about that.
Cache (SSD) RAW 320gb
Quad 10gbE connectivity (2 per controller)
Below shows the Nimble device being un-boxed. I highlighted the SSD drives in green
Continue reading ‘Nimble Storage CS220G ISCSI Array Initial Install’
•March 7, 2011 • 3 Comments
We had two DRAM cache modules fail in our RamSan 500 recently. The actual error was:
Uncorrected ECC event detected on boards 4,6
The DRAM cache fronts the Flash storage drives in the unit. Basically, loosing these two boards took down the unit completely. To get the unit back up, boards 4 and 6 needed to be removed. RamSan actually had me remove 4 of the boards instead of just the two that were bad. Guessing it has something to do with not being able to have slots not filled between active modules. Continue reading ‘RamSan 500 Pictures / Failure’
•March 1, 2011 • 2 Comments
I’m glad Jeff (see comments) caught where I went wrong. After his comment I went back through the n1000v_upgrade_software PDF from cisco. For version 4.0(4)SV1(3a), the VEMs should have been upgraded first. It is on page 9 of the document.
Upgrading from Release 4.0(4)SV1(3, 3a, or 3b) to Release 4.2(1)SV1(4)
Step 1 Upgrading the VEMs: Release 4.0(4)SV1(2, 3, 3a, 3b) to Release 4.2(1)SV1(4), page 20
Step 2 Upgrading the VSMs to Release 4.2(1)SV1(4) Using the Upgrade Application, page 33
I was following lower down in the document that showed an upgrade of the VSM first then the VEM. Looking closer that was for one that required an intermediate upgrade between the current running and the newer 4.2(1)SV1(4) firmware. Thanks for the catch!
So last weekend was our Cisco Nexus 1000v upgrade. We were upgrading from 4.0(4)SV1(3a) to 4.2(1)SV1(4). What should have been an easy upgrade really turned into a huge headache. Below is a walk-through of the upgrade process with notes on where things went wrong.
To start, lets verify the current running state of the VSM (1000v switch) and the VEM (ESX host modules). Below you will see that they are all on version 4.0(4)SV1(3a). Also note the standby VSM module number is 2. This will be the first one reloaded.
1000vSW# sh module
Mod Ports Module-Type Model Status
--- ----- -------------------------------- ------------------ ------------
1 0 Virtual Supervisor Module Nexus1000V active *
2 0 Virtual Supervisor Module Nexus1000V ha-standby
3 248 Virtual Ethernet Module NA ok
4 248 Virtual Ethernet Module NA ok
5 248 Virtual Ethernet Module NA ok
6 248 Virtual Ethernet Module NA ok
7 248 Virtual Ethernet Module NA ok
8 248 Virtual Ethernet Module NA ok
9 248 Virtual Ethernet Module NA ok
Mod Sw Hw
--- ---------------- ------------------------------------------------
1 4.0(4)SV1(3a) 0.0
2 4.0(4)SV1(3a) 0.0
3 4.0(4)SV1(3a) VMware ESXi 4.1.0 Releasebuild-348481 (2.0)
4 4.0(4)SV1(3a) VMware ESXi 4.1.0 Releasebuild-348481 (2.0)
5 4.0(4)SV1(3a) VMware ESXi 4.1.0 Releasebuild-348481 (2.0)
6 4.0(4)SV1(3a) VMware ESXi 4.1.0 Releasebuild-348481 (2.0)
7 4.0(4)SV1(3a) VMware ESXi 4.1.0 Releasebuild-348481 (2.0)
8 4.0(4)SV1(3a) VMware ESXi 4.1.0 Releasebuild-348481 (2.0)
9 4.0(4)SV1(3a) VMware ESXi 4.1.0 Releasebuild-348481 (2.0)
Continue reading ‘Cisco Nexus 1000v 4.2 Upgrade Problems And Fix’
•February 16, 2011 • 2 Comments
What I am getting at here is do not underestimate the amount of ports you will be using. We have implemented Cisco UCS with 6120 switches but also installed a pair of Nexus 5010 switches as well. Going in, we had only planned for a few devices to be connected to the 10gb Ethernet network outside of the UCS infrastructure. Looks like we underestimated!
Once we got over the fear of FCoE reliability, almost everything is now being ordered with 10gbE. The only reason of worry was during this implementation over a year ago, FCoE was not in the main stream yet. It was almost “bleeding edge” in the market.
Where are we a year later? Continue reading ’10gb Ethernet – A Year Later / Buy It Carefully’