Cisco is having to replace all the B440 blades that are deployed:
Update:
The firmware upgrade initially prescribed in this Field Notice has successfully detected FET failures and shut down servers, preventing a potential thermal event. Since this upgrade was released, however, a FET failure on a UCS B440 Blade Server has resulted in a second incident as described above. Cisco is directly contacting UCS B440 Blade Server customers and will replace UCS B440 Blade Servers currently deployed at customer sites. Cisco is making UCS B440 Blade Server hardware modifications, and a hardware replacement program has been launched. No other UCS hardware is affected.
Information is from a Cisco public website: http://www.cisco.com/en/US/ts/fn/634/fn63430.html

Netapp 8.1.Cluster Mode Overview -

• - Scalable cluster of Netapp filers or vfilers with 3rd party storage managed centrally and working collectively.   NAS scalable to 24 nodes, SAN scalable to 4.
• Support for SAN protocols
• NFS4.1 Support
• PNFS Support
• Asnychronous volume snap mirror for DR

Netapp 8.1 7 Mode

-Upgrades much easier, straight upgrade from 7.3.2+ to 8.1
-SAS and SATA drives can now be used in metrocluster
 

Both Modes

***Ability to do 32 to 64 bit aggregate conversion; rather than copy to new aggregate.  Happens as aggregate grows beyond 16tb aggregate limit automatically.  No performance impact.
***Aggregate size increased for the most part 50% for all systems from 8.0.x to 8.1.  This is inline with 3TB drives released.
-Max volume size is static.
***32 Bit volume snap mirror to 64Bit volume supported. 
***64 bit aggregrates are now default rather than 32.

Biggest Changes in Both Releases Storage Efficency = Deduplication, Cloning and Compression

1. No deduplication license
2.  Dedupe volume limit increased maxium volume size of supported system
3. Deduplication Performance increased, 33% higher
4. Hourly checkpoints checkpoints hourly, incase dedupe is stopped and restarted
5. Block Ratios

DataCompression

1. Compression wasn’t GA in 8.0.X in 8.1 its GA.  When it was originally released it was inline only meaning that it was compressed before going to disk.  Now it is offered both inline and post process scheduling.
2. MetroCluster Support since 8.0.2
3. Current customer usage is 40% breakdown to production vs 60% backup and archive
4. No licenses or volume limits
5. Compression of existing data 7x faster than 8.0.x

***Comparing Dedupe to Compression – Dedupe looks at the 4k blocks and creates pointers to other similar 4k blocks.  Compression looks at 32k block and looks for largest repeating pattern, cyclical process until no more repeating patterns.

Systems Manager

• 8.1 will require system manager 2.0.  System Manager will work back to DataOnTap 7.2
• Browser base supported on Windows and Linux
• ClusterMode Support
• Ability to halt and reboot controllers
• Create and Manage Snapmirror relationships
• Dedupe,compression, and snapshot integration
• File and Lun Cloning

Here is a list I compiled after completing my What’s New In vSphere 5 class.  I won’t bother getting into licensing….

-No block limit size for VMDK
-VMDK scales to 64 TB with 2TB limit on files
- 32 Cores up from 8, 1 TB of Ram
-NFS DataStores increase from 32 to 256
-SATP Modules loaded on demand no more setting from command prompt
-No more setting iscsi port binding from command prompt gui driven
-Software base fcoe initiator

–VAAI -thin provisioning stun + VMFS space reclamation = As the data store reaches max compacity, instead of overfilling and risking data corruption at 97% VMs are put in suspend mode.  Space Reclamation works with the storage array vendor to shrink the lun size on a thin provisioned volume as used space decreases to increase storage efficency.
–vCenter client for Linux.
-vCenter appliance linux based….No it doesnt support linked mode
-Profile Driven Storage- Create profiles for SLAs based on performance etc for performance and availability.
-Storage DRS- DRS based on i/o and size
-Virtual Machine format 8 not really exciting usb 3.0 support and also Windows Aero
-Storage I/O Control – Extended to NFS
-Network I/O Control – More granular offering per virtual machine control.
-Vsphere WebClient – Wasnt this in ESX2?
–RTT Latency increase from 5ms to 10ms in Enterprise Plus vMotion

