3 Channel Motorola SN system
This is a used system we purchased for testing in our LAB.
I am a n00b to Motorola SN systems so I have been on a steady learning curve.
The system was in trunking but was only allocating CH2 as a voice channel so the MCP750 was rest via the front reset button.
On the MCP750 COM1 port I see the following error during boot:
WARNING: /etc/fstab does not exist.
Is this normal?
The diagnostic output from the SMT conector is:
*DIAG* 20:33:24 5/23/07 BA 00 CSC 0E0 F 00 01
*DIAG* 20:33:24 5/23/07 BA 00 CSC 0E0 F 0E 10
*DIAG* 20:33:26 5/23/07 BA 00 CSC 0E0 F 0E 14
*DIAG* 20:33:28 5/23/07 BA 00 CSC 0E0 F 0E 15
The ACE cards reboot about every 15 seconds.
The LSB card indicates activity on serial 2 from our Gold Elite console but the LSB card never boots to a point were the ED/Sel switch can be used to disable or enable inputs.
THE System board is running the following versions:
COPYRIGHT MOTOROLA INC. 2003. ALL RIGHTS RESERVED.
VER: MTC 3600...........Software Version----------->R30.01.20
VER: LynxOS.............Software Version----------->LynxOS 3.0.1 110298-G
VER: Microprocessor.....Hardware Version----------->PowerPC
Starting up.
The ACE Cards configuration:
Site Config : SmartNet Site or SmartZone Remote
SW Revision : R_00.00.71
Bkplane Comm : Firewire
RSC Link : 4800 bps
TSC Link : 9600 bps
SN System in Failsoft
Moderator: Queue Moderator
Re: SN System in Failsoft
Don't worry about /etc/fstab, they all do that.
Your diag output returns as "Message not decoded - Contact SSC".
How many channels is the controller configured for?
ACE cards rebooting over and over like that likely indicate a configuration file mismatch or board failure. ACE2 relies on ACE1 to run the show, so start with ACE1. I simply cannot tell you how many times I've had to replace failed ACE cards. They are EXTREMELY touchy.
Do you have software for the controller? Do you have access to the SSC at Motorola?
Your diag output returns as "Message not decoded - Contact SSC".
How many channels is the controller configured for?
ACE cards rebooting over and over like that likely indicate a configuration file mismatch or board failure. ACE2 relies on ACE1 to run the show, so start with ACE1. I simply cannot tell you how many times I've had to replace failed ACE cards. They are EXTREMELY touchy.
Do you have software for the controller? Do you have access to the SSC at Motorola?
Re: SN System in Failsoft
I have code for ACE card. Is there a special cable I need to load flash to the ACE card.Since this is used equipment I did not think the SSC would provide support without some type of maintenance contract or a PO. At least that was the way it was when I worked for Mot many moons ago.
Re: SN System in Failsoft
Cable to flash the ACE is the same as the cable you use on PAM-C to monitor the controller/perform SMT functions. It's also the same cable used to monitor ACE diagnostics. Read on.
Boot controller with E/D switch on the ACE held down to put it in flash mode. Flash is performed at 57600 8-N-1. Transfer mode is ASCII.
You can also monitor the ACE diagnostics with a terminal on the ACE diag port. 9600 8-N-1. No switch holding required, this is the mode it comes up in normally when you power up.
ACE2 (if you have one) won't tell you much, ACE1 tells you everything. ACE2 looks to ACE1 for all of it's synchronization, operation, etc, however BOTH ACE cards must be at the same format (SN/SZ, CSC/PSC/ReSC) and version.
As for the SSC, f you work for an MSS/PSP, they should help you. If you're not MSS/PSP, well, I dunno.
There's literally thousands of potential causes for your problem, so this could prove interesting.
It may be dropping to failsoft because a majority of your channels are offline if the controller is configured for more than what you are using. You may need a codeplug specific to your application.
On top of that, these things *REALLY* don't like having their power cycled. Once you have it running, I suggest you LEAVE it running.
One other thing to do would be this: Log on to it and clear diags. Shut it down, then start it back up, then do a MANUAL diags, then a PRINT diags and post *ALL* of the output here, and I'll see what the crystal ball says.
Is your CPU card rebooting or appearing to reboot? Or just the ACE card(s)? How many ACE cards are in the controller? Do you have spares? What was the controllers original configuration when it was commissioned? What type of BR's are attached to it?
Boot controller with E/D switch on the ACE held down to put it in flash mode. Flash is performed at 57600 8-N-1. Transfer mode is ASCII.
You can also monitor the ACE diagnostics with a terminal on the ACE diag port. 9600 8-N-1. No switch holding required, this is the mode it comes up in normally when you power up.
ACE2 (if you have one) won't tell you much, ACE1 tells you everything. ACE2 looks to ACE1 for all of it's synchronization, operation, etc, however BOTH ACE cards must be at the same format (SN/SZ, CSC/PSC/ReSC) and version.
As for the SSC, f you work for an MSS/PSP, they should help you. If you're not MSS/PSP, well, I dunno.
There's literally thousands of potential causes for your problem, so this could prove interesting.
It may be dropping to failsoft because a majority of your channels are offline if the controller is configured for more than what you are using. You may need a codeplug specific to your application.
On top of that, these things *REALLY* don't like having their power cycled. Once you have it running, I suggest you LEAVE it running.
One other thing to do would be this: Log on to it and clear diags. Shut it down, then start it back up, then do a MANUAL diags, then a PRINT diags and post *ALL* of the output here, and I'll see what the crystal ball says.
Is your CPU card rebooting or appearing to reboot? Or just the ACE card(s)? How many ACE cards are in the controller? Do you have spares? What was the controllers original configuration when it was commissioned? What type of BR's are attached to it?