Lineadmin.bat utility for monitoring T1 / E1 states
A MSS 2004 R2 system that used to work suddenly stopped answering today - ring no answer (RNA). I first switched the TAS front page application to the http://localhost/TAS/startpage.htm (simple page that just says, "Welcome to Microsoft Speech Server") just to make sure it was not my application but I received the same results - RNA. Next, I stopped the TIM and ran the MtcInstallValidator.exe utility I have blogged about earlier. I ran the test and it failed at the Network Interface test, and stated: "Please verify all cables are properly connected and the hardware is properly configured." Well, this box is in another state so the next tip I got from a co-worker of mine. He mentioned to try running the lineadmin utility. Here is a little information about this utility:
lineadmin.bat
Documentation location:
C:\Program Files\Dialogic\doc\pdffiles\system_admin_win_v1.pdf
Line Admin Reference Chapter 8 straight from the documentation:
"The Line Admin tool puts lines into service so you can run many of the other diagnostic utilities. The Line Admin tool like the Alarms tool, is used for sending and monitoring the alarm states on a T1 or E1 line but the Line Admin tool is recommended as a more useful tool. The Line Admin tool only applies to Intel telecom boards that use the DM3 architecture."
Options
The Line Admin tool uses the following command line options:
- -board <n>
- Board number (required). Use the List Boards tool to obtain the board number.
- -line <n>
- Line number (optional, default is 1)
- -lines {n n+ …}
- Line numbers. This parameter is used when more than 1 line is monitored (optional, default is
- {1 2 3 4})
- -advanced <n>
- The presence or absence of the following alarms on the line: AIS, CRC, and D-Channel
The following example runs the Line Admin tool on board 1, lines 1, 2, 3, and 4:
lineadmin -board 1 -lines {1 2 3 4}
My Results
For some reason I kept running this and the GUI would not run.
Looking at the inside of the batch script:
@echo off
set QS_APPDIR=%QSCRIPT_DIR%/tools/lineadmin/lineadmin.qs
qscript "%QS_APPDIR%" %*
With some help from my co-worker we noticed that it was running qscript so we killed all my rogue qscript process and then ran lineadmin again and it brought up the GUI.
From this GUI I was able to tell that the span number two that I was interested in was in a yellow alarm state. This tells me that something is not correct with the switch configuration. Now, I just have to call the switch folks and work this out!
Thanks to Blaise and Chris my co-workers for all their help.
Technorati Tags: Microsoft Speech Server