cannot access option 11c through OTM

[ChrisKnerr2010]

I have two sites that I am having issues with. The issue I am having is that I cannot remote into the option 11c using the OTM navigator. We have back-up SEB's at the sites and I can access the option 11c through the SEB, yet when I try to access these sites through the OTM navigator i receive a message at the overlay passthrough screen saying that the remote destination is not reachable. Any suggestions?

 

[ChrisKnerr2010]

Nessman,

finally got to do a ld 37 stat on one of the remote sites through the SEB. here is what I found:
TTY 0 : ENBL
TTY 1 : ENBL
TTY 2 : ENBL
TTY 10 : DSBL DES: OTM
TTY 11 : DSBL DES: OTM

 

[Firebird Scrambler]

I think the next step is to connect the 11c Ethernet cable onto a laptop via a cross cable and see if you can ping each other?.

Have you checked your route entry in LD 117?. I know that you have done this many times, but I would start from scratch with the programming and try for a direct link first.

I always refer to this very old guide that I received a few ago.

This procedure lets you change the PABX IP addresses without Warm or Cold starting the PABX.

If there is a Callpilot, Symposium, Tapi server etc this will cause an
Outage of these devices and keep in mind if your changing the IP well
They need to know also. So its much more involved than just this!

Neil Teo 30/5/2003

This example is from an 11C system on 25.30


>ld 117
OAM000

MEM AVAIL: (U/P): 1038524 USED U P: 233655 104076 TOT: 1376255
DISK RECS AVAIL: 401
SURVIVABILITY AVAIL: 0 USED: 0 TOT: 0
=> new host DARWIN_11C 10.42.38.4
INET Data Added

=> pr host

Cabinet # 0
ID Hostname IP Address
1 PRIMARY_ENET 137.135.128.253
2 SECONDARY_ENET 137.135.128.254
3 LOCAL_PPP_IF 137.135.192.4
4 MERIDIAN1 10.42.38.130
5 DARWIN_11C 10.42.38.4
No database file exists for cab#1
No database file exists for cab#2
No database file exists for cab#3
No database file exists for cab#4
OK

=> stat host
*** Active Internet Host Table ***
ID Hostname IP Address
-- localhost 127.0.0.1
1 PRIMARY_ENET 137.135.128.253
2 SECONDARY_ENET 137.135.128.254
3 LOCAL_PPP_IF 137.135.192.4
4 MERIDIAN1 10.42.38.130

=> enl host 5
HOST: "DARWIN_11C" "10.42.38.4" enabled
OK

=> chg elnk active DARWIN_11C
INET Database updated

=> prt elnk
ACTIVE ETHERNET: "DARWIN_11C" "10.42.38.4"
INACTIVE ETHERNET: "SECONDARY_ENET" "137.135.128.254"
OK

=> chg mask 255.255.255.128
INET Data Changed

=> prt mask
SUBNET MASK: "255.255.255.128"
OK

=> pr ro
Cabinet # 0
Route entry(ies) not found.
No database file exists for cab#1
No database file exists for cab#2
No database file exists for cab#3
No database file exists for cab#4
OK

=> stat ro
*** Active Internet Routing Table ***
ID Destination Gateway Port
-- 137.135.128.128 137.135.128.253 0 [qu0]
-- 127.0.0.1 127.0.0.1 -- [lo0]

=> ****
OVL000
>ld 137
CIOD000
.stat elnk

ELNK ENABLED
Ethernet (qu unit number 0):
Host: PRIMARY_ENET
Internet address: 137.135.128.253
Broadcast address: 137.135.128.255
Ethernet address: 00:00:75:45:f8:fd
Netmask: 0xffff0000; Subnetmask: 0xffffff80
0 packets received; 8 packets sent
0 input errors; 8 output errors
0 collisions
.dis elnk

OK
.****
>
OVL000
>ld 48
LNK000
.stat elan

SERVER TASK: DISABLED

