Monday, October 6, 2014

UCS C220 M3 VIC 1225 and Vsphere note







Cisco Unified Computing System Overview
The Cisco Unified Computing System™ (Cisco UCS®) is a next-generation data center platform that unites compute, networking, storage access, and virtualization resources in a cohesive system designed to reduce total cost of ownership (TCO) and increase business agility. The system integrates a low-latency, lossless 10 Gigabit Ethernet unified network fabric with enterprise-class blade and rack x86-architecture servers. The system is an integrated, scalable, multichassis platform in which all resources participate in a unified management domain.
Product Overview
A Cisco® innovation, the Cisco UCS Virtual Interface Card (VIC) 1225 (Figure 1) is a dual-port Enhanced Small Form-Factor Pluggable (SFP+) 10 Gigabit Ethernet and Fibre Channel over Ethernet (FCoE)-capable PCI Express (PCIe) card designed exclusively for Cisco UCS C-Series Rack Servers. With its half-height design, the card preserves full-height slots in servers for third-party adapters certified by Cisco. It incorporates next-generation converged network adapter (CNA) technology from Cisco, providing investment protection for future feature releases. The card enables a policy-based, stateless, agile server infrastructure that can present up to 256 PCIe standards-compliant interfaces to the host that can be dynamically configured as either network interface cards (NICs) or host bus adapters (HBAs). In addition, the Cisco UCS VIC 1225 supports Cisco Data Center Virtual Machine Fabric Extender (VM-FEX) technology, which extends the Cisco UCS fabric interconnect ports to virtual machines, simplifying server virtualization deployment.
Figure 1. Cisco UCS VIC 1225
Features and Benefits
Stateless and agile: The personality of the card is determined dynamically at boot time using the service profile associated with the server. The number, type (NIC or HBA), identity (MAC address and World Wide Name [WWN]), failover policy, bandwidth, and quality-of-service (QoS) policies of the PCIe interfaces are all determined using the service profile. The capability to define, create, and use interfaces on demand provides a stateless and agile server infrastructure (Figure 2).
Figure 2. Virtual Device Support on the Cisco UCS VIC 1225
Network interface virtualization: Each PCIe interface created on the VIC is associated with an interface on the Cisco UCS fabric interconnect, providing complete network separation for each virtual cable between a PCIe device on the VIC and the interface on the fabric interconnect (Figure 3).
Figure 3. Cisco UCS VIC 1225 Architecture
Cisco SingleConnect Technology
Cisco® SingleConnect technology provides an exceptionally easy, intelligent, and efficient way to connect and manage computing in the data center. Cisco SingleConnect technology is an exclusive Cisco innovation that dramatically simplifies the way that data centers connect to:
● Rack and blade servers
● Physical servers and virtual machines
● LAN, SAN, and management networks
The solution addresses the challenges of today’s data center, and the result is a simple, intelligent, and efficient fabric:
● Easy: Cisco SingleConnect technology provides a “wire once and walk away” solution that eliminates traditional manual, time-consuming, error-prone processes and instead makes connecting servers to the Cisco Unified Computing System™ (Cisco UCS®) fast and easy.
● Intelligent: the technology is intelligent because it uses a zero-touch model to allocate I/O connectivity (LAN, SAN, and management) across any type of server: physical rack and blade servers and virtual machines. The network intelligence helps Cisco UCS adapt to the needs of applications. Rather than limiting applications to specific servers, Cisco UCS makes it easy to run any workload on any server.
● Efficient: the technology is highly efficient because LAN, SAN, and management connections are shared over a single network, increasing utilization while reducing the number of moving parts compared to traditional approaches with multiple networks.
Cisco SingleConnect technology is implemented with an end-to-end system I/O architecture that uses Cisco Unified Fabric and Cisco Fabric Extender Technology (FEX Technology) to connect every Cisco UCS component with a single network and a single network layer. As customers expect from Cisco, the Cisco UCS I/O architecture is based on open standards and is reliable, available, and secure.
Cisco Data Center VM-FEX Technology: Cisco Data Center VM-FEX technology extends fabric interconnect ports directly to virtual machines, eliminating software-based switching in the hypervisor. Cisco Data Center VM-FEX technology collapses virtual and physical networking infrastructure into a single infrastructure that is fully aware of the virtual machines’ locations and networking policies (Figure 4). Cisco Data Center VM-FEX technology is implemented by Cisco VICs with a pre-standard implementation of IEEE 802.1BR Port Extender.
Figure 4. Cisco Data Center VM-FEX with Cisco UCS VIC 1225
Table 1 summarizes the main features and benefits of the Cisco UCS VIC 1225.
Table 1. Features and Benefits
Feature
Benefit
x16 PCIe generation-2 interfaces
Delivers greater throughput
2 x 10-Gbps unified I/O
● Delivers 20 Gbps to the server
● Helps reduce TCO by consolidating the overall number of NICs, HBAs, cables, and switches because LAN and SAN traffic run over the same adapter card and fabric
Up to 256 dynamic virtual adapters and interfaces
● Creates fully functional unique and independent PCIe adapters and interfaces (NICs or HBAs) without requiring single-root I/O virtualization (SR-IOV) support from OSs or hypervisors
● Allows these virtual interfaces and adapters to be configured and operated independently, just like physical interfaces and adapters
● Creates a highly flexible I/O environment needing only one card for all I/O configurations
Note: Cisco UCS VIC 1225 hardware is SR-IOV capable, and you can enable SR-IOV after SR-IOV is broadly supported by the popular operating systems. Please refer to UCS Manager configuration limits for your specific OS and environment in the configuration guide.
Cisco SingleConnect technology
A single unified network - the same network brings LAN, SAN, and management connectivity to each server
Cisco Data Center VM-FEX technology
● Unifies virtual and physical networking in a single infrastructure
● Provides virtual machine visibility from the physical network and a consistent network operating model for physical and virtual servers
● Enables configurations and policies to follow the virtual machine during virtual machine migration
● Provides a pre-standard implementation of the IEEE 802.1BR Port Extender standard
Centralized management
Enables the card to be centrally managed and configured by Cisco UCS Manager
Network architecture
Provides a redundant path to the fabric interconnect using hardware-based fabric failover
More than 600,000 I/O operations per second (IOPS)
Provides high I/O performance for demanding applications
Support for lossless Ethernet
Uses Priority Flow Control (PFC) to enable FCoE as part of the Cisco unified fabric
Broad OS and hypervisor support
Supports customer requirements for Microsoft Windows, Red Hat Enterprise Linux, SUSE Linux, VMwarevSphere, and Citrix XenServer
Product Specifications
Table 2 lists the specifications for the Cisco UCS VIC 1225.
Table 2. Product Specifications
Item
Specifications
Standards
● 10 Gigabit Ethernet
● IEEE 802.3ae
● IEEE 802.3x
● IEEE 802.1q VLAN
● IEEE 802.1p
● IEEE 802.1Qaz
● IEEE 802.1Qbb
● Pre-standard IEEE 802.1BR
● Jumbo frames up to 9 KB
● Fibre Channel Protocol (FCP)
● Small Computer System Interface (SCSI)-FCP
● T11 FCoE
Components
Cisco UCS custom application-specific integrated circuit (ASIC)
Ports
2 x 10-Gbps FCoE SFP+ ports
Connectivity
PCIe 2.0 x16 form factor
Performance
10-Gbps line rate per port
Management
Cisco UCS Manager Release 2.0 (2) and higher
Number of interfaces
256 virtual interfaces (approximately 8 are reserved for internal use; other factors such as the OS and
hypervisor may limit this number further)
Physical dimensions
Length = 6.6 in (16.76 cm)
Width = 2.5 in. (6.35 cm)
Typical power
12 watts (W)
System Requirements
The Cisco UCS VIC 1225 is designed for use only on Cisco UCS C-Series Rack Servers. Cisco UCS VIC 1225 is supported on Cisco UCS C260 M2, C460 M2, C220 M3, C240 M3, C22 M3, C24 M3, C220 M4, C240 M4, and C460 M4 rack servers. One or more Cisco UCS VIC 1225 cards are supported on these servers depending on the slot configuration. See the server configuration guide for details.

