I have a server that seems to take a long time to actually be available on the network (serving its home web page). It seems to take an hour or so before I can get to the UI.
This one is new (refurbished), and I've only actually booted it twice so far (once a week ago to replicate content to it, and again when replication finished to relocate it into its permanent home where the old one was), but I had the same problem with the one it's replacing.
When I had the problem originally with the old server, I called Kaleidescape. Their suggestions were to use the serial console to configure a static address, which I'm using, and to try a different network cable, which also didn't seem to make any difference. I had to get off the phone, and by the time I got back to look at it the next day, it was working okay, and I don't ever reboot it, so I haven't pursued it.
The new server, the one that's slow today, was powered down cleanly (using the front panel button), and I can see from the console boot log that it's up--this is the snippet at the end of the log, from about 3:05pm:
I had link and activity lights on the back of the server, the switchport shows up and connected, and shows some traffic, but not much:
It finally started answering IP scans at 16:23, and seems to be working okay now.
Just wondered if anyone else had seen this sort of behavior.
Thanks!
This one is new (refurbished), and I've only actually booted it twice so far (once a week ago to replicate content to it, and again when replication finished to relocate it into its permanent home where the old one was), but I had the same problem with the one it's replacing.
When I had the problem originally with the old server, I called Kaleidescape. Their suggestions were to use the serial console to configure a static address, which I'm using, and to try a different network cable, which also didn't seem to make any difference. I had to get off the phone, and by the time I got back to look at it the next day, it was working okay, and I don't ever reboot it, so I haven't pursued it.
The new server, the one that's slow today, was powered down cleanly (using the front panel button), and I can see from the console boot log that it's up--this is the snippet at the end of the log, from about 3:05pm:
Product id: 3U Server (0x0102)
Video Server started. Version: 5.3.1-13010
Serial number: 000000xxxxxx
Video Server boot flash version: 9
HTTP Proxy Server:
IP Address : 10.0.0.75
Subnet Mask : 255.255.255.0
Broadcast Address: 10.0.0.255
Default Gateway : 10.0.0.254
DNS Server #1 : 10.0.0.1
DNS Server #2 : 10.0.0.2
Fan speeds (0,0,0) RPM
Video Server started. Version: 5.3.1-13010
Serial number: 000000xxxxxx
Video Server boot flash version: 9
HTTP Proxy Server:
IP Address : 10.0.0.75
Subnet Mask : 255.255.255.0
Broadcast Address: 10.0.0.255
Default Gateway : 10.0.0.254
DNS Server #1 : 10.0.0.1
DNS Server #2 : 10.0.0.2
Fan speeds (0,0,0) RPM
I had link and activity lights on the back of the server, the switchport shows up and connected, and shows some traffic, but not much:
GigabitEthernet2/48 is up, line protocol is up (connected)
Full-duplex, 1000Mb/s, link type is auto, media type is 10/100/1000-TX
5 minute input rate 2000 bits/sec, 1 packets/sec
5 minute output rate 2000 bits/sec, 1 packets/sec
Full-duplex, 1000Mb/s, link type is auto, media type is 10/100/1000-TX
5 minute input rate 2000 bits/sec, 1 packets/sec
5 minute output rate 2000 bits/sec, 1 packets/sec
It finally started answering IP scans at 16:23, and seems to be working okay now.
Just wondered if anyone else had seen this sort of behavior.
Thanks!