Mitel Forums - The Unofficial Source
Mitel Forums => Mitel MiVoice Business/MCD/3300 => Topic started by: bluewhite4 on October 29, 2014, 03:21:30 PM
-
Has anyone setup a PRI to be resilient between two controllers before?
-
What do you need to know?
-
On your secondary controller, is it constantly in Major alarm because the PRI connection to it is "down" (because of being online on the Primary)?
The way the documentation reads, it sounds like it shouldn't be, but the one I just setup is.
-
No alarm here.
EDT SHOW FRAMER CONFIG PRI shows the actual link status as down on the secondary.
Try EDT SHOW LINK CONFIG PRI. Mine both show "Resiliency: On". In EDT SHOW RESILIENCY, my Primary says P-A (Primary Active), and on the Secondary it is S-I (Secondary Inactive). You can force failover or failback with EDT FORCE FAILOVER ALL or FAILBACK ALL.
-
I thought the way to deal with the alarm on the secondary controller was to simply set the alarm threshold higher to cover it.
Ralph
-
Ralph,that's what I ended up doing. Just not overly comfortable with that since if it does ever go into resil. Mode and then does have a Pri issue, it won't raise the alarm.
Matthew, I'll do that when I'm back at the office. Thanks.
Sent from my iPhone using Tapatalk
-
No alarm here.
EDT SHOW FRAMER CONFIG PRI shows the actual link status as down on the secondary.
Try EDT SHOW LINK CONFIG PRI. Mine both show "Resiliency: On". In EDT SHOW RESILIENCY, my Primary says P-A (Primary Active), and on the Secondary it is S-I (Secondary Inactive). You can force failover or failback with EDT FORCE FAILOVER ALL or FAILBACK ALL.
My EDT Show Framer Config PRI and Show Resiliency show that its configured correctly.
Matthew can you do me a favor, can you tell me what your alarm levels are for Trunks, Digital Links, and NETSYNC Source?
-
Primary
---------------+--------+-------+-------+-------+---------+---------+----------
|Total In| Unavailable | Alarm Threshold Percentages
Category | System | Total | % | Alarm | MINOR | MAJOR | CRITICAL
---------------+--------+-------+-------+-------+---------+---------+----------
Trunks | 54 | 0 | 0 % | | > 0 % | 10 % | 100 % |
---------------+--------+-------+-------+-------+---------+---------+----------
---------------+--------+-------+-------+-------+---------+---------+----------
|Total In| Unavailable | Alarm Threshold Percentages
Category | System | Total | % | Alarm | MINOR | MAJOR | CRITICAL
---------------+--------+-------+-------+-------+---------+---------+----------
Digital Links | 9 | 0 | 0 % | | - | > 0 % | - |
---------------+--------+-------+-------+-------+---------+---------+----------
---------------+--------+-------+-------+-------+---------+---------+----------
|Total In| Unavailable | Alarm Threshold Percentages
Category | System | Total | % | Alarm | MINOR | MAJOR | CRITICAL
---------------+--------+-------+-------+-------+---------+---------+----------
NETSYNC source | 1 | 0 | 0 % | | > 0 % | - | - |
---------------+--------+-------+-------+-------+---------+---------+----------
Secondary
---------------+--------+-------+-------+-------+---------+---------+----------
|Total In| Unavailable | Alarm Threshold Percentages
Category | System | Total | % | Alarm | MINOR | MAJOR | CRITICAL
---------------+--------+-------+-------+-------+---------+---------+----------
Trunks | 24 | 0 | 0 % | | > 0 % | 10 % | 100 % |
---------------+--------+-------+-------+-------+---------+---------+----------
---------------+--------+-------+-------+-------+---------+---------+----------
|Total In| Unavailable | Alarm Threshold Percentages
Category | System | Total | % | Alarm | MINOR | MAJOR | CRITICAL
---------------+--------+-------+-------+-------+---------+---------+----------
Digital Links | 9 | 0 | 0 % | | - | > 0 % | - |
---------------+--------+-------+-------+-------+---------+---------+----------
---------------+--------+-------+-------+-------+---------+---------+----------
|Total In| Unavailable | Alarm Threshold Percentages
Category | System | Total | % | Alarm | MINOR | MAJOR | CRITICAL
---------------+--------+-------+-------+-------+---------+---------+----------
NETSYNC source | 1 | 0 | 0 % | | > 0 % | - | - |
---------------+--------+-------+-------+-------+---------+---------+----------
-
Very interesting...Just to confirm, the physical resilience is setup so that the PRI comes into controller A, then out of A and into B.
Mitel's telling us there is no way for controller B to silence the "physical" alarms without controller A being offline. But Your example would seem to show them to be wrong, and for it to work the way I thought it would/should.
-
Just for kicks, here's a pic of ours.
In the picture, the purple lead is the PRI input, and the black is the connection between the cards. The top controller is the Primary and it's active. Sadly, no resilience for BRI, so they have to be manually moved in times of trouble..
-
Hmm. Minus the BRI's, that matches my setup.
What software version are you running?
Wait, also, what type of T1 card is that in the backup controller? A dual T1/E1?
-
6.0 SP1 on both, but it started life as 5.0 something and I've never had PRI alarms on the secondary.
-
Wait, also, what type of T1 card is that in the backup controller? A dual T1/E1?
-
Oh, I'm pretty sure they are identical cards. Both come up in the Hardware>Framers>Resilient T1/E1 Framers forms.
-
Oh, I'm pretty sure they are identical cards. Both come up in the Hardware>Framers>Resilient T1/E1 Framers forms.
Wonder if that's my problem then. The T1 module in my secondary controller is a dual T1/E1 that the customer had before adding the resilient components.
I swore the guide said I could do that, but now after seeing your setup working the way I thought it should, I question that.
-
Digging back through the original sales docs, we quoted on 2x part number 50003560. I can't be sure if that's what went in, but it probably was.