http://www.vmware.com/files/pdf/products/vsphere/vmware-what-is-new-vsphere5.pdf

http://www.vmware.com/files/pdf/techpaper/Whats-New-VMware-vSphere-50-Storage-Technical-Whitepaper.pdf

http://www.vmware.com/files/pdf/techpaper/Whats-New-VMware-vSphere-50-Networking-Technical-Whitepaper.pdf

I got this from a friend this morning. Good stuff.  New 3Par Virtualization white paper for inform os 3.1.1 and Recovery Manager updates…http://h20195.www2.hp.com/v2/GetPDF.aspx/4AA3-4023ENW.pdf

Q: Should a Thin Provisioned Virtual Volume (TPVV) be used for ESX datastores?
A: Thin provisioning makes sense as long as you are not going to fill up the volume right away. If the volume is going to be full in a short time, there is no benefit to be gained from thin provisioning. If VMware snapshots are being created and are not being cleaned up, the benefits of thin provisioning will be negated. To the ESX host, it makes no difference if the host sees a thin provisioned LUN or a traditional “thick” provisioned LUN.

Q: Is there any overhead to using Thin Provisioned Virtual Volume (TPVV)?
A: The additional overhead of TPVVs as compared to traditional volumes is negligible.

Q: If using a 2 TB Thin Provisioned Virtual Volume (TPVV), what will vSphere see?
A: vSphere will see a 2 TB LUN available for its use. Without the use of VAAI and/or T10, vSphere cannot determine if a volume is a thin provisioned virtual volume and a traditional virtual volume. With vSphere 4 or vSphere 5.0 on InForm OS 2.3.1 we recommend installing the VAAI plug-in. For vSphere 5.0 and InForm OS 3.1.1 or higher, no plug-in is required.

Q: What size Virtual Volume (VV) should be created?
A: The volume size is not as important to HP 3PAR Storage Systems, as VVs are widely striped across as many drives as possible within the array. If using HP 3PAR Thin Provisioning Software, actual storage capacity is only consumed upon write. However, a 2 TB VV will be able to accommodate many more VMs than a 500 GB VV. ESX 4.1 or later has improved the way it performs metadata locking, meaning that you can now create a VV that is as large as you are comfortable with. For ESX 4.0 and prior, in order to minimize the impact of SCSI reservations and keep the environment well balanced, it is best to create 500 GB volumes (thin provisioned or “thick” provisioned).

Q: How many VMs can be put on a single Virtual Volume (VV)?
A: It depends. There is no one answer that will work for every situation. A number of factors such as server hardware, number of CPUs, amount of memory, type of VMs, applications running in the VMs, etc. will determine how many VMs can be comfortably hosted on a LUN.

Q: What type of path policy (Fixed, MRU, Round Robin) should be used with HP 3PAR Storage Systems?
A: With ESX 3.5, use the default policy (Fixed). With ESX 4.0 and later, change the default policy to the Round Robin path policy. To do this, log in to the service console for each ESX 4.0 host and run the following command line:
esxcli nmp satp setdefaultpsp –satp VMW_SATP_DEFAULT_AA –psp VMW_PSP_RR
For vSphere 5 you can change the path selection algorithm using the Manage Paths dialog box either from the Datastores or Devices view or from the command line on each host:
esxcli storage nmp satp set –satp=VMW_SATP_DEFAULT_AA –default-psp=VMW_PSP_RR

Q: VMware supports thin VMs. Which thin provisioning should be used: VMware, HP 3PAR, or both?
A: VMware thin provisioning only applies to VMs at the VMFS level. It allows one to over-allocate VMs to maximize VMFS usage. If the goal is to reduce storage costs and maximize storage utilization, then use HP 3PAR Thin Provisioning Software to provision large VMFS volumes with minimal upfront storage costs. There are no additional storage savings to be realized by using VMware thin provisioning. VMware thin provisioning does consume some CPU cycles on the ESX host as it is performed at the software layer (as compared to HP 3PAR Thin Provisioning Software, which is performed on the array). It is perfectly fine to place VMware thin VMs on HP 3PAR Thin Provisioning Software volumes so long as you are prepared to manage thin provisioning at both the VMware level and the array level.

