location version uptime last reboot reason
loc 1 3.9b22 1 day, 21 hours extended power outtage
loc 2 3.9b22 48 days, 23 hours software upgrade
loc 3 3.9b22 53 days, 10 hours software upgrade
loc 4 3.9b22 8 days, 13 hours maintenance
loc 4 3.9b22 32 days, 10 hours maintenance
loc 5 3.9b24 1 day, 22 hours ???
loc 5 3.9b24 1 day, 20 hours ???
loc 5 3.9b24 1 day, 3 hours ???
loc 6 3.9b22 30 days, 8 hours extended power outtage
loc 7 3.9b22 53 days, 10 hours software upgrade
loc 8 3.9b22 8 days, 3 hours extended power outtage
The ones marked ??? in location 5 are the ones I am concerned about. Each
of those PM3's has rebooted multiple times, sometimes within minutes of
the last reboot. They were working perfectly fine until about a week ago.
The location does not have any power problems, the boxes are on UPS', etc.
BTW, all three had uptimes of approximately 30 days (when we rebooted them
for maintenance reasons) until this problem.
I've got consoles hooked up on all three now and am just waiting until
it reboots again.
Tim
On Thu, Dec 02, 1999 at 01:26:14PM -0600, Donald E. Zelenak Jr. wrote:
> One Location:
> Lucent PortMaster PM-3 ComOS 3.9b22
> System uptime is 51 days 3 hours 21 minutes
>
> Another Location:
> Lucent PortMaster PM-3 ComOS 3.9b22
> System uptime is 50 days 23 hours 46 minutes
>
> This release is actually one of the first we dont have to reboot every 15
> days.. The first PM3 is probably 75% of the time full (48Mod 2 CT1 AMI/D4)
> and the second isn't always full, but its always in use (24 Mod 1 CT1
> AMI/D4)
>
>
> Don
> UDNet
>
> ----- Original Message -----
> From: "Tim Tsai" <tim@futuresouth.com>
> To: <portmaster-users@livingston.com>
> Sent: Tuesday, November 30, 1999 10:29 PM
> Subject: (PM) PM3 spontaneous reboots
>
>
> > Is anybody else seeing spontaneous reboots with 3.9b22 and/or 3.9b24?
> >
> > We have a group of 3 PM3's that's been rebooting randomly (generally will
> > run for a few hours). I have the console connected in two of them and of
> > course the last one that rebooted was the unconnected one.
> >
> > I am only seeing this in one location. 7 other PM3's in other locations
> > (some in groups) and they've been working fine.
> >
> > <1% ethernet collision (each PM3 is connected directly to a Cisco switch)
> > so I don't think that's the problem.
> >
> > It does appear that only fully loaded PM3's do this. I've moved the lines
> > around to trace this down and I don't recall any box with only one PRI
> > has rebooted.
> >
> > Dial-up only PM3's running OSPF and SNMP.
> >
> > Thanks,
> >
> > Tim
> > -
> > To unsubscribe, email 'majordomo@livingston.com' with
> > 'unsubscribe portmaster-users' in the body of the message.
> > Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>
-
To unsubscribe, email 'majordomo@livingston.com' with
'unsubscribe portmaster-users' in the body of the message.
Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>