[afnog] Flapping POS Interface on Frame-relay between a Juniper and Cisco

Righa Shake righa.shake at gmail.com
Fri Dec 9 06:25:05 UTC 2011

The interface finally stabalised. This after performing segment by segment
loop tests at SDH level.

We found errors which were sorted after which the service has been better
the random flaps have since disappeared.

 From The trouble shooting I can say the following:

Loop tests be performed with either PPP or HDLC encapsulation instead of
frame-relay.However its important to note that when you change the
encapsulation from Frame-relay to either of the above the subinterfaces
will be automatically deleted.So best be careful here.

The command *show controllers pos0/0/1 *will also help in detection of
errors that may reside at SDH level.

Thanks all for your assistance in helping solve this.

Righa Shake

Thank you all for your assistance in helping solve this.

Now dealing with random BGP cease notifications I receive from my upstream.

Righa Shake

On Tue, Nov 22, 2011 at 12:40 PM, Mark Tinka <mtinka at globaltransit.net>wrote:

> On Tuesday, November 22, 2011 02:43:19 PM Righa Shake wrote:
> > I did change and put in ietf this over the weekend and
> > the link has had some stability now.
> Good to hear. Strange, but not unusual. Normally, mismatched
> encapsulations would fail a raise of the Layer 2 transport -
> but like I said, strange :-).
> > The interface flaps have greatly reduced though they are
> > still there.
> How often? Like, how many times in an hour?
> > Am looking at the problem also from SDH level as am also
> > thinking the transport media could be an issue.
> If you're dealing with a 3rd party, are they seeing any
> alarms that correspond to the times you see a flap? If it's
> purely an encapsulation issue, then they wouldn't. But if
> it's a problem with the infrastructure provider (which I
> suspect), they should be seeing some alarms or logging some
> donwtime.
> Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://afnog.org/pipermail/afnog/attachments/20111209/9b0708e8/attachment.html>

More information about the afnog mailing list