"MOV" Command 1

as long as it's not a acd phone and the phone is disu before the move, it is used on this site in an 81 a dozen or more times a day.. more lately because we are moving 400 sets outof old dd cabinets in prep for an upgrade.. i would never use it in an opt 11 but know those who do...

john poole
bellsouth business
columbia,sc

I have mostly Opt 11's. Why would you not use it on an 11?

I have never experienced problems with MOV. That being said, I always heed warning about ACD and never us it on them. If you have a large quantity of sets to relocate, you can temporarily enable automatic set relocation, perform the relocations, then disable it again. The problem with automatic set relocation is you have to keep up on what TN's are what for your documentation.

As I have said many times on this and other forums, I have been using MOV command since 1979 and I don't know of any corruption. I have been hearing of this for 20 years and if it is true then way doesn't Nortel take the MOV command out???????????????????????????

The same thing with ACD sets. I worked for Nortel from 1979 to 1984 and was a test site for all new releases. Our standard answer for problems that we didn't know the answer to was, did you use the MOV command or did you change an ACD set without outing it first.

Do what you feel comfortable with.

I used to work for Nortel on one of there sites and the switches were corrupting every 3 months, the fault was that the link between the DN and TN became corrupted. There were no ACD units on the site. Whe you printed a TNH it would show active with no DN you could not out it or disable it.

I have never used the Mov command since. I was told that the Mov command was instituted for programmers to Mov data blocks within the switch. It is just as easy to use cpy command and do a 3 way swap anyway.

I have used it many times but was always warned by my tech support to out DTRs and Consoles first and anything that doesn't have a customer number. Never had a problem.

Meridian PBX Housekeeping Recommendations
For TN Corruption Prevention

Forward

Unfortunately there is no “cure all” to prevent TN or DN corruption as corruption occasionally occurs on any piece of equipment that is software driven and experiences many changes to it’s programming. The following is a list of patches, procedures, audits and suggestions that can positively impact the performance of the switch.


Index
Forward 1
Index 1
PATCHES 1
MPLR16603 1
MPLR16751 1
MPLR16669 1
MPLR15830 2
AUDITS & DIAGNOSTICS 2
LD 01: TEMPLATE AUDIT 2
MIDNIGHT/ BACKROUND ROUTINES 3
OTHER SUGGESTIONS 4
X11 MOV Command Clarification 4
MOV Command Restrictions: 4

PATCHES

MPLR16603
Instances of system memory and data corruption causing INI have been seen on some Meridian 1 PBXs running X11 Release 25.40. The problem could be experienced on any machine-type and has been traced to specific line of code relating to M3900 set-to-set messaging. When performing any service change to M3900, this line of code is
activated and can cause a variety of problems. In many situations, the results are not detrimental and would not be
noticed. However, in some cases, information can be written to an incorrect data block, causing corruption (which
can be corrected with an INI as noted below). Call processing issues may also occur. This patch is already on our additional global patch list for 25.40.

MPLR16751
A 12 digit or more FDN number for a 3900 set gets corrupted when the set is service changed.
This patch is not currently on our global patch list. Also Non-Public.

MPLR16669
This problem will affect all sites that have 500/2500 sets that were created or changed on 25.08, 25.10, 25.15, or 25.30, and then MOV those sets on 25.40, as the first service change to the set on 25.40. In other words if a set is
CHGed on 25.40 before it is MOVed on 25.40 then there will not be a problem. The problem remains a potential until all 500 sets created on 25 prior to 25.40 have been service changed to remove the HMDN data.

This patch is part of a product Advisory Bulletin that was issued August 22,2002 ( See Attached) This problem only exist on release 25.40 and 25.40B and will be incorporated into the dependency lists.
.
MPLR16657
Used with the above patch to identify any corruption caused by the MOV command. ( See Attached bulletin)

MPLR15830
Written for 25.15, 25.30 and 24.25. Fixed in 25.40 CHG 500 set cause hotline DN corruption.
Analogue and digital set share same DN. Analog set has CLS EHTA and FTR HOT D.
Digital set using DN as two-way hotline. MARP is on 500 unit.
If perform service change of analogue set MARP is not set correctly
Analog set removed from MARP TN's.

Additional patches in the MPL that address TN corruption are mostly diagnostic in nature and address specific site dependent needs. Patches that were available in earlier releases that were considered global in nature have been
incorporated or “fixed” in later releases.



AUDITS & DIAGNOSTICS

Template audits should be considered especially in the larger switches whenever there has been a lot of move, add and change (MAC) activity. The recommended frequency will vary depending on the amount of activity. A rule of
thumb would be every three months for heavy MAC activity to every six months for normal MAC activity.

