Invalid configuration for device ‘0’ Error when removing vm hard disk


vm invalid config

1.verify the hard disk source storage
2.These error came when mounted LUN inaccessible
3.Try to remove the vm hard disk
4.If error persists remove the VM from inventory
5.Take the backup of .vmx file and download
6.Edit the .vmx file and remove the scsi(x:x) id for the disk the file and upload it into datastore and add to inventory
8.Now power on the VM
9.Once LUN comes back online add that .vmdk which was removed from .vmx file earlier

Categories: VMware

VMware Tools installation in RHEL 5.4

1. Right click the RHEL 5.4 VM and click “Install/Upgrade VMware Tools”

2. Create one folder. I created folder in desktop and named as “Test”

3.Copy the media files from CD drive to “Test” folder

4.Open the Terminal,


5. Unzip the archive file by using tar command

6. Go to “vmware-tools-distrib” directory


7. install the tools by executing  ./

8. While installing choose number for screen resolution ( I selected 12=1024*768)

9. After few seconds vmware tools installed successfully.

Categories: VMware

Safely Remove Hardware Option in Windows VM Guest OS

We can see safely remove hardware option in windows guest operating system. This is critical one, if we remove network adapter it will cause VM unreachability.

Device Eject Option

We need to enable one option after power off the VM to hide this “Safely Remove Hardware” Option.

Power off the VM and right click “Edit Settings”

Go to Options and General,

Go to Configuration Parameters

Add Parameter “devices.hotplug” = “false”  without quotes

config parameter

Now, Power On the VM and you can see the task bar, Safely Remove Hardware Hided.

Categories: VMware

Windows internal database accessing


Microsoft products such as Windows Server Update Services (WSUS) 3.0 and Windows Sharepoint Services (WSS) 3.0 ship with SQL Server 2005 Embedded Edition. Now called the Windows Internal Database, more and more system administrators charged with managing WSUS and WSS are faced with the challenge of managing these databases. Since most of these system administrators are not full-fledged DBAs, how do they manage the Windows Internal Database?


The Windows Internal Database is an embedded data service that can only be used by a handful of Windows Services. It is designed in such a way that you are not allowed to connect to and use this particular database service for non-Microsoft products. By default, installing either WSUS 3.0 or WSS 3.0 will create the databases on the C:\ partition and will cause administration issues such as insufficient disk space. It is quite confusing to manage this SQL Server instance as it does not appear as a SQL Server service nor are there management tools included with the products. The easiest way is to use SQL Server Management Studio Express. You can install a copy of SQL Server Management Studio Express on the server running your WSUS 3.0 or WSS 3.0. You then register this instance using Named Pipes as this is the only configuration for connectivity. Use this server name when you register this instance


windows internal db access

If you prefer to use scripts to manage these databases, you can download and install the SQL Server 2005 Command Line Query Utility – sqlcmd . This tool will be installed, by default, on this directory

C:\Program Files\Microsoft SQL Server\90\Tools\binn

To connect to the database instance, you need to run the sqlcmd.exe utility, passing the instance name and your credentials

sqlcmd -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query –E

You can then run your administrative T-SQL scripts once connected to this database instance.


While these are possible reasons to administer the Windows Internal Database, it is not recommended to do anything beyond performing backups, moving or shrinking the database files. Modifying database schema or database properties would break supportability of these products. Plus, any changes made to these databases can be overwritten by the products’ service packs or cumulative updates.


Reference: Internal DB Access

Categories: MSSQL

How to find Brocade Model Number by using switch type

March 31, 2014 Leave a comment

Switch Type Switch Name
1 Brocade 1000 Switches
2,6 Brocade 2800 Switch
3 Brocade 2100, 2400 Switches
4 Brocade 20×0, 2010, 2040, 2050 Switches
5 Brocade 22×0, 2210,2240, 2250 Switches
7 Brocade 2000 Switch
9 Brocade 3800 Switch
10 Brocade 12000 Director
12 Brocade 3900 Switch
16 Brocade 3200 Switch
17 Brocade 3800VL
18 Brocade 3000 Switch
21 Brocade 24000 Director
22 Brocade 3016 embedded Blade Switch
23 8Gbit 10-port embedded fabric switch
26 Brocade 3850 Switch
27 Brocade 3250 Switch
29 Brocade 4012 EmbeddedBlade Switch
32 Brocade 4100 Switch
33 Brocade 3014 Switch
34 Brocade 200E Switch
36 Brocade FR4-18i DirectorBlade
37 Brocade 4020 Embedded Blade Switch
38 Brocade 7420 SAN Router
40 Fibre Channel Routing (FCR) Front Domain
41 Fibre Channel Routing (FCR) Xlate Domain
42 Brocade 48000 Director
43 Brocade 4024 Embedded Blade Switch
44 Brocade 4900 Switch
45 Brocade 4016 Embedded Blade Switch
46 Brocade 7500 Switch
47 Brocade FC4-16IP Director Blade
50 Brocade 4GB FC Port Blade
51 Brocade 4018 Embedded Blade Switch
55 Brocade FA4-18i Extension Director Blade
55,2 Brocade 7600 Switch
58 Brocade 5000 Switch
62 Brocade DCX Backbone
63 Brocade 8Gb Backbone Core Fabric Switch
64 Brocade 5300 Switch
66 Brocade 5100 Switch
67 Brocade Encryption Switch
68 Brocade 8Gb 16 FC 2 GigE ports Director Encryption Blade
69 Brocade 5410 Blade
70 Brocade 8GB 10 Port Embedded Fabric Switch
71 Brocade 300 Switch
72 Brocade 5480 Embedded Blade Switch
75 Brocade M5424 Embedded Blade Switch
76,6 Brocade 8000 FCoE Switch
77,3 Brocade DCX-4S
82 Brocade 8Gb 24-port Embedded Blade Switch
83 Brocade 16-FC port,
6-GE port, auto sensing 1, 2, 4 or 8Gbit Switch
86 Brocade 8Gbit 26-port embedded Switch
88 Brocade 10Gb 24 GigE ports DCE Blade
89 Brocade 8Gb 12 FC, 1Gb 10 GigE FCIP Blade, 10Gb 2 GigE ports FCR

Brocade sheet attached here: switch-types-blads-ids-product-names

Categories: Brocade

Switch ASIC

March 19, 2014 Leave a comment

ASIC are Platforms Generation Specific.

GoldenEye = Brocade 200E and other switches

GoldenEye2 = Brocade 300 and others

Condor = Brocade 48000 and others

Condor2 = DCX and others

Condor3 = 16G Capable Switches

Categories: Brocade

Alignment Offset in Windows

March 15, 2014 Leave a comment

Go to RUN->CMD-> execute the below command

wmic partition get BlockSize, StartingOffset, Name, Index

Categories: Microsoft