force a DSP alarm to clear

[KurpeusLondon]

Hi guys,

When we bought our mitel demo kit (Mitel reseller), that one came with a licence with IP compression enable.

I don't have the DSPs that supports IP compression and we don't intend to purchase it. As a result, my ICP CXII 3300 keeps alarming about these DSPs missing. I tried to contact Mitel to see if we could remove the IP Compression feature from our licence so that would clear down the alarm om my controller but they say they couldn't.

Some times ago, I use the command line to clear the alarm but it keeps coming back.

Have you got any other idea how I could do it ?

Thanks

 

[IrwinMFletcher]

I don't believe you can. You can set thresholds on most alarms, but not that one.

 

[Supernova99]

Can you not just simply remove the compression licence from your AMC account and the sync the system?
Mitel support can only add/remove licences if they are a Mitel Direct customer.
You will need to contact your VAR who will be able to remove it.
You will need to perform an online sync first.

Share what you know - Learn what you don't

 

[KurpeusLondon]

Well we are a Mitel direct customer. I contacted them through the AMC but they got back to me saying the demo kit comes with compression licences and they can't remove them.

 

[Supernova99]

If it is part of a 'bundle' then why haven't you been supplied with a DSP?
Sometimes the bundled licences will not allow removing individual components it depends on what was ordered.
Let me have your app record and I will see if I can remove it for you.

Share what you know - Learn what you don't

 

[IrwinMFletcher]

I can see that, demo units are most likely kept in a separate database than the traditional customer units.

Not to be rude, but the question that hasn't been answered is where is the card that came with the system?

 

[KurpeusLondon]

Hey guys,

Thanks a lot supernova for your offer, much appreciate, but I can't do that. By doing so, I would breach our ISO27001 standard.

Interresting point, I though the system is alarming because I don't have the required DSP to support IP compression but it seems that's not the issue:

On my first ICP 3300 CX II, I have one T1/E1 combo card plus a one Quad BRI. No alarm on that system

slotallinfo

Info returned by SystemDiscovery::MmcInfo():

MMC slotID : 0
moduleid : 76
driverid : 0
resetTiming : 0
pcbAssembly : 56006113
pcbRev : C.6
variant Id : 2
describ : T1E1 Resiliency-DSP-VEC-STRATUM4 MMC
country code :
procType :
coreSpeed : 0
clockSpeed : 0
pasicID : 4
controllerID : 0
IRQ levels : 2
8b Base Addr: 0x40000000
16b Base Addr: 0x50000000
32b Base Addr: 0x60000000
MAC Address :

MMC slotID : 1
moduleid : 74
driverid : 0
resetTiming : 4
pcbAssembly :
pcbRev : RB.1ÿÿ
variant Id : 0
describ : Quad BRI(S/T)
country code :
procType :
coreSpeed : 0
clockSpeed : 0
pasicID : 4
controllerID : 0
IRQ levels : 2
8b Base Addr: 0x0
16b Base Addr: 0x0
32b Base Addr: 0x0
MAC Address :
> no MMC module detected in slot 2

MMC slotID : 3
moduleid : 95
driverid : 6
resetTiming : 100
pcbAssembly :
pcbRev :
variant Id : 0
describ : 2 SHARC 21363 DSP
country code :
procType : ADSP 21363
coreSpeed : 200
clockSpeed : 25
pasicID : 4
controllerID : 0
IRQ levels : 2
8b Base Addr: 0x4c000000
16b Base Addr: 0x5c000000
32b Base Addr: 0x7c000000
MAC Address :



showdspinfo:



Dsp Status: (Warning! This only displays the current state of the dsps in the system. Failures previous to a system reboot are not recorded.)

Slot Number 0 Dsp 0 State: ACTIVE

Slot Number 3 Dsp 0 State: ACTIVE
Slot Number 3 Dsp 1 State: ACTIVE

Show fault alarm:

No faults on system
On the second system ( ICP 3300 CX II, one 4 BRI combo card) I have a digital link alarm

Info returned by SystemDiscovery::MmcInfo():

MMC slotID : 0
moduleid : 74
driverid : 0
resetTiming : 4
pcbAssembly :
pcbRev : RB.1ÿÿ
variant Id : 0
describ : Quad BRI(S/T)
country code :
procType :
coreSpeed : 0
clockSpeed : 0
pasicID : 4
controllerID : 0
IRQ levels : 2
8b Base Addr: 0x0
16b Base Addr: 0x0
32b Base Addr: 0x0
MAC Address :
> no MMC module detected in slot 1
> no MMC module detected in slot 2