LD 01: TEMPLATE AUDIT

Templates are used to store data, which is common to many telephones. This includes items such as key
functions and class of service. The Template audit program saves protected memory by eliminating
unused or duplicate telephone templates.

Load 01 also performs the following consistency checks.

User Count Scan
All telephones in the system are scanned to find the total number of users for a template.
Templates that have no users are removed. Incorrect user counts are identified and corrected.

Duplicate Template Scan
Each template is checked against every other template for possible duplication. If a match is found, a scan
is then initiated to locate all users of the current template and move them to the matched template. For each
of these users found, the template number in the telephone data block and the user count is updated. After
all of the users of the current template are moved to the matched template, the current template is removed.

Template Checksum Audit
A checksum is calculated for each template and compared with the existing template checksum. The
existing checksum will be corrected if there isn’t a match.

Key Lamp Strip Audit
Two checks are made to correct Key Lamp Strip (KLS) corruption. First, the template length is compared
to the number of KLS indicated in the protected line block. The second check verifies that the last word of
template reflects a ‘Null’ key. If these checks detect any discrepancies, they are corrected.

Operating Parameters.
Due to the Real Time impact of this program and large amount of data being scanned, the Template Audit
should be run during LOW TRAFFIC hours.

The Template Audit SHOULD NOT BE ABORTED unless it is critically necessary. If it does become
necessary to interrupt execution of the audit, be aware that the templates may be corrupted.

The template Audit cannot be run as a background task.

To confirm that extraneous templates have been removed and that all counts have been corrected to their
proper value, re-run the audit program.

A datadump (LD43) should be run after a template audit is executed.


MIDNIGHT/ BACKROUND ROUTINES


The following loads are recommended for inclusion in the midnight and background routines which can be
loaded in the Configuration Record LD17


LD 30 -Network & Signaling Diagnostic
( Recommend running in background )

LD 34 - Tone & Digit Switch & Digitone Receiver Diagnostic

LD 38 – Conference Circuit Diagnostic

LD 43- Equipment Data Dump

LD 44- Software Audit
( Recommend running in background )

LD 45- Background Signaling & Switching Diagnostic
* This overlay program is not available on option 11C systems. Use LD30 to perform signaling tests
on these systems.
( Recommend running in background )

LD 60- Digital Trunk Interface & Primary Interface Diagnostic

LD 135- Core Common Equipment Diagnostic

LD 137- Core Input/Output Diagnostic. ( Optional)









OTHER SUGGESTIONS

? For general Housekeeping Information, please reference NTP 553-3001-500

? Do Not make changes to TNs that were acquired by Symposium or Call Pilot. First De-acquire TN then
rebuild .


? Making changes to ACD agent TNs is not recommended. TNs should be outed then rebuilt.

? The use of Optivity Telephony Manager (OTM) can ease the recovery from TN corruption.
By validating configurations and providing a Graphical User Interface OTM can minimize input errors.
For more information on OTM please refer to NTP 553-3001-330.

? MOV Command Clarification for release 25.30 ( See Attached Product Bulletin 2001_097)

X11 MOV Command Clarification
At the request of the DAC M1 Core Task Force, this bulletin is being issued to clarify the current restrictions when using the move command (MOV) in various applications and configurations. The information listed below was verified on Release 25.30 software. Where applicable we have noted known differences in operation on older releases of software.
MOV Command Restrictions:

IMPORTANT NOTE: Prior to using the MOV command, it is advised that any active device (phone, card, shelf, loop, etc) be disabled.

LD 10 – Analogue Telephones
MOV command can be used to move analogue “IPE” telephones from one loop, shelf, card, unit to another lscu with the following restrictions (includes moves across Superloops):
- ACD sets must not be moved. Remove (out) data and re-enter at destination.
- Telephones with mixed directory numbers can only be moved to a TN on the same loop; unless the prompt MLDN = Yes in LD 17.
- Cannot be used for Option 11C model sets

MOV command can be used to move analogue “EPE” telephones from one unit or card to another, but does not support moving these phones across shelves or loops.

LD 11 – Digital Telephones
MOV command can be used to move digital “IPE” telephones from one loop, shelf, card, unit to another lscu with the following restrictions (includes moves across Superloops):
- ACD sets must not be moved. Remove (out) data and re-enter at destination.
- Cannot be used for Option 11C model sets

MOV command can be used to move digital “EPE” telephones from one unit or card to another, but does not support moving these phones across shelves or loops.

