Table of Contents
Advertisement
Ping the IP address of network device
located on a remote network - ping <IP
address>
Successfully pinging the IP address of the remote host
verifies that the local client can communicate with the
remote host through a router. if the remote host is located
across a high delay link, try using the -w (wait) parameter
to specify a longer time out period than the default time out
of four seconds.
If you cannot successfully ping the remote host IP address
after successfully pinging the default gateway, this
indicates that there is no respond from the remote host, or
if there is any network hardware problem between the
source host and the destination host. To rule out the
possibility of a problem in the work hardware, ping to a
different remote host on the same subnet where the first
remote host is located.
Ping the host name of another host on a
remote network - ping <host name>
Successfully pinging the name of the remote host verifies
that ping can resolve the remote host name to an IP
address. If you cannot successfully ping the remote host
name after successfully pinging the IP address of the
remote host, the problem is with host name resolution, but
not with network connectivity. When pinging the host
name of the target host, ping attempts to resolve the name
to an address (first through a DNS server, and next through
a WINS server, if one is configured), and then attempts a
local broadcast. Check TCP/IP properties to see whether
the client has DNS server and WINS server addresses
configured, either typed manually or assigned
automatically. If DNS and WINS server addresses are
configured in TCP/IP properties, and if they appear when
you type ipconfig/all, then try pinging with server
addresses to ascertain whether they are accessible.
On a network that uses DNS for name resolution, if the
name entered is not a Fully Qualified Domain Name
(FQDN), the DNS name resolver appends the computer's
domain name or name to generate the FQDN. Name
resolution might fail if you do not use an FQDN for a
remote name. These requests fail because the DNS name
resolver appends the local domain suffix to a name that
resides elsewhere in the domain hierarchy.
How to upgrade the software version
The HDXchange software may be upgraded by selecting
Upgrade on the System > Configuration page of the
Administration web pages.
See HDXC-C030 HDXC-B030 HDXC-X030 HDXC-L030
Installation Manual for details of the Administration web
pages.
The upgrade is achieved by transferring a set of RPM
(Red-hat Package Manager) software packages from a
supplied DVD.
The upgraded software files are normally stored at:
/Upgrade_rpms/[date]/[filename]
A list of the files that have been transferred and details of
the transfer process are stored in two files labelled:
rpmlist.txt and rpmlist.log
How to re-install the software
The HDXchange software is pre-loaded onto the server at
the factory and cannot be re-installed as a 'clean install'.
A system of creating 'checkpoints' is provided by the
System > Checkpoints page of the Administration web
pages, however, to store a backup copy of the current
operating system configuration on the server.
Alternatively, it may be burned onto a DVD.
If the operating system has to be 're-installed', restore the
system to a known-good checkpoint.
See HDXC-C030 HDXC-B030 HDXC-X030 HDXC-L030
Installation Manual for details of the Administration web
pages.
Note
• A checkpoint stores the operating system configuration
settings of the OS RAID, NOT data on the Media RAID.
A new checkpoint should be made following significant
events on the server such as changes to users and groups,
or after a software upgrade, or before replacing an OS hard
disk drive; so that a previous system configuration can be
restored in the event of a problem.
47
Basic operations
Advertisement
Table of Contents