UCSC-PCIE-C10T-02 Cisco VIC 1225T Dual Port 10GBaseT CNA Half





KB: Troubleshooting a black screen when logging into a Horizon View virtual desktop using PCoIP (1028332)

Troubleshooting a black screen when logging into a Horizon View virtual desktop using PCoIP (1028332)

Symptoms

  • When attempting to connect to a Horizon View virtual machine using the PCoIP protocol, a black screen is displayed temporarily and the client disconnects. Connecting to the same virtual machine using RDP protocol is successful.
  • Internal PCoIP connections may be successful, however connecting externally results in a black screen.
  • Connections from a PCoIP Zero Client fail, but connecting using the Horizon View software client is successful.

Monday, September 29, 2014

note about VMotion

vMotion VM between vSphere clusters – vSphere 4.X and vSphere 5.X

Yes, you can migrate VM’s between vSphere clusters (even between different versions) as long as below conditions are met:
  • vSphere clusters must be managed by single vCenter server
  • vSphere clusters must be within single DataCenter object in vCenter server
  • Pre vSphere 5.1 – clusters must have an access to the same datastore.
  • vMotion network is stretched between clusters.
  • Processors must be from the same vendor (Inter or AMD) and family (model) on both  clusters or both clusters have common EVC baseline applied.
  • Virtual Machine hardware version is supported by hypervisor – very useful during migration to new hardware or new version of vSphere platform.
  • If you have vDS implemented, make sure dvportgroup is span across both clusters 



