Page History
Add_workflow_for_techpubs | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
Include Page | ||||
---|---|---|---|---|
|
Panel | |
---|---|
In this section:
|
Feature Overview
The SBC relies SBC relies on IP addressing to interact with its operations-related services, such as reaching SNMP trap targets and acquiring services offered by an Element Management System (EMSa Ribbon Application Management Platform (
). However, the addresses of trap targets and the EMS Spacevars 0 model3
server can occasionally change. Spacevars 0 model3
The Service Discovery for Trap Target Destinations and EMS
Registration feature eliminates the need for SBC reconfiguration and re-initiation when IP address numbers change. This feature leverages a Domain Name System (DNS) Service Discovery framework and Fully and Fully Qualified Domain Name (FQDN) system to dynamically and automatically accomplish: Spacevars 0 model3
trap Trap destination discovery
EMS server registrationSpacevars 0 model3
Service Discovery for Trap Target Destinations
A static configuration in which SBC nodes specify the IP address and port for an SNMP trap target becomes hard to manage in an environment with multiple trap targets. The Service Discovery for Trap Target Destinations feature replaces the IP address with a Fully Qualified Domain Name (FQDN). The FQDN remains the same on all instances in a cluster. If for some reason a trap destination changes to a different location, instead of changing the IP address on all instances, you only need to change the IP address for that instance in the Service Registry.
Service Discovery for Trap Target Destinations associates an FQDN to a trap target so the FQDN can point to up to eight IP address and port combinations. If one of the destinations changes, simply update the new location of the remote entity in the Service Registry. The Service Discovery detects the change automatically according to the Time to Live (TTL) setting and notifies the SBC of the changes. The SBC automatically updates the trap destination when it receives the notification; no manual intervention at the SBC is required.
Service Discovery for
EMSRAMP Registration
Similar to the problems of static trap configurations when multiple destinations are possible, a static EMS
Spacevars | ||
---|---|---|
|
Service Discovery for EMS
Registration replaces static EMS Spacevars 0 model3
Spacevars | ||
---|---|---|
|
Info | ||||
---|---|---|---|---|
| ||||
The Service Discovery for EMS |
Implementation
Implementing the Service Discovery for Trap Target Destinations and EMS
Registration feature requires configuring the following three elements: Spacevars 0 model3
FQDNs for trap target discovery
FQDNs for EMS
registrationSpacevars 0 model3 Service Discovery for the SBC
Commands
The following table summarizes the commands used to implement the feature. (In a new SBC installation, metadata optionally provides values for the FQDN and Service Registry settings)
Table 1: Commands Commands for Implementing Service Discovery for Trap Target Destinations and EMS RAMP Registration
Command | Purpose |
---|---|
|
Specifies the FQDN of an SNMP trap target (for the full command syntax, refer to SNMP - CLI) |
|
Specifies the FQDN and IP address override of |
|
Specifies the Service Registry and Name Server that the SBC will use to resolve the trap target and |
|
For a complete description of how to configure the SBC, refer to the instructions contained in Configuring Service Discovery for Trap Destinations and RAMP Registration.
Dynamic Port
With the Service Discovery for Trap Target Destinations and EMS
Spacevars | ||
---|---|---|
|