You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Command Syntax

The command syntax to show a Monitoring Profile is shown here:

Example
> show profiles services monitoringProfile <monitoring profile name>
    additionalInformation
    displayLevel
    filter
    header
    headerPresence
    mgmtInterfaceGroup
    monitoringIpAddress
    monitoringIpPort
    signalingPackets
    state
    transport
    type

Command Parameters

Command Parameters for monitoringProfile

ParameterLength/RangeDefaultDescriptionM/O

additionalInformation

256 

Additional information in the header sent towards the monitoring server.

O
displayLevel  

Depth to show.

  • unsignedLong –
  • 1 .. 64 –
 O

filter

  

This table contains filters for the profile.

  • transport – Transport type used to filter the packets
  • trunkgroup – IP TG filter used to filter the packets.
O

headerPresence

 disabled

Specifies if X header presence towards monitoring server is enabled or not

O

mgmtInterfaceGroup

 mgmtGroup

The Management Interface Group to use for communicating with monitoring server.

O

monitoringIpAddress

  

IP address of the monitoring server.

M

monitoringIpPort

  

TCP/UDP port for the monitoring server.

  • int –
  • 0 .. 65535
M
monitoringProfileName24 Name of Monitoring Profile used for this SIP Signaling Port.O

signalingPackets

  

Specifies if all signaling packets, or only decrypted TLS packets, are sent towards monitoring server from all TGs.

O

state

  

Administrative state of this Monitoring Profile.

  • disabled
  • enabled
 

transport

 udp

Select the transport type for the monitoring server.

  • sctp – Stream Control Transmission Protocol
  • tcp – Transmission Control Protocol
  • tls-tcp – Transport Layer Security running on top of TCP
  • udp – User Datagram Protocol
O

type

 mgmt

Interface type supported by monitoring server. 

  • IP – IP interface to be used for this monitoring server, addressContext and ipInterfaceGroup must be completed when this is selected.
  • mgmt – Mgmt interface to be used for this monitoring server, mgmtInterfaceGroup must be completed when this sis selected.
O
 

Configuration Example

admin@SAPOTA% show profiles services monitoringProfile
monitoringProfile test1 {
    monitoringIpAddress   NN.NN.NN.NN;
    monitoringIpPort      6786;
    type                  mgmt;
    mgmtInterfaceGroup    mgmtGroup;
    signalingPackets      none;
    headerPresence        enabled;
    additionalInformation SAPOTA;
    header 1 {
        headerName   x-Ribbon-SIP-Source;
        sourceIpPort enabled;
    }
    header 2 {
        headerName        x-Ribbon-SIP-Destination;
        destinationIpPort enabled;
    }
    header 3 {
        headerName x-Ribbon-Date;
        date       enabled;
    }
    header 4 {
        headerName            x-Ribbon-Network-Id;
        additionalInformation enabled;
    }
    header 5 {
        headerName x-Ribbon-SBGTIME;
        timestamp  enabled;
    }
    filter 1 {
        trunkgroup RHEL_1;
        transport  udp;
    }
}

 

 

 


  • No labels