Cisco Cisco Prime Access Registrar 7.2 Release Notes
2
Cisco Prime Access Registrar 7.2 Release Notes
Co-Existence With Other Network Management Applications
Co-Existence With Other Network Management Applications
To achieve optimal performance, Prime Access Registrar should be the only application running on a
given server. In certain cases, when you choose to run collaborative applications such as a SNMP agent,
you must configure Prime Access Registrar to avoid UDP port conflicts. The most common conflicts
occur when other applications also use ports 2785 and 2786. For more information on SNMP
configuration, see the Configuring SNMP section, in the
given server. In certain cases, when you choose to run collaborative applications such as a SNMP agent,
you must configure Prime Access Registrar to avoid UDP port conflicts. The most common conflicts
occur when other applications also use ports 2785 and 2786. For more information on SNMP
configuration, see the Configuring SNMP section, in the
.
Enhanced Features in Cisco Prime Access Registrar 7.2
Prime Access Registrar 7.2 provides the following features:
•
•
•
•
Group-Based Load Balancing in Diameter Proxy Service Configuration
Prime Access Registrar allows you to create two or more groups of Diameter remote servers in a
Diameter proxy service configuration. Each of these groups will have a unique set of remote servers, i.e.
no two groups will share the same remote server.
Diameter proxy service configuration. Each of these groups will have a unique set of remote servers, i.e.
no two groups will share the same remote server.
The traffic between each of these groups is load-balanced in failover mode; while traffic between remote
servers within the same group is load-balanced based on round-robin or failover mode depending on the
existing Diameter configuration.
servers within the same group is load-balanced based on round-robin or failover mode depending on the
existing Diameter configuration.
The workflow for group-based load balancing is as given below:
1.
Traffic from Prime Access Registrar to Diameter remote server, via Diameter proxy service, is
directed through the first group, till Prime Access Registrar has active communication channel with
at least one remote server belonging to the first group.
directed through the first group, till Prime Access Registrar has active communication channel with
at least one remote server belonging to the first group.
Table 1
Minimum Hardware and Software Requirements for Prime Access Registrar Server
OS version
RHEL 6.4/6.6/7.0
CentOS 6.5
Model
X86
CPU type
Intel Xeon CPU 2.30 GHz
CPU Number
4
CPU speed
2.30 GHz
Memory (RAM)
8 GB
Swap space
10 GB
Disk space
1*146 GB