you can reboot the control station, it does not affect datamover connectivity.

As "dynamox" suggested, you may reboot the control station and try. If that does not help, you may need to open a service call.

My 2 cents
Sandip

I finally got around to digging into this a little deeper. Rebooting the control station did not resolve my issue. In fact, after power cycling, the management interface went completely offline. I connected via HyperTerm and was presented with a prompt stating "Enter Root Password to access maintenance mode" (or something to that effect) or press Ctrl+D to continue. I opted for Ctrl+D and the control station performed an automatic reboot.

Upon boot up, the normal post messages began flying by, until I saw this:

Your system appears to have shut down uncleanly
Press Y within 1 seconds to force file system integrity check...
Checking root filesystem
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/hda3
/ contains a file system with errors, check forced.
Error reading block 164039 (Attempt to read block from filesystem resulted in sh
ort read) while doing inode scan.

/: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
        (i.e., without -a or -p options)
[FAILED]

*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):

At this point I decided to open a service call. Much to my dismay, I was quickly informed that our maintenance contract for this unit has been expired for quite some time. I'm working with my team to decide whether we want to purchase extended maintenance or just pay for this particular support incident. In the meantime, I was wondering if there were any non-destructive procedures I can try to get the control station back online?