Here are some statistics from the last year of WAN implementations at my
company.
178 Unique circuit installs
- 123 FR
- 55 point-to-point circuits (T1 or greater)
46 Incomplete installations due to errors
- 13 Extended DEMARC
- 1 Bad serial port on router
- 12 Bad configuration by LEC
- 21 Bad configuration by CLEC
- 2 Operator error
Food for thought. I can give detailed information on this if anyone would
like to hear more.
Kelly D Griffin, CCNA
Network Engineer
Kg2 Network Design
http://www.kg2.com
----- Original Message -----
From: "John Neiberger" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, January 03, 2001 11:40 AM
Subject: RE: Frame Relay PVC
> I've experienced these types of symptoms several times and 99% of the time
> it really is the telco's fault, it just takes some serious pressure to get
> them to put some resources toward fixing the problem.
>
> However, at least once I found that it was a bad extension from the demarc
> (NIU) to the csu/dsu. The building we were in had lots of other equipment
> at the demarc, and from time to time throughout the day some of that
> equipment would generate enough EM noise that it would cause a lot of
errors
> on our line and the PVC would go down.
>
> The telco tested and didn't find any problems and even sent a tech who
> didn't discover any problems. I later went there myself and re-oriented
> some of the cables in relation to other equipment and the problem went
away.
>
> > My first and last inclination (not to mention every inclination in
> between)
> > is to blame the telco. If they've truly done testing on the circuit and
> > can't find anything, then consider whether you cross multiple carriers
on
> > that PVC. It may not be your local carrier's issue, which is why they
> > haven't found anything. If you're on a single carrier, then I would
> > recommend a redesign of that PVC. It's easy to say there's nothing
wrong
> > with the configuration of the PVC when you're talking with someone who
> > doesn't know all the ins and outs of frame switch configuration, but in
> my
> > experience, most of the carrier techs don't really KNOW their
equipment -
> > they just have a script they run through to create new PVCs, hence they
> may
> > not be exactly accurate when they say that everything is fine.
> >
> > Hope that helps.
> >
> > - Don
> >
> > -----Original Message-----
> > From: Radford Dion [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, January 03, 2001 8:46 AM
> > To: [EMAIL PROTECTED]
> > Subject: Frame Relay PVC
> >
> >
> >
> > I have a intermittent problem (about a dozen times a day) where a PVC
> goes
> > from the active to inactive state. It used to happen maybe once a week.
I
> > have not changed anything on either router. Furthermore, my other PVC's
> are
> > unaffected.
> >
> > I did a debug of the lmi packets and the output is below. My telco says
> > there is nothing wrong with the physical connection or the
configuration
> of
> > the PVC. If anyone has an explanation for these events, or even better,
a
> > solution to fix the damn thing, I'd love to hear it.
> >
> > Thanks,
> >
> > Dion
> >
> > Serial0(in): Status, myseq 89
> > RT IE 1, length 1, type 0
> > KA IE 3, length 2, yourseq 193, myseq 89
> > PVC IE 0x7 , length 0x3 , dlci 235, status 0x2
> > PVC IE 0x7 , length 0x3 , dlci 250, status 0x2
> > PVC IE 0x7 , length 0x3 , dlci 271, status 0x0
> > *Jan 3 10:23:37: %FR-5-DLCICHANGE: Interface Serial0 - DLCI 271 state
> > changed to INACTIVE
> > *Jan 3 10:23:37: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial0.1,
> > changed state to down
> > PVC IE 0x7 , length 0x3 , dlci 750, status 0x2
> > Serial0(out): StEnq, myseq 90, yourseen 193, DTE up
> > datagramstart = 0x401D66CC, datagramsize = 14
> > FR encap = 0x00010308
> > 00 75 95 01 01 01 03 02 5A C1
> >
> > Serial0(in): Status, myseq 90
> > RT IE 1, length 1, type 1
> > KA IE 3, length 2, yourseq 194, myseq 90
> > Serial0(out): StEnq, myseq 91, yourseen 194, DTE up
> > datagramstart = 0x40001338, datagramsize = 14
> > FR encap = 0x00010308
> > 00 75 95 01 01 01 03 02 5B C2
> >
> > Serial0(in): Status, myseq 91
> > RT IE 1, length 1, type 1
> > KA IE 3, length 2, yourseq 195, myseq 91
> > Serial0(out): StEnq, myseq 91, yourseen 194, DTE up
> > datagramstart = 0x40001338, datagramsize = 14
> > FR encap = 0x00010308
> > 00 75 95 01 01 01 03 02 5B C2
> >
> > Serial0(in): Status, myseq 91
> > RT IE 1, length 1, type 1
> > KA IE 3, length 2, yourseq 195, myseq 91
> > Serial0(out): StEnq, myseq 92, yourseen 195, DTE up
> > datagramstart = 0x402295A0, datagramsize = 14
> > FR encap = 0x00010308
> > 00 75 95 01 01 01 03 02 5C C3
> >
> > Serial0(in): Status, myseq 92
> > RT IE 1, length 1, type 1
> > KA IE 3, length 2, yourseq 196, myseq 92
> > Serial0(out): StEnq, myseq 93, yourseen 196, DTE up
> > datagramstart = 0x40000FB4, datagramsize = 14
> > FR encap = 0x00010308
> > 00 75 95 01 01 01 03 02 5D C4
> >
> > Serial0(in): Status, myseq 93
> > RT IE 1, length 1, type 1
> > KA IE 3, length 2, yourseq 197, myseq 93
> > Serial0(out): StEnq, myseq 94, yourseen 197, DTE up
> > datagramstart = 0x401D5E9C, datagramsize = 14
> > FR encap = 0x00010308
> > 00 75 95 01 01 01 03 02 5E C5
> >
> > Serial0(in): Status, myseq 94
> > RT IE 1, length 1, type 1
> > KA IE 3, length 2, yourseq 198, myseq 94
> > Serial0(out): StEnq, myseq 95, yourseen 198, DTE up
> > datagramstart = 0x400003FC, datagramsize = 14
> > FR encap = 0x00010308
> > 00 75 95 01 01 00 03 02 5F C6
> >
> > Serial0(in): Status, myseq 95
> > RT IE 1, length 1, type 0
> > KA IE 3, length 2, yourseq 199, myseq 95
> > PVC IE 0x7 , length 0x3 , dlci 235, status 0x2
> > PVC IE 0x7 , length 0x3 , dlci 250, status 0x2
> > PVC IE 0x7 , length 0x3 , dlci 271, status 0x2
> > *Jan 3 10:24:37: %FR-5-DLCICHANGE: Interface Serial0 - DLCI 271 state
> > changed to ACTIVE
> > *Jan 3 10:24:37: %LINEPROTO-5-UPDOWN: Line protocol on Interface
> Serial0.1,
> > changed state to up
> > PVC IE 0x7 , length 0x3 , dlci 750, status 0x2
> > Serial0(out): StEnq, myseq 96, yourseen 199, DTE up
> > datagramstart = 0x400003FC, datagramsize = 14
> > FR encap = 0x00010308
> > 00 75 95 01 01 01 03 02 60 C7
> >
> >
> > Configs:
> > Router A:
> >
> > interface Serial0
> > no ip address
> > encapsulation frame-relay
> > bandwidth 256
> > frame-relay lmi-type ansi
> > !
> > interface Serial0.1 point-to-point
> > ip address 172.19.148.254 255.255.255.0
> > frame-relay interface-dlci 271
> >
> >
> > Router B:
> >
> > interface Serial1
> > no ip address
> > encapsulation frame-relay
> > bandwidth 64
> > no fair-queue
> > frame-relay lmi-type ansi
> > !
> > interface Serial1.1 point-to-point
> > ip address 172.19.148.253 255.255.255.0
> > frame-relay interface-dlci 240
> >
> >
> > *****************************************************************
> > DISCLAIMER: The information contained in this e-mail may be
> confidential
> > and is intended solely for the use of the named addressee. Access,
> copying
> > or re-use of the e-mail or any information contained therein by any
other
> > person is not authorized. If you are not the intended recipient please
> > notify us immediately by returning the e-mail to the originator.
> >
> > _________________________________
> > FAQ, list archives, and subscription info:
> > http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> >
> > _________________________________
> > FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
>
>
>
>
> _______________________________________________________
> Send a cool gift with your E-Card
> http://www.bluemountain.com/giftcenter/
>
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
____________________________________________
http://1cis.com
Free E-mail Servers with unlimited mailboxes
1st Class Internet Solutions
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
