IP Office in redundant config

[technicaluser4]

When you have 2 x IP500V2 in a redundant configuration meaning that one system is purely standing by in case that the primary fails, what are the licenses that I need to duplicate (apart from the hardware costs involved for cards etc) to have the second one operational?

 

[intrigrant]

You cannot have a IP Office in redundant mode. no discussion - no work around - nothing

A simple mind delivers great solutions

 

[technicaluser4]

ok I meant Resilient, in case one system goes down, ip phones roll to the secondary...as described in the knowledge base however licensing requirements are not quite clear.

 

[Bas1234]

http://marketingtools.avaya.com/kno...Projects/manager/index.htm?scn_resilience.htm

Small Community Network Fallback

Release 5.0+: Each system in the Small Community Network can include one H.323 line where the Supplementary Services is set to IP Office SCN - Fallback rather than IP Office SCN. The system to which the H.323 line connects is then requested to provide fallback support for selected options for the local system.

•Note that both ends of the SCN trunk connection must be set to fallback.
•On the system requesting backup, the required SCN Backup Options are selected, indicating that it is requesting backup. A single system can only request backup from one other system.
•A system providing backup can provide backup for up to 7 other systems.

Important

•Fallback handover takes approximately 3 minutes. This ensure that fallback is not invoked when it is not required, for example when the local system is simply being rebooted to complete a non-mergeable configuration change.
•Fallback is only intended to provide basic call functionality while the cause of fallback occurring is investigated and resolved. If users make changes to their settings while in fallback, for example changing their DND mode, those changes will not apply after fallback.
•If the fallback system is rebooted while it is providing fallback services, the fallback services are lost.
•Fallback features require that the IP devices local to each system are still able to route data to the fallback system when the local system is not available. This will typically require each system site to be using a separate data router from the system.
•When an IP Phone re-registers to a secondary IP Office on the failure of the primary control unit, the second system will allow it to operate indefinitely as a “guest”, but only until the system resets. Licenses will never be consumed for a guest IP phone.
•Note that both ends of the trunk connection must be set to fallback.
•If using resilience backup to support Avaya IP phones, Auto-create Extn and Auto-create User should not be left enabled after initial configuration or any subsequent addition of new extensions and users. Leaving auto-create options enabled on a system that is a failover target may cause duplicate extension/user records on the multi-site network under multiple failure scenarios.


Fallback Options

Once a line is set to IP Office SCN - Fallback, the following options are available:

SCN Backup Options: Release 5.0+.
These options are only available on when the Supplementary Services option is set to IP Office - Fallback. The intention of this feature is to attempt to maintain a minimal level of operation while problems with the local system are resolved.
•Backs up my IP Phones: Default = On.
This option is used for Avaya 1600, 4600, 5600 and 9600 Series phones registered with the system. When selected, it will share information about the registered phones and users on those phones with the other system.

•If the local system is no longer visible to the phones, the phones will reregister with the other system. The users who were currently on those phones will appear on the other system as if they had hot desked.
•Note that when the local system is restored to the network, the phones will not automatically re-register with it. A phone reset via either a phone power cycle or using the System Status Application is required.
•When phones have registered with the other system, they will show an R on their display.
•If using resilience backup to support Avaya IP phones, Auto-create Extn and Auto-create User should not be left enabled after initial configuration or any subsequent addition of new extensions and users. Leaving auto-create options enabled on a system that is a failover target may cause duplicate extension/user records on the multi-site network under multiple failure scenarios.
•Backs up my Hunt Groups: Default = On.
When selected, any hunt groups the local system is advertising to the network are advertised from the other system when fallback is required. The trigger for this occurring is Avaya H.323 phones registered with the local system registering with the other system, ie. Backs up my IP Phones above must also be enabled. In a IP Office Server Edition network this option is only available on the H.323 trunk from the IP Office Server Edition Primary Server to the IP Office Server Edition Secondary Server.
•When used, the only hunt group members that will be available are as follows:
•If the group was a distributed hunt group, those members who were remote members on other systems still visible within the network.
•Any local members who have hot desked to another system still visible within the network.
•When the local system becomes visible to the other system again, the groups will return to be advertised from the local system.
•Backs up my Voicemail: Default = On.
This option can be used if the local system is hosting the Voicemail Pro server being used by the network. If selected, when the local system is no longer visible to the voicemail server, the other system will act as host for the voicemail server. In a IP Office Server Edition network this option is only available on the H.323 trunk from the IP Office Server Edition Primary Server to the IP Office Server Edition Secondary Server. It is assumed as being on an is automatically set by the Resilience Administration tool.
•This option requires the other system to have licenses for the Voicemail Pro features that are required to operate during any fallback period.
•This option requires Voicemail Pro 5.0+.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[intrigrant]

Did they mention hotdesking in the docs ( I did not read it, a tech never does )
Hotdesk users are not part of the resiliancy features.... at least they were in 7.0 and I did not roll out a system like that since then

A simple mind delivers great solutions

 

[Bas1234]

@intrigrant, they are...if you never hotdesk from one extn to the other....and keep the base extensions the same as the hotdeskusers

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged (Avaya Search tool

http://tinyurl.com/bas1234

)
______________________________________

 

[hairlessupportmonkey]

the server edition has redundancy built in now I understand.

ACSS - SME
General Geek

 

[tlpeter]

HSM, that is the same as with a normal IPO.

BAZINGA!

I'm not insane, my mother had me tested!

 

[Ironash]

What about VCM Modules when using SCN Fallback in IPO Preffered edition. is the (guest) IP phones in the backup system going to reserve VCM channels ? > & what abour VMPro backup >> must we have a preffered licences in both systems ?

BR,,
IronASH