One possibility is that the new 3550 is plugged into the same electrical outlet as the original server and that the NS is more sensitive to power issues that the 3550. I ran into this one time when the power button on the back of the PC was set to 230 instead of 115 and it made it re-boot any time something happened to the power outlet such as turning something on or off. It was running OK until something new was plugged into the power outlet.
""Keith Woodworth"" wrote in message news:[EMAIL PROTECTED] > Replaced an old foundry serveriron switch with a 3550 over the weekend. > Our primary NS (old BSD/OS 3.1 all patches) was plugged into the > serveriron and had well over 200 days uptime. NS was moved to the 3550, > all that changed was moving the cable from the old switch to the new 3550. > > Made the changes on the server to reflect new GW and away it went. > Well damned if the nameserver rebooted at 8:30am the next morning (sunday) > So this morning I sit down with my morning coffee and looking over mail I > see the nameserver rebooted again at 8:55am this morning. > > Only thing that changed as the Default route on the server and moving the > ethernet cable from old to new switch and that was all. > > Ports auto'd to 100/full on the 3550. We will hard set the ports today but > it is sorta odd that a server running fine for over 200 days on one switch > then moving it to a new switch suddenly decides to reboot two days in a > row at roughly the same time. Switch is fine, it did not reboot, nor did > anything else plugged into it. > > Anyone else seen anything like this? > > Thanks, > Keith Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=70539&t=70412 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
