I defined two IP connections (central stations) in an M1G / M1XEP. The second one is configured as a backup. When the M1G powers up, I can see it performing a handshake with both central stations. These are routed using policy routing through different Internet gateways.
So far, so good. I see bi-directional handshakes.
Today I did some testing with various types of failures induced on the primary Internet gateway while monitoring traffic from the M1. The M1 never attempted to communicate to the back-up central station link. It just declared a comm failure.
This leads me to believe that backup reporting simply doesn't work with IP on the M1. If that's true, it's certainly very disappointing. I'm wondering if anyone else has tested anything like this? I can skin this cat another way, but it seemed to me like the best solution would be to let the M1 itself determine when it needed to report via a backup connection.
I have not enabled connection supervision; Maybe that's the key?
So far, so good. I see bi-directional handshakes.
Today I did some testing with various types of failures induced on the primary Internet gateway while monitoring traffic from the M1. The M1 never attempted to communicate to the back-up central station link. It just declared a comm failure.
This leads me to believe that backup reporting simply doesn't work with IP on the M1. If that's true, it's certainly very disappointing. I'm wondering if anyone else has tested anything like this? I can skin this cat another way, but it seemed to me like the best solution would be to let the M1 itself determine when it needed to report via a backup connection.
I have not enabled connection supervision; Maybe that's the key?