Long Distance VMotion

Requirements:
·         An IP network with a minimum bandwidth of 622 Mbps is required.
·         The maximum latency between the two VMware vSphere servers cannot exceed 5 milliseconds (ms).
·         The source and destination VMware ESX servers must have a private VMware VMotion network on the same IP subnet and broadcast domain.
·         The IP subnet on which the virtual machine resides must be accessible from both the source and destination VMware ESX servers. This requirement is very important because a virtual machine retains its IP address when it moves to the destination VMware ESX server to help ensure that its communication with the outside world (for example, with TCP clients) continues smoothly after the move.
·         The data storage location including the boot device used by the virtual machine must be active and accessible by both the source and destination VMware ESX servers at all times.
·         Access from VMware vCenter, the VMware Virtual Infrastructure (VI) management GUI, to both the VMware ESX servers must be available to accomplish the migration.

Can I migrate running VM between datacenters using vMotion?


https://communities.vmware.com/message/2166733

Thursday, September 11, 2014

VMware NSX Manager 6.0.5 install


1. General error when deploy NSX manager ova on vcenter 5.5 web client 


2.  Search the error and read some vcenter logs but didn't get any related error

3. Deploy use vSphere C# client is working:



Thursday, August 21, 2014

software-defined storage (SDS) note VSAN,Nutanix

Read VMware vSphere Blog article VMware Virtual SAN with Cisco UCS Reference  Architecture
 http://blogs.vmware.com/vsphere/2014/08/vmware-virtual-san-cisco-unified-computing-system-reference-architecture.html
Which brief the integration of VSAN and UCS C240-M3 series server, the whitepaper is information whatever you deploy VSAN with UCS C-series or not.







Nutanix Virtual Computing Platform compared to VMware VSAN 1.0
  • This article mention lot of features of Nutanix and compared to VSAN.
  • It is interesting for comment about the SAN concepts

VSAN
VMware Education-VMware Virtual SAN Fundamentals [V5.5]
http://mylearn.vmware.com/mgrreg/courses.cfm?ui=www_edu&a=one&id_subject=55806

Technical Deep Dive -Keynote
SDS on ESXi Hypervisor, x86 servers
Embedded in vSphere kernel
Built-in resiliency
inexpensive disk and ssd
POC cheklist pdf

Nutanix NX-3050 series

This article about the complete Review of Nutanix NX-3050 series by Brian Shur :

http://www.datacenterzombie.com/nutanix-review-nx-3050-series/


  1. Architecture
  2. Ratings and reasons
  3. Cost
  4. Management console Web interface
  5. Upgrade note
  6. Performance of VMware View Planner 
  7. Nutanix DR



Wednesday, August 20, 2014

Cisco Bugid CSCul44421 Chassis seeprom local IO failure error on Switch

Symptom:

Error accessing shared-storage fault.

Problem Details: affected="sys/mgmt-entity-A"
cause="device-shared-storage-IO-error"
changeSet=""
code="E4196535"
created="2013-12-18T08:50:03"
descr="device Fxxxxxxxxxxxx, error accessing shared-storage"
dn="event-log/785673"
id="785673"
ind="state-transition"


From Cisco support :

The error accessing shared-storage fault is not harmful and does not affect system functionalities.  In UCS chassis design, we build in a chip called, SEEPROM, on the backplane. SEEPROM is a permanent memory and used to store cluster database version to avoid the case of cluster database being overwritten by old version when failover happens.