Q: Is the UNMAP primitive of VAAI supported across the board?
A: No, UNMAP is not supported prior to vSphere 5.0 with InForm OS 3.1.1.

Q: When do I need to install the VAAI plug-in?
A:

·         VAAI is not supported on HP 3PAR InForm OS 2.3.1 MU1 or earlier.

·         On vSphere 4.1, the VAAI 1.1 plug-in is required.

·         When running vSphere 5.0 with HP 3PAR InForm OS 2.31, the 3PAR VAAI 2.2 plug-in is required.

·         For vSphere 5.0 with HP 3PAR InForm OS 3.1.1 or higher, no plug-in is needed as all of the VAAI primitives are supported natively.

This was really cool.  It was literally the most impressive thing at HP discover for me.  It also tied in the Instant On Enterprise theme or slogan in seeing the power cloud maps and automation in the Matrix OS…  In the past as working as a customer and consultant I was able to implement and administrate Insight Control, however I never had the chance to use Insight Orchestratration.

Some Quick Notes that I took are:

• The Matrix software is version 6.3 running on a DL 380 Central Management Server
• Blades Chassis with Flex-10 Virtual Connect/Flex-Fabric…
• All HP Storage is Supported even Netapp and EMC…
• To use Storage Provisioning Manager you have to use an EVA or 3Par, I found it odd not 3Par Lefthand

Here is what we did in Lab…I’ll try to get slides, btw besides your workstation with a takehome lab manual they provided the information on a 17inch notebook as well.  It was really done Vegas style.

1) Creating Cloud Maps-  Inside Insight Orchestration Designer we created two templates on for physical servers on for virtual servers.  On the template we dropped the logical group objects for networks, storage, and servers being physical or virtual then published them.

2) Self Service Portal- We logged into this, and were presented with history of requests, running services, and resource utiliziation.  You can specify here in the self service portal also what users have access to what templates.  Next we created a service this creates a request to deploy your cloud map.  Once this is done the only thing left is to approve.  We approved and our infastructure was automatically deployed.  No lab hangs up.  It worked flawlessly.

3)  Importing Cloud Maps-  This was the coolest thing we did in lab, it really demonstrated the power and dynamic capability of the tool, definately makes you think Instant on Enterprise.  We logged into Insight Orchestration Designer and imported in a very elaborate cloud map.  It just showed how easy it would to replicate private cloud infrastructures through the process of importing and exporting cloud maps.

4) Storage Provisioning Manager and SPE –  As stated earlier this is the part that is only supported with EVA and 3Par.  It manages storage provisioning in the Matrix OS.  

 Two main use models are:

• Pre-poulated model the adminstrator populates the SPM catalog with storage services to be exposed to server management software, then sets access rights…Matrix then enables an administrator to request storage, which is sent to SPM as a storage services requests.  SPM then provides canidate services, and the administrator selects one or more apporiate volume services to fulfill the set of goals(requests)
• Request Based Model-  Administrator uses Matrix OS to request storage before it is imported or created.  The Administrator then adds the arrays and volumes to fulfil the goal.

In class we modified SPE (Storage Pool Entities) and changed storage type, portability, OS, and added a volume. 

Insight Capacity Planner/Advisor- 

• We created a planning senario selecting 20 legacy then gathering the performance statistics we could do senario forecasts with entering in CPU, Memory, Network I/O, and Disk I/O growth rate. 
• We also created a planning senario in which we consolidated to VMs
• Power and Price were also reportable and comparable

A lot.  I got to see in the flesh at HPDiscover last week, couldn’t really talk about it before then… So many new features and enhancements for one code release upgrade for existing x400 customers, that is the first thing that came to mind as I poured over all the new features in the P6000 from HP, not to mention the P6000 itself.  HP released the P6300 and P6500 looks like there isn’t an option as of yet for the 8400 replacement in terms of cache.  Can only guess 3Par is the probley the reason why…

Here is my summation, I am probley missing some:

1) Thin Provisioning –  This needed to be done, glad to see it is finally here.

