Realitis DX, Fault Status 1

[keptinthedark]

I need to perform a dilapidation report on a Realitis DX. It needs to move about 5m in a CER but 5m is 5m. I will need to shut it down, unplug and move it. Pull the cables back from existing location to new location in new CMS. At the moment the unit has the Minor Fault Light and the Major Fault light illuminated. For the purposes of the dilapidation I need to log on, see what the errors are pre and post move and prove to the client that we haven't introduced any.

From trawling, it appears I use a serial cable to the port on the back of the unit and use hyperterminal, telnet or similar.

Does the serial cable just need to be a straight through or does i have to be Null Modem?

Will I need a username and password to connect?

What commands would I need to use to generate a list of the minor and major faults on the system?

What commands if this option is available would be needed to backup the config if that is an advisable step, would I need a version of the Siemens software to amke this happen?

Thanks in advance,

Matt.

 

[happymal]

Matt,
From your thread its sounds as if you are new to the iSDX/Realitis.
Who is your maintainer? It would be advisable to get them in to take software backups and advise you of any possable hicups in your idea's.... even if there is a possable Time Related Charge for this.
Moving a Realitis or any PABX is not as easy as some people think, if it does not come back after your move what are you going to do? Getting the maintainer in after the event could cost you a lot.

 

[pablo100]

In reply to the points raised in your post, it looks as though your going to have to log in to the sytem and capture the contents of the hardware error table before you do anything else. I personnally would attempt to address/identify the causes of the visual indications of errors that you mention before moving the system.

To log in you will have to locate what is known a the 'V.24 box'. This is usually wall mounted in the vicinity of the DX and is the same size and shape as a double domestic mains power outlet but with 3 DB25 male 'D' type connectors on it.

Once located you can connect to port 2 on the 'V.24' to the serial port on a computer using a 'normal' 9 pin to 25 pin RS232 lead. If using a laptop you will need to be running a suitable terminal emulation software package ( e.g. Hyperterminal on Microsoft Windows ) set for 9600 baud, 8 stop bits, no parity and 1 stop bit.

On succesful connections to the dx you will be presentd with the 'software header' and a prompt for 'OSL please' - This is the login password and you will have to obtain this from you maintainer.

If you get this far post again and i may be able to help you further

Happymal is correct in saying that moving this gear is no piece of cake, have you checked that there is enough 'slack' in the yellow extension cable to enable you to move the system 5 metres? In my experience on a Realitis DX the cables are cut to required length and cable tied-in with very little spare to allow for movement. If you do not have enough slack cable you are looking at re-cabling and re-wiring the entire switch - not a job to be entered into with out your maintainer's ( and one or two engineer's)assistance.

 

[keptinthedark]

Thanks Pablo100 and happymal. I understand the dangers as I move and reconfigure some interesting comms systems and understand the risks, especially on existing standing installations some years old as this one is, and as for a maintainer..... a whoooo???

The unit is moveable. The unit is moving toward the MDF that the bulk of the cabling is punched down on and we will have to run in 2 x new coax for the Tx Rx link that then runs off in fibre to down the ways as that goes the other direction to the multicores.

I've found the V.24 port under the floor a bit smashed up, will hopefully get back there early next week to have a quick check and see if I can get the emulator connected in the least and then try and move from there. I need to check if it's battery backed, from my cursory check last time I didn't see a battery in it. If it loses power I assume it would hold it's config as the environment it is in isn't to pleaseant and that sort of thing happens on the odd occasion.

Thanks for your help thus far.

 

[pablo100]

After you have logged in you will be able to tell what software level the dx is running, this will be helpful in that it will tell me whether the system is using floppy disk/winchester autoloader or simm memory for software storage. Whatever the storage medium the system should be programmed to perform an 'autodump'( data save ) in the wee small hours of every day following any changes to the configuration database ( if any ).

As regards battery back up, how this is achieved will depend on whether the the system is AC or DC power. To find out on a Realitis DX, remove the lowest of the front access panels ( the narrowest ) and check how many red circuit breaker switches are present - one breaker indicates that is is AC, ant two tells you that it is DC.

AC systems are normally hard wired into a fused mains spur, or, connected to a third part UPS.

DC systems are connected to a dedicated RDX power cab containing the batteries and rectifiers.

 

