HDD Space full check symantec logs

If your hdd space is full but your windows using less space.
then check the below path if you are using symantec some logs will be created of 12gb like below.













Delete the logs which is in green and check the path in the taskbar.

To restart the management agents on ESX host

To restart the management agents on ESX host:

1.Log in to your ESX Server as root from either an SSH session or directly from the console of the server.
2.Type service mgmt-vmware restart.

Caution: Ensure Automatic Startup/Shutdown of virtual machines is disabled before running this command or you risk rebooting the virtual machines. For more information, see Restarting hostd (mgmt-vmware) on ESX Server Hosts Restarts Hosted Virtual Machines Where Virtual Machine Startup/Shutdown is Enabled (1003312) and Determining whether virtual machines are configured to autostart (1000163).
3.Press Enter.
4.Type service vmware-vpxa restart.
5.Press Enter.
6.Type logout and press Enter to disconnect from the ESX host.

If this process is successful, it appears as:

[root@server]# service mgmt-vmware restart
Stopping VMware ESX Server Management services:
VMware ESX Server Host Agent Watchdog [ OK ]
VMware ESX Server Host Agent [ OK ]
Starting VMware ESX Server Management services:
VMware ESX Server Host Agent (background) [ OK ]
Availability report startup (background) [ OK ]
[root@server]# service vmware-vpxa restart
Stopping vmware-vpxa: [ OK ]
Starting vmware-vpxa: [ OK ]
[root@server]#

Changing the IP for the Service Console (ESX)

Changing settings f rom the physical or remote console connection
Changing the IP for the Service Console must be done from the physical console or through a remote console session. If you make changes through a network connection such as SSH, network connectivity to the Service Console disconnects because the Service Console's network interface changes.

1. Run the following command to set the IP address:

[root@server root]# esxcfg-vswif -i -n vswif0 , where is the IP address and 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.

Changing the hostname without rebooting
To dynamically change the hostname, run the command:

[root@server root]# hostname newname

Note: This command creates a temporary hostname change. This change is lost when the system is rebooted.

Changing the DNS server settings

To change the DNS server settings, update the nameserver IPs and search domain the /etc/resolv.conf file.

Changing settings in VMware vSphere or Infrastructure Client

To change the hostname, domain, DNS servers, and default gateway in VMware vSphere or Infrastructure (VI) Client:

1.Highlight the ESX host and click the Configuration tab.
2.Click DNS and Routing.
3.Click Properties.
4.To change the hostname, domain, and DNS servers, click the DNS Configuration tab and enter the appropriate values.

Note: Disable VMware High Availability if you do not want virtual machines to failover during the hostname IP change.

5.To change the default gateway, click the Routing tab and enter the appropriate value.
6.Update the etc/opt/vmware/vpxa/vpxa.cfg file to reflect the new settings.
7.Reboot the ESX host for the changes to take place .

SSH sessions to the ESX Service Console

Note: Each SSH connection to an ESX host uses additional Service Console resources. Use caution when using scripts or third party software that create multiple SSH sessions to the ESX Service Console. Excessive use of SSH on an ESX machine may cause the service console to exhibit symptoms of memory exhaustion.

To enable root login for SSH and SCP clients:

1.If you have physical access to the ESX host, login to the console of your ESX host as the root user .

If you can only connect to the ESX host over the network, connect using an SSH client (such as PuTTY) and log in as a user other than root. After you are logged in, switch to the root user with the following command:

su -
Note: If you do not have any other users on the ESX host, you can create a new user by connecting directly to the ESX host with VMware Infrastructure (VI) or vSphere Client. Go to the Users & Groups tab, right-click on the Users list and select Add to open the Add New User dialog. Ensure the Grant shell access to this user option is selected. These options are only available when connecting to the ESX host directly. They are not available if connecting to vCenter Server.

2.Edit the configuration file for SSH with the following command:

nano /etc/ssh/sshd_config

3.Find the line that starts with PermitRootLogin and change the no to yes. You can find this line about 2 pages down from the top. Save the file by first pressing Ctrl-O and then Enter. Exit with Ctrl-X.

4.Restart the sshd service with the command:

service sshd restart

Note: Alternatively, use the command:

/etc/init.d/sshd restart