Cisco Cisco Packet Data Gateway (PDG)
SCCP Schema Statistics
▀
▄ Statistics and Counters Reference, StarOS Release 16
2286
Variables
Description
Data
Type
Type
ssa-txed
Description: Total number of Subsystem Allowed (SSA)
messages sent by Signalling Connection Control Part
(SCCP) function to the peer destination
Triggers: Increments when the SCCP subsystem becomes
available (SCCP function is not prohibited or unavailable)
and SCCP function sends an SSA message to inform the
peer destination.
Availability: per VPN context
Type: Counter
messages sent by Signalling Connection Control Part
(SCCP) function to the peer destination
Triggers: Increments when the SCCP subsystem becomes
available (SCCP function is not prohibited or unavailable)
and SCCP function sends an SSA message to inform the
peer destination.
Availability: per VPN context
Type: Counter
Int32
ss-oos-grant-txed
Description: Total number of
Subsystem-Out-of-Service-Grant (SOG) messages sent by
the SCCP function. SOG is sent as a reply by the SCCP
when it receives and accepts a
Subsystem-Out-of-Service-Request (SOR) message from
the peer SCCP.
Triggers: Increments when a SOG message is sent, in
reply to a SOR message, to the requesting SCCP.
Availability: per VPN context
Type: Counter
Subsystem-Out-of-Service-Grant (SOG) messages sent by
the SCCP function. SOG is sent as a reply by the SCCP
when it receives and accepts a
Subsystem-Out-of-Service-Request (SOR) message from
the peer SCCP.
Triggers: Increments when a SOG message is sent, in
reply to a SOR message, to the requesting SCCP.
Availability: per VPN context
Type: Counter
Int32
ss-oos-req-txed
Description: Total number of
Subsystem-Out-of-Service-Request ( SOR) messages sent
by the SCCP function, to the peer SCCP, to inform the
peer that the requesting SCCP wishes to go out-of-service.
Triggers: Increments when the SCCP wishes to go
out-of-service and sends a SOR.
Availability: per VPN context
Type: Counter
Subsystem-Out-of-Service-Request ( SOR) messages sent
by the SCCP function, to the peer SCCP, to inform the
peer that the requesting SCCP wishes to go out-of-service.
Triggers: Increments when the SCCP wishes to go
out-of-service and sends a SOR.
Availability: per VPN context
Type: Counter
Int32
ssp-txed
Description: Total number of Subsystem-Prohibited
(SSP) messages sent by the SCCP function, to the peer
SCCP subsytem, to inform the peer SCCP that the
originateing SCCP is not not available.
Triggers: Increments when the local SCCP is unavailable
and sends an SSP message.
Availability: per VPN context
Type: Counter
(SSP) messages sent by the SCCP function, to the peer
SCCP subsytem, to inform the peer SCCP that the
originateing SCCP is not not available.
Triggers: Increments when the local SCCP is unavailable
and sends an SSP message.
Availability: per VPN context
Type: Counter
Int32
ss-status-test-txed
Description: Total number of Subsystem-Status-Test
messages (SST) sent by the local SCCP, to the peer SCCP
subsystem, to verify the status of the marked peer.
Triggers: Increments when the local SCCP sends SST to
verify the peer's availability
Availability: per VPN context
Type: Counter
messages (SST) sent by the local SCCP, to the peer SCCP
subsystem, to verify the status of the marked peer.
Triggers: Increments when the local SCCP sends SST to
verify the peer's availability
Availability: per VPN context
Type: Counter
Int32