2) Dynamic Capacity Management – This is free now.

3) Business Copy – Support for VMFS volumes; also support for large luns

4) Different Connectivity Options – You can get different connectivity options like iSCSI FCoE FCP this is nice

5) Shrink live luns

6) Change vRaid on Fly (can’t be thin provisioned)

7) Move Lun between diskgroup –  This is great; I wouldn’t want autotiering anyhow

Drive Form Factor shelves are either LFF 12 drives or 24 SFF SAS

9) 6Gb Sas Connectivity for drive shelves…

10) Multiple connectivity option e.g. fibre channel, iscsi, FCoE, not to mention combo option e.g. fibre channel and iSCSI

What’s Missing?

Still not sure on VAAI support and where this is headed

What do I have to do to get there?

Buy a P6000, or upgrade your existing commandview and xcs firmware

Anything you don’t like?

Yeah, I don’t like that they took the EVA4400 controller design and implemented it in the P6000 design with 2 controllers and 1 shelf.  I liked the previous EVA6400/8400 design much better.

How about the price?

The price is significantly less

Yesterday I found out I am going to Vegas for the HP 2011 Discover Conference.  The first thing I did was start the registration process. I heard a rumor last week that a lot of sessions are already filled and I can confirm this is true.  A side note there is so much stuff left though, you could easily spend two full weeks.

For me the highlight is labs. I could only pick two labs per stated in the registration system this was somewhat disappointed as I tried to originally schedule 5.  I scheduled Hands on with the Blade System Matrix and Hands on with 3Par Advanced.  It was really hard to narrow this down to two…I am very excited to about E5000 best practices session.  I love the idea of the E5000.  If you haven’t had a chance to read about it check it out here it’s very innovative.

This advisory was released today  for Virtual Connect you can read about it here:

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=c02720395&lang=en&cc=us&taskId=101&prodSeriesId=3540808&prodTypeId=329290

