Relationship between LOCAL_FAULT and REMOTE_FAULT

16

In general, the LOCAL_FAULT and REMOTE_FAULT alarms are concurrently generated. For example, if the LOCAL_FAULT alarm is reported on the local board, the REMOTE_FAULT alarm will be reported on the peer board. If the LOCAL_FAULT alarm is reported on both the local and peer tributary boards, the LOCAL_FAULT and REMOTE_FAULT alarms will be reported on the local tributary board.

Other related questions:
Relationship between LOCAL_FAULT and REMOTE_FAULT
In general, the LOCAL_FAULT and REMOTE_FAULT alarms are concurrently generated. For example, if the LOCAL_FAULT alarm is reported on the local board, the REMOTE_FAULT alarm will be reported on the peer board. If the LOCAL_FAULT alarm is reported on both the local and peer tributary boards, the LOCAL_FAULT and REMOTE_FAULT alarms will be reported on the local tributary board.

Relationship between the Elk database and HD
Elk is an SQL on Hadoop solution. It is a component of HD and provides excellent SQL query performance and compatibility on HD.

Relationship between IPSec and NAT on the USG2160
During IPSec VPN deployment, the initiator on a private network may need to establish an IPSec tunnel with the responder on a public network. To ensure that an IPSec tunnel can be established when a network address translation (NAT) device exists, NAT traversal is required. In a non-NAT traversal scenario, the gateway uses port 500 to negotiate the IPSec tunnel. In a NAT traversal scenario, the gateway uses port 4500 to negotiate the IPSec tunnel. NAT traversal enables the NAT gateway between the two ends to be discovered during IKE negotiation so that ESP packets can properly traverse the NAT gateway.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top