In this section:
The SBC Core supports the use of the Master Trunkgroup Resource Manager (MTRM) to manage call and bandwidth resources on clients spread across multiple SBCs, thus enabling service providers to support enterprise customers using enterprise-wide CAC management down to the location and trunk group levels. The Master Trunkgroup Resource Manager (MTRM) is basically a client/server model consisting of a Master Trunk Group Server (MTRG server) and Master Trunk Group Client (MTRG client). The server and client are associated with a common name. MTRG-server and MTRG-client instances can co-exist in the same SBC, or can reside in different SBCs. The MTRG-server is configured with a CAC pool shared amongst its registered MTRG-clients. This CAC pool consists of call and bandwidth resources. The MTRG client registers with the respective MTRG server and requests for a configurable margin of call and/or bandwidth resources. The CAC resources configured on the server are shared and dynamically redistributed between the registered clients. Each client can optionally maintain its own set of local resources and/or obtain aggregate resources from the respective server. As idle client resources fall below a configurable margin (calls/bandwidth per request), a client requests more resources from the server. The server, depending on the availability, may or may not grant the resources.
This section describes the commands involved in configuring MTRM server and client connection ports.
If configuring MTRM connection port on the Management interface, first configure the Management Logical IP using syntax below. Then insert that IP address in the ipAddressV4
or ipAddressV6
field of the MTRM connection port.
% set system logicalMgmtIpInterface <name> mgmtIpInterfaceGroupName <mgmtInterfaceGroupName> ipAddress <logicalIPAddress> % set system logicalMgmtIpInterface <name> state enabled
The SBC 52x0 and SBC 7000 systems support creating IP Interface Groups containing sets of IP interfaces that are not "processor friendly" (i.e. carried on physical Ethernet ports served by separate processors). However, restrictions exist regarding the usage of such Interface Groups.
(This ability does not apply to the SBC 51x0 and SBC 5400 systems which have only two physical media ports. IP interfaces from the two physical ports may be configured within the same IP Interface Groups without restriction.)
For complete details, refer to Configuring IP Interface Groups and Interfaces.
The MTRM Conn Port CLI syntax is shown below for the Server and Client port roles selected using the portRole
parameter.
% set addressContext <addressContext name> zone <zone name> mtrmConnPort <index> portRole server healthCheckIgnore <disable | enable> healthCheckInterval <1-150> healthCheckTimeout <1-120> ipAddressV4 <IP address> ipAddressV6 <IP address> ipInterfaceGroupName <IPIG name> mgmtInterfaceGroupName <MIG name> mode <inService | outOfService> portNumber <4000-4500> state <disabled | enabled> % show addressContext <addressContext name> zone <zone name> mtrmConnPort % delete addressContext <addressContext name> zone <zone name> mtrmConnPort <index>
% set addressContext <addressContext name> zone <zone name> mtrmConnPort <index> portRole client forceSecondaryConnection <disabled | enabled> healthCheckIgnore <disable | enable> healthCheckInterval <1-150> healthCheckTimeout <1-120> ipAddressV4 <IP address> ipAddressV6 <IP address> ipInterfaceGroupName <IPIG name> mgmtInterfaceGroupName <MIG name> mode <inService | outOfService> primaryServerIPAddr <IPv4 or IPv6 address> primaryServerPortNumber <4000-4500> retryCount <3-20> secondaryIpAddress <IPv4 or IPv6 address> secondaryPortNumber <4000-4500> serverReconnectInterval <1-150> state <disabled | enabled> % show addressContext <addressContext name> zone <zone name> mtrmConnPort % delete addressContext <addressContext name> zone <zone name> mtrmConnPort <index>
Parameter | Length/Range | Description |
---|---|---|
<index> | 1-128 | The Master Trunk Group Connection Port index. |
forceSecondaryConnection | N/A | Enable this flag to force the MTRM Connection Port from the primary to the secondary server for a geo-redundant client. If MTRM is connected to secondary server, the MTRM connection port remains connected to the secondary even if the primary is available.
|
healthCheckIgnore | N/A | Enable this flag to ignore the health check time-out.
|
healthCheckInterval | 1-150 | The MTRM health check interval, in seconds. A health check message is sent to the peer at the end of each interval. (default = 5) |
healthCheckTimeout | 1-120 | The health check time-out duration, in seconds. The client connection closes if no response is received from the server during this time span. (default = 25) |
ipaddressV4 | N/A | The local IPV4 address. |
ipaddressV6 | N/A | The local IPV6 address. |
ipInterfaceGroupName | N/A | The IP Interface Group name used by MTRM connection port. |
mgmtInterfaceGroupName | N/A | Specifies the MGMT interface group name used by this MTRM connection port. |
mode | N/A | Specifies the operational mode for this MTRM connection port.
|
portRole | N/A | MTRM connection port role:
|
| N/A | The IPv4 or IPv6 address of the primary server. |
primaryServerPortNumber | 4000-4500 | The MTRM server port to connect to. (default = 4360) |
retryCount | 3-20 | The number of times to attempt a connection to the peer, after which the connection switches to the alternate server. (default = 5) |
secondaryIpAddress | N/A | The IPv4 or IPv6 address of the secondary server. |
secondaryPortNumber | 4000-4500 | Port number of the MTRM secondary server. (default = 4360) |
serverReconnectInterval | 1-150 | the amount of time in seconds after which the client tries to connect to the server. |
state | N/A | Specifies the administrative state of this MTRM connection port.
|
Use the following commands to reset MTRM connection port and statistics.
% request addressContext default zone defaultSigZone mtrmConnPort <index> reset statReset
Use the following system-level CLI syntax to view MTRM Conn Port details, peer status and statistics:
> show table addressContext <addressContext name> zone <zone name> mtrmConnPort > show status addressContext <addressContext name> zone <zone name> mtrmConnPortPeerStatus > show status addressContext <addressContext name> zone <zone name> mtrmConnPortPeerStatistics