SUPPORT COMMUNICATION – CUSTOMER ADVISORY Document ID: c02720395 Version: 3 Advisory: (Revision) HP Virtual Connect – Virtual Connect Manager May Be Unable to Communicate (NO_COMM) if DNS Is Enabled for Virtual Connect Ethernet Modules NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice. Release Date: 2011-03-07 Last Updated: 2011-03-07 DESCRIPTION Document Version Release Date Details 3 03/07/2011 Added clarifications to the three scenarios described in the Resolution section to ensure the full sequence of steps is followed. 2 03/04/2011 Added additional details regarding the circumstances in which the issue may occur. Also, added three different workaround scenarios depending on whether Enclosure Bay IP Addressing (EBIPA) or external DHCP is being used and the version of OA firmware that is in use. 1 02/14/2011 Original Document Release. The HP Virtual Connect Manager (VCM) may not be able to communicate (NO_COMM) with Virtual Connect (VC) Ethernet modules in an HP BladeSystem c-Class enclosure or multiple enclosures that are part of the same Virtual Connect Domain. The loss of communication may occur in a new or an existing environment when a VCM Administrator attempts to perform any of the following tasks: Firmware Update Add/remove/reset server blades or Onboard Administrator (OA) modules Retrieve any VC Ethernet module status and state information (e.g. stacking links, port statistics, etc.) Add/edit/copy/delete/assign Server Profile Add/edit/delete VC Network Configure Port Mirroring Restore Domain Configuration Change SNMP Settings Change Advanced Ethernet Settings IMPORTANT: Attempting to execute any of the above tasks during NO_COMM adds additional risk of a network outage during the recovery steps described below. Customers particularly susceptible to this issue have VC Modules with management IP Addresses configured in the 10.x.x.x range and configured for DNS. When this problem occurs, the VC Manager will still be accessible, but all VC Ethernet modules in the domain will be displayed with an Overall Status of “No Communication.” The Virtual Connect Domain will show a “failed” status, stacking links will show “failed” and Profiles and Networks will show a status of “Unknown.” When in this state, server blades in the Virtual Connect domain will still be able to pass data traffic with no impact. This occurs if DNS is enabled for the primary VC module. The VCM may initiate a DNS reverse lookup for a very limited scope of incorrect IP addresses for the VC Ethernet modules. If this reverse lookup fails, (i.e., it is not answered by the DNS infrastructure), the primary VC module will be able to communicate correctly with the VC Ethernet modules. If the DNS infrastructure responds to this incorrect DNS reverse lookup, then VCM attempts to communicate with the VC Ethernet modules on this incorrect IP Address and fails, triggering a NO_COMM condition. Recently, the global DNS infrastructure began responding to these limited DNS reverse lookups. SCOPE Any HP Virtual Connect Ethernet Modules in a c-Class BladeSystem enclosure running VC Firmware Version 1.3x, 2.x or 3.x (up to and including 3.15) RESOLUTION A future version of Virtual Connect firmware (currently planned for release in mid-March 2011) will prevent this issue from occurring. As a workaround, disable DNS for the Virtual Connect Ethernet Modules in Enclosure Bay IP Addressing (EBIPA) or external DHCP. Removing DNS from VC Modules can potentially impact the following Virtual Connect features, if configured to use DNS names: Directory Server Settings – If a DNS name is configured for the Directory Server Address then it will no longer be resolved. The IP address will need to be configured as the Directory Server Address. SNMP Trap Destination – If a DNS name is configured for the SNMP Trap Destination then it will no longer be resolved. The IP address will need to be configured as the SNMP Trap Destination. From the VCM CLI – Any URL targets provided to save backup configuration or support dump will need to use IP address and not DNS name. The following three workaround scenarios depend on whether Enclosure Bay IP Addressing (EBIPA) or external DHCP is being used and the version of Onboard Administrator (OA) firmware that is in use: Scenario 1 – Enclosure Bay IP Addressing is being used to provide IP Addresses to the VC Ethernet Modules and the OA firmware version is 3.00 (or higher): Log into the Onboard Administrator and select Enclosure Settings > Enclosure Bay IP Addressing. Select the “Interconnect Bays” tab and remove DNS server IP address entries from the bays that include VC Ethernet Modules and click Apply. Within 5 minutes, the DNS settings for the modules should update and normal module communication will be restored. It is important that no VC domain changes are made until the following step is fully completed. From the VCM GUI, select “Tools” => “Reset Virtual Connect Manager.” This will force resynchronization of the modules if not synchronized in Step 3 above.IMPORTANT : If the NO_COMM condition was present or detected during one of the VCM administrative update tasks (listed in the DESCRIPTION section above), VCM may automatically resynchronize the modules, which would create a temporary VC domain-wide network outage during VC module initialization in either Step 3 or Step 5 above (but not both). Outage time will vary depending on the size of the VC domain. Scenario 2 - Enclosure Bay IP Addressing is being used to provide IP Addresses to the VC Ethernet Modules and the OA firmware version is 2.60 (or earlier). If iLO DNS name registrations are statically assigned in the DNS infrastructure, move to Step 3 below: If relying on Dynamic DNS updates for iLO, the OA firmware version must be updated to at least OA FW 3.11 before proceeding with the next step, otherwise iLO will only be reachable by IP address and there may be other ramifications to iLO LDAP Authentication. In the OA, in Enclosure Bay IP Addressing, Select the “Interconnect Bays” tab and remove the DNS server IP address entries from the “Shared Interconnect Settings.” Click Apply. In the OA, in Enclosure Bay IP Addressing, Select the “Device Bays” tab and remove DNS server IP address entries from the “Shared Interconnect Settings” and click Apply. Within 5 minutes, the DNS settings for the modules should update and normal module communication will be restored. It is important that no VC domain changes are made until the following step is fully completed. From the VCM GUI, select “Tools” => “Reset Virtual Connect Manager.” This will force resynchronization of the modules if not synchronized in Step 3 above.IMPORTANT : If the NO_COMM condition was present or detected during one of the VCM administrative update tasks (listed in the DESCRIPTION section above), VCM may automatically resynchronize the modules, which would create a temporary VC domain-wide network outage during VC module initialization in either Step 4 or Step 6 above (but not both). Outage time will vary depending on the size of the VC domain. Scenario 3 - External DHCP is being used to provide IP Addresses to the VC Ethernet Modules with any version of OA firmware: On the External DHCP Scope, create an exclusion range of IP addresses (preferably only the VC Ethernet module addresses). This exclusion range needs to be configured within EBIPA on the OA. In the OA, in Enclosure Bay IP Addressing, select the “Interconnect Bays” tab and configure the IP Addresses that were excluded in Step 1 above for bays that contain VC Ethernet modules. Do not configure DNS Server entries. Click Apply. It is important that no VC domain changes are made until the following steps are fully completed. Reboot the standby and primary VC modules to force them to use the new EBIPA lease. In a redundant design, the modules should be rebooted serially to mitigate downtime. a. Reset the standby VC Module from OA. b. Wait 15 minutes for the standby module to recover. c. Reset the primary VC Module from OA. d. Within 5 minutes, normal module communication will be restored. IMPORTANT : If the NO_COMM condition was present or detected during one of the VCM administrative update tasks (listed in the DESCRIPTION section above), VCM may automatically resynchronize the modules, which would create a temporary VC domain-wide network outage during VC module initialization. Outage time will vary depending on the size of the VC domain.