[keptinthedark]

Hiya, well after a delay I finally got back there and hooked in. Got to OSL prompt as you explained. Obviously need some guidance from there. How do I test if a username and or password has been set and or changed from default? I type OSL and it prompted for User, Level etc. which I typed in 1 each time for and then it got to Key: and couldn't get any further than this. No battery backup, hardwired to DB. Turned it off the oher week as a belt and braces test and it came back to life, so hey all good really. I have pretty deep suspicions that this unit is however doing a whole lot of nothing which will be determined when I do the detailed Delp next week for the attached systems.

Thanks again for your help.

 

[dgcm]

You can sometimes work out the OSL from the header data you get at that first screen.

For example

Unpublished Work. Copyright Siemens plc.
All rights reserved.
DX DXPLF6518 30228.01 01.033
9.0.071 /01DUK 0001000 UK 14 28/11/08

You'd been to put the level first. You will know about them but lets assume customer level of 14, try user 00 then use the head data above.

The example above gives me a user level OSL of:

14 00 1465 182008 This uses the numbers in the header after DXPFL and the 2008 is from the last date shown.

I'm sure I haven't explained it very well, but I'm sure someone else will do better - but hopefully you get the idea.

 

[keptinthedark]

Thanks for the speedy response, and yes I did get a little lost. Below is the dump from my hyperterminal session last night.

Unpublished Work. Copyright Siemens plc.
All rights reserved.
DX DSGHF5765 31765.01 01.004
6.3.001 0001000 UK 12 08/11/99 A M 150
18/06/09 02:20:28

OSL, PLEASE.
?

Any hints on deciphering that. I suppose my first concern is the date of 1999, I wonder if this thing has gone back to defaults.

 

[dgcm]

Try 14 00 1457 651999

Though I'm fairly sure that won't work (I've been trying to apply the logic the seems to generate mine to yours, but it's still at bit early in the day for the brain).

