NSFNET Transition Update -- ANS

Guy Almes

ANS

Table of Contents

• Traffic on ANSNET
• Stan Barber's Notes
• Feb 1995 NANOG Home Page

Traffic on ANSNET

• ENSS 128 (Stanford)
• ENSS 130 (Argonne)
• ENSS 131 (Ann Arbor)
• ENSS 132 (Pittsburgh)
• ENSS 134 (Boston)
• ENSS 136
• ENSS 139 (Houston)
• ENSS 142 (Salt Lake City)
• ENSS 143 (Seattle)
• ENSS 144
• ENSS 145
• ENSS 218 (NY/NJ NAP)
• ENSS 257 (CA NAP)

Stan Barber's Notes

Guy looks at the average usage on the ENSS over a monthly period. He also gathers data on the busiest 15 minutes each day.

ENSS257 (California NAP) shows that it is not congested and is not much used. ANS is peering with CRL at this location.

ENSS145(Fix-East) indicates that in mid-October the rate was beginning to peek at about 19Mb/sec. Peter asked if Guy felt if the rate of 10Mb/sec has a high-water mark. Guy would not contradict that statement. ANS worked with other providers to make more even use of FIX-West.

ENSS136(College Park--SURANET, MAE-East) There was a dramatic 15 minute peak decrease when SURANET transitioned in the first week of December.

Sprint NAP (ENSS 218) shows steady increases. Shows about 6mb/sec in the first week of February.

Guy also said the ENSS136 will be moved to MAE-EAST+. Guy remarks that the three east coast interconnects (at FDDI) help make things work well on the East Coast. NEARNET transition shows they transitioned and backed off. Seattle showed no change. BARRNET did transition.