CM3.1 Sync problems? 1

[wjata]

Has anyone experienced serious slip problems with CM3.1?

We are experiencing sync problems on a multi-connect S8700 immediately following our upgrade to 3.1 from 3.0.1.

All T1’s in the fiber connected EPN’s are slipping, the T1’s in the IP connected EPN’s are just fine. I have tried changing the sync source to different T1’s and different port networks and to the latest tn464-h boards. I have also switched the SNI clocks as well. All firmware is the latest Feb-06 versions.

Any ideas?

Wayne

 

[Dunstan]

Is this in a mixed environment? Such as one using "control network c"? I ask because we are experienceing a similar problem at the moment. On a recent upgrade of the exact same nature.

Avaya currently is looking at it..But they seem lost.

 

[wjata]

The location that has the problem is a 4 port network with CSS and A&B ipsis in port networks 1,2,3 and pn 4 is fiber only. All the other loactions are running on the C network but they seem to be fine.

We do have Avaya engaged on this as well but they have not come up with anything yet.

 

[Dunstan]

Ask your avaya guy to look in the CM logs on the server....The issue we just found is that this actually starting when we originally enabled CNC, however it did not register on "disp alarms" or in any visible way until we did the 3.1 upgrade.

So what I am saying is two fold...one this problem has been associated with Control net C since it was available

two it does not show until you actually get to release 3.1.

Question for you...Are you really slipping? In other words although we show the slips all test items pass and we can do PN to PN faxing and modem calls which are not going to happen if you are truly slipping.

My guess is that these are erroneous errors...not real. Either way it has been almost two weeks and Avaya is still not sure which way to go with it next.

Perhaps we should make each others Avaya contacts aware of these two sites....maybe if they know it to be a problem in multiple locations using 3.1 and control net C it would be easier for them to resolve...

 

[wjata]

The problem became apparent when the remote definity-extenders (like modems) started to drop.

We enabled CNC about 6 weeks ago and did not notice any sync issues but then again we didn't have any reasoon to look for them.

I posted this here hoping to find some other brave souls that took this leap to 3.1 and if it is a common problem Avaya will be able to get it resolved quicker.

I'm working with George at ext 49021.

 

[berniebrown432]

A couple of thoughts:

Wayne, I didn't quite understand one thing. Did you try to use T1s in the fiber PN as the sync source and still get slips? If so, this should have also triggered sync alarms.

This also triggers a memory of a guy who had a timing issue between his CSS and a PN. It kept looking like either an SI or EI board, but I never saw a resolution from him. It was either on this bboard or avayausers.com.

You can also find me at the same ID over there.

Bernie

 

[wjata]

Bernie,

We have T1's in every PN and have tried using a T1 as the sync source in every one of our fiber connected PNs and still get slips but do not get any Sync alarms. We are slipping because definity extenders will not stay up.

I'll check in avayausers as well.

Thanks

 

[wjata]

Dunstan,

Do you have an Avaya tier3 tech name/ext that you have been working with that you could share? My tech seems to be running out of options. I passed along the CNC info but he hadn't of it.

Wayne

 

[Dunstan]

I took the liberty of passing on what you posted. Including the name and ext of your tier 3 guy.

Mine is as follows

Kevin P.

49551

We have an idea of a potential problem I will know if I make any progress in the morning. It is in relation to the Switch node clocks and a software glitch.


I am not sure what your experience is but mine seems to be past cutting edge with them (Avaya) and on the bleeding edge as it pertains to Control network C.

We have seen a number of strange things happen during the course of it;s production environment time.

 

[Dunstan]

Wjata,

No progress to report other then we have now moved up to tier 4. My Tier III guy and your have compared notes and the problems look nearly identical. They are stumped.

If you make any progress let me know.

The key here is control network C not the release you are on btw. The release you went to 3.1 is now showing something that it did not show prior (Alarms) but apparently the Avaya CM logs (the ones only they see) show these errors occur from the implementation of C forward.

 

[wjata]

Avaya has given us an interim fix for this sync problem in a mixed environment.

To fix the slip in the direct connect EPNs (1-4) that have their sync set to a T1 in EPN1 we needed to
1: disable sync
2: set sync (tone board)
3: enable sync
in all IP connected EPNs that did not have a T1 to sync to locally, aka freerun.

Crazy, but it works!

Thanks Dunstan for the team work.

Wayne

 

[Dunstan]

Aye we used the same method today. This is not a permanent fix the tickets (More then just ours) remain open with tier 4.

I appreciate all your help.