HP BL680c XenServer Administrator's Guide 4.1.0 - Page 106

Troubleshooting connections between XenCenter and, the XenServer Host, 3. Special debug boot

Page 106 highlights

Troubleshooting and aggregate them correctly. The syslogd daemon is a standard part of all flavors of Linux and Unix, and third-party versions are available for Windows and other operating systems. Procedure 6.1. To write logs to a remote server 1. Set the syslog_destination parameter to the hostname or IP address of the remote server where you want the logs to be written: xe host-param-set uuid= logging:syslog_destination= 2. Issue the command xe host-syslog-reconfigure uuid= to enforce to change. (You can also execute this command remotely by specifying the host parameter.) 6.2. Troubleshooting connections between XenCenter and the XenServer Host If you have trouble connecting to the XenServer Host with XenCenter, check the following: • Is your XenCenter an older version than the XenServer Host you are attempting to connect to? The XenCenter application is backward-compatible and can communicate properly with older XenServer Hosts, but an older XenCenter cannot communicate properly with newer XenServer Hosts. To correct this issue, install a XenCenter version that is the same, or newer, than the XenServer Host version. • Is your license current? You can see the expiration date for your License Key in the XenServer Host Overview tab under the Licenses section. Also, if you upgraded your software from version 3.2.0 to the current version, you should also have received and applied a new License file. • The XenServer Host talks to XenCenter via HTTPS over port 443 (a two-way connection for commands and responses using the XenAPI), and 5900 for graphical VNC connections with paravirtual Linux VMs. If you have a firewall enabled between the XenServer Host and the machine running the client software, make sure that it allows traffic from these ports. 6.3. Special debug boot options Safe mode and serial mode are special boot options that are made available for debugging boot problems. They should not be used in normal operation, but only under explicit instruction from the appropriate Support organization. Both debug options require use of a serial console. 100

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108

Troubleshooting
100
and aggregate them correctly. The syslogd daemon is a standard part of all flavors of Linux and Unix, and
third-party versions are available for Windows and other operating systems.
Procedure 6.1. To write logs to a remote server
1.
Set the syslog_destination parameter to the hostname or IP address of the remote server where you
want the logs to be written:
xe host-param-set uuid=<XenServer Host UUID> logging:syslog_destination=<hostname>
2.
Issue the command
xe host-syslog-reconfigure uuid=<XenServer Host UUID>
to enforce to change. (You can also execute this command remotely by specifying the
host
parameter.)
6.2. Troubleshooting connections between XenCenter and
the XenServer Host
If you have trouble connecting to the XenServer Host with XenCenter, check the following:
Is your XenCenter an older version than the XenServer Host you are attempting to connect to?
The XenCenter application is backward-compatible and can communicate properly with older XenServer
Hosts, but an older XenCenter cannot communicate properly with newer XenServer Hosts.
To correct this issue, install a XenCenter version that is the same, or newer, than the XenServer Host
version.
Is your license current?
You can see the expiration date for your License Key in the XenServer Host Overview tab under the
Licenses section.
Also, if you upgraded your software from version 3.2.0 to the current version, you should also have re-
ceived and applied a new License file.
The XenServer Host talks to XenCenter via HTTPS over port 443 (a two-way connection for commands
and responses using the XenAPI), and 5900 for graphical VNC connections with paravirtual Linux VMs.
If you have a firewall enabled between the XenServer Host and the machine running the client software,
make sure that it allows traffic from these ports.
6.3. Special debug boot options
Safe mode and serial mode are special boot options that are made available for debugging boot problems.
They should not be used in normal operation, but only under explicit instruction from the appropriate Support
organization. Both debug options require use of a serial console.