Archive for September 6, 2012

iDRAC or DRAC 6 Login problems

Posted: September 6, 2012 in DRAC
Tags: , ,

Have found out most of the times people have issues to login to the iDRAC or the DRAC 6 web console even if they are able to ping the IP Address.

They try to check if the cable is inserted fine or they think the iDRAC has issues.

If you are able to reach the DRAC IP but not able to login to the DRAC using the web console with “root” login then try the below steps,

  1. In the iDRAC menu go to “LAN User Configuration” as below:

  1. Then Go to “Account Access”.
  2. Select Enabled to enable the administrator account.
  3. When you have finished making changes to the iDRAC configuration, press the <Esc> key to display the Exit menu.
  4. Select Save Changes and Exit and press <Enter> to retain your changes.
  5. You should be able to login to the iDRAC using the Web Console.

 

By using replication monitor 

Go to start > run > type repadmin

Go to start > run > type replmon

The Replmon graphical user interface (GUI) tool is included when you install Windows Server 2003 Support Tools from the product CD or from the Microsoft Download Center

Replmon.exe: Active Directory Replication Monitor

This GUI tool enables administrators to view the low-level status of Active Directory replication, force synchronization between domain controllers, view the topology in a graphical format, and monitor the status and performance of domain controller replication.

The Replmon graphical user interface tool was removed from Windows Server 2008 and later. Repadmin is still available for troubleshooting replication.

Repadmin.exe: Replication Diagnostics Tool

This command-line tool assists administrators in diagnosing replication problems between Windows domain controllers.

Administrators can use Repadmin to view the replication topology as seen from the perspective of each domain controller. In addition, Repadmin can be used to manually create the replication topology, to force replication events between domain controllers, and to view both the replication metadata and up-to-date vectors.

Repadmin.exe can also be used for monitoring the relative health of an Active Directory forest. The operations replsummaryshowreplshowrepl /csv, and showvector /latency can be used to check for replication problems.

 

Symptoms:

–          Not be able to connect to the ESX host through vSphere Client.

–          The vSphere client gives out error message as “Connection Timed Out”

–          You may not be able to Start or Stop the Virtual Machine.

–          The ESX may show as Disconnected from the Central Virtual Server.

Resolution:

Rather than proceeding to restart the ESX host, you can proceed to restart the Management Agents on the ESX host.

(Note: Restarting the Management Tasks may impact any tasks running on that particular ESX)

–          Log into your ESX host using the “Root” Credentials through the SSH Session, you can better use the “Putty” Software to connect to the ESX    host.

–          Feed the IP address of the ESX Host.

–          Then Click on “Open” in the end of Tab.

–          Once get the Console window, Login with Root Credentials

–          Run the below command to restart the Management Agent on the ESX Host:

–          Now you should be able to connect to the ESX host through the vSphere client.

 

Caution: Ensure Automatic Startup /Shutdown of VM is disabled before running the above command.