| Add_workflow_for_techpubs |
|---|
| AUTH1 | UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'} |
|---|
| JIRAIDAUTH | CHOR-5032 |
|---|
| REV5 | UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'} |
|---|
| REV6 | UserResourceIdentifier{userKey=8a00a0c85bb25531015bc4122a4f0003, userName='null'} |
|---|
| REV3 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c99e02c0, userName='null'} |
|---|
| REV1 | UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cc7d083d, userName='null'} |
|---|
|
| CSS Stylesheet |
|---|
img.confluence-embedded-image { display: inline-block !important; } |
To Create a Link Monitor Table entry:
| Excerpt Include |
|---|
| UXDOC122:Managing Link Monitor Configuration Tables |
|---|
| UXDOC122:Managing Link Monitor Configuration Tables |
|---|
| nopanel | true |
|---|
|
Modifying a Link Monitor Configuration Table entry
| Include Page |
|---|
| UXDOC122:_Modify_Entry |
|---|
| UXDOC122:_Modify_Entry |
|---|
| nopanel | true |
|---|
|
Creating a Link Monitor Configuration Table Entry
- At the top of the Link Monitor Configuration table, click the Create Link Monitor Configuration (
) icon. Configure the fields. Refer to Field Definitions.
- Click OK.
Settings - Field Definitions
Monitor Type
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
Valid entries: CAC/IPSEC. Link is monitored via CAC/IPSEC profile. Backup Default Route. Link is monitored for problems on the default route to the ISP. The SBC recognizes when the Internet destination is not reachable from a given (preferred) ISP; all subsequent calls are routed (via backup default route) to the secondary ISP to reach the intended Internet destination. For details on configuring a Backup Default Route, refer to: | Note |
|---|
| Both CAC/IPSEC and Backup Default Route are available options for SBC 1000/2000. For SBC SWe Edge, Monitor Type is a read-only option and is always set to Backup Default Route. |
|
Monitored Peer Type
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
Specifies the type, either host or gateway, that the link is monitoring.
If the peer type is host, the ICMP Echo and Echo Reply is the the protocol used. If the peer is a gateway, the protocol is ARP request/reply. |
Host Name
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
Specifies the address of the host to monitor. The entry must be in IPv4 format or the Fully Qualified Domain Name (FQDN) of the host being monitored. This field is visible only when Host is selected from the Monitored Peer Type drop down list. |
Gateway IP Address
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
The IP address of the gateway. This field is visible only when Gateway is selected from the Monitored Peer Type drop down list. |
Lync CAC Profile
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
Use this to select a pre-configured Lync CAC profile. The Lync CAC profile information is sent to the HQ Lync server once each five minutes and after performing an IP layer reroute following a failure (if configured). This field only applies when Monitor type is configured for CAC/IPSEC, and visible only when Gateway is selected from the Monitored Peer Type drop down list. | Note |
|---|
This setting applies to SBC 1000/2000 only. |
|
Service Status
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
The Service Status field indicates the link status of the Link Monitor to the monitored host. Status entries include: Initializing: Green Down: Red Ready: Blue Active: Green Degraded: Yellow |
Display
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
Click on the Counters option to obtain detailed information of the Host. The Link Monitor Counters screen details the Gateway, Number of Poll Attempts, and Number of Successful Polls. |
Poll Period
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
Specifies the polling interval, in seconds, for testing the link status. The host or the nexthop gateway specified by HostIPAddress is probed once each specified interval. For Default Backup Route configuration, if a faster failover is desired, update the Poll Period, Failed Polls for Down State, and SuccessfulPolls for Up State, as desired. |
Failed Polls for Down State
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
Specifies the number of consecutive failed polling attempts made against the host specified in Host IP Address field after which the host is declared to be in a down state. When the gateway is declared down, the associated IPsec tunnel is torn down (for CAC/IPSEC configuration) or route is switched from the primary default route to the backup default route (for Default Backup Route configuration). |
Successful Polls for Up State
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
Specifies the number of successful polls made against the host specified in the Host IP Address field before declaring this gateway or host as service ready. |
Associated IPsec Tunnels
| Panel |
|---|
| bgColor | #FAFAFA |
|---|
| borderStyle | none |
|---|
|
Use this field to select a maximum of four pre-configured IPsec tunnels. This field only applies when Monitor type is configured for CAC/IPSEC, and visible only when Gateway is selected from the Monitored Peer Type drop down list. | Note |
|---|
This setting applies to SBC 1000/2000 only. |
|
Switch Back to Primary Gateway via Link Monitor
The SBC 1000/2000 recognizes that the Internet destination is not reachable from a given (preferred) ISP, and all subsequent calls are routed (via backup default route) to the secondary ISP to reach the intended Internet destination. The system automatically reconfigures the Default Gateway from Primary to Backup whenever the network failure on the Primary Link is detected.
The system will not make any automatic network configuration changes when the Primary Microsoft Teams Signaling Group Link is restored. The backup Microsoft Team Signalling Group will continue to be used until the Gateway change is manually initiated or the secondary route also fails. Initiate the Gateway change from the WebUI as follows:
- Access Protocols > Network Monitoring > Link Monitors.
- Click Switch Back To Primary Gateway.