Frame Relay: PVC has been reset but nothing recorded in log

As stated in the subject, I have seen this couple times that all PVCs on the same physical interface (e.g. s0) were reseted, but could not find anything in the log showing the status changing of s0. Typically, there should be something in the log, such as "interface s0 status down...." and ".....up", as well as "protocol  down / up". But I swear, I didn't see it at all in the log in some cases. Log is not full, it listed events before the PVC reset.

Q1: Could PVCs reset while the interface is up? What's causing this? LMI error? Any command can show this?

Q2: Could it be the log missed the event so didn't record the status changing of s0?

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Don JohnstonInstructorCommented:
Yes. A PVC is a "virtual" circuit. It exists independent of the physical interface. PVC's can be added, deleted or reset without your serial interface knowing it. Your router is receiving the information through LMI messages though. I would suspect the frame-relay provider is working on the PVC.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
robinluoAuthor Commented:
Well, as a matter of fact, I work for the FR provider and monitor all client's nodes. When this kind of things happened, our folks who looks after the circuit never see any error on their end. In other cases, if log does catch event of interface down / up, there is always alarm be seen on circuit side.

Donjohnston, I think you are right that this is a layer 2 issue, although most of the L2 error I've seen was caused by L1. But apparently the case in my question is exceptionist.

Thanks for your input.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.