Changing the IP address, default gateway, and hostname of the Service Console in ESX


  1. Run the following command to set the IP address:
    [root@server root]# esxcfg-vswif -i <a.b.c.d> -n <w.x.y.z> vswif0 , where <a.b.c.d> is the IP address and <w.x.y.z> is the subnet mask.

    Note: In this example,     v
    swif0 is the Service Console adapter that is the interface to which you are applying the IP address change.
  2. Open the /etc/hosts file with a text editor and modify it so that it reflects the correct IP address and hostname.
  3. To change the default gateway address and the hostname, edit the /etc/sysconfig/network file and change the GATEWAY and HOSTNAME parameters to the proper values.
  4. For the changes to take place, reboot the host or restart the network service with the command:
    [root@server root]# service network restart


    Note: This command breaks any current network connections to the Service Console. 

Comments

Post a Comment

Popular posts from this blog

AD LDS – Syncronizing AD LDS with Active Directory

Image
First, we will install the AD LDS Instance: 1. Create and AD LDS instance by clicking Start -> Administrative Tools -> Active Directory Lightweight Directory Services Setup Wizard. The Setup Wizard appears. 2. Click Next . The Setup Options dialog box appears. For the sake of this guide, a unique instance will be the primary focus. I will have a separate post regarding AD LDS replication at some point in the near future. 3. Select A unique instance . 4. Click Next and the Instance Name dialog box appears. The instance name will help you identify and differentiate it from other instances that you may have installed on the same end point. The instance name will be listed in the data directory for the instance as well as in the Add or Remove Programs snap-in. 5. Enter a unique instance name, for example IDG. 6. Click Next to display the Ports configuration dialog box. 7. Leave ports at their default values unless you have conflicts with the default values. 8. Click N
Read more

How to increase the log retention in Orchestrator Server ( server.log)

When you are debugging the Orchestrator related issues in mid/large deployments , it is expected that the server.log file rotates rapidly.  In this case we need to increase the log file size and the rotation interval. Below are the steps to make changes to the config file to capture large number of files for troubleshooting.  Config File Location :  Appliance deployment:  /etc/vco/app-server/log4j.xml Windows deployment:  <install_Location>\app-server\conf\log4j.xml Steps:  1. Edit the file  log4j.xml 2. Locate the  <appender class="org.apache.log4j.RollingFileAppender" name="FILE">  section 3. Increase the size of the log file to 10 MB   <param name="MaxFileSize" value="10240KB"/>    4. Increase the  number files to be retained before rotation  <param name="MaxBackupIndex" value="5"/> Cheers :-) 
Read more

DNS Scavenging.

                        DNS Scavenging is a great answer to a problem that has been nagging everyone since RFC 2136 came out way back in 1997.  Despite many clever methods of ensuring that clients and DHCP servers that perform dynamic updates clean up after themselves sometimes DNS can get messy.  Remember that old test server that you built two years ago that caught fire before it could be used?  Probably not.  DNS still remembers it though.  There are two big issues with DNS scavenging that seem to come up a lot: "I'm hitting this 'scavenge now' button like a snare drum and nothing is happening.  Why?" or "I woke up this morning, my DNS zones are nearly empty and Active Directory is sitting in a corner rocking back and forth crying.  What happened?" This post should help us figure out when the first issue will happen and completely avoid the second.  We'll go through how scavenging is setup then I'll give you my best practices.  Scavenging s
Read more