Minor Alarm

[ttrumble111]

Ralph,

I get the plid 6-1-1-6 would be "Cabinet 6 - Shelf 1 - Slot 1 - Circuit 6", and I can physically see it, but what about the others "cabinets 1, 4, & 7" or "shelfs 3 & 1" or "Slots 32, 10, 11, 6, & 2" - whats that all about?

1             3         32     ViperAA IP     Controller
1             1         10     MCSTHA         ICP Comms
1             1         11     MC266AA       Communications Processor
4             1          6      MCASUAA       ASU
7             1          2      MC270A         Universal T1

I pieced together the information above from the log when I rebooted the 3300 last Friday. I am just trying to better understand the layout of the 3300 better so if something fails or is in an alarm state I can better troubleshoot it.

One other question. I know I can plug and unplug the Ethernet Port, FIM TX & RX, and the T1 connectors while its running without adversely affecting the 3300 - I think??? PLEASE tell me if I am wrong so that I don't fry the 3300, but what about the RJ21/Amphenol/50 Pin telco connector on the back? Can I unplug and plug the Amphenol connector while its running without hosing the 3300?

- Tom

[v2win]

Cabinet 1 is the 3300 itself the cards in cabinet 1 are virtual. Cabinet 4 is your embedded ASU and Cabinet 7 is your T1 module.

Yes you can unplug all the connections including the 50 pin amp cable without hurting anything. You will lose service on those but that is implied.

[ttrumble111]

Thanks go to Ralph & v2win.

My backup Mitel system cutover went great Tuesday night @ 10PM.

Your answers to my questions have greatly assisted me on this project and I thank you.

Beers all around!

- Tom

[ttrumble111]

Oops I forgot to ask.

When Ralph suggested 'set thres lines 9 20 100' I did that but on a subsequent reboot it went back to "0 20 100". How do you save that threshold config to the firmware or configuration file so that on the next reboot I don't have to reset it again.

- Tom

[ralph]

That should have stayed.   That command is supposed to survive a reboot.

Not sure what's happening here.

Ralph

[MitelMania]

if you did a database restore the thresholds are lost..  I saw something about a backup and what not in the thread..  if you upgraded or did any kind of DB restore it will erase the alarm thresholds set by the set thresh commands..
-Christopher

[ttrumble111]

Thank you Christopher,

During the March Reboot of my 3300 backup, that is currently in production, I will check the threshold and see if it goes back to the default.

- Tom

[ttrumble111]

Before I reboot my "Backup" 3300, thanks to Ralph, Christopher, & v2win, from the Shell and check that the "thres lines 9 20 100" remained I would like to ask a couple of questions:

• Can I issue a command from the ESM similar to the appShutdown from the Shell and then <SPACE><SPACE><SPACE> for a simple reboot?
• I have been rebooting the Mitel 3300 once a month manually with the "appShutdown" command for the past 4 months and it seems that the reboots have kept the system running better than ever. Is this a good practice to continue? If so, what would be the command to schedule it for 0300 hours on the 1st of every month so that I don't have to babysit?
  

- Tom

[ralph]

I generally set up to reboot weekly so my command I use is "Program Reboot Sched Friday 2:15"

The following is right from the help files:


PROGRAMMED REBOOT
Qualifiers:
COURTESY ON

COURTESY OFF

DISPLAY

RESOURCE RECOVERY ON

RESOURCE RECOVERY OFF

RESOURCE RECOVERY <hh:mm:ss>

SCHEDULE ON

SCHEDULE OFF

SCHEDULE DAILY <hh:mm:ss>

SCHEDULE <day-of-week> <hh:mm:ss>

SCHEDULE MONTHLY <week # [1-4]> <day-of-week> <hh:mm:ss>

SCHEDULE INTERVAL <interval in weeks [1-52]> <MMM> <day-of-month> <hh:mm:ss>

•Note: The default values are:
PROGRAMMED REBOOT SCHEDULE IS OFF
PROGRAMMED REBOOT SCHEDULED: DAILY 02:15:00
PROGRAMMED REBOOT RESOURCE RECOVERY IS ON
PROGRAMMED REBOOT RESOURCE: RECOVERY 02:15:00
PROGRAMMED REBOOT COURTESY IS OFF