Trunks - CUBE Names

Vyopta provides support and services for Cisco CUBE Trunks. This document will explain how the names for the CUBE Trunks are created and what they mean.

Issue

How are the names for the CUBE Trunks created and what do they mean?

Solution

A Trunk is a logical connection between two systems defined at the target-protocol level. For a CUBE, "trunks" are defined by the dial peers. Note: A unique Truck consist of Trunk Name + System columns.

Outbound CUBE to ip/host

All dial peers for a system mapped to a target IP or Host. Example: Outbound CUBE to ipv4:192.168.1.201:5555 Note: If the description field is the same for all peers, the description will be used at the Trunk name.

Outbound CUBE to "Text"

All dial peers for a system mapped to a target "Text". Example: Outbound Dial-Peer for Calls to CUCM ABCD subscriber

Non-Target Peer Groups

All dial peers for a system with blank targets (catch all). Example: Non-Target Peer Groups

Server group #-ip/host

All dial peers for a system mapped to a group of targets. Each target will be listed separately. Example:

Server group 1-ipv192.168.1.100
Server group 1-ipv192.168.1.101
Server group 1-ipv192.168.1.102

Vyopta also provides monitoring for CUBE Trunks, including creation of “Trunks” at the target-protocol level from CUBE dial peer collection, trunk availability status, and filtering, sorting, and multi-sorting on Trunk Name, Target IP, Target Host, Protocol, Status, Data Source, and System.