We saw this same problem for a while, and they told us the other thing. It eventually turned out that they hadn't actually locked the port on the clear IPe switch to 10/half, and it was totally failling to correctly autonegotiate. Once they forced their end, it all got a lot happier... This took 3 days of them telling us that it was our end that was at fault. On Wed, 13 Jun 2001, Seeby Woodhouse - Orcon wrote:

Hmm

we have forced full-duplex and turned off auto-negotiation on our Catalyst 5000 switch - but we have also tried all the other settings possible. Clear have told us to set it to 10Mbps Full-Duplex - so that's what it is at present.

Cheers Seeby

Orcon Internet - www.orcon.net.nz

----- Original Message ----- From: "Ian Quinn" To: "Seeby Woodhouse - Orcon" Sent: Wednesday, June 13, 2001 6:42 PM Subject: RE: Orcon APE connection woes

...

I had some problems recently that were marginally similar. Although I had the speed and duplex settings configured, it didn't come right until I turned off auto negotiation as well (eg no negotiation or something along those lines).

No idea if it's your problem - just seems familiar.

Good luck :-)

Regards / Ian

...

-----Original Message----- From: Seeby Woodhouse - Orcon [mailto:seeby(a)orcon.net.nz] Sent: Wednesday, 13 June 2001 6:27 p.m. To: NZNOG Mailing List Subject: Orcon APE connection woes

Hi there everyone

Orcon has just had a 10Mbit IPExpress connection to APE completed, and I have been fighting with it all day.

If we ping anyone on APE, then we get around 2/3's of the pings through, and 1/3 are dropped. This happens in a pattern of 1/3 drop, 2/3 get through.

I talked with Clear and they said that it could be the IPExpress connection re-negotiating because of what is on our end, so we have been playing with the settings on our Catalyst 5000 switch - we have forced the port to our IPExpress connection full duplex / half duplex / 100mb / 10mb but they all seem to give the same results.

Clear has advised us to set our equipment to 10Mbit full duplex - so that's what it is at present.

The connection from IPExpress is then VLan'd from our Catalyst switch into our core Cisco 7505 router.

A ping report of 300 pings to ihug.ape.net.nz looks like this

--------------------------------------------------- ORCON7505#ping Protocol [ip]: Target IP address: ihug.ape.net.nz Repeat count [5]: 300 Datagram size [100]: Timeout in seconds [2]: Extended commands [n]: Sweep range of sizes [n]: Type escape sequence to abort. Sending 300, 100-byte ICMP Echos to 192.203.154.36, timeout is 2 seconds: ........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!..........!!!!! !!!!!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! !!!!!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!!!!!...........!!!!!!!!!!! !!!!!!!!!...........!!!!!!!!!!!!!!!!!!!!!..........!!!!!!!!!!!!!!!!!!! !!..........!!!!!!!! Success rate is 65 percent (197/300), round-trip min/avg/max = 1/3/24 ms --------------------------------------------------

Can anyone shed any light on this?

Is this related the the spanning tree problems that have been happening up at APE recently? Or should we be hassling Clear about the service.....

Cheers Seeby

Orcon Internet - www.orcon.net.nz

--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

--- Matt Camp --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog