diameter (Subscriber Aware Policy Control)
Syntax
diameter {
applications {
pcc-gx {
<maximum-pending-requests requests>;
}
}
<firmware-revision version>;
network-element element-name {
function function-name;
peer peer-name {
priority priority-value;
<timeout seconds>;
}
}
origin {
host hostname;
realm realm-name;
}
peer peer-name {
address ip-address;
connect-actively {
<capabilities-exchange-timeout seconds>;
<port port-number>;
<repeat-timeout seconds>;
<retry-timeout seconds>;
<timeout seconds>;
transport transport-name;
}
<disconnect-peer-timeout seconds>;
<incoming-queue> {
size size;
}
<outgoing-queue> {
<high-watermark high-watermark>;
<low-watermark low-watermark>;
size size;
}
<watchdog-timeout seconds>;
}
<product-name product-name>;
traceoptions {
file diameter;
flag flag;
level all;
peer {
peer-name;
}
}
Hierarchy Level
[edit access]
Description
Enabling tracing can adversely impact scale and performance and may increase security risk. We strongly recommend using the trace, tracing, or traceoptions commands only under the guidance of a JTAC support engineer. After collecting the debug information, immediately disable tracing to minimize risk and restore normal system performance.
Configure the Diameter base protocol parameters for subscriber-aware dynamic policy control, so that Diameter applications can connect to remote peers. The Diameter base protocol configuration includes configuration of the endpoint origin, the transport layer connection, the remote peers, and the network elements.
The remaining statements are explained separately. See CLI Explorer.
Required Privilege Level
access—To view this statement in the configuration.
access-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 17.1.