Limits and Bounds of Serviceability Service
Serviceability Connector
Expressway Clustering
-
It is recommended that the Serviceability Connector be hosted on a solitary Expressway. We do not offer support for the Serviceability Connector when it is used on clusters with many nodes.
Expressway Coresidency
-
The Serviceability connection calls for a dedicated connection host Expressway to function properly. We do not offer coresidency support in conjunction with any other connectivity.
Cisco BroadWorks
-
The Serviceability Connector provides support for the most recent major version of Broad Works servers in addition to N-2 compatibility for the two major releases that came before that release. There is one known exception; the command to receive MariaDB status [cmd: mdbctl status] from the Cisco Broad Works Messaging Server is only supported on Broad Works R22 or later. This command is the only one of its kind.
Hosted Collaboration Mediation Framework (HCM-F)
- Each Serviceability Connector is capable of managing a single HCM-F installation. This was done on purpose.
- Your company may make use of more than one Serviceability Connector, but there may be only one HCM-F implementation per Connector.
- When importing from HCM-F, the Serviceability Connector is able to handle the following number formats:
-
-
Up to 700 customers
-
Up to 1000 clusters
-
Up to 3000 devices
-
In the event that the import from HCM-F exceeds any one of these threshholds, the Serviceability Connector will sound an alarm.