Service Engineering Rules
The engineering rules listed here apply to the services configurations for the MME system.
-
A maximum combined total of 256 services (regardless of type) can be configured per system.
Important
Maintaining a large number of services increases the complexity of management and may impact overall system performance (i.e., resulting from such things as system handoffs). Therefore, we recommend that you limit the number of services that you configure and that you talk to your Cisco Service Representative for optimization suggestions and additional information on service limits.
-
The total number of entries per table and per chassis is limited to 256.
-
Of the 256 possible services, the MME supports a maximum total combination of eight (8) MME-specific services, of the types MME + eMBMS + SGs+ SBc + SLs -service, be configured per chassis.
-
The maximum number of HSS Peer Services that can be created and configured is 96 HSS Peer Services per MME chassis.
Important
In some cases, two diameter endpoints (S6a and S13) can be configured for a single HSS Peer Service. To ensure peak system performance, we recommend that the total of all Diameter endpoints should be taken into consideration and limited to 64 endpoints.
-
When a roaming subscriber uses dynamic destination Host length equal or greater than 64 bytes, it results in initial request intended to that HSS peer that leads to ATTACH REJECTS. To avoid rejection of roaming subscribers, use the length of the dynamic hostname to not more than 64 characters.
-
We strongly recommend that service names be unique across the chassis/system configuration. Even though service names can be identical to those configured in different contexts on the same system, this is not a good practice. Having services with the same name can lead to confusion, difficulty troubleshooting problems, and make it difficult to understand the outputs of show commands.