Panel | ||||
---|---|---|---|---|
In this section:
|
Info | ||
---|---|---|
| ||
Related articles: |
The
...
Spacevars | ||
---|---|---|
|
However, if these PKT ports are SR-IOV interfaces, currently there is no way to support the port redundancy for PKT interfaces since hypervisor is by-passed in such NIC configuration. To support port redundancy on SR-IOV interfaces, this feature is enhanced on SBC SWe cloud platform, which works based on ICMP/ARP probing mechanism. This mechanism requires four PKT ports (SR-IOV VFs) configured on a SWe instance, where each of these SR-IOV VFs may come from different physical NICs for better handling of connectivity failures due to physical NIC or physical link connected towards different physical switches.
The PKT ports are automatically configured in active-standby mode to provide port redundancy on active SWe instance. The PKT ports connected in standby SWe instance remains in standby mode. The ICMPv4/v6 probing mechanism is used on active PKT ports, while ARP ACD/ICMPv6 NUD mechanism is used on standby ports.
Info | |
---|---|
|
...
| |
The port redundancy feature |
...
applies to the following SBC platforms only:
|
...
|
...
...
Spacevars | ||
---|---|---|
|
Caption | ||||
---|---|---|---|---|
| ||||
Secondary port:
Active port: The PKT port that is currently selected for use (For example, signaling, media); either a primary or a secondary port on an active SWe node.
...
Info | ||
---|---|---|
| ||
The port in the active state does not necessarily imply it is "up". |
Local standby port: A standby PKT port on an active SWe node provides redundancy protection to the currently active port.
Enabled or Disabled ports: The PKT port may be administratively enabled or disabled. A PKT port that is disabled cannot be an active port.
...
Info | ||
---|---|---|
| ||
The PKT port's role (Primary/Secondary) is independent of the port's state (Active/Standby). |
...
Info | ||||
---|---|---|---|---|
| ||||
|
The
...
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
The following probing mechanisms are available on the
Spacevars | ||
---|---|---|
|
Caption | ||||
---|---|---|---|---|
|
...
|
...
|
...
|
* Address Resolution Protocol - Address Conflict Detection / Internet Control Message Protocol Version 6 – Neighbor Unreachability Detection
If the destination address configured is an IPv4 address, then IPv4 probing is initiated by sending an ARP Probe requests and listening for the responses.
ARP request probes are sent with:
The target can be expected to respond with an ARP Response using L2 unicast.
If the destination address configured is an IPv6 address, then IPv6 probing would be initiated using Neighbor Unreachability Detection mechanism (RFC 4861 section 7). This is based on Neighbor Solicitation and Neighbor Advertisement ICMPv6 messages.
Because these are IP packets, the
Spacevars | ||
---|---|---|
|
Spacevars | ||
---|---|---|
|
Neighbor Solicitation messages are sent with:
The Neighbor Solicitation message is sent on the LAN via L2 unicast to the system with the target IP address.
The target can be expected to respond with a Neighbor Advertisement using L2 unicast. Received messages are validated per RFC 4861 section 7.1.2: Check that the S bit = 1 (solicited) and that the target address = our configured target IP address.
Info |
---|
...
| ||
The |
...
|
Pagebreak |
---|