Matrix: IVC-32 card redundant mode taking too long to switch over
Q1. Customer needs the IP system redundancy. If Switch #1 has failed can the V-Series connect to IVC-32 #1 through the redundant IVC-32 (or another) in Omega frame?
A1. In this configuration if Switch #1 fails (and all communications are lost to the Panels, Agent-IC etc )
- the matrix will change the IP address of the Redundant card
- All Card 1 devices will reconnect to Card #4
- This process may take a couple of minutes to complete
Q2. In this case, Is the physical IVC-32 #1 necessary to be removed from matrix ? or automatically change ?
A2. In this configuration if Switch #1 fails (and all communications are lost to the Panels, Agent-IC etc )
- the matrix will change the IP address of the Redundant card
- All Card 1 devices will reconnect to Card #4
If the panels are still not connecting
Are all the IP V-Series that are configured on the IVC32 card on a different Network to the that of the IVC32?
If this is the case the problem is because the network gateway PC/router is taking too long to flush its ARP cache.
The gateway machine stores mappings between an IP address and the MAC address that has this IP address for all devices on the LAN.
When our redundant IVC32 card takes over it is given the IP address that the main card originally had. The gateway machine needs to update its ARP cache (its mapping for this IP address) after the card switchover.
If this takes too long the IVC32 cards will switch back again.
If this is what you are seeing there are two possible ways to correct this.
1) Check if the ping protocol has been blocked in the gateway machine's firewall settings. If it is blocked, unblock it.
When the redundant IVC32 card takes over it pings the gateway address in order to notify it of the new MAC address to IP address mapping. If this is blocked it will not happen.
The firewall could be updated to allow Ping from the IVC32 IP address.
2) Reduce the timeout on the gateway's ARP cache.
There will be a way on the gateway machine to make it flush its ARP cache more often. If this is set to every 10 or 15 seconds it will correct this issue.
If the gateway is a Linux OS there will be a config file that can be edited to do this.
On windows it may involve a change to registry settings on the gateway machine.
Thank you : I can connect the v-series to redundant IVC thanks to your help. The cause that the gateway setting on v-series was wrong IP address.
A1. In this configuration if Switch #1 fails (and all communications are lost to the Panels, Agent-IC etc )
- the matrix will change the IP address of the Redundant card
- All Card 1 devices will reconnect to Card #4
- This process may take a couple of minutes to complete
Q2. In this case, Is the physical IVC-32 #1 necessary to be removed from matrix ? or automatically change ?
A2. In this configuration if Switch #1 fails (and all communications are lost to the Panels, Agent-IC etc )
- the matrix will change the IP address of the Redundant card
- All Card 1 devices will reconnect to Card #4
If the panels are still not connecting
Are all the IP V-Series that are configured on the IVC32 card on a different Network to the that of the IVC32?
If this is the case the problem is because the network gateway PC/router is taking too long to flush its ARP cache.
The gateway machine stores mappings between an IP address and the MAC address that has this IP address for all devices on the LAN.
When our redundant IVC32 card takes over it is given the IP address that the main card originally had. The gateway machine needs to update its ARP cache (its mapping for this IP address) after the card switchover.
If this takes too long the IVC32 cards will switch back again.
If this is what you are seeing there are two possible ways to correct this.
1) Check if the ping protocol has been blocked in the gateway machine's firewall settings. If it is blocked, unblock it.
When the redundant IVC32 card takes over it pings the gateway address in order to notify it of the new MAC address to IP address mapping. If this is blocked it will not happen.
The firewall could be updated to allow Ping from the IVC32 IP address.
2) Reduce the timeout on the gateway's ARP cache.
There will be a way on the gateway machine to make it flush its ARP cache more often. If this is set to every 10 or 15 seconds it will correct this issue.
If the gateway is a Linux OS there will be a config file that can be edited to do this.
On windows it may involve a change to registry settings on the gateway machine.
Thank you : I can connect the v-series to redundant IVC thanks to your help. The cause that the gateway setting on v-series was wrong IP address.
CAN'T FIND YOUR ANSWER? CLICK HERE TO CONTACT SUPPORT
This solution was provided to you by Clear-Com via a question submitted to us by customers like you. If your question wasn’t answered, you need help or you have a recommended solution for our database, please send us an email at support@clearcom.com
The information on this page is owned by Clear-Com and constitutes Clear-Com’s confidential and proprietary information, may be used solely for purposes related to the furtherance of Clear-Com’ business and shall not be disclosed, distributed, copied or disseminated without Clear-Com’s prior written consent. Click Here for Clear-Com's privacy statement.