.dis elan test
OK
.
TIM000 17:43 29/5/2003 CPU 0

BUG480
BUG480 + 1066E05C 1067B7A0 1093DC2C 115B0A3E 115B0780
BUG480 + 115ACA36 115A9704 115A735C 10959A58 10958878
BUG480 + 1095812A 109565A6 10953A0A 10E3FFC2 10E3F2A8
BUG480 + 10E3EF50
.enl elan
OK
.
BUG480
BUG480 + 1066E05C 1067B7A0 1093DC2C 115B082A 115B0780
BUG480 + 115ACD36 115A9704 115A735C 10959A58 10958878
BUG480 + 1095812A 109565A6 10953A0A 10E3FFC2 10E3F2A8
BUG480 + 10E3EF50

ELAN020 ELAN Server enabled by LD 48
.stat elan

SERVER TASK: DISABLED

.*
.*
.*
.*
OVL000
>ld 137
CIOD000
.enl elnk
Initialize Network Interface.
Network Interface is up.
Host : DARWIN_11C
IP Address : 10.42.38.4
Sub-netmask : 255.255.255.128
OK
.****
>ld 117
OAM000

MEM AVAIL: (U/P): 1038524 USED U P: 233655 104076 TOT: 1376255
DISK RECS AVAIL: 401
SURVIVABILITY AVAIL: 0 USED: 0 TOT: 0
=> ping 10.42.38.1

PING 10.42.38.1 SUCCESSFUL

=> ping 10.42.112.95

PING 10.42.112.95 FAILED

=> new route 10.42.112.95 10.42.38.1 Basically how is the OTM IP reached, by going to gateway at 10.42.38.1
INET Data Added

=> pr ro
Cabinet # 0
ID Destination Gateway Port
2 10.42.112.95 10.42.38.1 0
No database file exists for cab#1
No database file exists for cab#2
No database file exists for cab#3
No database file exists for cab#4
OK

=> enl ro 2 Where “2” is the ID no obtained when printing it above.
ROUTE: "10.42.112.95" "10.42.38.1" enabled
OK

=> st ro
*** Active Internet Routing Table ***
ID Destination Gateway Port
-- 0.0.0.0 10.42.38.1 0 [qu0]
-- 10.42.38.0 10.42.38.4 0 [qu0]
-- 10.42.0.0 10.42.38.1 0 [qu0]
-- 10.42.112.0 10.42.38.1 0 [qu0]
-- 127.0.0.1 127.0.0.1 -- [lo0]
2 10.42.112.95 10.42.38.1 0 [qu0]

=> ping 10.42.112.95

PING 10.42.112.95 SUCCESSFUL ? Woo Hoo!

=>

To tidy things up at the end do a
=> update dbs
This renumbers the Ids to make it pretty basically.


OVL000
>ld 43
EDD000


.ddd

DB SEQ NUM = 210
CONFIG
PHYSICAL MAP
BCS TEMPLATE
PBX TEMPLATE
CUST
ACUST
CLID
ROUTE
DAPC
LTN TN
LTN LNK
TN
SCL


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!.

 

[ChrisKnerr2010]

Thanks firebird... It might take me a while to check on this but i will get back with you and let you know

 

[ChrisKnerr2010]

Here is what I get when I do a stat host in 117:

=> STAT HOST
*** Active Internet Host Table ***
ID Hostname IP Address
-- localhost 127.0.0.1

it appears that the route info has been lost. Im gonna have to work on this one.

 

[ChrisKnerr2010]

OK... might need some help on this one, every time i try to add a host i receive an update failed message.

 

[Firebird Scrambler]

I've seen this before when a restore is done via a PCMCIA card. The IP info is lost!. I always use a XBK file to restore with.

Have you tried using a different name?.

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!.

 

[ChrisKnerr2010]

no i havent tried a different name maybe il try that here in a little while

 

[ChrisKnerr2010]

is there any way to resore that information? say from ld 43?

 

[Firebird Scrambler]

