SEO

I jumpstarted my 280R using the hme0 interface and changed the /etc/
hostname.er0 file to /etc/hostname.ge0 to reference the fiber
interface, but there is a delay between the time the ge0 interface
responds to it's IP address via ping causing svc.startd errors. The
hme0 interface has no such delay.

Here are the ge0 errors:

Rebooting with command: boot
Boot device: /pci@8,600000/SUNW,qlc@4/fp@0,0/disk@w21000004cf780e2a,
0:a File and args:
SunOS Release 5.10 Version Generic_127111-05 64-bit
Copyright 1983-2007 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
SUNW,pci-gem0: Using Gigabit SERDES Interface
SUNW,pci-gem0: Auto-Negotiated 1000 Mbps Full-Duplex Link Up
Hostname: onyx
NIS+ domain name is ics.hrl.com
/dev/md/rdsk/d50 is clean

onyx console login: Feb 14 11:45:20 inetd[289]: authdes_refresh:
unable to synchronize clock

*ge0 interface responds to ping at this point*

Feb 14 11:45:22 /usr/lib/snmp/snmpdx: authdes_refresh: unable to
synchronize clock
Feb 14 11:45:52 svc.startd[7]: svc:/system/mdmonitor:default: Method
or service exit timed out. Killing contract 21.
Feb 14 11:45:52 svc.startd[7]: svc:/system/mdmonitor:default: Method "/
lib/svc/method/svc-mdmonitor" failed due to signal KILL.
Feb 14 11:46:05 svc.startd[7]: svc:/application/management/
wbem:default: Method or service exit timed out. Killing contract 46.
Feb 14 11:46:05 svc.startd[7]: svc:/application/management/
wbem:default: Method "/lib/svc/method/svc-wbem start" failed due to
signal KILL.
Feb 14 11:46:08 svc.startd[7]: svc:/application/management/
dmi:default: Method or service exit timed out. Killing contract 62.
Feb 14 11:46:08 svc.startd[7]: application/management/dmi:default<br