[8267] in Commercialization & Privatization of the Internet
Re: ANSnet backbone router problems??
daemon@ATHENA.MIT.EDU (John Curran)
Fri Nov 12 14:01:40 1993
To: Gordon Cook <cook@path.net>
Cc: com-priv@psi.com
In-Reply-To: Your message of Fri, 12 Nov 1993 17:09:53 +0000.
Date: Fri, 12 Nov 1993 14:00:29 -0500
From: John Curran <jcurran@nic.near.net>
--------
] From: Gordon Cook <cook@path.net>
] Subject: ANSnet backbone router problems??
] Date: Fri, 12 Nov 1993 17:09:53 GMT
]
] A friend well to the west of Nearnet sent me this. I gather that the RS-6000
] routers are being stressed in ways that they can't handle well and that the
] stress is at bandwidths in the less than 15 megabit per second range. IE 1/3
] of what the NSF has been paying for for nearly 3 years now.
]
] Could someone more technical than I offer their views on what is going on?
Gordon,
We make our ticket information available via email and finger so that
interested parties can track our network performance. You don't need to
find a friend to get this information: "finger ticket-5893@nic.near.net"
will suffice.
Two notes regarding this ticket:
o The _router_ is not the stressed component, it is the ethernet
interface. Traffic via the FDDI interfaces performs as desired.
o At this time, there is no hard determination whether the problem
is generic to the ethernet interface cards or simply a failure of
the particular card in ENSS134.
Feel free to track the progress if you'd like; we've addressed the
problem in the interim by moving outbound traffic to the FDDI interface.
You can be certain that we will track and pursue any performance problems
that our members encounter.
/John
] ---------------
] Retrieving information on NEARnet Trouble Ticket 5893. Please wait...
]
] Ticket Number: 5893 Ticket Status: open
] Ticket Type: unplanned Ticket Source: noc
] Ticket Scope: network Site/Line: nsfnet-enss134
]
] Ticket Owner: long Problem Fixer:
] Telco Number:
]
] Ticket Opened: 10/26/93 15:10 Problem Started: 10/26/93 15:00
]
]
] Problem Description:
] Seeing roughly 3 percent packet loss to the ENSS134 router.
] Tests to other routers on the MIT external net run cleanly.
] Have notified ANS Operations staff of the problem.
] ...
] Note: 11 Several NEARnet members have reported 20% packet loss to the
] 11/10/93 15:37 enss today. We are working on offloading some traffic from
] long that path immediately (rerouting MBONE tunnels) and are
] planning to eliminate that path for outbound traffic tonight
] between 8pm and 10pm. We assume that rerouting outbound
] traffic to a router on the FDDI ring will suffice to prevent
] the ENSS Ethernet interface from dropping packets. We still
] plan to move all traffic (both inbound and outbound) to the
] FDDI ring but are awaiting a fiber pull scheduled for 11/19.
] ...
] Note: 16 At 23:15 we have changed the way NEARnet routes outbound
] 11/10/93 23:45 to the NSFnet. We are currently routing outbound via a
] skennedy connection to the FDDI ring that the ENSS also has a
] presence on. Inbound traffic is using the usual NEARnet
] connection to the ENSS ethernet. This means that until the
] next NSFnet config window on Friday morning there will be
] asymmetric routing. If the FDDI does go down, routing will
] switch over. If the ethernet goes down routing gets even
] stranger, but should work. Current tests show no packet loss
]
] Note: 17 Testing indicates that our change to outbound traffic has
] 11/11/93 10:17 had a significant effect on NEARnet -> NSFnet performance.
] skennedy We spoke with ANS, and they plan to have their side
] configured on Friday at 1800 so that we can make routing
] via the FDDI connection symmetric, and avoid the lossy
] ENSS ethernet card.
]
] For more information, please contact the NEARnet Network Operations Center
] at nearnet-ops@nic.near.net or (617) 873-8730. Thanks!
