Unregister vSphere PlugIns

Source: http://malaysiavm.com/blog/how-to-remove-cisco-nexus-1000v-plugin/
Posted by:  jlchannel


The Cisco Nexus 1000V switch is a pure software implementation of a Cisco Nexus switch. It resides on a server and integrates with the hypervisor to deliver VN-Link virtual machine-aware network services. The Cisco Nexus 1000V switch takes advantage of the VMware vSphere vNetwork Distributed Switch framework to offer tightly integrated network services as part of both a server virtualization strategy and a broader data center virtualization strategy. In addition, the switch provides operations and management consistency with existing Cisco Nexus and Cisco Catalyst switches.

Here I would like to share how to remove Cisco Nexus 1000V Plugin
1. To view the extension key on the vCenter Server, open an Internet Browser, and enter the URL path http:///mob
2. Authentication dialog box open, Enter the username and password and click OK

3. The Managed Object Browser (MOB) open the Service Instance page, in the value column of the Properties table, click Content

4. In the Value column of the Properties table, Click extensionManager OR you can open browser with URL http://localhost/mob/?moid=ExtensionManager

5. In the Methods table, click UnregisterExtension

6. In the Value of the Parameters table, paste “Cisco_Nexus_1000V_1850055053″ and click Invoke Method.


Void MOB

Netapp: FC Ports funktion verändern (Target/Initiator)

> priv set advanced

fcadmin config [-e | -d] [ -t <type>] [<adapter> [<adapter> ... ]]
 Controls and displays the configurable FC adapters
        adapter -- adapter name
        -t type -- target | initiator | unconfigured
        -e      -- enable adapter (set online)
        -d      -- disable adapter (set offline)
 e.g.: fcadmin config -t target 0a 0b

Netapp: DFM PerfData verschieben

To move the perf data to another location, you can use the below command
# dfm datastore setup -p \\cifs-server\cifs-share\perfdata

This command will take care of the entire process.
i.e. (create a new directory, if not available) and move the perf data to this directory & then finally point the DFM server to use the perf data from this new location.

Before running the command, make sure you have done the following steps to make sure DFM server get access to the CIFS share

1. Add a user having privileges on the CIFS share as an “administrator” on the  DFM station.

2. Set the DFM Server service “Log On as” user as the above user.

3. Set the DFM Scheduler service “Log On as” user as the above user.

4. Add this user to the DFM with GlobalFullControl role.

Also read
http://now.netapp.com/NOW/knowledge/docs/DFM_win/rel38/html/faq/index.shtml#_9.15

Netapp VSC - Virtual Storage Console zeigt falsche Controller / IPs an

Es kommt immer wieder vor das in der Netapp VSC (Virtual Storage Console) falsche Controller bzw. Controller mit falsche IPs angezeigt werden, nachdem ein "Update" der durchgeführt wurde. Diese "Altlasten" kommen entweder von alten Storagesystemen oder von System deren IP irgendwann mal geändert wurde. 

Ist ein einfacher "remove" oder ein umkonfigurieren des bestehenden Controller-Eintrags nicht möglich, so gibt es die möglichkeit die Konfigurationsdatei des VSC zu entfernen und einen neuen Scan durchlaufen zu lassen. Die Konfigdatei findet sich unter:

> C:\Program Files\NetApp\Virtual Storage Console\etc\vsc\vsc.xml

Diese Datei am besten wegsichern (kopieren & umbenennen reicht) und im Anschluss die kompletten Netapp Dienste sowie Virtual Center Dienste neustarten.  Im Anschluss daran ein "Update"(rescan) im VSC machen und schon sind nur noch die aktuellen Systeme vorhanden.

Hinweis: Etwaige Konfigurationen und Einstellungen im SMVI oder im Bereich "Provisioning and Cloning" sind davon nicht betroffen. Diese Bereiche unterhalten Ihre eigenen configuration files.

VM Multicore Prozessoren zuweisen

This new setting, which you can add to the virtual machine configuration (.vmx) file, lets you set the number of cores per virtual socket in the virtual machine.

To implement this feature:

1. Power off the virtual machine.
2. Right-click on the virtual machine and click Edit Settings.
3. Click Hardware and select CPUs.
4. Choose the number of virtual processors.
5. Click the Options tab.
6. Click General, in the Advanced options section.
7. Click Configuration Parameters.
8. Include cpuid.coresPerSocket in the Name column.
9. Enter a value (try 2, 4, or 8) in the Value column.
   Note: Ensure that cpuid.coresPerSocket is divisible by the number of vCPUs in the virtual machine. That is, when you divide cpuid.coresPerSocket by the number of vCPUs in the virtual machine, it must return an integer value. For example, if your virtual machine is created with 8 vCPUs, coresPerSocket can only be 1, 2, 4, or 8.
   
   The virtual machine now appears to the operating system as having multi-core CPUs with the number of cores per CPU given by the value that you provided in step 9.
   
10. Click OK.
11. Power on the virtual machine.

For example:

Create an 8 vCPU virtual machine and set cpuid.coresPerSocket = 2. Window Server 2003 SE running in this virtual machine now uses all 8 vCPUs. Under the covers, Windows sees 4 dual-core CPUs. The virtual machine is actually running on 8 physical cores.

Note:

• Only values of 1, 2, 4, 8 for the cpuid.coresPerSocket are supported for the multi-core vCPU feature in ESX 4.0.
• In ESX 4.0, if multi-core vCPU is used, hot-plug vCPU is not permitted, even if it is available in the UI.
• Only HV 7 virtual machines support the multi-core vCPU feature.

Important: When using cpuid.coresPerSocket, you should always ensure that you are in compliance with the requirements of your operating system EULA (Regarding the number of physical CPUs on which the operating system is actually running)

Quelle: vmware KB -> KB Article: 1010184