The communication between IO module and SEEPROM is one way. We store the identical SAM DB version in three chassis rather than in one (so called three chassis redundancy). Because the communication between IO module and SEEPROM happens only one way, the error accessing shared-storage fault can happen sometimes - this is system behavior per specification and design. So, as long as one SEEPROM is readable, the UCS works normally.

If the error accessing shared-storage fault is currently in cleared state and does not raise again, do not apply the workaround and do not do anything.

If the error accessing shared-storage fault is raised state and is never cleared, or the fault keeps coming back, try the following workarounds:

* Reboot the IO module.


* If alert does not clear, reseat IO module. Make sure it's firmly seated.

https://tools.cisco.com/bugsearch/bug/CSCul44421

Other workaround mentioned in Cisco support forum:

  • Reboot/Reseat IOM
  • Reboot Chassis

https://supportforums.cisco.com/discussion/11349691/ucs-error-accessing-shared-storage-f0863

Wednesday, July 30, 2014

Backing up ESXi host configuration data

Using the ESXi Command Line

To synchronize the configuration changed with persistent storage, run the command:

vim-cmd hostsvc/firmware/sync_config

To backup the configuration data for an ESXi host, run the command:

vim-cmd hostsvc/firmware/backup_config

Note: The command should output a URL in which a web browser may be used to download the file. The backup file is located in the/scratch/downloads directory as configBundle-<HostFQDN>.tgz

The backup file should be move to the local datastore e.g. /vmfs/volumes/local1/ESXi_Backup/ if you aew noting going to download the file by the URL 



Using the ESXi Command Line:
Note: When restoring configuration data, the build number of the host must match the build number of the host that created the backup file.
  1. Put the host into maintenance mode by running the command:

    vim-cmd hostsvc/maintenance_mode_enter
  2. Copy the backup configuration file to a location accessible by the host and run the command:

    In this case, the configuration file was copied to the host's /tmp directory. For more information, see Using SCP to copy files to or from an ESX host (1918).
vim-cmd hostsvc/firmware/restore_config /tmp/configBundle.tgz

Note: Executing this command will initiate an automatic reboot of the host after command completion.


http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2042141

Monday, July 28, 2014

SW ,HW,OS Compatibility note

I am trying to gather links and resource in terms of checking Compatibility when design, deploy or upgrade...

The VMware Compatibility Guide shows the certification status of operating system releases for use as a Guest OS by the following VMware products:
• VMware ESXi/ESX Server 3.0 and later
• VMware Workstation 6.0 and later
• VMware Fusion 2.0 and later
• VMware ACE 2.0 and later
• VMware Server 2.0 and later
http://partnerweb.vmware.com/comp_guide2/pdf/VMware_GOS_Compatibility_Guide.pdf

VMware Compatibility Guide Portal:
VMware provides support only for the devices that are listed in this document

http://www.vmware.com/resources/compatibility/search.php


Correlating VMware products build numbers to update levels (1014508)

VMware vSphere and vCloud suite build numbers table

This table provides a list of all VMware vSphere and vCloud suite build numbers and release dates. The build numbers are based on full installations. Patching ESXi/ESX hosts increments the build number that shows in vCenter Server.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1014508


Enhanced vMotion Compatibility (EVC) processor support (1003212)
For hosts in cluster with different version of CPU

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003212




IBM servers OS support
http://www-03.ibm.com/systems/info/x86servers/serverproven/compat/us/nos/vmware.html

Wednesday, June 4, 2014

How to update the UCS’s Capability Catalog to enable new server components to be displayed correctly

What is Capability Catalog

From UCS Release Note "Cisco UCS Manager uses the catalog to update the display and configurability of server components such as newly qualified DIMMs and disk drives. The Cisco UCS Manager Capability Catalog is a single image, but it is also embedded in Cisco UCS Manager. Cisco UCS Manager 2.1(x) releases work with any 2.1(x) catalog file, but not the 1.x or 2.0 catalog versions. If a server component is not dependent on a specific BIOS version, using it and having it recognized by Cisco UCS Manager is primarily a function of the catalog version. The catalog is released as a single image in some cases for convenience purposes in addition to being bundled with Cisco UCS infrastructure releases"

