Are the hosts listed in your filer's /etc/hosts.equiv file and/or /etc/trusted.hosts file fully qualified? You might be experiencing a host name lookup failure. You could try just specifying IP addresses for the admin hosts as a temporary fix.
Paul Caron wrote:
Are the hosts listed in your filer's /etc/hosts.equiv file and/or /etc/trusted.hosts file fully qualified? You might be experiencing a host name lookup failure. You could try just specifying IP addresses for the admin hosts as a temporary fix.
The solution was found by Jeff Kennedy jlkennedy@amcc.com
that advised me at 6.2xx the "quota on" command has to be removed from /etc/rc file as the quota statement is now written in registry.
Effectively after removing "quota on" from /etc/rc file the filer reboot well and I was able to access it from the console and from a telnet/rsh session.
Maybe some Netapp guy should explain why this happen ?
Regards
Fran
f.bonnet@esiee.fr (Frank Bonnet) writes:
The solution was found by Jeff Kennedy jlkennedy@amcc.com
that advised me at 6.2xx the "quota on" command has to be removed from /etc/rc file as the quota statement is now written in registry.
Effectively after removing "quota on" from /etc/rc file the filer reboot well and I was able to access it from the console and from a telnet/rsh session.
I'm a bit mystified by one aspect of this: when has it *ever* been necessary to have "quota on" in /etc/rc ? As far back as I can recall (even before there were multiple volumes, and long before there was a "registry") the quota-on setting was part of the filing system state and survived reboots just fine.
Chris Thompson Email: cet1@cam.ac.uk
-
Chris Thompson -
Frank Bonnet -
Paul Caron