The main purpose of this MIB is to define the SNMP
notifications and alarms generated by Session Border Controller
application and used to send these notifications to SNMP
manager application. Each of these event/notification is
explained in detail in the MIB file.
The SBC service is implemented on a service card on CISCO
routers. SBC application offer functionalities like
firewall/NAT traversal, media bridging, policy-based call
routing, signaling protocol inter-working, call billing and
some degree of Call Admission Control. SBC looks to play an
essential role in full-scale commercial deployment of VoIP and
integration into the existing PSTN.
The Session Border Controller (SBC) enables direct IP-to-IP
interconnect between multiple administrative domains for
session-based services providing protocol inter-working,
security, and admission control and management. The SBC is a
voice over IP (VoIP) device that sits on the border
of a network and controls call admission to that network.
The primary purpose of an SBC is to protect the interior of
the network from excessive call load and malicious traffic.
Additional functions provided by the SBC include media
bridging and billing services.
Various types of notifications required for SBC applications
are
as follows:
1. When SIP/H2.48 calls are established and SBC application
receives traffic (RTP/RTCP packets) from a source whose IP
address or port is ambiguous, a source alert event is generated
for the unwanted data packets received by SBC application.
2. Blacklisting is the process of matching inbound packets based
on some simple parameters (for example source IP address) and
preventing packets that match those parameters from being
processed. SBC detects an attempt to disrupt traffic flowing
through it. When a source is blacklisted in SBC application, an
event is generated to provide information of the blacklisted
source like its IP address, port, VPN address etc.
3. When there is a change in the state of any SBC service
configured like a new SBC service is configured or the SBC card
goes to standby state, reboot or offline state, a service is
removed from SBC card, an event is generated by SBC.
4. When a large number of SIP/H.248 calls are ongoing and
system is congested i.e. high CPU usage or high use of memory
utilization, congestion event is generated at this point and
when congestion is cleared means CPU usage comes to normal
another event for congestion clear is generated.
5. When a service is configured on SBC application, its call
policies are defined during the configuration like maximum
number of calls, maximum call rates etc. If any of these
policies is violated, an event for violation of service level
agreement is generated.
6. When a radius server is attached/detached with SBC, a
notification is generated to provide information of radius
server type, IP address, port etc.
7. When an adjacency is attached/detached with SBC, a
notification is generated to provide its information like the
adjacency type and state.
8. When a H.248 controller is attached/detached with SBC to
establish H.248 calls with SBC, a notification is generated to
provide the information regarding the attached/detached H.248
controller like controller index, IP address, port, state etc.
GLOSSARY
SBC: Session Border Controller
CSB: CISCO Session Border Controller
CAC: Call Admission Control - protects voice traffic from the
negative effects of other voice traffic and to keep excess voice
traffic off the network. It is used to prevent congestion in
Voice traffic. It is used in the Call Setup phase.
RTP: Real Time Transport Protocol - defines a standardized
packet format for delivering audio and video over the Internet.
RTCP: Real Time Control Protocol - It is a sister protocol of
the Real-time Transport Protocol (RTP). RTCP provides
out-of-band control information for an RTP flow. It partners RTP
in the delivery and packaging of multimedia data, but does not
transport any data itself. It is used periodically to transmit
control packets to participants in a streaming multimedia
session.
VMG: Virtual Media Gateway - introduced to bridge between
different transmission technologies and to add service to
end-user connections. Its architecture separates control and
connectivity functions into physically separate network layers.
VPN: Virtual Private Network - It is a communications network
tunneled through another network, and dedicated for a specific
network.
Gate Id - Context Identifiers assigned uniquely to a SIP/H.248
call flows.
Flow Pair Id: Stream Identifiers assigned uniquely to a
SIP/H.248 call flows.
Adjacency: An adjacency contains the system information to be
transmitted to next HOP.
SLA: Service Level Agreement - Service level agreement includes
some call admission control policies which are defined during
the SBC configurations like maximum number of calls, maximum
call rates etc.
Diameter Server: A Diameter Server is one that handles
authentication, authorization and accounting requests for a
particular realm.
REFERENCES
1. CISCO Session Border Controller Documents and FAQ
http://zed.cisco.com/confluence/display/SBC/SBC
Parsed from file CISCO-SESS-BORDER-CTRLR-EVENT-MIB.mib
Module: CISCO-SESS-BORDER-CTRLR-EVENT-MIB
The main purpose of this MIB is to define the SNMP
notifications and alarms generated by Session Border Controller
application and used to send these notifications to SNMP
manager application. Each of these event/notification is
explained in detail in the MIB file.
The SBC service is implemented on a service card on CISCO
routers. SBC application offer functionalities like
firewall/NAT traversal, media bridging, policy-based call
routing, signaling protocol inter-working, call billing and
some degree of Call Admission Control. SBC looks to play an
essential role in full-scale commercial deployment of VoIP and
integration into the existing PSTN.
The Session Border Controller (SBC) enables direct IP-to-IP
interconnect between multiple administrative domains for
session-based services providing protocol inter-working,
security, and admission control and management. The SBC is a
voice over IP (VoIP) device that sits on the border
of a network and controls call admission to that network.
The primary purpose of an SBC is to protect the interior of
the network from excessive call load and malicious traffic.
Additional functions provided by the SBC include media
bridging and billing services.
Various types of notifications required for SBC applications
are
as follows:
1. When SIP/H2.48 calls are established and SBC application
receives traffic (RTP/RTCP packets) from a source whose IP
address or port is ambiguous, a source alert event is generated
for the unwanted data packets received by SBC application.
2. Blacklisting is the process of matching inbound packets based
on some simple parameters (for example source IP address) and
preventing packets that match those parameters from being
processed. SBC detects an attempt to disrupt traffic flowing
through it. When a source is blacklisted in SBC application, an
event is generated to provide information of the blacklisted
source like its IP address, port, VPN address etc.
3. When there is a change in the state of any SBC service
configured like a new SBC service is configured or the SBC card
goes to standby state, reboot or offline state, a service is
removed from SBC card, an event is generated by SBC.
4. When a large number of SIP/H.248 calls are ongoing and
system is congested i.e. high CPU usage or high use of memory
utilization, congestion event is generated at this point and
when congestion is cleared means CPU usage comes to normal
another event for congestion clear is generated.
5. When a service is configured on SBC application, its call
policies are defined during the configuration like maximum
number of calls, maximum call rates etc. If any of these
policies is violated, an event for violation of service level
agreement is generated.
6. When a radius server is attached/detached with SBC, a
notification is generated to provide information of radius
server type, IP address, port etc.
7. When an adjacency is attached/detached with SBC, a
notification is generated to provide its information like the
adjacency type and state.
8. When a H.248 controller is attached/detached with SBC to
establish H.248 calls with SBC, a notification is generated to
provide the information regarding the attached/detached H.248
controller like controller index, IP address, port, state etc.
GLOSSARY
SBC: Session Border Controller
CSB: CISCO Session Border Controller
CAC: Call Admission Control - protects voice traffic from the
negative effects of other voice traffic and to keep excess voice
traffic off the network. It is used to prevent congestion in
Voice traffic. It is used in the Call Setup phase.
RTP: Real Time Transport Protocol - defines a standardized
packet format for delivering audio and video over the Internet.
RTCP: Real Time Control Protocol - It is a sister protocol of
the Real-time Transport Protocol (RTP). RTCP provides
out-of-band control information for an RTP flow. It partners RTP
in the delivery and packaging of multimedia data, but does not
transport any data itself. It is used periodically to transmit
control packets to participants in a streaming multimedia
session.
VMG: Virtual Media Gateway - introduced to bridge between
different transmission technologies and to add service to
end-user connections. Its architecture separates control and
connectivity functions into physically separate network layers.
VPN: Virtual Private Network - It is a communications network
tunneled through another network, and dedicated for a specific
network.
Gate Id - Context Identifiers assigned uniquely to a SIP/H.248
call flows.
Flow Pair Id: Stream Identifiers assigned uniquely to a
SIP/H.248 call flows.
Adjacency: An adjacency contains the system information to be
transmitted to next HOP.
SLA: Service Level Agreement - Service level agreement includes
some call admission control policies which are defined during
the SBC configurations like maximum number of calls, maximum
call rates etc.
Diameter Server: A Diameter Server is one that handles
authentication, authorization and accounting requests for a
particular realm.
REFERENCES
1. CISCO Session Border Controller Documents and FAQ
http://zed.cisco.com/confluence/display/SBC/SBC
Parsed from file CISCO-SESS-BORDER-CTRLR-EVENT-MIB.my.txt
Company: None
Module: CISCO-SESS-BORDER-CTRLR-EVENT-MIB
The main purpose of this MIB is to define the SNMP
notifications and alarms generated by Session Border Controller
application and used to send these notifications to SNMP
manager application. Each of these event/notification is
explained in detail in the MIB file.
The SBC service is implemented on a service card on CISCO
routers. SBC application offer functionalities like
firewall/NAT traversal, media bridging, policy-based call
routing, signaling protocol inter-working, call billing and
some degree of Call Admission Control. SBC looks to play an
essential role in full-scale commercial deployment of VoIP and
integration into the existing PSTN.
The Session Border Controller (SBC) enables direct IP-to-IP
interconnect between multiple administrative domains for
session-based services providing protocol inter-working,
security, and admission control and management. The SBC is a
voice over IP (VoIP) device that sits on the border
of a network and controls call admission to that network.
The primary purpose of an SBC is to protect the interior of
the network from excessive call load and malicious traffic.
Additional functions provided by the SBC include media
bridging and billing services.
Various types of notifications required for SBC applications
are
as follows:
1. When SIP/H2.48 calls are established and SBC application
receives traffic (RTP/RTCP packets) from a source whose IP
address or port is ambiguous, a source alert event is generated
for the unwanted data packets received by SBC application.
2. Blacklisting is the process of matching inbound packets based
on some simple parameters (for example source IP address) and
preventing packets that match those parameters from being
processed. SBC detects an attempt to disrupt traffic flowing
through it. When a source is blacklisted in SBC application, an
event is generated to provide information of the blacklisted
source like its IP address, port, VPN address etc.
3. When there is a change in the state of any SBC service
configured like a new SBC service is configured or the SBC card
goes to standby state, reboot or offline state, a service is
removed from SBC card, an event is generated by SBC.
4. When a large number of SIP/H.248 calls are ongoing and
system is congested i.e. high CPU usage or high use of memory
utilization, congestion event is generated at this point and
when congestion is cleared means CPU usage comes to normal
another event for congestion clear is generated.
5. When a service is configured on SBC application, its call
policies are defined during the configuration like maximum
number of calls, maximum call rates etc. If any of these
policies is violated, an event for violation of service level
agreement is generated.
6. When a radius server is attached/detached with SBC, a
notification is generated to provide information of radius
server type, IP address, port etc.
7. When an adjacency is attached/detached with SBC, a
notification is generated to provide its information like the
adjacency type and state.
8. When a H.248 controller is attached/detached with SBC to
establish H.248 calls with SBC, a notification is generated to
provide the information regarding the attached/detached H.248
controller like controller index, IP address, port, state etc.
GLOSSARY
SBC: Session Border Controller
CSB: CISCO Session Border Controller
CAC: Call Admission Control - protects voice traffic from the
negative effects of other voice traffic and to keep excess voice
traffic off the network. It is used to prevent congestion in
Voice traffic. It is used in the Call Setup phase.
RTP: Real Time Transport Protocol - defines a standardized
packet format for delivering audio and video over the Internet.
RTCP: Real Time Control Protocol - It is a sister protocol of
the Real-time Transport Protocol (RTP). RTCP provides
out-of-band control information for an RTP flow. It partners RTP
in the delivery and packaging of multimedia data, but does not
transport any data itself. It is used periodically to transmit
control packets to participants in a streaming multimedia
session.
VMG: Virtual Media Gateway - introduced to bridge between
different transmission technologies and to add service to
end-user connections. Its architecture separates control and
connectivity functions into physically separate network layers.
VPN: Virtual Private Network - It is a communications network
tunneled through another network, and dedicated for a specific
network.
Gate Id - Context Identifiers assigned uniquely to a SIP/H.248
call flows.
Flow Pair Id: Stream Identifiers assigned uniquely to a
SIP/H.248 call flows.
Adjacency: An adjacency contains the system information to be
transmitted to next HOP.
SLA: Service Level Agreement - Service level agreement includes
some call admission control policies which are defined during
the SBC configurations like maximum number of calls, maximum
call rates etc.
Diameter Server: A Diameter Server is one that handles
authentication, authorization and accounting requests for a
particular realm.
REFERENCES
1. CISCO Session Border Controller Documents and FAQ
http://zed.cisco.com/confluence/display/SBC/SBC
ciscoSessBorderCtrlrEventMIB MODULE-IDENTITY LAST-UPDATED "200808270000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The main purpose of this MIB is to define the SNMP notifications and alarms generated by Session Border Controller application and used to send these notifications to SNMP manager application. Each of these event/notification is explained in detail in the MIB file. The SBC service is implemented on a service card on CISCO routers. SBC application offer functionalities like firewall/NAT traversal, media bridging, policy-based call routing, signaling protocol inter-working, call billing and some degree of Call Admission Control. SBC looks to play an essential role in full-scale commercial deployment of VoIP and integration into the existing PSTN. The Session Border Controller (SBC) enables direct IP-to-IP interconnect between multiple administrative domains for session-based services providing protocol inter-working, security, and admission control and management. The SBC is a voice over IP (VoIP) device that sits on the border of a network and controls call admission to that network. The primary purpose of an SBC is to protect the interior of the network from excessive call load and malicious traffic. Additional functions provided by the SBC include media bridging and billing services. Various types of notifications required for SBC applications are as follows: 1. When SIP/H2.48 calls are established and SBC application receives traffic (RTP/RTCP packets) from a source whose IP address or port is ambiguous, a source alert event is generated for the unwanted data packets received by SBC application. 2. Blacklisting is the process of matching inbound packets based on some simple parameters (for example source IP address) and preventing packets that match those parameters from being processed. SBC detects an attempt to disrupt traffic flowing through it. When a source is blacklisted in SBC application, an event is generated to provide information of the blacklisted source like its IP address, port, VPN address etc. 3. When there is a change in the state of any SBC service configured like a new SBC service is configured or the SBC card goes to standby state, reboot or offline state, a service is removed from SBC card, an event is generated by SBC. 4. When a large number of SIP/H.248 calls are ongoing and system is congested i.e. high CPU usage or high use of memory utilization, congestion event is generated at this point and when congestion is cleared means CPU usage comes to normal another event for congestion clear is generated. 5. When a service is configured on SBC application, its call policies are defined during the configuration like maximum number of calls, maximum call rates etc. If any of these policies is violated, an event for violation of service level agreement is generated. 6. When a radius server is attached/detached with SBC, a notification is generated to provide information of radius server type, IP address, port etc. 7. When an adjacency is attached/detached with SBC, a notification is generated to provide its information like the adjacency type and state. 8. When a H.248 controller is attached/detached with SBC to establish H.248 calls with SBC, a notification is generated to provide the information regarding the attached/detached H.248 controller like controller index, IP address, port, state etc. GLOSSARY SBC: Session Border Controller CSB: CISCO Session Border Controller CAC: Call Admission Control - protects voice traffic from the negative effects of other voice traffic and to keep excess voice traffic off the network. It is used to prevent congestion in Voice traffic. It is used in the Call Setup phase. RTP: Real Time Transport Protocol - defines a standardized packet format for delivering audio and video over the Internet. RTCP: Real Time Control Protocol - It is a sister protocol of the Real-time Transport Protocol (RTP). RTCP provides out-of-band control information for an RTP flow. It partners RTP in the delivery and packaging of multimedia data, but does not transport any data itself. It is used periodically to transmit control packets to participants in a streaming multimedia session. VMG: Virtual Media Gateway - introduced to bridge between different transmission technologies and to add service to end-user connections. Its architecture separates control and connectivity functions into physically separate network layers. VPN: Virtual Private Network - It is a communications network tunneled through another network, and dedicated for a specific network. Gate Id - Context Identifiers assigned uniquely to a SIP/H.248 call flows. Flow Pair Id: Stream Identifiers assigned uniquely to a SIP/H.248 call flows. Adjacency: An adjacency contains the system information to be transmitted to next HOP. SLA: Service Level Agreement - Service level agreement includes some call admission control policies which are defined during the SBC configurations like maximum number of calls, maximum call rates etc. Diameter Server: A Diameter Server is one that handles authentication, authorization and accounting requests for a particular realm. REFERENCES 1. CISCO Session Border Controller Documents and FAQ http://zed.cisco.com/confluence/display/SBC/SBC" REVISION "200808270000Z" DESCRIPTION "Changes to correct problem were csbSLACurrentUsage and csbSLAPolicyLimit was incorrectly defined as Integer32. Deprecated the following objects and notification. csbSLACurrentUsage csbSLAPolicyLimit csbSLAViolationNotifEnabled csbSLAViolation Created the following objects and notification csbSLACurrentUsageRev1 csbSLAPolicyLimitRev1 csbSLAViolationNotifEnabledRev1 csbSLAViolationRev1 Correct definition of csbAlarmTime object." REVISION "200805290000Z" DESCRIPTION "Initial version of the MIB module." ::= { ciscoMgmt 658 }
ciscoSessBorderCtrlrEventMIB OBJECT IDENTIFIER ::= { ciscoMgmt 658 }
Vendor: Cisco
Module: CISCO-SESS-BORDER-CTRLR-EVENT-MIB
[Automatically extracted from oidview.com]
ciscoSessBorderCtrlrEventMIB MODULE-IDENTITY LAST-UPDATED "201012060000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The main purpose of this MIB is to define the SNMP notifications and alarms generated by Session Border Controller application and used to send these notifications to SNMP manager application. Each of these event/notification is explained in detail in the MIB file. The SBC service is implemented on a service card on CISCO routers. SBC application offer functionalities like firewall/NAT traversal, media bridging, policy-based call routing, signaling protocol inter-working, call billing and some degree of Call Admission Control. SBC looks to play an essential role in full-scale commercial deployment of VoIP and integration into the existing PSTN. The Session Border Controller (SBC) enables direct IP-to-IP interconnect between multiple administrative domains for session-based services providing protocol inter-working, security, and admission control and management. The SBC is a voice over IP (VoIP) device that sits on the border of a network and controls call admission to that network. The primary purpose of an SBC is to protect the interior of the network from excessive call load and malicious traffic. Additional functions provided by the SBC include media bridging and billing services. Various types of notifications required for SBC applications are as follows: 1. When SIP/H2.48 calls are established and SBC application receives traffic (RTP/RTCP packets) from a source whose IP address or port is ambiguous, a source alert event is generated for the unwanted data packets received by SBC application. 2. Blacklisting is the process of matching inbound packets based on some simple parameters (for example source IP address) and preventing packets that match those parameters from being processed. SBC detects an attempt to disrupt traffic flowing through it. When a source is blacklisted in SBC application, an event is generated to provide information of the blacklisted source like its IP address, port, VPN address etc. 3. When there is a change in the state of any SBC service configured like a new SBC service is configured or the SBC card goes to standby state, reboot or offline state, a service is removed from SBC card, an event is generated by SBC. 4. When a large number of SIP/H.248 calls are ongoing and system is congested i.e. high CPU usage or high use of memory utilization, congestion event is generated at this point and when congestion is cleared means CPU usage comes to normal another event for congestion clear is generated. 5. When a service is configured on SBC application, its call policies are defined during the configuration like maximum number of calls, maximum call rates etc. If any of these policies is violated, an event for violation of service level agreement is generated. 6. When a radius server is attached/detached with SBC, a notification is generated to provide information of radius server type, IP address, port etc. 7. When an adjacency is attached/detached with SBC, a notification is generated to provide its information like the adjacency type and state. 8. When a H.248 controller is attached/detached with SBC to establish H.248 calls with SBC, a notification is generated to provide the information regarding the attached/detached H.248 controller like controller index, IP address, port, state etc. GLOSSARY SBC: Session Border Controller CSB: CISCO Session Border Controller CAC: Call Admission Control - protects voice traffic from the negative effects of other voice traffic and to keep excess voice traffic off the network. It is used to prevent congestion in Voice traffic. It is used in the Call Setup phase. RTP: Real Time Transport Protocol - defines a standardized packet format for delivering audio and video over the Internet. RTCP: Real Time Control Protocol - It is a sister protocol of the Real-time Transport Protocol (RTP). RTCP provides out-of-band control information for an RTP flow. It partners RTP in the delivery and packaging of multimedia data, but does not transport any data itself. It is used periodically to transmit control packets to participants in a streaming multimedia session. VMG: Virtual Media Gateway - introduced to bridge between different transmission technologies and to add service to end-user connections. Its architecture separates control and connectivity functions into physically separate network layers. VPN: Virtual Private Network - It is a communications network tunneled through another network, and dedicated for a specific network. Gate Id - Context Identifiers assigned uniquely to a SIP/H.248 call flows. Flow Pair Id: Stream Identifiers assigned uniquely to a SIP/H.248 call flows. Adjacency: An adjacency contains the system information to be transmitted to next HOP. SLA: Service Level Agreement - Service level agreement includes some call admission control policies which are defined during the SBC configurations like maximum number of calls, maximum call rates etc. Diameter Server: A Diameter Server is one that handles authentication, authorization and accounting requests for a particular realm. REFERENCES 1. CISCO Session Border Controller Documents and FAQ http://zed.cisco.com/confluence/display/SBC/SBC" REVISION "201012060000Z" DESCRIPTION "Added Notification csbQOSUnansweredCallRatioEvent, csbQOSUnansweredCallRatioClearEvent, csbQOSPercentPktLostEvent, csbQOSPercentPktLostClearEvent, csbQOSPercentPktDropEvent, csbQOSPercentPktDropClearEvent, csbQOSRoundTripDelayEvent, csbQOSRoundTripDelayClearEvent, csbQOSLocalJitterEvent, csbQOSLocalJitterClearEvent, csbQOSRemoteJitterEvent, csbQOSRemoteJitterClearEvent, csbQOSMoscqeEvent, csbQOSMoscqeClearEvent." REVISION "200808270000Z" DESCRIPTION "Changes to correct problem were csbSLACurrentUsage and csbSLAPolicyLimit was incorrectly defined as Integer32. Deprecated the following objects and notification. csbSLACurrentUsage csbSLAPolicyLimit csbSLAViolationNotifEnabled csbSLAViolation Created the following objects and notification csbSLACurrentUsageRev1 csbSLAPolicyLimitRev1 csbSLAViolationNotifEnabledRev1 csbSLAViolationRev1 Correct definition of csbAlarmTime object." REVISION "200805290000Z" DESCRIPTION "Initial version of the MIB module." ::= { ciscoMgmt 658 }
ciscoSessBorderCtrlrEventMIB MODULE-IDENTITY LAST-UPDATED "201012060000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO "Cisco Systems Customer Service Postal: 170 W Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS E-mail: [email protected]" DESCRIPTION "The main purpose of this MIB is to define the SNMP notifications and alarms generated by Session Border Controller application and used to send these notifications to SNMP manager application. Each of these event/notification is explained in detail in the MIB file. The SBC service is implemented on a service card on CISCO routers. SBC application offer functionalities like firewall/NAT traversal, media bridging, policy-based call routing, signaling protocol inter-working, call billing and some degree of Call Admission Control. SBC looks to play an essential role in full-scale commercial deployment of VoIP and integration into the existing PSTN. The Session Border Controller (SBC) enables direct IP-to-IP interconnect between multiple administrative domains for session-based services providing protocol inter-working, security, and admission control and management. The SBC is a voice over IP (VoIP) device that sits on the border of a network and controls call admission to that network. The primary purpose of an SBC is to protect the interior of the network from excessive call load and malicious traffic. Additional functions provided by the SBC include media bridging and billing services. Various types of notifications required for SBC applications are as follows: 1. When SIP/H2.48 calls are established and SBC application receives traffic (RTP/RTCP packets) from a source whose IP address or port is ambiguous, a source alert event is generated for the unwanted data packets received by SBC application. 2. Blacklisting is the process of matching inbound packets based on some simple parameters (for example source IP address) and preventing packets that match those parameters from being processed. SBC detects an attempt to disrupt traffic flowing through it. When a source is blacklisted in SBC application, an event is generated to provide information of the blacklisted source like its IP address, port, VPN address etc. 3. When there is a change in the state of any SBC service configured like a new SBC service is configured or the SBC card goes to standby state, reboot or offline state, a service is removed from SBC card, an event is generated by SBC. 4. When a large number of SIP/H.248 calls are ongoing and system is congested i.e. high CPU usage or high use of memory utilization, congestion event is generated at this point and when congestion is cleared means CPU usage comes to normal another event for congestion clear is generated. 5. When a service is configured on SBC application, its call policies are defined during the configuration like maximum number of calls, maximum call rates etc. If any of these policies is violated, an event for violation of service level agreement is generated. 6. When a radius server is attached/detached with SBC, a notification is generated to provide information of radius server type, IP address, port etc. 7. When an adjacency is attached/detached with SBC, a notification is generated to provide its information like the adjacency type and state. 8. When a H.248 controller is attached/detached with SBC to establish H.248 calls with SBC, a notification is generated to provide the information regarding the attached/detached H.248 controller like controller index, IP address, port, state etc. GLOSSARY SBC: Session Border Controller CSB: CISCO Session Border Controller CAC: Call Admission Control - protects voice traffic from the negative effects of other voice traffic and to keep excess voice traffic off the network. It is used to prevent congestion in Voice traffic. It is used in the Call Setup phase. RTP: Real Time Transport Protocol - defines a standardized packet format for delivering audio and video over the Internet. RTCP: Real Time Control Protocol - It is a sister protocol of the Real-time Transport Protocol (RTP). RTCP provides out-of-band control information for an RTP flow. It partners RTP in the delivery and packaging of multimedia data, but does not transport any data itself. It is used periodically to transmit control packets to participants in a streaming multimedia session. VMG: Virtual Media Gateway - introduced to bridge between different transmission technologies and to add service to end-user connections. Its architecture separates control and connectivity functions into physically separate network layers. VPN: Virtual Private Network - It is a communications network tunneled through another network, and dedicated for a specific network. Gate Id - Context Identifiers assigned uniquely to a SIP/H.248 call flows. Flow Pair Id: Stream Identifiers assigned uniquely to a SIP/H.248 call flows. Adjacency: An adjacency contains the system information to be transmitted to next HOP. SLA: Service Level Agreement - Service level agreement includes some call admission control policies which are defined during the SBC configurations like maximum number of calls, maximum call rates etc. Diameter Server: A Diameter Server is one that handles authentication, authorization and accounting requests for a particular realm. REFERENCES 1. CISCO Session Border Controller Documents and FAQ http://zed.cisco.com/confluence/display/SBC/SBC" REVISION "201012060000Z" DESCRIPTION "Added Notification csbQOSUnansweredCallRatioEvent, csbQOSUnansweredCallRatioClearEvent, csbQOSPercentPktLostEvent, csbQOSPercentPktLostClearEvent, csbQOSPercentPktDropEvent, csbQOSPercentPktDropClearEvent, csbQOSRoundTripDelayEvent, csbQOSRoundTripDelayClearEvent, csbQOSLocalJitterEvent, csbQOSLocalJitterClearEvent, csbQOSRemoteJitterEvent, csbQOSRemoteJitterClearEvent, csbQOSMoscqeEvent, csbQOSMoscqeClearEvent." REVISION "200808270000Z" DESCRIPTION "Changes to correct problem were csbSLACurrentUsage and csbSLAPolicyLimit was incorrectly defined as Integer32. Deprecated the following objects and notification. csbSLACurrentUsage csbSLAPolicyLimit csbSLAViolationNotifEnabled csbSLAViolation Created the following objects and notification csbSLACurrentUsageRev1 csbSLAPolicyLimitRev1 csbSLAViolationNotifEnabledRev1 csbSLAViolationRev1 Correct definition of csbAlarmTime object." REVISION "200805290000Z" DESCRIPTION "Initial version of the MIB module." ::= { ciscoMgmt 658 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.9.9.658.0 | ciscoSessBorderCtrlrMIBNotifs | 24 | 24 | None |
| 1.3.6.1.4.1.9.9.658.1 | ciscoSessBorderCtrlrMIBObjects | 79 | 158 | None |
| 1.3.6.1.4.1.9.9.658.2 | ciscoSessBorderCtrlrMIBConform | 2 | 23 | None |
To many brothers! Only 100 nearest brothers are shown.
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| ... | ||||
| 1.3.6.1.4.1.9.9.610 | ciscoLwappRogueMIB | 3 | 78 | This MIB is intended to be implemented on all those devices operating as Central Controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.611 | ciscoLwappDot11ClientCCXTextualConventions | 0 | 0 | This module defines the textual conventions used throughout the Cisco enterprise MIBs designed for implementation on Central Cont… |
| 1.3.6.1.4.1.9.9.612 | ciscoLwappDot11MIB | 3 | 17 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.613 | ciscoEvcMIB | 3 | 156 | Metro Ethernet services can support a wide range of applications and subscriber needs easily, efficiently and cost-effectively. … |
| 1.3.6.1.4.1.9.9.614 | ciscoLwappDot11LdapMIB | 3 | 33 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.615 | ciscoLwappRrmMIB | 3 | 28 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.616 | ciscoLwappMeshMIB | 3 | 121 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.617 | ciscoLwappMeshStatsMIB | 4 | 98 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.618 | ciscoLwappSysMIB | 3 | 163 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.619 | ciscoLwappLocalAuthMIB | 3 | 53 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.620 | ciscoLwappMeshBatteryMIB | 3 | 34 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.621 | ciscoH324DialControlMIB | 2 | 34 | This MIB module enhances the IETF Dial Control MIB (RFC2128) by providing H.324 call information over a telephony network. ITU-T R… |
| 1.3.6.1.4.1.9.9.622 | ciscoLwappDot11ClientTsMIB | 3 | 34 | This MIB is intended to be implemented on all those devices operating as Central controllers, that terminate the Light Weight Acc… |
| 1.3.6.1.4.1.9.9.623 | ciscoLwappCdpMIB | 3 | 51 | This MIB is intended to be implemented on all those devices operating as Central Controllers (CC) that terminate the Light Weight… |
| 1.3.6.1.4.1.9.9.624 | ciscoIpSlaTCMIB | 0 | 0 | This MIB contains textual conventions used by CISCO IPSLA MIBs. Acronyms: FEC: Forward Equivalence Class LPD: Label Path Discovery L… |
| 1.3.6.1.4.1.9.9.626 | ciscoDot11HtMacMIB | 3 | 40 | This MIB is intended to be implemented on Cisco's WLAN devices that provide the wired uplink to wireless clients through the high… |
| 1.3.6.1.4.1.9.9.627 | ciscoDot11RadarMIB | 3 | 25 | This MIB module is for IEEE 802.11a/h Root device, i.e. Access Point (AP) or Root Bridge. This MIB allows dynamic frequency selec… |
| 1.3.6.1.4.1.9.9.628 | ciscoServiceControlSubscribersMIB | 3 | 37 | This MIB provides global and specific information on subscribers managed by a service control entity, which is a network element … |
| 1.3.6.1.4.1.9.9.630 | ciscoTelnetServerMIB | 3 | 34 | MIB module for displaying and configuring Telnet related features in a device. Telnet is a program to log into another computer o… |
| 1.3.6.1.4.1.9.9.631 | ciscoServiceControlLinkMIB | 3 | 21 | This MIB module provides information about the status and configuration of links used by service control entities. The link on a … |
| 1.3.6.1.4.1.9.9.632 | ciscoSmeMIB | 3 | 54 | MIB module to manage Storage Media Encryption (SME) service. SME is an encryption service provided by an encryption node residing… |
| 1.3.6.1.4.1.9.9.633 | ciscoIpSlaAutoMIB | 3 | 57 | This module defines the MIB for IP SLA Automation. IP SLA Automation consists of the following: 1. Use of grouping - Group is an … |
| 1.3.6.1.4.1.9.9.634 | ciscoServiceControlTpStatsMIB | 3 | 39 | This MIB provides information and statistics on the traffic processor(s) of a service control entity, which is a network element … |
| 1.3.6.1.4.1.9.9.635 | ciscoIpSlaJitterMIB | 3 | 57 | This MIB module defines templates for IP SLA operations of UDP Jitter and ICMP Jitter. The UDP Jitter operation is designed to me… |
| 1.3.6.1.4.1.9.9.636 | ciscoIpSlaEchoMIB | 3 | 71 | This MIB module defines the templates for IP SLA operations of ICMP echo, UDP echo and TCP connect. The ICMP echo operation measu… |
| 1.3.6.1.4.1.9.9.637 | ciscoServiceControlRdrMIB | 3 | 56 | This MIB module defines objects describing statistics and configuration relating to the Raw Data Record Formatter running on a se… |
| 1.3.6.1.4.1.9.9.638 | ciscoAgwMIB | 3 | 324 | This module manages Cisco's WiMAX ASN Gateway (ASN-GW). A WiMAX network supports wireless data communication through WiMAX radio … |
| 1.3.6.1.4.1.9.9.639 | ciscoOtnIfMIB | 3 | 137 | This MIB module defines the managed objects for physical layer characteristics of DWDM optical channel interfaces and performanc… |
| 1.3.6.1.4.1.9.9.640 | ciscoImageLicenseMgmtMIB | 3 | 31 | The MIB module for managing the running image level of a Cisco device. Cisco's licensing mechanism provides flexibility to run a … |
| 1.3.6.1.4.1.9.9.642 | ciscoBridgeDomainMIB | 3 | 24 | A bridge domain is one of the means by which it is possible to define a broadcast domain on a bridging device. It is an alternati… |
| 1.3.6.1.4.1.9.9.643 | ciscoTelepresenceMIB | 3 | 119 | The MIB module defines the managed objects for a Telepresence system. Telepresence refers to a set of technologies which allow a p… |
| 1.3.6.1.4.1.9.9.644 | ciscoTelepresenceCallMIB | 3 | 178 | The MIB module defines the managed objects for Telepresence calls. Telepresence refers to a set of technologies which allow a pers… |
| 1.3.6.1.4.1.9.9.645 | ciscoEtherExtMIB | 3 | 18 | The MIB module to describe generic objects for ethernet-like network interfaces. This MIB provides ethernet-like network interfac… |
| 1.3.6.1.4.1.9.9.646 | ciscoAonStatusMIB | 3 | 80 | This MIB module defines managed objects that facilitate the management of AON node. The information available through this MIB in… |
| 1.3.6.1.4.1.9.9.647 | ciscoGgsnExtMIB | 3 | 212 | This MIB module extends the CISCO-GGSN-MIB. This MIB module manages the Gateway GPRS Support Node (GGSN) devices. A GGSN device pr… |
| 1.3.6.1.4.1.9.9.648 | ciscoVirtualInterfaceMIB | 2 | 32 | The MIB module for creation and deletion of Virtual Interfaces and Virtual Interface Groups. In addition to this MIB, interface … |
| 1.3.6.1.4.1.9.9.650 | ciscoL4L7moduleRedundancyMIB | 3 | 71 | The L4-7 SLB devices are used for scaling websites, building web enabled applications, and migrating to web services. The followin… |
| 1.3.6.1.4.1.9.9.651 | ciscoCommonRolesExtMIB | 3 | 37 | A MIB Module for managing the roles that are common between access methods like Command Line Interface (CLI), SNMP and XML interf… |
| 1.3.6.1.4.1.9.9.652 | ciscoSwitchStatsMIB | 3 | 106 | The MIB module provides management information for configuration and monitoring of traffic statistics on Cisco's switching device… |
| 1.3.6.1.4.1.9.9.653 | ciscoAdmissionPolicyMIB | 3 | 36 | This MIB module defines managed objects that facilitate the management of policies upon host(s) admission to a network. The inform… |
| 1.3.6.1.4.1.9.9.654 | ciscoMabMIB | 3 | 20 | MIB module for monitoring and configuring MAC Authentication Bypass (MAB) feature in the system. MAC Auth Bypass feature provides… |
| 1.3.6.1.4.1.9.9.655 | ciscoDigitalMediaSystemsMIB | 3 | 195 | Acronyms and Definitions The following acronyms and terms are used in this document: DMS: Digital Media Systems DAM: Digital As… |
| 1.3.6.1.4.1.9.9.656 | ciscoAuthFrameworkMIB | 3 | 117 | MIB module for Authentication Framework in the system. Authentication Framework provides generic configurations for authenticatio… |
| 1.3.6.1.4.1.9.9.657 | ciscoSbcCallStatsMIB | 3 | 201 | The main purpose of this MIB is to define the statistics information for Session Border Controller application. The statistics ar… |
| 1.3.6.1.4.1.9.9.660 | ciscoNportVirtualizationMIB | 3 | 19 | The MIB module for the management of N_port Virtualization or NPV within the framework of Cisco's N_port virtualization (NPV) Arc… |
| 1.3.6.1.4.1.9.9.661 | ciscoWan3gMIB | 3 | 378 | This MIB module provides network management support for Cisco cellular 3G WAN products. *** ABBREVIATIONS, ACRONYMS, AND SYMBOLS … |
| 1.3.6.1.4.1.9.9.662 | ciscoCbpTcMIB | 0 | 0 | This MIB module defines textual conventions used by the CISCO-CBP-BASE-CFG-MIB, CISCO-CBP-BASE-MON-MIB, and any MIB modules exten… |
| 1.3.6.1.4.1.9.9.663 | ciscoSwitchHardwareCapacityMIB | 3 | 141 | This MIB module defines the managed objects for hardware capacity of Cisco switching devices. The hardware capacity information c… |
| 1.3.6.1.4.1.9.9.664 | ciscoMmodalContactAppsMIB | 3 | 359 | The Cisco Unified Multi-Modal Contact Applications (MMCA) platform is a highly scalable, modular, extensible, open and secure pl… |
| 1.3.6.1.4.1.9.9.667 | ciscoServiceControllerMIB | 2 | 31 | This MIB module defines objects describing traffic controllers used by a service control entity. A service control entity is a ne… |
| 1.3.6.1.4.1.9.9.668 | ciscoP2PIfMIB | 3 | 16 | The Point to Point Interface MIB module. This MIB manages the generic objects for Serial link or SONET/SDH like point to point ne… |
| 1.3.6.1.4.1.9.9.669 | ciscoCdmaPdsnExtMIB | 3 | 178 | This MIB is an extension to the CISCO-CDMA-PDSN-MIB. A CDMA network supports wireless data communication through 3G CDMA radio acc… |
| 1.3.6.1.4.1.9.9.670 | ciscoReportIntervalTcMIB | 0 | 0 | CISCO-REPORT-INTERVAL-TC-MIB |
| 1.3.6.1.4.1.9.9.672 | ciscoMobilityTapMIB | 3 | 24 | This module manages Cisco's intercept feature for Mobility Gateway Products. This MIB is used along with CISCO-TAP2-MIB MIB to int… |
| 1.3.6.1.4.1.9.9.673 | ciscoFCoEMIB | 2 | 45 | This MIB module is for configuring and monitoring Fibre Channel over Ethernet (FCoE) related entities. This MIB defines the Virtu… |
| 1.3.6.1.4.1.9.9.679 | ciscoIeee8021CfmExtMIB | 3 | 55 | A MIB module for extending the IEEE8021-CFM-MIB and IEEE8021-CFM-V2-MIB to add objects which provide additional information about… |
| 1.3.6.1.4.1.9.9.680 | ciscoNhrpExtMIB | 3 | 36 | This MIB module is an extension of the NHRP MIB module as defined in RFC 2677. It defines notifications associated with critical … |
| 1.3.6.1.4.1.9.9.683 | ciscoEnergywiseMIB | 3 | 162 | The MIB is used to manage and optimize power usage in networks. Cisco EnergyWise is a specification of data, discovery and protoco… |
| 1.3.6.1.4.1.9.9.686 | ciscoLwappInterfaceMIB | 3 | 27 | ciscoLwappInterfaceMIB MODULE-IDENTITY LAST-UPDATED "200901090000Z" ORGANIZATION "Cisco Systems Inc." CONTACT-INFO "Cisco Syste… |
| 1.3.6.1.4.1.9.9.688 | ciscoFlowMonitorTcMIB | 0 | 0 | This MIB module defines textual conventions used by the MIB modules defining objects describing flow monitoring. GLOSSARY ========… |
| 1.3.6.1.4.1.9.9.689 | ciscoSlbDfpMIB | 3 | 22 | This MIB reports the congestion status of the real server. A server can be in congested state due to high memory consumption, hig… |
| 1.3.6.1.4.1.9.9.690 | ciscoMobilePolicyChargingControlMIB | 3 | 143 | Mobile PCC Infrastructure built on top of Policy Shim Layer, is a common interface to send and receive PCC related messages for a… |
| 1.3.6.1.4.1.9.9.691 | ciscoEthernetFabricExtenderMIB | 3 | 23 | The MIB module for configuring one or more fabric extenders to connect into a core switch. Since fabric extenders might not be m… |
| 1.3.6.1.4.1.9.9.692 | ciscoFlowMonitorMIB | 4 | 195 | This MIB module defines objects that describe flow monitoring. A typical application of this MIB module will facilitate monitorin… |
| 1.3.6.1.4.1.9.9.693 | ciscoServiceControlAttackMIB | 3 | 55 | This MIB provides data related to different types of attacks detected by a service control entity. A service control entity is a … |
| 1.3.6.1.4.1.9.9.694 | ciscoCtsTcMIB | 0 | 0 | This module defines the textual conventions used within Cisco Trusted Security framework. |
| 1.3.6.1.4.1.9.9.695 | ciscoGtcapMIB | 3 | 194 | The MIB for Transaction Capabilities(TCAP) messages transported over Signalling System No. 7 (SS7) Network via Cisco IP Transfer P… |
| 1.3.6.1.4.1.9.9.696 | ciscoBootHwDiagsMIB | 3 | 22 | This MIB is used to configure those devices that support boot-time hardware diagnostics. It provides the reports about the respe… |
| 1.3.6.1.4.1.9.9.697 | ciscoIpCbrMetricsMIB | 4 | 42 | This MIB module defines objects that describe the a set of metrics used to measure the quality of a IP CBR traffic flow. An IP CB… |
| 1.3.6.1.4.1.9.9.698 | ciscoObmiMIB | 3 | 60 | The On-Board Management Interface (OBMI) provides an out-of-band communications channel (in Cisco terms: a console port), that is… |
| 1.3.6.1.4.1.9.9.699 | ciscoMdiMetricsMIB | 4 | 46 | This MIB module defines objects that describe the Media Delivery Index (MDI). The MDI [RFC4445] measurement describes the qualit… |
| 1.3.6.1.4.1.9.9.700 | ciscoCableL2vpnMIB | 3 | 28 | This MIB module defines managed objects that facilitate the management of Cisco devices complying to the DOCSIS L2VPN Feature for… |
| 1.3.6.1.4.1.9.9.701 | ciscoSeuMitigationMIB | 3 | 51 | This MIB reports the status of non-automatic and automatic, rate-adaptive Single Event Upset (SEU) mitigation algorithms and adju… |
| 1.3.6.1.4.1.9.9.702 | ciscoSanBaseSvcMIB | 3 | 57 | Common MIB module to manage services in Storage Area Network (SAN). Service is deployed on service nodes on multiple switches fo… |
| 1.3.6.1.4.1.9.9.703 | ciscoRtpMetricsMIB | 4 | 61 | This MIB module defines objects that describe the quality metrics of RTP streams, similar to those described by an RTCP Receiver … |
| 1.3.6.1.4.1.9.9.706 | ciscoInterfaceXcvrMonitorMIB | 3 | 33 | A MIB module that provides monitoring information about the transceivers plugged into interface on a system. |
| 1.3.6.1.4.1.9.9.708 | ciscoContentDeliveryStreamingMIB | 2 | 30 | This MIB instrumentation is for managing the Content Delivery and Streaming functionality on Cisco devices. Contents are ingested… |
| ... | ||||