About varrow_jgillow

varrow_jgillow · 03-30-2012

Why does UCS not send call home alert emails if all LAN or SAN uplinks fail to a fabric interconnect?Today while testing multipathing and network redundancy, we disconnected all LAN and SAN uplinks from a fabric interconnect in a HA cluster. 60-some...

varrow_jgillow · 07-23-2012

I had this problem back in May and was able to create a RAID 1 volume using the UCS Server Configuration Utility.http://jeremygillow.varrowblogs.com/?p=176

varrow_jgillow · 03-29-2012

I have still seen some of these messages with 2.0(1w), usually they are false alarms and can be ignored. Although today I had a esxi 5.0 blade that was logged into SAN fabric A but not fabric B, had to reboot the blade then it logged into both as it...

varrow_jgillow · 03-21-2012

I set up teaming yesterday on a couple B200 M2 blades with M81KR, wrote a short blog post with screen shots here:http://jeremygillow.varrowblogs.com/?p=155Jeremy

varrow_jgillow · 12-21-2011

Have you tried to reacknowledge the B440 M2 blades? (while they are associated to the service profile with the boot from SAN policy). Note -- they will power cycle for that procedure.

varrow_jgillow · 09-19-2011

I've only implemented 1.4(3q) once and we had an issue where UCSM would disconnect every few minutes. We had to disable the HTTPS redirection and use regular HTTP then there were no disconnection problems. Even ignoring that, the upgrade from 1.4(3...

Member Since	‎04-05-2011 12:57 PM
Date Last Visited	‎08-18-2017 03:55 AM
Posts	7
Total Helpful Votes Received	5

User Statistics

User Activity

No call home email from complete uplink failure?

Re:UCS C200 M2 with 1064E - no raid configuration possible

UCS 2.0(1q) Patch Released

Windows Teaming Driver Available for M81KR VIC

ESXi 5 boot from SAN with 2.0(1t) on B440 M2 problem

UCSM 1.4(3q) Issue