I wouldn't worry about the 1999 bit. That's just the year the system was commissoned on that software version. My OSL changed when I went from version 6.3 to Version 9, as of course that year changed, so the last 4 digits of the OSL changes from 2000 to 2008 (very confusing when you've been tapping away the same string for nearly 9 years and then it changes).

Some guys just seem to know how to work it out (assuming a previous mantainer hasn't changed it), the above is only for the user level access (I'm not allowed anything more dangerous) but a similar principle applies for higher levels.

The format for entry can be all done on one line when entering:

osl (space) 14 (space) 00 (space) 65 (space) 182000

Or instead of pressing space you can press enter after each segment (it might help work out which bit is wrong).

Hopefully someone that know's more than I do will read this and give you a proper response

 

[keptinthedark]

Thanks for that. I will give it a try Sun night when I am back on site.

What I really need following that, and assuming you can do this from user level access, I want to see what errors/faults are present on the system as the Major and Minor Fault lights are lit and I'd like to know what they are supposedly.

All help greatly appreciated.

 

[dgcm]

I've got a zipped copy of the electronic command manual for 6.3 if it's any use to you.

I had a quick look, but couldn't find the command you were looking for - but there are so many that seem the same !

If you want it, let me know somehow and we'll work out how to get it to you.

 

[pablo100]

input the following command:

LET A (return)

This will list off the hardware error table, capture the output and post here and we will go from there.

 

[keptinthedark]

Bad news unfortunightly. Both of the suggested logons didn't work which was a bit gutting. At a bit of a dead end I think on this one.

Not sure if anyone has any other suggestions they can chuck in the ring.

Looks like we'll be moving it with caveats. Fiil you in Wed with how the move goes.

Thanks for all your help.

 

[keptinthedark]

What a score, have found maintenance manual in an unused filing cabinet adn it appeasrs to haev a logon code.

Will try that tonight and the LET A command to see if I can generate a list of faults, it also gives me a list of numbers that supposedly react to various devices.

Fingers crossed.

 

[happymal]

Unpublished Work. Copyright Siemens plc.
All rights reserved.
DX DSGHF5765 31765.01 01.004
6.3.001 0001000 UK 12 08/11/99 A M 150
18/06/09 02:20:28

OSL, PLEASE.
?


Try osl 1 0 0157651999
or osl 2 0 0257651999
or osl 5 0 0557651999

These are all standard from the header with level, user, level-01/02/05+header(5765)+year(1999). It is no neccessary to use full user and level in the first bit ie, osl 01 00 0157651999.

or you can try a sneeky one, osl 0 5 0602259980, this was used by Siemens installers on new switches as a temp password which they were supposted to delete after installation, but many were forgot about,.

if non of these work your previous 'maintainer' may have changed them all, you can then go to Siemens for a password reset but it will cost.

 

[keptinthedark]

Well move went OK all in all, a few other dramas occured but all good. I have here the error table, would be handy if anyone could cast their eyes over it and tell me what these faulst are likely to be related to.

PRE-MOVE PABX DUMP
----------------------------------------------------
Unpublished Work. Copyright Siemens plc.
All rights reserved.
DX DSGHF5765 31765.01 01.004
6.3.001 0001000 UK 12 08/11/99 A M 150
25/06/09 03:03:50

DX DSGHF5765 31765.01 01.004
6.3.001 0001000 UK 12 08/11/99 A M 150
25/06/09 01:45:05

REFNO TYPE ADDRESS CODE DATE TIME I

00 40U CPU D00 0022 00/00/00 00:00 00

04 12N 011609 P 24/06/09 02:00 02

01 49N 0124 0002 20/06/09 04:13 00

02 49N 0124 0003 20/06/09 04:13 00

03 49N 0124 0005 20/06/09 04:13 00



DOWNED CARDS:-



DEACTIVATED EQUIPMENT:-



?



=============================================================

POST-MOVE DUMP



DX CPU Application V3.0.11

Aug 8 2002 15:27:32

Unpublished work. Copyright Siemens plc.

All Rights Reserved.





Unpublished Work. Copyright Siemens plc.

All rights reserved.

DX DSGHF5765 31765.01 01.004

6.3.001 0001000 UK 12 08/11/99 A M 150

25/06/09 03:03:50



OSL, PLEASE.

?

LEVEL:USER:KEY:

?let a

DX DSGHF5765 31765.01 01.004

6.3.001 0001000 UK 12 08/11/99 A M 150

25/06/09 03:04:33

REFNO TYPE ADDRESS CODE DATE TIME I

00 40U CPU D00 0022 00/00/00 00:00 00

01 49N 0124 0002 25/06/09 03:03 00

02 49N 0124 0003 25/06/09 03:03 00

03 49N 0124 0005 25/06/09 03:03 00



DOWNED CARDS:-



DEACTIVATED EQUIPMENT:-



?

 

[happymal]

REFNO TYPE ADDRESS CODE DATE TIME I

00 40U CPU D00 0022 00/00/00 00:00 00

04 12N 011609 P 24/06/09 02:00 02

01 49N 0124 0002 20/06/09 04:13 00

02 49N 0124 0003 20/06/09 04:13 00

03 49N 0124 0005 20/06/09 04:13 00


40 type 22 is when on reload it fails to read Network interface clients. (This is when a password is set or not set for FTP or IPnetwork clients) Type asmi (lowercase) At the SMI A> prompt type se .you should see a print out as follows Or simular.

DX SYSTEM MAINTENANCE INTERFACE
23/07/08 10:40 Firmware Version:0.206 Application Version:2.0.14 Release ACTIVE
SMI A> se
SER1=9600
SER2=1200
SER3=9600
SER4=9600
CIL=3
CUST=2
REMOTE=4
IPACT=88.0.0.1
ETHACT=00:00:32:07:61:1c
MEDETHACT=00:00:32:07:61:1d
FPGA=0.0/fpga2009.a
MUSICFILE=0.0/music02.a
DSPFILE=0.0/dsp0109.a
MODEM_STRING=ATQ1S0=1+MS=9\n\r
AUTO=0.0/xyzxx613.app
NIVAL=0.0/ni.dat

the data in the ni.dat file is what it cannot read.

Type e to exit.
Type lnic

this will give you a list of what should be in the ni.dat folder.

The type 12 011609 on post move refers to an analogue trunk that had failed its line test and then passed it (P).

The others refer to a digital link on card 0124 failing loss of AIS loss of synch and loss of multiframe (Clocking).

if records have been done you could try latx a this should give you a text string for all delta channel links.