IP Redundancy feature

[VladimirShushkov]

Hello, colleagues!

I deal with OXE with 2 CPU7-2 and 2 INT-IP boards. I want to configure the IP Redundancy feature according to the related part of the system documentation. So currently I've connected one CPU7 and one INT-IP to one catalyst switch, the second CPU7 and INT-IP to another switch.
After that I turn off the embedded ethernet link between CPU boards using special jumper XF03. But what should I do next? The doc says that all I need is to turn on the IP Redundancy option and that's all. But here there are some questions:
1. If OXE has ABCF over IP link should I add accesses of two INTIP boards in that IP trunk group (currently in IP trunk group there are accesses only from one INTIP board)? Or maybe I should leave one INT-IP board unconfigured and it will automatically take configuration of neighbor board?
2. If OXE has another Crystal connected to the main cabinet with INTIPA-INTIPB link should I change some parameters? Will the remote crystal connect to the main cabinet after the primary INTIP fails?
3. What if I have three INTIP boards? How OXE will know which of remained 2 boards it has to use in the case of failure?

Thank you very much!

[tot3nkopf]

1. IP trunk group should have resources also configured on the second INTIP
2. Depends on architecture and type of shelf.

Shelfs are connected to the CPU from signalling perspective (through INTIPB connections) or to other shelves through INTOF connection --> then 2 INTOF A and B)
For INTIPBs (works in pairs, INTIP declared and connected on CPU positions of the remote shelf). For INTIPAs this is not applicable.Resource allocation for IP phones is dynamic at IP domain level. For H.323 trunks see 1. For SIP trunks is N/A.

3. As mentioned at 2. and 1. this is dynamic (automatic) for general compressor resources needs and specific config needed for trunks.