CISCO-CALLHOME-MIB :: ccmAlertGroupPattern

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsCISCO-CALLHOME-MIBccmAlertGroupPattern

ccmAlertGroupPattern

Module: CISCO-CALLHOME-MIB

OID (symbolic): CISCO-CALLHOME-MIB::ccmAlertGroupPattern

OID (numeric): 1.3.6.1.4.1.9.9.300.1.1.30.4.1.1

Node type: OBJECT-TYPE

Type: SnmpAdminString

Access: not-accessible

Description: The object contains a regular expression.

Regular Expressions:
-------------------

A regular expression is a pattern (a phrase, number, or more
complex pattern):

Regular expressions are case sensitive and allow for complex
matching requirements. Simple regular expressions include
entries like Serial, misses, or 138.

Complex regular expressions include entries like 00210... , 
(is ), or [Oo]utput.

Some Practical examples of regular expressions:
----------------------------------------------
The examples correspond with the various ways that you can
use regular expressions in your configurations.

For example, syslog messages on IOS look as follows:
a.
--
2004 Jul 21 13:26:55 %SYS-5-REDUNDANTCLOCK_OK: Redundant
clock recovered
b.
--
2004 Jul 21 13:26:59 %SYS-5-REDUNDANTCLOCK_FAIL: Redundant
clock failed
c.
--
2004 Jul 26 16:53:47 %MGMT-5-LOGIN_FAIL:User failed to log
in from 171.69.48.75 via Telnet - max attempt reached


A pattern of REDUNDANTCLOCK.* would cause all the syslogs 
with severity greater than specified by
ccmProfileAlertGroupSeverity
and having a pattern  REDUNDANTCLOCK followed by
REDUNDANTCLOCK followed by any number of occurrences (*)
of any character (.) resulting in corresponding Call Home
messages being generated for syslog alert group.

So both messages a and b in above examples will be resulting
in issuance of Call Home messages for the pattern 
REDUNDANTCLOCK.*.

Next, a pattern of ^Telnet would cause all the syslogs 
with severity greater than specified by
ccmProfileAlertGroupSeverity and having a string starting 
and with Telnet resulting in corresponding Call Home
messages being generated for syslog alert group.

A pattern of LOGIN_FAIL$ would cause all the syslogs with
severity greater than specified by 
ccmProfileAlertGroupSeverity and having a string ending in
LOGIN_FAIL resulting in corresponding Call Home messages
being generated for syslog alert group.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.300ciscoCallHomeMIBCISCO-CALLHOME-MIB
1.3.6.1.4.1.9.9.300.1ciscoCallHomeMIBObjectsCISCO-CALLHOME-MIB
1.3.6.1.4.1.9.9.300.1.1ccmCallHomeConfigurationCISCO-CALLHOME-MIB
1.3.6.1.4.1.9.9.300.1.1.30ccmCallHomeAlertGroupCfgCISCO-CALLHOME-MIB
1.3.6.1.4.1.9.9.300.1.1.30.4ccmPatternAlertGroupTableCISCO-CALLHOME-MIB
1.3.6.1.4.1.9.9.300.1.1.30.4.1ccmPatternAlertGroupEntryCISCO-CALLHOME-MIB
1.3.6.1.4.1.9.9.300.1.1.30.4.1.1ccmAlertGroupPatternCISCO-CALLHOME-MIB