1. Go to UCS Manager Release Notes page to locate the corresponding “Capability Catalog” update content.  http://www.cisco.com/c/en/us/support/servers-unified-computing/ucs-manager/products-release-notes-list.html
2. Click on “Capability Catalog” on the UCSM 2.0 Release Notes
 3. Download the "Capability Catalog”
 4. Locate “Capability Catalog” tab under Admin in UCSM and Click “+” to start uploading the new Catalog file just downloaded


a
 5. Wait it process to complete the update, it will activate automatically.





Monday, May 26, 2014

KB Datastore renaming fails when the Virtual Infrastructure Client is connected directly to ESX host (1004845)

Datastore renaming fails when the Virtual Infrastructure Client is connected directly to ESX host (1004845)


Details

When the Virtual Infrastructure (VI) Client is connected directly to an ESX host, renaming a datastore fails.

Solution

To rename the datastore:
  1. Log in to the VirtualCenter Server using the Virtual Infrastructure Client.
  2. Select Host > Configuration > Storage.
  3. Right-click on the datastore and select Rename, or click the datastore name directly.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Tuesday, May 20, 2014

Vmware KB Testing VMkernel network connectivity with the vmkping command (1003728)

Testing VMkernel network connectivity with the vmkping command (1003728)

Purpose

For troubleshooting purposes, it may be necessary to test VMkernel network connectivity between ESX hosts in your environment.

This article provides you with the steps to perform a vmkping test between your ESX hosts.

Resolution

The vmkping command sources a ping from the local VMkernel port.
 