Only via an XBK backup in LD 143. But it would probably mean that you would lose any changes done since then assuming that you have a backup.

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!.

 

[ChrisKnerr2010]

OK tried various different names to create "hosts" again and nothing worked, opened up the book and read in order to add a host it must be present in the host table... is this the route table that they are talking about? or is it another area that I need to look at!

 

[ChrisKnerr2010]

Looking at similar posts I think that this may be either a corrupt database or an SSC card error... In either case majority of the other posts had to rely on vendor assistance in this manner. Any other suggestions before I go this route?

 

[Firebird Scrambler]

Send me a recent backup copy and I can load it in on my test system.
It's one way to find out if you have a corrupted database?.

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!.

 

[marcuspb]

There may also be an old backup on the OTM server if you ever did backups on OTM.

 

[ChrisKnerr2010]

how would I pull this out of the 11? would i have to be on site or can I do it remotely?

 

[Firebird Scrambler]

Here is my backup guide below. As you have a 11c system, refer to the last 2 parts.

MERIDIAN OPTION 11 & 11E SYSTEMS
INFORMATION ON HOW TO PROVIDE A BACKUP OF THE CUSTOMER DATABASE

This information is to be used by any Meridian engineer who has access to a PC with a communications package such as... "Windows Terminal" or "ProComm +" etc. It could be used by a Customer, But they would have to have version 19 software or above, this is because they may only have access to TTY terminals 1 & 2.

It is very easy to do a backup, either onto a hardisk or onto a floppy disk. This is quite handy if you are doing a Software upgrade from version 16.90 to 20/21 etc... Or as an on site backup copy if you are a maintenance engineer.

The first thing to do is to connect up to TTY "0" and change the baud rate to "9600"

(This will speed it up to about 1 minute)

Remember TTY "0" can only be used on pre V19 software only! From V16.90! Logon to the system as normal & go into "LD 22", it Is also a good practice to print & record the following details..

REQ ISS --- prints out the software version
REQ ISSP -- prints patching info as well on post V19 software
REQ TID --- prints the cartridge i d
REQ SLT --- this prints out the Sys key codes, Agents Mopt etc...
(This is most important because the key codes could be different to what is written on the cartridge ie... more Agents! etc)

Once you have obtained this information type "****" & go into "LD 43". do a "EDD" & save system info to score & cartridge. When this has finished type "XBK" the system will reply with...
"info:" all you need to do is to type using the keyboard the following example.. "Database backup from site V18.40h name date"
& then hit c/r twice.. The system will reply with "r>" & will now be waiting for your PC to receive the data.
(You will have about 2 minutes to get things moving!).

If you are using "windows terminal" then click on box marked "transfers" & then onto line "receive binary file" you will then be asked to specify a path & file name e.g... a:\opt11e.bkp.
hit c/r or "ok" & the backup should start. if this is successful, Then the system will give out a "ok" prompt at the end.