I got this questions two times this week “What is the benifit of VMware Enterprise Plus?” when I was a VMware customer I went Enterprise Plus right away…Lots of people complained however its great value IMO.   Perhaps the biggest value of Enterprise plus is just the licensing core count increase from 6 to 12.  The current Nahalem EX processors are at 8 cores, and AMD are at 12….Besides this however there are other great features:

1. Host Profiles-  These are used to automate configurations and ensure compliance; VMware is adding more and more configuration parameters that are included in each release.
2. 8 Core SMP virtual machines
3. Network I/O Control this is used to QOS virtual network resources
4. Storage I/O Control- priortization for VMs resources to shared storage, redistibutes vms un
5. Distributed Virtual Switch- Besides trimming down to one switch, and then adding in hosts for consistency a few other benefits…PVLANS, Load Based Teaming, ingress traffic shaping , required for Cisco Nexus 1000v integration

Here is a quick few use cases and review on Pvlans (they were new to me) :

• Communities can communicate with eachother in community and router use case: DMZ with 1 app server and 1 corresponding database server. 
• Isolated- Can only communicate with router  use case:  in a DMZ where you have a standalone webserver that doesn’t have the needs to communicate to other servers in the DMZ as often the case with DMZ; 2nd use case in a desktop vdi enviroment where desktops don’t need to communicate with eachother (This example is from Eric Slueth blog video on Pvlans)
• Promiscous – For routers.

Recently I was helping a customer architect a solution and I went back to the Best Practices for Vpshere and the EVA you can find it here:  http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA1-2185ENW.pdf

I thought I would make a quick summation and comment as some of it seems neglected in terms of being updated.

1. When creating hosts in commandview create them as Type: VMware
2. Use a single disk group with the same size disks and the largest possible disk group
3. Single Diskgroup sparing is sufficent unless MTTR is > 7 days
4. Don’t use VRaid 6 – Vraid 5 provides adequate redundancy
5. When using disks of varying performance characteristics still use a single diskgroup
6. Balance your VMFS Luns across both controllers for ownership with alternating failback and failover policies  read more here (http://www.ivobeerens.nl/?p=465)
7. Configure Round Robin advanced parameters to IOPS=1….I dont think HP is right here this was fixed fixed in Vpshere 4 update 1; This shouldnt be necessary
8. When using DR groups, ensure that DR groups managing controllers are spread across controllers
9. Use less than 16 VMDKs per VMFS datastore
10. Use the same lunid per host per lun
11. Create VMFS datastores through Vcenter for proper alignment
12. For heavy i/o load vms use the paravirtualized virtualized virtual adapters for the VM data Luns
13. Verify data drives for windows 2003 machines within os for proper alignment
14. Set Round Robin multipathing on your hosts and then reboot; dont forget to set your Microsoft clusters to MRU here is the quick and easy command:

esxcli nmp satp setdefaultpsp --satp VMW_SATP_ALUA --psp VMW_PSP_RR