(PM) The Reboot of the PM3's, Too many collisions?

David Fisher (dave@fidalgo.net)
Mon, 20 Jul 1998 09:28:32 -0700

This is a multi-part message in MIME format.

------=_NextPart_000_003A_01BDB3C0.C3126FA0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Here is the show netstat and version of each of my four portmaster
3's. I am wondering if anyone else is having a lot of collisions on =
their
network, or is the PM3's reporting a lot of network collisions.

If you will notice I have also listed my USR Total Control Rack, which
has been up more then 100 days and with NO collisions.

I am wondering if this has been causing the reboot of the PM3's? The
only one that has not rebooted since I installed ComOS v3.8b17, which
by the way has been the most stable ComOS yet, was the fourth and
last PM3.

The previous ComOS v3.8b15 rebooted a lot more often. Now the 1st,
2nd, and 3rd PM3's only rebooted once so far. But I am wondering if
Lucent/Livingston has set a hard reboot option when you reach so many
collisions. Also, why does my USR have no collisions and the PM3 has
lots? They are all only the same network, same Ethernet, with the same
3Com SuperStack II Hub.

pm3-1> sh netstat
Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
ether0 36516076 61 36434744 159 2625754 942 0
pm3-1> version
Livingston PortMaster PM-3 ComOS 3.8b17
System uptime is 10 days 2 hours 16 minutes

pm3-2> sh netstat
Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
ether0 15585017 407 15305040 66 1302613 316 0
pm3-2> version
Livingston PortMaster PM-3 ComOS 3.8b17
System uptime is 6 days 9 hours 40 minutes

pm3-3> sh netstat
Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
ether0 10832628 666 10735749 16 888020 84 0
pm3-3> version
Livingston PortMaster PM-3 ComOS 3.8b17
System uptime is 7 days 15 hours 21 minutes

pm3-4> version
Livingston PortMaster PM-3 ComOS 3.8b17
System uptime is 26 days 5 hours 22 minutes
pm3-4> sh netstat
Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
ether0 3600840 9 2182681 22 699118 44 0

Command> sh netstat
Name Ipkts Ierrs Opkts Oerrs Collis Resets Queue
net0 184148209 1289 186145881 10307 0 0 0
Command> sh uptime
System has been up for 9007630 seconds (104 days 6 hrs 7 min 10 sec)

------
David Fisher, Owner/Administrator Skagit 360-428-3720
Fidalgo Networking, Internet Services Whatcom 360-708-9296
1725 Continental Place, Suite B San Juan 360-378-7671
Mount Vernon, Washington 98273-5640 Fax 360 416-0471

------=_NextPart_000_003A_01BDB3C0.C3126FA0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">

 
Hi,
 
   Here is the show netstat and version of = each of=20 my four portmaster
3's.  I am wondering if anyone else is having a = lot of=20 collisions on their
network, or is the PM3's reporting a lot of network=20 collisions.
 
  If you will notice I have also listed my USR = Total=20 Control Rack, which
has been up more then 100 days and with NO=20 collisions.
 
  I am wondering if this has been causing the = reboot of=20 the PM3's?  The
only one that has not rebooted since I installed = ComOS=20 v3.8b17, which
by the way has been the most stable ComOS yet, was = the fourth=20 and
last PM3.
 
  The previous ComOS v3.8b15 = rebooted a lot=20 more often.  Now the 1st,
2nd, and 3rd = PM3's only=20 rebooted once so far.  But I am wondering if
Lucent/Livingston has set a hard reboot option when = you reach=20 so many
collisions.  Also, why does my USR have no = collisions and=20 the PM3 has
lots?  They are all only the same network, same = Ethernet,=20 with the same
3Com SuperStack II Hub.
 
pm3-1> sh=20 netstat
Name     = Ipkts     =20 Ierrs   Opkts      Oerrs  =20 Collis  Resets  Queue
ether0   = 36516076  =20 61      36434744  =20 159     2625754  942    =20 0
pm3-1>=20 version
Livingston PortMaster PM-3 ComOS 3.8b17
System uptime is = 10 days 2=20 hours 16 minutes
 
pm3-2> sh=20 netstat
Name     = Ipkts     =20 Ierrs   Opkts      Oerrs  =20 Collis  Resets  Queue
ether0   = 15585017  =20 407     15305040  =20 66      1302613  = 316    =20 0
pm3-2> version
Livingston = PortMaster PM-3=20 ComOS 3.8b17
System uptime is 6 days 9 hours 40 minutes
 
pm3-3> sh=20 netstat
Name     = Ipkts     =20 Ierrs   Opkts      Oerrs  =20 Collis  Resets  Queue
ether0   = 10832628  =20 666     10735749  =20 16      888020  = 84     =20 0
pm3-3> version
Livingston PortMaster PM-3 ComOS = 3.8b17
System=20 uptime is 7 days 15 hours 21 minutes
 
pm3-4> version
Livingston = PortMaster PM-3=20 ComOS 3.8b17
System uptime is 26 days 5 hours 22 minutes
pm3-4> sh netstat
Name     = Ipkts     =20 Ierrs   Opkts      Oerrs  =20 Collis  Resets  Queue
ether0   = 3600840   =20 9       2182681   =20 22      699118  = 44     =20 0
 
Command> sh=20 netstat
Name     = Ipkts     =20 Ierrs   Opkts      Oerrs  =20 Collis  Resets  Queue
net0     = 184148209 =20 1289    186145881  10307  =20 0      =20 0        0
Command> sh = uptime
System has been up for 9007630 seconds (104 days 6 hrs 7 min = 10=20 sec)
 
 
------
David Fisher,=20 Owner/Administrator        =20 Skagit       360-428-3720
Fidalgo = Networking,=20 Internet Services     Whatcom  = 360-708-9296
1725=20 Continental Place, Suite=20 B            = San=20 Juan  360-378-7671
Mount Vernon, Washington 98273-5640=20 Fax           360=20 416-0471
------=_NextPart_000_003A_01BDB3C0.C3126FA0-- - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: