The Oracle Communications Subscriber-Aware Load Balancer (Subscriber-Aware Load Balancer)'s show balancer metrics command displays a comparison between the number of local endpoints (that is, the associations between source addresses and each SBC) and the number of remote endpoints (that is, what the SBC reports to the Subscriber-Aware Load Balancer as the number of endpoints it has received via the tunneled interface). In the following output, those two numbers are the same; this is true if and only if there are no users in the access network that have multiple phone lines sourced from the same IP address. Were that the case, the number of remote endpoints would be higher than the number of local endpoints.

This table is populated with the data received in the periodic heartbeats from the SBC to the Subscriber-Aware Load Balancer. As these heartbeats are somewhat infrequent (every two seconds by default), the data in this table should only be considered accurate within two seconds.

ORACLE# show balancer metrics
                            local remote             max         max  Over
SBC Name                    epts  epts max reg CPU   CPU  Mem%   Mem  Load
--- ----------------------- ----- ---- ------- ----  ---- -----  ----- ----
 93 magichat                0     0    480000  2.7  90.0  0.9    95.0   no
 94 westy                   0     0    480000  2.7  90.0  0.8    95.0   no
 95 samadams                0     0    480000  2.8  90.0  0.7    95.0   no
 96 bass                    0     0    480000  4.3  90.0  2.8    95.0   no
 97 sixtus                  0     0    480000  2.9  90.0  12.8   95.0   no
 98 newcastle               0     0    480000  2.9  90.0  1.8    95.0   no
 99 guiness                 0     0    480000  3.6  90.0  0.8    95.0   no
ORACLE#

Fields descriptions include:

• SBC contains the SBC handle.
• Name contains the SBC hostname.
• max reg contains the maximum number of endpoints the Subscriber-Aware Load Balancer will send to this specific SBC. Its value is derived from the product of the session-multiplier parameter in the cluster-config configuration element and the SBC’s licensed session capacity. The SBC passes this value to the Subscriber-Aware Load Balancer during the SBC’s registration process into the cluster.
• CPU contains the last received information on the CPU percentage from this SBC.
• Max CPU contains the threshold percentage at at which the SBC defines itself as overloaded.
• Mem contains the last received information on the Mem percentage from this SBC.
• Max Mem contains the threshold percentage at which the SBC defines itself as overloaded.
• Overload displays whether or not the SBC is reporting itself as overloaded to the Subscriber-Aware Load Balancer.