MMC slotID : 3
moduleid : 95
driverid : 6
resetTiming : 100
pcbAssembly :
pcbRev :
variant Id : 0
describ : 2 SHARC 21363 DSP
country code :
procType : ADSP 21363
coreSpeed : 200
clockSpeed : 25
pasicID : 4
controllerID : 0
IRQ levels : 2
8b Base Addr: 0x4c000000
16b Base Addr: 0x5c000000
32b Base Addr: 0x7c000000
MAC Address :


Dsp Status: (Warning! This only displays the current state of the dsps in the system. Failures previous to a system reboot are not recorded.)

Slot Number 3 Dsp 0 State: ACTIVE
Slot Number 3 Dsp 1 State: ACTIVE


show fault alarm:

Digital links:

----------------------------------------------------------
| | | Total |
| Cab Shelf Slot | Card Description | Faults |
----------------------------------------------------------
| 3 1 2 | MC274Ax Basic Rate Interfac | 1 |
----------------------------------------------------------


From the alarm detail link :

Category Name Alarm Level Total Unavailable% Minor Threshold Major Threshold Critical Threshold
DSP Status Minor 5 40 1 - 100

So as per the CX II addendum page 31, none if my system are able to support IP compression ( G.729 ? ) but only one system is alarming about DSP issue. It looks like it's something else but what ?

 

[IrwinMFletcher]

What do the LOS page show for each system?

I believe that 'fault' alarms are from programming/trunks etc. DSPs do not fall under that category, so they wouldn't show up under the normal system fault alarms.

 

[IrwinMFletcher]

*submitted too soon*

My guess is that they both have 8 licenses. The first system doesn't alarm because it put the 8 G729 sessions on the DSP on the T1 Combo card.

DumpDspBootInfo will show you that.

 

[KurpeusLondon]

hmm ok but on the CX II addendum they say system base + T1/E1 combo does not provide G729 ip compression. (page 31)

Non alarming system:

Dsp(0,0): mmcSlot=1 (1-based) Load Type: TELEPHONY(1,"/sysro/DspConfig/TELEPHONY.161")
Mod Type: NOCONFERENCE(1)
Dsp(1,0): mmcSlot=4 (1-based) Load Type: TELEEC(6,"/sysro/DspConfig/TeleEC.363")
Mod Type: NOCONFERENCE(1)
Dsp(1,1): mmcSlot=4 (1-based) Load Type: TELEEC(6,"/sysro/DspConfig/TeleEC.363")
Mod Type: NOVOICEMAIL(7)


On the alarming one:

--------------------------
Dsp(0,0): mmcSlot=4 (1-based) Load Type: TELEEC(6,"/sysro/DspConfig/TeleEC.363")
Mod Type: NOCONFERENCE(1)
Dsp(0,1): mmcSlot=4 (1-based) Load Type: TELEEC(6,"/sysro/DspConfig/TeleEC.363")
Mod Type: NOVOICEMAIL(7)

 

[IrwinMFletcher]

Ah, right, because the extra T1 requires the extra telephony. But still, what do your LOS pages say is licensed?

 

[IrwinMFletcher]

Actually one second thought, that still looks odd. My NEW guess is that the system with the combo card doesn't have compression licenses.

 

[KurpeusLondon]

Sorry for the delay.

Actually they both have 8 compression licences enabled.

it must be something else. Something to do with the BRI combo card.

The show fault alarm commnand shows there is one fault with MC274Ax Basic Rate Interface. Altough it doesn't explain much, I take the guess it's why I've a dsp alarm.

That alarm detail page (from direct link, not maintenace command) show DSP status with a total of 5 resources and 40% unavailable meaning 2 dsp aren't working.

I think someone may have put a combo card for as testing purpose then removed it. I check the config and all non used slots are unconfigured. Actually I did remove these config last week but I haven't rebooted the system since (live system). Could that be the issue ?

Otherwise is there any command I should use when you add/remove comba card to your system ?

Cheers,

 

[IrwinMFletcher]

Post the DumpDspBootInfo results from both systems.

Also the pcHelp command.

 

[Supernova99]

Once you remove a card in software it is prudent to reboot the controller as it will have set is current running resources acordingly to take in the DSP's etc

Share what you know - Learn what you don't

 

[IrwinMFletcher]

Supernova, that should be automatic since the cards aren't hot-swappable, the system should be off to remove the card. Unless you want to risk frying the card or the mainboard.

 

[Supernova99]

If a BRI card was installed and it was physically removed before de-programming then the system will need a reboot.

Best practice to delete card programming before removing card.

quote:
<q>I think someone may have put a combo card for as testing purpose then removed it. I check the config and all non used slots are unconfigured. Actually I did remove these config last week but I haven't rebooted the system since (live system). Could that be the issue ? </q>


Share what you know - Learn what you don't

 

[IrwinMFletcher]

My bad, missed the word 'software' in your original post.

 

[Supernova99]

Irwin,
No probs sometimes it is easy to miss the obvious.
I have done it many times!

Share what you know - Learn what you don't