Chapter11. Logging
Resource Monitoring
YourTelecommuting Module can send SNMP traps when usage passes certain levels. Set the levelson this page.
Thetrap receivers are configured on the SNMP page.
Foreach usage, there is an Alarm by and a Resume by level. When the usage hits the Alarm by level, the
TelecommutingModule sends a trap about this and locks the trap sending for that usage, which means that as long
asthe level stays high, no more traps are sent. When the level goes down to below the Resume by level, the lock is
released.Next time the Alarm by level is reached, a new trap is sent.
Toavoid excessive trap sending, it is recommended that the Alarm by and Resume by level for a resource are not
settoo close.
SIP Sessions Trap Levels
Enterthe SIP sessions levels here. When the number of SIP sessions reaches the Alarm by level, an SNMP trap is
sent.
SIP User Registrations Trap Levels
Enterthe SIP user registrations levels here. When the number of registered SIP users reaches the Alarm by level, an
SNMPtrap is sent.
CPU Load Trap Levels
Enterthe CPU load levels here. When CPU usage increases above the Alarm by limit, an SNMP trap is sent.
Memory Usage Trap Levels
Enterthe memory usage levels here. When memory usage increases above the Alarm by limit, an SNMP trap is sent.
Save
Savesthe Resource Monitoring configuration to the preliminary configuration.
Cancel
Revertsall of the above fields to their previous configuration.
Logging Configuration
Your3Com VCX IP Telecommuting Module generates log messages for various events and for the trafficto and
throughthe Telecommuting Module. Here, you select log classes to state what to do with the log messages.
Whenan IP packet is received by the Telecommuting Module, a log message is generated, containing sender and
receiverIP addresses and other information such as the protocol used and if the packet was allowed, rejected or
discarded.The Telecommuting Module then uses the log settings for Configuration Transport and Log class for
non-SIPpackets to know how to process the log message.
105