BCM 400 3.7 MSC Sys Test Log EVENT 680? 1

[v2d2v]

BCM 3.7 redundant, with all the latest patches.
Any of you gurus know what EVENT 680 is?

 

[Thraxis77]

Did you ever find an answer to this? I'm encountering this now and wondering the same thing...

 

[v2d2v]

No I never did find out what that event was. I have a hunch it has somthing to do with IP trunking or Gateway

 

[fireeater]

found this in some old docs of mine but not sure if it is relevant to the bcm or the mics

680: UTAMdsblReason 'E' TestLog
680: | CAUSE:
680: | This is an informational LOG EVENT generated when the Wireless
680: | System is DISABLED by the UTAM feature functionality. The Log Event
680: | is used to indicate the REASON that UTAM has DISABLED the system.
680: | ENVIRONMENT:
680: | This log event occurs in all wireless products that include the UTAM
680: | System Disablement feature functionality. It is logged in the
680: | FAULTS file with the following parameter indications:
680: | Parm 1 - Reason that UTAM has DISABLED the Wireless System.
680: | 1 COLD/WARM START - System has never been previously enabled.
680: | Parm 2 - N/A
680: | Parm 3 - N/A
680: | 2 WARM START - System was previously enabled - UTAM codes
680: | have been applied, BUT additional codes are
680: | still required to bring up the TOTAL number
680: | past the previous THRESHOLD. This scenario
680: | occurs when a MEMORY RESET (**STARTUP) or a
680: | BACKUP & RESTORE is initiated.
680: | Parm 2 - Total number of UTAM Codes previously entered.
680: | Parm 3 - Total number of UTAM Codes required to enable the system.
680: | 3 WARM START - System was geographically moved or the
680: | base station TCM ports configuration has
680: | been modified.
680: | Parm 2 - Total number of PRIMARY signature vectors.
680: | Parm 3 - Total number of failed signature vectors.
680: | 4 WARM START - The UTAM Disablement Test was NOT actually
680: | executed, due to an incomplete configuration.
680: | Note that, this scenario can occur if too many
680: | base stations do not reboot, after a power
680: | failure, due to an RPI unit failure.
680: | Parm 2 - Total number of PRIMARY signature vectors.
680: | Parm 3 - Minimum number of PRIMARY Signature Vectors required.
680: | 5 WARM START - There are INSUFFICIENT RADIO CREDITS available.
680: | Parm 2 - Total number of Radio Credits in the system.
680: | Parm 3 - Total number of Radio Credits REQUIRED, at the time
680: | that the Log Event was generated.
680: | 6 WARM START - System was geographically moved or the
680: | device (NORSTAR SET or base station) TCM ports
680: | configuration has been modified.
680: | Parm 2 - Total number of devices that form the Device Mapping
680: | Signature. 680: | Parm 3 - Total number of devices that failed (mismatched) the
680: | Device Mapping Signatu
680: | 7. WARM START - The UTAM disablement test that is based on the
680: | Device To Port Mapping Signature, was NOT actually
680: | executed, due to an incomplete configuration. Note
680: | that this scenario can occur if too many devices do
680: | not reboot, after a power failure.
680: | Parm 2 - Total number of devices that were actually detected and
680: | that are part of the captured Device to Port Mapping
680: | Signature.
680: | Parm 3 - Minimum number of devices required to execute the Disablement
680: | Test.
680: | HUMAN ACTION:
680: | The following actions are recommended to recover from a DISABLED
680: | system scenario, based on the parameter indications:
680: | 1 COLD/WARM START - UTAM Activation Code is required.
680: | Sufficient Radio Credits must be included
680: | in the UTAM code.
680: | 2 WARM START - After entering all the previously obtained
680: | UTAM Activation Codes and UTAM Recovery Codes,
680: | obtain ONE additional UTAM Recovery Code. The
680: | additional Recovery Code should contain ZERO
680: | Radio Credits.
680: | 3 WARM START - UTAM Recovery Code is required. There should be
680: | ZERO Radio Credits included in a UTAM Recovery
680: | Code.
680: | 4 WARM START - The system DISABLEMENT was caused by a faulty
680: | configuration. Correcting the configuration and
680: | restarting the system will clear the DISABLEMENT
680: | condition. Alternatively, entering a UTAM
680: | Recovery Code with ZERO Radio Credits, will also
680: | clear the system DISABLEMENT condition. However,
680: | it is possible that the existing configuration
680: | may not be supported by the UTAM minimum system
680: | requirements, which may cause another DISABLEMENT
680: | on a subsequent restart.
680: | 5 WARM START - Obtain a UTAM Activation Code with the additional
680: | Radio Credits required for the number of new
680: | base stations added to the system. Alternatively,
680: | dis-connect the base stations that caused the
680: | Radio Credits to be exceeded and restart the system.
680: | 6. WARM START - UTAM Recovery Code is required. There should be
680: | ZERO Radio Credits included in a UTAM Recovery
680: | Code. Note that, if the DISABLEMENT was caused
680: | by a malfunctioning device (NORSTAR SET or basestation),
680: | then the device will have to be replaced and a
680: | UTAM Recovery Code will still be required.
680: | 7. WARM START - The system DISABLEMENT was caused by a faulty device
680: | configuration. Whenever the system is disabled due to
680: | a faulty or incorrect Device to Port Mapping configuration,
680: | the system will require a UTAM Recovery Code, in order to
680: | ENABLE the wireless operation.

HALLOWED ARE THE ORI

mike

http://www.ics-on.ca

 

[Thraxis77]

Well, this does make some sense in my case. Right after our system rebooted itself is when the evt occured. Looks like I can safely ignore this as we don't use the wireless channels anyway....

Thanks!