MOV PAIR command can be used providing the system is on Rls 24 or 25. This command will not function properly on rls 15 – 23, recommend using MOV on these releases of software.

Notes:
- If moving a voice unit with an associated data unit, the data unit must also be moved. On the NT8D02 DLC card, both voice and data TN’s can be moved by the MOV PAIR command.
- If Call Forward is activated prior to the set move, the Call Forward data will be moved to the destination set.





LD 12 – Attendant Consoles
Attendant Consoles cannot be moved across loops or superloops. Console data must be deleted “Out data” and reentered in the new location.

- Option 11C note: Superloops on an Option 11C are as follows: internal superloops in a 2 cabinet Option11C system are (4 slots per Sloop):
slots 1- 4 5 – 8 9 - 12 13 – 16 17 – 20
|--------------------------------|-------------------------------|
cabinet 0 cabinet 1

- SCH0475 message will be changed from “SCH0475 Trunk units cannot be moved between loops” to ”SCH0475 Trunk or Attendant units cannot be moved between loops or superloops”.

-
LD 13 – Digitone Receiver, Tone Detectors, MF Senders and Receivers
MOV command not supported due to complexity of restrictions and the risk of data corruption if restrictions not adhered to. Limited usefulness.

LD 14 – Trunk Data Block
MOV command cannot be used to move trunk data blocks.


LD 17 – Configuration Record 1
MOV command not supported for moving MSDL D-channels and PRI D-channels due to complexity of restrictions and the risk of data corruption if restrictions not adhered to. Limited usefulness.

LD 18 – Group Call
MOV command can be used to renumber one group call or speed call list to another.

LD 19 – Code Restrictions
MOV command can be used to move code restriction data blocks to a new route.

LD 25 – Move Data Blocks
MOV command can be used to move data blocks at a card, shelf or loop level within the following guidelines:
1. Before using the MOV command, the following hardware should be removed from the source and destination loop, shelf or cards and reconstructed after the move is completed.
- Consoles
- Digitone Receivers
- Dial Tone Detectors
- Multifrequency Compelled Signalling cards (MFC/MFE)
- PRA loops
- ACD telephones
- All lines associated with the loop or card on the destination side of the move command.
2. Loops must be configured in LD 17
3. NT8D17 Conference/TDS card cannot be moved with LD 25
4. Type of source card must match with the card type on the destination side.
5. Cannot move Superloop data on a customer basis (SCH5235)


LD 26 – Group Do Not Disturb
MOV command can be used to move DN from one DND Group data block to another.


LD 49 – Flexible Code Restrictions
MOV command can be used to move code restriction data blocks to a new customer and/ or NFCR tree data block.



--
Fletch
Visit the Nortel Technical Support Portal at:

answer to my disdain for an opt 11.. a single processor switch that needs 374 patches the day you do the install can't be real good news.. i have seen more corruption in a single opt 11 then i have in all the 81's i have every installed.. might be just the luck of the draw but the smaller switches have not been my biggest friend.. (maybe i just don't trust a hard drive that don't spin)

john poole
bellsouth business
columbia,sc

Currently, Succession 3.0 will end up with about 35 to 40 patches with the current DepList loaded. This is true regardless if it's an Option 11C or an Option 81.

The number of patches in a system in no way reflects the release stability.

--
Fletch
Visit the Nortel Technical Support Portal at:

i've installed 50 options 11's and maybe 100 81's and 61's.. i have seen more software corruption on a single opt 11 then on all the big switches put together.. i know what the book says but rls 16 or so when i installed my 1st 11 up to maybe rls 20 when i installed my last, 11's gave me more strange trouble then it should have.. not big stuff, just pri's, dchl etc that would not auto restore after an outage, or phones that you would have to out and put back in to get them to follow a hunt.. same switch different processor, different problems

john poole
bellsouth business
columbia,sc

Has anyone tried the MOV command in LD 25? I have to move Phantom TN's from a TERQ Loop to a Phantom SuperLoop prior to my Succession upgrade. I tried moving a card in a test lab switch and the cards moved, but my TTY locked up and would not let me input any data, but I could see normal bug messages on the TTY. I had to INI to get the TTY back. One other time Nortel tried to clear the problem by getting into the "code" and the switch went into an INI loop and we had to sysload to get the PBX running. Are we doing somethig wrong?

will not work between a terq and a supl.. supl to supl works but both loops must be the same cequ def. best to run a short script that disu's the station, moves it then does an idu.. if you can use merge the script will take an hour or so to move a few 100 stations

john poole
bellsouth business
columbia,sc