Uninstall:
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer
Reg_SZ: Logging
Value: voicewarmupx
The letters in the value field can be in any order. Each letter turns on a different logging mode. Each letter's actual function is as follows for MSI version 1.1:
v - Verbose output
o - Out-of-disk-space messages
i - Status messages
c - Initial UI parameters
e - All error messages
w - Non-fatal warnings
a - Start up of actions
r - Action-specific records
m - Out-of-memory or fatal exit information
u - User requests
p - Terminal properties
+ - Append to existing file
! - Flush each line to the log
x - Extra debugging information. The "x" flag is available only on Windows Server 2003 and later operating systems, and on the MSI redistributable version 3.0, and on later versions of the MSI redistributable.
Monday, December 28, 2009
Advanced UNIX
Linux:
* Create User: adduser plolla -d /home/plolla -s /bin/bash
* Set Password: passwd plolla
* Checking RAM: free -m
* uname -m (The output will read x86_64 for 64-bit and i686 or similar for 32-bit)
Solaris:
* Checking RAM: prtconf | head -3 |grep Mem
* /usr/bin/isainfo -kv (If your OS is 64-bit, you will see output like:64-bit sparcv9 kernel modules. If your OS is 32-bit, you will get this output: 32-bit sparc kernel modules)
* pkgchk -p | grep Package Name
* pkginfo -i system
* pvs -d - Displays the dynamic version of the file.
AIX:
* Checking RAM: $ lsattr -El sys0 | grep realmem
* prtconf
* bootinfo -y ----> hardware is 64-bit or 32
* bootinfo -K ----> kernel is 64-bit or 32 ( to check 64 kernel is installed go to /usr/lib/boot and look for " unix_64 "
Windows :
set p | findstr /i archi
1) PROCESSOR_ARCHITECTURE=x86 ..... 32-bit
2) PROCESSOR_ARCHITECTURE=AMD64 ... 64-bit
HPUX:
to find what OS : getconf KERNEL_BITS
what varsion can run :getconf HW_CPU_SUPP_BITS
$ file /stand/vmunix
/stand/vmunix: PA-RISC1.1 executable ---> 32-bit
/stand/vmunix: ELF-64 executable object file ---> 64-bit
To check the Kernel Variables: kctune or kmtune
* Create User: adduser plolla -d /home/plolla -s /bin/bash
* Set Password: passwd plolla
* Checking RAM: free -m
* uname -m (The output will read x86_64 for 64-bit and i686 or similar for 32-bit)
Solaris:
* Checking RAM: prtconf | head -3 |grep Mem
* /usr/bin/isainfo -kv (If your OS is 64-bit, you will see output like:64-bit sparcv9 kernel modules. If your OS is 32-bit, you will get this output: 32-bit sparc kernel modules)
* pkgchk -p | grep Package Name
* pkginfo -i
* pvs -d - Displays the dynamic version of the file.
AIX:
* Checking RAM: $ lsattr -El sys0 | grep realmem
* prtconf
* bootinfo -y ----> hardware is 64-bit or 32
* bootinfo -K ----> kernel is 64-bit or 32 ( to check 64 kernel is installed go to /usr/lib/boot and look for " unix_64 "
Windows :
set p | findstr /i archi
1) PROCESSOR_ARCHITECTURE=x86 ..... 32-bit
2) PROCESSOR_ARCHITECTURE=AMD64 ... 64-bit
HPUX:
to find what OS : getconf KERNEL_BITS
what varsion can run :getconf HW_CPU_SUPP_BITS
$ file /stand/vmunix
/stand/vmunix: PA-RISC1.1 executable ---> 32-bit
/stand/vmunix: ELF-64 executable object file ---> 64-bit
To check the Kernel Variables: kctune or kmtune
Debug Tools
Debug:
1. Run “ps –fu” and share the output
2. Run truss –far –vall –tall and share the output
3. Run jstack (http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstack.html) and share the output
a. jstack
4. Run pstack (http://docs.sun.com/app/docs/doc/816-0210/6m6nb7mih?a=view) and share the output
a. pstack
5. The jps utility may be useful as well (http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jps.html)
6. Modifying the call to run the jarfile so we can use dbx on the process may also be useful. (http://docs.sun.com/source/819-3683/Java_debug.html)
1. Run “ps –fu
2. Run truss –far –vall –tall
3. Run jstack (http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jstack.html) and share the output
a. jstack
4. Run pstack (http://docs.sun.com/app/docs/doc/816-0210/6m6nb7mih?a=view) and share the output
a. pstack
5. The jps utility may be useful as well (http://java.sun.com/j2se/1.5.0/docs/tooldocs/share/jps.html)
6. Modifying the call to run the jarfile so we can use dbx on the process may also be useful. (http://docs.sun.com/source/819-3683/Java_debug.html)
IIS 32bit to 64bit & Vice-Versa
IIS:
cscript iisweb.vbs /query
64 bit to 32 bit IIS:
ASP.NET 1.1, 32-bit version
To run the 32-bit version of ASP.NET 1.1, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Type the following command to enable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
Type the following command to install the version of ASP.NET 1.1 and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
Make sure that the status of ASP.NET version 1.1.4322 is set to Allowed in the Web service extension list in Internet Information Services Manager.
Back to the top
ASP.NET 2.0, 32-bit version
To run the 32-bit version of ASP.NET 2.0, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Type the following command to enable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
Type the following command to install the version of ASP.NET 2.0 (32-bit) and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
Make sure that the status of ASP.NET version 2.0.50727 (32-bit) is set to Allowed in the Web service extension list in Internet Information Services Manager.
Back to the top
ASP.NET 2.0, 64-bit version
To run the 64-bit version of ASP.NET 2.0, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Type the following command to disable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in Internet Information Services Manager.
Note The build version of ASP.NET 2.0 may differ depending on what the currently released build version is. These steps are for build version 2.0.50727.
cscript iisweb.vbs /query
64 bit to 32 bit IIS:
ASP.NET 1.1, 32-bit version
To run the 32-bit version of ASP.NET 1.1, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Type the following command to enable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
Type the following command to install the version of ASP.NET 1.1 and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe -i
Make sure that the status of ASP.NET version 1.1.4322 is set to Allowed in the Web service extension list in Internet Information Services Manager.
Back to the top
ASP.NET 2.0, 32-bit version
To run the 32-bit version of ASP.NET 2.0, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Type the following command to enable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
Type the following command to install the version of ASP.NET 2.0 (32-bit) and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -i
Make sure that the status of ASP.NET version 2.0.50727 (32-bit) is set to Allowed in the Web service extension list in Internet Information Services Manager.
Back to the top
ASP.NET 2.0, 64-bit version
To run the 64-bit version of ASP.NET 2.0, follow these steps:
Click Start, click Run, type cmd, and then click OK.
Type the following command to disable the 32-bit mode:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 0
Type the following command to install the version of ASP.NET 2.0 and to install the script maps at the IIS root and under:
%SYSTEMROOT%\Microsoft.NET\Framework64\v2.0.50727\aspnet_regiis.exe -i
Make sure that the status of ASP.NET version 2.0.50727 is set to Allowed in the Web service extension list in Internet Information Services Manager.
Note The build version of ASP.NET 2.0 may differ depending on what the currently released build version is. These steps are for build version 2.0.50727.
IPV6 Configuration
XP / 2003
###############
To install IPv6, run:
netsh interface ipv6 install
To find your IPv6 addresses when IPv4 is disabled, run:
netsh interface ipv6 show address
To ping a machine, run:
ping (e.g., ping 2001:db8:0:3eee::1)
To uninstall IPv6, run:
netsh interface ipv6 uninstall
To disable IPV4/ IPV6: Go to Network Connection properties and disable IPV6/ V4 Protocol Stack.
Vista / 2008
############
It's installed by default
Red Hat AS5:
###############
** It's installed by default
** To find your IPv6 addresses run one of:
ifconfig
ip addr ls
** To remove IPv6, add the following entries to /etc/modprobe.conf and then reboot:
alias net-pf-10 ipv6 off
alias net-pf-10 off
alias ipv6 off
** To create an IPv6-only with limited support for IPv4 (i.e., IPv6 solo) reboot your machine after modifying your interface configuration file (e.g., /etc/sysconfig/network-scripts/ifcfg-ethX) so it has the following entries
BOOTPROTO=none
IPV6INIT=yes
###############
To install IPv6, run:
netsh interface ipv6 install
To find your IPv6 addresses when IPv4 is disabled, run:
netsh interface ipv6 show address
To ping a machine, run:
ping (e.g., ping 2001:db8:0:3eee::1)
To uninstall IPv6, run:
netsh interface ipv6 uninstall
To disable IPV4/ IPV6: Go to Network Connection properties and disable IPV6/ V4 Protocol Stack.
Vista / 2008
############
It's installed by default
Red Hat AS5:
###############
** It's installed by default
** To find your IPv6 addresses run one of:
ifconfig
ip addr ls
** To remove IPv6, add the following entries to /etc/modprobe.conf and then reboot:
alias net-pf-10 ipv6 off
alias net-pf-10 off
alias ipv6 off
** To create an IPv6-only with limited support for IPv4 (i.e., IPv6 solo) reboot your machine after modifying your interface configuration file (e.g., /etc/sysconfig/network-scripts/ifcfg-ethX) so it has the following entries
BOOTPROTO=none
IPV6INIT=yes
Sunday, March 23, 2008
Solving VMware network problems on Linux
The VMware Configuration File
The updated configuration file with the extention vmx, contains a lot of information about the virtual machine that you have created, for instance information about your NIC (network) card, and is located in the same directory where your VMware machine files where created (for example C:\Virtual Machines\RHEL3U8_32).
The contents of my local (VMware Server version 1.1) vmx configuration file (C:\Virtual Machines\RHEL3U8_32\Red Hat Enterprise Linux 3.vmx) looks like: config.version = "8"virtualHW.version = "4"numvcpus = "2"scsi0.present = "TRUE"memsize = "1024"scsi0:0.present = "TRUE"scsi0:0.fileName = "RHES3_32_HD01-000002.vmdk"ide1:0.present = "TRUE"ide1:0.fileName = "auto detect"ide1:0.deviceType = "cdrom-raw"floppy0.present = "FALSE"Ethernet0.present = "TRUE"displayName = "RHEL3U8 - 11GR1B1"guestOS = "rhel3"priority.grabbed = "normal"priority.ungrabbed = "normal"
scsi0:1.present = "TRUE"scsi0:1.fileName = "RHES3_32_HD02-000002.vmdk"ide1:0.autodetect = "TRUE"
scsi0:0.redo = ""scsi0:1.redo = ""ethernet0.addressType = "generated"uuid.location = "56 4d d3 5d de 35 5f 1a-12 be 75 4f f9 c1 9e 66"uuid.bios = "56 4d d3 5d de 35 5f 1a-12 be 75 4f f9 c1 9e 66"ethernet0.generatedAddress = "00:0c:29:c1:9e:66"ethernet0.generatedAddressOffset = "0"
Ethernet0.connectionType = "nat"
ide1:0.startConnected = "FALSE"
checkpoint.vmState = ""checkpoint.vmState.readOnly = "FALSE"
It contains all necessary info needed for my VMware Server software to start-up and/or deal with this environment.
Updating the configuration file will also update the unique MAC address mentioned in this file. ethernet0.generatedAddress = "00:0c:29:c1:9e:66"ethernet0.generatedAddressOffset = "0"
Cloned and/or moved VMware machines will therefore have a different MAC addresses in the vmx configuration file and in the Linux VMware guest environment and network traffic is not possible anymore between host and guest environments. The following actions, SUSE and RedHat environments are used as an example, can be taken to straighten up these network problems.
The examples are based on the first Ethernet card in your system, referenced by eth0.If your system uses more Ethernet network cards, then replace the number 0 (of eth0) by the number that references your Ethernet card
RedHat
1) Take a note off the newly generated address, for example the shown value “00:0c:29:c1:9e:66”
2) Startup your virtual Linux machine.
3) Login on your Linux environment with the root account, via the VMware console, and open a terminal window.
4) In the directory /etc/sysconfig/network-scripts there will be a file for your (virtual) Ethernet card called ifcfg-eth0. This file contains your Linux MAC address.
5) Update the MAC address in the ifcfg-eth0 file with the same MAC address as shown in your VMware vmx-configuration file (eg. “00:0c:29:c1:9e:66”).
6) Activate your Ethernet card by executing the “ifup eth0” statement on the Linux command prompt (use ifdown eth0 to de-activate the Ethernet card).
SUSE
1) Take a note off the newly generated address, for example the shown value “00:0c:29:c1:9e:66”
2) Startup your virtual Linux machine.
3) Login on your Linux environment with the root account, via the VMware console, and open a terminal window.
4) In the directory /etc/sysconfig/network resides a file with a part of the MAC address in its name. vamisux00:/# /etc/sysconfig/network # ls -l if* ifcfg-eth-id-00:50:56:a0:17:d7
5) Rename this file to match the MAC address mentioned in your VMware configuration file.vamisux00:/# mv ifcfg-eth-id-00:50:56:a0:17:d7 ifcfg-eth-id-00:0c:29:c1:9e:66
6) Activate your Ethernet card by executing the “ifup eth0” statement on the Linux command prompt (use ifdown eth0 to de-activate the Ethernet card).
Check your status
A method to check if everything went well is to use the ifconfig statement. vamisux00:/# ifconfig –a
eth0 Link encap:Ethernet HWaddr 00:0c:29:c1:9e:66inet addr:10.10.10.10 Bcast:10.252.252.255 Mask:255.255.255.0UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:5962141 errors:0 dropped:0 overruns:0 frame:0TX packets:3686442 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:6098753239 (5816.2 Mb) TX bytes:876441853 (835.8 Mb)Base address:0xecc0 Memory:fe6e0000-fe700000
…etc
If everything went OK; it will be possible to ping the outside world from within your virtual machine.
HELP - MAC address not unique (on your network)!
A MAC address should be unique on a network (theoretically) and reflects in its values, amongst others, the manufacturer of the network card and a unique number for the card itself. That this isn’t always the case, is often proven on big LAN events or by spoofing a MAC address manually on your Wireless LAN card.
I was in situation already once regarding cloning a VMware machine. I still don’t know why, but VMware generated every time the same MAC address. Anyway, I found the solution via the VMware community.
A Linux tool called vmmacgen (the VMware MAC Generator) exists, with which you can generate a unique MAC address. This is a Linux binary executable and therefore must be run on a Linux operation system. The vmmacgen tool can be found on the http://www.vmguru.com/ website. It is described there as:
This is a small binary application written by Parag Mehta from VMware that randomly generates a valid MAC address that can be utilized by VMware ESX Server. The MAC addresses generated falls within the valid range of "Static" MAC Addresses that may be manually assigned in the virtual machine’s VMX file.
So I tried it also with VMware GSX and Server software, and it did the trick. The following is an example of its output. vamisux00:/# file vmmacgen vmmacgen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5,dynamically linked (uses shared libs), not stripped vamisux00:/# ./vmmacgen vmmacgen - 1.0Generated Static MAC address is : 00:50:56:9:BA:95
Add the above generated MAC address as following:Ethernet.addressType="static"Ethernet.address = "00:50:56:9:BA:95***** Remember to remove the following three lines *****Ethernet.generatedAddressEthernet.addressType = "vpx" or "generated"Ethernet.generatedAddressOffset
You will have to use these generated values in your VMware vmx configuration file.
An example of a vmx configuration file before the change ethernet0.present = "TRUE"ethernet0.networkName = ""ethernet0.addressType = "vpx"ethernet0.generatedAddress = "00:50:56:a0:17:d7"
An example of a vmx configuration file after the change ethernet0.present = "TRUE"ethernet0.networkName = ""ethernet0.addressType = "static"ethernet0.address = "00:50:56:9:BA:95"
So the following changes were made:
*) The ethernet0.addressType value has to be changed to static*) The ethernet0.generatedAddress parameter has to be changed to ethernet0.address*) The old MAC address has to be replaced with the generated MAC address
I hope I could be of help.
The updated configuration file with the extention vmx, contains a lot of information about the virtual machine that you have created, for instance information about your NIC (network) card, and is located in the same directory where your VMware machine files where created (for example C:\Virtual Machines\RHEL3U8_32).
The contents of my local (VMware Server version 1.1) vmx configuration file (C:\Virtual Machines\RHEL3U8_32\Red Hat Enterprise Linux 3.vmx) looks like: config.version = "8"virtualHW.version = "4"numvcpus = "2"scsi0.present = "TRUE"memsize = "1024"scsi0:0.present = "TRUE"scsi0:0.fileName = "RHES3_32_HD01-000002.vmdk"ide1:0.present = "TRUE"ide1:0.fileName = "auto detect"ide1:0.deviceType = "cdrom-raw"floppy0.present = "FALSE"Ethernet0.present = "TRUE"displayName = "RHEL3U8 - 11GR1B1"guestOS = "rhel3"priority.grabbed = "normal"priority.ungrabbed = "normal"
scsi0:1.present = "TRUE"scsi0:1.fileName = "RHES3_32_HD02-000002.vmdk"ide1:0.autodetect = "TRUE"
scsi0:0.redo = ""scsi0:1.redo = ""ethernet0.addressType = "generated"uuid.location = "56 4d d3 5d de 35 5f 1a-12 be 75 4f f9 c1 9e 66"uuid.bios = "56 4d d3 5d de 35 5f 1a-12 be 75 4f f9 c1 9e 66"ethernet0.generatedAddress = "00:0c:29:c1:9e:66"ethernet0.generatedAddressOffset = "0"
Ethernet0.connectionType = "nat"
ide1:0.startConnected = "FALSE"
checkpoint.vmState = ""checkpoint.vmState.readOnly = "FALSE"
It contains all necessary info needed for my VMware Server software to start-up and/or deal with this environment.
Updating the configuration file will also update the unique MAC address mentioned in this file. ethernet0.generatedAddress = "00:0c:29:c1:9e:66"ethernet0.generatedAddressOffset = "0"
Cloned and/or moved VMware machines will therefore have a different MAC addresses in the vmx configuration file and in the Linux VMware guest environment and network traffic is not possible anymore between host and guest environments. The following actions, SUSE and RedHat environments are used as an example, can be taken to straighten up these network problems.
The examples are based on the first Ethernet card in your system, referenced by eth0.If your system uses more Ethernet network cards, then replace the number 0 (of eth0) by the number that references your Ethernet card
RedHat
1) Take a note off the newly generated address, for example the shown value “00:0c:29:c1:9e:66”
2) Startup your virtual Linux machine.
3) Login on your Linux environment with the root account, via the VMware console, and open a terminal window.
4) In the directory /etc/sysconfig/network-scripts there will be a file for your (virtual) Ethernet card called ifcfg-eth0. This file contains your Linux MAC address.
5) Update the MAC address in the ifcfg-eth0 file with the same MAC address as shown in your VMware vmx-configuration file (eg. “00:0c:29:c1:9e:66”).
6) Activate your Ethernet card by executing the “ifup eth0” statement on the Linux command prompt (use ifdown eth0 to de-activate the Ethernet card).
SUSE
1) Take a note off the newly generated address, for example the shown value “00:0c:29:c1:9e:66”
2) Startup your virtual Linux machine.
3) Login on your Linux environment with the root account, via the VMware console, and open a terminal window.
4) In the directory /etc/sysconfig/network resides a file with a part of the MAC address in its name. vamisux00:/# /etc/sysconfig/network # ls -l if* ifcfg-eth-id-00:50:56:a0:17:d7
5) Rename this file to match the MAC address mentioned in your VMware configuration file.vamisux00:/# mv ifcfg-eth-id-00:50:56:a0:17:d7 ifcfg-eth-id-00:0c:29:c1:9e:66
6) Activate your Ethernet card by executing the “ifup eth0” statement on the Linux command prompt (use ifdown eth0 to de-activate the Ethernet card).
Check your status
A method to check if everything went well is to use the ifconfig statement. vamisux00:/# ifconfig –a
eth0 Link encap:Ethernet HWaddr 00:0c:29:c1:9e:66inet addr:10.10.10.10 Bcast:10.252.252.255 Mask:255.255.255.0UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1RX packets:5962141 errors:0 dropped:0 overruns:0 frame:0TX packets:3686442 errors:0 dropped:0 overruns:0 carrier:0collisions:0 txqueuelen:1000RX bytes:6098753239 (5816.2 Mb) TX bytes:876441853 (835.8 Mb)Base address:0xecc0 Memory:fe6e0000-fe700000
…etc
If everything went OK; it will be possible to ping the outside world from within your virtual machine.
HELP - MAC address not unique (on your network)!
A MAC address should be unique on a network (theoretically) and reflects in its values, amongst others, the manufacturer of the network card and a unique number for the card itself. That this isn’t always the case, is often proven on big LAN events or by spoofing a MAC address manually on your Wireless LAN card.
I was in situation already once regarding cloning a VMware machine. I still don’t know why, but VMware generated every time the same MAC address. Anyway, I found the solution via the VMware community.
A Linux tool called vmmacgen (the VMware MAC Generator) exists, with which you can generate a unique MAC address. This is a Linux binary executable and therefore must be run on a Linux operation system. The vmmacgen tool can be found on the http://www.vmguru.com/ website. It is described there as:
This is a small binary application written by Parag Mehta from VMware that randomly generates a valid MAC address that can be utilized by VMware ESX Server. The MAC addresses generated falls within the valid range of "Static" MAC Addresses that may be manually assigned in the virtual machine’s VMX file.
So I tried it also with VMware GSX and Server software, and it did the trick. The following is an example of its output. vamisux00:/# file vmmacgen vmmacgen: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), for GNU/Linux 2.2.5,dynamically linked (uses shared libs), not stripped vamisux00:/# ./vmmacgen vmmacgen - 1.0Generated Static MAC address is : 00:50:56:9:BA:95
Add the above generated MAC address as following:Ethernet
You will have to use these generated values in your VMware vmx configuration file.
An example of a vmx configuration file before the change ethernet0.present = "TRUE"ethernet0.networkName = ""ethernet0.addressType = "vpx"ethernet0.generatedAddress = "00:50:56:a0:17:d7"
An example of a vmx configuration file after the change ethernet0.present = "TRUE"ethernet0.networkName = ""ethernet0.addressType = "static"ethernet0.address = "00:50:56:9:BA:95"
So the following changes were made:
*) The ethernet0.addressType value has to be changed to static*) The ethernet0.generatedAddress parameter has to be changed to ethernet0.address*) The old MAC address has to be replaced with the generated MAC address
I hope I could be of help.
Friday, August 17, 2007
How to Check Patch levels on UNIX?
To check patch level on different platforms.
AIX : oslevel –r
Linux : rpm –qa
HPUX : swlist
Solaris : showrev-p
Basic UNIX Commands:
To check patch level on different platforms.
AIX : oslevel –r
Linux : rpm –qa
HPUX : swlist
Solaris : showrev-p
Basic UNIX Commands:
- find . –name "filename " –depth –print ( Find a File )
- zip –r filename.zip ( Unzip a File)
- mount -t smbfs/nfs -o username=nsd,password=nsdbuild //172.25.70.48/builds /net ( Mount a Folder)
- Cpio -ivdm <>
- gunzip -d filename.gz ( Decompress)
Subscribe to:
Posts (Atom)
-
My quick reference list of questions for Driving License Theory Test Distances: Parking 5meter Before Pedestrian Crossing / Junc...
-
The concept of T-shirt sizes for SAP HANA SAP defined so-called T-shirt sizes for SAP HANA to both simplify the sizing and to limit...
-
Both the row and column storage engine each have a built-in query capability optimized for the respective storage method. Consequently e...