To initiate a vmkping test from the console of an ESX Server host:
  1. Connect to the ESX/ESXi host using an SSH session. For information see Tech Support Mode for Emergency Support (1003677) andUsing Tech Support Mode in ESXi 4.1 and 5.0 (1017910).
  2. In the command shell, run the command:

    # vmkping x.x.x.x
    where x.x.x.x is the hostname or IP address of the server that you want to ping.
  3. If you have Jumbo Frames configured in your environment, run the vmkping command with the -s and -d options.

    # vmkping -d -s 8972 x.x.x.x
    Note: If you have more then one vmkernel port on the same network (such as a heartbeat vmkernel port for iSCSI) then all vmkernel ports on the host on the network would need to be configured with Jumbo Frames (MTU: 9000) too. If there are other vmkernel ports on the same network with a lower MTU then the vmkping command will fail with the -s 8972 option. Here in the command -d option sets DF (Don't Fragment) bit on the IPv4 packet.

  4. In ESXi 5.1, you can specify which vmkernel port to use for outgoing ICMP traffic with the -I option:

    # vmkping -I vmkX x.x.x.x

    Notes: 
    • ICMP response behavior has changed in ESXi 5.1. For more information, see Change to ICMP ping response behavior in ESXi 5.1 (2042189).
    • In releases prior to ESXi 5.1, the host will automatically select the vmkernel port based on the host's vmkernel routing/forwarding table. To display the host's vmkernel routing table, use the esxcfg-route -l command.
    • Verification of your MTU size can be obtained from a SSH session by using
esxcfg-nics -l

Output should be similar to:

# esxcfg-nics -l
Name    PCI           Driver      Link Speed     Duplex MAC Address       MTU    Description
vmnic0  0000:02:00.00 e1000       Up   1000Mbps  Full   00:50:56:17:0a:60 9000   Intel Corporation 82545EM Gigabit Ethernet Controller (Copper)
vmnic1  0000:02:01.00 e1000       Up   1000Mbps  Full   00:50:56:17:0a:65 9000   Intel Corporation 82545EM Gigabit Ethernet Controller (Copper)

esxcfg-vmknic -l 

Output should be similar to:

# esxcfg-vmknic -l

Interface  Port Group/DVPort   IP Family IP Address                    Netmask         Broadcast   MAC Address          MTU     TSO     MSS       Enabled Type

vmk1       iSCSI  IPv4      10.10.10.10                                255.255.255.0   10.10.10.255 00:50:56:XX:XX:64    9000    65535     true    STATIC

A successful ping response is similar to:
 
# vmkping 10.0.0.1
PING server(10.0.0.1): 56 data bytes
64 bytes from 10.0.0.1: icmp_seq=0 ttl=64 time=10.245 ms
64 bytes from 10.0.0.1: icmp_seq=1 ttl=64 time=0.935 ms
64 bytes from 10.0.0.1: icmp_seq=2 ttl=64 time=0.926 ms
--- server ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.926/4.035/10.245 ms
 
An unsuccessful ping response is similar to:
 
# vmkping 10.0.0.2
PING server (10.0.0.2) 56(84) bytes of data.
--- server ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 3017ms

 
Notes:
  • If you see intermittent ping success, this might indicate you have incompatible NICs teamed on the VMotion port. Either team compatible NICs or set one of the NICs to standby.
  • If you do not see a response when pinging by the hostname of the server, initiate a ping to the IP address. Initiating a ping to the IP address allows you to determine if the problem is a result of an issue with hostname resolution. If you are testing connectivity to another VMkernel port on another server remember to use the VMkernel port IP address because the server's hostname usually resolves to the service console address on the remote server.


Vmware Cluster datastore path dead

Symptoms:

  1. have 4 esxi5.1 hosts (esxi01-04) in vmware cluster, VM in two specific datastore cannot start up on esxi01 host
  2. checked the iSCSI Network adapter should be fine as only two datastore have issue
  3. checked the LUN mapping is fine
  4. Try rescan and refresh datatstore didn't solve the issue
  5. Try to disconnect and re-mount the datastore on esxi01 didn't solve the problem . 
  6. For a reason to resume service asap, migrate all VMs to TEMP datastore, unmount and detach the datastore for all esxi host
  7. unmaping LUN on storage side, rescan datastore on vmware cluster the problem LUN should be disappear.
  8. Remap LUN to esxi hosts, add to datasore cluster again, re-signature and format the LUN, put VM on it for testing 

Search through esxi logs and get result below:

standard input)-2014-05-xxT03:09:31.297Z cpu6:8198)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a9800037536d72502444xxxxxxxxb" state in doubt; requested fast path state update...
(standard input)-2014-05-xxT03:09:31.594Z cpu4:8401)ALERT: NMP: vmk_NmpVerifyPathUID:1167:The physical media represented by device naa.60a9800037536d72502444xxxxxx (path vmhba32:C0:T0:L13) has changed. If this is a data LUN, this is a critical error. Detect
(standard input)-2014-05-xxT03:09:31.594Z cpu4:8401)WARNING: ScsiDevice: 1422: Device :naa.60a9800037536d72502444xxxxxxx has been removed or is permanently inaccessible.
(standard input):2014-05-xxT03:09:32.410Z cpu4:8196)WARNING: HBX: 1548: HB failed due to no connectivity on [HB state abcdef02 offset 4059136 gen 17 stampUS 1847607014728 uuid 535950b3-29e2ce5d-488a-0025b501011f jrnl <FB 70200> drv 14.58] on vol 'XXXXXXX'
(standard input)-2014-05-xxT03:10:50.461Z cpu10:8202)WARNING: NMP: nmp_DeviceRequestFastDeviceProbe:237:NMP device "naa.60a9800037536d72502xxxxxxxx" state in doubt; requested fast path state update...
(standard input)-2014-05-xxT03:16:42.380Z cpu15:10515)WARNING: Vol3: 1717: Failed to refresh FS 535daf66-4b90cce6-fa7c-0025b50100ee descriptor: Device is permanently unavailable
(standard input)-2014-05-xxT03:16:42.661Z cpu15:10515)WARNING: Vol3: 1717: Failed to refresh FS 535daf66-4b90cce6-fa7c-0025b50100ee descriptor: Device is permanently unavailable

not sure whether this KB describe the exact issue but at least they got similar symptoms

VMFS Resignature causes thrashing between multiple VMware ESXi 4.x/5.x and ESX 4.x hosts (1026710

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1026710

Unmounting a LUN or detaching a datastore/storage device from multiple VMware ESXi 5.x hosts (2004605)
This article provides steps to unmount a LUN from an ESXi 5.x host, which includes unmounting the file system and detaching the device. These steps must be performed for each ESXi host.
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2004605

Thursday, May 15, 2014

networking device SIM note

For building a Lab consist of number of networks and cloud related products, i a am looking for some Router softwares which can connect different networks as the real router doing, There are some reference link below:

Cisco CSR1000v For Home Labs
http://www.fryguy.net/2013/12/27/cisco-csr1000v-for-home-labs/

Cisco CSR1000V vs the Fabled IOU
http://lamejournal.com/2013/12/28/cisco-csr1000v-vs-fabled-iou/

How to upgrade Titanium VMware image to 6.1.1

http://51sec.blogspot.hk/2013/03/how-to-upgrade-titanium-vmware-image-to.html