To verify the information on the disk with what is on the system, then type in LD 43 "XVR" the system will reply with "r>" & will start incrementing with "cccc"... for about 1 minute
until timeout.
(Don't hang about!)

Click on box marked "transfers" & then onto line "send binary file". select the same file that you did the backup on & hit c/r or "ok" & the verify should start. you will receive a "ok" prompt when it has finished.

If you are using "DOS Procomm +" then go to page 3 for help.
P.S when you have finished don't forget to change the baud rate switch's back on the CPU to
1200,2400 or 9600 etc!

MERIDIAN OPTION 11 & 11E SYSTEMS
INFORMATION ON PROVIDING A RELOAD OF THE SYSTEM CONFIGURATION


Please read this sheet first before attempting a reload!

This information is to be used by any Meridian engineer who has access to a pc with a communications package such as... "Windows Terminal" or "Procomm + etc". It should never ever be used by a customer because they could easily damage the Option 11 CPU cartridge.

It is very easy to do a reload, either from a hardisk or from a floppy disk. this is quite handy if you are restoring a Customers database after a major system failure, or if a upgrade has gone horribly wrong!. (and believe me it has happened!)

the first thing to do is to connect up to TTY "0" and change the baud rate to "9600"

( This speeds things up quite a lot, But don’t use 19200! ).

Remember TTY "0" can only be used on pre V19 software only!

Logon to the system as normal & go into "LD 43" then type "XRT"
the system will reply with... "wait -- 2 minutes"

(please be aware that the CPU is erasing the "Score" clean & it only takes 45 seconds on version 19 software to do this!)

The system will then reply with "r>" & it will start to increment with "cccc"... for about 2 minutes until timeout.( Please don't hang about! ) & click on box marked "transfers" in "windows terminal" & then onto line "send binary file". Select the file that you did the last backup to & hit c/r
or "ok" & the restore should start. You will receive a "ok" prompt when it has finished
(You should see a progress chart on the screen!)

If you are using "Procomm +" then the procedure is similar by using the "page up" key or file send box (key alt-z for lists)

To verify the information on the system matches with what is on the disk, then type in LD 43 "XVR". The system will reply with "r>" & will start incrementing with "cccc"... for about 2 minutes
until timeout.(don't hang about!) click on box marked "transfers" & then onto line "send binary file".
Select the same file that you used for "XRT" & hit c/r or "ok" & the verify will start.
You will receive a "ok" prompt when it has finished.

If for any reason you cannot get the database to load into the "Score" Then you must do a "EDD" so that the "Score" & "Cartridge" becomes the same level again.

If this is successful, then type in "UPS DP". This will dump the system patches on sys load & changed the cartridge to a "Prep" state.

When this has been completed i.e. "Database backup complete" You can now do a full mains system reset. this will force the CPU to load up the customers database from the "Score".

Note! ( Type “XSL” followed by “Y” & password “OHNO” to reboot) “Nortel’s sense of humour!”
When the system has powered up, Logon go into LD 43 & try & do a "EDD" or "EDD CLR". You might will get a "EDD 112" appear, which means a security check failure / invalid Cartridge.
If this happens then you will have to change the key codes.





Assuming that you had recorded the info in LD 22 "SLT", Then go into LD 97 & type the following...
REQ "CHG"
TYPE "SYSP"
hit c/r until "ISM"
Hit c/r & enter in all the fields that have changed i.e.. Agents, Ast, Mopt etc followed by the 3 key codes.
You will get the "REQ" prompt if it's ok.

The final steps are to set the time & date & to do a "EDD" to bring the cartridge & Score to the same level.

P.S When you have finished don't forget to change the baud rate back to the original setting
(1200,2400 or 9600 etc) if you were using the race line port TTY 0!.

Useful Tips

It is not necessary to use the "XVR" command when doing a backup or restore. However since you are on site & probably using the race line TTY 0 port, Then for the extra time of about 3 minutes it's still a good idea to carry it out.

It is possible to do a Auto Data Conversion using a 18.40h backup file onto a version 19.19/21.19 Cartridge & also to do using a 19.19 backup file onto a version 21.19 Cartridge, by using the "XRT" method explained as above.

Also when using the "XRT" & "UPS DP" commands the operation of the system is not affected until you do a system power reset.

Additional Information when using "DOS" Procomm + Version

When using the "XBK" command to do a backup in Procomm, & you have hit c/r after inputting "info:...", Then press the "page down" button. The screen will display "download protocols".
You then key "X" for xmodem . The display will now have changed to "receive xmodem" & is now waiting for you to enter a file name such as e.g.. a:\opt11e.bkp. Now hit c/r & your P.C will start to
receive the data.
Using the "XRT" command is very similar but you have to key the "page up" button instead, followed by "xmodem" & then the file name + c/r.

(If you are using a old.laptop M5000 type P.C. Then you have to press the "FN" button & "page up / page down" button together to get it to work!)



MERIDIAN OPTION 11c SYSTEMS V22 ONWARDS
INFORMATION ON HOW TO PROVIDE A BACKUP OF THE CUSTOMER DATABASE

This information is to be used by any Meridian engineer who has access to a P.C. with a communications package such as... "Windows Terminal" or "Procomm +". It can also be used by a
Customer, This is because they may have access to TTY terminals 1 & 2.
(A TTY port provided on a expansion cabinet can also be used!)

It is very easy to do a backup, Either onto a hardisk or onto a floppy disk. This is quite handy if you are doing a Software Upgrade from version 22 upwards etc... Or as an on site backup copy if you are a maintenance engineer.

The first thing to do is to connect up to TTY "0" and change the baud rate to "9600 or 19200"

(This speeds things up quite a lot!).

Logon to the system as normal & go into "LD 22", It is also a good practice to print & record the following details...
REQ issp -- prints out the software version & patching info
REQ tid --- prints the site & System Dongle i d
REQ slt --- this prints out the Sys key codes, Agents Mopt etc...
(This is most important because the key codes could be different to what is written on the flash ROM s/w Daughter Board ie... more Agents! etc)

Once you have obtained this information type "****" & go into "LD 43". do a "EDD" & save system info to SSC & flash ROM. When this has finished exit LD 43 & go into LD 143 & type "XBK"
the system will reply with...
"info:" All you need to do is to type using the keyboard the following example.. "Database backup from siteV22.16h name date" & then hit c/r twice.. The system will reply with "r>" & will now be waiting for your P.C. to receive the data.

(You will have about 1 minute to get things moving!).

If you are using "Windows Terminal" Then click on box marked "transfers" & then onto line "receive binary file". You will then be asked to specify a path & file name e.g... a:\opt11c.bkp.
Hit c/r or "ok" & the backup should start. If this is successful, Then the system will give out a "ok" prompt at the end.

To verify the information on the disk with what is on the system, Then type in LD 143 "XVR" The system will reply with "r>" & will start incrementing with "cccc"... for about 1 minute until timeout. (Don't hang about!). Click on box marked "transfers" & then onto line "send binary file". Select the same file that you did the backup on & hit c/r or "ok" & the verify should start.
You will receive a "ok" prompt when it has finished.

If you are using "DOS Procomm +" Then go to page 6 for help.
P.S When you have finished, Don't forget to change the baud rate switch's back on the CPU to

1200 or 2400!


MERIDIAN OPTION 11c SYSTEMS V22 ONWARDS
INFORMATION ON PROVIDING A RELOAD OF THE SYSTEM CONFIGURATION


Please read this sheet first before attempting a reload!


This information is to be used by any Meridian engineer who has access to a P.C. with a comunications package such as... "Windows Terminal" or "Procomm +". It should never ever be used
by a Customer because they could easily damage the CPU.

It is very easy to do a reload, either from a hardisk or from a floppy disk. this is quite handy if you are restoring a Customers database after a major system failure, Or if a upgrade has gone horribly wrong!. (And believe me it has happened!) But please refer to a separate information sheet on this.

The first thing to do is to connect up to TTY "0" and change the baud rate to "9600 or 19200"

(This does speed things up a lot!).
Other TTY's can be used but it might take a bit longer to do!

Logon to the system as normal & go into "LD 143" then type "XRT" The system will reply with... "wait -- 2 minutes"

(Please note that the CPU is erasing the "SSC" clean & it only takes a few seconds on version 22 software to do this!)

The system will then reply with "r>" & it will start to increment with "cccc"... for about 2 minutes until timeout (Please don't hang about!). Click on box marked "transfers" in "Windows Terminal" & then onto line "send binary file". Select the file that you did the last backup to & hit c/r or "ok" & the restore should start. You will receive a "ok" prompt when it has finished. (You should see a progress chart on the screen!)

If you are using "Procomm +" Then the procedure is similar by using the "page up" key or file send box (key alt-z for lists).

Note!
You must verify that the information on the system matches with what is on the disk, you must type in LD 143 "XVR" the system will reply with "r>" & will start incrementing with "cccc"... for about 2 minutes until timeout.
(Don't hang about!)

Click on box marked "transfers" & then onto line "Send binary file". Select the same file that you used for "XRT" & hit c/r or "ok" & the verify should start. You will receive a "ok" prompt when it has finished.
If for any reason you cannot get the database to load into the "SSC" then you must do a "EDD" in LD 43 so that the "SSC" & "flash ROM s/w Daughter board" is at the same level again.

If all is well then type
"upgrade" followed by
"3. utilities" &
then "1. restore backed up database".
key "1. backup flash drive"
key "y" to copy the backup file from the "z" CPU drive into the "c"
You can now do a full mains system reset. This will force the CPU
to load up the customers database from the "SSC"
Note! (Type “XSL” followed by “Y” & password “OHNO” to reboot the Option 11c)
When the system has powered up, Logon go into LD 43 & try & do a "EDD" or "EDD CLR". You might will get a "EDD 112" appear which means a security check failure / invalid flash ROM s/w.
If this happens then you will have to change the keycodes.
Assuming that you had recorded the info in LD 22 "SLT", Then go into LD 143 & type the following...
"upgrade"
key "2. system upgrade"
Then key "3. option 11c feature / parameter upgrade"
Enter the prompts as required in the fields given i.e.. Agents, Ast, Mopt etc followed by the 3 key codes.
You will get the "keycodes successful & key "y" for reboot" prompt if it's ok.

The final steps are to reboot the system & set the time & date & to do a "EDD" to bring the system Daughterboard & Score to the same level.

P.S when you have finished don't forget to change the baud rate back to the original setting (1200, 2400 or 9600 etc) if you were using the race line port TTY 0!.

Useful Tips

It is not necessary to use the "XVR" command when doing a backup or restore. However since you are on site & probably using the TTY “0” port, Then for the extra time of about 1 minute it's still a good idea to carry it out.

It is possible to do an auto data conversion using a 18.40h, 20.19 or a 21.19 backup file onto a version 22.16 system, but you need to go through the "upgrade" process in LD 143.

Additional information when using "DOS" Procomm +

When using the "XBK" command to do a backup in Procomm, & you have hit c/r after imputing "info:.", Then press the "page down" button. The screen will display "download protocols".
You then key "X" for xmodem . The display will now have changed to "receive xmodem" & is now waiting for you to enter a file name, such as e.g.. a:\opt11c.bkp. Now hit c/r & your P.C will start to
receive the data.
Using the "XRT" command is very similar but you have to key the "page up" button instead, followed by "xmodem" & then the file name + c/r.

(If you are using an old.laptop M5000 type P.C. Then you have to press the "FN" button & "page up / page down" button together to get it to work!)


Documentation by
David Bromley issue 12


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!.

 

[marcuspb]

If you ever had DBA sessions setup there was an option to do a backup of the system and also a restore option, this would be on the OTM server.
This is different than a OTM backup of sites and systems, which is handy for the server but not very useful for the PBX.
Look under utilities (same area as you would find the scheduler) and see if data buffering is there and more importantly if you can open it up. If it opens, or is already open, you can highlight a system and use the database disaster recovery function to do a restore.
But if you can't get to the systems through the elan, I'm not sure if you can make this work.

 

[ChrisKnerr2010]

This just in on this... It is confirmed that I have corrupted databases. The strange part is now it is a total of 4 sites! Every single one of them is corrupted! I cannot access any type of ld 43 info, cant even do an edd... I only have a few strands of hair left !!!! I was instructed to get with our vendor of record so they can open up a TAC case with Nortel themselves.

 

[marcuspb]

As a last resort, personally I would out the tty's for OTM on one of the systems and see if it will free up what ever has the system stuck.
It sounds like something was/is on the ELAN and may have filled up a buffer somewhere.

 

[ChrisKnerr2010]

There are no TTY's to out. its like everything is lost and it wont let me rebuild anything for the elans