Disabling TN's - When do you NEED to?

[phannah]

This has been discussed to death, but I wanted to, perhaps, get opinions on when it is necessary to disable a set, and when you can skip that step. I'm talking about non ACD sets - that's clear enough, out and rebuild, but I think for standard sets, it's still gray.

I've read posts in which LD 20 and LD 95 changes were done to a set without disabling it, but I've become very cautious since a couple of free INI's.

The other question regarding disabling a set during changes, is if the set being changed, or outed for that matter shares common DN's with other sets, must these sets be disabled as well, or can this be skipped? I know there's a perfect world, and the real world, and sometimes it's just not an option.

Thank's!

Patrick

 

[Dougo123]

I've been doing echg on not acquired sets and have not seen a problem. Wait,let me say sets that have never been acquired since first programed that will never be used in symposium. I know most here will advise against doing this in a pbx thats running it, and maybe I've been dodging a bullet. but that's just my 2 cents. If anyone has seen corruption from this I'd like to know too. Any set that is acquired I always completely remove and rebuild. On another note, anyone else using screenpops and what's your thoughts?

 

[johnpoole]

you can make changes all day on standard sets without disu, but the next one you do might ini the switch. it's like the seatbelt in your truck, after you get used to using it, it's second nature. i have never heard of disu a tn to change a name, or disu all sets with common dn's.. all my scripts, all the techs that work on a switch i am working on, prt, disu, chg, idu. with those four steps as a habit, your in safer water.. i don't beleive a change by itself can ini a switch. i think when the cpu is taxed with traffic and other err, bug codes etc, acd calls, and you happen to make a change, during that change, if the user transfers a call or starts a conf, etc, you're part of a sequence that happens to be the straw that breaks the camels back. i do no acquired set will ini, in a heart beat, ever time. as you well stated, any acd change, is a auto out, then new, you may short cut that, and live to tell about it, you may do it and end up with a hard drive that's not even bootable, if you where trying to save time of you could slip out early, your not going to make happy hour. their may be techs that disagree, but not in my switchroom, those rules are carved in stone. when i went to texas the 1st time, that was never mentioned, of course you couldn't prt a tnd in ld 20 either, dn's in 20 tn's in 21 and stat in 32, and changing loads took 5 minutes at least. that was rls 6. my hair was blond, my kids didn't have grandkids...(darn i'm old)

john poole
bellsouth business
columbia,sc

 

[acewarlock]

Your memory is failing also.
TNB 20
DNB 22
RDB 21

 

[johnpoole]

yes it was, at least i remembered you couldn't prt tn's and dn's in the same load. that in itself was a stretch. and you always catch my mistakes, that i will remember, in case you EVER make one..

john poole
bellsouth business
columbia,sc

 

[johnpoole]

i guess to be totally safe we could just turn off the cni's for any change.. maybe people would quit wanting so many changes, remember some of the old stuff you had to power cycle to make changes take effect?

john poole
bellsouth business
columbia,sc

 

[acewarlock]

I've been known to make a mistake or two, but I can't remember when I did last. HA HA

 

[DavidGaud]

Hi
here we never got problems when we made change on a set if it's not acquired by symposium.
In a case of a symposium set we always de-acquired it even if it is just a change of name in LD95.

David

 

[johnpoole]

that's true, but i would recogmend a disu anyway, their free, and they have been known to avoid corruption. i have READ about that when someone started a transfer just as you hit the last stroke, when the switch came back up the from and to tn were both vacant, but you couldn't add a phone to either of them and the dn, although printed no act no date, was not in the ludn table and you couldn;t put it on a phone? nortel took about an hour to clear the problem.. this post was from a pretty good tech, and he had no reason to bs.. it never hurts to take the extra 3 seconds

john poole
bellsouth business
columbia,sc