Beginning with SBC Core release 12.0, the SBC interoperates with the Ribbon Application Management Platform (RAMP), replacing the Insight EMS.
However, the EMA, CLI and API will continue to include EMS-labeled parameters and screens to facilitate SBC migrations from older releases. Accordingly, any references to "EMS" in this documentation apply to the RAMP platform.
In this section:
The SBC relies on IP addressing to interact with its operations-related services, such as reaching SNMP trap targets and acquiring services offered by a Ribbon Application Management Platform (
The Service Discovery for Trap Target Destinations and
Trap destination discovery
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.
Similar to the problems of static trap configurations when multiple destinations are possible, a static
Service Discovery for
The Service Discovery for
Implementing the Service Discovery for Trap Target Destinations and
FQDNs for trap target discovery
FQDNs for
Service Discovery for the SBC
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 for Implementing Service Discovery for Trap Target Destinations and 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 a Unable to show "metadata-from": No such page "_space_variables" server (for the full command syntax, refer to System - Ems) |
| 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.
With the Service Discovery for Trap Target Destinations and