How to change an Auxiliary ID 4

[davidcc2112]

thread798-1401803

Hi,

I am trying to find the steps on how to change an Auxiliary ID in a Nortel 11C. We had to rebuild with another Dongle and keycode and now cannot get the MMail up due to the Aux ID is now different to the original one. Apart from rebuilding using the original Dongle and Keycode, it would be easier to just change the Aux Id to match the MMail. I understand this is possible but can't find the steps in any doco I have. I know LD 143 is required but want to confirm the steps before going onsite tot eh live system.
The original database was corrupt and EDD/BKO was not working since Feb 2011. We had to update the database manually onto a different daughterboard with a different dongle and keycode.

Can anyone help?

Cheers
David

 

[GHTROUT]

I did a forum search on "AUD ID" and it was interesting.

thread798-1593623

thread798-1641020

The first one shows someone getting prompted to change it, but they said "No" so we can't prove what "Yes" would do

--
Nortel Resources at GHTROUT.com World Famous!
--

 

[davidcc2112]

Hi GHTROUT,

I cannot change in LD 143 with .upgrade as the system requires new keycodes which we cannot get on this old 23.35 11C. Original Keycodes do not work and we tried to make no changes until the Aux ID change request as well but still the new keycodes are required.
In the linked thread the user BillCorv wrote:

BillCorv (TechnicalUser) 28 Aug 07 12:01
"Sounds like the MM Card Option ID 914433 does not match the Auxiliary ID on your Option 11.
Print your TID in LD 22
REQ TID
If the auxiliary ID does not match you can change it in LD 143 by running the UPGRADE. You will need to enter commands as if you were doing an Upgrade.
Print your key codes in LD 22. You will need to enter them.
REQ SLT"

Is there another way to change the AUX ID? In your attached thread, 798-1593623 a member mentioned going into PDT to change but was told a data dump could not be done. Is this recommended to try?
Thanks
David

 

[bhassell2000]

If you do a SLT in LD 22 does it show you the keycodes at the bottom of the report? Are these the keycodes that do not work now?

Thanks,

Buddy

Linked in Profile

http://www.linkedin.com/in/buddyhassell

 

[davidcc2112]

History of our situation.

We have an Option 11c 23.35 which was unable to EDD/BKO recently. Time restraints required us to retrieve another used 23.35 SSC with dongle and daughterboard to build as a backup if INI did not fix the EDD/BKO issue. We were able to install the latest backup and then manually update the customer database onto the replacement daughterboard but using the replacement dongle as we did not want to use the existing daughterboard assuming it might be the cause of the issue.
By the way - The rebooting of the system did not fix the EDD and eventually we were not able start the PBX with the existing database so we were stuck using the replacement parts and dongle ID and keycodes.
I have tried to use the existing keycodes and replacement keycodes but neither allow the steps to complete in LD 143 (.upgrade). I have tried to change 1 package to action the upgrade but it ass for a new keycode regardless if I change anything or not.
Is there another way to get the MMail up without having to format the old daughterboard and build from scratch?
Cheers
David

 

[one234]

HI,

If it is the same software release just replace the new dongle with the old dongle and enter the keycode of the old dongle.



Marc D.

If Bill Gates had a nickel for every time Windows crashed... Oh wait, he does...

 

[bdjoe5]

Meridian Mail works off of the Option 11's keycode. The dongle knows the serial of the PBX as well as the AUX ID of mail. I've had to change the AUX ID before when changing out mail systems but that requires Nortel to assign a new keycode for the dongle so both serials match.

I agree with Marc D ...put the old dongle back on and use those keycodes, as the serial and aux ID match already.

It's easier to put an existing dongle onto a new core card/daughter card and go from there.

 

[davidcc2112]

OK I will try that. Thanks for your help.

 

[Firebird Scrambler]

It's possible via "pdt" to change the AUX ID. I've done it, but you won't be able to do a EDD!. However the trick here is to change the AUX ID, then power up the Meridian Mail as it will look for the changed AUX ID.

Once it's powered up, just re enter back in the original ID. You will need to be sure that the Option 11c has a good UPS in place as any reboot will cause the mail to fail.

I can't give out details here!.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[davidcc2112]

Hi Firebird Scrambler
Thanks for this.

Reference:
Orignal Dongle = DG1
New Dongle = DG2
Original Database (daughterboard) = DB1
new database (daughterboard) = DB2

I tried to change back to DG1 and bootup works but there must be a problem with DG1 as it doesn't allow me to EDD with DG1 and DB2 together. Also MMAil does not boot up with DG1 at all. Only when I put in DG2 (DG2 / DB2 active) does the MMAil startup but we cannot access MMail (busy tone)Also cannot access from AX in Terminal window.

Also DB2 does not work at all anymore so we cannot return to original system with MMail working. Just loops in Startup with many errors too vast to list.

So Summarizing:

1. System orignally could not EDD. Also eventually could not get into Maintenance LD's or eventually normal LD's and TTY0 locked up but couldn't release by rebooting alone.

2. Replaced DG1/DB1 with DG2/DB2
= No access to MMail
= Able to EDD and released TTY0 automatically from DB2

3. Replaced DB2 only (keeping DG1)
= unable to EDD
= Unable to start MMail

4. Replaced DG1 with DG2 again (DG2 and DB2 active)
Then swapped DG2 with DG1 when MMAil was down but system was active.
= Still unable to start MMail.

I am getting this error after restarting MMail:

Program Resource Manager [Arg=""] Node 1 Ver. 1.0 (MM13)
PRM (Info) Using Software Volume : BOOT100:
PRM: Waiting for Seer Server to register
PRM: SetMMBlock: DoShutMM set to FALSE 0
PRM: InitSystem: MaxProgs calculated to be 50
PRM: Audit task is up
PRM InitSystem: starting VS node 1 prog 0 sibling -1
PRM: doing FOX security check
System ID = (new Dongle ID)
Meridian Mail Site ID (Old dongle ID ) does not match Meridian1 (new dongle ID)
**********System shut down****************

I am kind of out of thoughts.
I am assuming I will have to backup MMail if possible but how do I get to it now that DB1 is wonky.

Thanks if you can help

 

[davidcc2112]

Also I did try to add the DG1 keycodes but it didn't accept:
Keycode validation NOT successful.
Installation aborted.. returning to Main Menu

It also wouldn't accept the DG2 keycodes by the way

 

[Firebird Scrambler]

I think it's best if we talk off this forum as it's getting a litle tricky. Can you contact me or put in the dongle ID's on this forum please?. We need to check out what each one is licenced up for and also the software level etc.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

http://www.linkedin.com/in/davidbromley

If it's working, then leave it alone!.

 

[davidcc2112]

OK I left you an invitation on your Linkedin account.

 

[davidcc2112]

Thanks to all of you for your help. I was able to change the AUX ID in PDT.