PDF user manual for CopperEdge 150

&3(0HVVDJH/RJ7DEOHIf you need to perform diagnostics for an IAD CPE (such as aCR408, CR508, or CR508T), you can log debug messages to aCPE log table, which you can view from the Craft prompt.To log messages, you will use two MIB groups: cmCpeIADTableand cmCpeLogTable.• cmCpeIADTable—Create and delete the log table entriesusing the LogAction, LogType, LogLevel, andLogDuration objects.• cmCpeLogTable—View up to 1000 logged messageentries. The first entry contains the oldest information.In the following examples, we will turn on message logging andgenerate some messages.To start logging messages:1. First check the cmCpeBoardTable to see if the CPEsupports cmCpeLogTable.CRAFT> get cmcpeboard [cpe:1.5.2] groupmapGroup: cmCPEBoardTableInstance: [CPE:1.5.2]GroupMap= 3a.40.39.91.92.93.94.9b.a5.a0.a7In the GroupMap, a5 indicates cmCpeLogTable.2. Then check the cmCpeIADTable to see how theLogAction object is set.CRAFT> geta cmcpeiadIndex CurrentIpAddr CurrentCAIpAddr SavedIpAddrSavedCAIpAddr NumVoicePorts NumConnections CommandTOSByte LogAction LogType LogLevelLogDuration TotalMsgsLogged Trace1Mask Trace2MaskInstance: [CPE:1.13.2]CPE:1.13.2 10.10.1.5 10.10.1.1 10.10.1.510.10.1.1 8 16 None10 None 0 030 0 0 03. Since LogAction=None, there should be no messageslogged in the cmCpeLogTable.CRAFT> geta cmcpelogNo more instances4. Turn on the debug message logging feature for theduration of the timer, set in the LogDuration object:CRAFT> set cmcpeiad [cpe:1.5.2] logaction=startdebugSet SuccessfulWhen the timer expires, the LogAction object isautomatically set to StopDebug and messages are nolonger logged.&RSSHU(GJH,QVWDOODWLRQDQG2SHUDWLQJ*XLGH