Previous  - Volume Troubleshooting Next  - Icons

General Troubleshooting

General troubleshooting includes:

Client/Server Problems

User is not authorized to connect to the server.

This error can occur for the following reasons:

  • The user name is incorrect.
  • The password is incorrect.
  • The user does not have an account on the machine.
  • The password and group files or NIS tables do not contain entries for the user.
  • The user is not listed in the vrtsadm group entry.
       Enter the user name and password again. If the same error appears, ask the administrator of the machine to make sure that your user name is included in the vrtsadm group entry and your user name and password are entered correctly in the appropriate password and group files or NIS tables.

There is no such server.

The specified host machine does not exist or is not in the Domain Name System (DNS).

       Check the machine name and enter the machine name again.

Unable to connect to the server.

The VEA system may not be running on the machine to be administered.

       Make sure the server is running and the client and server are properly configured. If necessary, restart the VEA system.

Possible client/server versions mismatch.

The VEA client and server versions may be incompatible.

       Check the client and server versions using the following commands:
        # vea -V
        # vxsvc -V
    If necessary, upgrade the client or server.

Server connection lost.

The VEA service has been stopped.

       Restart the server.

The server seems to have multiple addresses.

The server (host) may be known by multiple addresses.

       Try to specify one of the server IP addresses as the server host name.

Configuration Changes

VxVM is dynamic, so it automatically displays new objects or changes to existing objects on the system. These changes or additions are usually reflected in VEA immediately (or within a short time).

If you add objects (such as new disks) to the system and VxVM does not display these objects within a short time, you can force VxVM to check for new objects in one of the following ways:

  1. Scan the disks on the system (Rescan Disks) to make sure that VxVM recognizes any newly attached hardware.
  2. Update the system configuration database.

Previous  - Volume Troubleshooting Next  - Icons