System Message Guide for Cisco IOS XE 17.16.x

<!DOCTYPE html> <html xmlns:fb="//www.facebook.com/2008/fbml" xmlns:og="//opengraphprotocol.org/schema/" lang="en" xml:lang="en" class="no-touch no-js"> <head> <meta charset="utf-8"> <meta name="HandheldFriendly" content="True" /> <meta name="MobileOptimized" content="320" /> <meta name="viewport" content="width=device-width, initial-scale=1.0" /> <meta name="rei" content="3/2/2022 10.39am est" /> <script tyle="text/javascript" src="/content/dam/cdc/j/cdcrSwitch.js"></script> <script type="text/javascript"> if (typeof cdc === "undefined"){ cdc = {}; } cdc.localizedLang="en/us"; if (window.cdcext === undefined) { window.cdcext = {}; } cdcext.customEnvironment = "prod"; if (window.cdclocale === undefined) { window.cdclocale = {}; } cdclocale.locale = cdc.localizedLang=="en/us"?"en_us":cdc.localizedLang; </script> <script src="/c/dam/cdc/t/ctm-core.js"></script> <script> window['adrum-start-time'] = new Date().getTime(); window.environ = "prod" ; </script> <script> if (window.cpe === undefined) { window.cpe = {}; } cpe.accountName = "prod"; cpe.config = ["cinf","dsc","pps"]; cpe.hideMethod = "elements"; window.targetGlobalSettings = JSON.parse('{\x22timeout\x22:4000}'); window.targetPageParamsAll = () => JSON.parse('{\x22entity\x22:\x22{\\\x22id\\\x22:\\\x221734921215167142\\\x22,\\\x22categoryId\\\x22:\\\x22Products,Cisco IOS and NX\u002DOS Software,TSD Products System Message Guide\\\x22}\x22}'); const bullseyeLibrary = `/etc.clientlibs/cisco-cdc/clientlibs/clientlib-external/resources/external/bullseye.js`; import(bullseyeLibrary); </script> <script src="/etc.clientlibs/cisco-cdc/clientlibs/clientlib-external/resources/regional-mbox/regional-mbox.js"></script> <title>System Message Guide for Cisco IOS XE 17.16.x - Cisco</title> <meta name="format-detection" content="telephone=no"> <meta http-equiv="Content-type" content="text/html;charset=UTF-8" /> <meta name="description" content="Quick Start Guide: System Message Guide for Cisco IOS XE 17.16.x" /> <meta name="title" content="System Message Guide for Cisco IOS XE 17.16.x" /> <meta name="documentId" content="1734921214759141" /> <meta name="templateName" content="eot" /> <meta name="SecondaryPID" content="AZR-MKPL-C8KV-2H,E2N-SDWAN-P-T1-G-A,L-CSR-SVC-C8KV-ES=,E2N-SDWAN-P-T2-G-P,E3N-ENTWAN-C-T2-E,SC8KV8SQUK9-1716,E2N-SDWAN-C-T3-G-A,E3N-ENTWAN-C-T0-E,E3N-ENTWAN-C-T4-A,DNA-P-T2-A-3Y,E2N-SDWAN-C-T2-G-A,E2N-SDWAN-P-T2-G-A,E2N-SDWAN-P-T1-G-P,E3N-MGMT-C-C11TG,E2N-SDWAN-P-T4-G-A,E3N-ENTWAN-P-T0-E,E3N-ENTWAN-P-T4-A,E3N-ENTWAN-P-T2-E,E3N-ENWAN-P-T2HA-E,E3N-ENWAN-C-T0HA-E,E2N-SDWAN-C-T1-G-A,E2N-SDWAN-P-T5-G-A,E2N-SDWAN-P-T3-G-A,E2N-SDWAN-C-T0-G-A,C8000V-HSEC=,L-DNA-C8000-MOD,E2N-SDWAN-P-T3-G-P,C8000V-PLR=,E3N-ENWAN-C-T2HA-E,8000-SW-LICENSE-W,E3N-ENWAN-P-T0HA-E,SC8KV8STUK9-179,L-DNA-C8000V,8000-S-ROUTER-EMU,SC8KVUK9-1716,SC8KVUK9-1715,SC8KVUK9-1712,SC8KVUK9-1713,E3N-ENTWAN-C-T1-E,E3N-ENTWAN-C-T5-A,SC8KVUK9-1711,E3N-ENWAN-P-T1HA-E,8000-SW-SERVICE=,E2N-SDWAN-C-T1-G-P,E3N-ENWAN-C-T1HA-E,M2USB-64G,E3N-ENTWAN-P-T1-E,E3N-ENTWAN-P-T5-A,8800-LC-48H-O-TRK,E2N-SDWAN-C-T2-G-P,SC8KV8SEQUK9-1716,E2N-SDWAN-C-T5-G-A,M2USB-64G=,SC8KV8STUK9-1712,SC8KV16SQUK9-1716,E2N-SDWAN-P-T0-G-A,C8000V-HSEC,SC8KV8STUK9-1713,SC8KV8STUK9-1715,E2N-SDWAN-C-T3-G-P,E2N-SDWAN-C-T4-G-A,CDNA-E-C9140,SWAP1700-RCOVRY-K9,S3G3K9W7-15303JF,SWAP2700-RCOVRY-K9,AIR-DCL-A,AIR-DCL-C-E1,AIR-DCL-A-T,AIR-DCL-C-A1,AIR-DCL-E-T,CDNA-A-C9140,AIR-DCL-P,AIR-DCL-C-P1,PI-LFAS-AP-R,AIR-SW-82,SW-SRE-WLC-7.2-K9,CDNA-P-C9140,AIR-DCL-E,WLC-AP-R,DNA-P-10M-A-3Y,DNA-P-50M-A-3Y,C1DNA-C-1G-A-1Y,C1DNA-C-20M-A-5Y,DNA-C-500M-A-5Y,C1DNA-C-500M-A-1Y,SSP-CDSDR-B,C1117-4PLTELA,DNA-P-T2-E-3Y,ASR1002-HX-RF,DNA-C-1G-A-5Y,ISR4351/K9-RF,C1DNA-P-10G-A-3Y,ISR4331/K9-RF,DSTACK-MSP-T2-A,ENCS5412/K9-RF,SL-CSR-5G-NE-E,SL-CSR-2.5G-NE-E,ISR4331/K9++,C1DNA-P-1G-A-5Y,DNA-P-500M-A-5Y,DNA-C-20M-A-3Y,DNA-C-100M-E-1Y,DNA-C-10G-A-5Y,DSTACK-MTE,SL-CSR-100M-NA-A,C1DNA-C-1G-A-3Y,DNA-C-100M-E-3Y,VP-SW-SSPT,VP-SW-ELA,C1DNA-C-500M-A-3Y,ASR1001-HX-WS,SDWAN-PM,DNA-UMB-SIGE-K9-1Y,IR1101-A-DNA,DNA-C-20M-A-5Y,DSTACK-MSP-T1-A,C1DNA-C-100M-A-5Y,VP-SW-PPTL,DNA-P-500M-A-3Y,DNA-C-10G-A-3Y,C1DNA-C-1G-A-5Y,DNA-C-500M-A-1Y,VEDGE-2000-AC-K9,DNA-P-1G-A-5Y,SISR44V2UCMK9-172,DNA-P-10G-A-3Y,C1DNA-C-50M-A-1Y,DNA-C-500M-E-5Y,DNA-C-T0-E-3Y,SL-CSR-1G-NE-E,ISR4331/K9-WS,SDWAN-DNA-A,C1DNA-C-500M-A-5Y,SISRVUCMK9-1610,DNA-C-20M-E-3Y,DNA-C-50M-E-1Y,C1117-4PLTELA-WS,DNA-C-10M-A-5Y,CX-MI-DNAC-NET,C1DNA-C-100M-A-3Y,C1DNA-C-20G-A-3Y,SISRVUCMK9-169,C1DNA-C-10G-A-5Y,ASR1002-HX-WS,SL-CSR-250M-NA-A,C1DNA-P-100M-A-3Y,SL-CSR-500M-NA-A,C8KV-PLR-T3-A,DNA-C-20G-A-3Y,SSP-CDSDR,C1DNA-P-10M-A-3Y,DNA-P-10M-A-5Y,DNA-P-10G-A-5Y,DNA-C-500M-A-3Y,C1DNA-C-20M-A-3Y,ENCS5412/K9,DNA-P-T2-E-5Y,DNA-UMB-SIGE-K9-5Y,DNA-C-20M-E-5Y,DNA-C-50M-E-3Y,C1DNA-P-10G-A-5Y,ISR4351/K9++,C1DNA-C-100M-A-1Y,C1DNA-C-20G-A-1Y,DNA-C-20G-A-1Y,C1DNA-C-20M-A-1Y,IR1101-E-PF,ISR4331-DNA,C1DNA-P-100M-A-5Y,DNA-C-20M-A-1Y,C8KV-PLR-T2-A,SISR44V2UCMK9-1611,C1DNA-P-1G-A-3Y,C1DNA-P-10M-A-5Y,PNP-CAP-FEDRAMP,DNA-P-20M-A-3Y,DNA-P-100M-A-3Y,CX-MI-SD-WAN-NET,DNA-P-T1-E-3Y,C1DNA-C-50M-A-5Y,DNA-C-500M-E-1Y,C1DNA-C-10M-A-5Y,ISR4321/K9-RF,DNA-C-1G-E-1Y,C1DNA-P-20M-A-5Y,DNA-C-10M-E-5Y,DNA-C-50M-A-1Y,C1117-4PLTEEA-RF,SL-CSR-5G-NA-A,DNA-C-50M-E-5Y,L-C8KV-T0-A,C1DNA-C-10G-A-1Y,DNA-C-10M-A-1Y,C8KV-PLR-T1-A,DNA-C-100M-A-5Y,SL-CSR-100M-NE-E,SL-CSR-2.5G-NA-A,C1117-4PLTEEA,DNA-P-1G-A-3Y,DNA-C-500M-E-3Y,DNA-C-T0-E-5Y,DNA-P-T1-E-5Y,C1DNA-C-50M-A-3Y,C1DNA-C-10M-A-3Y,C1111-8P-WS,DNA-P-100M-A-5Y,DNA-C-1G-E-3Y,C1DNA-P-20G-A-3Y,DNA-C-50M-A-3Y,DNA-C-20M-E-1Y,ASR1002-X-RF,C1DNA-C-10G-A-3Y,VP-SW-NFR,L-C8KV-T1-A,C1DNA-C-20G-A-5Y,SL-CSR-1G-NA-A,C8KV-PLR-T0-A,IR1101-A-PF,DNA-C-10M-A-3Y,DNA-C-20G-A-5Y,C1DNA-P-20M-A-3Y,VP-SW-NELA,C1DNA-P-500M-A-3Y,DNA-C-100M-E-5Y,C1117-4P,SSP-CDCS-B,DNA-P-20G-A-3Y,ISR4351/K9-WS,DNA-C-1G-A-1Y,DNA-C-1G-E-5Y,DNA-C-50M-A-5Y,CISCO_VMANAGE,C1DNA-P-20G-A-5Y,C1111-8PLTEEA-DNA,DNA-P-T0-E-5Y,DNA-C-T2-E-5Y,IOSXE-CTRL-MODE,DNA-C-10M-E-1Y,IR1101-E-DNA,DNA-C-10G-A-1Y,L-C8KV-T2-A,C1DNA-C-10M-A-1Y,C1117-4P-WS,DNA-C-T1-E-3Y,C1DNA-P-50M-A-3Y,DNA-C-100M-A-1Y,SL-CSR-250M-NE-E,DNA-P-20G-A-5Y,DNA-P-20M-A-5Y,C1DNA-P-500M-A-5Y,ASR1002-X-WS,SSP-CD-SDR,SL-CSR-500M-NE-E,DNA-C-1G-A-3Y,VP-SW-STD,ASR1001-X-WS,SDWAN-PROMO,DNA-P-T0-E-3Y,DNA-C-T2-E-3Y,DNA-C-10M-E-3Y,ISR4331-DNA-WS,DSTACK-MSP-T3-A,ISR4321/K9-WS,ASR1001-HX-RF,L-C8KV-T3-A,DNA-C-T1-E-5Y,PNP-CAP-DOD-IL5,DNA-C-100M-A-3Y,DNA-P-50M-A-5Y,VP-SW-POC,C1DNA-P-50M-A-5Y" /> <meta property="fb:app_id" content="156494687694418" /> <meta name="ioContentSource" content="WEM" /> <meta name="concept" content="Cisco IOS XE 17" /> <meta name="secondaryConcept" content="Cisco IOS XE 17.16.1" /> <meta name="secondaryConcept" content="Cisco Catalyst 9200 Series Switches" /> <meta name="secondaryConcept" content="Cisco Catalyst 9300 Series Switches" /> <meta name="secondaryConcept" content="Cisco Catalyst 9400 Series Switches" /> <meta name="secondaryConcept" content="Cisco Catalyst 9500 Series Switches" /> <meta name="secondaryConcept" content="Cisco Catalyst 9600 Series Switches" /> <meta name="secondaryConcept" content="Cisco Catalyst ESS9300 Embedded Series Switch" /> <meta name="secondaryConcept" content="Cisco Catalyst IE3200 Rugged Series" /> <meta name="secondaryConcept" content="Cisco Catalyst IE3300 Rugged Series" /> <meta name="secondaryConcept" content="Cisco Catalyst IE3400 Heavy Duty Series" /> <meta name="secondaryConcept" content="Cisco Catalyst IE3400 Rugged Series" /> <meta name="secondaryConcept" content="Cisco Embedded Services 3300 Series Switches" /> <meta name="secondaryConcept" content="Cisco 1000 Series Integrated Services Routers" /> <meta name="secondaryConcept" content="Cisco 4000 Series Integrated Services Routers" /> <meta name="secondaryConcept" content="Cisco Catalyst 8000V Edge Software" /> <meta name="secondaryConcept" content="Cisco Catalyst 8200 Series Edge Platforms" /> <meta name="secondaryConcept" content="Cisco Catalyst 8300 Series Edge Platforms" /> <meta name="secondaryConcept" content="Cisco Catalyst 8500 Series Edge Platforms" /> <meta name="secondaryConcept" content="Cisco Catalyst IR1100 Rugged Series Routers" /> <meta name="secondaryConcept" content="Cisco Catalyst IR1800 Rugged Series Routers" /> <meta name="secondaryConcept" content="Cisco Catalyst IR8100 Heavy Duty Series Routers" /> <meta name="secondaryConcept" content="Cisco ESR6300 Embedded Series Routers" /> <meta name="secondaryConcept" content="Cisco ASR 900 Series Aggregation Services Routers" /> <meta name="secondaryConcept" content="Cisco ASR 920 Series Aggregation Services Router" /> <meta name="secondaryConcept" content="Cisco Network Convergence System 500 Series Routers" /> <meta name="secondaryConcept" content="Cisco ASR 1000 Series Aggregation Services Routers" /> <meta name="secondaryConcept" content="Cisco Catalyst 9800 Series Wireless Controllers" /> <meta name="secondaryConcept" content="Cisco Wireless LAN Controller Software" /> <meta name="secondaryConcept" content="Cisco SD-WAN" /> <meta name="docType" content="TSD Products System Message Guide" /> <meta name="iaPath" content="cisco.com#Products#Cisco Products#Cisco IOS and NX-OS Software#Cisco IOS XE#Cisco IOS XE 17" /> <meta name="contentType" content="cisco.com#US#postSales" /> <meta name="locale" content="US" /> <meta name="language" content="en" /> <meta name="country" content="US" /> <meta name="hub" content="Enterprise Networks" /> <meta name="CCID_Page" content="cc001784" /> <meta name="date" content="Wed Dec 18 21:45:32 PST 2024" /> <meta name="accessLevel" content="Customer" /> <meta name="accessLevel" content="Guest" /> <meta name="accessLevel" content="Partner" /> <meta name="entitlementExpression" content="contains( "0,1,2,3,4,7" , $profileField[3] )" /> <meta property="og:site_name" content="Cisco" /> <meta property="og:type" content="website" /> <meta property="og:title" content="System Message Guide for Cisco IOS XE 17.16.x" /> <meta property="og:description" content="Quick Start Guide: System Message Guide for Cisco IOS XE 17.16.x" /> <meta property="og:url" content="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/17_xe/syslogs/17-16-x/b-system-message-guide-17-16-x.html" /> <link rel="canonical" href="https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/17_xe/syslogs/17-16-x/b-system-message-guide-17-16-x.html"/> <script src="/etc.clientlibs/clientlibs/granite/jquery.min.js"></script> <script src="/etc.clientlibs/clientlibs/granite/utils.min.js"></script> <script src="/etc.clientlibs/clientlibs/granite/jquery/granite.min.js"></script> <script src="/etc.clientlibs/foundation/clientlibs/jquery.min.js"></script> <script src="/etc.clientlibs/foundation/clientlibs/shared.min.js"></script> <script src="/etc.clientlibs/cq/personalization/clientlib/underscore.min.js"></script> <script src="/etc.clientlibs/cq/personalization/clientlib/personalization/kernel.min.js"></script> <script src="/etc.clientlibs/cq/personalization/clientlib/personalization/kernel.min.js"></script> <script type="text/javascript"> $CQ(function() { CQ_Analytics.SegmentMgr.loadSegments("\/etc\/segmentation"); CQ_Analytics.ClientContextUtils.init("\/c\/dnc\/etc\/clientcontext\/default", "\/content\/en\/us\/td\/docs\/ios\u002Dxml\/ios\/17_xe\/syslogs\/17\u002D16\u002Dx\/b\u002Dsystem\u002Dmessage\u002Dguide\u002D17\u002D16\u002Dx"); }); </script> <link rel="stylesheet" href="/etc/designs/cdc/clientlibs/responsive/css/cisco-sans.min.css" type="text/css"> <script src="/etc/designs/cdc/clientlibs/responsive/js/foundation.min.js"></script> <link rel="stylesheet" href="/etc/designs/cdc/fw/b/responsive/css/eot.min.css" type="text/css"> <script> sessionStorage.setItem("logOutIntermediateMessage", 'You are being logged out.'); </script>  <script type="application/ld+json"> [ { "@context": "http://www.schema.org", "@type": "WebPage", "name": "System Message Guide for Cisco IOS XE 17.16.x", "url": "https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/17_xe/syslogs/17-16-x/b-system-message-guide-17-16-x.html", "description": "Quick Start Guide: System Message Guide for Cisco IOS XE 17.16.x", "publisher": { "@type": "Corporation", "name": "Cisco" } }] </script>    <script>!function(e){var n="https://s.go-mpulse.net/boomerang/";if("False"=="True")e.BOOMR_config=e.BOOMR_config||{},e.BOOMR_config.PageParams=e.BOOMR_config.PageParams||{},e.BOOMR_config.PageParams.pci=!0,n="https://s2.go-mpulse.net/boomerang/";if(window.BOOMR_API_key="GKZXC-NS3SU-A7VFH-HKBHM-U7LKH",function(){function e(){if(!o){var e=document.createElement("script");e.id="boomr-scr-as",e.src=window.BOOMR.url,e.async=!0,i.parentNode.appendChild(e),o=!0}}function t(e){o=!0;var n,t,a,r,d=document,O=window;if(window.BOOMR.snippetMethod=e?"if":"i",t=function(e,n){var t=d.createElement("script");t.id=n||"boomr-if-as",t.src=window.BOOMR.url,BOOMR_lstart=(new Date).getTime(),e=e||d.body,e.appendChild(t)},!window.addEventListener&&window.attachEvent&&navigator.userAgent.match(/MSIE [67]\./))return window.BOOMR.snippetMethod="s",void t(i.parentNode,"boomr-async");a=document.createElement("IFRAME"),a.src="about:blank",a.title="",a.role="presentation",a.loading="eager",r=(a.frameElement||a).style,r.width=0,r.height=0,r.border=0,r.display="none",i.parentNode.appendChild(a);try{O=a.contentWindow,d=O.document.open()}catch(_){n=document.domain,a.src="javascript:var d=document.open();d.domain='"+n+"';void(0);",O=a.contentWindow,d=O.document.open()}if(n)d._boomrl=function(){this.domain=n,t()},d.write("<bo"+"dy onload='document._boomrl();'>");else if(O._boomrl=function(){t()},O.addEventListener)O.addEventListener("load",O._boomrl,!1);else if(O.attachEvent)O.attachEvent("onload",O._boomrl);d.close()}function a(e){window.BOOMR_onload=e&&e.timeStamp||(new Date).getTime()}if(!window.BOOMR||!window.BOOMR.version&&!window.BOOMR.snippetExecuted){window.BOOMR=window.BOOMR||{},window.BOOMR.snippetStart=(new Date).getTime(),window.BOOMR.snippetExecuted=!0,window.BOOMR.snippetVersion=12,window.BOOMR.url=n+"GKZXC-NS3SU-A7VFH-HKBHM-U7LKH";var i=document.currentScript||document.getElementsByTagName("script")[0],o=!1,r=document.createElement("link");if(r.relList&&"function"==typeof r.relList.supports&&r.relList.supports("preload")&&"as"in r)window.BOOMR.snippetMethod="p",r.href=window.BOOMR.url,r.rel="preload",r.as="script",r.addEventListener("load",e),r.addEventListener("error",function(){t(!0)}),setTimeout(function(){if(!o)t(!0)},3e3),BOOMR_lstart=(new Date).getTime(),i.parentNode.appendChild(r);else t(!1);if(window.addEventListener)window.addEventListener("load",a,!1);else if(window.attachEvent)window.attachEvent("onload",a)}}(),"".length>0)if(e&&"performance"in e&&e.performance&&"function"==typeof e.performance.setResourceTimingBufferSize)e.performance.setResourceTimingBufferSize();!function(){if(BOOMR=e.BOOMR||{},BOOMR.plugins=BOOMR.plugins||{},!BOOMR.plugins.AK){var n=""=="true"?1:0,t="",a="bdpnbeqxgy4r2z5znrtq-f-92f4eb0f8-clientnsv4-s.akamaihd.net",i="false"=="true"?2:1,o={"ak.v":"39","ak.cp":"61004","ak.ai":parseInt("271834",10),"ak.ol":"0","ak.cr":3,"ak.ipv":4,"ak.proto":"http/1.1","ak.rid":"dc8b68","ak.r":37669,"ak.a2":n,"ak.m":"dsca","ak.n":"essl","ak.bpcip":"8.222.208.0","ak.cport":47332,"ak.gh":"23.53.33.212","ak.quicv":"","ak.tlsv":"tls1.2","ak.0rtt":"","ak.0rtt.ed":"","ak.csrc":"-","ak.acc":"reno","ak.t":"1740205159","ak.ak":"hOBiQwZUYzCg5VSAfCLimQ==h4axqvkQaEIUZqGOe80PgT0rVTFg0K+OlYhmxUA8ckF+xt2sQjiFq3Am+vzpWOOI2HusQT5GOXpFnjxgkVbzAsdm7yAvpMtUrbioBc0xgthck/xb3kzMrnUvi0fNsS9ej7QbVouLjomzBXs+SkOeRCAKpmvsOHjhaMGkBN2adhTLCLYHgnyAhVHhNm0AMnWz9GuauoSyHlpokzg9e/KsiKegClk/Vdf4PsjpyKefOOHnY7vOVLWlLoc3ZGSSgkqPod5I/4i/r02FjQpGeyphsg3V9h/sks7DBkqqalwRZqhZlXc4XLC0S1t6QobiD3AOMaowY4NVE3xRrA2V1OJTHIh7DOuIZb0qjInpCqDKexM6CeEHgZ2BMtQqd1p00U06DzGKfaSI64SY2UiAmu2fX8OF2NvyjSST8rbWcuL4FO4=","ak.pv":"521","ak.dpoabenc":"","ak.tf":i};if(""!==t)o["ak.ruds"]=t;var r={i:!1,av:function(n){var t="http.initiator";if(n&&(!n[t]||"spa_hard"===n[t]))o["ak.feo"]=void 0!==e.aFeoApplied?1:0,BOOMR.addVar(o)},rv:function(){var e=["ak.bpcip","ak.cport","ak.cr","ak.csrc","ak.gh","ak.ipv","ak.m","ak.n","ak.ol","ak.proto","ak.quicv","ak.tlsv","ak.0rtt","ak.0rtt.ed","ak.r","ak.acc","ak.t","ak.tf"];BOOMR.removeVar(e)}};BOOMR.plugins.AK={akVars:o,akDNSPreFetchDomain:a,init:function(){if(!r.i){var e=BOOMR.subscribe;e("before_beacon",r.av,null,null),e("onbeacon",r.rv,null,null),r.i=!0}return this},is_complete:function(){return!0}}}}()}(window);</script></head> <body id="wcq" class="fw-res cdc-support cdc-eot cdc-high-density cdc-full-width cdc-transform "> <div id="fw-skiplinks"> <ul class="container"> <li><a id="skiplink-content" href="#fw-content">Skip to content</a></li> <li><a id="skiplink-search" href="#">Skip to search</a></li> <li><a id="skiplink-footer" href="#fw-footer-v2" class="last">Skip to footer</a></li> </ul> </div> <script type="module" src="/site/web-components/us/en/cdc-header.js"></script> <cdc-header></cdc-header> <nav class="fw-c-header__seo-links" aria-hidden="true" style="display:none"> <ul> <li><a tabindex="-1" href="https://www.cisco.com/site/us/en/index.html">Cisco.com Worldwide</a></li> <li><a tabindex="-1" href="/c/en/us/products/index.html">Products and Services</a></li> <li><a tabindex="-1" href="https://www.cisco.com/site/us/en/solutions/index.html">Solutions</a></li> <li><a tabindex="-1" href="/c/en/us/support/index.html">Support</a></li> <li><a tabindex="-1" href="/c/en/us/training-events.html">Learn</a></li> <li><a tabindex="-1" href="//www.cisco.com/c/en/us/about/sitemap.html">Explore Cisco</a></li> <li><a tabindex="-1" href="/c/en/us/buy.html">How to Buy</a></li> <li><a tabindex="-1" href="https://www.cisco.com/site/us/en/partners/index.html?dtid=odicdc001129">Partners Home</a></li> <li><a tabindex="-1" href="https://www.cisco.com/site/us/en/partners/cisco-partner-program/index.html?ccid=cc000864&dtid=odiprc001129">Partner Program</a></li> <li><a tabindex="-1" href="https://www.cisco.com/site/us/en/partners/support-help/index.html">Support</a></li> <li><a tabindex="-1" href="https://www.cisco.com/site/us/en/partners/tools/index.html?dtid=odiprc001129">Tools</a></li> <li><a tabindex="-1" href="https://locatr.cloudapps.cisco.com/WWChannels/LOCATR/pf/index.jsp#/">Find a Cisco Partner</a></li> <li><a tabindex="-1" href="https://www.cisco.com/site/us/en/partners/connect-with-a-partner/index.html?ccid=cc000864&dtid=odiprc001129">Meet our Partners</a></li> <li><a tabindex="-1" href="https://www.cisco.com/site/us/en/partners/index.html?dtid=odicdc001129">Become a Cisco Partner</a></li> </ul> </nav> <div id="fw-content" class="container grid"> <div class="row full blowout" data-owner="ID"> <div class="col full "> <nav id="fw-breadcrumb" class="data-based" aria-label="breadcrumbs" data-owner="ID"> <ul itemscope itemtype="//schema.org/BreadcrumbList"> <li aria-hidden="true"><a href='#' class="skip"></a></li> <li itemprop='itemListElement' itemscope itemtype='//schema.org/ListItem'><a itemprop='item' href='/c/en/us/support/index.html'>Support<meta itemprop='position' content='1' /></a></li><li itemprop='itemListElement' itemscope itemtype='//schema.org/ListItem'><a itemprop='item' href='/c/en/us/support/all-products.html'>Product Support<meta itemprop='position' content='2' /></a></li><li itemprop='itemListElement' itemscope itemtype='//schema.org/ListItem'><a itemprop='item' href='/c/en/us/support/ios-nx-os-software/index.html'>Cisco IOS and NX-OS Software<meta itemprop='position' content='3' /></a></li><li itemprop='itemListElement' itemscope itemtype='//schema.org/ListItem'><a itemprop='item' href='/c/en/us/support/ios-nx-os-software/ios-xe-17/series.html'>Cisco IOS XE 17<meta itemprop='position' content='4' /></a></li><li itemprop='itemListElement' itemscope itemtype='//schema.org/ListItem'><a itemprop='item' href='/c/en/us/support/ios-nx-os-software/ios-xe-17/products-system-message-guides-list.html'>Error and System Messages<meta itemprop='position' content='5' /></a></li> </ul> </nav> <script> if (window.cdc === undefined) { window.cdc = {}; } if (cdc.breadcrumb === undefined) { cdc.breadcrumb = (function () { let clone = document.querySelector('#fw-breadcrumb').cloneNode(true); let appendClone = function () { let hasBreadcrumb = document.querySelector('#fw-breadcrumb') !== null, firstMarquee = document.querySelectorAll('.dmc-mq')[0]; if (!hasBreadcrumb && firstMarquee !== undefined) { firstMarquee.querySelector('.frame .inset').insertBefore(this.clone, firstMarquee.querySelector('.frame .inset').firstElementChild); } }; return { clone: clone, appendClone: appendClone } }()); } //DE380224 var anchorChild = document.getElementsByTagName("a"); for(var i=0; i<anchorChild.length; i++){ if(anchorChild[i].getAttribute("itemprop")=="item") { if ( anchorChild[i].href.includes("%3Clocale%3E") ){ let anchorChildHREF = anchorChild[i].href; let docLocale = document.querySelector('meta[name="locale"]').getAttribute('content'); let docLanguage = document.querySelector('meta[name="language"]').getAttribute('content'); var docSeparator; if ((docLocale.toLowerCase() == "us") && (docLanguage.toLowerCase() == "en")) { docSeparator="/"; } else { docSeparator="_"; } let anchorURLReplace = docLanguage.toLowerCase() + docSeparator + docLocale.toLowerCase(); anchorChildHREF = anchorChildHREF.replace("%3Clocale%3E", anchorURLReplace); anchorChild[i].setAttribute('href', anchorChildHREF); } } } </script> <h1 id="fw-pagetitle" class="" data-owner="ID">System Message Guide for Cisco IOS XE 17.16.x</h1> </div> </div>  <div class="row blowout wide-narrow-v2 visitedlinks"> <div class="col wide-v2"> <script> if (typeof(cdc) == "undefined") cdc={}; if (typeof(cdc.translations) == "undefined") cdc.translations={}; </script> <div class="docHeaderComponent base-blowout"> <div class="linksRow"> <div class='versionddcontainer'></div> <script type="text/html" class="versionstemp"> <div class="versionsdd"> <button class="versionbutton" aria-haspopup="true" aria-expanded="false" aria-labelledby="other versions" class="version"><label></label></button> <ul class="versionlist" aria-labelledby="other versions"> <% let pageUrl = window.location.pathname.replace("/content/","/c/").toLowerCase(); if (false) pageUrl = pageUrl.substring(0,pageUrl.lastIndexOf("/"))+".html"; for(let i=0; i< data.length; i++) { let item = data[i], myurl = item.linkUrl, urlm = myurl.replace("/content/","/c/");; mytitle = item.linkTitle; myclass= urlm.toLowerCase() == pageUrl ? "class=\"selected\"":""; %> <li><a href="${myurl}" ${myclass}>${mytitle}</a></li> <% } %> </ul> </div> </script> <div class="toolbar"> <div class="noprint" id="saveModule"> <script type="text/javascript"> cdc.util.ensureNamespace("cdc.rc.savedoc"); cdc.rc.savedoc.isLoggedIn = false; cdc.rc.savedoc.save = "Save"; cdc.rc.savedoc.saved = "Saved"; </script> <button class="save" aria-expanded="false" aria-label="Save"> <label>Save</label> </button> </div> <div class="saveDocumentMessage login cdc-expandPanel" role="region" aria-live="polite"> <a href="/c/login/index.html?referer=/c/en/us/td/docs/ios-xml/ios/17_xe/syslogs/17-16-x/b-system-message-guide-17-16-x.html">Log in</a> to Save Content </div>   <div class="noprint downloadDocument"><button type="button" class="view-download-list-link anchor" aria-expanded="false"><div class="toolbarIcon downloadIcon"></div><label class="iconLabel">Download</label></button></div> <div class="noprint printDocument js-only"><button type="button" class="anchor printPage" aria-label="Print"><div class="toolbarIcon printIcon"></div><label class="iconLabel">Print</label></button></div> </div> </div>  <script language="javascript"> cdc.translations.map = "{en-us=https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/17_xe/syslogs/17-16-x/b-system-message-guide-17-16-x.html, x-default=https://www.cisco.com/c/en/us/td/docs/ios-xml/ios/17_xe/syslogs/17-16-x/b-system-message-guide-17-16-x.html}";//storing the map for use in the JS cdc.translations.locale="en_us"; </script> <div class="availableLanguagesList"> <h3>Available Languages</h3> <ul id="translationsList"> </ul> </div> <div id="download-list-container" class="noprint panelRow" role="region" aria-live="polite"> <div class='download-list' aria-label="Download Options"> <h3>Download Options</h3> <ul> <li> <div class="fileText"> <a href="/c/en/us/td/docs/ios-xml/ios/17_xe/syslogs/17-16-x/b-system-message-guide-17-16-x.pdf" class="download-pdf"><div class="fileIcon pdfIcon"></div>PDF</a> (3.2 MB) View with Adobe Reader on a variety of devices </div> </li> </ul> </div> </div> <div class="infobarClearFix"> <div class="infobar"> <div class="updatedDate">Updated:December 11, 2024</div> </div> <div class="disclaimers techdocs"> <div class="disclaimerButtons"> <div class="aboutBias"> <button aria-expanded="false" >Bias-Free Language</button> </div> </div> <div class="biasfreeContent panel"> <h3>Bias-Free Language</h3> The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. <a href="https://www.cisco.com/c/en/us/about/social-justice/inclusive-language-policy.html">Learn more</a> about how Cisco is using Inclusive Language. </div> </div> </div> </div> <script> jQuery(document).ready(function(){ if(jQuery("body").hasClass("cdc-eot-toc") && jQuery(".cdc-eot-toc").find(".DocumentHistory").length > 0){ jQuery(".cdc-eot-toc .seeRevisions").show(); if(jQuery(window).width() >= 768){ jQuery(".cdc-eot-toc .updatedDate").nextAll(".bullet").show(); } }else{ jQuery(".cdc-eot-toc .infobar .bullet").hide(); jQuery(".cdc-eot-toc .seeRevisions"); jQuery(".cdc-eot-toc .updatedDate"); } }) </script> <script src="/etc/designs/cdc/fw/clientlibs/granite-utils.min.js"></script> <script> if (window.cdc === "undefined") window.cdc={}; if (typeof cdc.rc === "undefined") cdc.rc={}; // initialize dictionary for i18n cdc.util.ensureNamespace("cdc.rc"); cdc.rc.eotkeys = { showOnly5Products : "Show Only 5 Products", showAllRowsProducts : "Show All nRows Products", supportCommunityUrl : "https://community.cisco.com/t5/technology-and-support/ct-p/technology-support", supportCommunity : "Cisco Community", thankYou : "Thank You", viewersAlso : "Customers Also Viewed", show : "Show", more : "More", showOnly3Documents: "Show Only 3 Documents" }; </script> <div id="eot-doc-wrapper"> <MIGRATE> <LINK rel="stylesheet" href="/etc/designs/cdc/transformation/commonltr_responsive.css" type="text/css"> </MIGRATE> <main role="main"> <article role="article" aria-labelledby="" id="system-message-guide-for-cisco-ios-xe-17.16.x"> <article class="topic nested0" aria-labelledby="ariaid-title1" lang="en-US" id="system-message-guide-for-cisco-ios-xe-17.16.x">  <nav> <h2 class="topictitle2">Contents</h2> <ul class="simple"> <li class="olchildlink"><a style="font-weight: bold" href="#system-message-guide-for-cisco-ios-xe-17.16.x">System Message Guide for Cisco IOS XE 17.16.x</a></li> <li class="olchildlink"><a style="margin-left: 15px" href="#id_129553">Cisco System Messages Overview</a></li> <li class="olchildlink"><a style="margin-left: 15px" href="#id_129553">How To Read System Error Messages</a></li> <li class="olchildlink"><a style="margin-left: 15px" href="#id_129553">Error Message Traceback Reports</a></li> <li class="olchildlink"><a style="margin-left: 15px" href="#system-and-error-messages-in-cisco-ios-xe-17.16.x">System and Error Messages in Cisco IOS XE 17.16.x</a></li> <li class="olchildlink"><a style="margin-left: 30px" href="#r-a-to-e-syslogs_17161"> A to E </a></li> <li class="olchildlink"><a style="margin-left: 30px" href="#r-f-to-j-syslogs_17161"> F to J </a></li> <li class="olchildlink"><a style="margin-left: 30px" href="#r-k-to-o-syslogs_17161"> K to O </a></li> <li class="olchildlink"><a style="margin-left: 30px" href="#r-p-to-t-syslogs_17161"> P to T </a></li> <li class="olchildlink"><a style="margin-left: 30px" href="#r-u-to-z-syslogs_17161"> U to Z </a></li> <li class="olchildlink"><a style="margin-left: 15px" href="#id_129698">Additional References</a></li> </ul> </nav>  <h1 class="title topictitle1" id="ariaid-title1">System Message Guide for Cisco IOS XE 17.16.x</h1> <div class="body"></div>  <nav role="navigation" class="related-links"></nav>  <article class="topic concept nested1" aria-labelledby="ariaid-title2" lang="en-US" id="id_129553"> <h2 class="title topictitle2" id="ariaid-title2">Cisco System Messages Overview</h2> <div class="body conbody"> This document describes system messages for Cisco software releases. During operation, the system software sends these messages to the console (and, optionally, to a logging server on another system) during operation. Not all system messages indicate problems with your system. Some are purely informational, and others may help diagnose problems with communications lines, internal hardware, or the system software. </div>  <nav role="navigation" class="related-links"></nav>  </article> <article class="topic concept nested1" aria-labelledby="ariaid-title3" lang="en-US" id="id_129553"> <h2 class="title topictitle2" id="ariaid-title3">How To Read System Error Messages</h2> <div class="body conbody"> System error messages begin with a percent sign (%) and are structured as follows:<samp class="ph systemoutput sysout">%FACILITY-SUBFACILITY-SEVERITY-MNEMONIC: Message-text</samp> <ul class="ul"> <li class="li"> <samp class="ph systemoutput sysout">FACILITY</samp> is a code consisting of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software. </li> <li class="li"> <samp class="ph systemoutput sysout">SEVERITY</samp> is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. <a class="xref" href="#id_129553__error-message-severity-levels">Table 1</a> lists the severity levels. </li> <li class="li"> <samp class="ph systemoutput sysout">MNEMONIC</samp> is a code that uniquely identifies the error message. </li> <li class="li"> <samp class="ph systemoutput sysout">Message-text</samp> is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets (<code class="ph codeph">[ ]</code>). A decimal number, for example, is represented as <code class="ph codeph">[dec]</code>. <a class="xref" href="#id_129553__representation-of-variable-fields-in-error-messages">Table 2</a> lists the representations of variable fields and the type of information in them. </li> </ul> The following is a sample system error message: <samp class="ph systemoutput sysout">%LINK-2-BADVCALL: Interface [chars], undefined entry point</samp> Some error messages also indicate the card and slot reporting the error. These error messages begin with a percent sign (%) and are structured as follows: <samp class="ph systemoutput sysout">%CARD-SEVERITY-MSG:SLOT %FACILITY-SEVERITY-MNEMONIC: Message-text</samp> <ul class="ul"> <li class="li"> <samp class="ph systemoutput sysout">CARD</samp> is a code that describes the type of card reporting the error. VIP and FEIP are possible card types. </li> <li class="li"> <samp class="ph systemoutput sysout">MSG</samp> is a mnemonic that indicates that this is a message. It is always shown as <samp class="ph systemoutput sysout">MSG</samp>. </li> <li class="li"> <samp class="ph systemoutput sysout">SLOT</samp> indicates the slot number of the card reporting the error. It is shown as <samp class="ph systemoutput sysout">SLOT</samp> followed by a number (for example, <samp class="ph systemoutput sysout">SLOT5</samp>). </li> </ul> The prepended portion of the error message (<samp class="ph systemoutput sysout">%CARD-SEVERITY-MSG:SLOT)</samp> is not shown in the error message listings in this document. <section class="section" id="id_129553__error-message-severity-levels"> <h3 class="title sectiontitle">Error Message Severity Levels</h3> Error message severity levels correspond to the keywords assigned by the logging global configuration commands that define where and at what level these messages appear. The default is to log messages to the console at the debugging level (7). For more information, see the system configuration chapter and descriptions of the logging command in the configuration guide and command reference. <table width="100%" border="1" class="table"> <caption></caption> <colgroup> <col style="width:50%"> <col style="width:50%"> </colgroup> <thead class="thead"> <tr> <th font-weight="bold" class="entry align-left" id="id_129553__error-message-severity-levels__entry__1"> Level </th> <th font-weight="bold" class="entry align-left" id="id_129553__error-message-severity-levels__entry__2"> Description </th> </tr> </thead> <tbody class="tbody"> <tr> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__1 "> 0 - emergency </td> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__2 "> System unusable </td> </tr> <tr> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__1 "> 1 - alert </td> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__2 "> Immediate action needed </td> </tr> <tr> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__1 "> 2 - critical </td> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__2 "> Critical condition </td> </tr> <tr> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__1 "> 3 - error </td> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__2 "> Error condition </td> </tr> <tr> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__1 "> 4 - warning </td> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__2 "> Warning condition </td> </tr> <tr> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__1 "> 5 - notification </td> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__2 "> Normal, but significant, condition </td> </tr> <tr> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__1 "> 6 - informational </td> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__2 "> Informational message only </td> </tr> <tr> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__1 "> 7 - debugging </td> <td class="entry align-left" headers="id_129553__error-message-severity-levels__entry__2 "> Appears during debugging only </td> </tr> </tbody> </table> </section> <section class="section" id="id_129553__representation-of-variable-fields-in-error-messages"> <h3 class="title sectiontitle">Representation of Variable Fields in Error Messages</h3> <table width="100%" border="1" class="table frame-all"> <caption></caption> <colgroup> <col style="width:50%"> <col style="width:50%"> </colgroup> <thead class="thead"> <tr> <th font-weight="bold" class="entry colsep-1 rowsep-1" id="id_129553__representation-of-variable-fields-in-error-messages__entry__1"> Representation </th> <th font-weight="bold" class="entry colsep-1 rowsep-1" id="id_129553__representation-of-variable-fields-in-error-messages__entry__2"> Type of Information </th> </tr> </thead> <tbody class="tbody"> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [atalk_address] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> AppleTalk address </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [atalk_net] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> AppleTalk network, either 600 or 600-601 </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [char] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Single character </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [chars] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Character string </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [dec] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Decimal number </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [enet] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Ethernet address (for example, 0000.FEED.00C0) </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [hex] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Hexadecimal number </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [inet] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Internet address (for example, 10.0.2.16) </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [int] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Integer number </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [node] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Address or node name </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [sci_notation] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Scientific notation </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [t-line] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> Terminal line number in octal (or decimal if the decimal-TTY service is enabled) </td> </tr> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__1 "> [v-name] </td> <td class="entry colsep-1 rowsep-1" headers="id_129553__representation-of-variable-fields-in-error-messages__entry__2 "> VINES name; or number (hex or decimal) </td> </tr> </tbody> </table> </section> </div>  <nav role="navigation" class="related-links"></nav>  </article> <article class="topic concept nested1" aria-labelledby="ariaid-title4" lang="en-US" id="id_129553"> <h2 class="title topictitle2" id="ariaid-title4">Error Message Traceback Reports</h2> <div class="body conbody"> Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative. The following sample message includes traceback information: <samp class="ph systemoutput sysout">-Process= "Exec", level= 0, pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860</samp> </div>  <nav role="navigation" class="related-links"></nav>  </article> <article class="topic nested1" aria-labelledby="ariaid-title5" lang="en-US" id="system-and-error-messages-in-cisco-ios-xe-17.16.x"> <h2 class="title topictitle2" id="ariaid-title5">System and Error Messages in Cisco IOS XE 17.16.x</h2> <div class="body"> <section class="section" id="system-and-error-messages-in-cisco-ios-xe-17.16.x__d54e651"> The following tables list system and error messages and recommended actions. Scroll right to see the Recommendation Action. Alternatively, you can download the system and error messages in the excel format here: <a class="xref" href="https://www.cisco.com/c/dam/en/us/td/docs/switches/lan/sys_messages/17-16/smg_1716x.xlsx" target="_blank">System Message Guide for Cisco IOS XE 17.16.x</a>. </section> </div>  <nav role="navigation" class="related-links"></nav>  <article class="topic reference nested2" aria-labelledby="ariaid-title6" lang="en-US" id="r-a-to-e-syslogs_17161"> <h3 class="title topictitle3" id="ariaid-title6"> A to E </h3> <div class="body refbody"> <section class="section" id="r-a-to-e-syslogs_17161__d54e711"> <table width="100%" border="1" class="table"> <caption></caption> <colgroup> <col style="width:37.334510150044125%"> <col style="width:8.8261253309797%"> <col style="width:16.504854368932037%"> <col style="width:8.8261253309797%"> <col style="width:8.8261253309797%"> <col style="width:19.68225948808473%"> </colgroup> <thead class="thead"> <tr> <th font-weight="bold" class="entry align-left" id="r-a-to-e-syslogs_17161__entry__1"> Facility-Severity-Mnemonic </th> <th font-weight="bold" class="entry align-left" id="r-a-to-e-syslogs_17161__entry__2"> Severity-Meaning </th> <th font-weight="bold" class="entry align-left" id="r-a-to-e-syslogs_17161__entry__3"> Message </th> <th font-weight="bold" class="entry align-left" id="r-a-to-e-syslogs_17161__entry__4"> Message-Explanation </th> <th font-weight="bold" class="entry align-left" id="r-a-to-e-syslogs_17161__entry__5"> Component </th> <th font-weight="bold" class="entry align-left" id="r-a-to-e-syslogs_17161__entry__6"> Recommended-Action </th> </tr> </thead> <tbody class="tbody"> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AAA_AUDIT_MESSAGE-6-METHOD_LIST_STATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> mlist [chars] of [chars] service is marked for notifying state and its current state is : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Method list state change </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AAA_AUDIT_MESSAGE-6-NOTIFY_MLIST_STATE_TO_AAA_CLIENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Notifying state of [chars] method list [chars] of [chars] service as [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Method list state change notified to AAA CLIENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACCESS_SESSION_TRACE-3-TRACE_INIT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Access session trace initialization failed with code: [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to initialize access-session trace. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Review smd logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACCESS_SESSION_TRACE-3-TRACE_REG_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Component [chars] registration failed. Error code: [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Component failed to register with access-session trace </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Review smd logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACLMGR_MESSAGE-3-ACL_LEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> ewlc ACL flex push error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-3-CHANGE_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL [chars] change configuration could not be updated on all installed interfaces.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The given ACL change configuration could not be applied to all installed policies in hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Find out more about the error by using the show platform software trace messages fed command. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-3-ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL [chars] configuration could not be applied on [chars].\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The given ACL configuration could not be applied to hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Find out more about the error by using the show platform software trace messages fed command. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-3-SGACL_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SGACL configuration could not be changed on [chars].\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error occurred during SGACL configuration change, all SGACLs have been removed from cell. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> User needs to manually remove the cell configuration and attempt to re-apply when resources have been freed. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-4-ACLTCAM_FULL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on [chars] could not be programmed in hardware, ACL TCAM is full.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> You have exceeded the system limit of ACL TCAM, use a simpler configuration which uses less ACL entries.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-4-DGT_FULL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on [chars] could not be programmed in hardware, DGT ID table is full.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> You have exceeded the system limit of DGT, use a simpler configuration which uses less DGT entries.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-4-HASH_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on cell [chars] could not be found.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration is unknown. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> There is no SGACL Cell with this configuration found.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-4-HASH_FULL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on cell [chars] could not be programmed in hardware, SGACL table is full.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> You have exceeded the system limit of SGACL cells, use a simpler configuration which uses less SGACL cells.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-4-HASH_ZERO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on cell [chars] could not be programmed in hardware, sgt or mpls-vpn hash size is zero.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Cannot configure in hardware due to zero sgt or mpls-vpn hash entries. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Allocate hash entries to sgt or mpls-vpn using custom template.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-4-POLICYLABEL_FULL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on [chars] could not be programmed in hardware, Policy Label table is full.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> You have exceeded the system limit of the number of Policies, use a simpler configuration which uses less Policy entries.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-4-PROGRAM_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on [chars] programming failed in hardware.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> You have exceeded the system limit of entries, use a simpler configuration which uses less entries.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-4-SIS_STATS_FULL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Policy id [dec] could not be programmed in hardware, SIS stats table is FULL.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> You have exceeded the system limit of hardware resources, use a simpler configuration which uses less resources.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-4-UNLOADED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on interface [chars] could not be programmed in hardware and traffic will be dropped.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration is too large; dropped will be dropped on this interface. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Allocate more space to the relevant section of the TCAM and reboot, or else use a simpler configuration. If possible, use the same ACLs on multiple interfaces.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-6-GACL_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Logging is not supported for GACL.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The ACL logging is not supported for client/group ACL. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is needed. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-6-PACL_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Logging is not supported for PACL.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The ACL logging is not supported on port interface. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is needed. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-6-RELOADED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on interface [chars] has now been loaded into the hardware.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration that previously was unable to fit into the hardware will now fit and has been programmed for this interface. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required, informational only.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-6-REMOVED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The [chars] [chars] [chars] ACL configuration that was previously unloaded has been removed from interface [chars].\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration that was previously unloaded, because of lack of space, has been removed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required, informational only. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ACL_ERRMSG-6-THRESHOLD_EVENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The [chars] threshold alarm state is [chars] for switch [dec] asic [dec]; with [dec] entries used and [dec] entries remaining.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration exceeds the threshold, because of lack of space. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required, informational only. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ADMINTECH-3-INCOMPLETE_BUNDLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Admin-tech bundle is incomplete, IOS tech-support timed out after [dec] seconds </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This syslog is generated IOS tech-support times out resulting into incomplete admin-tech. Default timeout for admin-tech is 30 mins, however on loaded systems, this timeout might not be sufficient and admin-tech could potentially time out </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-admintech </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Increase the timeout value for admin-tech with 'request platform software sdwan admin-tech timeout &lt;&gt; </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ADMINTECH-3-PUBLISH_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Admin-tech bundle [chars] could not be uploaded to Cisco SD-WAN Manager, reason: [chars] ([dec]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This error syslog is generated when admin-tech can not be published to SD-WAN Manager over over HTTP channel. This can be due to degration in the network or control connectivity loss </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-admintech </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry generating admin-tech </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> ADMINTECH-5-PUBLISH_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Admin-tech bundle [chars] successfully uploaded to Cisco SD-WAN Manager </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated when admin-tech is successfully uploaded to SD-WAN Manager after the generation is complete </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-admintech </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AFC_SCHED-1-AFC_HTTPCON_HEALTHCHECK_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AFC Healthcheck failed with HTTP connection error: [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AFC Healthcheck failed due to HTTPCON error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> afc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AFC_SCHED-1-AFC_HTTP_HEALTHCHECK_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AFC Healthcheck failed with HTTP status code [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AFC Healthcheck failed due to HTTP error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> afc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AFC_SCHED-1-AFC_PROVIDER_HEALTHCHECK_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AFC Healthcheck failed : [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AFC Healthcheck failed due to provider error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> afc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AFC_SCHED-3-AFC_CLOUDM_HEALTHCHECK_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AFC Healthcheck failed, can't communicate with cloud services because [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AFC Healthcheck failed due cloudm communication failure </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> afc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AFC_WNCD-1-AFC_CONDITIONS_NOT_MET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Some geolocation information is missing for AP with Radio MAC [chars] to use AFC:[chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Some conditions are preventing the AP from using AFC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> afc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AFC_WNCD-4-AFC_GEOLOCATION_HIGH_UNCERTAINTY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Current location uncertainty for AP [chars] is high ([dec] meters). </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Geoloocation uncertainty for the AP is above 400m </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> afc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AFC_WNCD-6-AFC_WNCD_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Info Level - [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General AFC WNCD Lib info message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-spwifi </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_GTK_UNABLE_TO_UPDATE_BROADCAST_KEYS_TO_AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Unable to update broadcast keys to AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unable to update broadcast keys to AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_COP_1_DataEncryption </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP [chars] User ID: [chars] [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> TLV_AP_CC_AUDIT_PAYLOAD parameters </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_AWIPS_SYSLOG-6-APMGR_AWIPS_MESSAGE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AWIPS alarm:[chars] ([dec]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AWIPS alarm detected </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-awips </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-2-BSSID_CLEANUP_TIMEOUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> BSSID cleanup timeout, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> BSSID cleanup could not be completed. This may result in failure to push configuration updates to Access Points. Make a note of any recent changes made to the network or the device configuration which may have triggered this and proceed to the suggested action. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. It is suggested to collect archive traces and live process core to analyse the error. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-2-WLAN_CRIT_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WLAN Error : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Critical issue seen with WLAN config. Make a note of any recent changes made to the network or the device configuration which may have triggered this and proceed to the suggested action. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. It is suggested to collect archive traces and live process core to analyse the error. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-2-WLAN_CRIT_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CRITICAL, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller critical message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-2-WLC_APMGR_CRIT_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CRITICAL, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller warning message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-AP_NTP_SYNC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP [chars] MAC [chars], NTP sync has failed. Reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Ap failed to sync with the NTP server </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Verify the IP address of the NTP server and the authentication credentials. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-AP_RADIO_STUCK_ALARM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Radio Stats Monitoring: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Radio stats monitoring and radio stuck alarm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EWLC_APMGR_ANTENNA_SET_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Antenna set error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Antenna id enable/disable operation has resulted in error. please follow error message for details </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please follow error message string and take corrective action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EWLC_APMGR_AP_REG_DOMAIN_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error: Cannot set country code [chars] for AP MAC:[chars],Regulatory domain check failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Regulatory domain of all radio slots of the AP does not match with the country code </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by checking regulatory domain supported by Access Point (AP). Radios within APs are assigned to a specific regulatory domain as a part of factory setting. Configuring a country code ensures that each radio's broadcast frequency bands, channels and transmit power levels are compliant with country-specific regulations. Please ensure that user configured country code is compliant with country code setting in AP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EWLC_APMGR_UNSUPPORTED_COUNTRY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Regulatory domain error while setting country code for AP MAC:[chars], country code [chars] is not configured on WLC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Specified country code is not present in the configured country code list </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Validate the country code configuration on the Controller and add the country code to the configured country code list if it is not already present. Please refer to the configuration guide to configure country code. If you still require contact your Cisco technical support representative and provide the information you have gathered. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EWLC_GEN_CHAN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EWLC_RRM_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> event change: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller RRM error message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EWLC_RRM_QUERY_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Trying to query information related to AP with invalid slot ID. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please report the error to technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EWLC_WLAN_ETA_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> et-analytics config validation Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Global and Wireless et-analytics config dependency error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EWLC_WLAN_MPSK_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> MPSK config validation Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> MPSK and Central auth dependency error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EWLC_WLAN_MPSK_PSK_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> MPSK config validation Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> MPSK and PSK dependency error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EXEC_CLI_INVALID_SLOT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Executed exec-cli is not applicable for AP: [chars], number of slots: [dec], while cli executed for slot: [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The executed EXEC CLI is not applicable for this AP, because the limitation number of slots </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EXEC_CLI_NOT_5G_DUAL_RADIO_AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Executed exec-cli is not applicable for AP: [chars] because AP does not support dual 5ghz radio. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The executed EXEC CLI is not applicable for this AP, because AP does not support dual 5ghz radio </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EXEC_CLI_NOT_MASTER_RADIO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Executed exec-cli is applicable for only master radio for AP : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The executed EXEC CLI is applicable only for master radio </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-EXEC_CLI_TX_POWER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Tx Power Config Notification: Radio Role is AUTO. So, Tx power change is not allowed for AP [chars] on slot [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Tx Power configuration is not allowed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_AP_AUDIT_REPORT_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AP Audit Report Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_AP_CONFIG_CHECKER_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> error received from AP [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Error on AP while applying configuration updates from controller. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_AP_JOIN_24G_DCA_CHANNEL_LIST_EMPTY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The DCA Channel list is empty for 24ghz rf profile [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DCA Channel list for 24ghz radio is empty, it affects Channel Assignment to AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please add channels to DCA List </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_AP_JOIN_5G_DCA_CHANNEL_LIST_EMPTY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The DCA Channel list is empty for 5ghz rf profile [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DCA Channel list for 5ghz radio is empty, it affects Channel Assignment to AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please add channels to DCA List </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_AP_JOIN_6G_DCA_CHANNEL_LIST_EMPTY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The DCA Channel list is empty for 6ghz rf profile [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DCA Channel list for 6ghz radio is empty, it affects Channel Assignment to AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please add channels to DCA List </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_AP_JOIN_CRIT_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Join/Disjoin Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AP Join/Disjoin Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_AP_LOG_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Remote Log: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AP Remote logging </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_AP_PACKET_CAPTURE_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AP packet capture Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_EXEC_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> %% Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Improper arguments or config </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Arguments to be changed </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_GEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_MDNS_AP_ERROR_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error mDNS AP : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Error Message related to mDNS AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-3-WLC_UNSUPPORTED_AP_MODE_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unsupported AP mode. [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> vWLC ultra-low WLCs do not support Local Mode APs. This error will be logged whenever an AP tries to join in Local Mode on a vWLC ultra-low WLC. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Fix the configuration to allow AP to join in Flexconnect Mode. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-4-AP_CPU_ALARM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP [chars], MAC [chars], CPU=[dec]%%, alarm state: [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An alarm was triggered for AP CPU measurements </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-4-AP_GNSS_USB_DISCONNECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP [chars], GNSS USB Module has been removed. This might impact location availabilty and derivation for nearby APs </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> GNSS USB module disconnected from AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-afc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-4-AP_MEM_ALARM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP [chars], MAC [chars], Memory=[dec]%%, alarm state: [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An alarm was triggered for AP Memory measurements </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-4-AP_MERAKI_CONVERSION_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP [chars], MAC [chars], Meraki serial number: [chars], Meraki persona change result: Failed. Reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Conversion to Meraki AP validation result </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-4-EASYPSK_UNSUPPORTED_AP_MODE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unsupported AP mode for Easy-PSK WLAN [dec] on AP [chars], MAC [chars]. Easy-PSK only supported in local mode. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Easy-PSK WLAN configured on AP not in local mode. WLAN will not be pushed to the AP. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-spwifi </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Fix the configuration to move AP in local mode. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-4-WLC_APMGR_WARNING_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Warning, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller warning message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-4-WLC_CONFIG_CHECKER_WARNING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> config check: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Warning message related to config checker </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-4-WLC_MDNS_AP_WARNING_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Warning mDNS AP : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Warning message related to mDNS AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-5-AP_AFC_BELOW_TX_MIN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP [chars], 6GHZ radio operating below tx min due to afc restriction </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> 6GHZ radio operating below rf profile configured tx min due to afc restriction </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-afc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-5-AP_AFC_IMMINENT_FLAG_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP [chars], 6GHZ radio AFC response is about to expire on AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> 6GHZ AFC expiry imminent flag set </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-afc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-5-AP_COUNTRY_CODE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Name [chars] Mac: [chars] Model [chars] Type [chars] : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Resolved country code </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-5-AP_EXEC_CLI </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Exec CLI : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Exec cli information or output </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-5-EWLC_APMGR_NOTICE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> event change: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller Notice message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-5-WLC_AP_PUBLIC_CLOUD_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unsupported AP mode. [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Public cloud WLCs do not support Local Mode in AP. This error will be logged whenever an AP tries to join in Local Mode in a Public Cloud WLC. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Fix the configuration to allow AP to join in Flexconnect Mode. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-6-AP_MERAKI_CONVERSION_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP [chars], MAC [chars], Meraki serial number: [chars], Meraki persona change result: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Conversion to Meraki AP validation result </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-6-CHAN_ZERO_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP: [chars] reported channel 0 on slot [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AP has reported Channel 0 on one of the radio slots. This generally happens when the configurations on the AP are set to factory default. WLC recovers this by rebooting the AP. Unless the message repeatedly appears, it does not require any action. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-6-CLIENT_DEBUG_BUNDLE_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Client debug bundle [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller Client debug bundle info message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-6-EWC_APMGR_OLD_VERSION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Event: [chars] Please upgrade AP to 8.10 or 16.12 or higher before joining a EWC network </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Please upgrade 11AX AP to 8.10 or 16.12 so it can join EWC network </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-6-EWC_APMGR_POLL_CCO_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CCO polling for software version completed successfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The action of polling CCO for LATEST and SUGGESTED software version has completed successfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-6-WLC_APMGR_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Info : - [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller info message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> APMGR_TRACE_MESSAGE-6-WLC_AP_JOIN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Join Info : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AP Join/Disjoin Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AP_POWER_PROFILE_TRACE_MESSAGE-3-WLC_GEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_FPD-3-FRU_HWPRG_UPG_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error reason:[chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Some error occurred during auto upgrade </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry upgrade </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_FPD-3-FRU_HWPRG_UPG_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] failed to program. error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable was upgraded failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry upgrade </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_FPD-5-FRU_HWPRG_UPG_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] are upgrading, please don't reload or power-cycle this card. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable firmware is upgrading </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_FPD-5-FRU_HWPRG_UPG_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] are successfully programmed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_ADVISE_SW_COM_BUNDLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Switch [dec] running incompatible bundled software has been added to the stack. Switch [dec] must be running compatible bundled software in order to join the stack. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No explanation required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the member with compatible software. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_ADVISE_SW_FAILED_PLATFORM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to determine platform hardware type of switch [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Somehow the platform type could not determined. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Add an action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_ADVISE_SW_MODE_UNKNOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Switch [dec] has been added to the stack. Failed to initiate auto advise for switch [dec] because switch [dec] is not running installed or bundled software </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No explanation required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the member with compatible software. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_CONF_EXEC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Auto upgrade is enabled by config. Please disable auto upgrade configuration to execute auto upgrade manually using exec CLI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> TODO: add an explanation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> TODO: add an action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_COPY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to copy upgrade packages from [chars] [dec] to [chars] [dec]/R[dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> TODO: add an explanation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> TODO: add an action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_DISK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [dec]/[dec] doesn't have enough free disk space to perform auto upgrade. A minimum of [dec] KB of free disk space is required Initiating the auto-delete of the old images on joining member/FRU. (Default is oldest image in configuration mode) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> There might be older files because of which there is not enough memory. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Clean up disk space in the remote switch. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_EXPAND </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to install the running software on switch [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> TODO: add an explanation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_MEM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [dec] doesn't have enough free memory to perform auto upgrade. A minimum of [dec] KB of free memory is required </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> There might be older files because of which there is not enough memory. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Clean up disk space in the remote switch. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_PLATFORM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to determine platform hardware type of [chars] [dec]/R[dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Somehow the platform type could not determined. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Add an action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_FAILED_STATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A previous provisioning action is pending reboot. Please reboot the [chars] [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The user has run an operation that requires a reboot to take action. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the switch </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_INTERNAL_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Local chassis/RP number did not publish yet </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Somehow the chassis/FRU number is missing. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Try to do it again. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_MODE_UNKNOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Switch [dec] has been added to the stack. Failed to initiate auto upgrade for switch [dec] because switch [dec] is not running installed or bundled software </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No explanation required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the member with compatible software. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_NOTHING_TO_CLEAN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Couldn't find enough old install images on incompatible standby/member for deletion. Please manually free up [dec] MB space on incompatible standby/member and try again using 'install autoupgrade'. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> If there is no old images are found on joining standby/member's boot directory </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> User will have to manually delete old files using IOS delete command </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_NOTHING_TO_UPGRADE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> No incompatible standby/member is found, nothing to auto-upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Exec autoupgrade scenario when there is no incompatible member in stack. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required from the user </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_NOT_SUPPORTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The system is not running installed software. Auto upgrade for [chars] [dec]/R[dec] cannot be initiated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A system with incompatible software has been detected in the stack. The auto upgrade functionality cannot be initiated because the stack/HA system is not running installed software. The user must manually upgrade the incompatible switch/FRU. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform the one shot cli to convert system is install mode. Boot the system from the boot directory (bootflash/harddisk) using 'boot bootflash:packages.conf' </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_NO_DOWNGRADE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Skip auto-upgrade on chassis [dec]. The Active chassis's software version [chars] is lower than this chassis's minimum software version requirement [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Skip auto-downgrade scenario when the active switch does not fulfill the minimum software release version requirment. The active switch is running an image lower than the remote chassis's minimum software version. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Upgrade the stack to a higher release version or remove the switch from the stack. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_PLATMISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> No software was found to upgrade [chars] [dec]/R[dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Happens because of incompatible switches. For example, ngwc and non-ngwc ones are incompatible </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Plugin compatible switches for autoupgrade to run. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-AUTO_UPGRADE_ROMMON_NOT_UPDATED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unable to confirm boot config on [chars] [dec]/R[dec], assuming it is set as [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> TODO: add an explanation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> NO action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-SMU_SYNC_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SMU upgrade failed on switch [dec]. Auto upgrade of image will pass with out syncing SMUs on this switch. SMUs will be synced at boot time of the switch [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> SMU sync failed because of some reason. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required, SMU sync will be tried in next reload. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-3-SMU_UPGRADE_FAILED_DISK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Switch [dec] doesn't have enough free disk space to sync SMU. A minimum of [dec] KB of free disk space is required. Auto upgrade will pass with out syncing SMUs on this switch </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> There might be older files because of which there is not enough memory. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Clean up disk space in the remote switch. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_ADVISE_SW_BUNDLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> switch [dec] running installed software has been added to the stack. Switch [dec] must be running bundled software in order to join the stack. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No explanation required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the member with compatible software. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_ADVISE_SW_CONV </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [dec] running bundled software has been added to the stack that is running installed software. The 'install autoupgrade' command can be used to convert [chars] [dec] to the installed running mode by installing its running software. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No explanation required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No specific action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_ADVISE_SW_FOUND </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Found donor switch [dec] to auto upgrade switch [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Just an init message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_ADVISE_SW_INITIATED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Auto advise initiated for [chars] [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A system with incompatible software has been detected in the stack. The stack will now determine whether or not software is available to be copied to the incompatible system, and if so, advise the user how to copy it. Otherwise, the system will merely let the user know that the software on the stack needs to be updated. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_ADVISE_SW_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [dec]/R[dec] with incompatible software has been added to the system/stack. all system/stack members were scanned and it has been determined that the 'install autoupgrade' command can be used to install compatible software on [chars] [dec]/R[dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> TODO: add an explanation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> TODO: add an action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_ADVISE_SW_SEARCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Searching stack for software to upgrade [chars] [dec]/R[dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Just an init message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_ADVISE_SW_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Upgrading [chars] [dec] with software from [chars] [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Just an init message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_CONV </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Converting [chars] [dec] to installed mode by installing its running software. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This needs to be converted as part of the auto upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_FINISH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Finished installing software on [chars] [dec]/R[dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> TODO: add an explanation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> TODO: add an action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_FOUND </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Found donor [chars] [dec] to auto upgrade [chars] [dec]/R[dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Just an init message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_INITIATED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Auto upgrade initiated for [chars] [dec]/R[dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A system with incompatible software has been detected in the stack. The stack will first attempt to download software from a previously-configured location, and install it to make the system compatible. If this is not successful, the stack will then determine whether running software on another stack member is available to be copied to the incompatible system, and whether or not it is appropriate to copy the software automatically </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_INSTALLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Finished installing the running software on [chars] [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> TODO: add an explanation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> TODO: add an action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_RELOAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Reloading [chars] [dec] to complete the auto upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Part of autoupgrade </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Just wait until the reload completes. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_RELOAD_INSTALLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Reloading [chars] [dec] to boot in installed mode. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> TODO: add an explanation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> TODO: add an action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_SEARCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Searching stack for software to upgrade [chars] [dec]/R[dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Just an init message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Upgrading [chars] [dec]/R[dec] with software from [chars] [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Just an init message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-AUTO_UPGRADE_START_CHECK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Auto upgrade start checking for incompatible switches. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Part of autoupgrade </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> NO action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE-5-SMU_RB_SYNC_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SMU rollback sync failed on [chars]. Rollback operations may be affeced </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> SMU rollback sync failed on some reason. Most probable causes are SMUs are not present on the media or the media is full. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Bring back the SMUs deleted and check whether there is enough space in remote member/SMUs </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE_MODULAR-3-AUTO_ERR_SMU_SYNC_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to sync SMUs to standby. Make sure that SMU files are present on active and there is space enough to copy SMUs on standby. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> SMU sync failed. Most probable cause are the smu files may have been removed from the active switch using IOS/linux commands. Another reason is there is no space enough to copy the files to the standby </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If the files are removed from the active bring it back to same location. Make sure there is enough space to copy the files on the standby </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE_MODULAR-3-AUTO_NOTICE_RUN_CORRECTION_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to correct the SMU mismatch between the running version on active and standby. Pls abort the smu installation using 'install abort' </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system tried to recover from the missmatch, but failed. Engineer intervention is required </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Get the 'show install log' and the btrace logs from active and standby </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE_MODULAR-5-AUTO_ADVISE_SW_MISSMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Active and standby are running differnt versions, SMUs will not be synced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No explanation required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the member with same software. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE_MODULAR-5-AUTO_NOTICE_RUN_MISSMATCH_STBY_RELOAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Missmatch between running version of SMUs. Trying to recover. Standby will reload </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> There is a missmatch on the running version. This will happen when the standby reloads after activate/deactivate and before commit. The machine will try to correct it. One reload is required for correcting the chanages. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE_MODULAR-5-AUTO_NOTICE_STBY_RELOAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Installing SMUs on standby. Standby will reload </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No explanation required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AUTO_UPGRADE_MODULAR-5-SMU_AUTO_UPGRADE_INITIATING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Initiating SMU autoupgrade for [chars] [dec]/R[dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No explanation required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the member with same software. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> AVC_MESSAGE-3-EWLC_AVC_FNF_CLI_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CLI validation error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General AVC FNF CLI validation error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-0-CHASFS_OBJECT_NOT_PRESENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] not present. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-0-CHASFS_PROPERTY_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property was not properly created. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-0-CHASFS_PROPERTY_GET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to read chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property was not properly read by the system. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-0-CHASFS_PROPERTY_NOT_PRESENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] property [chars] not present. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-0-CHASFS_PROPERTY_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to write chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property failed to write. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-0-SERVICES_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize general application services because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize application services. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-0-UIPEER_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create user interface peer. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to create a user interface peer. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-3-BAD_CELL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Bad battery cell detected in unit [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Battery firmware detected a bad cell, which can't be recharged. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Replace the bad battery unit. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-3-CHASFS_PROPERTY_DESTROY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to destroy chassis filesystem property [chars]/[chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property that should have been destroyed was not destroyed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-3-CLI_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] command execution failed with err=[dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CLI execution failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-3-COMM_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Battery communication error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Battery communication error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-3-FW_UPGRADE_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Firmware upgrade failed with error [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Battery firmware upgrade failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check battery status. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-3-HW_INIT_PH_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware init phase error, [chars] init returned [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Hardware failed to initialize. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-3-HW_RUNTIME_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware runtime error, [chars] init returned [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Hardware failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-4-AC_TO_DC_TRANSITION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AC power is off, running on batteries. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Lost power from AC power line, system is powered by backup batteries. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check AC power line. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-4-FW_UPGRADE_STARTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Firmware upgrade to version [dec] started </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Battery firmware upgrade started. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-4-LOW_LEVEL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Battery charge running low ([dec]%%) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Battery charge is below low level threshold. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check AC power line. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-4-STATUS_CHANGE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The [chars] parameter for BBU unit [dec] has changed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Status change of BBU parameters </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-5-BBU_EVT_LOG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Battery Event Log - [chars]:[chars] \n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> BBU Event Log Data. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-5-CELL_RECOVERED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Battery cell in unit [dec] recovered </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A battery cell, which was previously detected to be bad, has now recovered. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-5-CLI_OK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Command [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CLI execution successful. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-5-DC_TO_AC_TRANSITION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AC power is back on, running on power line </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AC power is restored, system is powered by AC power line </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-5-FW_UPGRADE_FINISHED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Firmware upgrade finished successfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Battery firmware upgrade finished. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-5-HW_HOTPLUG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Battery detected, started initialization </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Battery hotplugged in the system, Started probing and initialization. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-5-NORMAL_LEVEL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Battery charge reached normal level ([dec]%%) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Battery charge is above low level threshold. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BBU-7-FSM_TRANSITION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> FSM transition ([dec], [dec]) -&gt; [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> FSM transition (old_state, event) -&gt; new state </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cabo-platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BCRDU-3-PATCH_ACTIVATE_FAIL_MESSAGE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to activate patch. The patch name is [chars] and the reason is: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> During system reload, all committed patches will be automatically activated.For some reason, a patch activation fails. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check [bcrdu] ERR entries in the log files for message reporting problems. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BCRPGC-3-REFERENCE_STUBBED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Stubbed [chars] is referenced </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Stubbed function/variable is referenced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> File a DDTS and attach the backtrace </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BCRPGC-3-USWAP_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> uswap error - no space on [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Path for USWAP files. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this error is seen, it is recommended to clean up the flash usage. If more assistance is required, file a DDTS, attach the backtrace and btrace </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BFDMGR-5-BFD_STATE_CHANGE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> BFD tunnel ([chars]:[dec] =&gt; [chars]:[dec], [chars]) state changed to [chars], Local-TLOC: [chars]/[chars], Remote-TLOC: [chars]/[chars], reason for state change: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This syslog is generated when a BFD tunnel state changes </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-forwarding </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BFDMGR-6-BFD_SLA_CHANGE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> BFD tunnel ([chars]:[dec] =&gt; [chars]:[dec], [chars]) SLA changed from [chars] to [chars], Local-TLOC: [chars]/[chars], Remote-TLOC: [chars]/[chars] PFR stats: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This syslog is generated whenever SLA of a BFD tunnel running on top of specific TLOC changes </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-forwarding </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BINOS_LOGIN-3-AUTHERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The authentication process failed, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This error occurs when there is an error in the system that prevents the user from being successfully authenticated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BINOS_LOGIN-3-NOTROOT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> login attempted to run without proper credentials. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> login can not be run without proper credentials. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BINOS_LOGIN-3-NOTTY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> login attempted but stdin is not a tty </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> login can not be run without stdin set to tty </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BINOS_LOGIN-3-PAMERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> PAM error [chars] encountered. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system encountered a PAM error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BINOS_LOGIN-3-PWNOENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> No entry for user [chars] in passwd file </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The username/password authenticated correctly, but the user's environment could not be established because the user's environment data is missing. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BINOS_LOGIN-6-PAMAUTHDENY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User was not authenticated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> User was not authenticated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BINOS_LOGIN-6-PAMMAXTRIES </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Maximum number of retries exceeded. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The user tried and failed too many times to login. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BIPC-3-BIPC_PERFORMANCE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> buffer size request [dec] failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An internal buffer allocation has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. If the problem persists, or router performance is noticeably degraded, contact Cisco technical support. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BIPCMGR-3-INVALID_TDL_ERROR_ON_MARSHAL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> TDL epoch error on marshal [dec] unexpected: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The bipc manager has attempt to marshal a message to be sent. The tdl library has generated an error on marshal that is unexpected. The message was not sent. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is unexpected. Report this to Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-0-APP_STARTFAILCRIT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to launch a critical process [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A process important to the chassis has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the message and investigate the error message logs to learn more about the problem. If the problem persists or cannot be resolved, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-0-BOOT_BADDIMM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: This memory configuration: [chars] is not supported on this platform! </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This memory configuration isn't supported on this platform. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Change memory configuration to a supported one. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-0-BOOT_COMPLETE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Critical boot tasks failed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system has encountered a critical failure preventing successful boot. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and system logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-0-BOOT_NOSPACE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: No space on bootflash [chars] for packages, using system memory! Delete files from bootflash to free memory and reload the system; otherwise, system behavior will be unpredictable due to high memory utilization. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to boot system from bootflash. Image is booting from system memory! Delete files from bootflash to free memory and reload the system; otherwise, system behavior will be unpredictable due to high memory utilization. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Delete files from bootflash to free memory and reload the system. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-0-BOOT_VERITY_CORRUPT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Verity device [chars] is corrupted. Reloading FRU. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The integrity check of the verity mapped device has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check image integrity. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-0-DRV_INITFAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] driver failed to initialize properly </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A kernel driver that is critical to the functioning of the system failed to initialialize properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and check the kernel error logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-0-DRV_LOADFAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to load driver [chars] ( [chars] ) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A kernel driver that was critical to the functioning of the system failed to load. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and check the kernel error logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-APP_STARTFAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to launch process [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A process that does not affect the forwarding of network traffic failed to start. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If the failed process is not something that needs to be corrected, do not address this message. If the failed process needs to be addressed, install new software and reload the router. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-BOOTTIME_GET_ISSU_INFO_OF_REMOTE_CHASSIS_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to get ISSU information from remote chassis. Details: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to get remote switch information for compatibility check. This could be for multiple underlying failures such as reachability of peer member lost or remote member not responding </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If standby is stuck retry with reloading standby. If standby does not comes up even after reloading attempts, try reloading the whole stack to recover. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-BOOTTIME_INCOMPATIBLE_SW_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Incompatible software detected. Details: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Incompatible software is detected on target fru/chassis. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Upgrade manually or check auto-upgrade configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-BOOTTIME_MISMATCH_RESTRICTED_STACK_SETUP_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Mismatch detected. Details: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Incompatible stacked setup detected on target fru/chassis. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Switch with mismatch require to be reloaded </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-BOOTTIME_SMU_MISSING_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SMU file [chars] missing and system impact will be unknown </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> SMU file not found during bootup. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> System will be running without the fix from the SMU </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-BOOTTIME_SMU_RUN_CORRECTION_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to correct the SMU mismatch between the running version on active and [chars]. Pls abort the smu installation using 'install abort' </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system tried to recover from the missmatch, but failed. Engineer intervention is required </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Get the 'show install log' and the btrace logs from active and standby </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-BOOTTIME_SMU_SYNC_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to copy the SMUs to switch [chars]. Reload cancelled and switch will be declared incompatible </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> SMU sync failed on newly joined switch. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Switch with mismatch will be declared incompatible. Check the space on the remote switch. Check whether the file is present on active. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-COMP_SW_TREE_DIR_CREATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> COMP_SW_TREE directory is being generated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> If chasfs/issu directory is missing on active, this message is displayed and the directory and its contents are being regenerated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. This is an informative message. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-DUAL_BOOT_MEMORY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Dual IOS boot indicated in ROMMON ([chars]), unavailable on [chars] RP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Running two IOS instances on the same RP is unavailable on route-processors with insufficient memory </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Unset the specified ROMMON variable or increase the memory on the route-processor. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-EXT_ISSU_CHK_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Detected booting up of standby RP with image beyond the ISSU domain of active RP by the [chars] process. The standby RP is forced to reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> If standby RP is booted up with an image which is beyond the ISSU software domain of the active RP's image, the functionality of active RP may be unpredictable. Hence the standbby is being reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the standby RP FRU from the chassis or boot it up with an image whose version is compatible with current running active RP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-FLASH_READ_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> failed to get [chars] from flash </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Property not populated. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. This is informative message. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-FSCK_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> filesystem on [chars] contains errors fsck couldn't resolve. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A device's file system consistency check failed & fsck utility was unable to repair it. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this occurs frequently, contact Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-OPMODE_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Device-mode error : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system has encountered a device-mode failure during boot. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> The device-mode booting err information captured with console logging For information, try show platform softwate device-mode CLI. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-PARTIAL_CORE_CLEANUP_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Partial core clean up failed for [chars]: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> During RP boot, a failure occurred cleaning up incomplete core files. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please check the router file systems. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-3-SYSD_STARTFAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to launch boot task [chars] ( [chars] ) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A boot task failed to start. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If the failed boot task is not something that needs to be corrected, do not address this message. If the failed boot task needs to be addressed, install new software and reload the router. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-4-BOOT_CORRUPT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Boot Partition corrupted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Boot Parition on the router is corrupted. Router booting from bootflash. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Contact Cisco technical support. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-5-BOOTTIME_RB_SYNC_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to sync the SMUs to switch [chars]. Install rollback operation may get affected. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Rollback point sync failed on newly joined switch. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Switch will not have the rollback points. Check the space on the remote switch. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-5-BOOTTIME_SMU_MISMATCH_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SMU mismatch from active detected. SMUs will be copied and switch [chars] will be reloaded </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> SMU mismatch found on newly joined switch. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Switch with mismatch will be reloaded </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-5-BOOTTIME_SMU_RUN_MISMATCH_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Running SMU mismatch from active dectected. System will try to correct it, switch [chars] will be reloaded </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Running version of SMU mismatch found on newly joined switch. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stack will try to correct itself. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-5-BOOTTIME_SMU_TEMP_ACTIVE_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SMU file [chars] active temporary... SMU commit is pending </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> SMU file is active temporary and 'install commit' needs to be run to make it permanent. Else reload without commit will deactive this SMU. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Execute 'install commit' before reload to make activate permanent. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-5-BOOTTIME_SMU_TEMP_DEACTIVE_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SMU file [chars] deactive temporary... SMU commit is pending </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> SMU file is deactive temporary and 'install commit' needs to be run to make it permanent. Else reload without commit will active this SMU again. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-p-smu </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Execute 'install commit' before reload to make deactivate permanent. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-5-OPMODE_LOG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Device-mode logging : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The device-mode booting information.: </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> The device-mode booting information captured with console logging For information, try show platform softwate device-mode CLI. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-6-APP_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The process [chars] has started </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The process has successful launched and begun executing. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-6-DRV_LOAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Loaded driver [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A kernel driver that was critical to the functioning of the system was successfully loaded. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BOOT-6-PARTIAL_CORE_REMOVED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Removed incomplete core file: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> On boot of the RP, an incomplete core file was found and removed. Incomplete core files can happen for a variety or reasons, including the coincident failure of the active RP while a core file is being generated. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. This is not an error, it is an indication that the system is cleaning up a previous error. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BRELAY-3-LOCATE_FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Command could not be executed. Target FRU could not be resolved </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The brelay process is responsible for determining the target of a command, either local or a remote brelay instance. Control is returned to IOSd by exiting the brelay instance. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the status of the command target. Check the brelay log files for further indications as to why the initialization failed and if necessary restart the machine. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-3-EXEC_DIRECTIVE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] Command directive execution failed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell was unable to execute the requested directive. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the diagnostic shell trace file for more information on the underlying failure. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-3-EXEC_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] Command execution failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell was unable to execute the requested interactive command. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the diagnostic shell trace file for more information on the underlying failure. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-3-EXEC_PREPARE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] Command execution prepare failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell was unable to prepare the requested interactive command for execution. The command failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the diagnostic shell trace file for more information on the underlying failure. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-3-GET_HOSTNAME_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] Get hostname failed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell was unable to read the hostname from the kernel. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. The diagnostic shell periodically checks for hostname changes to set the user prompt. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-3-RECEIVE_MESSAGE_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] Receive message [chars] failed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell was unable to receive a message from the Shell Manager </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry the operation or start a new diagnostic shell session. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-3-SEND_MESSAGE_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] Send message [chars] failed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell was unable to send a message to the Shell Manager. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry the operation or start a new diagnostic shell session. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-3-TERMINAL_OPERATION_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] Terminal [chars] [chars] failed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell was unable to get or set terminal properties. An attempt to change or act on terminal properties failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the diagnostic shell and reattempt the failed operation </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-6-BSHELL_UPGRADE_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] New software detected. Bshell instance restarting. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell detected a new installation of diagnostic shell software. The diagnostic shell instance exits and restarts with the new software version. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is an informational message only. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-6-SESSION_ENDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] bshell session ended for user '[chars]' </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A user has exited a diagnostic shell session. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is an informational message only. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-6-SESSION_STARTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] bshell session started for user '[chars]' </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A user has started a diagnostic shell session. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is an informational message only. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-6-SMAN_CONNECTION_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] Shell Manager connect failed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell is unable to connect to the Shell Manager, possibly because the Shell Manager process is no longer available. This type of error is experienced if a software upgrade is in progress. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. Once the Shell Manager process has restarted, the diagnostic shell will reconnect. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSHELL-6-SMAN_CONNECTION_LOST </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [[chars]] Shell Manager connection lost </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The diagnostic shell was disconnected from the Shell Manager and the Shell Manager process is no longer available. This type of error is experienced if a software upgrade is in progress. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is an informational message only. No action is required. Once the Shell Manager process has restarted, the diagnostic shell will reconnect. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASFS_LOCATION_TRANSLATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to translate a location to a chasfs object name because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The backplane switch manager failed to translate a location to a chasfs object name. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASFS_OBJECT_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hardware failed to create a chassis filesystem object. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASFS_OBJECT_NOT_PRESENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] not present. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASFS_OBJECT_WATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to watch chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object was not watched because of the reason stated in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASFS_PROPERTY_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property was not properly created. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASFS_PROPERTY_GET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to read chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property was not properly read by the system. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASFS_PROPERTY_NOT_PRESENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] property [chars] not present. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASFS_PROPERTY_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to write chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property failed to write. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASSIS_STATUS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to get chassis hardware status because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to get the chassis hardware status. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for CPLD driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-CHASSIS_TYPE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The chassis type [chars] is invalid. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The chassis type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-INVALID_ARGUMENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A system function was given an invalid argument. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A system function was given an invalid argument. This is due to a software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-IPC_CONNECTION_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An IPC connection has invalid state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-IPC_CONNECT_MASTER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IPC connection to the active RP failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> IPC connection to the active RP failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-IPC_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> IPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-MESSAGE_REGISTER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to register with active RP because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The active RP failed to register. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-MESSAGE_RELAY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to relay a message because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to relay a message. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-MESSAGE_RESPONSE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An invalid message response was received because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An invalid message response was received. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-MQIPC_ADVANCE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to advance MQIPC queue because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The MQIPC initialization failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-MQIPC_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> MQIPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-PEER_TABLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A peer table initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-PLATFORM_FAMILY_TYPE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The platform family type [chars] is invalid. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The platform family type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-RESOLVE_FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to determine [chars] card because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The router failed to determine a FRU state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-SERVICES_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize general application services because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize application services. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-SIGNAL_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize signals because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize signals. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-SLOTS_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize chassis slot information because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize the chassis slot information. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-SLOT_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A card absolute slot number cannot be determined for this chassis type </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An absolute slot number is invalid. This could be due to a software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-0-UIPEER_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create user interface peer. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to create a user interface peer. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-3-BSM_SERVICE_SETUP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to setup the backplane switch manager (bsm) service </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Backplane Switch Manager failed to set itself up as a proxy to the backplane switch. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-3-CHASFS_OBJECT_DESTROY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to destroy chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object that should have been destroyed was not destroyed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-3-CHASFS_PROPERTY_DESTROY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property that should have been destroyed was not destroyed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSMRP-3-PEER_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A peer table entry has invalid state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A peer table entry has an invalid state. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> esg-bsm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BSSID_MGR_TRACE_MSG-3-WLC_GEN_ERR_TB </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BTRACE_MANAGER-3-BTRT_ERR_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Btrace Rotate Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Btrace Rotate error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BTRACE_MANAGER-4-FILTER_CONFIG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Btrace Manager UTF Filter Applied from conf file: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Btrace Filter Manager </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-trace </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> BTRACE_MANAGER-7-BTRT_LOG_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Btrace Export: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Btrace export info </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAC_TRACE_MESSAGE-5-EWLC_GEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Call admission control : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General ewlc Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_SMGR_TRACE_MESSAGE-3-DUPLICATE_IP_PORT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IP-Port mapped to more than one AP. [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> If the APs are behind NAT/PAT, one of the port is possibly mapped to multiple APs. Client may not be able to join this AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If the APs are behind NAT/PAT, kindly check if same port is mapped to multiple APs </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_SMGR_TRACE_MESSAGE-3-WLC_GEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General ewlc Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_SMGR_TRACE_MESSAGE-4-AP_MSG_THRESHOLD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Warning : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Number of messages in capwap queue crossed the threshold(exceeded or recovered) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_SMGR_TRACE_MESSAGE-5-AP_JOIN_DISJOIN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Event: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> AP Join/Disjoin Event </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_SMGR_TRACE_MESSAGE-6-WLC_APMGR_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Info : - [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller info message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_TRACE_MSG-2-MAX_SUPPORTED_AP_LIMIT_90PCT_EXCEEDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> 90%% ([dec]) of Maximum Supported AP Join Limit: [dec] exceeded </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Exceeded 90% of maximum supported AP join limit </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_TRACE_MSG-2-MAX_SUPPORTED_AP_LIMIT_EXCEEDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Maximum supported AP join limit: [dec] exceeded </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Maximum supported AP join limit exceeded </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_TRACE_MSG-3-MAX_AP_LIMIT_REACHED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Ap [chars] will be disconnected. Maximum AP Join Limit: [dec] Reached </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Maximum AP join limit reached error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_TRACE_MSG-3-MAX_LICENSE_AP_LIMIT_REACHED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Ap [chars] is not allowed to join. Please start reporting licensing to Cisco to get the ACK for resumption of normal operation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Device is not registered, maximum AP join limit reached error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_TRACE_MSG-4-EWC_AP_JOIN_DISABLED_DURING_PNP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Attempt by AP [chars] with MAC [chars] to join this controller was rejected due to PnP image download in progress </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> External AP is not allowed to join when internal AP image upgrade is going on as part of PnP image download </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_TRACE_MSG-4-EWC_AP_JOIN_DISABLED_DURING_PREDOWNLOAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Attempt by AP [chars] with MAC [chars] to join this controller was rejected due to network upgrade </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> New AP is not allowed to join during network upgrade </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_TRACE_MSG-4-EWC_AP_JOIN_DISABLED_WNCDS_CONFIG_INIT_STILL_IN_PROGRESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Attempt by AP with MAC [chars] to join this controller was rejected as WNCDs config init still in progress </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> External AP is not allowed to join as WNCD processes are still being initialized with wlan/policy/site configs </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-app-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAPAC_TRACE_MSG-4-EWC_INTERNAL_AP_JOIN_DISABLED_DURING_PNP_NO_PROVISION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Attempt by Internal AP [chars] with MAC [chars] to join this controller was rejected due to PnP Image Dwonload is in progress and PnP Provision is not Done </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Internal AP is not allowed to join in PnP image upgrade flow till the PnP Provision is done </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_ACTIVE_CHECK_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unable to determine name of AP running active controller. Please ensure internal AP has joined and try again </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Installer needs to check that the configured preferred master matches the current active controller AP name before reloading. However it was unable to determine the active controller AP name, probably because the internal AP has not joined. Please ensure that the internal AP has joined and then try again </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_ACTIVE_NOT_PREFERRED_MASTER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The configured preferred master AP name does not match the current active controller AP name. Please configure the preferred master AP name with 'wireless ewc-ap preferred-master' to match the active controller AP name as shown by 'show wireless ewc-ap redundancy summary' and try again </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Installer requires that the configured preferred master matches the current active controller AP name before reloading. Please ensure that the preferred master is configured correctly and then try again </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_AP_JOIN_IMAGE_VERSION_DOWNLOAD_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Configured image download profile failed to download version.info; check network and server configuration </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Configured image download profile may not be able to download the correct AP images </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_AP_JOIN_IMAGE_VERSION_DOWNLOAD_START_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to start downloading AP image version with error [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Configured image download profile may not be able to download the correct AP images </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_DWNLD_IMG_MASTER_INTERNAL_AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> External download for internal AP cannot start, a previous download has been already performed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> EWC image upgrade workflow requires mandatory download for new image master AP required by the internal AP. If a previous 'install add' has been performed without ativation, an 'install remove' action is needed to clear fully the previous downloads. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Execute 'install remove profile default', 'clear ap predownload statistics', and retry Network Upgrade </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_EXTERNAL_DOWNLOAD_IN_PROGRESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Controller performs another external transfer, for example a new AP joins the network. Once transfer completed, please try Network Upgrade again </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> EWC allows only one active image transfer. For an AP join case, such a transfer has to be completed/aborted before a Network Upgrade is started. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check 'show ap summary'. If the number of APs is the expected one, update the image download profile to point to the new software version, and retry Network Upgrade </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_GEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> %% Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Network not ready for this install command </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Try again later </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_NO_SPACE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> No sufficient space on bootflash for upgrade. Please do 'dir bootflash:' to list and delete unwanted files. Please do 'install remove profile default'. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No sufficient space on flash to hold the image, please do some cleanup on bootflash: </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Try 'install remove profile default' </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_AP_PREDOWNLOAD_REQUIRES_POLL_CCO_FIRST </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Please do poll-cco once before starting EWC-AP software predownload via CCO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> EWC-AP software prodownload via CCO requires polling CCO first to get suggested/latest software version </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_EWC_INTERNAL_AP_JOIN_IN_PROGRESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Internal AP has not joined the controller. Once internal AP is up, please try Network Upgrade again. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> If internal AP is not present Network Upgrade can not start. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check 'show ap summary'. Wait for internal AP is present before Network Upgrade start </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-3-CAPWAPIMGDWNLD_GEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> %% Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Improper arguments or config </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Arguments to be changed </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-4-CAPWAPIMGDWNLD_EWC_AP_AP_JOIN_IMAGE_VERSION_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Configured image download profile downloads AP image version [chars]; requires AP image version [chars] to join this controller </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Configured image download profile does not work for AP join </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-4-CAPWAPIMGDWNLD_EWC_PREMATURE_ACTIVATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Image predownload is still in progress, 'install activate' might lead to a longer upgrade of the network </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Not all APs might have the new image yet </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-5-CAPWAPIMGDWNLD_EWC_AP_AP_LIST_EVENTS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> List Event: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> EWC-AP Master/Invalid Master AP list insertion/deletion/reelection Events </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_AP_IMAGE_DELETED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Event: Downloaded AP image [chars] was deleted </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Downloaded AP image deleted </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_AP_IMAGE_WITHOUT_NODE_DELETED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Event: Downloaded AP image [chars] without image node was deleted </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Downloaded AP image deleted from RAM disk </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_AP_JOIN_IMAGE_VERSION_MATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Configured image download profile downloads AP image version [chars], matching required AP image version to join this controller </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Configured image download profile works for AP join </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_DWNLD_COMPLETE_WITHOUT_NODE_DELETED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Event: External Download complete and deleted for AP image [chars] without image node </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Downloaded AP image deleted from RAM disk </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_HARDDISK_CLEANUP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> corefiles and/or tracelogs have been deleted, [dec] Bytes disk space is freed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> corefiles and tracelogs have been deleted </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_IMAGE_MMAPED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> EWC-AP Event: EWC-AP Controller image [chars] mmaped ... Timer started to unmap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> EWC-AP Image MMaped in Memory </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_IMAGE_MMAPED_RESET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> EWC-AP Event: EWC-AP Controller image [chars] already mmaped in memory ... Timer to unmap reset </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> EWC-AP Image MMaped in Memory </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_IMAGE_MUNMAPPED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> EWC-AP Event: EWC-AP Controller image [chars] unmapped from memory ... Timer to unmap Stopped </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Controller image unmapped from memory </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_PREDOWNLOAD_AP_COUNT_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> AP Event: Predownload Total AP count [dec], predownloaded AP count [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Predownload Total and Completed AP count mismatched </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_SEND_MASTER_GOING_DOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Sending master-going-down message to other APs so that they backoff for 5 minutes for existing active controller to be active after reload </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> To prevent EWC-AP-capable AP's from becoming EWC-AP controller when current controllr goes through reload, send master-going-down message to them so they wait 5 minutes for the current controller to reboot and become controller again </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-CAPWAPIMGDWNLD_EWC_AP_WRONG_STATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Network upgrade is not in correct state. Please do 'install remove profile default', and try again </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Network Upgrade is not in correct state. Please cancel and try again </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Try 'install remove profile default' </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CAPWAP_IMGDWNLD_TRACE_MESSAGE-6-TRACE_EXPORT_TEST </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Btrace log export test event: Testing Log Export Feature </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> GUI Triggered Flow to test Log Export Feature </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-1-CERT_EXPIRED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Certificate expired </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This alert syslog is generated when the certificate used for DTLS/TLS connection towards SD-WAN controller has expired. Control connection to controllers will not come up as a result of this catastrophic failure </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please contact Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-1-CERT_EXPIRING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Certificate expiring soon. Time remaining: [dec] [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This alert syslog is generated to warn impending certificate expiry </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> New certificate should be installed prior to expiring. Please contact Cisco TAC for assistance </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-3-CERT_STORE_INIT_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Certificate store init failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This error syslog is generated when certificate store initialization fails. Control connection to controllers will not come up as a result of this failure </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please contact Cisco TAC and open a support ticket for this issue </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-5-CERT_INSTALLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A new certificate has been installed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated when a new certificate is installed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-5-CERT_UNINSTALLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Certificate has been uninstalled </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated when an installed certificate is uinstalled by administrative action </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-5-NEW_CSR_GENERATED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> New certificate signing request generated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated whenever new certificate signing request is generated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-5-ROOT_CA_CRL_INSTALLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Root CA CRL has been installed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated when a root CA Certificate Revocation List is installed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-5-ROOT_CA_CRL_UNINSTALLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Certificate has been uninstalled </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated when a root CA Certificate Revocation List is uninstalled by administrative action </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-5-ROOT_CERT_CHAIN_INSTALLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Root certificate chain installed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated when a root certificate chain is installed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT-5-ROOT_CERT_CHAIN_UNINSTALLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Root certificate chain uninstalled </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated when an installed root certificate chain is uninstalled by administrative action </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> vip-certificate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT_MGR_ERRMSG-3-CERT_MGR_GENERAL_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> General error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General cert mgr lib error message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT_MGR_ERRMSG-3-CERT_VALIDATION_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Certificate Validation Error, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT_MGR_ERRMSG-3-FIPS_AUDIT_FIA_X509_EXT_1_ITT_LSC_CA_CERT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> LSC CA certificate not generated with CA flag true </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> LSC CA certificate not generated with CA flag true </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT_MGR_ERRMSG-3-FIPS_SUITABILITY_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> FIPS Compliance: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General cert mgr lib error message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT_MGR_ERRMSG-3-PKI_SSL_IPC_RESP_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IPC Respone Error, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT_MGR_ERRMSG-3-WLANCC_UPDATE_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to send WLAN CC (Commit Criteria) update to PKI IOSd due to database error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT_MGR_ERRMSG-4-CERT_MGR_WARNING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Warning, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Wireless LAN Controller warning message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CERT_MGR_ERRMSG-6-FIPS_SUITABILITY_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> FIPS Compliance: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General cert mgr lib error message </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CFGMGR-3-ADMIN_PASSWD_UNCHANGED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to set new admin password </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This syslog is generated when the default password of admin account is not updated due to an error. This could occur during bootup when the system is initializing </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-confd-startup </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please retry updating default password for admin account. If admin password cannot be updated after couple of attempts, please contact Cisco TAC for assistance </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CFGMGR-4-ADMIN_PASSWD_CHANGE_DEFERRED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> New admin password not set yet, waiting for daemons to read initial config </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This syslog is generated when the system is initializing and user tries to update default password of admin account. Once bootup completes, config database is unlocked and admin password can be changed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-confd-startup </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This should be a temporary log, if the log continues to be seen on console, please contact Cisco TAC for assistance </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CFGMGR-6-ADMIN_PASSWD_CHANGED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Successfully set new admin password </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This info syslog is generated when the default password of admin account is updated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-confd-startup </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CFMGR_LOG-4-COUNTRY_CFG_DEPRECATED_CLI </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars]: 'ap country &lt;coutry-code&gt;' is deprecated, instead use 'wireless country &lt;country-code&gt;' </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> 'ap country &lt;code&gt;' cli has been has been deprecated, Please start using 'wireless country &lt;code&gt;' instead </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please start using new form of cli mentioned in the explanation message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CFMGR_LOG-4-UNSUPPORTED_AP_DTLS_CIPHER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unsupported AP DTLS ciphersuite: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unsupported ciphersuite for AP DTLS in a given security mode </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CFMGR_LOG-7-CFG_DOWNLOAD_LOG_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Scheduled Config Download: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Config Download info </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CGM_NGWC-3-NOMEM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> No Enough Shared Memory in CGM\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the existing ACL configuration.\n </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CHASFS-3-NOCHASFSDIR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The directory [chars] does not exist. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No explanation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CHASFS-3-NOINOTIFY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The inotify device could not be opened. Error [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This error occurs when there is an error in the system that prevents the notification facility from being accessed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CHASFS-3-NOOPEN_PROPERTY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error opening chassis file system object [chars]: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An application was not able to open a an object in its local chassis file system. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CHASFS-3-NORESOLVE_LOCAL_OBJECT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error resolving local FRU object: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An application was not able to create a reference to an object in its local chassis file system. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CIA-0-CPA_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> cpa_init failed, return code: [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> cpa_init has failed. This might be because CPA south bound libraries are missing or a mapping of CPA libraries to PD_TYPE missing in cpa_fru_db.conf </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Review cpa logs </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_EXCLUSION_AUDIT_MESSAGE-3-FIPS_AUDIT_FTA_TSE_1_CLIENT_ASSOCIATION_REJECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Client [chars] association rejected and excluded, reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Client association rejected because of excluding </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_EXCLUSION_SERVER-5-ADD_TO_EXCLUSIONLIST_REASON </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Client [chars] was added to exclusion list, reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Client was added to exclusion list </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Message notification informing about the client was added to exclusion list </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_EXCLUSION_SERVER-5-ADD_TO_EXCLUSIONLIST_REASON_DYNAMIC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Client [chars] was added to exclusion list associated with AP Name:[chars], BSSID:[chars], reason:[chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Client was added to exclusion list </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Message notification informing about the client was added to exclusion list </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_HA_SVC_MESSAGE-3-EWLC_RECREATE_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Heap recreate failure in module [chars]. [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failure seen during heap recreate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_IPV6_TRACE_MESSAGE-3-CLIENT_IPV6_CRIT_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> client_ipv6 Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Client IPv6 Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_IPV6_TRACE_MESSAGE-4-CLIENT_IPV6_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> client_ipv6 Warning: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Client IPv6 Warning Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_GTK_UNABLE_TO_UPDATE_BROADCAST_KEYS_TO_CLIENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Unable to update broadcast keys to Client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unable to update broadcast keys to Client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_DEFLECTION_ATTACK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Deflection attack detected from this mobile </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Deflection attack detected from this mobile </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_KEY_DATA_LEN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Invalid key data length </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Invalid key data length </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_KEY_TYPE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Invalid key type </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Invalid key type </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_MIC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Received Invalid MIC in EAPOL Key Message handshake </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Received Invalid MIC in EAPOL Key Message handshake </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_MIC_IN_M2 </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Received Invalid MIC in EAPOL Key Message M2 </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Received Invalid MIC in EAPOL Key Message M2 </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_REPLAY_WINDOW </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Invalid Replay Window </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Invalid Replay Window </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_INVALID_SECURE_BIT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Invalid secure bit </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Invalid secure bit </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PMK_ZERO_MIC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Zero MIC received </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Zero MIC received </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_2_PTK_UNABLE_TO_SEND_SESSION_KEY_TO_AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Unable to send Session key to AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unable to send Session key to AP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-3-FIPS_AUDIT_FTA_TSE1_DENY_CLIENT_ACCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - - Client association denied as it is not in Active Hours slot [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Received association request in non-active hours </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_AUDIT_MESSAGE-6-FIPS_AUDIT_FIA_8021X_EXT_1_CLIENT_ASSOCIATION_RECEIVED_FROM_MOBILE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [chars]: [chars] Association received from mobile on BSSID [chars] AP [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Association received from mobile on BSSID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_GUEST_LAN_LOG-3-CLIENT_JOIN_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Wired Guest client [chars] failed joining on vlan [dec] physical interface [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Wired Guest client failed joining </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, client failed joining and was deleted. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_GUEST_LAN_LOG-3-CLIENT_JOIN_FAILED_NO_MAC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Refusing creation of wired Guest client with no MAC on vlan [dec] physical interface [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Wired Guest client failed joining </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, client failed joining and was deleted. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_GUEST_LAN_LOG-5-CLIENT_JOIN_IGNORED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Already existing client [chars] join request on vlan [dec] and physical interface [chars] was ignored </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A request to join the client was ignored because the client is already connected </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_GUEST_LAN_LOG-7-CLIENT_RECEIVED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Wired Guest Client [chars] join request received on vlan [dec] - interface [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> New Wired Guest client join received </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-3-CLIENT_TRACEBACK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Client Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-4-ANCHOR_INVALID_MBSSID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Export anchor required but config is incorrect (e.g.: wlan should be up, wlan profile name and policy profile name should match) for: Wlan-Profile: [chars], Policy Profile: [chars], client [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Export anchor required but config is incorrect (e.g.: wlan should be up, wlan profile name and policy profile name should match) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that Wlan needs to be up or wlan profile name and policy profile name need to match </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-4-ANCHOR_INVALID_WLAN_ID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Export anchor required but unable to get wlan id for: Wlan-Profile: [chars], Policy Profile: [chars], client [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Export anchor required but unable to get wlan id </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that Wlan name is not configured </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-4-ANCHOR_NOT_EXPORT_WLAN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Export anchor required but wlan not configured as mobility export anchor for: Wlan-Profile: [chars], Policy Profile: [chars], client [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Export anchor required but wlan not configured as mobility export anchor </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that Wlan is not configured as mobility export anchor </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-4-ANCHOR_VAP_SECURITY_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Export anchor required but local and remote security/profile configuration is not matching for: Wlan-Profile: [chars], Policy-Profile: [chars] client [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Export anchor required but local and remote security/profile configuration (wlan and/or policy profile) is not matching </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that local and remote wlan and policy profiles need to have the same security or configuration settings </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-4-ANCHOR_WEBAUTH_ON_MAB_NOT_CONFIGURED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Export anchor: webauth on mac failure configuration mismatch between anchor and foreign for: Wlan-Profile: [chars], Policy Profile: [chars], client [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Webauth on Mac Failure configuration mismatch between anchor and foreign </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that Wlan on anchor or foreign is not configured for webauth on mac failure </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-5-ADD_TO_EXCLUSIONLIST_MAC_THEFT_REASON </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Client [chars] with IP: [chars] was added to exclusion list, legit ifid: 0x%08x, current ifid: 0x%08x, reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Blacklisting client on MAC address theft. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that there was MAC address theft. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-5-ADD_TO_EXCLUSIONLIST_REASON </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Client [chars] with IP: [chars] was added to exclusion list, legit Client [chars], IP: [chars], reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Blacklisting client on IP address theft or MAC address theft or IP and MAC address theft. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that there was IP theft or MAC address theft or IP and MAC address theft. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-5-EASYPSK_CLIENT_DELETED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Easy-PSK client [chars] : client deleted due because AAA exchange failed reason [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Easy-PSK client was deleted because of AAA Exchange failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that client was deleted due to AAA exchange failure. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-5-WEBAUTH_ON_MAB_FAILURE_ROAMING_DENIED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Client [chars] : Roaming denied, reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Roaming denied for Webauth on MAB failure client. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it means that roaming occurred with controllers with different MAC authentication lists. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-6-CLIENT_ADDED_TO_RUN_STATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Username entry ([chars]) joined with ssid ([chars]) for device with [chars] on channel ([dec]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Details for client when it goes to run state </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that client successfully went to RUN state </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-7-CLIENT_IP_UPDATED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Username ([chars]), [chars], IP [chars]IP address updated, [chars] to AP ([chars]) with SSID ([chars]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Details for client when it goes to run state </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that client successfully went to RUN state </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-7-CLIENT_MOVED_TO_DELETE_STATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Username ([chars]), [chars], IP [chars]disconnected from AP ([chars]) with SSID ([chars]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Details for client when it goes to delete state </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that client successfully went to DELETE state </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_LOG-7-CLIENT_MOVED_TO_RUN_STATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Username ([chars]), [chars], IP [chars][chars] to AP ([chars]) with SSID ([chars]) on channel ([dec]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Details for client when it goes to run state </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it implies that client successfully went to RUN state </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_VLAN_OVERRIDE_LOG-7-CLIENT_VLAN_OVERRIDE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Client [chars] on wlan [chars] and policy profile [chars] received a vlan override after web-authentication and it is moved to the new VLAN to learn a new IP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The client received a vlan override after web-authentication </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_VLAN_OVERRIDE_LOG-7-CLIENT_VLAN_OVERRIDE_TIMEOUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Client [chars] on wlan [chars] and policy profile [chars] failed to re-associate and learn a new IP after the VLAN Override and is deleted </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The client needs to re-associate within 30s after a vlan override otherwise it is deleted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLIENT_ORCH_VLAN_OVERRIDE_LOG-7-FOREIGN_CLIENT_VLAN_OVERRIDE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Export foreign client [chars] on wlan [chars] and policy profile [chars] received a vlan override from export anchor </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The export foreign client received a vlan override from anchor </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_ONBOARDING_DRAGONFLY-3-CLOUDM_ONBOARDING_HTTPCON_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] with HTTP connection error: [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> received an httpcon error while onboarding controller </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cloudm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_ONBOARDING_DRAGONFLY-3-CLOUDM_ONBOARDING_HTTP_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] with HTTP status code [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> received an http error while onboarding controller </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cloudm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_ONBOARDING_DRAGONFLY-6-CLOUDM_ONBOARDING_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Successfully [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Successfully onboarded, otp updgraded, or received access token for device </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cloudm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_ONBOARDING_SPACES-3-CLOUDM_ONBOARDING_SPACES_AUTH_TOKEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cisco Spaces persistent credentials could not be installed for [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Spaces persistent credential installation went through errors </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cloudm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it means persistent credentials for Spaces could not be installed for errors </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_ONBOARDING_SPACES-3-CLOUDM_ONBOARDING_SPACES_OTP_INSTALL_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cisco Spaces OTP could not be installed for [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Spaces OTP installation went through errors </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cloudm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it means OTP for Spaces could not be installed for errors </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_ONBOARDING_SPACES-6-CLOUDM_ONBOARDING_SPACES_ACCESS_TOKEN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cisco Spaces access token has been updated. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Updated access token for Spaces </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cloudm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it means access-token for Spaces have been installed </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_ONBOARDING_SPACES-6-CLOUDM_ONBOARDING_SPACES_ACCESS_TOKEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cisco Spaces access token could not be installed for [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Spaces access token installation went through errors </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cloudm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it means access token for Spaces could not be installed for errors </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_ONBOARDING_SPACES-6-CLOUDM_ONBOARDING_SPACES_AUTH_TOKEN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cisco Spaces persistent credentials have been installed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Installed persistent client-credentials for Spaces </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cloudm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it means client-credentials for Spaces have been installed </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_ONBOARDING_SPACES-6-CLOUDM_ONBOARDING_SPACES_OTP_INSTALL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cisco Spaces OTP has been installed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Installed OTP for Spaces </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cloudm </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this message occurs, it means OTP for Spaces has been installed </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLOUDM_TEST-6-HTTP_RESPONSE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Completed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Result of the test request </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-ui </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLUSTERMGR-1-PLATFORM_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> \n Platform mismatch detected. A stack cannot be formed with peer switch: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The peer switch is incompatible and cannot join the stack. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-clustering </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Replace peer switch with platform compatible switch </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLUSTERMGR-1-RELOAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> \n Reloading due to reason [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The specified switch has received a reload request and is being reloaded. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-clustering </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CLUSTERMGR-6-DUAL_ACTIVE_CFG_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> \n Dual Active Detection [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Switch detected availability or unavailability of Dual Active Detection ports. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-clustering </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_IDPROM_ENVMON-3-CMAN_IDPROM_FIELD_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The idprom contains an invalid environmental monitoring field. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_INIT-1-CMAN_BOOT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CMAN: [chars]\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CMAN Initialization has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_INIT-1-CMAN_INIT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CMAN: [chars]\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CMAN Initialization has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_LED-6-BEACON_LED_TURNED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Slot [dec] Beacon LED turned [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Beacon LED turned ON/OFF. This is a notification message only.No action is required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is a notification message only. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_LED-6-CHASSIS_BEACON_LED_TURNED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Chassis Beacon LED turned [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Beacon LED turned ON/OFF. This is a notification message only.No action is required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is a notification message only. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_NYQ-1-CMAN_INIT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CMAN: [chars]\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CMAN Initialization has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_SEM-2-SEM_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SEM event has occurred in device [chars]. Event code: [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Single Event Upset (SEU) event has occurred in one of the FPGA. These events may occur at any point of time, but are considered to be rare. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If the error is seen only once, there is no need for anything to be done. If these errors are appearing continuously/persistently, please copy over the logs as they appear in the console, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_THERMAL-1-THERMAL_GREEN_THRESHOLD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hotspot temperature has exceeded GREEN threshold\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The switch is too cold. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_THERMAL-1-THERMAL_RED_THRESHOLD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hotspot temperature has exceeded RED threshold. Switch will shutdown soon.\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hotspot temperature is critically overheated. The switch will soon shutdown to prevent permanent damage. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMAN_THERMAL-2-THERMAL_YELLOW_THRESHOLD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hotspot temperature has exceeded YELLOW threshold\n </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hotspot temperature is too high. Improve cooling immediately. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-C2W_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP C2W has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The C2W bus on the SIP is used to read the shared port adapter (SPA) IDPROM. This error indicates that the SIP C2W bus failed to initialize. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for C2W driver errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CHASFS_LOCATION_TRANSLATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to translate a location to a chasfs object name because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to translate a data sensor location to the chassis filesystem (CHASFS) module. This error could be caused by a software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CHASFS_OBJECT_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to create a chassis filesystem object. This error could be caused by a software defect or a filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CHASFS_OBJECT_NOT_PRESENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] not present. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system was unable to find an expected chassis filesystem object. This error could be caused by a software defect or a filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CHASFS_OBJECT_WATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to watch chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to watch a chassis filesystem object. This error could be caused by a software defect or a filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CHASFS_PROPERTY_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to create a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CHASFS_PROPERTY_GET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to read chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to read a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CHASFS_PROPERTY_NOT_PRESENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] property [chars] not present. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system cannot locate a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CHASFS_PROPERTY_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to write chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to write a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CHASSIS_TYPE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The chassis type [chars] is invalid. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system has detected an invalid chassis type. This error could be caused by a hardware defect, software defect, or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for IDPROM or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CPLD_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP CPLD has failed initialization :[chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A SIP complex programmable logic device (CPLD) failed to initialize. This error could be caused by a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for CPLD driver or hardware errors. Verify that the software and CPLD versions are compatible. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CPLD_INTR_ENABLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The CPLD initialization has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The CPLD interrupt enable failed to initialize. This error could be caused by a hardware defect or CPLD driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for CPLD driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-CPLD_IOCTL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A CPLD driver I/O control has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A complex programmable logic device (CPLD) I/O driver control has failed. This error could be caused by a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for CPLD driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-FLOW_CONTROL_MBE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Multi-bit ECC error seen, Cause [chars], MIP100 is going to be reloaded to recover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Non correctable multi bit errors were detected in the FPGA. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> MIP100 is reloaded to correct the error. If the problem persists, the MIP100 hardware may need to be replaced. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-FPGA_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The CC has failed initialization because [chars]. Reloading the card </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FPGA on the carrier card has failed to initialize. This error could be caused by a hardware </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the driver logs or hardware errors. Decode the core accompanied with this error. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-HTDP_ENABLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The HTDP initialization has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Hypertransort datapath failed to initialize. This error could be caused by a hardware defect or HTDP driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for HTDP driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-HT_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP HyperTransport has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A SIP HyperTransport (HT) CPU bus failed to initialize. This error could be caused by a hardware defect or HT driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for HT driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-HT_IOCTL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A SIP HyperTransport driver I/O control has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or HT driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for HT driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-IPC_CONNECTION_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An IPC connection has invalid state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An inter-process communication (IPC) connection has an invalid state. This error could be caused by a software defect or system resource limitation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-IPC_CONNECT_MASTER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IPC connection to the active RP failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The inter-process communication (IPC) connection to the active route processor (RP) failed. This error could be caused by a software defect or system resources limitation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-IPC_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An inter-process communication (IPC) initialization failed. This error could be caused by a software defect or system resource limitation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-PCI_RESCAN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The PCIE bus could not be rescanned because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The PCIE bus failed to rescan. This error could be caused by a hardware defect, software driver defect, or improper internal configuration. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for PCIE bus driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-PEER_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A peer table entry has invalid state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An invalid state occurred in a peer table entry. This error could be caused by a software defect or system resource limitation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-PLIM_HALT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A PLIM driver has critical error [chars], [dec], param %x param %x </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or an HT driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. If the problem persists, you may need to replace the PLIM. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-PLIM_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The PLIM has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The physical layer interface module (PLIM) failed to initialize. This error could be caused by a hardware defect or a PLIM driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for PLIM driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-PLIM_IOCTL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A PLIM driver I/O control has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A physical layer interface module (PLIM) driver I/O has failed. This error could be caused by a hardware defect or a PLIM driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for PLIM driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-SERDES_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP Serial Bridge ASIC has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The SIP serial bridge ASIC failed to initialize. This error could be caused by a hardware defect, software driver defect, or improper internal configuration. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for serial bridge ASIC driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-SERVICES_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize general application services because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize certain application services. This error could be caused by a software defect or system resource limitation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-0-UIPEER_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create user interface peer. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to create a user interface peer. This error could be caused by a software defect or system resource limitation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-BAD_ID_HW </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed Identification Test in [chars]. The module [chars] on the slot [dec] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Hardware in the specified location could not be identified as a genuine Cisco product </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cbr-platform-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-BAD_ID_HW_SLOT_STR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed Identification Test in [chars]. The module [chars] on the [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Hardware in the specified location could not be identified as a genuine Cisco product </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-CC_SPA_MOVE_SM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> ***** CMCC SPA SM was strucked for a minute in state: s_kill_wait for slot [dec], moving the state machine </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CMCC SPA SM was strucked for a minute in state: s_kill_wait for the line card. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> move the cmcc spa state machine. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-CC_SPA_PSM_READY_NOT_RCVD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> ***** CMCC did not received PSM READY event [dec] sec for slot [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CMCC SPA SM was not received PSM READY for 100 sec. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> do remove hard. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-CC_SPA_STRUCK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> ***** CMCC SPA SM was strucked for [dec] seconds for slot [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CMCC SPA SM was strucked for a minute in state: s_kill_wait for the line card. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> move the cmcc spa state machine. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-FRU_HWPRG_UPG_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to [chars] [chars] hardware programmable on [chars] in [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Upgrade hw-programmable failed to upgrade the CPLD/FPGA firmware on the given FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the card and retry to program the hw-programmable. If the card fails to come up please contact TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-FRU_HWPRG_UPG_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Success to [chars] [chars] hardware programmable on [chars]. Please execute the POST Upgrade CLI: upgrade hw-programmable cable &lt;r0/r1&gt; daybreak post-upgrade slot &lt;slot&gt; to finish the upgrade process </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Upgrade hw-programmable success to upgrade the CPLD/FPGA firmware on the given FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-FRU_IOFPGA_UPG_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to upgrade field programmable device on [chars] in slot [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Upgrade of field programmable device failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the card and retry to program the field programmable device. If the card fails to come up please contact TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-FRU_IOFPGA_UPG_LC_PWR_CYCLE_DONE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Power cycled the [chars] in slot [dec], after FPGA upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Power cycled the card after FPGA upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Line card has been power cycled after FPGA upgrade. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-FRU_IOFPGA_UPG_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Successfully upgraded the field programmable device on [chars] in slot [dec]. Power-cycling the line card. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Upgrade field programmable device was successful on the given FRU. Line card needs to be power-cycled or removed and re-inserted for upgrade to take effect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Line card needs to be power cycled or removed and re-inserted for the upgrade to take effect. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-2-FRU_LC_PWR_RESET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> ***** Detected power reset for the Line card in slot [dec]. To recover from the error, Line card will brought up shortly </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Detected Auto power reset(may be HW issue) for the Linecard. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Pseudo OIR of the Line card has been to recover/bring up the card. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-C2W_READ </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An C2W read has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An attempt to read the C2W bus has failed. This error could be caused by a hardware or software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for C2W driver errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-C2W_WRITE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An I2C write has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An attempt to write to the inter-integrated circuit (I2C) has failed. This error could be caused by a hardware or software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for I2C driver errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-CARD_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The CONFIG&PICTYPE in slot [dec] mismatch : CONFIG : [chars], PIC : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The CMD and PIC in the slot mismatch. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Shut down the LC and change the card mode or remove the pic card. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-CC_HOTSWAP_CKT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hot Swap Circuit has failed for bay [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Hot Swap Circuit for the SPA bay has been tripped. This error could be caused by bad SPA or CC hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the CMCC and PSM OIR logs. Verify whether the recovery reload could bring up the SPA </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-DDR_SINGLE_BIT_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Single-bit DRAM ECC error: mme: [dec], sbe: [dec], address: 0x%08X, pid: [dec], name: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The SIP DRAM experienced a single-bit error checking code (ECC) error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This error is usually self-correcting. If the problem persists, you may need to replace the SIP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-FLOW_CONTROL_SBE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Single-bit ECC error seen, Cause [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Self correctable single bit errors were detected in the FPGA </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This error is usually self-correcting. If the problem persists, the MIP100 hardware may need to be replaced. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-FPGA_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] FPGA error detected: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A SIP field programmable logic device failure detected. This error could be caused by a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for FPGA driver or hardware errors. Verify that the software and firmware versions are compatible. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-HB_TIMEOUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Periodic Heartbeat message from RP timed out. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> RP sends periodic heartbeat message to the SIP. The SIP did not receive this heartbeat message for last timeout period. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-HT_DETACH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP HyperTransport has failed detachment because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A SIP HyperTransport (HT) CPU bus failed to detach from software during SIP MDR. This error could be caused by a hardware defect or HT driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-IDPROM_ACCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed access or process an IDPROM because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to access an IDPROM or an IDPROM process failed. This error could be caused by a hardware defect, software defect, or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for IDPROM or hardware errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-IDPROM_SENSOR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> One or more sensor fields from the idprom failed to parse properly because [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> One or more IDPROM sensors failed to parse. This error most likely occurred because of a checksum failure in the IDPROM. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for IDPROM or hardware errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-INCOMPATIBLE_STANDBY_SUPERVISOR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Standby supervisor in slot [dec] is not compatible with the Active supervisor; Standby Supervisor will be reloaded. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Supervisor found in Standby slot may not be fully compatible with the active supervisor and may cause issues. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Use supervisors with the same specifications to enable High Availablitly features. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-LC_FPGA_UPGRADE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The FPGA upgrade request for linecard in switch [dec] slot [dec] failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Upgrade of FPGA on the linecard failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the card and retry to program the field programmable device. If the card fails to come up please contact TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-LC_FPGA_UPGRADE_PWR_CYCLE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Power cycle failed for the linecard in switch [dec] slot [dec], after FPGA upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Power cycle failed for the linecard after FPGA upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> OIR the card and retry to program the field programmable device. If the card fails to come up please contact TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-MASTERSHIP_WATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize a watch on the active rp because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The cc process has failed to setup a watch on the rp chasfs active-rp property. This error is likely caused by a problem with chasfs as a whole. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs to determine the exact reason for the failure. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-MESSAGE_RESPONSE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An invalid message response was received because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An invalid message response was received. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-NETWORK_CLOCK_CAL_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP network clock jitter attenuator calibration fails </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The SIP network clock jitter attenuator calibration can not complete within certain time. This would incur some SPA LOS alarms or other error events for some SPA port types. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-NETWORK_CLOCK_CAL_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP network clock jitter attenuator is calibrating </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The SIP network clock jitter attenuator is calibrating after device initilization stage. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP if SPA LOS alarms are seen after this. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-NETWORK_CLOCK_DH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP network clock jitter attenuator has entered digital holdover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A SIP network clock jitter attenuator has entered digital holdover mode and certain SPAs may report LOS alarms. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-NETWORK_CLOCK_LOS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP network clock jitter attenuator has lost signal </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A SIP network clock jitter attenuator has lost signal from the WAN PLL and certain SPAs may report LOS alarms. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the SIP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-PLIM_DETACH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The PLIM has failed detachment from software because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The physical layer interface module (PLIM) failed to detach from software. This error could be caused by a hardware defect or a PLIM driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-PLIM_RESTART </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The PLIM has failed to restart because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The physical layer interface module (PLIM) failed to restart during SIP MDR. This error could be caused by a hardware defect or a PLIM driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-PLIM_STATUS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A PLIM driver informational error [chars], block %x count %x </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or an HT driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for PLIM or hardware errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-SCOOBY_ILAK_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to bringup the Interlaken interface. Cause: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Interlaken Rx or Tx failed for this card. This error could be caused by a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the Linecard. If the problem still persists, replace the Linecard. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-SIP_MDR_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP failed Minimal Disruptive Restart because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The SIP failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SIP by resetting the SIP hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-SPA_HOTSWAP_CKT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SPA on bay [dec] has tripped the Hot Swap Circuit during power-up. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Hot Swap Circuit for te SPA bay has been tripped. This error could be caused by bad SPA hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the CMCC and PSM OIR logs. Verify whether the recovery reload could bring up the SPA </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-SPA_MDR_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SPA in bay [dec] failed Minimal Disruptive Restart because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The SPA in bay %u failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SPA by resetting the SPA hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-SPA_ONLINE_REQ_TERMINATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The online request for SPA in subslot [dec]/[dec] was terminated because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The online request for SPA in subslot %d/%u was terminated. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-SPA_PSEUDO_HARD_OIR_VFT_NOT_IMPLEMENTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The PSEUDO OIR VFT is not implemented for bay [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The pseudo OIR vft not implemented for this platform </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Do nothing </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-SPA_SOFT_STOP_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SPA in bay [dec] could not be soft stopped because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The SPA in bay %u could not be soft stopped. An attempt will be made to recover the SPA by resetting the SPA hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-SSD_PIDA_OIR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hot insertion/removal of SSD module in [dec]/[dec] not supported. Please reload the router with SSD module installed in bay 3 </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Hot swapping of SSD is not supported </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the router with SSD module installed in bay 3. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-STANDBY_EOBC_LINK_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Standby EOBC link error detected. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Standby EOBC link error: either link state is down, or duplexity is not full, or speed is not 1Gbps. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system hardware. Re-seat and securely screw in all FRUs. If the problem persists, please contact TAC support. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-UNKNOWN_3RDPARTY_MODULE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unknown 3rd-party module was inserted in subslot [dec]/[dec]. please check whether the 3rdparty-mode is configured for this subslot </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unknown 3rd-party module was inserted in the given subslot. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-UNKNOWN_SPA_LC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unknown SPA was inserted in slot [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unknown SPA was inserted in the given slot. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the unsupported SPA line card and upgrade the software as needed. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-3-UNSUPPORTED_LC_TYPE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An unsupported card of type [chars] is inserted in slot [dec] of the chassis. Remove the card from the chassis or upgrade to an image which supports the card </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unsupported line card was inserted in the given slot. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the unsupported SPA line card and upgrade the software as needed. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-5-C9400X_LC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> C9400X-SUP-2 supports 240G per slot with [chars] installed in Slot [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Informational message that 480G Linecard is installed in the chassis with Supervisor card that supports only 240G per slot. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational notification. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-5-CMCC_EZMAN_HB_MISS_EXCEED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CMCC Missed [dec] Heartbeats from EZMAN, Reloading the Line Card </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CMCC Monitors the Health of the EZMAN by keeping a track of the Heartbeat messages. In case the EZMAN gets stuck in a event under watchdog disable context (sw_wdog_disbale), then the CMCC will stop getting these updates. The CMCC after a certain period of time would reset the card, since EZMAN is unresponsive </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the card, a software initated to restart the EZMAN </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-5-SERDES_BLOCK_EVENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A SerDes link informational error [chars], block %x count %x </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A serial bridge I/O event has occurred. This event is not serious but is logged for diagnostic purposes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-5-SERDES_RX_RESET_EVENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Interlaken Rx Alignment Status [chars], Retry Count [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Rx Sync Failed for Interlaken, Status Timer Expired. So, Resetting the Rx Interlaken Core </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-5-SPA_MDR_DONE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SPA[dec] completed Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Informational message that the Minimal Disriptive Restart of a particular SPA has completed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational notification. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-5-SPA_MDR_INIT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SPA[dec] initiated Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Informational message that the Minimal Disriptive Restart of a particular SPA has begun. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational notification. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FLOW_CONTROL_OTHER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Flow control error seen, Cause [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Flow control error is detected in the FPGA </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Appropriate action is taken in software to correct this error. If the problem persists, the MIP100 hardware may need to be replaced. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_HWPRG_UPG_ADM1266_CFG_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable ADM1266 Configurations on [chars] in slot [chars] were successfully programmed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable ADM1266 configuration was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_HWPRG_UPG_LMK03328_CFG_RESET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable LMK03328 Configurations on [chars] in slot [chars] were successfully partially programmed, please reload it to continue programming. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable LMK03328 configuration was partially upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_HWPRG_UPG_LMK03328_CFG_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable LMK03328 Configurations on [chars] in slot [chars] were successfully programmed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable LMK03328 configuration was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_HWPRG_UPG_PSOC_PREPARE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable PSOCs on [chars] in slot [chars] were set in the golden mode. The card will reload to finish the upgrading </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable PSOCs were set in the golden mode for FPD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_HWPRG_UPG_PSOC_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable PSOCs on [chars] in slot [chars] are upgrading, please don't reload or power-cycle this card. It will take about 2 mins to finish. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable PSOC is upgrading </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_HWPRG_UPG_PSOC_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable PSOCs on [chars] in slot [chars] were successfully programmed. The card will reload to make new firmware work. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable PSOC was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_HWPRG_UPG_TPS40422_CFG_RESET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable TPS40422 Configurations on [chars] in slot [chars] were successfully partially programmed, please reload it to continue programming. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable TPS40422 configuration was partially upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_HWPRG_UPG_TPS40422_CFG_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable TPS40422 Configurations on [chars] in slot [chars] were successfully programmed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable TPS40422 configuration was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_IOFPGA_UPG_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Field programmable device on [chars] in slot [dec] is being upgraded. It will take about 2 mins to finish the upgrade. Please do not reload or power-cycle this card while upgrade is in progress. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The field programmable device on the FRU is upgrading </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_LC_UPGRADE_REQD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Found mismatch between the Line card FPGA versions bundled in Software and programmed in Hardware in slot [dec]. FPGA version bundled in SW: %x, present in HW: %x. To upgrade the FPGA to version bundled in SW, perform physical OIR of the line card or run the CLI: hw-module subslot &lt;slot&gt;/&lt;SPA no.&gt; oir power-cycle </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> New FPGA is bundled in SW. FPGA upgrade is needed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> To upgrade to latest FPGA, do physical OIR Line card or do Pseudo OIR of the line card using CLI: hw-module subslot &lt;slot&gt;/&lt;SPA no.&gt; oir power-cycle; To view the present FPGA versions in chassis, use the CLI: show firmware version all </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_UPGRADE_REQD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Slot [dec] needs firmware upgrade. Firmware upgrade is traffic impacting. To perform firmware upgrade use any of the 3 options: Option 1: Perform physical removal and insertion of the line card. Option 2: Run the &lt;CLI&gt; 'hw-module subslot [dec]/0 oir power-cycle' &lt;/CLI&gt;. Option 3: Perform manual upgrade using &lt;CLI&gt; 'upgrade hw-programmable all filename bootflash: all' &lt;/CLI&gt;. Use &lt;CLI&gt;'show firmware version all'&lt;/CLI&gt; to know the mismatch </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> New version bundled in Software & Current Hardware running version is not latest. upgrade is needed. please follow the options provided </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> To perform firmware upgrade use any of the 3 options: Option 1: Perform physical removal and insertion of the line card Option 2: Run the &lt;CLI&gt; 'hw-module subslot &lt;slot&gt;/0 oir power-cycle' &lt;/CLI&gt; Option 3: Perform manual upgrade using &lt;CLI&gt; 'upgrade hw-programmable all filename bootflash: all' &lt;/CLI&gt; Use &lt;CLI&gt;'show firmware version all'&lt;/CLI&gt; to know the mismatch </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-FRU_VER_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars]: Found mismatch between the versions bundled in Software and programmed in Hardware in slot [dec]. Version Present in HW: %x, Version present in SW Bundle: %x. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> New FW is bundled in SW. FW upgrade is needed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> To perform firmware upgrade use any of the 3 options: Option 1: Perform physical removal and insertion of the line card Option 2: Run the &lt;CLI&gt; 'hw-module subslot &lt;slot&gt;/0 oir power-cycle' &lt;/CLI&gt; Option 3: Perform manual upgrade using &lt;CLI&gt; 'upgrade hw-programmable all filename bootflash: all' &lt;/CLI&gt; Use &lt;CLI&gt;'show firmware version all'&lt;/CLI&gt; to know the mismatch </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-LC_FPGA_UPGRADE_NOT_REQUIRED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> FPGA version on linecard in switch [dec] slot [dec] is 0x%x </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Upgrade of FPGA on the linecard is not required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-LC_FPGA_UPGRADE_PWR_CYCLE_DONE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Power cycled the linecard in switch [dec] slot [dec], after FPGA upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Power cycled the linecard after FPGA upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-LC_FPGA_UPGRADE_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Linecard fpga device in switch [dec] slot [dec] is being upgraded. It will take about 5 mins to complete the upgrade Linecard will power-cycled automatically during this process. Please do not reload or power-cycle the linecard when upgrade is in progress </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The fpga device on the linecard is upgrading </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-LC_FPGA_UPGRADE_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Successfully upgraded the field programmable device on linecard in switch [dec] slot [dec]. The line card will be power cycled </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Upgrade field programmable device was successful on the given FRU. Linecard needs to be power-cycled or removed and re-inserted for upgrade to take effect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Line card needs to be power cycled or removed and re-inserted for the upgrade to take effect. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-MGMT_SFP_INSERT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> transceiver module inserted in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC-6-MGMT_SFP_REMOVED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Transceiver module removed from [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The online insertion and removal (OIR) facility detected the removal of a transceiver module from the interface specified in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMCC_LED-6-BEACON_LED_TURNED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Slot [dec] Beacon LED turned [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Beacon LED turned ON/OFF. This is a notification message only.No action is required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is a notification message only. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMDMA-2-FPGA_DOWNLOAD_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Critical Error is detected while downloading the FPGA. After this card will reboot. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Due to timing issue in DMA sometime FPGA download failure is seen </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Contact your Cisco technical support representative and provide the system report and crash file. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMDMA-6-FPGA_DOWNLOAD_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] fpga DMA download [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This is informative message about the start/complete of the fpga DMA download </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMEM-3-SENSOR_INIT_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Sensor ([chars]) initialization failed due to [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This error indicates that environmental monitor software cannot initialize the sensor. The software will not register and monitor this sensor. This could occur when the IDPROM has a bad I2C address for this sensor. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMEM-4-OBFL_INIT_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> OBFL initialization failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This error indicates the OBFL dedicated filesystem is not mounted. OBFL diagnostic information will not be retained for customer troubleshooting. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFC-0-CHASFS_PROPERTY_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property was not properly created. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFC-0-CHASFS_PROPERTY_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to write chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property failed to write. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFC-3-IDPROM_ACCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to access or process IDPROM '[chars]': [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed access or process an IDPROM. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-0-CPLD_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CPLD initialization has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The CPLD has failed to initialize. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-0-CPLD_IOCTL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A CPLD driver I/O control has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A complex programmable logic device (CPLD) I/O driver control has failed. This error could be caused by a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for CPLD driver and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-0-SPI4_MUX_HALT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SPI4 MUX driver has detected a critical error [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A SPI4 MUX driver has failed or detected a critical hardware fault. This could be due to a hardware defect or driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> The only corrective action is to restart the FP </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-2-BAD_ID_HW </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed Identification Test in [chars]. The module [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Hardware in the specified location could not be identified as a genuine Cisco product </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cbr-platform-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-2-FPGA_DOWNLOAD_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Critical Error is detected while downloading the FPGA. After this card will reboot. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Due to timing issue in DMA sometime FPGA download failure is seen </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Contact your Cisco technical support representative and provide the system report and crash file. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-2-UADP_EVENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> UADP EVENT (ASIC #[dec] [chars]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unified Access Datapath ASIC Event </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Copy the message exactly as it appears on the console or in the system log. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-CPLD_ECSR_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An error has been detected on the ECSR bus </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error has been detected on the ECSR bus. This may cause problems when accessing the fowarding processor </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. Please check the chassis-manager logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-CPLD_ERP_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An error has been detected on the ERP bus (cause [dec], phase [dec]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error has been detected on the ERP bus. This may cause problems when accessing the fowarding processor </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. Please check the chassis-manager logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-DDR_SINGLE_BIT_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Single-bit DRAM ECC error: mme: [dec], sbe: [dec], address: 0x%08X, pid: [dec], name: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A single-bit data corruption error has occurred in the forwarding processor (FP). </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> These errors are self-correcting. If the problem persists, the FP hardware may need to be replaced. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-DPP_MAC_LINK_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> DPP Mac Link failed [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> One or more Mac links of DPP blocks failed. It could be because of a configuration error or hardware failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine show hardware platform cman fp for detailed Report. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-DPP_SERDES_SYNC_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> UADP fabric interface synchronisation [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> One of more UADP fabric interface Serdes failed to sync, This could be due to a hardware defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-FPGA_IMG_ABSENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> FPGA image is absent please contact Cisco technical support representative. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Due to corruption is file system FPGA images are deleted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Contact your Cisco technical support representative and provide the tracelogs. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-HB_TIMEOUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Periodic Heartbeat message from RP timed out. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> RP sends periodic heartbeat message to the ESP. The ESP did not receive this heartbeat message for last timeout period. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-HT_FATAL_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize the HyperTransport interface to the QFP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The HyperTransport interface to the QFP failed to initialize completely. Software will restart the ESP to recover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-IDPROM_ACCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed access or process an IDPROM because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Access to an IDPROM failed due to a hardware or software defect, or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for IDPROM and hardware errors. Copy the error message and related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered nformation. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-IDPROM_SENSOR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> One or more sensor fields from the idprom failed to parse properly because [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Output from the IDPROM sensors failed to parse, commonly caused by a checksum failure in the IDPROM. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for IDPROM and hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-MASTERSHIP_UPDATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An error ([chars]) has occurred while communicating the mastership role of this FP to the CPP. The FP is currently [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error occurred while communicating a change in the state (Active, Active with a Standby, or Standby) of the forwarding processor (FP). The error can cause an inconsistency of expected states between FPs and could affect the replication of state between the FPs. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. This error is usually temporary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-MASTERSHIP_WATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize a watch on the active rp because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The fp process has failed to setup a watch on the rp chasfs active-rp property. This error is likely caused by a problem with chasfs as a whole. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs to determine the exact reason for the failure. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-N2_DDR_MBE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The encryption processor has detected an uncorrectable multi-bit error in memory at address [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The encryption processor has detected an uncorrectable multi-bit in memory. This could be due to a hardware defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for encryption processor hardware errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-N2_FATAL_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An error has been detected on encryption processor: type [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error has been detected on encryption processor. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please check the chassis-manager logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-N2_INPUT_EXCEPT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Crypto device overloaded. : type [chars]: 0x%08X </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An exception has been detected on encryption processor. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please lower crypto traffic rate. If the error still happens, encryption processor may stop processing. Need to reload ESP. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-OCT_DRV_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An error has been detected on encryption processor: [chars]: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error has been detected on encryption processor. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please check the chassis-manager logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-SBUS_FATAL_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SBUS Controller not responding, bringing down [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Spico SBUS controller fails to repsond, This could be due to a hardware defect. Reset the CHIP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-SIF_SERDES_SYNC_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Sif Serdes Sync Failed for Supervisor Failure Bitmap 0x%x </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> One of more Supervisor ASIC Sif Serdes failed to sync, This could be due to a hardeware defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the show hardware platform cman fp for detailed Sif Serdes Report. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-SPI4_MUX_STATUS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SPI4 MUX driver has detected a informational error [chars] (occurred [dec] time(s)) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A SPI4 MUX driver has failed or detected a information hardware fault. This could be due to a hardware defect or driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for SPI4 MUX and hardware errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-3-STANDBY_EOBC_LINK_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Standby EOBC link error detected. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Standby EOBC link error: either link state is down, or duplexity is not full, or speed is not 1Gbps. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system hardware. Re-seat and securely screw in all FRUs. If the problem persists, please contact TAC support. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-6-CRYPTO_MODULE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Crypto Hardware Module is [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The log is to indicate whether Crypto Hardware Module IPSECHW is physically inserted in the chassis. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-6-DPP_SERDES_SYNC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> UADP fabric interface synchronisation [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The log is to indicate UADP fabric interface Serdes Sync succeeded during intialization of setup. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMFP-6-N2_DRV_UPDATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware crypto device disabled. [chars]: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A crypto device driver has failed or detected a hardware fault. This could be due to a hardware defect or driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> The only corrective action is to restart the ESP </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMLIB-2-IDPROM_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Invalid IDPROM assembly number 0x%04X. IDPROM update required </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> IDPROM assembly number is not supported. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> IDPROM update is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMLIB-3-THROUGHPUT_VALUE_APPLY_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Throughput [chars] [chars] - failed to persist throughput of [chars] kbps. Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Status indicating that a failure was observed during the writing of the throughput to persistent store. The error reason may shed light on the cause. The throughput value may have be used to configure the CPP hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the ios, chassis-manager and license-manager logs for possible clues. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMLIB-3-THROUGHPUT_VALUE_SETUP_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Throughput [chars] [chars], throughput set to [chars] kbps. Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Status indicating that a failure was observed during the setup of the throughput. The error reason may shed light on the cause. The set value is used to configure the CPP hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the ios, chassis-manager and license-manager logs for possible clues. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMLIB-4-FW_CHECK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> slot [chars]: [chars] current firmware version is [chars], while the minimum required version is [chars]. Please upgrade it to minimum required version or higher. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Firmware version in the specified location is lower than minimum required version </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Upgrade firmware version to latest. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMLIB-6-THROUGHPUT_VALUE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Throughput [chars] [chars], throughput set to [chars] kbps </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Status indicating whether appropriate throughput is found or enabled and ensuring the value is used to configure the CPP hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. This is an informational message indicating that the throughput is configured. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASFS_LOCATION_TRANSLATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to translate a location to a chasfs object name because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The chassis manager failed to translate a location to a chasfs object name. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASFS_OBJECT_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hardware failed to create a chassis filesystem object. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASFS_OBJECT_NOT_PRESENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] not present. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASFS_OBJECT_WATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to watch chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object was not watched because of the reason stated in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASFS_PROPERTY_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property was not properly created. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASFS_PROPERTY_GET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to read chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property was not properly read by the system. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASFS_PROPERTY_NOT_PRESENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] property [chars] not present. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASFS_PROPERTY_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to write chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property failed to write. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASSIS_ID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error while updating chassis id, Error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The chassis Id is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASSIS_STATUS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to get chassis hardware status because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to get the chassis hardware status. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for CPLD driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CHASSIS_TYPE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The chassis type [chars] is invalid. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The chassis type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CLOCK_MASTERSHIP_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to set CLOCK mastership because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The router failed to establish CLOCK mastership. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CPLD_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP CPLD has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP CPLD has failed to initialize. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-CPLD_IOCTL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A CPLD driver I/O control has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A CPLD driver I/O control has failed. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-DDR_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP DDR has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP DDR has failed to initialize. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for DDR or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-EHSA_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> EHSA initialization has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> EHSA has failed initialization. This could be due to a hardware or software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-EHSA_STATE_GET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to get EHSA state because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to get EHSA state. This could be due to a hardware or software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-EHSA_STATE_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to set EHSA state because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to set EHSA state. This could be due to a hardware or software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-FP_MASTERSHIP_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to set FP mastership because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The router failed to establish ESP mastership. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-HT_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP HyperTransport has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP HyperTransport has failed initialization. This could be due to a hardware defect or HT driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for HT driver and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-HT_IOCTL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A RP HyperTransport driver I/O control has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A RP HyperTransport driver I/O has failed. This could be due to a hardware defect or HT driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for HT driver and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-I2C_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP I2C has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP I2C has failed to initialize. These components provide low-level communications between the RP and the other cards in the system. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-INTERNALS_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize internal state because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initilize the internal state for the reason mentioned in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-INTERNAL_HW_SHUTDOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Internal unrecoverable error condition was detected. System is being reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Internal unrecoverable error condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-INVALID_ARGUMENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A system function was given an invalid argument. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A system function was given an invalid argument. This is due to a software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-IPC_CONNECTION_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An IPC connection has invalid state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-IPC_CONNECT_MASTER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IPC connection to the active RP failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> IPC connection to the active RP failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-IPC_CONNECT_REMOTE_IOS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IPC connection to a remote IOSd failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> IPC connection to a remote IOSd failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-IPC_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> IPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-MESSAGE_REGISTER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to register with active RP because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The active RP failed to register. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-MESSAGE_RELAY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to relay a message because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to relay a message. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-MESSAGE_RESPONSE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An invalid message response was received because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An invalid message response was received. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-MQIPC_ADVANCE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to advance MQIPC queue because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The MQIPC initialization failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-MQIPC_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> MQIPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-PEER_TABLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A peer table initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-PLATFORM_FAMILY_TYPE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The platform family type [chars] is invalid. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The platform family type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-PWR_FAULT_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Power fault monitor initialization has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The power fault monitor has failed to initialize. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-RESOLVE_FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to determine [chars] card because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The router failed to determine a FRU state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-RESOURSE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Resource allocation failed in [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system is unable to allocate the requested resource. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, this message is seen as a result of a temporary resource issue. Retry the request for the resource when the system is experiencing lower traffic volumes. If the message persists, reload the router using the reload command. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-ROLE_ADDRESS_UPDATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to update role-based EOBC IP addresses because [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to update a role-based EOBC IP address for the reason stated in the message line. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-SERDES_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP Serial Bridge ASIC has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP Serial Bridge ASIC has failed to initialize. This could be due to a hardware defect, software driver defect or improper internal configuration. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for Serial Bridge ASIC and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-SERDES_INTERRUPT_DISPATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Serial Bridge interrupt dispatch error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to dispatch an error interrupt from the Serial Bridge. This could be due to a software defect or inconsistent internal state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for Serial Bridge errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-SERDES_IOCTL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A Serial Bridge driver I/O control has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Serial Bridge driver I/O control has failed. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for Serial Bridge driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-SERVICES_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize general application services because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize application services. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-SIGNAL_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize signals because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize signals. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-SLOTS_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize chassis slot information because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize the chassis slot information. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-SLOT_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A card absolute slot number cannot be determined for this chassis type </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An absolute slot number is invalid. This could be due to a software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-SYSPAGE_WRITE_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The syspage chassis-type write has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The syapge chassis-type write failed. This could be due to a software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-UIPEER_CREATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create user interface peer. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to create a user interface peer. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-0-WANPLL_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP WAN PLL has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP WAN PLL has failed to initialize. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for WAN PLL or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-ACT2_UDI_DATA_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The act2 udi secure area format mismatch with unsecure area </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This Router may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cbr-platform-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Replace the current product with a Cisco authorised product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-BAD_ID_HW </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed Identification Test in [chars]. The module [chars] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Hardware in the specified location could not be identified as a genuine Cisco product </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cbr-platform-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Replace the hardware with a genuine Cisco product. If this message recurs, contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-CRYPTOGRAPHIC_HW_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> ESP[dec] does not support strong cryptography. Chassis will reload. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> IOS software featuring strong cryptography is invalid for use with any non-strong-cryptography Embedded Service Processor. The router node will reload if this combination is encountered. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Install a non-strong-cryptography image of the RP IOS package or replace the indicated Embedded Service Processor with one that supports strong-cryptography </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-FRU_CPLD_INCOMPATIBLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] has been held in reset as its CPLD firmware version is incompatible with [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This FRU requires a newer CPLD firmware to function properly in this chassis </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Upgrade the CPLD firmware on this FRU using the &lt;b&gt; upgrade hw-programmable CPLD file &lt;pkg_file&gt; slot &lt;fru_slot&gt; &lt;/b&gt; command. Please see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-FRU_FPGA_INCOMPATIBLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] has been held in reset as its FPGA firmware version is incompatible with [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This FRU requires a newer FPGA firmware to function properly in this chassis </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Upgrade the FPGA firmware on this FRU using the &lt;b&gt; upgrade hw-programmable FPGA file &lt;pkg_file&gt; slot &lt;fru_slot&gt; &lt;/b&gt; command. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-FRU_HWPRG_UPG_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to [chars] [chars] hardware programmable on [chars] in [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Upgrade hw-programmable failed to upgrade the CPLD/FPGA firmware on the given FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the card and retry to program the hw-programmable. If the card fails to come up please contact TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-FRU_HWPRG_UPG_PSOC_PREPARE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable PSOCs on [chars] in slot [chars] were set in the golden mode. Please power-cycle or OIR the card to finish the upgrading </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable PSOCs were set in the golden mode for FPD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-FRU_HWPRG_UPG_PSOC_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable PSOCs on [chars] in slot [chars] are upgrading, please don't reload or power-cycle this card. It will take about 10 mins to finish. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable PSOC is upgrading </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-FRU_HWPRG_UPG_PSOC_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable PSOCs on [chars] in slot [chars] were successfully programmed. Please power-cycle or OIR the card to make them work </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable PSOC was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-QUAD_SUP_DISABLE_SUPERVISOR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Exceeded the maximum failure attempts to enable Quad-Sup SVL. Forcing the supervisor in Switch [dec] slot [dec] into reset state. Keeping the supervisor in this state may cause system instability. Please pull out the supervisor and follow the quad sup migration procedure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> ICS is booted with quad sup incompatible image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the supervisor in quad sup compatible image </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-QUAD_SUP_INCOMPATIBLE_SUPERVISOR_PWR_OFF </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Exceeded the maximum failure attempts to enable Quad-Sup SVL. Forcing the supervisor in Switch [dec] slot [dec] into power off state. Keeping the supervisor in this state may cause system instability. Please pull out the supervisor, use 'hw-module switch &lt;switch-num&gt; subslot &lt;slot&gt; oir power-cycle' to power it on back and follow the quad sup migration procedure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> ICS is booted with quad sup incompatible image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the supervisor in quad sup compatible image </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-QUAD_SUP_SW_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The Peer supervisor in Switch [dec] Slot [dec] is not reachable, one of the reason could be, Supervisor booting with quad-sup incompatible image. Continuing in this state could lead to undesirable behaviour. To recover from this state, boot the supervisor in Quad-SUP compatible image by following the migration procedure.(Attempt : [dec] of 5) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> ICS is booted with quad sup incompatible image </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the supervisor in quad sup compatible image or contact TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-QUAD_SUP_UPLINK_SVL_SUPERVISOR_PWR_OFF </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Supervisor in Switch [dec] Slot [dec] is booted when stackwise-virtual configured over supervisor ports which is unsupported. Keeping the supervisor in this state may cause system instability. Forcing the supervisor into power off state. Please pull out the supervisor, use 'hw-module switch &lt;switch-num&gt; subslot &lt;slot&gt; oir power-cycle' to power it on back and follow the quad sup migration procedure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> ICS is booted with quad sup with stackwise-virtual over supervisor ports </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Boot the supervisor with stackwise-virtual configured over linecard ports </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-RP_CPLD_INCOMPATIBLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> All other cards in the system have been held in reset as the Active RP [chars] in slot [chars] has CPLD firmware version that is incompatible with [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Active RP requires a newer CPLD firmware to function properly in this chassis </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Upgrade the CPLD firmware on this FRU using the &lt;b&gt; upgrade hw-programmable CPLD file &lt;pkg_file&gt; slot &lt;fru_slot&gt; &lt;/b&gt; command. Please see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-2-RP_CPLD_INCOMPATIBLE_OTHER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] has been held in reset because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Active RP requires a newer CPLD firmware to function properly in this chassis. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Upgrade the CPLD firmware on this FRU using the &lt;b&gt; upgrade hw-programmable CPLD file &lt;pkg_file&gt; slot &lt;fru_slot&gt; &lt;/b&gt; command. Please see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-BITS_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP BITS E1/T1 interface has failed initialization because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP BITS E1/T1 interface has failed to initialize. This could be due to a hardware defect, a software driver defect or improper configuration. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for BITS driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASFS_OBJECT_DESTROY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to destroy chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem object that should have been destroyed was not destroyed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASFS_PROPERTY_DESTROY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A chassis filesystem property that should have been destroyed was not destroyed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASSIS_FRU_FAULT_IGNORED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CMAN_IGNORE_FRU_FAULTS is set. [chars]: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Debug variable will prevent a FRU from being restarted due to some faults. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASSIS_FRU_FAULT_IGNORED_ISSET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CMAN_IGNORE_FRU_FAULTS is set. Some FRU faults will be ignored and FRU may not restart due to a fault </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Debug variable will prevent a FRU from being restarted due to some faults. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASSIS_MONITOR_FRU_BOOT_RETRIES_EXCEEDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] has been held in reset because it has failed to successfully boot in [dec] tries </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU has failed to successfully boot in the maximum allowable attempts and is held in reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FRU from the chassis if the FRU continously fails to boot. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASSIS_MONITOR_FRU_BOOT_STATUS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Reloading [chars] because the FRU boot status is unknown </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The time at which the FRU started booing is not available. This time is used to check the boot status of the FRU. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FRU from the chassis if the FRU is continously reloaded. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_EXCEEDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Reloading [chars] because it has failed to come online </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A FRU has failed to come online within the maximum boot time. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FRU from the chassis if the FRU is continously reloaded. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_IGNORED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] exceeded online time but will not be reset because fault ignore is configured </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU failed to come online within the maximum online time. This message applies to all FRUs. A reload will not be performed because fault ignore is configured. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Reloading [chars] because it has failed to become ready for packet processing </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU failed to become ready within the maximum ready time. This message applies to FP FRUs. A switchover will be performed if another FP is available. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FRU from the chassis if the FRU is continously reloaded. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-CHASSIS_MONITOR_READY_TIME_IGNORED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] exceeded ready time but will not be reset because fault ignore is configured </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU failed to become ready within the maximum ready time. This message applies to FP FRUs. A switchover and/or reload will not be performed because fault ignore is configured. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-DDR_SINGLE_BIT_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Single-bit DRAM ECC error: mme: [dec], sbe: [dec], address: 0x%08X, pid: [dec], name: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP DRAM has single-bit ECC errors. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the system self-corrects these single-bit ECC errors and no user action is necessary. If the problem persists, gather the console output with the error message along with the show tech-support command output and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-DUAL_IOS_STANDBY_BAY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Standby bay cannot be launched due to failure in bringing down existing processes (Attempts: [dec]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> During standby bay shutdown, some related processes still remain running for an unexpectedly prolonged period of time. Chassis-manager has timed-out waiting for all related processes to shutdown. As a result, it is unable to notify Process-manager to restart the bay </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for standby bay's Forwarding-manager (fman), Interface-manager (iman), Pluggable-Service-Daemon (psd) and IOS. Ascertain which of these processes is taking too long to shutdown and note the reason. Take corrective action based on the error noted in the log </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-EXT_ALARM_INTERRUPT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Alarm [chars]:external alarm contact [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> There is an external alarm on the line. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If alarm is asserted, then clear at the source. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FAN_FAILURE_SYS_SHUTDOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: More than one Fan Failure detected and shutdown SYS state. System shutdown now TRUE:%x. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> More than one fan failures are identified this causing overheating the system and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FAN_INCOMPATIBLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The combination of Power Supply and Fan Tray is incompatible </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The combination of Fan tray and one of the power supply slots is not supported. This could cause unpredictable system behavior. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This error indicates that the combination of one of the power supplies in P0 or P1 is not supported with the Fan Tray. In order to fix this issue, please review the installation guide, replace the fan tray or the power supply based on the requirement. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FAN_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP has failed to initialize Fan [dec] module controller because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP failed to initialize the Fan. This could be due to a software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FAN_REMOVE_IM_SHUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The Interface Modules (IM's) may shutdown in [dec] minutes [dec] seconds. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Fan tray has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reinsert a fan tray into the fan tray slot as soon as possible. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FAN_REMOVE_RSP2_SHUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The system will shut down when CYLON temp reaches 105C </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Fan tray has been removed and the router will shutdown when cylon temperature reaches critical temperature i.e. 105C to protect itself from overheating in the amount of time stated in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reinsert a fan tray into the fan tray slot as soon as possible. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FAN_REMOVE_RSP3_SHUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> System received fan tray removal notification, Reinsert or service the faulty fan tray to avoid system shutdown due to high temperature. System will shutdown when the ARAD temp reaches Critical temperature i.e 105C. Based on current ARAD temperature [dec]C approximate time of shutdown is [dec] minutes [dec] seconds. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Fan tray has been removed and the router will shutdown when the ARAD temp reaches Critical temperature i.e 105C to protect itself from overheating. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr903-system </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reinsert a fan tray into the fan tray slot as soon as possible. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FAN_REMOVE_SHUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The system will shut down in [dec] minutes [dec] seconds </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Fan tray has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reinsert a fan tray into the fan tray slot as soon as possible. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FAN_REMOVE_SYS_SHUTDOWN_PENDING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> System shutdown will occur in [dec] minutes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FP_DOWNREV </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] has been held in reset because it is down-rev to the previous FP (0x%x -&gt; 0x%x) in the chassis. Reboot the router to bring it up. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FP inserted is a lower version than the previous Active FP in the router. Downrev of FP is not supported. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reboot the router. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FP_LESSTHAN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] has been held in reset because it is down-rev to the active and cannot act as a standby. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The part number read from the FP IDPROM is not compatible with part number of the active FP; therefore, it may not act as a standby. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FP from the chassis. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FP_UNSUPP_UPREV </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] has been held in reset because of an upsupported upgrade of FP (0x%x -&gt; 0x%x) in the chassis. Reboot the router to bring it up. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FP inserted is a higher version than the previous Active FP in the router but this upgrade of FP is not supported. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reboot the router. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_HWPRG_BAD_DEVICE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Invalid HW programming device for [chars] in slot [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The device is not supported in hardware programming. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is an informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_HWPRG_LOAD_KMODULE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cannot load a kernel module on [chars] in slot [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Cannot load a Kernel module when upgrade CPLD or FPGA. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the card and retry to program the hw-programmable. If you get the same error, please contact TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_HWPRG_NO_FILE_ENTRY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cannot find file or directory on [chars] in slot [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Cannot find a file or a directory when upgrade CPLD or FPGA. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is an informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_HWPRG_RESTART_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error [chars] when Chassis Manager restarts [chars] in slot [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Restart procedure has an error after upgrade. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Try hw-module command to reload the FRU. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_HWPRG_UPG_PS_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Power-Supply Module MCU [chars] in slot [chars] program failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable power-supply upgrade failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please check Power-Supply model and PKG file. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_HWPRG_UPG_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable [chars] on [chars] in slot [chars] was successfully programmed. The card will now be power-cycled or reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable CPLD/FPGA was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_HWPRG_UPG_UNSUPP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Upgrade of hardware programmable [chars] on [chars] in slot [chars] is not supported. Card will now be powered down. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> upgrade of hw-programmable CPLD/FPGA not supported. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_INCOMPATIBLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] has been held in reset: [chars] is incompatible with [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The part number read from the FRU IDPROM is invalid for this chassis type. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FRU from the chassis. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_INVPARTNUM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] has been held in reset because the part number %08X is invalid. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU IDPROM contains an invalid part number. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> The FRU IDPROM should be repaired or the board replaced. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-FRU_NOPARTNUM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cannot get part number from IDPROM for [chars]: [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU IDPROM cannot be read or does not contain a valid part number field. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> The FRU IDPROM should be repaired. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-HWLIB_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The hardware library has failed to initialize because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This could be due to a hardware defect, software driver defect or improper internal configuration. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for CPLD hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-HWMOD_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> hw-module [chars] command for slot [chars] failed ([chars]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The last hw-module command that was entered failed to complete </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry the command. If the retry of the command fails, reload the router. If reloading the router fails to resolve the problem, note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-HWPRG_UPG_UNSUPP_SLOT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> upgrade of hardware programmables on [chars] is not supported while in slot [chars]. Card will now be powered down. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> upgrade of hw-programmable CPLD/FPGA not supported in the given slot. Move the card to a different slot and perform the upgrade </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Move the card to a different slot and perform the upgrade </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-I2C_READ </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An I2C read has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An I2C read has failed. This could be due to a hardware or software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-I2C_WRITE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An I2C write has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An I2C write has failed. This could be due to a hardware or software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-IDPROM_ACCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to access or process IDPROM '[chars]': [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed access or process an IDPROM. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-IDPROM_SENSOR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> One or more sensor fields from the idprom failed to parse properly because [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> One or more sensor fields from the IDPROM failed to parse properly. This problem is often the result of a checksum failure in the IDPROM. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-INCOMPATIBLE_FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] is not compatible with [chars] and so it is disabled </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Product ID read from the FRU IDPROM is invalid for this hardware configuration. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FRU from the chassis. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-INCOMPATIBLE_FRU_SDWAN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] is not supported in controller mode </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Product ID read from FRU IDPROM is not supported in sdwan controller mode. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FRU from the chassis </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-INCOMPATIBLE_STANDBY_SUPERVISOR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Standby supervisor is not compatible with the Active supervisor. Standby Supervisor will be disabled </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Supervisor found in Standby slot may not be fully compatible with the active supervisor and may cause issues. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Use supervisors with the same specifications to enable High Availablitly features. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-INTERNAL_HW_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An nternal error condition was detected and resolved. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An internal error condition was detected, and affected part of hardware was reset. If this error condition reoccurs, the hardware may need to be replaced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-INVENTORY_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] inventory file could not be read. FRU may need a reload to initialize properly, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU inventory file could not be read. The file can possibly be corrupt. The FRU will possibly not initialize properly. The FRU should reset automatically. If it does not, it should be reloaded manually. If the error persists, the FRU will need to be replaced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Wait a few minutes. If FRU does not reset automatically, it should be manually reloaded. If error persists, the FRU needs to be replaced. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-LICENSE_TIMEOUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Throughput license request timed out. Throughput level set to default </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Throughput license was never received from lman </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine logs for error messages </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-OOD_OPR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An OOD operation has failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An OOD opearion has failed. This could be due to a hardware or software defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for OOD errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-OPR_PENDING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The slot [dec] is has pending operation, please try later. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The previous operation on this board has not completed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Try with the same command later </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PEER_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A peer table entry has invalid state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A peer table entry has an invalid state. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PEM_REMOVE_SHUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The system will shut down in [dec] minutes </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A power supply has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reinsert a power supply into the power supply slot as soon as possible. The second power supply is required because the fans in the power supply are essential in monitoring router temperature. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PFU_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to handle power supply failure for [chars] in slot [dec], [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A power supply has failed and the system is unable to properly handle the failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PFU_FAN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to handle fan failure for [chars] in slot [dec], [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> One or more fans have failed and the system is unable to properly handle the fan failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PFU_INCOMPATIBLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> PFU Incompatible: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Error message for any PFU compatibility errors. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove incompatible PSUs. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PFU_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP has failed to initialize a Power Supply/Fan module controller because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP failed to initialize a Power Supply or Fan module controller. This could be due to a hardware defect or C2W access failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for C2W and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PFU_MISSING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The platform does not detect a power supply in slot [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> There is no power supply in one of the power supply slots. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Insert a power supply into the empty slot. The router requires two power supplies because the fans in the power supply are needed to cool the router. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PFU_OIR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to handle a [chars] oir event for PEM in slot [dec], [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A power supply was inserted or removed into or from a router and the software did not properly handle the event. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-POWERBUDGET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> not enough power budget left for : [chars]:[dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system do not have enough power budget for the new card. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cbr-platform-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> the message will be displayed when not enough power budget left for the new card inserted. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PSU_INCOMPATIBLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The combination of Power Supply in P0: [chars] and P1: [chars] is not supported in power [chars] mode </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An incompatible power supplies combination has been identified in P0 and P1 power supply slots. This could cause unpredictable behavior in power management in the router. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This error indicates that the combination of the two power supplies in P0 and P1 is an unsupported combination. In order to fix this issue, please review the installation guide, plug out one of the power supplies based on the requirement. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-PWR_FAULT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Shutting down [chars] because power fault on primary is [chars] and secondary is [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU has been shutdown as a result of a power issue. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check to ensure the router is receiving power. Otherwise, note the time of the error message and examine the logs for power-related errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-RP_MASTERSHIP_SET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to set RP mastership [chars] because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The router failed to establish RP mastership. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the router. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-RP_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] has been held in reset because the part number differs from that of the active RP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The part number read from the FRU IDPROM is not compatible with part number of the active RP; therefore, it may not act as a standby. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FRU from the chassis. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-RP_RESET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> RP is resetting : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This RP is resetting due to the reason specified. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-RP_SB_RELOAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Reload of Standby RP failed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A request to reload the standby RP failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Manually reload the standby RP. If that fails, configure SSO or RPR and then attempt the reload. If the problem persists, note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, show redundancy state, and the output of show tech-support and provide the gathered information to a Cisco technical support representative </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-RP_SWITCH_SB_NOT_READY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> RP switchover: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An RP switchover occurred when the standby RP was not ready. The standby RP reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. Allow the standby RP to reset. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SENSOR_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize sensor monitoring because [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Sensor monitoring failed to initialize. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SENSOR_TYPE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The sensor type is [dec] is invalid. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A sensor type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SERDES_ESI_INIT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Serial Bridge ESI link [chars] between [chars] and [chars] failed to config </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Serial Bridge ESI link did not configure. This could be due to a software error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for Serial Bridge and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SERDES_ESI_LOCK_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Serial Bridge ESI link [chars] between [chars] and [chars] failed to lock </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Serial Bridge ESI link did not lock. This could be due to a hardware defect or a software configuration error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for Serial Bridge and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SERDES_NSTEP_SYNC_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Link down in Slot=[dec], Link-Type=[dec], Link-Status=0x%x, Link=[dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> One or more Backplane Link didn't come up. This could be due to a hardware defect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for repeated SYNC errors after repeated retries. If the logs, provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SIP_MDR_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The SIP[dec] failed Minimal Disruptive Restart because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The SIP failed Minimal Disruptive Restart. Minimal Disruptive Restart process is aborted and an attempt will be made to recover the SIP by resetting the SIP hardware. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the system logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SOFT_ERROR_RELOAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Uncorrected Soft error on [chars], reloading RP to recover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Uncorrected Soft error on critical module, reloading the RP to recover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr903-system </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this reoccures frequently, contact asr903-system </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SOFT_ERROR_RELOAD_RECOMMENDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Uncorrected Soft error on [chars], reload is recommended to recover. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Uncorrected Soft error on critical module, reload is recommended to recover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr903-system </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this reoccures frequently, contact asr903-system </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SOFT_ERROR_UPDATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Critical soft error on [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Update for each soft error on different components </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr903-system </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this reoccures frequently, contact asr903-system </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SOFT_ERROR_WAIT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Uncorrected Soft error on [chars], waiting for standby to switchover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Uncorrected Soft error on critical module, waiting for standby to reach SSO to switchover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr903-system </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this reoccures frequently, contact asr903-system </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-SYS_REBOOT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> System going down, reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> System reboot is called from software. Please check the reason and earlier syslog, traces </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the reason string and take appropriate action </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-THROUGHPUT_LICENSE_APPLY_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Throughput license look-up failed due to '[chars]' </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This message is to notify the user that a license look-up did not succeed because license manager process could not be contacted. This is a rare case but is due to either a crashed license daemon(licensed) or it encountered an internal error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. However, it is possible that a re-boot of the box may correct this behavior. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-UDI_AUTH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Quack Unique Device Identifier authentication failed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This chassis seems to be compromised or tampered with. UDI burned on to the Quack chip and the one read from chassis EEPROM do not match. It can also be a case of either EEPROM or Quack device failure. More details about which specific field failed to match are logged in license daemon log file (licensed_R0.log). </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> User immediately needs to contact Cisco support. This device appears to be tampered with or is a counterfeit device or had a system failure. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-UNSUPPORTED_FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] is not supported with [chars] and so it is disabled </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Product ID read from the FRU IDPROM is not supported in this router. This is due to either Hardware or Software compatibility limitation indicated in the console log </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the FRU from the chassis. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-UNSUPPORTED_PEM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] is not supported with [chars] and it needs to be replaced immediately </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Product ID read from the PEM IDPROM is not supported in this hardware configuration. It will be allowed to continue but immediate replacement is required </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the PEM from the chassis and replace it with a supported PEM. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-3-WANPLL_SETUP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to setup the [chars] of the RP WAN PLL because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to setup the RP WAN PLL appropriately. This could be due to a hardware defect of the device. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for WAN PLL related hardware errors. Check if the issue is transient or repeatable. If the problem is not recoverable collect the output of the error message and the chassis- manager and IOS logs. Provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-ACTIVE_SLOTBAY_BIAS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The configured active slot/bay bias [dec] is invalid. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The configured active slot/bay bias is not 0 or 1. The default value of 0 is used. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-CPP_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Active cable linecard in slot [dec] has been physically removed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Plug out one LC with heavy traffic, it may cause cpp queue pending drain and modem offline. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cbr-platform-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-FAN_TRAY_OVER_CURRENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A Fan Tray over-current has been detected. System will be reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Internal error (Fan Tray over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-INTRUSION_ALERT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The system cover has been [chars] !! </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> These tamper alert message indicate the event of intrusion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-MOTHERBOARD_OVER_CURRENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Motherboard over-current has been detected. System will be reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Internal error (Motherboard over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-NGWICS_OVER_CURRENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A NIM over-current condition has been detected. System will be reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Internal error (NIM over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-SERDES_ESI_CARD_RESEAT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Serial Bridge ESI link [chars] between [chars] and [chars] isn't locked; Card should be reseated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Serial Bridge ESI link did not lock during first 10 reties due to improper seating. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for Serial Bridge and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-SYSTEM_OVER_CURRENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Overall system over-current has been detected. System will be reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Internal error (system over-current) condition was detected, and so the system was reset. If this error condition reoccurs, the hardware may need to be replaced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-TAMPER_DETECTION_EVENT_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> System cover was opened [dec] times and closed [dec] times during power [chars] since last known event index [dec] at 20%02x/%02x/%02x %02x:%02x:%02x </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> These tamper warning indicate the event of intrusion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-4-TAMPER_DETECTION_NO_LAST_KNOWN_EVENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> System cover was opened [dec] times and closed [dec] times during power [chars]. There is no last known/marked event. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> These tamper warning indicate the event of intrusion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-5-CHASSIS_MONITOR_BOOT_TIME_PRINT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Card [chars] took [dec] secs to boot </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This is an informational message about boot time of all cards. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Action is not necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-5-FRU_CPLD_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CPLD ver [chars] in slot [chars] does not match Active CPLD ver [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This FRU requires a matching CPLD firmware to function properly in this chassis </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Upgrade the CPLD firmware to have matching versions. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-5-HA_NOTICE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> HA message: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> HA Error Occured. This could be due to a software defect, please follow action </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for HA and hardware errors. Try re-inserting Standby SUP properly and see if problem gets corrected, If the problem is not correctable or the logs are not helpful, collect the the output of the error message,the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-5-NEBS_ACCESS_PID_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to acess NGIO PID list for [chars] on slot/bay [dec]/[dec] in NEBS mode. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unable to acess NGIO PID list for slot %d bay %d in NEBS mode </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-5-PEM_OUTPUT_DETECT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Output of PEM [dec] is [dec] V </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Value of Output of PEM. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cbr-platform-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If PEM Output is 0, check Power Cable. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-5-PRERELEASE_HARDWARE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] is pre-release hardware </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The board does have an official production part number. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Immediately contact Cisco for a replacement board. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-5-SUDI_KEY_READ_INIT_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SUDI(SHA2) key read failed during Initializtion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> SHA key read failed during Initializtion. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check SUDI Trustpoint creation. Please collect output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-5-UNSUPPORTED_MODULE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unsupported Module inserted. The module [chars] on the slot [dec] may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco memory, WIC cards, AIM cards, Network Modules, SPA cards, GBICs or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Hardware in the specified location could not be identified as a genuine Cisco product </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-5-UNSUPPORTED_MODULE_IN_NEBS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The module [chars] on slot/subslot [dec]/[dec] is not supported in NEBS power mode. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Hardware in the specified location should be removed in NEBS mode </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-DUAL_IOS_REBOOT_REQUIRED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Configuration must be saved and the chassis must be rebooted for IOS redundancy changes to take effect </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Chassis manager received notification that IOS software redundancy has been configured. For these changes to take effect, the system must be restarted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the chassis. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-DUAL_IOS_STARTING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Software redundant IOS configured; starting standby in [dec] seconds. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Chassis manager received notification that IOS software redundancy has been configured. The standby IOS will be started in the time specified. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-DUAL_IOS_STOPPING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Bringing down standby IOS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Chassis manager received notification to stop the standby IOS instance. This may be for a redundancy mode change. Depending on the reason, the standby may be subsequently restarted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FORCE_RESET_OTHER_RP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The other SUP RP [dec] is still holding the midplane lock to block the suppervisor failover, force reset it to release the midplane lock. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Other Supvervisor is force reset due to hold the midplane lock for a long time during supervisor failover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FP_HA_SB_NOTREADY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> FP switchover: F[dec] [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The standby ESP is not ready for a switchover. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FP_HA_STATUS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> F[dec] redundancy state is [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The ESP has transitioned into a new High Availability state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. This is an informational message. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FP_SB_RELOAD_REQ </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Reloading Standby FP: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A reload of Standby FP has been requested. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FRU_FPGA_UPG_REQUIRED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] in slot [chars] has INCOMPATIBLE FPGA firmware version with [chars]. Upgrade the FPGA firmware </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This FRU requires a newer FPGA firmware to function properly in this chassis </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Upgrade the FPGA firmware on this FRU using the &lt;b&gt; upgrade hw-programmable FPGA file &lt;pkg_file&gt; slot &lt;fru_slot&gt; &lt;/b&gt; command. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FRU_HWPRG_CPLD_POSTUPG_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware CPLD postupgrade on CLC[dec] was successfully programmed.The LC is reloading to make it take effect. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable CPLD postupgrade was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FRU_HWPRG_UPG_ADM1266_FM_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable ADM1266s on [chars] in slot [chars] are upgrading, please don't reload or power-cycle this card. It will take about 10 mins to finish. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable ADM1266 Firmware is upgrading </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FRU_HWPRG_UPG_ADM1266_FM_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable ADM1266s on [chars] in slot [chars] were successfully programmed. The card is reloading to make them work </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable ADM1266 fimware was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FRU_HWPRG_UPG_PSOC_DONE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable PSOCs on [chars] in slot [chars] were upgraded successfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable PSOC was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FRU_HWPRG_UPG_PS_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Power-Supply Module MCUs in slot [chars] were successfully programmed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable power-supply was upgraded succesfully </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-FRU_HWPRG_UPG_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Hardware programmable [chars] on [chars] in slot [chars] is upgrading. please don't reload or power-cycle this card. It will take about 5 mins to finish. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The hw-programmable was upgrading </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-HT_CLOSURE_MODE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The HTPI driver failed to set it's closure mode properly </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This is not a critical error, but it will result in possible traffic interruption during certain software failure cases or ISSU operations. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Note the error message and contact a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-HT_STATUS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> R[dec] hypertransport configured for F[dec] active </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP HyperTransport driver was properly configured for a newly active FP. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. This is as informational message indicating normal system operation. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-IGNORE_PFU_OIR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Simulating FAN OIR due to FAN Speed profile change </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> FAN tray OIR is simulated throught software to select new FAN SPEED profile. this message is to let know the user that this is a simulated FAN oir and not physical FAN oir. User needs to ignore next occurrence messages/alarms associated with FAN tray removal/insertion actions. such as FAN tray missing, PEM/FAN removed/inserted and system shutdown will happen messages </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr903-system </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> ignore FAN tray or PEM/FM removal/insertion messages and system shutdown message </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-MGMT_SFP_INSERT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> transceiver module inserted in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The online insertion and removal (OIR) facility detected a newly inserted transceiver module for the interface specified in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-MGMT_SFP_REMOVED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Transceiver module removed from [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The online insertion and removal (OIR) facility detected the removal of a transceiver module from the interface specified in the error message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-MODULE_INSERTED_CFG_MISMATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The module inserted in Switch:[dec] Slot:[dec] doesn't support the configured Stackwise Virtual link/Dual Active Detection Link Speed. Line card is Power denied. Please replace the Line card with the configured SVL/DAD link speed or remove the config and reload the system </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Line Card and SVL/DAD CONFIG in the slot mismatch. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Change the config and reload the system or remove the Line card. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-REDT_FP_UNSUPPORTED_IN_INTER_CHASSIS_MODE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] redundant FP in slot [chars] is not supported in inter-chassis redundancy mode </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Because the system is configured in box-to-box or inter-chassis redundancy mode, the intra chassis redundancy mode is not supported and redundant FP, if any, will be disabled. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-REDT_RP_UNSUPPORTED_IN_INTER_CHASSIS_MODE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] redundant RP in slot [chars] is not supported in inter-chassis redundancy mode. Please remove it for inter-chassis redundancy to work properly on system reload. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Because the system is configured in box-to-box or inter-chassis redundancy mode, the intra chassis redundancy mode is not supported and redundant RP, if any, will be disabled. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-RFROLE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> RP switchover, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> On RP switchover chasfs rfrole property has been changed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-RP_SB_RELOAD_REQ </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Reloading Standby RP: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A reload of Standby RP has been requested. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-RP_SWITCH_SB_SYNC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> RP switchover: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The RP switch synchronization timer expired. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-SINGLE_IOS_REBOOT_RECOMMENDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Configuration must be saved and the chassis should be rebooted for optimal single-IOS execution </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Chassis manager received notification that IOS software redundancy has been unconfigured. For optimal runtime resource allocation, the system must be restarted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the chassis. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-STBY_HARDDISK_UNAVAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> stby-harddisk is offline </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The stby-harddisk is not available. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. This is an informational message. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-TEST_SPA_OIR_ONLINE_INSERT_DENIED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SPA [dec]/[dec] oir insert is denied </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> test command executed disallowing the spa to be inserted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Execute the test command allowing the insertion of the spa for normal operation </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-TEST_SPA_OIR_ONLINE_OPS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SPA [dec]/[dec] oir online status is set to [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> test command executed to either allow/deny the spa coming online. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If the card does not come online, execute the test command to allow the spa to come online. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP-6-THROUGHPUT_LICENSE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Throughput license [chars], throughput set to [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Status indicating whether throughput license is found and the corresponding througput the CPP hardware is configured to provide. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is necessary. This is an informational message indicating throughput configured. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-3-PWR_FRU_HW_AUTO_SHUTDOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: The card on slot [dec] hit abnormal voltage or current. it has been auto-shutdown by hardware for protection </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU hit abnormal voltage or current and has been auto-shutdown in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-3-TEMP_FRU_HW_AUTO_SHUTDOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: The card on slot [dec] is overheating. it has been auto-shutdown by hardware for protection </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU is overheating and has been auto-shutdown in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-3-TEMP_FRU_SHUTDOWN_NOW </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown now. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-3-TEMP_FRU_SHUTDOWN_PENDING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown will occur in [dec] minutes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-3-TEMP_PSU_SHUTDOWN_NOW </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: [chars] temperature sensor on [chars] is in a shutdown PSU state. PSU shutdown now. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The PSU is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-3-TEMP_SYS_SHUTDOWN_NOW </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: [chars] temperature sensor on [chars] is in a shutdown SYS state. System shutdown now. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-3-TEMP_SYS_SHUTDOWN_PENDING </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: [chars] temperature sensor on [chars] is in a shutdown SYS state. System shutdown will occur in [dec] minutes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-3-TEMP_WARN_CRITICAL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: [chars] temperature sensor on [chars] is in a critical state reading [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-3-TRANSCEIVER_TEMP_SYS_SHUTDOWN_NOW </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: transceiver temperature sensor is in a shutdown SYS state. System shutdown now %x. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Transceiver is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_ENVMON-6-TEMP_SYS_SHUTDOWN_DISABLED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: System is in a thermal shutdown disabled state. System won't shut down now. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Thermal shutdown disable is configured to bypass system shutdown. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-1-FAN_POLICY_ALERT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> SYSTEM FAN POLICY Alert : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> System FAN policy check detect issues </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Monitor or Replace faulty fan modules may be needed. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-1-PFU_FAN_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> System detected fan tray removal or fan failure, reinsert or service the faulty fan tray to avoid system shutdown due to high temperature. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Fan tray has been removed or one of the fan failed and the router will shutdown when the temp reaches Critical temperature to protect itself from overheating. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reinsert a fan tray into the fan tray slot as soon as possible. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-1-PFU_NO_FAN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> System detected no fan or fan tray available, either not present or in failure state. Reinsert or service the faulty fan or fan tray to avoid system shutdown. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> No working fan or fan tray detected in the system, could be removed or in failure state, switch will be shutdown when the temp reaches critical temperature to protect itself from overheating. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reinsert working fan or fan tray as soon as possible. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-2-PSU_VOLATGE_MIX </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Mix of 110V and 220V is not supported configuration, PSU in slot [chars] is in 110V and PSU in slot [chars] is in 220V. This can cause system reload, Connect the same voltage input to avoid system reload immediately. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Some PSUs are connected to 110V and some are connected to 220V. This is not supported from hardware as it may cause system failure and system may go for reload. Input voltage can be checked using CLI show platform hardware chassis power-supply detail </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Connect all the power supplies to same voltage input source as soon as possible. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-DCPOWERREDUNDANCY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> dc input [chars] failed for pem: [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The DC input failed for pem module. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> the message will be displayed when DC input failed. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-FANASSY_REMOVED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Fan Assembly is removed. Please insert to avoid system from heating. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Fan Assembly has been removed from the system. It needs to be inserted back to prevent system from heating. If the system over heats, parts of the system will not function normally and system may shut itself down. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Insert the fan assembly in the system to prevent system from over heating. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PEM_STATUS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: The power supply module on slot [dec] hits [chars], </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The power supply module are not functioning properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PEM_VOLTAGENOTSUPPORTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Input voltage of power supply module on PS[dec] is not supported. Please use the supported range of either [dec]-[dec] volts for [dec]W or [dec]-[dec] volts for [dec]W </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The input voltage of the power supply module is out of range </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PFU_FANS_DEAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The fans in the [chars] in slot [dec] have all failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system is in danger of overheating because none of the fans in one of the PEMs are working properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PFU_FANS_DEAD_SHUTDOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Shutting down system now because the fans in slot [dec] have all failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> When the fans fail then system does not have sufficient cooling capacity. To prevent damage, the system will automatically shut down. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PFU_FAN_DEAD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Fan [dec] in the [chars] in slot [dec] has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A fan is not functioning properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PFU_FAN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Fan [dec] in slot [dec] has the error: [chars], Please replace it with a new fan. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A fan is not functioning properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PFU_IDPROM_CORRUPT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The PEM/FM idprom could be read, but is corrupt in slot P[dec] The system will run without environmental monitoring for this component </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PFU_IDPROM_READ_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Could not read the PEM/FM idprom in slot P[dec]. The system will run without environmental monitoring for this component </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PFU_SHUTDOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Shutting down system now because the PEM in slot [dec] was removed or not seated correctly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PFU_SLOT_VACANT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The platform does not detect a power supply in slot [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> There is no power supply in one of the power supply slots. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Insert a power supply into the empty slot. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PWR_MGMT_ALARM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: System does not have sufficient input power for minimum reliable operation requiring [dec] watts. The system needs [dec] watts of additional power. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> System power does not meet minimum requirements. Insert additional power supplies or provide current power supplies with a greater input voltage source if applicable. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PWR_MGMT_LC_SHUTDOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Linecard in slot [dec] with priority [dec] and a power requirement of [dec] watts has shutdown. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A LC was shutdown due to a power loss. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PWR_MGMT_SINGLE_SUP_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> ERROR: Remote supervisor has been detected in slot [dec]. System is configured to SINGLE-SUP power mode. Remove remote supervisor IMMEDIATELY. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> User inserted a second supervisor in a single-sup power mode. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PWR_PROTECTION_ACTION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Shutdown the card [chars] due to insufficient power budget. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The total power is not enough, shutdown FRUs for power protection. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PWR_PROTECTION_MODE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Detected low input voltage ([dec]V) on the power supply in slot P[dec], the power budget may not be enough, some cards may be shutdown due to the power budget reduction. Please check the power input. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Input voltage of power supply is too low. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-PWR_REDUN_ALARM_STATE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: An active power supply has failed and the system has entered alarm state. The system is operating without power redundancy and has [dec] watts of power remaining </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An active power supplied failed while in redundant power mode. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-SHUTDOWN_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The system attempted to shut itself down, but failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system reached a condition where it should be shut down, but the shutdown call failed. The system should be manually rebooted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-TEMP_FRU_SHUTDOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown will occur in [dec] minutes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The FRU is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-3-TEMP_SYSTEM_SHUTDOWN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] temperature sensor is in a shutdown system state. System shutdown will occur in [dec] minutes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system is overheating and will be shut down in order to protect the components. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-4-PFU_FANTRAY_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Fantray in slot [chars] has the error: [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A fantray is not functioning properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-4-PFU_FAN_ID_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: [chars] of [chars] has an error: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A fan is not functioning properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-4-PFU_FAN_INSUFFICIENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Insufficient number of fan modules installed. There are only [dec] fan modules, expecting [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Insufficient number of fan modules installed, should insert new fans as soon as possible to avoid system from over heating. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-4-PFU_FAN_TRAY_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Fan tray in slot [dec] has the error: [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A fan tray is not functioning properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-4-PFU_FAN_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Fan [dec] in slot [dec] has the error: [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A fan is not functioning properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-4-PWR_MGMT_CAPACITY_MIXED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> System contains power supplies of mixed power capacity. Redundancy operating mode Full protected is not supported with this configuration. System will run in Normal protected state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> HW does not support Full protected mode with mixed capacity power supplies. This is due to current sharing; specifically dealing with the case in which all active power supplies fail simultaneously. Full protected state is demoted to Normal protected state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-4-PWR_MGMT_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING: Insufficient number of power supplies ([dec]) are installed for power redundancy mode [chars]. The system needs [dec] watts additional power. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Insufficient number of power supplies are installed. Should insert new power supplies as soon as possible </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-5-DCPOWERINPUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> dc input [chars] recovered for pem: [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The DC input recovered for pem module. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> the message will be displayed when DC input recovered. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-FANASSY_INSERTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Fan Assembly is inserted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Fan Assembly that was previously removed has been inserted in the system. Preventing the system from over heating is important. So fan assembly should not be removed for extended period of time during normal operation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No further action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PEM_INSERTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Power Supply in slot [dec] not operational. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A PEM seems to be inserted without the power cable connected. This message is a notice that the power supply is not operational, will not provide power to the system, and may not be completely detected by the software until the power cable is connected and the PEM is supplied with the power. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Insert the power supply cable in the PEM and provide power. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PFU_BEACON_LED_ON_OFF </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] [dec] beacon LED is TURNED [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Power Supply or Fan-tray, Beacon LED turned ON/OFF. This is a notification message only.No action is required. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is a notification message only. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PFU_FAN_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The required number of fan trays or fan modules are detected. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> After previous no fan or insufficient fan modules alarm, the required minimum number of fan trays or fan modules have been detected. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No further action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PFU_FAN_RECOVERED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Fan in slot [dec] has been recovered from error conditions, Now it's working normally. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Fans are just recovered from an error condition, </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PFU_FAN_RECOVERED_I2C </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Successfully restored I2C communication to PSoC [dec] on fan module in slot [dec]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Fans are just recovered from an I2C communcation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PFU_INSERTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] inserted. System shutdown aborted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced.This message serves as notice that the module has been replaced within the required time </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PSU_VOLATGE_MIX_RECOVERED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> All PSUs are now connected to the same input voltage. System has recovered from mix of input voltages. PSU in slot [chars] is connected to [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Some PSUs were connected to 110V and some were connected to 220V. This was not supported from hardware as it may have caused system failure. The system is now in a stable state with all PSUs connected to the same input voltage </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> All the power supplies should be connected to same input voltage source </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PWR_MGMT_LC_RECOVERED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Linecard in slot [dec] with priority [dec] has been recovered from shutdown </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A LC was recovered from a shutdown </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PWR_MGMT_NON_REDUNDANT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Changing the power redundancy mode to non-redundant </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Changing the power redundancy mode to non-redundant </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PWR_MGMT_OK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Sufficient number of power supplies ([dec]) are installed for power redundancy mode [chars] (excess power [dec] watts). </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Sufficient number of power supplies are installed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PWR_MGMT_REDUNDANT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Changing the power redundancy mode to redundant. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Changing the power redundancy mode to redundant </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PWR_MGMT_SINGLE_SUP_NOTICE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> NOTICE([dec] of [dec]): System is now running in SINGLE-SUP power budget mode. Insertion of the remote supervisor is not supported in this power mode. System may shutdown if second supervisor is inserted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> User needs to be notified that single-sup mode is enabled </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PWR_PROTECTION_RECOVERED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The power supply in slot P[dec] has been recovered from the power protection mode. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Power supply input are just recovered from an error condition, </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PWR_REDUN_RECOVERED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> System has recovered from the alarm state and has [dec] watts of power remaining </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> User has recovered the system from the alarm state triggered by a power failure </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CMRP_PFU-6-PWR_UP_FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Power up the card [chars] due to power budget change. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The total power become enough, power FRUs. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CONFIG_VALIDATOR_MESSAGE-5-EWLC_GEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> EWLC wireless config db Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CSVERIFY-3-CSVERIFY_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Signature verification: [[chars]] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> During digital signature verification, an error has occured </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the diagnostic csverify trace file for more information on the underlying failure. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CSVERIFY-6-CSVERIFY_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Signature verification success for [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Signature verification was successful for the file mentioned. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is an informational message. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CXPD-3-MAX_LOCAL_EXIT_EXCEEDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Maximum local exit: [dec] exceeded, failed to initialize application: [chars] (interface: [chars]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This syslog is generated when the number of DIA exits exceed maximum supported value. SaaS app initialization will fail because of this reason </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-cxp </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> CXP has reached the maximum number of probes it can handle. Need to disable either some applications or the links in which CoR SaaS is enabled </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CXPD-5-APP_CHANGE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Application: [chars] exit changed from ([chars] via [chars]) local-color [chars] remote-color [chars] to ([chars] via [chars]) local-color [chars] remote-color [chars] from [dec]/[dec] to [dec]/[dec] (latency/loss) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This log is generated whenever exit for a SaaS application changes from one TLOC to another TLOC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-cxp </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> CXPD-5-SCORE_CHANGE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Application: [chars] ([chars] exit via [chars]), local-color: [chars], remote-color: [chars], score changed from [dec]/[dec] to [dec]/[dec] (latency/loss) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This syslog is generated whenever the score (loss/latency combination) changes for SaaS application over given TLOC </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-cxp </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBAL-3-BIPC_MSG_ALLOC_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> BIPC msg size too big to allocate </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> BIPC msg size beyond limit. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Report this occurance to Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBAL-3-MQIPC_ADVANCEERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> MQIPC advance error [[chars]] reader [[chars]] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> MQIPC fails to advance to the next msg in DBAL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Report this occurance to Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBAL-3-MQIPC_EVENTLOSS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> MQIPC event lost reader [[chars]] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> MQIPC event notifying of non-empty queue not delivered to DBAL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Report this occurance to Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBAL-3-MQIPC_PEEKERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> MQIPC peek error [[chars]] reader [[chars]] err_msg [[chars]] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> MQIPC fails to peek and fetch a msg in DBAL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Report this occurance to Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBAL-3-MQIPC_READER_INIT_BY_TIMER </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> MQIPC reader [chars] initialized by timer not chasfs watcher. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> MQIPC reader initialized by timer not chasfs watcher. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Report this occurance to Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBAL-4-LONG_EXEC_BATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Long exec [[dec]:[dec]] create:exec:now [[dec]:[dec]:[dec]] e:p [[dec]:[dec]] resumes [[dec]] peer [[chars]] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DBAL batch execution took an extended period of time. This may or may not be a problem depending on the circumstances </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Collect log archive and show tech-support and report this occurance to Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBAL-6-DELAYED_BATCH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Delayed batch [[dec]:[dec]] create:exec:notif:now [[dec]:[dec]:[dec]:[dec]] eproc [[dec]] e:p [[dec]:[dec]] peer [[chars]] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DBAL batch with an extended lifetime. This can occur when large amounts of data and/or operations are being performed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If this is causing impact to any service, collect log archive and show tech-support and report this occurance to Cisco TAC. Otherwise, safe to ignore. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBGD-3-SYNTHETIC_TEST_PROBE_DNS_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> DNS server is [chars], [chars] interface not valid in VRF: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This error syslog is generated during synthetic test probes when FQDN cannot be resolved due to errors in DNS config </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-srvcability </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBGD-5-INTERFACE_AUTO_BW </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Interface [chars] (vpn: [dec]) bandwidth determined by auto speedtest, upstream b/w: [dec] bps, downstream b/w: [dec] bps </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated whenever upstream or downstream bandwidth of an interface is auto adjusted </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-srvcability </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DBGD-5-SYNTHETIC_TEST_PROBE_RESULT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Synthetic test probe result for app: [chars], url: [chars], src_intf: [chars], latency: [dec], loss: [dec]%%, score: [dec], count [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This notice syslog is generated once synthetic test probe finishes measuing loss and latency to given SaaS application </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> cedge-srvcability </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DC_DYNAMIC_XML_LOG-3-DC_DYNAMIC_XML_CANNOT_GET_XML_FILE_SIZE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unable to get file size of dynamic XML file dc_user_profiles.xml </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unable to get file size of dynamic XML file dc_user_profiles.xml </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DC_DYNAMIC_XML_LOG-3-DC_DYNAMIC_XML_CANNOT_LOAD_XML </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unable to load dynamic XML file dc_user_profiles.xml </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unable to load dynamic XML file dc_user_profiles.xml </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DC_DYNAMIC_XML_LOG-3-DC_DYNAMIC_XML_CANNOT_OPEN_XML_FILE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unable to open dynamic XML file dc_user_profiles.xml </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unable to open dynamic XML file dc_user_profiles.xml </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DC_DYNAMIC_XML_LOG-3-DC_DYNAMIC_XML_CANNOT_PARSE_XML </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unable to parse dynamic XML file dc_user_profiles.xml </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Unable to parse dynamic XML file dc_user_profiles.xml </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CDB_MAN_SUB_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to register as mandatory subscriber [chars] ([dec]): [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to mark DMI as a mandatory subscriber </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CHG_VRF_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The DMI application failed to set the correct virtual routing and forwarding network. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The DMI application failed to set the correct virtual routing and forwarding network; thus, it cannot communicate with Confd. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CLI_CHANNEL_CLOSED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CLI engine event channel closed unexpectedly ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The CLI engine event channel to the network element closed unexpectedly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> DMI will reset. No action necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CONFD_CB_REG_DONE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to complete callback registration [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A DMI application cannot complete callback registration with Confd. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CONFD_CB_REG_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to register callback with Confd [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A DMI application cannot register a particular callback with Confd. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CONFD_CONNECT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to connect to Confd via [chars] socket [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A DMI application cannot connect to Confd via a particular socket type. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CONFD_INIT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize Confd [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Confd did not initialize properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Back out any recent yang model updates. Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CONFD_SUB_DONE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to complete subscription [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A DMI application cannot complete subscriptions for changes to yang models. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Back out any recent model updates. Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CONFD_SUB_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to subscribe [chars] model [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A DMI application cannot subscribe for changes to a particular yang model. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Back out any recent model updates. Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-CONTROL_SOCKET_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Confd control socket ready check returned an error [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The control socket connection to Confd has returned an error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> DMI will reset. No action necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-MAAPI_CONNECT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Could not connect to Confd via DMI MAAPI socket [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to connect via MAAPI socket. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-MAAPI_WAIT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Wait for Confd to initialize to phase two failed [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Confd did not initialize properly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Back out any recent yang model updates. Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-NESD_CREATE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create nes daemon. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Either an out-of-memory condition has been encountered, or the DMI CLI engine cannot connect to the network element. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-NESD_INIT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize the network element synchronizer daemon </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The nesd daemon failed to initialize. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-NESD_PREHOOK_INIT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize component-specific add-ons to the network element synchronizer daemon </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The nesd daemon failed to initialize its component-specific add-ons. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-NES_RESET_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to reinitialize the DMI network element synchronizer daemon. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The network element synchronizer daemon cannot reset in order to recover from a critical error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-NETCONF_SSH_CRITICAL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> NETCONF/SSH: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A critical message from the NETCONF SSH daemon. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-NOTIFICATION_READ_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to read notification [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An attempt to read an event from the Confd notification socket failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> DMI will reset. No action necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-RUNNING_DATASTORE_INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Running datastore is invalid due to configuration failure during commit phase. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> IOS configuration failed during commit phase of the transaction. As a result, running datastore is not in sync with IOS configuration. Configuration to IOS is not allowed until datastore becomes valid after full sync. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Device will perform full-sync. CDB lock must be released by the controler to unblock full-sync. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-SD_INIT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize the syncfd daemon </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The syncfd daemon failed to initialize. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-SD_RESET_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to reinitialize the DMI syncfd daemon. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The syncfd daemon cannot reset in order to recover from a critical error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-VTY_SERVER_RESET_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to reinitializie VTY server utility instance. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to reset VTY server utility in order to recover from critical error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-WORKER_SOCKET_CLOSED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Confd worker closed unexpectedly [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The worker socket connection to Confd has closed unexpectedly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> DMI will reset. No action necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-2-WORKER_SOCKET_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Confd worker socket ready check returned an error [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The worker socket connection to Confd has returned an error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> DMI will reset. No action necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-AUTH_TIMED_OUT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> [chars] request from [chars]:[chars] for [chars] over [chars] timed out. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A AAA request timed out. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check connectivity to the configured AAA server. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CDB_ABORT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to abort transaction [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to abort a transaction. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CDB_READ_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Could not read the yang path '[chars]' from the DMI data store [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to read a specific model path from the DMI data store. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Download the model in question from the network element and verify the path exists. Update the model if needed. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CDB_SET_NAMESPACE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Could not set the model namespace '[chars]' for accessing the DMI data store [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to set a specific model namespace for accessing the DMI data store. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CDB_START_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Could not start session to read configuration from the DMI data store [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to open the DMI data store. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CDB_SYNC_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Confd subscription socket sync failed [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to sync the subscription socket. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_CONNECT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to connect to network element. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot connect to the network element in order to interact with its CLI parser. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the CLI engine protocol settings. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_CONNECT_LOSS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Detected connection to the network element has been lost. Attempting to reconnect </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI has lost connection to the network element. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_EVENT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to retrieve CLI engine event ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot retrieve its CLI engine event in order to interact with the network element CLI parser. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_LOG_LVL_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to set CLI engine logging level ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot set its CLI engine logging level. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart DMI. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_POLL_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to read CLI engine results - max polling attempts exceeded ([dec]). </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot read its CLI engine results in order to interact with the network element CLI parser. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_READ_EVENT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to read CLI engine event ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot read its CLI engine event in order to interact with the network element CLI parser. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_READ_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to read CLI engine results ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot read its CLI engine results in order to interact with the network element CLI parser. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_RECONNECT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error reconnecting to the network element ([dec]): [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The CLI engine has lost its connection to the network element and attempted to reconnect with an error occurred. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_TOKEN_RETRY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CLI engine authentication token is not available, retry for [dec] seconds </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> When IOSP-client connects to IOSP-server, it is authenticated by a session authentication token. The token is not available yet. Retry is made to retrieve the token. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> None required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_VTY_CREATE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The CLI engine failed to create a VTY instance ([dec]): [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The DMI CLI engine cannot create a VTY instance. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_VTY_OPEN_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The CLI engine failed to open a VTY ([dec]): [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The DMI CLI engine cannot open a VTY. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Free up available VTY resources by closing unused VTYs. Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_VTY_TIMEOUT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The DMI CLI engine failed to disable the VTY timeout ([dec]): [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI disables the VTY timeout for the network element synchronizer's VTY connection to ensure its number cannot be silently claimed by other VTY sessions. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> None required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_ENGINE_WRITE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error writing the CLI: [chars] - [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A CLI engine error occurred while send a command line to the network element's CLI parser </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Enter the command line in question manually via the network element's console or vty. If successful, stop and restart netconf-yang and retry. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-CLI_GEN_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to generate CLI change set [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred when requesting the CLI change set for a transaction. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-DIFF_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error saving diff file: [chars]/[chars] - [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An operating system error occurred while performing a diff of two files and redirecting to a third file. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check free space on device. Clean up if necessary. Also, reducing the value of max-diag-messages-saved in the cisco-ia model may help. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-DIR_EXISTS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Message diagnostics directory '[chars]' exists, but is not a directory. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A existing file is conflicting with a directory name. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove or rename the offending file. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-EDIT_REJECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The NETCONF running datastore edit request from application [chars], user [chars], via [chars] was recieved while a synchronization from the device running-configuration to the NETCONF running datastore was in progress. The edit request was rejected. Resend the edit request when the running-configuration synchronization has completed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A NETCONF running datastore edit request occurred simultaneously with a database synchronization operation. Thus, the request has been rejected. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry the NETCONF edit again later. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-INIT_SYNC_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Initial DMI sync failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI failed to synchronize the network element's running configuration with the DMI data store upon DMI startup. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-INTERNAL_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Internal error - [chars] [dec]: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An unexpected internal error has occurred. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Consult man page for impacted area to interpret the error code and string. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-INVALID_PRESERVE_PATH </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The NED preserve path specified |[chars]| does not exist. Please remove from the /native/cisco-ia/preserve-ned-path list. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A non-existent XPath has been specified to be preserved during complete syncs. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the offending path from the /native/cisco-ia/preserve-ned-path list. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-INVALID_REG_EXP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The regular expression |[chars]| is invalid. Please remove from the '[chars]' model or via the CLI '[chars] [chars]' </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An invalid regular expression has been specified which will not compile. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Remove the offending regular expression from the specified model or via "no CLI". </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-LOAD_SCHEMAS_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cannot load Confd schemas [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI failed to load Confd schemas for yang model namespaces. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Back out any recent yang model updates. Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_APPLY_TRANS_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to apply a transaction via DMI MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to apply a transaction via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_DELETE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to delete model path '[chars]' via DMI MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to delete a model path via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_FINISH_TRANS_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to finish a transaction via DMI MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to finish a transaction via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_KILL_SESSION_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Could not kill DMI MAAPI user session [dec] - [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A parser lock timeout has occurred, and DMI attempted to kill the session holding the global lock, but failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Kill the NETCONF user session holding the global lock manually. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_LOAD_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to load '[chars]' commands to model path '[chars]' via DMI MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to load commands to a model path via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_LOAD_FILE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to load file '[chars]' via DMI MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to load commands from a file via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_LOCK_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to lock the DMI data store via DMI MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to lock the DMI data store via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_SAVE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Could not save model path '[chars]' to file via DMI MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to save a model path via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_START_TRANS_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Could not start DMI MAAPI transaction [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to start a transaction via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_START_USER_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Could not start DMI MAAPI user session [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to start a user session via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MAAPI_UNLOCK_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to unlock the NETCONF running data store via MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to unlock the DMI data store via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MEM_UNAVAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Memory was not available to perform the DMI action. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Insufficient system memory is available to perform the DMI action. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-MODEL_RESTORE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> DMI failed to restore the model '[chars]' from the network element's running configuration to the DMI data store ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI failed to restore the model '%s' from the network element's running configuration to the DMI data store. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the netconf-yang section of the network element's running configuration. If populated with non-default values, stop and restart netconf-yang. If problem continues, restore the model's configuration in question via Netconf </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-NETCONF_KILL_SESSION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> NETCONF session [dec] has held a parser configuration lock/NETCONF datastore global lock for the maximum time allowed and has been killed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A parser lock timeout has occurred, and DMI has killed the corresponding NETCONF session. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Establish a new NETCONF session. Adjust your application to hold global locks for a shorter interval -- seconds, not minutes </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-NETCONF_SSH_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> NETCONF/SSH: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error message from the NETCONF SSH daemon. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SAVE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error saving file: [chars] - [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An operating system error occurred while opening or writing to a diagnostic file. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check free space on device. Clean up if necessary. Also, reducing the value of max-diag-messages-saved in the cisco-ia model may help. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_CLI_FILTER_ADD_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to add CLI configuration monitor filter ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot add a CLI filter to monitor for external CLI changes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_CLI_FILTER_CREAT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create CLI configuration monitor filter for pattern '[chars]' ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot create a CLI filter to monitor for external CLI changes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_CLI_FILTER_MODE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to set mode for CLI configuration monitor filter ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot set the mode for its CLI filter to monitor for external CLI changes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An attempt to synchronize the running configuration to the NETCONF running data store has failed: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An attempt to send the running-config to ConfD to repopulate its data store has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Identify the offending CLI that makes the sync fail and delete it from the configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An attempt to synchronize the running configuration to the NETCONF running data store has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An external change (outside of NETCONF or RESTCONF) has been detected. An attempt to send the running-config to Confd to repopulate its data store has failed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Force a full sync via the 'sync-from' RPC. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_LOCK_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to lock the NETCONF running data store via MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to lock the DMI data store via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_MODULE_CHECK_ADD_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to add module up check ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot add a module up check to monitor for module up status. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_OIR_FILTER_ADD_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to add OIR monitor filter ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot add an OIR filter to monitor for OIR induced configuration changes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_OIR_FILTER_CREAT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create OIR monitor filter ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot create an OIR filter to monitor for OIR induced configuration changes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_SYSLOG_FILTER_ADD_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to add syslog monitor filter ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot add a syslog filter to monitor for external CLI changes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_SYSLOG_FILTER_CREAT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create syslog monitor filter for pattern '[chars]' ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot create a syslog filter to monitor for external CLI changes. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-SYNC_UNLOCK_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to unlock the NETCONF running data store via MAAPI [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to unlock the DMI data store via MAAPI. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-VTY_NUM_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> DMI failed to retrieve its tty number from the network element </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI must keep track of its tty number it uses to send command lines to the network element's parser in order to avoid triggering its own sync events </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check that the 'show users line' command line is working </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-VTY_SERVER_CREAT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to create VTY server utility instance. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to create VTY server utility instance for DMI operational data use. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-3-VTY_SERVER_START_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to start VTY server utility instance. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to start VTY server utility instance for DMI operational data use. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Stop and restart netconf-yang. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CANDIDATE_DATASTORE_DIRTY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Synchronization of the running configuration to the running datastore is deferred because the candidate datastore is dirty. Commit or discard the uncommitted configuration. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Configuration is performed from the IOS terminal while the candidate datastore has uncommitted configuration. The system cannot perform sync until the configuration in the datastore is either committed or discarded. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Commit or discard the configuration in the candidate datastore in order for the sync to proceed. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CDB_MAINTENANCE_MODE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> WARNING!!! - CDB MAINTENANCE MODE IS ACTIVE - [chars]. This mode is intended only for Cisco support - it must be disabled for normal NETCONF operation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Cisco-support only NETCONF mode has been enabled as a recovery mechanism for an out-of-sync condition. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Disable this mode in order to return the device to normal NETCONF operation. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CLI_ENGINE_ENABLE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The DMI CLI engine failed to enable the network element's CLI parser (enter privileged mode) ([dec]): [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot enter privileged mode when communicating with the network element's CLI parser. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. Check AAA settings for the Netconf/Restconf user account. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CLI_ENGINE_RC_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The DMI CLI engine failed to get the overall return code from the command '[chars]' ([dec]): [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot read CLI engine return code for the particular command. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CLI_ENGINE_STATE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to query the CLI engine state ([dec]): [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DMI cannot read its CLI engine state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Perform a manual sync operation to ensure the DMI data store is in sync with the network element's running configuration. If problem continues, stop and restart netconf-yang </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CLI_LOCK_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to obtain exclusive access to the IOS parser: [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An IOS parser error has occurred attempting to obtain a configuration parser lock. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry NETCONF operation. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CLI_LOCK_OVERRIDE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Configuration lock cleared and obtained by NETCONF session. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An IOS parser lock has been cleared to avoid conflict with NETCONF session. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry CLI operation after NETCONF session completes. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CLI_ROLLBACK_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CLI rollback warning: tid ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd induced CLI transaction was aborted and during the rollback CLIs, an error was returned </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Confirm that the network element's running configuration is in the original state before the failed transaction </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CLI_UNLOCK_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to unlock the IOS parser store: [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An IOS parser error has occurred attempting to unlock the parser lock. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Retry NETCONF operation. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CONFD_ROLLBACK_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error copying Confd rollback file ([dec]): [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error occurred saving the Confd rollback information. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please enable rollback in Confd. Check for free file system space. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-CONTROL_SOCKET_CLOSED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Confd control socket closed [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The control socket connection to Confd has closed unexpectedly. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> DMI will reset. No action necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-DIAG_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Unable to prepare file system for message diagnostics. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error occurred saving DMI message diagnostics. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check for free file system space. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-NETCONF_TRACE_WARN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error copying netconf.trace. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An error occurred saving the Netconf trace information. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please enable netconfTraceLog in Confd. Check for free file system space. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-RUNNING_DATASTORE_VALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Running datastore is valid. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Running datastore is valid after successful full-sync operation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Rollback configurations using rollback-files RPC to bring device into well known state. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-4-SUB_READ_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Confd subscription socket read failed [chars] ([dec]): [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Confd error has occurred attempting to read the subscription socket. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> DMI will reset. No action necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-ACTIVE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> process is in steady state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> process is in steady state. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-AUTHENTICATION_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Authentication failure from [chars]:[chars] for [chars] over [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A user failed to authenticate. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-AUTHORIZATION_FAILED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User '[chars]' from [chars]:[chars] was not authorized for [chars] over [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A user was not authorized for the requested service. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-AUTH_PASSED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User '[chars]' authenticated successfully from [chars]:[chars] for [chars] over [chars]. External groups: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A user authenticated successfully for a service. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-CONFIG_I </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Configured from [chars] by [chars], transaction-id [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A change to the running configuration was performed using NETCONF or RESTCONF. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-INITIALIZED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> process has initialized. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> process has initialized. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-NACM_INIT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> NACM configuration has been set to its initial configuration. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The running-config under the /nacm tree has been set to its initial configuration. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-NACM_READRULES </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> NACM readrules for privilege level [dec] loaded successfully. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> NACM rules to permit readonly access loaded successfully. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-RESET </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> process internal state reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> process internal state reset. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-SYNC_COMPLETE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The running configuration has been synchronized to the NETCONF running data store. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An external change (outside of NETCONF or RESTCONF) has been detected; thus, the running-config has been sent to Confd to repopulate its data store. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-SYNC_NEEDED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Configuration change requiring running configuration sync detected - '[chars]'. The running configuration will be synchronized to the NETCONF running data store. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A configuration change that may trigger additional changes has been detected; thus, the running-config will be sent to Confd to repopulate its data store. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-5-SYNC_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Synchronization of the running configuration to the NETCONF running data store has started. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An external change (outside of NETCONF or RESTCONF) has been detected; thus, the running-config will be sent to Confd to repopulate its data store. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-6-NETCONF_SSH_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> NETCONF/SSH: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An informational message from the NETCONF SSH daemon. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DMI-7-GEN_DEBUG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> DMI DEBUG [chars] [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A debug message for syslog consumption. For troubleshooting wihtout btrace </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DOT11_LOG-3-CLIENT_DOT11_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General Client Dot11 Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DOT1X-3-PROC_START_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Dot1x unable to start. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to create the Dot1x process. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart Dot1x process by entering &lt;cmd&gt;dot1x system-auth-control&lt;cmd&gt; command. If this message recurs, Reload the device. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DOT1X-3-UNKN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An unknown operational error occurred. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The Dot1x process cannot operate due to an internal system error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reload the device/process </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DOT1X-4-INFO_EAPOL_PING_RESPONSE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The interface [chars] has an 802.1x capable client with MAC [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An EAPOL ping was sent out on this port to determine 802.1x readiness of the client attached. An EAPOL response has been received by the device such as a PC. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DOT1X-4-MEM_UNAVAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Memory was not available to perform the 802.1X action. AuditSessionID [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Insufficient system memory is available to perform the Dot1x Authentication. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DOT1X-5-FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Authentication failed for client ([chars]) with reason ([chars]) on Interface [chars] AuditSessionID [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Dot1x authentication was unsuccessful. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DOT1X-5-RESULT_OVERRIDE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Authentication result overridden for client ([chars]) on Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Authentication result was overridden </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DOT1X-5-SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars] Username [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Dot1x authentication was successful. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSS_EXT_2_DTLS_REPLAY_ATTACK </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - DTLS Replay Attack for connection closed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DTLS Replay Attack for connection closed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSS_EXT_2_DTLS_REPLAY_ATTACK_DETECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - DTLS Replay Attack detected for Source IP [chars] and Dest IP [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DTLS Replay Attack detected for Source IP and Dest IP </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FPT_ITT_1_DTLS_SESSION_CLOSED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - DTLS peer has closed the connection, cipher [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DTLS connection established with peer </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FPT_ITT_1_DTLS_SESSION_ESTABLISHED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - DTLS connection established with peer, cipher [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> DTLS connection established with peer </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DTLS_AUDIT_MESSAGE-6-FIPS_AUDIT_FPT_ITT_1_DTLS_SESSION_HANDSHAKE_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Failed to complete DTLS handshake with peer, reason: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to complete DTLS handshake with peer </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DTLS_TRACE_MSG-3-WLC_DTLS_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> DTLS Error, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General ewlc Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> DTLS_TRACE_MSG-3-X509_CERT_VERIFY_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Cert verify Error, [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General ewlc Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EAP-2-PROCESS_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> EAP critical error [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This is critical condition where the router could not perform EAP process related operation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Review SM logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Reload the device/process. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EAP-3-BADPKT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IP=[chars] HOST=[chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This messages informs that the router received an invalid or malformed EAP packet from the specified host. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check specified host for EAP operation. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EAP-6-FIPS_UNSUPPORTED_METHOD </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Method [chars] in eap profile [chars] is not allowed in FIPS mode </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This message informs that a method is not supported in FIPS mode. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Use FIPS supported methods - PEAP, TLS and FAST </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EAP-6-MPPE_KEY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IP=[chars] MPPE_RECV_KEY_LENGTH=[dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This messages informs that the router received MPPE KEY for the specified host. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EMD-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This error could be due to a software defect or system resource limitation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the card. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EMD-0-RESOLVE_FRU </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to determine [chars] card because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system was unable to to determine a card state. This error could be due to a software defect or system resource limitation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the card. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EMD-0-SERVICES_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize general application services because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize the application services. This error could be due to a software defect or system resource limitation. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the card. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EMD-3-IDPROM_ACCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed access or process an IDPROM because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to access an IDPROM or an IDPROM process failed. This error can occur from a hardware defect, software defect, or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for IDPROM and hardware errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EMD-3-IDPROM_SENSOR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> One or more sensor fields from the idprom failed to parse properly because [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> One or more IDPROM sensor fields failed to parse properly. The most likely reason is a checksum failure in the IDPROM from incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for IDPROM and hardware errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EMD-3-PFU_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> The RP has failed to initialize a Power Supply/Fan module controller because [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The route processor (RP) failed to initialize a power supply or a fan module controller. This error could be caused by a hardware defect or a C2W access failure. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for C2W and hardware errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EMD-3-SENSOR_INITIALIZATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to initialize sensor monitoring because [chars]. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The system failed to initialize an IDPROM sensor monitoring process. This error can occur from a hardware defect, software defect, or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Examine the logs for IDPROM and hardware errors. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM-4-ACL_CONFIG_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> ACL NAME '[chars]' | ACE SEQUENCE [dec] | RESULT FAILURE | REASON [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This message indicates that adding an ACE to the specified ACL was ignored because of wrong configuration </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Change ACE configuration for the specifed ACL </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM-4-POLICY_APP_FAILURE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Policy Application Failed for Client [[chars]] MAC [[chars]] AuditSessionID [[chars]] for POLICY_TYPE [chars] POLICY_NAME [chars] REASON [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This message indicates that the displayed policy for the client could not be applied by the EPM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Policy application failure could happen due to multiple reasons.The reason for the failure is notified to the client and the client has to take appropriate action based on it </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM-6-AAA </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> POLICY [chars]| EVENT [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This message indicates a download request has been sent/downloaded successfully for the specified dACL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM-6-AUTH_ACL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> POLICY [chars]| EVENT [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> his message indicates a AUTH_DEF_ACL or AUTH_DEF_ACL_OPEN has been applied or removed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM-6-IPEVENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IP [chars]| MAC [chars]| AuditSessionID [chars]| EVENT [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This message indicates the IP event Wait/Release/Assignment that has occured with respect to the specified host </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM-6-POLICY_APP_SUCCESS </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Policy Application succeded for Client [[chars]] MAC [[chars]] AuditSession ID [[chars]] for POLICY_TYPE [[chars]] POLICY_NAME [[chars]] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This message indicates that the displayed policy for the client has been applied successfully by the EPM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM-6-POLICY_REQ </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> IP [chars]| MAC [chars]| AuditSessionID [chars]| EVENT [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This message indicates that a policy application/remove request has been received by the EPM </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM_PLUGIN-5-ERR_HS20_URLFILTER_NOT_CONFIGURED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Attempt to enable url filtering for Hotspot 2.0 client [chars] without having an Hotspot 2.0 urlfilter configured </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An attempt was made to activate post-auth Hotspot 2.0 url filtering on the client, as requested by the Radius server but no urlfilter list name configured under the wireless hotspot anqp-server linked with the wireless policy profile. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-spwifi </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Make sure a valid urlfilter list name is configured under the wireless hotspot anqp-server profile linked with the wireless policy profile </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM_PLUGIN-5-ERR_VLAN_NOT_FOUND </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Attempt to assign non-existent or shutdown VLAN [chars] to 802.1x port [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> An attempt was made to assign a VLAN to an 802.1x port, but the VLAN was not found in the VTP database. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Make sure the VLAN exists and is not shutdown or use another VLAN. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM_PLUGIN-5-IGNORED_VLAN_VALIDATION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Vlan [chars] not defined on the controller, choosing Vlan [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Either the client is export-foreign or fallback-vlan CLI is configured </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check if fallback-vlan is configured or if the client is export foreign. In such a case, no action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM_PLUGIN-5-PRINT_SEQUENCE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Creating ACE [dec] for ACL [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Every 10000th ACE and its ACL name printed to indicate the ACEs being created. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Please check that the ACE count matches the configured ACE count. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM_PLUGIN-5-VLAN_ASSIGN </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Vlan assignment successful for client : [chars] with Vlan id : [dec] on Interface : [chars], AuditSessionID is [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> The syslog indicates that the Vlan was assigned to the client </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPM_PLUGIN-6-STICKY_TIMER_START </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Sticky timer of [dec] seconds started for mac [chars] interface [chars] for template [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Log is used to notify the start of the sticky timer </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Sticky timer has begun. No action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EPOCH-6-EPOCH_REJECTED </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Peer [chars] has rejected epoch: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> This error occurs if epoch from shell-manager has been rejected by the peer. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Check the epoch and peer state. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EVUTIL-3-PERMISSION </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Operation not permitted for pid [dec] tid [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Eventlib has detected that a process has attempted to invoke an API that is listed as having a level of permission. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Review the process logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EVUTIL-3-PREREQUISITE_INIT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> A preferred library has failed to initialize: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Eventlib has detected that a preferred library which provides infrastructure services has failed to fully initialize. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Review the process logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EVUTIL-6-PREREQUISITE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Preferred library is absent </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Eventlib has detected that a preferred library is missing from the process. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This is an informational message. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_HA_LIB_MESSAGE-3-BULK_SYNC_STATE_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error: Bulk sync status : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Bulk sync status Error message. TERMINATED - Bulk-sync terminated </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_HA_LIB_MESSAGE-3-WIRELESS_CONFIG_SYNC_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error: Wireless config sync not complete. Reloading the WLC! </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Switchover happens before wireless config sync is complete! </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_HA_LIB_MESSAGE-6-BULK_SYNC_STATE_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> INFO: Bulk sync status : [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Bulk sync status INFO message. COLD - Bulk-sync ongoing. CONFIG_DONE - critical DB sync complete. WARM - Most of the DB's synced. HOT - Bulk-sync completed </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_INFRA_MESSAGE-3-EWLC_EVENTHOG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Event name: [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> System has detected an excessive number of sub-events. Normal WLC functionality may be impacted. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-app-infra </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_INFRA_MESSAGE-3-EWLC_GEN_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> General ewlc Error Message. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_INFRA_MESSAGE-4-EWLC_CAC_WARNING_MSG </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CPU Utilization [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CPU utilisation for the process has breached the monitored level, some functionality may be impacted. If the condition persists, action may be needed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If the condition is transient and does not occur frequently, these messages can be ignored otherwise an investigation is needed. LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_INFRA_MESSAGE-6-EWLC_CAC_INFO </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CPU Utilization [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> CPU Utilisation for the process has recovered below the monitored level </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_UTILITY_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_1_WPA2_INPUT_TOO_LARGE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Failed to compute PRF mode ([dec]), size ([dec]) - input is too large </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to compute PRF mode because of input is too large </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_UTILITY_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_1_WPA2_INVALID_MODE </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Failed to compute PRF mode ([dec]), size ([dec]) - invalid mode </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to compute PRF mode because of invalid mode </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EWLC_UTILITY_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_CKM_1_WPA2_OUTPUT_BUFFER_SMALL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> User ID: [chars] - Failed to compute PRF mode ([dec]), size ([dec]) - output buffer is too small </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Failed to compute PRF mode because of output buffer is too small </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_CLIENT-2-ECC_DOUBLE_BIT_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Double bit ECC errors observed. NP (CC card) is going to be reloaded to recover </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> ECC error observed on the NP device.Reset the NP Device. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This error is usually self-correcting. If the problem persists, the CC card/hardware may need to be replaced. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_CLIENT-3-ECC_SINGLE_BIT_ERROR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Single bit ECC error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> ECC error observed on the NP device.Reset the NP Device. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> This error is usually self-correcting. If the problem persists, the MIP100 hardware may need to be replaced. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_CLIENT-3-OBJECT_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Failed to bringup [chars]. Failure reason is [chars] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Bringup of object(NP/Bay/Interface) has failed in EZMAN. This can be due to any hardware/software failures and can be a serious error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Restart the Linecard. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_CLIENT-3-VLAN_STATS_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> NP Counter Read Failed for Vlan [dec] [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> NP VLAN statistics error. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Continous MSG of these Events, Trigger the reboot of the system </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_CLIENT-5-EZ_CLIENT_VLAN_FULL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> TCAM Full VLAN is not Able to add </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Rx Sync Failed for Interlaken, Status Timer Expired. So, Resetting the Rx Interlaken Core </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_INFRA-3-PLATFORM_ID_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Invalid HW Part number([dec]) and HW Revision([dec]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> HW Part number and revision read from the IDPROM are not showing up expected values which means the IDPROM is either corrupted or incorrectly programmed. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Possible Hardware issue. Change the hardware. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_RM-2-FPGA_VERSION_CHECK_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CASTOR FPGA[[dec]] version does not meet minimum required version. Read version : 0x%x, Min Req Version : 0x%x </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> Castor FPGA version requirement not met. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_RM-2-SEM_ERR </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> CASTOR FPGA[[dec]] - SEU event has occurred. Event code: [dec], SLR: 0x%x, Frame: 0x%x, Word, 0x%x, Bit: 0x%x </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> A Single Event Upset (SEU) event has occurred. These events may occur at any point of time, but are considered to be rare. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> If the error is seen only once, there is no need for anything to be done. If these errors are appearing continuously/persistently, please copy over the logs as they appear in the console, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_RM-3-L2_BLOCK_EVENT </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> L2 Block Event Node:[chars] (0x%08X - Tree [dec] Instance [dec]) </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> NP of L2 is generating Events. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> Continous MSG of these Events, Trigger the reboot of the system </td> </tr> <tr> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__1 "> EZMAN_RM-3-SERDES_AUTOTUNE_FAIL </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__3 "> Serdes Autotune [chars] on lane [dec] </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__4 "> NP5 Serdes RX is unable to autotune to the peer device's TX. This is a physical layer issue between NP5 and peer device. </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-a-to-e-syslogs_17161__entry__6 "> OIR the Host-card if possible. </td> </tr> </tbody> </table> </section> </div>  <nav role="navigation" class="related-links"></nav>  </article> <article class="topic reference nested2" aria-labelledby="ariaid-title7" lang="en-US" id="r-f-to-j-syslogs_17161"> <h3 class="title topictitle3" id="ariaid-title7"> F to J </h3> <div class="body refbody"> <section class="section" id="r-f-to-j-syslogs_17161__d54e28568"> <table width="100%" border="1" class="table"> <caption></caption> <colgroup> <col style="width:37.334510150044125%"> <col style="width:8.8261253309797%"> <col style="width:16.504854368932037%"> <col style="width:8.8261253309797%"> <col style="width:8.8261253309797%"> <col style="width:19.68225948808473%"> </colgroup> <thead class="thead"> <tr> <th font-weight="bold" class="entry align-left" id="r-f-to-j-syslogs_17161__entry__1"> Facility-Severity-Mnemonic </th> <th font-weight="bold" class="entry align-left" id="r-f-to-j-syslogs_17161__entry__2"> Severity-Meaning </th> <th font-weight="bold" class="entry align-left" id="r-f-to-j-syslogs_17161__entry__3"> Message </th> <th font-weight="bold" class="entry align-left" id="r-f-to-j-syslogs_17161__entry__4"> Message-Explanation </th> <th font-weight="bold" class="entry align-left" id="r-f-to-j-syslogs_17161__entry__5"> Component </th> <th font-weight="bold" class="entry align-left" id="r-f-to-j-syslogs_17161__entry__6"> Recommended-Action </th> </tr> </thead> <tbody class="tbody"> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED-0-HWSTALL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ASIC [dec] CORE [dec] Packet Buffer Complex Stalled. Switch will be reloaded\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The specified asic/core packet buffer complex stalled. This is a critical error. This switch will reload. If there is a redundant switch, switch over will happen </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED-2-INIT_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Module [chars] failed initialization\n[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The specified module failed initialization. The switch will reload. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_EPC_ERRMSG-4-UNSUPPORTED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> EPC on interface [chars] is not supported.To recover, Stop the capture.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Unsupported configuration. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Stop the capture on %s interface.\n </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_L3M_SYS_MSG-3-RSRC_IPv4_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate the hardware resource for ipv4 multicast entry. Use \'show platform software fed [switch] &lt;module&gt; ip multicast retry mroute\' for details. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_L3M_SYS_MSG-3-RSRC_IPv6_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate the hardware resource for ipv6 multicast entry. Use \'show platform software fed [switch] &lt;module&gt; ipv6 multicast retry mroute\' for details. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_L3M_SYS_MSG-6-RSRC_Recovered </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed Multicast hardware resources recovered. Multicast replication will be operational again. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_L3_ERRMSG-3-L3_FIB_OUT_OF_RESOURCE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to program [chars] fib [chars]/[dec] in NPU due to out of resource\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Running out of Hardware resource to support the scale of this L3 FIB feature. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform software fed active ip/ipv6 route summary </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_L3_ERRMSG-3-L3_PORT_OUT_OF_RESOURCE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to program port [chars] in NPU due to out of resource\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Running out of Hardware resource to support the scale of the L3 Port feature. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Verify supported scale for the platform from sdm and reduce the L3 Port scale accordingly. Capture show platform hardware fed active fwd-asic resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_L3_ERRMSG-3-UNSUPPORTED_ACTION </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ERROR:[chars] Additionally, please remove this command from the interface config mode.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The specified action is not supported on this platform. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this unsupported functionality from the release documents and remove the command from the interface config mode </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_L3_ERRMSG-6-ADVISORY_NOTICE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Advisory Notice: [chars] \n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This message is to bring attention to the user about certain capabilities and limitations of a feature. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is needed. Please be mindful of the limitations. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-3-mpls_unsupported_feature </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Unsupported feature. Failed to program. [chars] in software or hardware\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The feature is not yet supported. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this unsupported feature from the release documents and remove the command from the interface config mode </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-4-MPLS_L2VPN_ATOM_DISP_PAUSE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Critical limit reached for [chars] resource. MPLS L2VPN ATOM_DISP Create PAUSED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS L2VPN ATOM DISP creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-4-MPLS_L2VPN_ATOM_IMP_PAUSE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Critical limit reached for [chars] resource. MPLS L2VPN ATOM_IMP Create PAUSED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS L2VPN ATOM IMP creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-4-MPLS_L2VPN_XCON_AC_PAUSE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Critical limit reached for [chars] resource. MPLS L2VPN XCON_AC Create PAUSED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS L2VPN XCON_AC creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-4-MPLS_LABEL_PAUSE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Critical limit reached for [chars] resource. MPLS Label Create PAUSED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS Label OCE creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-4-MPLS_LENTRY_PAUSE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Critical limit reached for [chars] resource. Lentry Create PAUSED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS Lentry creations are paused as needed resources(mentioned in error message) are not available so new label entries can not be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-4-mpls_out_of_resource </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Out of resource for MPLS [chars]. Failed to program [chars] in hardware\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Running out of Hardware resource to support the scale of this MPLS feature. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-6-MPLS_L2VPN_ATOM_DISP_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] resources are now available. MPLS L2VPN ATOM_DISP Create RESUMED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS L2VPN ATOM DISP creations are resumed. Now new entries can be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-6-MPLS_L2VPN_ATOM_IMP_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] resources are now available. MPLS L2VPN ATOM_IMP Create RESUMED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS L2VPN ATOM IMP creations are resumed. Now new entries can be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-6-MPLS_L2VPN_XCON_AC_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] resources are now available. MPLS L2VPN XCON_AC Create RESUMED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS L2VPN XCON_AC creations are resumed. Now new entries can be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-6-MPLS_LABEL_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] resources are now available. MPLS Label Create RESUMED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS Label creations are resumed. Now new entries can be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_MPLS_ERRMSG-6-MPLS_LENTRY_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] resources are now available. Lentry Create RESUMED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS Label entries creations are resumed. Now new label entries can be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_PUNJECT-6-PKT_CAPTURE_FULL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Punject pkt capture buffer is full. Use show command to display the punted packets.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> All the available punt capture buffers have been written with punted packets. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is needed. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_PUNJECT_CLI-6-EPDA_NPU_TRAPS_DEBUGGING_WARNING </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Warning: Please note traps enabled in Enhanced Packet Drop Analyzer (EPDA) will share the counters in Enhanced Drop Detection(EDD) CLI. This will result in showing the same counter values for the trap(s) in EDD\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> When EPDA is enabled the counters will be shared by EDD while displaying EDD counters </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is needed. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_PUNJECT_CLI-6-EPDA_TM_TRAPS_DEBUGGING_WARNING </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Warning: Enabling TM traps will affect Per VOQ counters. Please clear TM traps once drop-capture is completed\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Enabling TM traps will affect per voq counters </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is needed. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_QOS_ERRMSG-3-FED3_SERVICE_POLICY_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to apply service-policy.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred during service-policy installation in FED. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> pangea-qos </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Need to find the info from logs. Use "sh platform software trace message fed active" to find the logs </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_QOS_ERRMSG-3-FED3_SERVICE_POLICY_FAILED_PREVIOUSLY </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The policy [chars] on interface [chars] on [chars] direction is already in ERROR state. No action will be taken.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> There was an error occured early. No further action is taken until the policy removed and reattached. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> pangea-qos </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Remove the policy from the interface and reattach. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_VLAN_MAPPING_ERRMSG-3-MAPPING_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to update VLAN_MAPPING in hardware for interface [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurs when mapping VLAN. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> The resource limit would have been reached, remove the recent added vlan mapping configuration </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED3_VLAN_MAPPING_ERRMSG-3-VP_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to add VP in hardware for interface [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurs when adding VP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> VP limit would have been reached, please remove the recent configuration </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_CCK_ERRMSG-4-INCONSISTENCY_FOUND </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Consistency Checker(CCK) detected inconsistency for [chars]. Check 'show consistency run-id [dec] detail'. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> CCK has detected the inconsistency between the IOSD and fmanFP tables. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out the entry using the show consistency &lt;&gt; command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_BOTH_V4_V6_ADDR_SET </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to start, both v4 & v6 addr is set </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Packet trace failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_INVALID_IN_FILE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to start, invalid file, not found </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Packet trace failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_INVALID_PORT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to start, invalid Port, not found </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Packet trace failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_INVALID_SWITCH </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to start, invalid Switch, not found </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Packet trace failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_MAC_NOT_SET </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to start, for simulation packet generation src/dst mac is must </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Packet trace failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_MEMORY_ALLOC_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to start, memory allocation failed </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Packet trace failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_MULTIPLE_ACES </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Multiple entries found in provided ACL, common fields will get overlapped by later entries </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Warning for acl having multiple aces </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_NETWROK_PREFIX_NOT_SUPPORTED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to start, simulation needs full address, netwrok prefix not supported </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Packet trace failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_SRC_AND_DST_ADDR_NOT_SET </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to start, both src and dst addr is required </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Packet trace failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_COND_DEBUG-6-COND_DEBUG_START_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to start trace </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Packet trace failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-3-ADVBASEATTACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Unable to attach flow monitor or IP NBAR/Et-analytics to interface [chars]. Flow monitor and IP NBAR/Et-analytics are not allowed on the same interface. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not allowed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please try to modify your configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-3-ATTACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to attach flow monitor to interface [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurs when attaching the flow monitor to the interface. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using show mgmt-infra trace messages fed-fnf-config-error switch number command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-3-DETACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to detach flow monitor from interface [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Error occurs when detaching the flow monitor from the interface. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using show mgmt-infra trace messages fed-fnf-config-error switch number command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-3-FLOWMONITOR_ENABLEERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> '[chars]' enablement failed due to '[chars]' configuration present on interface [chars]. These features cannot co-exist. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not allowed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please try to modify your configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-3-REFMONITOR_ENABLEERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to enable [chars] [chars] Reflexive ACL on [chars] and traffic will be dropped; '[chars]' configuration present on interface. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not allowed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please try to modify your configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-3-REFMONITOR_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to enable [chars] [chars] Reflexive ACL on [chars] and traffic will be dropped; Netflow programming failed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration failed; traffic will be dropped on this interface. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error with the help of FED logs </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-3-REFMONITOR_RSCFULL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to enable [chars] [chars] Reflexive ACL on [chars] and traffic will be dropped; Netflow profiles exhausted. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration failed; traffic will be dropped on this interface. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Remove the existing FNF/FNF based feature attachment and retry </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-3-SGTCATTACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Detach the existing [chars] before attaching [chars] to interface [chars]. These features cannot co-exist. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not allowed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please try to modify your configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-6-NOTALLOWED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is not allowed.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not allowed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please try to modify your configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_FNF_ERRMSG-6-UNSUPPORTED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is unsupported\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not supported. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please do not use the current configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_IPC_MSG-5-FAST_RELOAD_COMPLETE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Fast reload operation complete </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This is used to indicate that the fast reload is complete. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> accsw-p-fsu </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needed. This is not an error. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_IPC_MSG-5-xFSU_COMPLETE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Fast reload operation complete </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This is used to indicate that the fast reload is complete. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> accsw-p-fsu </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needed. This is not an error. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_IPC_MSG-5-xFSU_NIF_DISABLE_START_TIME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> NIF was DISABLED at [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> XFSU NIF Disable Timestamp </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> accsw-p-fsu </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needed. This is not an error. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_IPC_MSG-5-xFSU_NIF_ENABLE_START_TIME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> NIF was ENABLED at [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> XFSU NIF ENABLE Timestamp </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> accsw-p-fsu </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needed. This is not an error. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_IPC_MSG-5-xFSU_NIF_UPGRADE_TIME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> NIF UPGRADE took [dec] milliseconds </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> XFSU NIF UPGRADE Time </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> accsw-p-fsu </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needed. This is not an error. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L2M_ERRMSG-3-COLLISION_LIST_RSRC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate hardware resource for group [chars] - reason: [chars] - entry collided with groups: [chars] in hash </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L2M_ERRMSG-3-RSRC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate hardware resource for group [chars] - resource type: [chars] - reason: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L2M_ERRMSG-3-VLAN_RSRC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate hardware resource for vlan [dec] - resource type: [chars] - reason: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3M_ERRMSG-3-RSRC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate hardware resource for [chars] - rc:[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3M_ERRMSG-4-lsm_LB_warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IGP load balance not supported for Label Switch Multicast. Configure 'no mpls mldp forward recursive' to disable </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS IGP load balance/ECMP is not supported. Entries will be put into retry and once user disables the ECMP via CLI, LSM will recover </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3M_ERRMSG-4-lsm_RSRC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate the hardware resource for LSM(Label Switch multicast) entry, LSM replication will be impacted </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. Entry will be in retry queue waiting for resources, once available LSM will recover </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3M_ERRMSG-4-lsm_label_warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> MPLS label range from [dec] to [dec] is not supported with Label Switch Multicast (LSM). Reconfigure 'mpls label range' accordingly. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS range of upper 4k from 1M supported protocal value is reserved for LSM to use internally. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3M_ERRMSG-4-lspvif_RSRC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate the hardware resource for Lspvif Adjacency, some of the LSM MDTs will be impacted </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. Entry will be in retry queue waiting for resources, once available LSM MDTs will recover </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3M_ERRMSG-6-lsm_RSRC_ERR_recovered </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed LSM hardware resources recovered. LSM replication will be operational again </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource failure is recovered again and LSM(Label Switch Multicast) will be back to normal </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3M_ERRMSG-6-lspvif_RSRC_ERR_recovered </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Retry of Lspvif Adjacency hardware resource(s) is(are) successful, LSM MDTs will be operational again </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource failure is recovered again and LSM(Label Switch Multicast) will be back to normal </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-L3_FIB_ENTRY_PAUSE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Critical limit reached for [chars] resource. L3 FIB Entry Create PAUSED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> L3 FIB Entry creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for l3 routes summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-L3_FIB_ENTRY_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] resources are now available. L3 FIB Entry Create RESUMED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> L3 FIB Entry creations are resumed. Now new entries can be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-MAX_TUNNEL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The maximum number of Tunnel has been reached\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> New Tunnels will not be working as expected. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-MPLS_LABEL_PAUSE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Critical limit reached for [chars] resource. MPLS Label Create PAUSED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS Label OCE creations are paused as needed resources(mentioned in error message) are not available so new entries can not be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls routes summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-MPLS_LABEL_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] resources are now available. MPLS Label Create RESUMED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS Label creations are resumed. Now new entries can be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-MPLS_LENTRY_PAUSE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Critical limit reached for [chars] resource. Lentry Create PAUSED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS Lentry creations are paused as needed resources(mentioned in error message) are not available so new label entries can not be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out from error messages about the resources that are not available. Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-MPLS_LENTRY_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] resources are now available. Lentry Create RESUMED.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> MPLS Label entries creations are resumed. Now new label entries can be programmed in HW. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needs to be taken. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-RSRC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate hardware resource for [chars] - rc:[dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-RSRC_L3_LE_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Interface [chars] creation failed due to L3 Interface hardware resource exhaustion </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource for L3 Interface exhausted and the requested interface will not be created. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect output of show platform hardware fed switch &lt;switch number&gt; fwd-asic resource utilization command. Check if RSC_L3IF_LE has exhausted. If yes, free up any unused L3 Interfaces by doing no interface &lt;interface&gt; and retry creating the failed interface. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-UNSUPPORTED_CMD </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is not supported on the interface [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The specified cli is not yet supported. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this unsupported feature from the release documents and remove the command from the interface config mode </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-ecr_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Platform unicast routing ecr module encountered [chars] error in FED\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in platform ecr code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this error by using the show platform ipunicast ecr commands. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-fib_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Platform unicast routing fib module encountered [chars] error in FED\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in platform fib code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this error by using the show platform ipunicast route commands. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-intf_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] interface [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Error in HW programming for Interface. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this failure from ifm show outputs and debugs for the interface </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-mpls_ecmp_modify_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> MPLS Load Balance modify is not supported [dec]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Modification of an ECMP object with MPLS Adjacencies is not supported yet. It is not an expected event </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this error by using the show commands for the specified object and identify the possible trigger for the modify. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-mpls_out_of_resource </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Out of resource for MPLS [chars]. Failed to program [chars] in hardware\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Running out of Hardware resource to support the scale of this MPLS feature. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Verify supported scale for the platform from sdm and reduce the scale accordingly. Capture show platform command for mpls summary, tcam utiliztion and resource utilization </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-mpls_recursive_label_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Unsupported recursive MPLS label for local_label [dec] [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The specified MPLS local label is recursive and is not yet supported. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this error by using the show commands for the specified local_label and modify the config using LDP filters to remove recursive labels. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-mpls_unsupported_feature </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Unsupported feature. Failed to program. [chars] in software or hardware\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The feature is not yet supported. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this unsupported feature from the release documents and remove the command from the interface config mode </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-pbr_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Platform unicast routing pbr module encountered [chars] error in FED\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in platform pbr code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this error by using the show platform ipunicast policy commands </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_L3_ERRMSG-3-wccp_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Platform unicast routing wccp module encountered [chars] error in FED\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in platform wccp code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about this error by using the show platform ipunicast wccp commands. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PM-3-FRU_SWITCH_TIMEOUT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Transeiver update timed out. Remove and re-insert all FRUs in this switch to recover.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An FRU update event took too long to process on this switch. The FRUs on this switch may not be recoginized or function properly after this. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Remove and re-insert all FRUs on this switch. The system should recognize and process them correctly after that. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PM-3-FRU_TIMEOUT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> FRU module [dec] bringup timed out. Remove and re-insert it to recover.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The given FRU module in the switch in question could not be recognized because it took too long do so. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Remove and re-insert the specified FRU module. The system should recognize it correctly after that. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PM-3-FRU_TRANSCEIVER_TIMEOUT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Transceiver event handling for interface [chars] timed out. Remove and re-insert the FRU module containing this interface to recover.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Than handling onf a transceiver event took too long for the given interface. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Remove and re-insert the FRU module containing this interface. The system should recover from this failure condition after that. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PM-3-HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Port Manager error -[chars] hardware update failed.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in Port Manager code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PM-3-RESRC_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Port Manager error -[chars] resource access failed.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in Port Manager code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PTP_ERRMSG-3-ATTACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to run PTP [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurs when running PTP. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using show mgmt-infra trace messages fed-ptp-config-error switch number command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PTP_ERRMSG-3-DETACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to run PTP [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Error occurs when running PTP. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using show mgmt-infra trace messages fed-ptp-config-error switch number command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PTP_ERRMSG-6-NOTALLOWED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is not allowed.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not allowed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please try to modify your configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PTP_ERRMSG-6-UNSUPPORTED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is unsupported\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not supported. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please do not use the current configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_PUNJECT-6-PKT_CAPTURE_FULL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Punject pkt capture buffer is full. Use show command to display the punted packets.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> All the available punt capture buffers have been written with punted packets. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is needed. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-AFD_POLICER_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in programming the Approximate Fair Dropping policer. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-AFD_QUEUE_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to program AFD [chars] virtual queue for [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in programming the Approximate Fair Dropping virtual queue. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-LABEL_2_QUEUE_MAPPING_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars]: code [dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in programming label to queue map. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-NETFLOW_TABLE_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to program netflow entries for policy-map [chars] for client mac:[chars] iifid:0x%llx. code:[dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in programming netflow table. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-POLICER_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars]: code [dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in programming the policer. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-POLICER_MAP_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars]: code [dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in programming the policer map. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-QUEUE_BUFFER_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars]: code [dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred when programming the queue buffer. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support priveleged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-QUEUE_SCHEDULER_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars]: code [dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred when programming the queue scheduler. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-TABLEMAP_EGRESS_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars]: code [dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred when programming egress table-map to hardware. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-TABLEMAP_INGRESS_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars]: code [dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred when programming ingress table-map to hardware. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-3-TABLEMAP_INIT_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to initialize [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred during table-map initialization. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-APPLICATION_ID_OVERFLOW </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate application ID for policy-map [chars] on [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The application IDs are exhausted. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Reduce the number of applications to make application ID available. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-CONFIGURE_PORT_TYPE_HW_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to configure port [chars] as [chars] port in hardare. rc:[dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The port could not be configured in hardware </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Try to shutdown the port and then unshut the port </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-LABEL_2_QUEUE_MAPPING_OVERFLOW </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars]. No more queue-maps are available.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The system supports up to 8 queue-maps. This limit has been reached. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unconfigure some of the queuing policies to make the resource available. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-NETFLOW_TABLE_OVERFLOW </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to program netflow entries for policy-map [chars] for client mac:[chars] iifid:0x%llx. No netflow resource is available.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The netflow resources are exhausted. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unconfigure features to make the netflow resource available. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-OUTPUT_ACS_CLIENT_POLICY_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Unsupported output client policy([chars]).\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Unsupported policy. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unsupported client output policy </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-OUTPUT_CLIENT_POLICY_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Unsupported output client policy([chars]) - range operators.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Unsupported policy. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Range operators are not supported in client output policy </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-POLICER_MAP_TABLE_OVERFLOW </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars]. No more policer map tables are available.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The ASIC supports up to 64 policer map tables. This limit has been reached. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unconfigure some policer maps to make the resource available. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-POLICER_OVERFLOW </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] for [chars]. No policer resource is available.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The policer resource limit has been reached. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unconfigure some policers to make the resource available. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-STACK_BUFFER_CONFIG_MGIG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Detected stack-buffer disable ([dec]), which is not a supported configuration for mGig platforms. Change to 'stack-buffer enable' configuration.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The stack-buffer configuration for an mGig switch should always remain as enabled. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Change the configuration back as stack-buffer enable </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-TABLEMAP_OVERFLOW </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to attach [chars]. No more table-maps are available.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The system supports up to 16 table-maps per direction. This limit has been reached. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unconfigure some of the table-maps to make the resource available. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_QOS_ERRMSG-4-TCAM_OVERFLOW </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to program TCAM for policy-map [chars] on [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The TCAM resources are exhausted. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unconfigure features to make TCAM resources available. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_ROT-4-VALIDATION_FAILURE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The RoT Validation for ASIC [dec] has failed because [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The NPU RoT validation has failed. This could be due to a hardware or software defect. This is a critical error. NPU will stop forwarding traffic </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SPAN_ERRMSG-3-UNSUPPORTED_CONFIG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> SPAN configuration for source is not supported [chars] \n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A failure occurred in platform SPAN Source prgm </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> This failure occurs with SPAN Src (port, Vlan) is part of a different SPAN session and is being reprogrammed again </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SPAN_ERRMSG-3-fspan_hw_update_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Platform FSPAN encountered an error in FED - [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in platform FSPAN code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect output of hardware tables/registers related to FSPAN and details of related ASIC resource handles. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SPAN_ERRMSG-3-sess_rc </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Platform SPAN encountered an update error in FED - [chars], session [dec], return code [dec].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in platform update SPAN code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect the output of debug platform monitor-fed while configuring SPAN or FSPAN. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SPAN_ERRMSG-3-span_gen_hw_update_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Platform SPAN encountered an error in FED - [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in platform SPAN code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect the output of debug platform monitor-fed command while configuring SPAN or FSPAN. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SPAN_ERRMSG-3-span_hw_update_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Platform SPAN encountered an error in FED - [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in platform SPAN code. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect output of hardware tables and registers related to SPAN and details of related ASIC resource handles. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SPAN_ERRMSG-3-span_stp_status_update_err </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Platform SPAN encountered an error in FED - [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurred in platform SPAN code for STP state updates in ASIC. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect output of hardware tables and registers related to FSPAN and details of related ASIC resource handles. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SRVO_ERRMSG-3-ATTACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to run SRVO [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurs when running SRVO. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using show mgmt-infra trace messages fed-srvo-config-error switch number command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SRVO_ERRMSG-3-DETACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to run SRVO [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Error occurs when running SRVO. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using show mgmt-infra trace messages fed-srvo-config-error switch number command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SRVO_ERRMSG-6-NOTALLOWED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is not allowed.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not allowed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please try to modify your configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_SRVO_ERRMSG-6-UNSUPPORTED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is unsupported\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not supported. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please do not use the current configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_STATS-6-MEMORY_PARITY_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Detected memory parity errors on ASIC INST([dec])\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Memory parity errors reached threshold. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> If this message occurs, customer needs to reach out to TAC. TAC will collect and review the output of \'show logging onboard switch active message detail\'. If there are so many single-parity memory errors (&gt;=1000 in 24 hours). TAC may ask the switch to be reloaded or RMAed. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_STP_ERRMSG-3-MAX_INSTANCES </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The maximum number of STP instances has been reached:[dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The maximum number of STP instances that can be programmed has been reached. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Delete or resolve loops manually for the vlans created further. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_VLAN_TRANSLATE_ERRMSG-3-ATTACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to run VLAN_TRANSLATE [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An error occurs when running VLAN_TRANSLATE. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using show mgmt-infra trace messages fed-vlan_translate-config-error switch number command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_VLAN_TRANSLATE_ERRMSG-3-DETACHERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to run VLAN_TRANSLATE [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Error occurs when running VLAN_TRANSLATE. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out more about the error by using show mgmt-infra trace messages fed-vlan_translate-config-error switch number command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_VLAN_TRANSLATE_ERRMSG-6-NOTALLOWED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is not allowed.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not allowed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please try to modify your configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_VLAN_TRANSLATE_ERRMSG-6-UNSUPPORTED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is unsupported\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The requested configuration is not supported. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please do not use the current configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-BO_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [dec] [dec] break out failed </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> New BO command might have entered too fast or Deactivation taking time to clean feature objects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Likely IOS and FED might be out of state, reload to use BO ports </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-BO_NOT_FINISHED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [dec] [dec] previous breakout command not yet finished, wait for completion message </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> New BO command might have entered too fast or Deactivation taking time to clean feature objects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Likely IOS and FED might be out of state, reload to use BO ports </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-BO_SUCCESSFUL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [dec] [dec] break out successful </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> New BO command might have entered too fast or Deactivation taking time to clean feature objects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Likely IOS and FED might be out of state, reload to use BO ports </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-CABLE_AUTH_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> *** Stack cable authentication failed for cable inserted on stack port [dec] on switch [dec] *** </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Stack Cable authentication failed on the switch </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Fed would have crashed, remove the stack cable inserted in the mentioned port and cross check </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-CABLE_AUTH_FAILED_RELOAD </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Reloading chassis because cable auth failed on stack_port [dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Stack Cable authentication failed on the switch </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Fed would have crashed, remove the stack cable inserted in the mentioned port and cross check </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-NO_BO_SUCCESSFUL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [dec] [dec] no break out successful </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> New BO command might have entered too fast or Deactivation taking time to clean feature objects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Likely IOS and FED might be out of state, reload to use BO ports </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-NO_PG_SUCCESSFUL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Slot [dec] Portgroup [dec] No Portgroup Successful </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> New PG command might have entered too fast or Deactivation taking time to clean feature objects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Likely IOS and FED might be out of state, reload to use PG ports </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-PG_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Slot [dec] Portgroup [dec] Failed </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> New PG command might have entered too fast or Deactivation taking time to clean feature objects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Likely IOS and FED might be out of state, reload to use PG ports </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-PG_SUCCESSFUL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Slot [dec] Portgroup [dec] Successful </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> New PG command might have entered too fast or Deactivation taking time to clean feature objects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Likely IOS and FED might be out of state, reload to use PG ports </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FED_XCVR_MSG-3-SPEED_MISMATCH </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] are operating in different speeds, Ports in each port-group should operate in same speed. Please make sure that both the ports operate in same speed. Alternatively, Configure hw-module slot &lt;&gt; port-group &lt;&gt; select &lt;speed&gt;, shut and no shut preferred interface to use specific port in the port-group. This config is not supported if any of the ports in port-group is inserted with dual-rate optics. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The ports in port-group should be of the same speed for all ports to function </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enter hw-module slot &lt;&gt; port-group &lt;&gt; select &lt;speed&gt;,followed by\n shut and no shut of interface to use a specific port. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FILTER-3-EWLC_APFILTER_REGEX_CREATE_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> APFilter regular expression error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Recreate regular expression correctly </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FILTER-3-EWLC_GEN_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> General Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FILTER-4-EWLC_APFILTER_PRIORITY_UPDATE_WARN </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Warning: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> APfilter priorities are overridden, old filter will be invalid </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FILTER_BINARY_NOTIFICATION-5-MERGE_COMPLETED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Merged logs generation completed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Notification to user that merged logs are generated </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Go to bootflash and view the merged logs </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FIRMWARE-5-INSTALL_STATUS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Firmware install stage: [chars], install-id: [chars], message: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated during firmware installation which goes through multiple steps </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> lte-fw </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FIRMWARE-6-INSTALL_STATUS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Firmware install stage: [chars], install-id: [chars], message: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated during firmware installation which goes through multiple steps </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> lte-fw </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FLASH_CHECK-3-DISK_QUOTA </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] quota exceeded [free space is [dec] kB] - [recommended free space is [dec] kB] - Please clean up files on [chars]. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The remaining free space on the disk is below the recommended threshold of at least 30 percent of the installed disk device space. This limits the system from core files necessary to root cause critical system faults. The disk device is bootflash or harddisk. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please remove unneeded files from the disk device. Any core files under the core directory should be reported and then deleted. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FLASH_CHECK-3-FLASH_ISSUE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Detected Flash issues. Please issue the [chars] command at your earliest convenience. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> eUSB failure is detected, flash partitions may be inaccessible. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please issue the cli command shown in the error message. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FLASH_CHECK-3-FLASH_RECOVERY </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Detected Flash issues. Proceeding with [chars] soft-error recovery. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> eUSB failure is detected, which prevents access of flash partitions. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FLASH_CHECK-3-RESET_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Flash recovery failed. Please issue the reload slot &lt;#&gt; command at your earliest convenience. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An attempted flash recovery has failed. Switch needs to be manually reloaded </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FLASH_CHECK-3-RESET_SUCCESS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Flash recovery was successful. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An attempted flash recovery was successful. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-3-CRYPTO_DEVICE_REQUEST_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Crypto-device is busy processing last request. This request will be discarded </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Crypto-device is still processing previous reload reqeust or still processing crypto feature packets. New request will not be applied </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-3-CRYPTO_LICENSE_THPUT_MAX_APPROACHED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Average crypto throughput rate approached the licensed crypto bandwidth of [dec] bps during [dec] sampling periods in the last 24 hours, sampling period is [dec] seconds </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> To monitor crypto throughput and, to generate notification/warning if the average throuput utilization over a longer time are approaching or exceeding the cypro licensed bandwidth </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-3-CRYPTO_LICENSE_THPUT_THRESHOLD_EXCEED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Average crypto throughput rate exceeded [dec] percent of licensed crypto bandwidth of [dec] bps during [dec] sampling periods in the last 24 hours, sampling period is [dec] seconds </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> To monitor crypto throughput and, to generate notification/warning if the average throuput utilization over a longer time are approaching or exceeding the cypro licensed bandwidth </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-3-LICENSE_THPUT_INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Invalid throughput [dec]kbps </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The throughput value is invalid. The forwarding engine will not operate at the throughput value. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_DDTS_TAC_DETAILS </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-3-REFGRP_ENTRY_LIMIT_EXCEED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Reflexive group [chars]([dec]) exceeded limitation of [dec] entries. Reflexive functionality is not supported for this ACE, please remove it. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A software limitation has been exceeded. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-3-REFGRP_LIMIT_EXCEED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Number of reflexive group exceeded limitation of [dec]. Reflexive functionality is not supported for this ACE, please remove it. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A software limitation has been exceeded. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-3-REF_ACE_IDX_LIMIT_EXCEED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Reflexive group [chars]([dec]) ACE index([dec]) exceeded limitation of [dec]. Reflexive functionality is not supported for this ACE, please remove it. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A software limitation has been exceeded. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-3-REF_ACL_IDX_LIMIT_EXCEED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Reflexive group [chars]([dec]) ACL index([dec]) exceeded limitation of [dec]. Reflexive functionality is not supported for this ACL, please remove it. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A software limitation has been exceeded. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-CRYPTO_DEVICE_NOT_PRESENT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Hardware crypto-device is not present. Request aborted </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware crypto-device is not present on the system. User request doesn't apply or be executed. This may not be an error. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-CRYPTO_DEVICE_REQUEST_COMPLETE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Crypto-device is ready to process packets </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Crypto-device is load with new core based on user request. Now it is ready to process packets </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-FMANACLLOGMISSMSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> access-list logging datapath rate-limited or missed [dec] packet[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Some packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPACCESSLOGDP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> list [chars] [chars] [chars] [chars][chars] [chars]-&gt; [chars] ([dec]/[dec]), [dec] packet[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPACCESSLOGNP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> list [chars] [chars] [dec] [chars][chars] [chars]-&gt; [chars], [dec] packet[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPACCESSLOGP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> list [chars] [chars] [chars] [chars][chars]([dec]) [chars]-&gt; [chars]([dec]), [dec] packet[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPACCESSLOGSGDP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' dest-ip='[chars]' type='[dec]' code='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPACCESSLOGSGNP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[dec]' src-ip='[chars]' dest-ip='[chars]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPACCESSLOGSGP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' src-port='[dec]' dest-ip='[chars]' dest-port='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPV6ACCESSLOGDP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> list [chars] [chars] [chars] [chars][chars] [chars]-&gt; [chars] ([dec]/[dec]), [dec] packet[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-acl </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPV6ACCESSLOGNP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> list [chars] [chars] [dec] [chars][chars] [chars]-&gt; [chars], [dec] packet[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-acl </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPV6ACCESSLOGP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> list [chars] [chars] [chars] [chars][chars]([dec]) [chars]-&gt; [chars]([dec]), [dec] packet[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-acl </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPV6ACCESSLOGSGDP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' dest-ip='[chars]' type='[dec]' code='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPV6ACCESSLOGSGNP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[dec]' src-ip='[chars]' dest-ip='[chars]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANFP-6-IPV6ACCESSLOGSGP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ingress_interface='[chars]' sgacl_name='[chars]' action='[chars]' protocol='[chars]' src-ip='[chars]' src-port='[dec]' dest-ip='[chars]' dest-port='[dec]' sgt='[dec]' dgt='[dec]' logging_interval_hits='[dec]' </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A packet matching the log criteria for the given access list was detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANRP-3-OBJ_DWNLD_TO_FP_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] download to FP failed </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An object has failed to download to the forwarding processor (FP) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the process logs to identify the cause for object download failure </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANRP-3-PEER_IPC_RESET </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IPC to [chars] has been reset after previous stuck </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IPC to a peer has been reset after previous stuck </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> check if there is any functional impact after recovery </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANRP-3-PEER_IPC_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IPC to [chars] has returned to normal after previous stuck </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IPC to a peer is back to normal after previous stuck </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> check if there is any functional impact after recovery </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANRP-3-PEER_IPC_STUCK </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IPC to [chars] is stuck for more than [dec] seconds </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IPC to a peer is stuck, resulting no new messages sent over for a long time </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Run show platform peer object-manager rp [active|standby] to confirm that no new messages are sent over the Config IPC </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMANRP-4-INVALID_CCE_POSITION </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Invalid position '[dec]' prevented [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A messaging error has occurred during service-policy modification and the configuration could not be downloaded properly </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_DDTS_TAC_DETAILS </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMAN_CAPWAP-3-AP_TUNNEL_CLEANUP_PENDING </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> AP CAPWAP tunnel cleanup is incomplete. [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> CAPWAP tunnel delete acknowledgement is not yet received from FMAN FP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMAN_CAPWAP-3-AP_TUNNEL_EXIST </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> AP CAPWAP tunnel plumb failure. [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> CAPWAP tunnel plumb failure due to MAC or IFID conflict </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMAN_IPSEC_NGWC-3-IPSEC_ANTI_REPLAY_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IPSEC (flow id [dec]) receives anti-replay error. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> traffic being received is not within the IPSec anti-replay window. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the size of anti-replay window configured. Adjust to maximum 256-bits if needed </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMAN_IPSEC_NGWC-3-IPSEC_CONFIG_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IPSEC fail to configure because [chars]. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The IPSEC configuration has failed. This could be due to a hardware/software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information. Reconfigure IPSEC </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMAN_IPSEC_NGWC-3-IPSEC_INIT_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IPSEC fail to initialize because [chars]. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The IPSEC initialization has failed. This could be due to a hardware/software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information. Reboot the system if IPSEC needs to be configured </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMAN_IPSEC_NGWC-3-IPSEC_TTL_NOT_SUPPORT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IPSEC tunnel ttl configuration ignored because [chars]. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The IPSEC configuration for tunnel ttl value is not supported and therefore has been ignored. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> remove tunnel ttl configuration as it is not supported. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMAN_IPSEC_NGWC-3-IPSEC_TUNNEL_CONFIG_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] SADB [dec] IF_ID [dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The IPSEC configuration has failed. This could be due to a hardware/software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information. Reconfigure IPSEC </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP-3-DP_NOMEM </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> DP not enough memory. [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An object download to DP failed because the memory of DP is not enough. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Run show platform resource to see the memory usage </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP-3-INTERFACE_OBJECT_NOT_FOUND </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Interface object lookup by [chars] not found for interface [dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The desired interface object was not found. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the interface state in the operating system, route processor (RP) and forwarding processor (FP) forwarding manager logs. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP-3-OBJ_ACK_FROM_DP_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> AOM ack of objects to Data Plane is back to normal </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An object ack from lower layer to FMAN-FP has finished after a temporary stuck. It can be caused by incomplete configuration or software defects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> check if there is any functional impact after recovery </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP-3-OBJ_ACK_FROM_DP_STUCK </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> AOM ack download to Data Plane is stuck for more than [dec] seconds [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An object ack from lower layer to FMAN-FP has taken long time. It can be caused by incomplete configuration or software defects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Run show platform software object-manager fp [active|standby] [pending-ack-update| pending-ack-batch|pending-ack-commands] sorted &lt;min_pending_time&gt; to see the sorted list of update/ batch/command in pending state for more than the min_pending_time. For incomplete configuration, use show platform platform software object fp [active|standby] resolve to see if there is any resolve object </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP-3-OBJ_DWNLD_TO_DP_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] download to DP failed </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An object has failed to download to the data plane </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the list of error objects in the forwarding processor (FP) forwarding manager asynchronous object logs. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP-3-OBJ_DWNLD_TO_DP_RESUME </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> AOM download of objects to Data Plane is back to normal </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An object download from FMAN-FP to lower layer has finished after a temporary stuck. It can be caused by incomplete configuration or software defects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> check if there is any functional impact after recovery </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP-3-OBJ_DWNLD_TO_DP_STUCK </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> AOM download to Data Plane is stuck for more than [dec] seconds [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An object download from FMAN-FP to lower layer has taken long time. It can be caused by incomplete configuration or software defects </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Run show platform software object-manager fp [active|standby] [pending-issue-update|pending-issue-batch] sorted &lt;min_pending_time&gt; to see the sorted list of update/batch/ command in pending state for more than the min_pending_time. For incomplete configuration, use show platform platform software object fp [active|standby] resolve to see if there is any resolve object </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_ACL-3-ACL_LIMIT_EXCEEDED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ACL [chars] exceeded limitation of [dec] ACEs per ACL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A software limitation has been exceeded. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Reduce the access control list (ACL) configuration. A reboot of the forwarding processor (FP) is recommended. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_ACL-3-ACL_MODIFY_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ACL:[chars] modification through object group edit failed </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Object-group used in the ACL was modified. Those changes could not be accommodated in the ACL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr1k-acl </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Fix the object-group changes. Delete ACL and reconfigure it </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_ACL-3-ACL_OBJECT_DOWNLOAD </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars][chars] fail to download because [chars]. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The access control list (ACL) object has failed to download. This could be due to a hardware or software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information on the relevant object download states. Remove the ACL attachment to the interface or delete the ACL. Reboot the forwarding processor (FP). </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_ACL-3-ACL_PROTOCOL_CHECK </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ACL [chars] protocol does not match what was previously configured </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The error occurs for one of two reasons. An access control list (ACL) reference was made to an ACL of a different protocol; or an ACL was added or edited when there were similarly named ACL references of a different protocol </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Remove the conflicting ACL or the conflicting ACL references. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_ACL-3-OGACL_BINCODE_CHECK </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] OGACL request failed in bincode check: required bits ([dec]) max available bits ([dec]). </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The scaled OGACL failed to download due to the hardware or software resource limitation on bincode. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr1k-acl </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information on the relevant object download states. Remove the OGACL configuration and binding, reduce the scaling and reconfigure it </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_ACL-3-OGACL_PD_RESOURCE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] OGACL runs out of PD resources. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The scaled OGACL failed to download due to PD hardware or software resource limitation. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr1k-acl </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information on the relevant object download states. Remove the OGACL configuration and binding, reduce the scaling and reconfigure it </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_ACL-3-SGACL_OBJECT_DOWNLOAD </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> SGACL Cell ([dec] [dec]) policy [chars] fail to download because [chars]. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The SGACL policy has failed to download. This could be due to a hardware or software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information on the relevant object download states. Remove the SGACL policy for that cell, correct the error and reconfigure it </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_CCK-4-INCONSISTENCY_FOUND </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Consistency Checker(CCK) detected inconsistency for [chars]. Check 'show consistency-checker run-id [dec] detail'. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> CCK has detected the inconsistency between the IOSD and fmanFP tables. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out the entry using the show consistency-checker &lt;&gt; command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_CXSC-3-CXSC_DEINITIALIZATION </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] Returned: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The CXSC DEINITIALIZATION has FAILED. This could be due to a hardware or software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-cxsc </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_CXSC-3-CXSC_DOMAIN_CONFIG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] Returned: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The CXSC DOMAIN CONFIG DOWNLOAD has FAILED. This could be due to a hardware or software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-cxsc </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_CXSC-3-CXSC_INITIALIZATION </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] Returned: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The CXSC INITIALIZATION has FAILED. This could be due to a hardware or software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-cxsc </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check memory usage and router configuration and try to re-activate virtual service again. If it shows the same results then please contact TAC. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_CXSC-3-CXSC_POLICY_DOWNLOAD </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] Returned: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The CXSC POLICY DOWNLOAD has FAILED. This could be due to a hardware or software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-cxsc </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check memory usage and router configuration and try to re-activate virtual service again. If it shows same results then please contact TAC. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_CXSC-6-CXSC_POLICY_DOWNLOAD_SUCCESS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> New policy version: [dec] has now been installed and is active </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The CXSC POLICY DOWNLOAD of the numbered version has succeeded. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-cxsc </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> This an informational message only, no action is required. Note that policy version is not monotonically increasing so there is nothing to be concerned about if the current installed policy version is less than the previous installed policy version. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_QOS-4-QOS_WITHOUT_UPDATING </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Warning, Qos download AOM without updating [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> qos download aom wihtout updating action. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_QOS-6-QOS_STATS_PROGRESS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> statistics are progressing </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> QoS statistics are now progressing normally. This is an informational message. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_QOS-6-QOS_STATS_STALLED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> statistics stalled </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> QoS statistics are temporarily stalled. This is an informational message. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_URPF-3-LIST_DOWNLOAD </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Unicast RPF list [chars] for list [dec] fail to download because [chars]. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The unicast reverse path forwarding (URPF) list failed to download. This can be caused by a hardware or software resource limitation or software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information on the relevant download states. Reboot the forwarding processor (FP). </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMFP_URPF-3-OBJECT_DOWNLOAD </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Unicast RPF [chars] on inteface [chars] fail to download because [chars]. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The unicast reverse path forwarding (URPF) operation failed to download. This can be caused by a hardware or software resource limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information on the relevant download states. Remove the uRPF feature enabled on any interface. Reboot the forwarding processor (FP). </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FMRP_CCK-4-INCONSISTENCY_FOUND </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Consistency Checker(CCK) detected inconsistency for [chars]. Check 'show consistency-checker run-id [dec] detail'. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> CCK has detected the inconsistency between the IOSD and fmanRP tables. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Find out the entry using the show consistency-checker &lt;&gt; command </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FPGA_DRV-1-CRC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> SEU [chars] errors are detected in FPGA, [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> SEU errors are detected in FPGA </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FPMD-3-ACL_PROGRAM_FAILURE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to associate access-list: [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when FPMD cannot program or partially programmed given access-list in datapath. This error can result into packets flowing through the network without applying access-list as intended </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> vip-cedge-policy </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check btrace for any error logs, collect tech-support and share with Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FPMD-3-MAX_FILTER_EXCEEDED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Filter count exceeded Max ([dec]) filters per class for class_id [dec] at filter_id [dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when maximum number of filters have already been reached for given class </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> vip-cedge-policy </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Remove any unused filters from given class </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FPMD-3-POLICY_PROGRAM_FAILURE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to associate data-policy [chars] with vpn-list: [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when FPMD cannot program or partially programmed given data-policy in datapath. This error can result into packets flowing through the network without applying data-policy as intended </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> vip-cedge-policy </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check btrace for any error logs, collect tech-support and share with Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FPMD-3-SDWAN_POLICE_CONFIRM_BURST_INCREASED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> SDWAN Policer [chars] Conform burst [dec] increased to [dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when FPMD receives policer config but configured policer burst is less than the default burst tolerance for the CIR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> vip-cedge-policy </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check btrace for any error logs, collect tech-support and share with Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FPMD-5-FLOW_LOG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> FLOW LOG device-vpn: [dec] tenant-vpn: [dec] src: [chars]/[dec] dst: [chars]/[dec] proto: [dec] tos: [dec] direction: [chars], policy: [chars], sequence: [dec], Result: [chars] Pkt count: [dec] bytes: [dec] Ingress-Intf: [chars] Egress-intf: [chars] Tenant: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated for every flow that matches data-policy, app-route policy and/or access-list. The log contains information about L3 and L4 headers, along with direction and result </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> vip-cedge-policy </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FPMD-6-ACL_PROGRAM_SUCCESS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Successfully associated access-list: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This informative log is generated when access-list is successfully programmed in data-path </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> vip-cedge-policy </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FQDN_MESSAGE-3-FQDN_FLEX_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> ewlc fqdn flex push error message. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FQDN_MESSAGE-3-FQDN_LISTNAME_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> ewlc FQDN url list name error message. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FQDN_MESSAGE-3-FQDN_LOCAL_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> ewlc fqdn urllist forwarding push error message. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FTMD-3-FIB_ROUTE_ADD_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Route addition failed for prefix [chars], reason [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is typically generated when the system is under stress and a route cannot be added in forwarding base </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> cedge-forwarding </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please collect tech-support and share with Cisco TAC, a support ticket should be created to debug this </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FTMD-3-TLOC_ADD_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> TLOC ([chars]/[chars]) addition failed, reason: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is typically generated when the system is under stress and a TLOC cannot be added in forwarding base or encountered a error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> cedge-forwarding </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> FTMD-5-FLOW_LOG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> **HSL-LOGGING IMPLICIT-ACL** vpn: [dec], source: [chars]/[dec], destination: [chars]/[dec], protocol: [dec], tos: [dec], reason: [chars], packets: [dec], bytes: [dec], ingress-interface: [chars], egress-interface: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated whenever a packet hits implicit ACL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> cedge-forwarding </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GEOFENCE-2-DEVICE_LOCATION_INSIDE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Device location is inside Geofencing range ([chars]) current latitude/longitude: (%.6f, %.6f) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when the device location is inside configured Geofencing range </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> geo-fencing </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GEOFENCE-2-DEVICE_LOCATION_LOST </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Device location unavailable [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when the device location is lost </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> geo-fencing </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GEOFENCE-2-DEVICE_LOCATION_OUTSIDE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Device location is outside Geofencing range, current latitude/longitude: (%.6f, %.6f) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when the device location is outside configured Geofencing range </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> geo-fencing </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GEOFENCE-5-DEVICE_LOCATION_UPDATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Device location changed by more than 20 meters from last report, current latitude/longitude: (%.6f, %.6f) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when the device moves within configured Geofencing range </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> geo-fencing </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GEOFENCE-6-DEVICE_TRACKING_STARTED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Device Tracking started in Geofencing mode ([chars]) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when device tracking is started </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> geo-fencing </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GEOFENCE-6-DEVICE_TRACKING_STOPPED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Device Tracking stopped in Geofencing mode </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This syslog is generated when device tracking is stopped while Geofencing feature is enabled </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> geo-fencing </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GEO_CLOUDM-5-EXEC_CLI </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Exec CLI : [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Information message related to exec cli </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> ewlc-ap-location </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GEO_CLOUDM-5-RANGING_REQUEST </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Ranging request : [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Information message related to ranging request </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> ewlc-ap-location </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GNMIB-5-SRV_ADMIN_SCN </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Component [ [chars] ] administrative state: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> gnmib component administrative state </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-gnmi-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GNMIB-5-SRV_OPER_SCN </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Component [ [chars] ] operational status: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> gnmib component operational status </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-gnmi-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GNMIB-6-GRPC_CON_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Received gRPC [chars] from [chars] for RPC [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> gRPC Connection state logging </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-gnmi-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GNMIB-6-GRPC_CON_STATE_AUTH </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Received gRPC [chars] from [chars] for RPC [chars] for user [chars] group [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> gRPC Connection state logging with user authentication </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-gnmi-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GNMIB-6-GRPC_TUNN_SESS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Received gRPC Tunnel session request from [chars] for Target Type [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> gRPC Tunnel state logging </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-gnxi-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GNMIB-6-GRPC_TUNN_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Connected to gRPC Destination [chars] ([chars]) with Targets[[chars]] using [chars]:[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> gRPC Tunnel state logging </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-gnxi-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> GREENLIB-6-SUBSCRIPTION_RECORD_NOT_SENT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Subscription record from DB [[chars]] and table [[chars]] was not sent out due to [[chars]] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A record for an On-change Subscription was not sent due to the size of the record being too large </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HFSLIB-3-HFSINOFAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Inotify failed to initialize : [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This error occurs when the inotify sub-system is misbehaving </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HFSLIB-3-HFSINOWATCH </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Inotify failed to add a watch: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This error occurs when the inotify sub-system is misbehaving </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HFSLIB-3-HFSOPEN </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Problem accessing the udev generated file: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> No explanation. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HL_CORE-3-MAY_DEFER_WRAPPER_RESCHEDULE_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to (re)schedule CPUHOG protected loop. Operation will be aborted. Please check the logs for more details. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hyperlocation was interrupted while trying to defer a looping operation and can not continue. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HL_MGR-3-CMX_IPV6_IN_FABRIC </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> CMX [chars] connected over IPv6 which is not currently supported for Hyperlocation in Fabric mode. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Currently the Fabric mode only operates over IPv4. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please connect the CMX over IPv4, or change the mode to flex/local. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HL_MGR-3-NEXTHOP_OUTPUT_INTERFACE_NOT_SVI </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> CMX [chars] is reachable through a routed port with MAC address %pM. This deployment configuration is not supported for Hyperlocation </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> CMX should be reachable via a SVI (VLAN) interface for traffic forwarding to be operational </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please rejoin CMX. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HMAN-2-INITIALIZATION_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Host Manager initialization failed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Initialization of the host manager failed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-hostmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Review Host Manager logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HMAN-3-CONSOLE_SETUP_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to setup console service. It should be enabled on [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Setup of a console service failed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-hostmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the host manager launch parameters and correct as required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HMAN-3-HOSTNAME_SET_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to set hostname: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The host manager received notification that the system hostname has been set. The host manager failed to pass this value to the ASR kernel. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-hostmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Repeat the process to configure the hostname. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HMAN-3-VRF_API_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars], vrf ([chars]) - ret ([dec]) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The host manager has received notification that the VRF information needs to be modified. The host manager failed to perform the operation due to the error indicated in the log. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-hostmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HMAN_CPU-3-PAGE_FAULT_HIGH </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> CPU Usage due to Memory Pressure exceeds threshold on [chars]. Below are the top 5 memory consuming processes: [chars] (PID=[dec]; RSS=[dec] KB), [chars] (PID=[dec]; RSS=[dec] KB), [chars] (PID=[dec]; RSS=[dec] KB), [chars] (PID=[dec]; RSS=[dec] KB), [chars] (PID=[dec]; RSS=[dec] KB) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> When CPU usage due to Major Page Fault exceeds a pre-defined threshold for a CPU core, this error message is emitted. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-hostmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is needed if system continues to perform as expected. If sytem performance deteriorate (and eventually, system reloads due to unspecified reason) around the time when this message is observed, open a case with the Technical Assistance Center via the following Internet link, or contact your Cisco technical support representative: http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HW_IDPROM_ENVMON-2-ACT2_UDI_DATA_INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The act2 udi secure area format mismatch with unsecure area </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This Router may not have been manufactured by Cisco or with Cisco's authorization. This product may contain software that was copied in violation of Cisco's license terms. If your use of this product is the cause of a support issue, Cisco may deny operation of the product, support under your warranty or under a Cisco technical support program such as Smartnet. Please contact Cisco's Technical Assistance Center for more information. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HW_IDPROM_ENVMON-3-HW_IDPROM_CHECKSUM_INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The idprom contains an invalid checksum in a sensor entry. Expected: %x, calculated: %x </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HW_IDPROM_ENVMON-3-HW_IDPROM_FIELD_INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The idprom contains an invalid environmental monitoring field. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HW_IDPROM_ENVMON-3-PS_IDPROM_INVALID_PID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] in slot PFU[dec] has INVALID PID [chars] and it needs to be replaced immediately </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The PID read from the PEM IDPROM is not supported in this hardware configuration. It will be allowed to continue but immediate replacement is required </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HW_PFU-3-PFU_IDPROM_CORRUPT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The PEM/FM idprom could be read, but is corrupt in slot P[dec] The system will run without environmental monitoring for this component </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HW_PFU-3-PFU_IDPROM_INVALID_PID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The PEM/FM idprom has invalid PID in slot PFU[dec] The system will run without environmental monitoring for this component </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The idprom contains PID information required in order to properly operate the environmental monitoring subsystems. The idprom PID is invalid , therefore no monitoring will take place. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HW_PFU-3-PFU_IDPROM_READ_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Could not read the PEM/FM idprom in slot P[dec].The system will run without environmental monitoring for this component </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> HW_PFU-3-PFU_UNSUPPORTED_PID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The PEM/FM in slot P[dec] is not supported. The system will run without environmental monitoring for this component </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The PEM/FM inserted in not supported by this platform. Replace with a supported module. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-system-rsp3 </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ID_MANAGER-3-ID_MANAGER_INTERNAL_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Internal erorr occurred: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Internal Error occured with ID Manager </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ID_MANAGER-3-INVALID_ID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> bad id in [chars] (id: 0x%08X) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An ID Manager error occurred </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ID_MANAGER-3-INVALID_ID_TABLE_SIZE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> bad new ID table size </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A bad new table request to ID Manager occurred </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IFM-3-RSRC_L3_LE_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Interface [chars] creation failed due to L3 Interface hardware resource exhaustion </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware resource for L3 Interface exhausted and the requested interface will not be created. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect output of show platform hardware fed switch &lt;switch number&gt; fwd-asic resource utilization command. Check if RSC_L3IF_LE has exhausted. If yes, free up any unused L3 Interfaces by doing no interface &lt;interface&gt; and retry creating the failed interface. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ILET-2-AUTHENTICATION_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The system integrity check has failed during the boot-up sequence. Please contact Cisco's Technical Assistance Center for more information. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Trusted Anchor module detected an invalid SUDI. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-hostmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please contact Cisco's Technical Assistance Center for more information </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-0-UIPEER_CREATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to create user interface peer. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The system failed to create a user interface peer. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-ACTIVATION_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] '[chars]' [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The activation state of the named virtualization service has changed as notified by IOx-manager. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-ALLOC_VIRT_INST_RCS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A memory allocation request failed to allocate a data structure required to activate the virtualization service. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-CPUSHARES_LIMIT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service machine definition file is requesting more CPU shares than the system has available for virtualization services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Deactivate any other virtualization services to free up CPU share resources and activate this virtualization service. If that does not address the problem, then enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-DEACT_FOR_ISSU </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] Max ([dec]s) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> None. Allow the ISSU to continue and the VMs will restart when the ISSU completes; or cancel the ISSU and IOx-manager will automatically restart the VMs. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-DISK_IMAGE_PATH </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-FIND_VIRT_INST_ENTRY </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to find virtualization service with id [dec] in the IOx-manager list </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service with the ID named could not be located in the IOx-manager list. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-GENERAL_FAILURE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named virtualization service has triggered the log. Please interpret the log in the context of the virtualization services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-GUESTSHELL_ENABLED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The guest shell has been enabled. The command '[chars]' may be used to access it, '[chars] destroy' to remove it. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Informs the user that the guest shell virtualization service has been enabled (which is done by default). </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> The user may use or remove the guest shell with the commands specified. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-HA_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IOx-manager tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-HA_SWITCHOVER_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IOx-manager HA switchover state related messages for a virtual-service whilst it is being recovered on newly active RP after a HA switchover. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-HA_SYNC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] '[chars]' [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The ha-sync persistent storage disk for the virtualization service cannot be watched for sync to standby RP. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-HA_SYNC_THREAD_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> HA remote sychronize thread has failed and exited. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IOx-manager tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check IOx-manager's logs for the cause of the failure. Check for the pthread error msg and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-INITIALIZATION_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Initialization of [chars] failed for IOx Manager </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Initialization of IOx Manager process failed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Review ioxman logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-INSTALL_FAILURE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The installation of the virtualization service failed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the installation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-INSTALL_LOG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The installation log of the named virtualization service, is to provide more information about long running operation, that could affect the control of CLI </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-INSTALL_MEDIA_RETRY </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> VM install media still unavailable.[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The install media was not detected. Waiting for udev to complete install media(harddisk) detection. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> After IOx-manager exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-INSTALL_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] '[chars]'[chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The installation state of the named virtualization service has changed as notified by IOx-manager. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-INVALID_ACT_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service activate message was received, however, the data it contained could not be interpreted </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-INVALID_DEACT_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to process virtualization service deactivate message </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service deactivate message was received, however, the data it contained could not be interpreted </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-INVALID_UNPROV_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to process virtualization service unprovision message </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service unprovision message was received, however, the data it contained could not be interpreted </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-IOX_INST_CRIT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOX SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-IOX_INST_LOG_UNTHROTTLE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to unthrottle the log for IOX service [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named IOX service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> For debugging collect the ioxman logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-MEMORY_LIMIT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service machine definition file is requesting more memory than the system has available for virtualization services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-MOVE_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] '[chars]' [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The move of the core or log file of the named virtualization service has as been successful or failed as notified by IOx-manager. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check IOx-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-NETWORK_CONFIG_ERROR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A network configuration error has been detected for the named virtualization service. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-RESET_FORCE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Services non-recoverable reset command processed </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A 'virtualization service reset force' command has been entered and processed. This action initiates a cleanup of last resort. Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Once the command is entered and accepted, there is no recourse but to restart the system. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-RESIZE_OPER_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization service '[chars]' [chars][chars] to '[dec]' [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IOx-manager attempts to resize various VM parameters like rootfs size, CPU share, memory if requested by user. Success/failure status messages for these resize operations are communicated by this syslog. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check IOx-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-RSYNC_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IOx-manager tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check IOx-manager's logs for the cause of the failure. Check for the rsync error code and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-START_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named virtualization service failed to start. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-UNINSTALL_ALL_VMS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> All Virtualization Services are being uninstalled [chars][chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> All virtualization services are being uninstalled by IOx-manager. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the reason given as to why all virtualization services are being uninstalled for more information. If the reason indicated is due to some error condition, check IOx-manager's logs for the cause of the failure. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-UPGRADE_LOG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The upgrade log of the named virtualization service, is to provide more information about long running operation, that could affect the control of CLI </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-VCPU_INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service machine definition file is requesting invalid VCPU value. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-VCPU_LIMIT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service machine definition file is requesting more VCPUs than the system has reserved for virtualization services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-VIRT_INST_DISK </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service requires Disk Storage in excess of the Free Disk Storage available to virtualization services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-VIRT_INST_LOG_UNTHROTTLE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to unthrottle the log for virtualization service [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named virtualization service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> For debugging collect the iox-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-VIRT_INST_MEMORY </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The virtualization service requires physical memory in excess of the free memory available to virtualization services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Enable the IOx-manager trace logs and repeat the activation of the virtualization service. Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-VIRT_INST_MGMT_INTERFACE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization service [chars] has no management interface defined but it is configured in CLI. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A management interface is configured but none is defined. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Deactivate the virtualization service, remove the management interface configuration CLI, and reactivate the virtual-service. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-2-VIRT_INST_STATE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named virtualization service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> An attempt at restarting the virtualization service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-3-IOX_INST_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOX SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-3-IOX_NETMASK_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app configuration has wrong [chars] netmask. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The netmask configuration is wrong. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Configure guest-ipaddress with IPV4 or IPV6 netmask. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-3-PSS_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Purpose: [chars], URI: [chars], errcode: [dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Persistent Storage Service handling error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-3-PSS_SNAPSHOT_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Source URI: [chars], Destination URI: [chars], errcode: [dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Persistent Storage Service snapshot error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-3-SDWRAP_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Description: [chars], errcode: [dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Debug infrastructure error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Collect the IOx-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-4-HA_SYNC_NEEDED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> If using the guest shell, please use 'guestshell sync' if you want to preserve state on standby in case of supervisor switchover </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message notifying user that he needs to manually synchronize the Virtualization service contents to standby supervisor in order to preserve these contents in case of a supervisor switchover. Currently only applicable to the guest shell </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> User can type the 'guestshell sync' command on active supervisor to synchronize it's contents to the standby supervisor if desired. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-4-IOX_INST_WARN </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOX SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-4-WATCHDOG_TIMER </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] '[chars]' [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The watchdog timer configured for the named virtual service has expired. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check any logs produced by the virtualization service to determine the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-5-AUX </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service[chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The AUX login to a virtualization service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-5-IOX_INST_NOTICE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOX SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-5-IOX_IPV6_NOTICE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> guest-interface([dec]), IPV6 address configured with guest-ipaddress is ignored </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The IPV6 address configuration with guest-ipaddress is ignored. 'ipv6-address' has been configured and multiple static IPV6 addresses are not supported </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Configure guest-ipaddress with IPV4 address. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-5-IOX_NOTICE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The generic IOX notice. Please interpret the log in the context of the information provided. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-5-IOX_URL_COPY_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> URL Copy: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Copy a package file from URL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check if 'ip name-server', 'ip name-server vrf Mgmt-vrf' and 'ip http' are configured properly for the device </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-5-IOX_VPG_IPV6_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> no IPv6 address for VirtualPortGroup[dec] in IOS_Oper_DB </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> VirtualPortGroup IPv6 address is not present in IOS_Oper_DB </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check if 'show ip interface brief' displays IPv6 for the VirtualPortGroup </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-5-PERMISSION_DENIED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Virtualization Service '[chars]' is not owned by client IOSd </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An attempt was made to modify a virtual-service that is not owned by by the client. The request was rejected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-ACTIVATE_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for activating an app. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-DEACTIVATE_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for deactivating an app. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-INSTALL_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for installing an app. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-IOX_ENABLEMENT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOX is ready. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for IOX enablement. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-IOX_INST_INFO </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOX SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-IOX_MEDIA_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> dynamic media: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for IOX shared median </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-IOX_RECONCILE_INFO </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> App-hosting application reconcile process [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Indicates stage of reconcile (application recovery) process. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-IOX_START_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] failed to start </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Indicates starting an app after installation. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-IOX_START_INFO </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] cannot be started because it is not installed </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Indicates starting an app before installation. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-IOX_START_SUCCESS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] is in RUNNING state </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Indicates starting an app after installation. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-START_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for starting an app. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-STOP_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for stopping an app. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-UNINSTALL_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for uninstalling an app. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-UPGRADE_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for upgrading an app. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-6-VERIFICATION_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for signature verification </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IM-7-IOX_INST_DEBUG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOX SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The named IOX service has triggered the log. Please interpret the log in the context of the IOX services. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-0-FIPS_CPP_CLIENT_BYPASS_TEST </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> CPP Client FIPS bypass test failed for [chars]\n. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Forwarding Manager CPP client IPSEC bypass test failed. This could be due to a hardware malfunction or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> If the problem persists reboot the forwarding processor (ESP). </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-0-FIPS_FMFP_BYPASS_TEST </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> NIST bypass test failed for [chars].\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Forwarding Manager IPsec component detected a discrepancy when adding or deleting a security sensitive object. This could be due to a hardware or software resouce limitation or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the logs for information on the relevant object download states. Remove the object or a parent object in question. If the problem persists reboot the forwarding processor (ESP). </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-0-FIPS_FMFP_N2_SEVERE_ERR_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Cryptographic coprocessor severe failure: [chars]\n. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Cryptographic coprocessor critical operation failed. Further data processing on ESP is halted </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> forwarding processor (ESP) is rebooted automatically. no action needed </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-6-FIPS_FMFP_CRNG_TEST </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> continuous [chars]approved RNG test failed.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Forwarding Manager IPsec component detected two identical random number sequences. This could be due to a hardware mulfunction or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> If the problem persists reboot the forwarding processor (ESP). </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-6-FIPS_FMFP_KAT_TEST </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> power up cryptographic self-test did not run to completion: [chars]\n. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Forwarding Manager power up known answer self-test (KAT) failed. This could be due to a hardware malfunction or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> If using ipsec, reboot the forwarding processor (ESP). </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-6-FIPS_FMFP_N2_ERR_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Cryptographic coprocessor non-critical failure: [chars]\n. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Cryptographic coprocessor non-critical operation failed. If the problem persists reboot the forwarding processor(ESP) </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> If the problem persists reboot the forwarding processor (ESP). </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-6-FIPS_FMFP_OLAP_TEST </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> FIPS-approved RNG key seed and state overlap.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Forwarding Manager IPsec component detected an overlap in FIPS-approved RNG key seed and state. This could be due to a hardware mulfunction or a software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> If the problem persists reboot the forwarding processor (ESP). </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-6-FMFP_CRYPTO_DEVICE_BUSY </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> All Crypto Device cores are busy with data packets.\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> All ESP crypto device are busy. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> qfp-ipsec </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> May need to lower crypto traffic rate. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-6-FMFP_IPSEC_CRYPTO_CTRL_THROTTLED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IPsec Control Plane Overload Crypto Device: [chars]. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This ESP crypto device is overloaded. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> qfp-ipsec </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> May need to config platform ipsec control-plane medium|heavy </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-6-FMFP_IPSEC_MIN_MTU_INFO </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> MTU smaller than minimum IPSec MTU, [chars]\n. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Minimum MTU supported by crypto processor is 256B, MTU lower than 256B is set to 256B </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needed </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-6-FMFP_IPSEC_UNSUPPORTED_CIPHER </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Cipher [chars] is not supported on this ESP. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This ESP does not support this IPSec cipher </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needed </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IMGR-6-FMFP_KAT_TEST_RESULT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> crypto self-test for algorithm: ([chars] ... passed)\n. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Forwarding Manager power up known answer self-test (KAT) success. This is not an error message </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action needed. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> INSTALL-3-INSTANT_ERROR_MESSAGE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Error Message: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This message is used to send a instant erorr message. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> INSTALL-3-OPERATION_ERROR_MESSAGE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to [chars] package [chars], Error: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This message is used to inform the failure reason. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please refer to the error message to analyze the cause of failure. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> INSTALL-5-INSTALL_AUTO_ABORT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Install auto abort timer expired: initiating abort </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An install operation has been aborted because the auto abort timer has expired. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> INSTALL-5-INSTALL_AUTO_ABORT_TIMER_PROGRESS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Install auto abort timer will expire in [dec] seconds </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An install operation will be aborted after specified seconds of time. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> INSTALL-5-INSTALL_COMPLETED_INFO </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Completed [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This message is used to indicate the completion of install operations. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-p-install </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action required. This is not an error, it is an indication that the system completed this operation. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> INSTALL-5-INSTALL_SCHEDULE_TIMER_PROGRESS </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Install schedule timer will expire in [dec] seconds </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An install operation will be started after specified seconds of time. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-p-install </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No user action is needed. This is an informational message only. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> INSTALL-5-INSTALL_START_INFO </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Started [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This message is used to indicate the beginning of install operations. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-p-install </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action required. This is not an error, it is an indication that the system is starting this operation. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> INSTALL-5-OPERATION_COMPLETED_INFO </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Completed [chars] package [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This message is used to indicate the completion of operations. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action required. This is not an error, it is an indication that the system completed the operation. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> INSTALL-5-OPERATION_START_INFO </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Started [chars] package [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This message is used to indicate the beginning of operations. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action required. This is not an error, it is an indication that the system is starting the operation. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-2-MAX_LIMIT_XCVR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Number of [chars] that can be supported has reached the max limit of [dec], transceiver is err-disabled. Unplug the transceiver in interface [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Because of power constraints, we can support only limited number of high power transceivers in certain platforms. If we insert more than the limit, it will be disabled. It is recommended to unplug the transceiver </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug the transceiver once the max limit is reached </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-3-FIFO_OVERFLOW </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> [chars] fifo overflow occurred for port [dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A hardware error in phy has occurred </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the IOMD logs for Phy driver or hardware errors. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-3-INTERRUPT_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> interrupt handling error [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Interrupt could not be handled because of internal sw error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the IOMD logs. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-4-LC_OIR_REQD </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Found mismatch between the line card Phy firmware versions bundled in software and programmed in hardware in slot [dec]. To upgrade the Phy firmware to version bundled in software, perform physical OIR of the line card or run the CLI: hw-module subslot [dec]/[dec] oir power-cycle. If ISSU is in progress, firmware upgrade should be done only after the completion of ISSU. To check the firmware versions, use the CLI: show firmware version all </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> During ISSU the software does not upgrade the PHY firmware. PHY firmware upgrade needs a reset and will lead to data path down time. Hence software avoids PHY firmware upgrade. This causes a mismatch between the firmware bundled in the image and that programmed in the PHY. Due to this mismatch any new features claimed by the new software will not be automatically enabled and needs a manual upgrade via power-cycle of the line card </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> To upgrade to latest phy firmware, do physical OIR or soft OIR of the line card using CLI: hw-module subslot &lt;slot&gt;/&lt;bay&gt; oir power-cycle. To view the present phy firmware version, use the CLI: show platform hardware iomd &lt;slot&gt;/&lt;bay&gt; ethernet_controllers phy &lt;port number&gt; api-version or show firmware version all </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-4-NOT_SUPPORTED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> 1G Transceiver is inserted in slot [dec] for ports [chars]. The current linecard phy firmware does not support 1G capability. To upgrade the firmware, perform physical OIR of the line card or use the CLI: hw-module subslot [dec]/0 oir power-cycle. If ISSU is in progress, firmware upgrade should be done only after the completion of ISSU </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> During ISSU the software does not upgrade the PHY firmware. PHY firmware upgrade needs a reset and will lead to data path down time. Hence software avoids PHY firmware upgrade. This causes a mismatch between the firmware bundled in the image and that programmed in the PHY. Due to this mismatch any new features claimed by the new software like 1G will not be automatically enabled and needs a manual upgrade via power-cycle of the line card </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> To upgrade to latest phy firmware, do physical OIR or soft OIR of the line card using CLI: hw-module subslot &lt;slot&gt;/&lt;bay&gt; oir power-cycle. To view the present phy firmware version, use the CLI: show platform hardware iomd &lt;slot&gt;/&lt;bay&gt; ethernet_controllers phy &lt;port number&gt; api-version or show firmware version all </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-4-NOT_SUPPORTED_XCVR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> 1G Transceiver is inserted in slot [dec] for port [dec]. The current linecard phy firmware does not support 1G capability. To upgrade the firmware, perform physical OIR of the line card or use the CLI: hw-module subslot [dec]/0 oir power-cycle </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> During ISSU the software does not upgrade the PHY firmware. PHY firmware upgrade needs a reset and will lead to data path down time. Hence software avoids PHY firmware upgrade. This causes a mismatch between the firmware bundled in the image and that programmed in the PHY. Due to this mismatch any new features claimed by the new software like 1G will not be automatically enabled and needs a manual upgrade via power-cycle of the line card </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> To upgrade to latest phy firmware, do physical OIR or soft OIR of the line card using CLI: hw-module subslot &lt;slot&gt;/&lt;bay&gt; oir power-cycle. To view the present phy firmware version, use the CLI: show platform hardware iomd &lt;slot&gt;/&lt;bay&gt; ethernet_controllers phy &lt;port number&gt; api-version or show firmware version all </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-4-QSA28_UNSUPPORTED_MODE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> On SLOT [dec], QSA28 transceiver plugged into port [dec] configured in 40G mode is not supported. Please remove QSA28 from the port or configure the port as 100G. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> QSA28 is supported only on 100G ports. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug QSA28 from the port or change the port configuration to 100G. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-4-QSA_UNSUPPORTED_MODE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> On SLOT [dec], QSA transceiver plugged into port [dec] configured in 100G mode is not supported. Please remove QSA from the port or configure the port as 40G. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> QSA is supported only on 40G ports. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug QSA from the port or change the port configuration to 40G. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-4-REMOVE_XCVR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Unplug the transceiver in interface [chars], keeping transceiver can have impact on other transceiver in the same port-group </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Inserting an incompatible transceiver is not recommended since it can have impact on other transceiver in the same port-group </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug the incompatible transceiver </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-4-UNSUPPORTED_TRANSCEIVER </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> On SLOT [dec], Transceiver plugged into port [dec] is not supported. Please remove the transceiver. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> It's not recommended to insert unsupported transceivers. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug the transeiver. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-5-LINK_INCONSISTENCY </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Inconsistency detected between hardware and software parameters in slot [dec] for ports [chars], restoring the consistency. Link flap or traffic drop might be observed on these ports during this process </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> During switchover or ISSU, if the serdes parameters are different in active and standby, these parameters will be reprogrammed. This may result in link flap or traffic drop momentarily </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-5-MODULE_REINIT_REQUIRED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Hardware parameters on PHY for slot [dec] need modification, Which may have an impact on link and traffic during switchover. User intervention is required to fix the problem by reloading slot [dec]. Use the command 'hw-module subslot [dec]/0 oir power-cycle' to reset the slot during maintainance </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Hardware parameters need to be updated on PHY. Due to hardware limitation these parameters cannot be applied dynamically. For applying these parameters we need reload linecard </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Perform Linecard reload by using below command so that parameter changes get commited to hardware. If this step is not performed then you may face a link flap and traffic loss during switchover Command : hw-module subslot &lt;slot&gt;/0 oir power-cycle </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-6-STBY_PORTS_INITIALIZED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Interfaces on slot [dec] are initialized on standby and ready for switchover </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> All the interfaces on standby for particular slot is initialized and Interface are ready for switchover. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_ETHER_GEIM-6-UNSUPPORTED_MODE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> On SLOT [dec] QSFP transceiver plugged into 40G port [dec] and a QSA module plugged into port [dec] is unsupported combination. To linkup the desired connections, please remove QSFP transceiver from port [dec] as well as QSA module from port [dec] and then insert only the required QSFP transceiver or QSA module in the respective port. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Due to a hardware limitation in PHY, QSFP Optics on top port and QSA module on bottom port is not supported </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug the error disabled transceiver </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-3-I2C_READ </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> An I2C read has failed because [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An I2C read has failed. This could be due to a hardware or software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-3-I2C_WRITE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> An I2C write has failed because [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An I2C write has failed. This could be due to a hardware or software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-3-INTR_EVENT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOMd fast thread event ([dec]). </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IOMd fast thread event </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-3-INVALID_BAY_NUM </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> An invalid bay number is specified in one of the internal APIs. bay=[dec] max_bay=[dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Invalid bay number to find the TDL domain </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-3-INVALID_SLOT_NUM </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> An invalid slot number is specified in one of the internal APIs. slot=[dec] max_slot=[dec] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Invalid slot number to find the TDL domain </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-3-IPCALLOCFAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to allocate IPC buffer [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The IM failed to allocate a buffer for communication with RSP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-3-IPCSENDFAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOMD failed to send a message [chars] reason: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IOMD failed to send message to the RP </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-3-LINECARDDIAGSFAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Module [chars] in Slot [dec] failed online diagnostics. Please use 'show post' for more details </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Online Diag has failed. This could be due to a hardware or software defect. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-3-SVL_SPEED_MISMATCH </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Speed of SVL Port [dec] in Slot [dec] does not match with other SVL Links. Please take neccessary action. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Speed of this SVL Link does not match with the speed of other SVL Links This can be due to replacement of a cable with different Speed on SVL port. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please check the operating speed of this SVL Link and the operating speed of the other SVL Links.If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-4-BADPOINTER </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Function [chars] detected an invalid [chars] pointer of %08lX, ignoring </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A software error has occurred, this message is displayed when an invalid pointer is detected. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-4-FAN_ALARM </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Interface [chars], fan alarm [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Fan alarm due to temperature </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> For MINOR, action is &lt;fill minor action&gt; For MAJOR, action is &lt;fill major action&gt; For CRITICAL, action is &lt;fill critical action&gt; </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-4-INTR_OVER_LIMIT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> IOMd main thread disabled interrupt for [dec] msec. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> IOMd main thread process disabled interrupt too long </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-4-LC_OIR_REQD </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Found mismatch between the line card Phy firmware versions bundled in software and programmed in hardware in slot [dec]. To upgrade the Phy firmware to version bundled in software, perform physical OIR of the line card or run the CLI: hw-module subslot [dec]/[dec] oir power-cycle. If ISSU is in progress, firmware upgrade should be done only after the completion of ISSU. To check the firmware versions, use the CLI: show firmware version all </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> During ISSU the software does not upgrade the PHY firmware. PHY firmware upgrade needs a reset and will lead to data path down time. Hence software avoids PHY firmware upgrade. This causes a mismatch between the firmware bundled in the image and that programmed in the PHY. Due to this mismatch any new features claimed by the new software will not be automatically enabled and needs a manual upgrade via power-cycle of the line card </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> To upgrade to latest phy firmware, do physical OIR or soft OIR of the line card using CLI: hw-module subslot &lt;slot&gt;/&lt;bay&gt; oir power-cycle. To view the present phy firmware version, use the CLI: show platform hardware iomd &lt;slot&gt;/&lt;bay&gt; ethernet_controllers phy &lt;port number&gt; api-version or show firmware version all </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-6-BEACON_LED_TURNED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Slot [dec] Port [dec] Beacon LED turned [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Beacon LED turned ON/OFF. This is a notification message only.No action is required. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> This is a notification message only. No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-6-HIGH_POWER_OPTICS_DETECTED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The port [chars] supports optics with a max power of [dec].[dec] W, but inserted optics max power is [dec].[dec] W. This can lead to operational issues for these and neighbouring ports. To identify allocated port max power, please execute the CLI: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Due to a thermal limitation, insertion of High power QSFP/SFP Optics in this port is not suggested. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug the high power XCVR. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-6-HIGH_POWER_OPTICS_PRESENT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The line card [dec] has optic(s) inserted in port(s) that has power limitations. The optics max power is more than the power recommended. This can lead to operational and thermal issues for these and neighbouring ports. To identify allocated port max power, please execute the CLI: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Due to a thermal limitation, insertion of High power QSFP/SFP Optics in some ports is not advised. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug the high power XCVR. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-6-STBY_PORTS_INITIALIZED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Interfaces on slot [dec] are initialized on standby and ready for switchover </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> All the interfaces on standby for particular slot is initialized and Interface are ready for switchover. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-6-TDLMSG_INCOMPATIBLE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Failed to copy message [chars] to buffer, not allowed for current domain. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Failure to marshal a message indicates an incompatibility with the intended recipient. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> asr900-im </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Examine the logs for IOMD. If the problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-6-UNSUPPORTED_MODE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Transceiver module in [chars] going in err-disabled state. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Breakout optics is not supported in non-breakout port; Non-breakout optics is not supported in breakout port </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug the error disabled transceiver </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-6-UNSUPPORTED_MODE_BREAKOUT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Transceiver module in [chars] going in err-disabled state. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Breakout optics is not supported in non-breakout port; Non-breakout optics is not supported in breakout port </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug the error disabled transceiver </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_INFRA-6-UNSUPPORTED_SPEED_COMBINATION </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> On SLOT [dec] QSFP 100G/40G transceiver plugged into port [dec] and a QSA module plugged into port [dec] is unsupported combination. To linkup the desired connections, please remove QSFP transceiver from port [dec] as well as QSA module from port [dec] and then insert only the required QSFP transceiver or QSA module in the respective port. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Due to a hardware limitation in PHY, QSFP Optics on top port and QSA module on bottom port is not supported </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Unplug the error disabled transceiver </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOMD_STARFLEET-5-LINK_RECOVERY </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Interface [chars] link recovery mechanism triggered [Reason: System Side Signal down] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Link recovery mechanism detected a system side signal issue on UADP transmit. Recovery mechanism was triggered for correcting it. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOSD-3-BIPC_REJECT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Could not accept ipc connection: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This error occurs if shell-manager has denied an ipc connection request from IOS. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the connection request parameters. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOSD-3-TDL_PROPERTIES </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Could not set message properties for connection: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This error occurs if shell-manager is unable to set message properties for the IOS-sman connection </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the connection request parameters. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOSXE_UPGRADE_ROMMON-0-ROMMON_LOADTEST_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ROMMON FIPS_140-3 Load test *FAILED*: file [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> FIPS 140-3 Related Load test failed for the ROMmon. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the system messages to see if any messages appeared that might indicate the source of the ROMmon Load test problem. If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the collected information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOSXE_UPGRADE_ROMMON-0-ROMMON_UPGRADE_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ROMMON upgrade failed: partition [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An attempt to upgrade the ROMmon failed. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Check the system messages to see if any messages appeared that might indicate the source of the ROMmon problem. If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the collected information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOXCAF-5-GUESTSHELL_IPV4_NOTICE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> guestshell ip address([chars]) of Mgmt-Intf is ignored. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The ipv4 address configured for guestshell's Mgmt-Intf is ignored. When guestshell is on Mgmt-Intf it is natted and has an internal 192.168 ipv4 address. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOXCAF-5-GUESTSHELL_IPV6_NOTICE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> guestshell ipv6 address([chars]) of Mgmt-Intf is ignored. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The ipv6 address configured for guestshell Mgmt-Intf is ignored. When guestshell is on Mgmt-Intf it is natted and has an internal 192.168 ipv4 address. Therefore there is no need to provide a static ipv6 address to guestshell interfaces. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOXCAF-6-INSTALL_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for installing an app. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOXCAF-6-UPGRADE_MSG </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> app-hosting: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Message for upgrading an app. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> In the failed case, check Ioxman's trace log for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOXMGR-2-DNAC_EGRESS_INTF_NOT_SVI </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Not supported: egress interface ([chars]) towards Cisco-DNAC server [chars] is not an SVI </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> Egress interface to reach the Cisco-DNAC server is restricted to be an SVI </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> ewlc-iot-gw </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> If this message occurs, the egress interface towards the Cisco-DNAC server needs to be configured as an SVI </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IOXMGR-2-DNAC_EGRESS_INTF_NO_GLOB_IPV6_ADDR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Cisco-DNAC configured address is IPv6, but no global IPv6 address configured on egress interface [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> At least one local IPv6 global/routable address is needed to reach the Cisco-DNAC server </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> ewlc-iot-gw </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> If this message occurs, at least one IPv6 global address needs to be configured on the egress interface towards the Cisco-DNAC server. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IPC_ERRMSG-4-IPC_WARNING_TRACE </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Warning, [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> General warning message with traceback </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> ewlc-app-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> IPC_LOG-3-IPC_LOGWRITE_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ipc log write [dec] bytes failed because [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An internal logging mechanism failed to write a message. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action is required. However, if router performance is noticeably degraded, contact Cisco Technical Assistance. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-0-BOOT_SYNC_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Problem with sync of ISSU boot state - [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The ISSU state between two FRUs is not properly synchronized as a result of a boot error. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-0-PKG_INCONSIST </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Reason: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A software consolidated package or sub-package has an error that indicates the sub-package should not be installed or used. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> If this message is received, the desired consolidated package or sub-package should not be used. Upgrade using a different consolidated package or sub-package, and report the problem consolidated package or sub-package to Cisco technical support. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-0-PKG_MNT_SCRIPT_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Package: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A consolidated package or sub-package has encountered an error indicating it is not usable. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Upgrade your software using a different consolidated package or sub-package. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-0-RESET_FRU_FAIL </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Problem with ISSU reset of remote FRU - [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> After a sub-package installation, one or more FRUs that were upgraded failed to initialize within the timeout period. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> This problem is more likely to occur in routers with larger configurations, so if your router has a large configuration, you may want to wait a few more minutes to see if your hardware initializes. If the hardware continues to not initialize, reset the FRUs which failed to initialize. If resetting the FRUs fails to resolve the issue, gather the output of show tech-support and contact a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-0-SOFTWARE_INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Package for location [chars]: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The sub-packages have encountered an error related to the structure of the loaded software. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> This error is likely caused by a failure of the boot or installation process or a corrupted provisioning file. If the system displays error messages related to the boot that can be addressed, address those messages. Downloading new software, if possible, may also help with the problem. If the problem persists, gather the output of show tech-support and provide it to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-3-BOOT_SYNC </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Problem with sync of ISSU boot state - [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The ISSU state between two FRUs is not properly synchronized as a result of a boot error. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> This message will automatically appear during certain events, such as during a FRU removal or if the FRU loses connectivity. In most cases, the router will resynchronize the ISSU state between the FRUs without any user intervention. If the ISSU state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-3-BOOT_UNCLEAN </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Found reload log file, moved to [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> A log file was found at bootup indicating that all shutdown tasks were not performed on a previous reload. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No user action is necessary. The system will automatically resolve most issues related to the shutdown task as part of the bootup procedure. If a problem related to the tasks that did not shutdown occurs, another error message will occur providing information about that problem. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-3-INCOMPAT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> The packages in [chars] are not consistent </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The sub-packages specified for running on the chassis are not compatible with one other. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Install a compatible set of packages to allow normal operation. This will require booting a known-good package set. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-3-ISSU_COMP_CHECK_FAILED </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ISSU compatibility check failed for [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The image is not ISSU compatible </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-issu-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please add another ISSU compatible image to start ISSU </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-3-SYNC_ERR </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Problem with sync of state - [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The software state between two FRUs or switches is not properly synchronized as a result of a boot error. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> This message may appear during certain events, such as during a FRU or switch removal or if the FRU or switch loses connectivity. In most cases, the router will resynchronize the software state between the FRUs or switches without any user intervention. If the software state is not resynchronized after multiple attempts, the problem is likely a result of another problem. Monitor the other system messages to see if a more serious issue has occurred on your router. If you are unable to resolve this other issue and this message persists, gather the output of show tech-support and provide it to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-3-UCODE_INCOMPAT </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> Found mismatch for ucode feature - [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> During boottime microcode feature version check, a version mismatch was found for this feature. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> Please ensure that versions of features in microcode are compatible by provisioning a different set of microcode files. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-5-ISSU_AUTO_ROLLBACK </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ISSU rollback timer expired: initiating rollback </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> An ISSU upgrade has been rolled back because the rollback timer has expired. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No user action is needed. If you want to commit the ISSU upgrade, redo the upgrade. Otherwise, this is an informational message only. </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-5-ISSU_STAGE_INFO </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> STAGE [chars]: [chars] [chars]\n </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> This message is used to indicate the start/completion of ISSU stages. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> polaris-issu-infra </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No action required. This is an indication that ISSU stage has started or completed </td> </tr> <tr> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__1 "> ISSU-5-ISSU_STATE_INVALID </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__3 "> ISSU stored state found invalid and cleaned up: [chars] </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__4 "> The RP has corrected a failed ISSU install state that was detected at bootup. </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-f-to-j-syslogs_17161__entry__6 "> No user action is necessary. This is an informative message indicating that the failed ISSU state has been corrected. </td> </tr> </tbody> </table> </section> </div>  <nav role="navigation" class="related-links"></nav>  </article> <article class="topic reference nested2" aria-labelledby="ariaid-title8" lang="en-US" id="r-k-to-o-syslogs_17161"> <h3 class="title topictitle3" id="ariaid-title8"> K to O </h3> <div class="body refbody"> <section class="section" id="r-k-to-o-syslogs_17161__d54e40511"> <table width="100%" border="1" class="table"> <caption></caption> <colgroup> <col style="width:37.334510150044125%"> <col style="width:8.8261253309797%"> <col style="width:16.504854368932037%"> <col style="width:8.8261253309797%"> <col style="width:8.8261253309797%"> <col style="width:19.68225948808473%"> </colgroup> <thead class="thead"> <tr> <th font-weight="bold" class="entry align-left" id="r-k-to-o-syslogs_17161__entry__1"> Facility-Severity-Mnemonic </th> <th font-weight="bold" class="entry align-left" id="r-k-to-o-syslogs_17161__entry__2"> Severity-Meaning </th> <th font-weight="bold" class="entry align-left" id="r-k-to-o-syslogs_17161__entry__3"> Message </th> <th font-weight="bold" class="entry align-left" id="r-k-to-o-syslogs_17161__entry__4"> Message-Explanation </th> <th font-weight="bold" class="entry align-left" id="r-k-to-o-syslogs_17161__entry__5"> Component </th> <th font-weight="bold" class="entry align-left" id="r-k-to-o-syslogs_17161__entry__6"> Recommended-Action </th> </tr> </thead> <tbody class="tbody"> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_ACL_ERRMSG-3-ACL_EDIT_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to program modified [chars] [chars] [chars] [chars] ACL in hardware. The number of ACEs exceeded hardware limit.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> You have exceeded the system limit of ACE entries. Delete the ACL first and then modify the acl by reducing number of ACEs and re-configure the ACL on the box.\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_ACL_ERRMSG-3-ACL_NOT_SUPPORTED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> ACL is not supported on this interface [chars].\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Unsupported configuration </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> ACL is not supported on this interface %s.Remove the ACL from interface on IOS\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_ACL_ERRMSG-3-EPC_EOMPLS_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> EPC is not supported on EOMPLS port. To recover, stop the capture from [chars] interface.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Unsupported configuration </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Stop the capture from %s interface..\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_ACL_ERRMSG-3-OGACL_EGRESS_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> OGACL is not supported in egress dir. To recover, Delete [chars] ACL [chars] proto , correct mistake and re-create ACL.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Invalid configuration </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Delete ACL , correct mistake and re-create ACL.\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_ACL_ERRMSG-4-UNLOADED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] ACL on interface [chars] could not be programmed in hardware.Either number of ACLs or number of ACES in acl exceeded hardware limit. All the packets will be dropped.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> You have exceeded the system limit of entries, use a simpler configuration which uses less entries.It can be either number of ACLs or number of ACES in the acl.\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_ACL_ERRMSG-6-SUB_INTF_BIND_WARNING </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [chars] [chars] ACL on interface [chars] could not be programmed in hardware. VLAN is not ready in hardware. Once VLAN is ready, ACL will be attached to vlan automatically in hardware.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Invalid configuration. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> VLAN is not ready in hardware.Once VLAN is ready, ACL will be attached to vlan automatically in hardware. Worst case, first detach ACL from sub-interface. Configure vlan on this sub-interface if not already done and then reattach ACL \n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_FNF_ARGON_ERRMSG-4-OOR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [chars] FNF mon_id [dec] on interface [chars] could not be programmed in hardware.Either number of ACLs or number of ACES in flow monitor or netflow profile exceeded hardware limit.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> You have exceeded the system limit of entries, use a simpler configuration which uses less entries. It can be either number of ACLs or number of ACES in the acl.\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_L2_ERRMSG-3-MCID_EMDB_RSC_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to allocate replication entry to do flooding for vlan: [dec], vp_if_id: 0x%lx - reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_L2_MCAST_ERRMSG-3-MCID_EMDB_RSC_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to allocate replication entry for vlan: [dec], Group: [chars], vp_if_id: 0x%lx - reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_L2_MCAST_ERRMSG-3-MCID_RSC_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to allocate mcid for vlan: [dec], Group: [chars] - reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_L3TUNNEL_ERRMSG-3-EXIST_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Duplicate Tunnel config not supported\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Same tunnel source and destination </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Delete the tunnel and move to unique src/dst combination\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_L3TUNNEL_ERRMSG-3-OOR_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Unique 16 sources and 1K Tunnels only supported\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Too many tunnels </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Delete unwanted tunnels\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_L3TUNNEL_ERRMSG-3-TUN_MOD_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Please delete the tunnel and recreate it. Set the tunnel mode first and then configure the tunnel src and tunnel destination. Dynamic change to Tunnel mode not allowed.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Dynamic Tunnel mode change not allowed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Delete Tunnel. Set the correct mode and then configure tunnel src and tunnel dst\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_L3_ERRMSG-6-UNSUPPORTED_LB </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Mixed Mode of Tunnel and Normal ADJ Unsupported in LB, lbal_obj_id: 0x%x.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mixed Mode of Tunnel and Normal ADJ is Unsupported in LB. We are printing the lbal_obj_id which is effected </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Normal Adj will be removed from LB if Tunnel is present. Only Tunnel adj will be present for LB </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_QOS_ERRMSG-3-LA_QOS_SCH_BANDWIDTH_REMAINING_RATIO_IGNORED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Ignoring Non-default[Ratio=1], Interface level Bandwidth remaining ratio([dec]) on Main-interface [chars] for policy [chars]. Reason: No support\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Interface level(HQOS) Bandwidth remaining ratio is supported only across sub-interface on same main-interface or among main-interface with sub-interface priority propagation mode enabled and its sub-interface. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> bigbang-qos </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No Specific action required. However, for clarity user can consider installing different policy without Bandwidth remaining ratio in parent policy. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_QOS_ERRMSG-3-LA_QOS_TCAM_OOR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> No TCAM availabe to program policy [chars] on interface [chars] on [chars] direction.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> TCAM is full on the slice where the interface is on. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> bigbang-qos </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reduce the number of ACE in the policy. Remove the policy and attach again. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_QOS_ERRMSG-3-LA_QOS_VOQ_CGM_PROFILE_EXHAUSTED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> VOQ Congestion Mangement(CGM) profiles exhausted.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> All the available 32 VOQ CGM Profiles have been used up and a new profile creation was attempted </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> bigbang-qos </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Check all queueing policies for unique CGM Configuration. See if some can be combined to free some CGM Profiles </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_QOS_ERRMSG-4-LA_QOS_SCH_PORT_SHAPER_GREATER_THAN_INTERFACE_SPEED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> For [chars], User configured port shaper speed[[dec]] is greater than physical port speed [[dec]]. Limiting the same to physical port speed\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> User configured port shaper in H-QOS policy is higher than physical interface speed. User needs to revisit the policy. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> bigbang-qos </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No Specific action required. However, user needs to revisit the policy. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_SGACL_ERRMSG-3-SGACL_CELL_BIND_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> SGACL [chars] on cell ([dec] [dec]) is not allowed. SGACL policy of default cell is not allowed to be shared with any other cells \n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Invalid configuration. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> SGACL policy associated with default cell is non-sharable with other cells. Maintain a separate policy for default permission. \n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_SGACL_ERRMSG-3-SGACL_CELL_MONITOR_WARNING </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> This platform supports only one counter per cell. User attached both V4 & V6 policies to cell [[dec], [dec]] but monitor mode is set to only one protocol. This may lead to inaccurate Hw-Deny, HW-Monitor cell counters. There will be no effect on functionality\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Invalid configuration. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Configure monitor mode for both IPv4 & IPV6 \n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_SGACL_ERRMSG-3-SGACL_DEFAULT_CONFIG_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> TCAM Resource Error. Default permission configuration failed. Delete default sgacl permissib ons, free up some TCAM resources and configure default permission again\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Configuration is too big </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Delete sgacl default permissions. Free up some TCAM resources and configure default permissions again\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LA_SGACL_ERRMSG-3-SGACL_EDIT_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to program modified [chars] [chars] [chars] [chars] ACL in hardware. The number of ACEs exceeded hardware limit.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The configuration is too large. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> You have exceeded the system limit of ACE entries. Delete the ACL first and then modify the acl by reducing number of ACEs and re-configure the ACL on the box.\n </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LISP_AGENT_MESSAGE-3-LISP_AGENT_DB_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> DB-Error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An internal error occurred due to which unable to update the oper DB records </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-wlss-lisp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LISP_AGENT_MESSAGE-3-LISP_AGENT_MAP_REGISTER_MSG_SEND_FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error: Failed to send [chars] to MAP Server for [chars]: %02x%02x.%02x%02x.%02x%02x </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An internal error occurred due to which unable to send Map Register message to MAP server </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-wlss-lisp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LISP_AGENT_MESSAGE-3-LISP_AGENT_MAP_REGISTRATION_REJECT_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error: [chars] %02x%02x.%02x%02x.%02x%02x with rejection code [dec] - [chars], MS IP: [chars], VNID: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Received MAP Registration Reject Message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-wlss-lisp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LISP_AGENT_MESSAGE-3-LISP_AGENT_MAP_REPLY_NACK_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error: [chars] %02x%02x.%02x%02x.%02x%02x </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Received MAP reply NACK Message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-wlss-lisp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LISP_AGENT_MESSAGE-3-LISP_AGENT_MAP_REQUEST_MSG_SEND_FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error: Failed to send [chars] to MAP Server for [chars]: %02x%02x.%02x%02x.%02x%02x </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An internal error occurred due to which unable to send Map Request message to MAP server </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-wlss-lisp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LISP_AGENT_MESSAGE-3-LISP_AGENT_MS_IP_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> LISP AGENT clear [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Map Server msg stats not exists error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-wlss-lisp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LISP_AGENT_MESSAGE-3-LISP_AGENT_RECEIVE_ERROR_NOTIFICATION_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error: Received reliable error notification msg with [chars] [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> the Error Notification message received from the MAP Server </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-wlss-lisp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LISP_AGENT_MESSAGE-6-LISP_AGENT_TRANSPORT_MS_CONNECTION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] with map server IP [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> re-establishment of connection with map server got success </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-wlss-lisp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LI_CORE-2-EGRESS_INTF_NOT_SVI </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Not supported: egress interface ([chars]) towards LI host [chars] is not an SVI </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Egress interface to reach the LI host is restricted to be an SVI </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-spwifi </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, the egress interface towards the LI host server needs to be configured as an SVI </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LI_CORE-2-EGRESS_INTF_NO_GLOB_IPV6_ADDR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> LI host address configured is IPv6, but no global IPv6 address configured on egress interface [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> At least one local IPv6 global/routable address is needed to reach the LI host server </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-spwifi </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, at least one IPv6 global address needs to be configured on the egress interface towards the LI host server. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-1-AP_INSUFFICIENT_PERM_APCOUNT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> APs connected exceed the permanent licenses available by [dec]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The number of APs connected is greater than the number of permanent licenses. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Purchase adder licenses to add to your existing permanent licenses. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-1-AP_USAGE_EXCEEDED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> AP-count license usage has exceeded the available AP-count by [dec]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> AP-count license usage has exceeded the available AP-count. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Remove the excess APs from the controller. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-1-EVAL_EXP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Evaluation period of [chars] license expired [dec] days ago. Purchase a permanent license. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The evaluation license has expired. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Purchase a permanent license. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-1-EXCESS_AP_LIC </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Total AP-count licenses available have exceeded the maximum supported AP-count by [dec]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The number of AP-count licenses available is greater than the maximum number of supported AP-count. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> The extra AP-count licenses can be moved to another controller. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-1-PRIMARY_REMOVED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The current stack does not support the applied AP License Count. Reconnect a Catalyst 5760 SKU running valid AP License Count within 90 days. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> AIR-CT5760-HA-K9 does not support the same licensing as AIR-CT5760-HA-K9. So an AIR-CT5760-HA-K9 SKU is needed in the stack to support this licensing. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reconnect a Catalyst 5760 SKU running valid AP License Count within 90 days. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-1-RTU_DISABLED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Cannot proceed. Right-to-use Licensing is diabled. Switch is in Smart Licensing mode. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> RTU functionality is disabled when switch in SL mode. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Enable RTU licensing with CLI: no license smart enable. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-1-SKU_INCOMPAT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Both the switches in the stack are AIR-CT5760-HA-K9 SKUs. Replace one of the switches with another Catalyst 5760 SKU running valid AP License Count </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Two AIR-CT5760-HA-K9 SKUs are not supposed to stack. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Replace the license mismatch switch with a Catalyst 5760 SKU running valid AP License Count. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-1-TERM_EXP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Subscription term period of [chars] license expired [dec] days ago. Please renew your license. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The subscription license has expired. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Renew your subscription license. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-3-FILE_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars]: License file update failed. Reapply the configuration. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failed to update the license file. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reapply the configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-3-FILE_READ_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars]: License file read failed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failed to read the license file. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reapply the configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-4-EVAL_WARN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Evaluation period of [chars] license is about to expire in [dec] days. Purchase a permanent license. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The evaluation license is about to expire. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Purchase a permanent license. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-4-TERM_WARN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Subscription term period of [chars] license is about to expire in [dec] days. Please renew your license. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The subscription license is about to expire. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Renew your subscription license. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-AP_ADD </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [dec] adder AP-count licenses are added </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> AP-count licenses have been added. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> More APs can be supported. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-AP_DEL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [dec] adder AP-count licenses are removed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> AP-count licenses have been removed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Fewer APs are supported. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-DISABLE_RTU </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars]: Right-to-use Licensing is disabled. Switch is in Smart Licensing mode. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> User enables Smart Licensing. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Request image license license if needed. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-ENABLE_RTU </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars]: Right-to-use Licensing is enabled. Switch is in RTU mode. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> User configures RTU licensing by disabling Smart Licensing. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Configure image license and ap count license if needed. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-FACTORY_DEFAULT_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Factory Default License File [chars] on [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An error occured when trying to create the factory default file. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Fix the issue and try again. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-IOSD_LIC_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Switch #[dec]: Current IOSd runs on [chars] license while RTU active license is [chars]. Please configure RTU license to current IOSd license. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> When customer switches license mode from Smart Licensing to RTU Licensing, current IOSd license might mismatch with RTU active license. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Configure RTU license level to current IOSd license. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-LIC_ACT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] license is activated successfully on [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The license level is activated. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reboot the switch to invoke the activated license. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-LIC_ACTVED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] license was already activated. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The license level was already activated. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reboot the switch to invoke the activated license. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-LIC_CHANGE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] reboot license level changed from [chars] to [chars]. Reboot the switch to invoke the new license level. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Reboot license level has been changed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reboot the switch to invoke the activated license level. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-LIC_EULA_CLEAR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> EULA for [chars] license has been cleared on [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> License level has been deactivated. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> The end user license agreement (EULA) needs to be accepted while activating this license level. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-LIC_EVAL_TO_PERM </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> License level upgraded from [chars] [chars] to [chars]; [chars] license is in-use without reboot </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A license has been upgraded to a permanent or subscription license. A reboot is NOT required for the new license level to be effective. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-LIC_EXPED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] evaluation license has expired; you cannot activate it again. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> You cannot use an expired evaluatoin license. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Purchase a permanent license level or activate another license level. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-LIC_IMAGE_INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Switch #[dec]: The license boot level string is invalid. Boot up with the highest activated license. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The license boot level string is invalid. The RTU highest activated license is used. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Use 'license boot level' to configure a valid license level </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-LIC_INCOMPAT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Switch [dec] has an incompatible license level. Activate a compatible license on the switch so that the switch can join the stack. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The added switch has an incompatible license level. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Activate a new license and reboot the switch. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-LIC_INVALID_DEACT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] license is not active on [chars]; therefore, it cannot be deactivated. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The license level is not activated. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No need to deactivate this license. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMLIB_RTU_LICENSE-6-PLAT_INCOMPAT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Switch [dec] has an incompatible platform level. Activate a compatible platform on the switch so that the switch can join the stack. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The added switch has an incompatible platform level. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Run in compatible scaled mode and reboot the switch. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASFS_LOCATION_TRANSLATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to translate a location to a chasfs object name because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The license manager failed to translate a location to a chasfs object name. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASFS_OBJECT_CREATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The hardware failed to create a chassis filesystem object. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASFS_OBJECT_NOT_PRESENT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] not present. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASFS_OBJECT_WATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to watch chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A chassis filesystem object was not watched because of the reason stated in the error message. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASFS_PROPERTY_CREATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A chassis filesystem property was not properly created. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASFS_PROPERTY_GET </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to read chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A chassis filesystem property was not properly read by the system. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASFS_PROPERTY_NOT_PRESENT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] property [chars] not present. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASFS_PROPERTY_SET </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to write chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A chassis filesystem property failed to write. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASSIS_STATUS </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to get chassis hardware status because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The system failed to get the chassis hardware status. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for CPLD driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-CHASSIS_TYPE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The chassis type [chars] is invalid. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The chassis type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-INVALID_ARGUMENT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> A system function was given an invalid argument. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A system function was given an invalid argument. This is due to a software defect. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-IPC_CONNECTION_INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> An IPC connection has invalid state. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-IPC_CONNECT_MASTER </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> IPC connection to the active RP failed because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> IPC connection to the active RP failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-IPC_INITIALIZATION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> IPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> IPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-MESSAGE_REGISTER </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to register with active RP because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The active RP failed to register. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-MESSAGE_RELAY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to relay a message because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failed to relay a message. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-MESSAGE_RESPONSE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> An invalid message response was received because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An invalid message response was received. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-MQIPC_ADVANCE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to advance MQIPC queue because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The MQIPC initialization failed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-MQIPC_INITIALIZATION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> MQIPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-PEER_TABLE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> A peer table initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-PLATFORM_FAMILY_TYPE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The platform family type [chars] is invalid. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The platform family type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-RESOLVE_FRU </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to determine [chars] card because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The router failed to determine a FRU state. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-SERVICES_INITIALIZATION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to initialize general application services because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The system failed to initialize application services. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-SIGNAL_INITIALIZATION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to initialize signals because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The system failed to initialize signals. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-SLOTS_INITIALIZATION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to initialize chassis slot information because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The system failed to initialize the chassis slot information. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-SLOT_INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> A card absolute slot number cannot be determined for this chassis type </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An absolute slot number is invalid. This could be due to a software defect or incorrect IDPROM content. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-0-UIPEER_CREATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to create user interface peer. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The system failed to create a user interface peer. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-3-CHASFS_OBJECT_DESTROY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to destroy chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A chassis filesystem object that should have been destroyed was not destroyed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-3-CHASFS_PROPERTY_DESTROY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A chassis filesystem property that should have been destroyed was not destroyed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-3-LICENSE_SERVICE_SETUP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to setup the licensing proxy service </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> License Manager failed to set itself up as a proxy for licensable features. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-3-PEER_INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> A peer table entry has invalid state. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A peer table entry has an invalid state. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-3-RTU_UNINITIALIZED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> RTU not yet initialized: stack enabled [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> License manager has not initialized RTU, but manager got RTU enable/disable request </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No user action is necessary. Reloading might work </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-3-THROUGHPUT_LICENSE_APPLY_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Throughput license look-up failed due to '[chars]' </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This message is to notify the user that a license look-up did not succeed because license manager process could not be contacted. This is a rare case but is due to either a crashed license daemon(licensed) or it encountered an internal error. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No user action is necessary. However, it is possible that a re-boot of the box may correct this behavior. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-3-UDI_AUTH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Quack Unique Device Identifier authentication failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This chassis seems to be compromised or tampered with. UDI burned on to the Quack chip and the one read from chassis EEPROM do not match. It can also be a case of either EEPROM or Quack device failure. More details about which specific field failed to match are logged in license daemon log file (licensed_R0.log). </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> User immediately needs to contact Cisco support. This device appears to be tampered with or is a counterfeit device or had a system failure. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LMRP-6-THROUGHPUT_LICENSE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Throughput license [chars], throughput set to [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Status indicating whether throughput license is found and the corresponding througput the CPP hardware is configured to provide. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-csl </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No user action is necessary. This is an informational message indicating throughput configured. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LOADBALANCE_TRACE_MESSAGE-3-AP_SW_UPDATE_ERR_LOG_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> AP SW update [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> AP Software Update logging </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> AP software update failed. ISSU image upgrade or SMU patching could be aborted. The user needs to initiate ISSU upgrade/SMU patch again. If the error occured during manual operation, operation can be initiated again </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LOADBALANCE_TRACE_MESSAGE-5-AP_SW_UPDATE_LOG_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> AP SW update [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> AP Software Update logging </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LOADBALANCE_TRACE_MESSAGE-5-LB_LOG_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Loadbalancer Log : [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Generic loadbalancer message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LOADBALANCE_TRACE_MESSAGE-5-LB_NOTICE_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Loadbalancer : [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Loadbalancer informational message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-app-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> LUA_VM-2-INITIALIZATION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Cannot initialize the Lua Virtual Machine </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The Lua Virtual Machine is a critical component of the shell-manager process. It is used to render responses to user commands. If this component cannot be initialized then the shell-manager will be unable to process any commands directed at the IOS-XE daemons. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> The shell-manager process could not be started. Check the trace log files for more details as to why the virtual machine failed to initialize correctly. This may be an out of memory condition so rebooting the chassis may resolve the problem. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MAB-5-FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Authentication failed for client ([chars]) with reason ([chars]) on Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> MAB Authentication was unsuccessful. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MAB-5-RESULT_OVERRIDE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Authentication result overridden for client ([chars]) on Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Authentication result was overridden </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MAB-5-SUCCESS </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Authentication successful for client ([chars]) on Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> MAB Authentication was successful. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MATM-3-CONSISTENCY_CHECK_RESULT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> No Inconsistency detected for Address %02x:%02x:%02x:%02x:%02x:%02x, vlan [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Consistency checker execution completed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No Inconsistency detected </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MATM-3-HWERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Hardware [chars] failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A hardware API access error message occurred. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Find out more about the error by using the commands show platform matm recon_state and show tech-support and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MATM-3-INVALID_EVENT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> An invalid event :[dec] received in [chars], expected event:[dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> MATM feature received invalid event on it's event handler </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> The condition is being recovered, no action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MATM-3-MAC_INCONSISTENCY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Inconsistency detected: Address :%02x:%02x:%02x:%02x:%02x:%02x, Vlan [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> There is a difference between mac address entry in software and hardware </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Try clearing the mac or run recovery mechanism </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MATM-3-MAX_ENTRIES </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The maximum number of MAC addresses has been reached:[dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The maximum number of MAC entries that can be programmed has been reached. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> New MAC addresses will not be learned. Stop any redundant MAC incrementing traffic for extra streams. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MATM-3-RECONCILIATION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Reconciliation post switchover failed : [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Consistency check across modules shows inconsistency in data. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-l2 </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Find out more about the error by using the commands show platform matm recon_state and show tech-support and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_AVL_DB_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> DB Mismatch: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Previous joins and leaves have corrupted the database. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_CLIENT_DATA_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Client %02X%02X.%02X%02X.%02X%02X multicast data is NULL. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Internal multicast database client entry should contain multicast data when a multicast join request comes from below service layer </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_CLIENT_ENTRY_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Client %02X%02X.%02X%02X.%02X%02X does not exist in internal database. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> internal multicast database must contain the client entry when a multicast join request comes from below service layer </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_CLNT_ENT_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> (S,G) count is zero whereas multicast data of client %02X%02X.%02X%02X.%02X%02X is not NULL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> when client disassociates (S,G) count is zero but client's multicast entry is not NULL. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_CLTMAC_LOOKUP_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Mismatch between two database while [chars] mgid = [dec] client mac = %02X%02X.%02X%02X.%02X%02X </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Two different databases have different values for the client. Multicast functionality will be affected due to mismatch of database values. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_DETELE_AVL_MGID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Deletion of mgid [dec] from internal multicast databases failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mgid entry deletion from the internal database fails </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_GRP_JOIN_LEAVE_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] for client %02X%02X.%02X%02X.%02X%02X multicast group [chars], mgid [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failure occurred while handling multicast group join or leave. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_INSERT_MGID_FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> insertion of mgid into database failed for some unknown reason - for source [chars] - group [chars] - vlan [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Internal multicast database corrupted. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_IP_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] IP Value already inserted for mgid [dec] mismatches. saved value [chars] expected [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> the IP of the stored database and incoming database mismatches </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_MGID_CLIENT_TREE_DESTROY_FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Mgid [dec] client tree destroy in internal multicast database failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mgid client tree destroy in internal database failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_MGID_CLIENT_TREE_WALK_FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Mgid [dec] client tree walk in internal multicast database failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mgid client tree walk in internal database failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_MGID_DATA_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> There is some data mismatch between two databases for mgid [dec]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> some database in multicast code is having unexpected null data </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_MGID_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> mgid value mismatch in database value found [dec] - expected mgid [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> the stored mgid value in the database is not same as expected. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_MGID_NULL_DATA </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> multicast database is having unexpected [chars] NULL value for mgid [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> some database in multicast code is having unexpected null data </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_MGID_SGV_DATA_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> There is some data mismatch between two databases for source [chars] group [chars] vlan [dec] mgid [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> some database in multicast code is having unexpected null data </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_MOBILITY_HANDOFF_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [chars] mobility multicast handoff for client %02X%02X.%02X%02X.%02X%02X </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failure occurred while handling mobility multicast handoff. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_SG_MAXMGID_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Multicast group count [dec] is greater than maximum mgids [dec] per client for client %02X%02X.%02X%02X.%02X%02X </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This and further new mgid entries for this client will be ignored Multicast functionality will be affected for those mgids. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_SG_NONZERO_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] (S,G) count [dec] is greater than zero whereas client %02X%02X.%02X%02X.%02X%02X multicast data is NULL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Two different databases have different values for the client. Multicast functionality will be affected due to mismatch of database values. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-MCAST_SPAM_UPDATE_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] for mgid type [dec], client %02X%02X.%02X%02X.%02X%02X multicast group info [chars] to AP %02X%02X.%02X%02X.%02X%02X </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failure occurred while sending multicast info to AP. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-3-TASK_CREATE_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> ERROR: Failed to create client-multicast library </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An internal error occurred due to which the client multicast subsystem could not be initialized. APs may not be able to join the controller. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-4-MCAST_MOM_NOT_CONFIGURED_ON_MOM_ONLY_PLATFORM </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Multicast-over-Multicast (wireless multicast &lt;ipv4Addr&gt;/ipv6 &lt;ipv6Addr&gt;) is not configured on Multicast-over-Multicast Only platform. Wireless multicast will not work until MOM is configured </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Wireless multicast is configured without MOM on MOM-Only platform </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCAST_ERROR_MESSAGE-6-MCAST_MOM_CONFIG_CHANGE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Capwap multicast mode [chars] [chars]. IPv4 [[chars]:[chars]] and IPv6 [[chars]:[chars]] with Wireless multicast status [chars]. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Wireless capwap multicast mode changed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCG_APMGR_MESSAGE-3-APMGR_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error : [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> APMGR error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> mcg-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCG_APMGR_MESSAGE-5-AP_DISJOIN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> AP Name : [chars], MAC : [chars], Session : [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> AP disjoin information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> mcg-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCG_APMGR_MESSAGE-5-AP_JOIN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> AP Name : [chars], MAC : [chars], Session : [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> AP Join information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> mcg-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MCP_SYS-0-ASSERTION_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Assertion failed: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An internal state consistency check failed.Correct operation cannot be guaranteed, and the system has been halted. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDNS_SYSLOG-3-EXCESS_SERVICE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> number of responses([dec]) for query ([chars]) is limited to ([dec]) due to query response threshold </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An MDNS Service Query resulted in too many services in the response, user experience for MDNS may be suboptimal. This may also consume more CPU cycles </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> mdns-binos </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Check the service policy configuration and consider moving to a more restrictive location if the problem persists </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDNS_SYSLOG-3-EXCESS_SERVICE_WIDE_AREA_BONJOUR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Number of services in the response ([dec]) for query [chars] has exceeded threshold [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An MDNS Service Query resulted in too many services in the response, user experience for MDNS may be suboptimal and may take up more CPU </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> mdns-binos </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> re-check the service policy on the Wide area bonjour side and Controller. Move to more restrictive location filter if problem persists </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-NODE_ISSU_SIP_WAIT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Could not wait for [chars] to complete Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified linecard was performing a Minimal Disruptive Restart using node ISSU, however Minimal Disruptive Restart did not complete before the next operation needed to commence. This linecard was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or module OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-NODE_ISSU_SPA_WAIT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Could not wait for [chars] in [chars] to complete Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified module was performing a Minimal Disruptive Restart using node ISSU, however Minimal Disruptive Restart did not complete before the next operation needed to commence. This module was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or module OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-NO_ACTIVE_ESP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> No active ESP was found when initiating Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where no active ESP was found to continue forwarinding traffic during the Minimal Disruptive Restart. All requested linecards and or modules were reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or linecard OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-NO_SPAS_IN_SIP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> No Minimal Disruptive Restart compatible SPAs found in [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified linecard that was to undergo Minimal Disruptive Restart did not contain any compatible SPAs. This linecard was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or module OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-READ_COMPAT_INFO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to read valid Minimal Disruptive Restart compatibility information for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where either modules in or the specified linecard itself, was to undergo Minimal Disruptive Restart however valid compatibility information could not be read prior to commencing Minimal Disruptive Restart. If the linecard itself was to go through Minimal Disruptive Restart, it and the modules within it were reset as normal. If only modules were going through Minimal Disruptuve Restart, all modules were reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-READ_SIP_RESET </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to read a valid Minimal Disruptive Restart reset value for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where either modules in or the specified linecard itself, was to undergo Minimal Disruptive Restart however a valid SIP reset value could not be read. This linecard was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-RESTART_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to perform Minimal Disruptive Restart on [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified linecard or module failed to undergo a Minimal Disruptive Restart. This linecard or module was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-SIP_OFFLINE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] is not online to perform Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified linecard was to undergo Minimal Disruptive Restart however the linecard was not found to be online. The linecard was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or linecard OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-SOFTWARE_TRANSFER </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to receive upgrade software for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified linecard was to undergo Minimal Disruptive Restart however the linecard was not able to receive the upgrade software prior to commencing Minimal Disruptive Restart. The linecard was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-SPA_BAY_INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Could not perform Minimal Disruptive Restart on invalid [chars] in [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was invalid. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or module OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-SPA_IS_NOT_READY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] in [chars] is not ready to perform Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be ready. The module was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or module OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-SPA_NOT_FOUND </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] in [chars] could not be found to perform Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found. The module was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or module OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-SPA_OFFLINE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] in [chars] is not online to perform Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be online. The module was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or module OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-SPA_TYPE_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Could not perform Minimal Disruptive Restart on [chars] in [chars] due to a SPA type mismatch </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module's SPA type was found to be different to what was expected. The module was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or module OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-3-SPA_WAS_NOT_READY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] in [chars] was not ready to perform Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> An unexpected error has occured where the specified module was to undergo Minimal Disruptive Restart however the module was not found to be ready at the time it was checked. The module was reset was normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review the IOSd, RP and CC chassis manager logs for errors or module OIR. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-5-CARD_RESTART </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Minimal Disruptive Restart [chars] to acquire provisioned software </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The FRU specified was not running the currently provisioned software, which it will acquire on Minimal Disruptive Restart. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-5-SIP_UNSUPPORTED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] does not support Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The linecard specified was restarted during an Minimal Disruptive Restart, however it does not support this feature either because of its type or there are no SPA's that support Minimal Disruptive Restart inserted. This linecard was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No user action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDR-5-SPA_UNSUPPORTED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] does not support Minimal Disruptive Restart </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The module specified was restarted during an Minimal Disruptive Restart, however it does not support this feature either because of its type or software version. This module was reset as normal. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No user action is necessary. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDT_CONNECTION-6-STATE_CHANGED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Connection state changed (id [chars] - [chars]): [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The connection state has been changed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-mdt-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Notification for connection state changed. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDT_SUBSCRIPTION-4-EXCEEDED_ACTIVE_SUB_LIMIT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Active subscription limit exceeded (stream [chars], id [chars], client [chars]): [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified subcription will not be connected due to exceeding the maximum number of active subscriptions on this platform. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-mdt-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reduce the number of active subscriptions by either removing configured subscriptions or terminating dynamic subscriptions that are not needed. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDT_SUBSCRIPTION-4-INVALID_ARGUMENTS </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Subscription creation failed (stream [chars], id [chars], client [chars]): [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The value of the given parameter is invalid or not specified. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-mdt-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Correct the invalid parameter and try the subscription again. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDT_SUBSCRIPTION-4-NOT_SUPPORTED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Subscription creation failed (stream [chars], id [chars], client [chars]): [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The value of the given parameter is not supported. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-mdt-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Try the subscription again with a supported value. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDT_SUBSCRIPTION-4-OUTSIDE_LIMIT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Subscription creation failed (stream [chars], id [chars], client [chars]): [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The value of the parameter is outside of the allowable range. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-mdt-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Try the subscription again with a value within the allowable range. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDT_SUBSCRIPTION-4-RESUMED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Subscription resumed (stream [chars], id [chars], client [chars]): [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified subscription was resumed from run-time error. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-mdt-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Try to slow down the data source or check if the connection is stable. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDT_SUBSCRIPTION-4-TERMINATED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Subscription terminated (stream [chars], id [chars], filter [chars], client [chars]): [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified subscription was terminated due to run-time error. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-mdt-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Try the subscription again </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MDT_SUBSCRIPTION-4-XPATH_INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Subscription creation failed (stream [chars], id [chars], client [chars]): [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified XPath filter is invalid. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-mdt-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Correct the XPath filter and try the subscription again. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-3-MERAKI_INTFC_SETUP_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Meraki interface setup error: [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Initial meraki interface setup failed - cannot bringup config updater </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Retry reconfiguring service meraki connect </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-CONFIG_MONITOR_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Config Monitor ERR: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Config monitor err message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-CONFIG_MONITOR_NOTIF </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Config Monitor: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Config monitor message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-CONFIG_UPDATER_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Config Updater ERR: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Config Updater err message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-CONFIG_UPDATER_NOTIF </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Config Updater: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Config Updater message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-CURL_FETCH_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Curl Fetch ERR: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Curl Fetch error message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-MERAKI_FSM_START_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Meraki FSM failed to start </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Meraki mgrd FSM failed to start </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-MERAKI_RESET_NOTIFICATION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> : Reset Notification [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Reset recovery message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-MERAKI_RESET_RECOVERY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> : Reset recovery [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Reset recovery message </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-PRI_TUNNEL_STATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Primary Tunnel State: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Primary tunnel state change notification </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_MGRD-5-SEC_TUNNEL_STATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Secondary Tunnel State: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Secondary tunnel state change notification </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_NCMD-5-NODE_CERT_RENEW_STATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Node Cert Renew State: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Node Cert renew state change notification </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_NCMD-5-NODE_CERT_STATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Node Cert State: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Node Cert state change notification </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_NCMD-5-NODE_CLOUD_ID_STATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Node Cloud_ID State: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Node Cloud_ID state change notification </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MERAKI_NCMD-5-NODE_TOKEN_STATE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Node Token State: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Node Token state change notification </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> polaris-aurora </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MESH_DB_TRACE_MESSAGE-3-EWLC_MESH_DB_EXEC_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %% Error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Improper arguments or config </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Arguments to be changed </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MESH_DB_TRACE_MESSAGE-6-EWLC_MESH_DB_INFO_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %% Info: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Info level logs </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MESH_TRACE_MESSAGE-3-EWLC_MESH_AP_DISCONNECT_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %% Error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failed to Disconnect AP for Mesh config changes </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reboot the AP for the mesh configs to be applied </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MESH_TRACE_MESSAGE-3-EWLC_MESH_AP_RESET_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %% Error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failed to reboot AP for Mesh config changes </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reboot the AP for the mesh configs to be applied </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MESH_TRACE_MESSAGE-3-EWLC_MESH_EXEC_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %% Error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Improper arguments or config </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Arguments to be changed </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MESH_TRACE_MESSAGE-3-EWLC_MESH_PROFILE_CHANGE_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %% Error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mesh profile change for AP did not get Applied </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Reboot the AP for the mesh configs to be applied </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MESH_TRACE_MESSAGE-4-EWLC_MESH_DCA_INTERVAL_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> DCA interval is too long. Configure it to 10min to make sure algorithm will run </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The DCA algorithm might not run during that channel update period </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Configure DCA interval to a 10min period to make sure that the algorithm will run </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> ME_APMGR_TRACE_MESSAGE-2-EWC_APMGR_CFG_SYNC_FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to synchronize configuration to EWC-capable APs on the network </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failed to synchronize configuration to EWC-capable APs on the network </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> A switchover to the standby followed by reconfiguration is recommended. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> ME_APMGR_TRACE_MESSAGE-6-EWC_APMGR_RESET </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> AP Event: Controller Image Download is successful, reset AP mac [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Controller Image Download is successful, reset AP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-2-WLAN_CRIT_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> WLAN Error : [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Critical issue seen with WLAN config. Make a note of any recent changes made to the network or the device configuration which may have triggered this and proceed to the suggested action. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. It is suggested to collect archive traces and live process core to analyse the error. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-3-BUFF_ALLOC_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to allocate memory for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-3-BUFF_DEALLOC_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to deallocate memory for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-3-MSG_PAYLOAD_ALLOCATE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Cannot allocate [chars] for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-3-MSG_PAYLOAD_BUILD_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Cannot build [chars] for [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-3-MSG_PAYLOAD_BUILD_GENERAL_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Failed to build [chars]: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-3-MSG_PAYLOAD_PROCESS_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Cannot process [chars] for [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: [chars] received is missing payload [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-4-ANCHOR_RESP_LOCAL_DELETE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Export anchor required but internal error occurred (e.g.: out of resources), sending export anchor deny for: Wlan-Profile: [chars], Policy Profile: [chars], client mac: %02x:%02x:%02x:%02x:%02x:%02x </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Export anchor required but internal error occurred (e.g.: out of resources) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, it implies that internal error occurred and needs further debugging. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-4-ANCHOR_RESP_PROFILE_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Export anchor required but config is incorrect, sending export anchor deny mismatch for: Wlan-Profile: [chars], Policy Profile: [chars], client mac: %02x:%02x:%02x:%02x:%02x:%02x </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Export anchor required but config is incorrect: sending export anchor deny mismatch </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, it implies that configuration should be checked for wlan and policy profile </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MMIF_LOG-7-MSG_PAYLOAD_SIZE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The payload size has exceeded the limit. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Available buffer cannot hold IPV6 NDP pkt payload. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_APLIST_LOG-3-APENTRY_DEL_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Could not delete an AP from the AP list. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_APLIST_LOG-3-INVALID_APLISTUPD_RECVD </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Received an invalid ap-list-update from [chars]. Entries: [dec], Expected: [dec]. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_APLIST_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] message received is missing payload [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_APLIST_LOG-4-APENTRY_ADD_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Unable to create an ApList entry for AP %02x%02x.%02x%02x.%02x%02x. ApList table is full </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-0-MOBILITY_TASK_FAILED_TO_START </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] task could not be started. The system will be rebooted </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> The mobility services failed to start correctly </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-0-MSG_RECV_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars]: msg revd failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-0-QUEUE_CREATE_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars]: queue creation failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-1-MOBILITYUSER_STATECREATE_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Unable to create mobility state for user [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-1-USER_NOT_ALLOWED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Unable to allow user [chars] into the system. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Unable to allow the user into the system for the reported reason </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-2-INIT_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error while initializing mobility daemon. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Error while initializing mobility daemon </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this error is seen, it is recommended that the controller's mobility configuration be redone as it may have been lost. If you still require assistance, open a case with the Technical Assistance Center via the Internet or contact your Cisco technical support </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-BUFF_ALLOC_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to allocate memory for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-BUFF_DEALLOC_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to deallocate memory for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-CONFIGDOWNLOAD_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to send a config download [chars] paket to [dec].[dec].[dec].[dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failed to send a configdownload packet </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-DGRAM_SEND_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Unable to send [chars] to [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Unable to send a mobility packet </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-INVALID_PKT_RECVD </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Received an invalid packet from source endpoint: [chars]. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Please check mobility configuration to see if it needs correction. If the problem persists, open a case with the TAC via the Internet action, or contact your Cisco technical support representative and provide the representative with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PAYLOAD_ALLOCATE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Cannot allocate [chars] for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PAYLOAD_BUILD_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Cannot build [chars] for [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PAYLOAD_BUILD_GENERAL_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Failed to build [chars]: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PAYLOAD_DECODE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: [chars] cannot decode mobility payload/s for [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PAYLOAD_ENCODE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: [chars] cannot encode mobility payload/s for [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PAYLOAD_PROCESS_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Cannot process [chars] for [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: [chars] received is missing payload [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PROC_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Unable to process the received mobility message [chars] from [chars]. reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PROC_FAILED_GROUP_NAME_HASH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Pkt group name hash: [chars] Peer group name hash: [chars] [chars]. reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_PROC_FAILED_MAC_ADDR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Pkt MAC: %02x%02x.%02x%02x.%02x%02x Peer MAC: %02x%02x.%02x%02x.%02x%02x [chars]. reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-MSG_TIMER_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Timer error: failed to [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-RECV_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Unable to receive mobility message [chars] from [chars]. reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Unable to receive a mobility packet </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-3-SEND_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Unable to send [chars] to [chars]. Reason: [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Unable to send a mobility packet </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-4-MOBILITY_OUTGOING_MSG_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Invalid outgoing msg </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-7-MSG_PAYLOAD_SIZE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The payload size has exceeded the limit. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Available buffer cannot hold IPV6 NDP pkt payload. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_INFRA_LOG-7-MSG_PROC_UNEXISTING_CLIENT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Unable to process the received mobility message [chars] from [chars]. reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_STD_NO_ACTION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-2-MAX_SUPPORTED_CLIENTS_90PCT_EXCEEDED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> 90%% ([dec]) of maximum supported number of joined client [dec] exceeded </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Exceeded 90% of maximum supported client join limit </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-2-MAX_SUPPORTED_CLIENTS_EXCEEDED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Maximum supported number of joined clients [dec] exceeded </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Maximum supported number of joined clients exceeded. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-ANCHOR_GENERIC_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Anchor: [chars]. client mac: %02x:%02x:%02x:%02x:%02x:%02x </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Anchor has detected and error. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-BUFF_ALLOC_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to allocate memory for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-BUFF_DEALLOC_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to deallocate memory for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-MIP_READ_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars]. Encountered memory error, please report the error if you experience a crash. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-MSG_PAYLOAD_ALLOCATE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Cannot allocate [chars] for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-MSG_PAYLOAD_BUILD_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Cannot build [chars] for [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-MSG_PAYLOAD_BUILD_GENERAL_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Failed to build [chars]: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-MSG_PAYLOAD_ENCODE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: cannot encode mobility payload/s for [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-MSG_PAYLOAD_PROCESS_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: Cannot process [chars] for [chars]. Reason: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> %02x%02x.%02x%02x.%02x%02x: [chars] received is missing payload [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-3-MSG_TIMER_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] Timer: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-4-EXPORT_ANCHOR_DENY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Export anchor required, but received export anchor deny for: WLAN Profile: [chars], Client MAC: %02x:%02x:%02x:%02x:%02x:%02x, Error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Export anchor required: received export anchor deny </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, depending on the error code appropriate action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-4-RETRIES_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> MAC: %02x:%02x:%02x:%02x:%02x:%02x: All retries of [chars] (XID: [dec]) to [chars] have been exhausted </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> All retries for packet are exhaused </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-6-ANCHOR_GENERIC_INFO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Anchor: [chars]. client mac: %02x:%02x:%02x:%02x:%02x:%02x </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Anchor has detected a protocol issue and recovered. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-6-MAX_CLIENTS_PER_WLAN_REACHED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Maximum number of Clients on wlan [chars] with Limit: [dec] Reached </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Maximum number of Clients per wlan Join Limit Reached. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-6-MAX_CLIENTS_THRESHOLD_REACHED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Maximum number of Client Join Limit: [dec] Reached </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Maximum number of Client Join Limit Reached. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-6-MM_EXPORT_ANCHOR_FULL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Export Anchor not responding, back off condition set (Client MAC: %02x:%02x:%02x:%02x:%02x:%02x, AnchorIP: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSINFO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-6-WLAN_CLIENT_LIMIT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Client limit reached on [chars]. Denied client mac: %02x:%02x:%02x:%02x:%02x:%02x </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Client limit reached on wlan on anchor. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-7-EXPORT_ANCHORS_DOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> MAC:%02x:%02x:%02x:%02x:%02x:%02x: All Export-Anchors are down. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> All Export-Anchors are down. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, it implies that there is loss of network connectivity between the WLC and the export anchors for this guest LAN. It is recommended that the network and the status of the anchors be debugged for connectivity issues. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_LOG-7-MSG_PAYLOAD_SIZE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The payload size has exceeded the limit. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Available buffer cannot hold IPV6 NDP pkt payload. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-0-MULTICAST_GROUP_IP_SET_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error in [chars] while setting local mobility group multicast IP address [dec].[dec].[dec].[dec]. Please disable mobility multicast-mode if this error continues </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mobility is unable to use multicast for messaging </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-1-ANCHORS_DOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> All Export-Anchors are down </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> All Export-Anchors are down on WLAN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, it implies that there is loss of network connectivity between the WLC and the export anchors for this WLAN. It is recommended that the network and the status of the anchors be debugged for connectivity issues. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-1-KEEP_ALIVE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Mobility [chars] tunnel to peer [chars] changed state to [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mobility tunnel state change message. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-BUFF_ALLOC_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to allocate memory for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-BUFF_DEALLOC_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to deallocate memory for [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-INTFCHANGE_REGISTER_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to register callback for interface changes </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-INVALID_NONCE_RECVD </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Received an invalid Nonce-update from [chars]. [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-INVALID_PMKDEL_RECVD </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Received PMK-delete from [chars] with no Station address TLV. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-INVALID_PMKUPD_RECVD </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Received an invalid PMK-update from [chars]. [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-MEMBER_ADD_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Could not add Mobility Member. Reason: [chars], IP: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Could not add Mobility Member for the given reason. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-MEMBER_DEL_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Could not delete Mobility Member. Reason: [chars], IP: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mobility Member deletion from the list failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Please check if the mobility member to be deleted exists </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-MEMBER_UPDATE_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Could not update Mobility Member. Reason: [chars], IP: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Could not update Mobility Member for the given reason. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-MSG_PAYLOAD_RECEIVE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] message received is missing payload [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-MULTICAST_GROUP_SEND_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Unable to send multicast mobility message. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mobility is unable to use multicast for messaging </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-PEER_PING_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Mobility ping to [chars] rejected. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mobility ping rejected </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Please check the ping command issued </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-PEER_PING_VERSION_UNKNOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Mobility ping to [chars] rejected. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mobility ping version unknown </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Please check if the controllers in the mobility list can interOp and </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-PING_DROPPED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Drop [chars] ping from [chars]. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mobility ping response Dropped </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-PING_SEND_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to send a [chars] ping to [chars] . Reason: [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Failed to send a ping </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Please check mobility configuration to see if it needs correction </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-SOCK_INVALID_MULTICAST_ADDRESS </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Mobility group local multicast address has invalid setting: [dec].[dec].[dec].[dec]. Resetting it to 0.0.0.0 and disabling mobility multicast </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mobility multicast group address configuration was found invalid. It may have been corrupted during config transfer </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Configure the address again by using cmd: config mobility multicast-mode enable multicast_address </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-SOCK_OPER_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to [chars] a socket. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A Socket operation is failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-SOCK_SET_ADDRESS_OPTION_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to [chars] a socket. Reason: [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A Socket operation is failed. Multicast mode will not work for mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Try setting the local group multicast address again. If the same error is seen, disable the multicast-mode for mobility and </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-SYSTEM_IP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Peer IP conflicts with system IP [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Peer Ip is conflicting with System Management Ip. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-3-SYSTEM_MAC </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Member [chars] is configured with a MAC that conflicts with system mobility MAC addres (%02x%02x.%02x%02x.%02x%02x) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Peer MAC is conflicting with System Mobility MAC. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-4-DTLS_HANDSHAKE_FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] handshake failed for [chars] HB is down, need to re-initiate DTLS handshake </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Error during DTLS handshake </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-4-HB_MEMBER_ADD_BY_IP_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error adding Mobility member to heartbeat list (IP: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-4-HB_MEMBER_ADD_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error adding Mobility member to heartbeat list (MAC: %02x:%02x:%02x:%02x:%02x:%02x, IP: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-4-HB_MEMBER_DELETE_BY_IP_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error deleting Mobility member from heartbeat list (IP: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-4-HB_MEMBER_DELETE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error deleting Mobility member from heartbeat list (MAC: %02x:%02x:%02x:%02x:%02x:%02x, IP: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-4-HEARTBEAT_LIST_MEMBER_UPDATE_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error updating Mobility member IP in heartbeat list (MAC: %02x:%02x:%02x:%02x:%02x:%02x,, oldIP: [chars], newIP: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-4-MEMBER_DOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] path to mobility member [chars] is DOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A path to mobility member is DOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, it implies that there is loss of network connectivity between the WLC and one of its mobility peers. It is recommended that the network and the status of the peers be debugged for connectivity issues. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-4-PMTU_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Capwap path MTU discovery error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Mobility path MTU discovery failure </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-4-PMTU_SET_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to set path MTU to fast path for peer IP: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-6-HEARTBEAT_LIST_MEMBER_UPDATED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Updating Mobility member IP in heartbeat list (MAC: %02x:%02x:%02x:%02x:%02x:%02x,, oldIP: [chars], newIP: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSINFO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-6-MEMBER_ADDED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Adding Mobility member (IP: [chars]: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSINFO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-6-MEMBER_DELETED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Deleting Mobility member (IP: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSINFO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-6-MEMBER_UP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] path to mobility member [chars] is UP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A path to mobility member is UP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-6-MEMBER_UPDATED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Updating Mobility member (IP: [chars]: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSINFO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-6-MM_EXPORT_ANCHOR_FULL_RESET </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Export Anchor back off condition cleared (AnchorIP: [chars]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSINFO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-guest </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-6-PING_RECEIVER_ENTRY_DELETED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Deleted ping receiver entry ([chars]) from heartbeat list for WLAN ([dec]) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> LOG_EXPL_SYSINFO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MM_NODE_LOG-6-SOCK_SET_ADDRESS_OPTION </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Setting [chars] multicast group [chars] on the mobility sockets. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Multicast group membership was set on the socket. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> MOBILITYD_LOG-2-INIT_FAILED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error while initializing mobility daemon. [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Error while initializing mobility daemon </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-mobility </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this error is seen, it is recommended that the controller's mobility configuration be redone as it may have been lost. If you still require assistance, open a case with the Technical Assistance Center via the Internet or contact your Cisco technical support </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NDBMAN-3-CONFIG_COMMIT_FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Commit failed for feature '[chars]' from [chars]:[dec] via [chars] user [chars] session [dec], transaction-id [dec]i error [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A failed attempt to change running configuration was made via one of the model-based interfaces NETCONF/RESTCONF/GNMI. Configuration was successfully validated by the feature during the validation phase of the transaction but failed during the commit phase </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Check the device cnfiguration. Collect device logs. Reinitialize the model-based component </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NDBMAN-4-CONFIG_REJECT_W </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Config rejected by feature '[chars]' from [chars]:[dec] via [chars] user [chars] session [dec], transaction-id [dec] error [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A failed attempt to change running configuration was made via one of the model-based interfaces NETCONF/RESTCONF/GNMI. Either the feature validation logic rejected the config change as invalid or an error occured during an attempt to validate the config modification </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NDBMAN-5-ACTIVE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> All data providers active. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> All data providers active. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NDBMAN-5-CONFIG_I </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Configured feature '[chars]' from [chars]:[dec] via [chars] user [chars] session [dec], transaction-id [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A change to the running configuration was performed via one of the model-based interfaces NETCONF/RESTCONF/GNMI. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NDBMAN-5-MODEL_RPC_I </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> RPC '[chars]:[chars]' invoked from [chars]:[dec] via [chars] user [chars] session [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A model remote procedure call was performed via one of the model-based interfaces NETCONF/RESTCONF/GNMI. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NDBMAN-5-RESET </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> A data provider has stopped. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> At least one data provider has stopped. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Informational only. No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NDBUTIL-4-OUT_OF_RANGE_FOR_DECIMAL64_AND_FD </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Double (%1$s) with value (%2$lf) is out-of-range (-%3$ld to %3$ld, exclusive) for a Decimal64 with fraction-digits = %4$d. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The value of the EI double cannot be reliably converted to Yang Decimal64 with the specified fraction-digits with the proper precision, so the EI to Yang conversion is intentionally failing. The EI value should not be this big, so there's an error with the module setting the attribute's value. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Report an error to the Cisco engineering team responsible for the module that's setting the attribute. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_APPLY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> AP neighborhood based algorithm applied. [dec] number of APs have been load-balanced across WNCd instances. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> RF based AP neighborhood algorithm is applied </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, it implies that number of APs required load-balanced as per the load-balancing output </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_DONE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> AP clustering and WNCD assignment algorithm completed. [dec] number of AP neighborhoods formed and ready to load-balance across WNCD instances. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> RF based AP clustering formation is done and sub-neighborhoods have been allocated the WNCD instances </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, it implies that all AP can be loadbalanced by using exec apply CLI or reload of the controller </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_START </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Starting AP clustering and WNCD assignment algorithm. Total number of APs collected for calculation: [dec]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Notification to start the neighborhood calcultion </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, Neighborhood algorithm is in progress. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_TIMER_EVENT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> RRM based AP neighborhood algorithm cannot be started within 1 hour of system boot on calendar profile timer expiry event. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Calander profile start timer expiry event is ignored </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, it implies that AP neighborhood algorithm is not started on timer expiry event. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NEIGHBORHOOD_LOG-5-AP_NEIGHBORHOOD_UNSUPPORTED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> RF based AP neighborhood load-balancing is not applicable to this platform. Please unconfigure calendar profile from ap neighborhood global configuration. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Calander profile timer event callback handling error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> If this message occurs, it implies that a calander profile is attached to ap neighborhood config on an unsupported platform </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-DAD </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Dual Active detected: [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Dual Active detected print on console. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action. Action is only after recovery mode </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-DAD_RECOVERY_MODE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Dual Active detected: Switch going into recovery mode [chars].\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Dual Active detected print on console. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> This switch need to be reloaded once user finishes debugging </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-DAD_RECOVERY_RELOAD_ALERT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Switch is in recovery mode, needs Reload now. [chars].\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Switch is in recovery mode, needs Reload now </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> This switch need to be reloaded since some correction is noticed </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-DOMAIN_NUMBER_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Stackwise virtual domain number mismatch on stackwise virtual link [dec]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a stackwise virtual link is connected to a peer with a different domain number than the local switch </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> For the switch to form a stack please configure same domain numbers on both the switches </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-PORT_CONNECTION_STATUS_CHANGE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> PORT:[chars] changed state from [chars] to [chars].\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> FSS Stack Port status change message. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-PORT_CONN_DISCONNECTED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] on front side stack link [dec] connection has DISCONNECTED: [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a front side stack link has disconnected connection. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-PORT_CONN_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] on front side stack link [dec] connection is in ERR-DISABLE: [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a front side stack link has reached err-disable state. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-PORT_CONN_PENDING </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] on front side stack link [dec] connection is PENDING.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a front side stack link has a pending connection. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-PORT_CONN_READY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] on front side stack link [dec] connection is READY.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a front side stack link has a ready connection. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-PORT_CONN_TIMEOUT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] on front side stack link [dec] connection has TIMEOUT: [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a front side stack link has disconnected connection. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-PORT_LINK_DOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] on front side stack link [dec] is DOWN.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a front side stack link has come up. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-PORT_LINK_UP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] on front side stack link [dec] is UP.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a front side stack link has come up. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-STACK_LINK_DOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Front side stack link [dec] is DOWN.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a front side stack link has come up. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIF_MGR-6-STACK_LINK_UP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Front side stack link [dec] is UP.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> A port associated with a front side stack link has come up. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIM_XXD-3-DISK_ERROR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Error detected on disk [dec] in module [chars] in subslot [dec]/[dec]. [chars]. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Disk error detected in the SPA (NIM-SSD/NIM-HDD). Refer to comment for details. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Back-up any data and replace the disk. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIM_XXD-3-DISK_REMOVAL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> One or more disks in SPA ([chars]) in subslot [dec]/[dec] can not be detected. Please power down this SPA and insert disk(s). </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Disks have been removed from SPA </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Power down the SPA, insert disks and power up the SPA. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NIM_XXD-5-DISK_MONITOR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Disk [dec] in module [chars] in subslot [dec]/[dec] is detected but monitoring is not available. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Monitoring of disk in SPA (NIM-SSD/NIM-HDD) is unavailable. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Add a database file with monitoring information for this disk model and manufacturer. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NMSP_SYSLOG-3-NMSP_DB_LOCK_NOT_ACQUIRED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> NMSP client application is expected to acquire lock for NMSP local database before calling NMSP API: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Locking sequence for the DB's is defined in this application. The locking order of DB's needs to be followed as per the application set order, where local DB come first. NMSP client application must acquire local DB lock before calling NMSP API </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-nmsp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NMSP_SYSLOG-3-NMSP_HTTPS_ERROR_CONFIG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> nmspd cloud service config error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Configuration error prevented successful connection to CMX cloud service. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-nmsp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Check configuration of cmx cloud service, e.g. server URL and token. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NMSP_SYSLOG-3-NMSP_HTTPS_ERROR_CRYPTO </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> nmspd HTTPS error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Peer verification of CMX cloud service failed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-nmsp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Check that server certificate can be verified by root CA certificates in trustpool of crypto PKI. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NMSP_SYSLOG-3-NMSP_SSL_ERROR_CERT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> nmspd TLS certificate error: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Error validating TLS certificate for incoming CMX connection </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-nmsp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Check that certificates and SHA2 key are properly setup on eWLC. Contact TAC if issue persists. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NMSP_SYSLOG-3-NMSP_SSL_ERROR_DISCONNECT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> nmspd TLS disconnection: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Remote CMX connection over TLS protocol had been dropped. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-nmsp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Check connectivity with CMX, CMX service status and AAA configuration. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NMSP_SYSLOG-3-NMSP_SSL_ERROR_INTERNAL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> nmspd internal error occured when handling TLS connection: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Internal eWLC error prevented successful establishment of CMX connection over TLS protocol </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-nmsp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Check availability of the system resources of the eWLC controller: memory, open files, sockets. Contact TAC if issue persists </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NMSP_SYSLOG-5-NMSP_HTTPS_INTERFACE_NOTICE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> nmspd HTTPS info: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Wireless management interface notification. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-nmsp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NMSP_SYSLOG-5-NMSP_HTTPS_NOTICE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> nmspd HTTPS info: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This is an informational message. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-nmsp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NMSP_SYSLOG-5-NMSP_SSL_NOTICE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> nmspd TLS notice: [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This is an informational message. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> ewlc-nmsp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action required. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-1-DUAL_ACTIVE_CFG_MSG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Dual Active Detection [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Switch detected availability or unavailability of Dual Active Detection ports. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-1-EPA_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars]. The mis-match may caused by hardware failure or different EPA types.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The Standby EPA mismatch with Active EPA. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Need to make them match </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-1-FATAL_ERR </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Stack manager encountered an unrecoverable error. [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The stack manager process has encountered an unrecoverable error and the switch is being reloaded. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Please ensure valid switch numbers are being used. If you still believe there is an error in the system, please send the system report to a TAC representative </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-1-LIC_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> License level is [chars] and needs to be upgraded to [chars] for Stackwise Virtual to function.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Current Licnese level on active switch does not support Stackwise Virtual. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Need to be upgraded to supported license level </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-1-RELOAD </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Reloading due to reason [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified switch has received a reload request and is being reloaded. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-1-RELOAD_REQUEST </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Received reload request for [chars], reason [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified switches are being reloaded. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-1-STACK_MERGE_IGNORE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Stack Merge Ignored [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Switch detected multiple Active switches. But stack-merge is being ignored. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-4-SWITCH_ADDED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] has been added to the stack.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified switch has been added to the stack. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-4-SWITCH_REMOVED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] has been removed from the stack.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified switch has been removed from the stack. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-5-CHASSIS_ROLE_UPDATE_FAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Failed to Set [chars] Chassis [dec] chassis_role [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This is used to indicate that update to new role failed </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> This is a rare failure condition. Please reach out to TAC </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-5-FAST_RELOAD_DONE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Fast reload operation completed successfully on entire stack </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This is used to indicate that the fast reload on stack is complete. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> accsw-p-fsu </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action needed. This is not an error. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-ACTIVE_ELECTED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] has been elected ACTIVE.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified switch has been elected active. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-ACTIVE_READY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Active [chars] [dec] is ready.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The active switch is ready. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-CHASSIS_ADDED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] has been added to the stack.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified chassis has been added to the stack. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-CHASSIS_READY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] is ready.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified chassis is ready. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-CHASSIS_REMOVED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] has been removed from the stack.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified chassis has been removed from the stack. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-CHASSIS_REMOVED_KA </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] has been removed from the stack due to keepalive failure. \n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Chassis has been removed due to the keepalive failure. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-DISC_DONE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] has finished stack discovery.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified switch has completed stack discovery and is moving to the election phase. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-DISC_START </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] is starting stack discovery.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified switch is starting stack discovery. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-KA_MISSED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Keepalive missed for [dec] times for [chars] [dec] \n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Chassis has been removed due to the keepalive failure. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-STACK_LINK_CHANGE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Stack port [dec] on [chars] [dec] is [chars]\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified stack port has changed status. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-STANDBY_ELECTED </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] has been elected STANDBY.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified switch has been elected standby. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NODE_HDLR-6-SWITCH_READY </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] [dec] is ready.\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The specified switch is ready. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> NPI_L3TUNNEL_ERRMSG-3-MAX_TUNNEL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The maximum number of Tunnel has been reached\n </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> Hardware resource allocation has failed and the entry will not be programmed. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> New Tunnels will not be working as expected. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> ODM_SERVER_ERRMSG-3-ODM_TABLE_REGISTER_DB_NOT_CONFIG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Client ([chars]/[dec]) table [[chars]/[chars]] registration DB [[chars]] is not found in server configuration </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> ODM client is registering its monitored TDL database tables to ODM server daemon. But ODM server daemon doesn't have requested (consolidated) database information. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> ODM_SERVER_ERRMSG-3-ODM_TABLE_REGISTER_TABLE_NOT_CONFIG </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Client ([chars]/[dec]) table [[chars]/[chars]] registration table is not found in server DB [[chars]] configuration </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> ODM client is registering its monitored TDL database tables to ODM server daemon. But ODM server daemon doesn't have requested table information in consolidated database. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> ODM_SERVER_ERRMSG-4-ODM_TABLE_REGISTER_CONFIG_MISMATCH </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Client ([chars]/[dec]) table [[chars]/[chars]] registration table configuration (0x%x) mis-matched with server configuration (0x%x) </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> ODM client is registring its monitored TDL database tables to ODM server daemon. But ODM table configuration is not matched between client and server. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> OMPD-3-PEER_STATE_INIT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] peer [chars] state changed to Init </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This syslog is generated when OMP peer state changes to INIT </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> OMPD-3-STATE_DOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Operational state changed to [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This syslog is generated when Cisco SD-WAN Overlay Management Protocol (OMP) goes DOWN </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> OMPD-5-PEER_STATE_UP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] peer [chars] state changed to Up </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This syslog is generated when OMP peer state changes to UP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> OMPD-5-STATE_UP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Operational state changed to [chars] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This syslog is generated when Cisco SD-WAN Overlay Management Protocol (OMP) comes UP </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> OMPD-6-NUMBER_OF_VSMARTS </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> Number of vSmarts connected : [dec] </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This info log is generated whenever SD-WAN edge device either establishes (or) looses connection with SD-WAN Controller nodes </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> OMPD-6-PEER_STATE_HANDSHAKE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> [chars] peer [chars] state changed to Handshake </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> This syslog is generated when OMP peer state changes to HANDSHAKE </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> OOM-0-NO_MEMORY_RESET </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The system is completely out of available memory. The board will be reset. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The system has exhausted all available memory and the hardware component will be reset. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> Review other messages related to low memory states and see if those messages contain any information about an issue that can be addressed. If this problem persists, copy all the output from the console as well as the output of show tech-support, and provide the gathered information to your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__1 "> OOM-3-NO_MEMORY_AVAIL </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__3 "> The system is very low on available memory. Operations will begin to fail. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__4 "> The system has exhausted all available memory. It is not possible to continue stable operation. </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-k-to-o-syslogs_17161__entry__6 "> The system has exhausted all available memory and stable operation is no longer possible. </td> </tr> </tbody> </table> </section> </div>  <nav role="navigation" class="related-links"></nav>  </article> <article class="topic reference nested2" aria-labelledby="ariaid-title9" lang="en-US" id="r-p-to-t-syslogs_17161"> <h3 class="title topictitle3" id="ariaid-title9"> P to T </h3> <div class="body refbody"> <section class="section" id="r-p-to-t-syslogs_17161__d54e50906"> <table width="100%" border="1" class="table"> <caption></caption> <colgroup> <col style="width:37.334510150044125%"> <col style="width:8.8261253309797%"> <col style="width:16.504854368932037%"> <col style="width:8.8261253309797%"> <col style="width:8.8261253309797%"> <col style="width:19.68225948808473%"> </colgroup> <thead class="thead"> <tr> <th font-weight="bold" class="entry align-left" id="r-p-to-t-syslogs_17161__entry__1"> Facility-Severity-Mnemonic </th> <th font-weight="bold" class="entry align-left" id="r-p-to-t-syslogs_17161__entry__2"> Severity-Meaning </th> <th font-weight="bold" class="entry align-left" id="r-p-to-t-syslogs_17161__entry__3"> Message </th> <th font-weight="bold" class="entry align-left" id="r-p-to-t-syslogs_17161__entry__4"> Message-Explanation </th> <th font-weight="bold" class="entry align-left" id="r-p-to-t-syslogs_17161__entry__5"> Component </th> <th font-weight="bold" class="entry align-left" id="r-p-to-t-syslogs_17161__entry__6"> Recommended-Action </th> </tr> </thead> <tbody class="tbody"> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PAE_CORE_TEST-6-REPORT_ID </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Created report id: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Result of the test report request </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ui </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PAM_UPDB-3-NOENVIRONMENT_SET </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error setting user in application environment: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The user has succesfully authenticated, but the user information could not be saved to the application environment. The user session will not proceed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PAM_UPDB-3-NOPROMPT_READ </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error reading [chars] prompt: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The authentication module was unable to read the specified prompt file. The default prompt will be used. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PCGW_HA_LIB_MESSAGE-3-BULK_SYNC_STATE_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error: Bulk sync status : [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Bulk sync status Error message. TERMINATED - Bulk-sync terminated </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> pcgw-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PCGW_HA_LIB_MESSAGE-3-PCGW_CONFIG_SYNC_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error: pcgw config sync not complete. Reloading the PCGW! </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Switchover happens before pcgw config sync is complete! </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> pcgw-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PCGW_HA_LIB_MESSAGE-6-BULK_SYNC_STATE_INFO </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> INFO: Bulk sync status : [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Bulk sync status INFO message. COLD - Bulk-sync ongoing. CONFIG_DONE - critical DB sync complete. WARM - Most of the DB's synced. HOT - Bulk-sync completed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> pcgw-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PEER_SELECTION-5-EWC_PEER_SELECTION_ADD_EV </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ADD event: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Reports an important HA peer (a.k.a. standby) selection ADD event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PEER_SELECTION-5-EWC_PEER_SELECTION_PREFER_EV </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Preferred master event: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Reports an important HA peer (a.k.a. standby) selection preferred master event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PEER_SELECTION-5-EWC_PEER_SELECTION_REMOVE_EV </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> REMOVE event: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Reports an important HA peer (a.k.a. standby) selection REMOVE event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PEER_SELECTION-5-EWC_PEER_SELECTION_SELECT_EV </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> SELECT event: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Reports an important HA peer (a.k.a. standby) selection SELECT event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM-2-S1_ASIC_FABRIC_BW_ABOVE_THRESHOLD </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> S1 ASIC EVENT: The number of fabric ports in the S1 ASIC [dec] are above the system threshold.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Silicon one ASIC fabric port threshold event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the fabric info for the S1 ASIC </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM-2-S1_ASIC_FABRIC_BW_BELOW_THRESHOLD </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> S1 ASIC EVENT: The number of fabric ports in the S1 ASIC [dec] are below the system threshold.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Silicon one ASIC fabric port threshold event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the fabric info for the S1 ASIC </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM-2-S1_ASIC_THROTTLING_DISABLE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> S1 ASIC EVENT: S1 ASIC [dec] temperature is back to normal. Traffic throttling is disabled now.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Silicon one ASIC overheating event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Copy the message exactly as it appears on the console or in the system log </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM-2-S1_ASIC_THROTTLING_ENABLE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> S1 ASIC EVENT: A high temperature condition is detected in S1 ASIC [dec]. The system will automatically enable traffic throttling in an attempt to restore temperatures and prevent permanent damage to the ASIC. Traffic drops are expected in this scenario and normal traffic behaviour will resume after the ambient ASIC temperatures are restored.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Silicon one ASIC overheating event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the ambient temperature of the room and check for blockages in airflow </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM-3-ELEMENT_CRITICAL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars]: [chars] value [chars] [chars] critical level [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Shell Manager monitors the health of each board and emits an error message when a value has passed a critical level. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Reduce static and dynamic loads on the system by reducing the number of elements in the configuration or by limiting the capacity for dynamic services. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM-3-ELEMENT_TMPFS_CRITICAL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars]: TMPFS value [dec]%% above critical level [dec]%% </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Shell Manager monitors the tmpfs usage of each board and emits an error message when a value has passed warning level. The critical level is computed based on total DRAM memory. Currently the critical level is 50% of total DRAM memory </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Emit syslog message with current tmpfs usage, warning level along with location of the board in which the error is happening </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM-3-ELEMENT_TMPFS_WARNING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars]: TMPFS value [dec]%% above warning level [dec]%% </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Shell Manager monitors the tmpfs usage of each board and emits an error message when a value has passed warning level.The warning level is computed based on total DRAM memory. Currently the warning level is 40% of total DRAM memory </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Emit syslog message with current tmpfs usage, warning level along with location of the board in which the error is happening </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM-4-ELEMENT_WARNING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars]: [chars] value [chars] [chars] warning level [chars]. [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Shell Manager monitors the health of each board and emits a warning message when a value has passed a critical level. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Reduce static and dynamic loads on the system by reducing the number of elements in the configuration or by limiting the capacity for dynamic services. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM-5-RESETCARD </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] reset to acquire provisioned software </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The linecard specified was not running the currently provisioned software, which it will acquire on restart. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PLATFORM_MGR-1-PLATMGR_INIT_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Platform Manager: [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Platform Manager Initialization has failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Find out more about the error by using the show tech-support privileged EXEC command and by copying the error message exactly as it appears on the console or system log and entering it in the Output Interpreter tool. Use the Bug Toolkit to look for similar reported problems. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-0-PROCESS_NOTIFICATION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The process lifecycle notification component failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The process lifecycle notification component failed, preventing proper detection of a process start and stop. This problem is likely the result of a software defect in the software sub-package. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Note the time of the message and investigate the kernel error message logs to learn more about the problem and see if it is correctable. If the problem cannot be corrected or the logs are not helpful, copy the error message exactly as it appears on the console along with the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-0-PROCFAILCRIT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> A critical process [chars] has failed (rc [dec]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A process important to the functioning of the router has failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Note the time of the message and investigate the error message logs to learn more about the problem. If the problem persists, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support with the gathered information. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-PROCFAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The process [chars] has failed (rc [dec]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The process has failed as the result of an error. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-PROCFAILOPT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> An optional process [chars] has failed (rc [dec]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A process that does not affect the forwarding of traffic has failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Note the time of the message and investigate the kernel error message logs to learn more about the problem. Although traffic will still be forwarded after receiving this message, certain functions on the router may be disabled as a result of this message and the error should be investigated. If the logs are not helpful or indicate a problem you cannot correct, copy the error message as it appears on the console and the output of show tech-support and provide the information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-PROCFAIL_IGNORE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] process exits and failures are being ignored due to debug settings. Normal router functionality will be affected. Critical router functions like RP switchover, router reload, FRU resets, etc. may not function properly. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A process exit or failure is being ignored due to the user-configured debug settings. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> If this behavior is desired and the debug settings are set according to the user's preference, no action is needed. If the appearance of this message is viewed as a problem, change the debug settings. The router is not expected to behave normally with this debug setting. Functionality like SSO switchover, router reloads, FRU resets, etc. will be affected. This setting should only be used in a debug scenario. It is not normal to run the router with this setting </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-PROCHOLDDOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The process [chars] has been helddown (rc [dec]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The process was restarted too many times with repeated failures and has been placed in the holddown state. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-PROC_BAD_COMMAND </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Non-existent executable or bad library used for process [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The executable file used for the process is missing or a dependent library is bad </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Make sure that the named executable is present and dependent libraries are good </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-PROC_BAD_EXECUTABLE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Bad executable or permission problem with process [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The executable file used for the process is bad or has permission problem </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Make sure that the named executable is replaced with correct executable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-PROC_EMPTY_EXEC_FILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Empty executable used for process [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The executable file used for the process is empty </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Make sure that the named executable is of non-zero size </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-PROC_RESTART_CNT_EXCEEDED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The process [chars] restart count ([dec]) has exceeded the configured limit ([dec]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The process was restarted many times and has exceeded the configured limit. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> This message will appear with other messages related to the process. Check the other messages to determine the reason for the failures and see if corrective action can be taken. If the problem persists, copy the error messages and the output of show platform software tech-support into a plaintext file and contact Cisco technical support. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-RELOAD_FRU_IGNORED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> All [chars]/[dec] reloads are being ignored. This is being done for debugging purposes and will be changed at a later time to allow the reload. Critical router functions like RP switchover, router reload, FRU resets, etc. may not function properly. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A supervisor failure is being ignored due to debugging purposes. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> This will be removet at a later point in time </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-RELOAD_RP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Reloading: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The RP is being reloaded </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-RELOAD_RP_SB_NOT_READY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Reloading: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The RP is being reloaded since there is no ready standby instance </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Make sure this is not due to an error condition </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-RELOAD_SYSTEM </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Reloading: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The system is being reloaded </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-3-RPSWITCH </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RP switch initiated. Critical process [chars] has failed (rc [dec]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A RP switchover has been initiated due to a critical fault </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Make sure this is not due to an error condition. If it is due to an error condition, collect debug information like all console output and log files </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-5-EXITACTION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Process manager is exiting: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The process manager is exiting </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Make sure this is not due to an error condition. If it is due to an error condition, collect information requested by the other log messages </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-6-PROCSHUT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The process [chars] has shutdown </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The process has gracefully shutdown. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No user action is necessary. This message is provided for informational purposes only. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-6-PROCSTART </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The process [chars] has started </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The process has launched and is operating properly. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No user action is necessary. This message is provided for informational purposes only. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-6-PROCSTATELESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The process [chars] is restarting stateless </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The process has requested a stateless restart. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No user action is necessary. This message is provided for informational purposes only. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PMAN-6-PROC_PATCH </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Process [chars] restarted to apply/remove a patch </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Process will be relaunched to apply/remove a patch </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-chassismgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No user action is necessary. This message is provided for informational purposes only. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> POLICY-3-DATA_POLICY_COMMIT_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Data policy commit failure error, reason: [chars] ([chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This error syslog is generated when OMP daemon is not able to commit data policies config, received from SD-WAN Controller, into config database. This can happen when there multiple commits (writes) happening in parallel. SD-WAN edge device will not be able to apply centralized data policies to traffic </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required, the system should recover after sometime when OMP daemon would retry committing data policy config into CDB </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> POLICY-3-TAG_INSTANCES_COMMIT_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Tag instances commit failure error, reason: [chars] ([chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This error syslog is generated when OMP daemon is not able to commit tag instances config, received from SD-WAN Controller, into config database. This can happen when there multiple commits (writes) happening in parallel SD-WAN edge device will not be able to apply centralized data policies to traffic </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required, the system should recover after sometime when OMP daemon would retry committing tag instance config into CDB </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> POLICY-5-EMPTY_POLICY_FROM_PEER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Using empty policy from peer [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when Cisco SD-WAN Controller does not push (or) removes centralized data policy from cEdge device </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> POLICY-5-NO_POLICY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Not using any policy </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when there are no OMP connections to Cisco SD-WAN Controller and Graceful Restart timer has also expired. Existing centralized data policy is removed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> POLICY-5-POLICY_FROM_PEER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Using policy from peer [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated whenever data-policy config received from Cisco SD-WAN Controller is programmed into data path </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> vip-omp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PRELIB_DL-3-UNREGISTERED_DLOPEN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Unregistered request to dlopen library [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The program is attempting to dynamically open a library that has not been explicitly listed on its list of dynamically opened libraries. This represents a potential security threat as well as creates potential run-time instabilities </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> File a DDTS against the listed program to register the library in question. If this was an unexpected call to dlopen then the source of the call should be root-caused and closed </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-3-DMI_DIR_CREATE_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: Failed to create directory: [chars] ([chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An error has occurred when attempting to create a directory. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Log a message </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-3-DMI_DIR_DELETE_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: Failed to delete directory: [chars] ([chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An error has occurred when attempting to delete a directory. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Log a message </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-3-DMI_FILE_CREATE_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: Failed to create file: [chars] ([chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An error has occurred when attempting to create a file. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Log a message </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-3-DMI_FILE_DELETE_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: Failed to delete file: [chars] ([chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An error has occurred when attempting to delete a file. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Log a message </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-3-SD_ROUTING_DMI_REQUIRED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/SD-ROUTING: Please configure netconf-yang to activate the sd-routing feature </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> SD-Routing depends upon DMI </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cntrl-mng-rtg </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-DMI_NOTIFY_NETCONF_START </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: netconf-yang server has been notified to start </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A specific informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-DMI_NOTIFY_NETCONF_STOP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: netconf-yang server has been notified to stop </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A specific informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-DMI_NOTIFY_RESTARTING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: netconf-yang and/or restconf will now be restarted, and any sessions in progress will be terminated </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A specific informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-DMI_NOTIFY_RESTCONF_START </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: restconf server has been notified to start </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A specific informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-DMI_NOTIFY_RESTCONF_STOP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: restconf server has been notified to stop </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A specific informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-DMI_NOTIFY_USER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/DMI: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ddmi-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-PSID_NOTIFY_SYSTEM_INTEGRITY_START </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> SYSTEM INTEGRITY: pistis daemon has been notified to start </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A specific informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-PSID_NOTIFY_SYSTEM_INTEGRITY_STOP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> SYSTEM INTEGRITY: pistis daemon has been notified to stop </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A specific informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-SD_ROUTING_NOTIFY_START </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/SD-ROUTING: SD-Routing server has been notified to start </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A specific informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cntrl-mng-rtg </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PSD_MOD-5-SD_ROUTING_NOTIFY_STOP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> PSD/SD-ROUTING: SD-Routing server has been notified to stop </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A specific informational message from psd_mod </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cntrl-mng-rtg </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Not applicable </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTHUTIL-3-EVENT_HANDLER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Task [chars] has no [chars] event handler </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The task specified has failed to install a handler for the specified event. This implies that the event has been dropped. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTHUTIL-3-SCHED_EMPTY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Scheduler has no tasks available </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Pth scheduler has detected that there is no task available to run. This is an error condition for the process itself is a task. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTHUTIL-3-SCHED_FD_OVERFLOW </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Scheduler has more than [dec] FDs </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The are too many FDs for the Pth scheduler. This is an error condition for the process itself. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTHUTIL-3-STACK_OVERFLOW </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Task [chars] stack overflow </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A Pth task has overflowed its stack. This has been detected by the Pth scheduler and reported. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTHUTIL-3-TIMER_THRASHING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Timer [chars] is thrashing on [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Pth scheduler has detected that an event has remained on the ready queue after being notified of requiring processing. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTHUTIL-3-TIMER_UPDATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Timer [chars] update of [chars] not updated [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The attempt to update a watched timer has failed due to either the timer not existing or the inability to move the timer to its new position post update. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-CHASFS_OBJECT_CREATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The hardware failed to create a chassis filesystem object. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-CHASFS_OBJECT_NOT_PRESENT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] not present. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-CHASFS_OBJECT_WATCH </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to watch chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A chassis filesystem object was not watched because of the reason stated in the error message. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-CHASFS_PROPERTY_CREATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to create chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A chassis filesystem property was not properly created. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-CHASFS_PROPERTY_GET </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to read chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A chassis filesystem property was not properly read by the system. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-CHASFS_PROPERTY_NOT_PRESENT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Expected chassis filesystem object [chars] property [chars] not present. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-CHASFS_PROPERTY_SET </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to write chassis filesystem object [chars] property [chars] because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A chassis filesystem property failed to write. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-IPC_CONNECTION_INVALID </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> An IPC connection has invalid state. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-IPC_CONNECT_MASTER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> IPC connection to the active RSP failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> IPC connection to the active RSP failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-IPC_INITIALIZATION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> IPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> IPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-MESSAGE_REGISTER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to register with active RSP because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The active RSP failed to register. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-MESSAGE_RELAY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to relay a message because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Failed to relay a message. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-MESSAGE_RESPONSE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> An invalid message response was received because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An invalid message response was received. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-MQIPC_ADVANCE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to advance MQIPC queue because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The MQIPC initialization failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-MQIPC_INITIALIZATION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> MQIPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-PEER_TABLE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> A peer table initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-0-RESOURSE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Resource allocation failed in [chars] because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The system is unable to allocate the requested resource. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, this message is seen as a result of a temporary resource issue. Retry the request for the resource when the system is experiencing lower traffic volumes. If the message persists, reload the router using the reload command. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-3-CHASFS_OBJECT_DESTROY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to destroy chassis filesystem object [chars] because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A chassis filesystem object that should have been destroyed was not destroyed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> PTPD-3-CHASFS_PROPERTY_DESTROY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A chassis filesystem property that should have been destroyed was not destroyed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr900-ptp </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_CLIENT_POLICY_AP_INSTALL_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Failed to install policy: [chars] for Client: %02x%02x.%02x%02x.%02x%02x on AP: [chars] with status: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Client policy install on AP failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_CLIENT_POLICY_AP_SEND_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: For Client mac %02x%02x.%02x%02x.%02x%02x, failed to send policy [chars] to AP due to reason: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Error Binding Client Policy. Policy not sent to AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_CLIENT_POLICY_AP_UNINSTALL_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Failed to uninstall policy: [chars] for Client: %02x%02x.%02x%02x.%02x%02x on AP: [chars] with status: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Client policy unbind operation on AP failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_CREATE_POLICY_DB_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Unable to allocate resources for QoS Policy Content DB </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Internal Error. Unable to allocate resources for QoS Policy Content DB </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_DOT11_CLIENT_RECORD_NOT_FOUND </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Failed to get dot11 client record for Client: %02x%02x.%02x%02x.%02x%02x </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> QoS get function for dot11 client record failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-client </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_INVALID_POLICY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Policy [chars] is invalid in [chars] direction for vapid:[dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> QoS policy validation failed. Policy will not be installed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_MEM_ALLOC_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error: Failed to allocate memory [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An internal error occurred due to which memory allocation failed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_MODIFY_POLICY_DB_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Unable to modify QoS Policy due to Reason:[chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Internal Error. Unable to modify QoS Policy Content in DB </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_MSG_BLKLIST_CLIENT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Blacklisting client %02x%02x.%02x%02x.%02x%02x. Error installing client QOS policy: [chars] in [chars] direction. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Failure occured while installing QoS client policy. Client will be deleted. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_POLICY_EXCEED_MAX </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [dec] policy maps sent to AP [chars], exceeds the recommended [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Number of policies exceeds limit warning. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_POLICY_MISSING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Policy [chars] in [chars] direction for vapid:[dec] has no content </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> QoS policy validation failed. Policy will not be installed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_SSID_INVALID_POLICY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Policy [chars] is invalid in [chars] direction for vapid:[dec]. Once the policy is modified, the bssid needs to be reset before the new policy-map definition can take effect </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> QoS BSSID policy validation failed. Policy will not be installed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_SSID_POLICY_BIND_ON_AP_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Failed to bind SSID policy on AP: [chars] for wlan: [dec], Slot id: [dec] in [chars] direction with status: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> SSID policy bind operation failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-3-QOS_SSID_POLICY_UNBIND_ON_AP_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ERROR: Failed to unbind SSID policy on AP: [chars] for wlan: [dec], Slot id: [dec] in [chars] direction with status: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> SSID policy unbind operation on AP failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> QOS_ERROR_MESSAGE-6-QOS_HA_NO_BSSID_RECORD_SYNC_AP_DELETE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Deleting AP %02x%02x.%02x%02x.%02x%02x because BSSID record sync for slotId [dec] wlan_id [dec] pm_dir [chars] failed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> QoS BSSID record sync pre-switchover failed. Hence deleting the AP. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-3-ALL_SOURCE_PORT_EXHAUSTED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] : Dynamic socket pool limit reached Max : [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> All Source ports are exhausted </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-3-ALL_SOURCE_PORT_EXHAUSTED_AFTER_CLEANUP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] : Dynamic socket pool limit is still at Maximmum [dec] after clean up </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> All Source port are exhausted even after cleanup </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-3-BUFFER_OVERFLOW </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Radius I/O buffer has overflowed for [chars] with length [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An unusually large number of RADIUS attributes has caused AAA to overflow its RADIUS I/O buffer. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-3-RADIUS_PARSE_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Radius Parse FAIL due to op decode/bad packet </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> When Radius Parse response op decode/bad packet </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-3-RADIUS_TIMER_FAILED_TO_START </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to start radius timer. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Radius timer failed to start </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-3-RADIUS_TIMER_FAILED_TO_STOP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to stop radius timer. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Radius timer failed to stop </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-3-SECRETDEFINEFAILED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Key definition ignored. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The user is attempting to store either a corrupted shared secret or memory allocation failed during secret definition. Any existing shared secret will be preserved. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-3-SOCKET_OPERATION_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Cannot open UDP socket for service [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The router is unable to open a socket for UDP communications by the indicated service. Most of the time another service might be using the same port. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-6-ALLDEADSERVER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Group [chars]: No active radius servers found. Id [dec]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This error message occurs when all the servers configured in a server group are found to be unresponsive. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-6-BADATTRLIST </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Unable to process attribute list. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The attribute list is syntactically incorrect. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-6-INVALID_PACKET </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Invalid packet posted to RADIUS. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Radius not able to process a packet as it is invalid </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-6-RADIUS_ALIVE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RADIUS server [chars]:[dec],[dec] is being marked alive. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A RADIUS server that previously was not responding has responded to a new request or the deadtimer has expired. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADIUS_AUDIT_MESSAGE-6-RADIUS_DEAD </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RADIUS server [chars]:[dec],[dec] is not responding. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The server might not be available to serve request. server has not responded to repeated requests. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-aaa </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_DTLSC_DTLS_REPLAY_ATTACK </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> DTLS replay attack for hostname: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Detected DTLS replay attack </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_DTLSC_EXT_2_DTLS_SESSION_ESTABLISHED_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> User ID: [chars] Failure to establish a DTLS session with RadSec server, reason: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Failure to establish a DTLS session with RadSec server </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_RADSEC_SERVER_CERTIFICATE_VALIDATION_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RADSEC server certificate validation failed with server [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> RADSEC server certificate validation failed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_RADSEC_SERVER_IDENTITY_CHECK_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RADSEC server identity check failed with server [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> RADSEC server identity Check failed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-3-FIPS_AUDIT_FCS_TLSC_EXT_2_TLS_SESSION_ESTABLISHED_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> User ID: [chars] Failure to establish a TLS session with RadSec server, reason: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Failure to establish a TLS session with RadSec server </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSC_DTLS_NEGOTIATED_CIPHER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Negotiated Cipher is [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Negotiated Cipher during RADSEC HS SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSC_DTLS_SESSION_CLOSED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RADSEC DTLS connection closed with peer [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> RADSEC DTLS connection closed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_DTLSC_DTLS_SESSION_ESTABLISHED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RADSEC DTLS connection established with peer [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> DTLS session established message after RADSEC HS SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_TLSC_TLS_SESSION_CLOSED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RADSEC TLS connection closed with peer [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> RADSEC TLS connection closed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RADSEC_AUDIT_MESSAGE-6-FIPS_AUDIT_FCS_TLSC_TLS_SESSION_ESTABLISHED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RADSEC TLS connection established with peer [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> TLS session established message after RADSEC HS SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-qos </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> REGISTRY-3-FASTCASE_OUT_OF_BOUNDS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Attempt made in [chars] to register with out of bounds key </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> In the FASTCASE registry the key has to be smaller than the size specified when the registry was created. This message indicates that an attempt was made to register with a key which is out of bounds. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> REGISTRY-3-SEQ_LIST_OVERWRITE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Attempt to overwrite a set sequence function ([chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A single function can be set as a callback for a specified sequence number for a sequenced list registry. This message indicates that an attempt to set a new callback has failed because a callback function has already been set for this sequence number. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> REGISTRY-3-STUB_CHK_OVERWRITE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Attempt made to overwrite a set stub function in [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A single function can be set as a callback for when a stub with check registry is invoked. This message indicates that an attempt to set a new callback has failed because a callback function has already been set. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RFMGR_SYSLOG-4-DCA_CHANNEL_LIST_EMPTY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The DCA Channel list is empty for rf profile [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> DCA Channel list is empty It affects Channel Assignment to AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Please add channels to DCA List </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RFMGR_SYSLOG-4-MULTI_BSSID_PROFILE_NOT_FOUND </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Invalid Multi bssid profile [chars], applying default-multi-bssid-profile </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Invalid multi-bssid-profile is applied, 802.11ax specific payloads are not pushed to AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Please assign a valid Multi bssid profile </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RFMGR_SYSLOG-4-NO_REM_NON_AUTO_RF_CHAN_DCA </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> WARNING: RF Profile [chars] - Deleting channel [dec] from remove channel list, please add the channel to allowed channel list directly for adding it to DCA Used/Allowed channel list. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Deleting channel from remove channel list adds it to DCA Used/Allowed channel list, but the right way of adding a channel to DCA Used/Allowed channel list is to add the channel directly to allowed channel list by not adding it to remove channel list and then deleting. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Please add the channel directly to allowed channel list for making it part of DCA Used/Allowed channel list </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-GW_REACHABLE_ACTIVE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Gateway reachable from Active </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Gateway reachable from Active </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-GW_REACHABLE_STANDBY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Gateway reachable from Standby </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Gateway reachable from Standby </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-GW_UNREACHABLE_ACTIVE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Gateway not reachable from Active </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Gateway not reachable from Active </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-GW_UNREACHABLE_STANDBY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Gateway not reachable from Standby </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Gateway not reachable from Standby </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RMI_ACTIVE_RECOVERY_MODE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Going to Active(Recovery) from Active state </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Going to Active(Recovery) From Active </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RMI_GW_DECISION_DEFERRED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> High CPU utilisation on active or standby, deferring action on gateway-down event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> High CPU utilisation on active or standby, deferring action on gateway-down event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RMI_LINK_DOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The RMI link is DOWN. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The redundancy mgmt intf link was down. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RMI_LINK_UP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The RMI link is UP. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The redundany mgmt intf link came up </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RMI_STBY_REC_TO_STBY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Going from Standby(Recovery) to Standby state </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Going from Standby(Recovery) to Standby on GW reachable </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RMI_STBY_TO_STDBY_REC </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Going from Standby to Standby(Recovery) state </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Going from Standby to Standby(Recovery) on GW unreachable </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RMI_STBY_TO_STDBY_REC_REASON </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Going from Standby to Standby(Recovery) state, Reason: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Going from Standby to Standby(Recovery) on RP Down event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RMI_STDBY_REC_TO_ACTIVE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Going from Standby(Recovery) to Active state </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Going from Standby(Recovery) to Active on RP DOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RP_LINK_DOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Setting RP link status to DOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> RP link status set to DOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RIF_MGR_FSM-6-RP_LINK_UP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The RP link is UP. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The redundany port link came up </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RLDP_INITIATE_MESSAGE-6-EWLC_RLDP_INITIATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RLDP initiate [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> General ewlc RLDP initiate startup status </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RM_ERRS-2-ERR_FREE_MEM_CRITICAL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Insufficient free memory for service to work: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Insufficient free memory for service to handle new connection. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-htx </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Disable not required features. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RM_ERRS-4-ERR_INSUFFICIENT_FREE_MEM </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Insufficient free memory [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Free memory is lesser than configured for service. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-htx </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Disable not required features. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RM_ERRS-6-ERR_RECOVERED_FREE_MEM </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Recovered, sufficient free memory available [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Required free memory is available now for the service. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-htx </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is requried </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-ADHOC_AUTOCONTAIN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Adhoc rogue AP with MAC address [chars] has been automatically contained as per WPS policies. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Adhoc Rogue has been automatically contained </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-ADHOC_AUTOCONTAIN_CLEAR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Auto-containment for adhoc rogue AP with MAC address [chars] has been stopped. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Adhoc Rogue auto-containment has been stopped </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-AP_AUTOCONTAINED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue AP with MAC address [chars] has been automatically contained as per WPS policies </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Rogue AP has been auto-contained </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-AP_AUTOCONTAINED_CLEARED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Automatic containment for rogue AP with MAC address [chars] has been cleared. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Rogue AP autocontainment has been stopped </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-AP_BEING_CONTAINED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Managed AP [chars] with radio MAC [chars] slot [dec] is contained by another AP. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A managed AP is contained by another AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-AP_BEING_CONTAINED_CLEAR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Managed AP [chars] with radio MAC [chars] slot [dec] is no longer contained by another AP. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A managed AP is no longer contained by another AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-AP_CONTAINED_BY_RULE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue AP with MAC address [chars] has been contained due to rule [chars] with containment level [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Rogue AP has been contained due to a rule match </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-AP_HONEYPOT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Potential Honeypot AP detected with Rogue AP MAC [chars] with SSID [chars] by AP with Radio MAC [chars], slot [dec]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Potential Honeypot AP detected </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-AP_HONEYPOT_CLEAR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Potential Honeypot AP MAC address [chars] is cleared. This Rogue AP is no longer advertising an SSID that is configured on this controller. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Potential Honeypot AP cleared </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-AP_IMPERSONATION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Impersonation of AP with Radio MAC [chars] using source MAC address [chars] has been detected by AP [chars] with Radio MAC [chars], Slot [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> AP impersonation attack has been detected </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-MAX_NUM_ROGUE_AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue AP count for the system has reached the maximum limit of [dec] entries. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Rogue AP maximum scale has been reached </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-MAX_NUM_ROGUE_AP_CLEAR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue AP count for the system is within the limit of [dec] entries. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Number of Rogue APs is below system limit </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-MAX_ROGUE_PER_AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The average number of Rogue APs per detecting AP radio has crossed the threshold of [dec] on AP [chars] with radio MAC [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The average number of Rogue APs per detecting AP radio has crossed the threshold. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-MAX_ROGUE_PER_AP_CLEAR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The average number of Rogue APs per detecting AP radio is below the threshold of [dec] on AP [chars] with radio MAC [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The average number of Rogue APs per detecting AP radio is below the threshold. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-RLDP_ASSOC_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RLDP failed with error code [dec] while trying to associate to Rogue AP [chars] using AP [chars] with Radio MAC [chars], slot [dec]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> RLDP failed while trying to associate to Rogue AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-ROGUE_AP_CLEARED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue AP [chars] removed from Radio MAC [chars], Slot [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Rogue AP has been removed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-ROGUE_AP_DETECTED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue AP [chars] detected on Radio MAC [chars], Slot [dec], band [chars], Channel [dec], RSSI [dec], SNR [dec], Classification: [chars], State: [chars][chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A new Rogue AP has been detected </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-ROGUE_AP_ON_WIRED_NETWORK </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue AP with MAC address [chars] has been detected on the wired network. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A Rogue AP has been detected on the wired network </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-ROGUE_AP_ON_WIRED_NETWORK_CLEAR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue AP with MAC address [chars] is no longer on the wired network. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Rogue AP is not anymore on the wired network </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-ROGUE_CLIENT_DETECTED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue client with MAC address [chars] has been detected by [dec] APs, rogue client BSSID [chars], state [chars], last detecting AP [chars], rogue client gateway MAC [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Rogue client detected </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-ROGUE_CLIENT_THRESHOLD_CLEAR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue Client [chars] removed from Rogue AP [chars], state [chars], channel [dec], detected by AP [chars], slot [dec], current channel [dec], band [chars]. Rogue client count is now below the threshold for this Rogue AP. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Number of rogue clients per Rogue AP is below the threshold </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROGUE_SYSLOG-6-ROGUE_CLIENT_THRESHOLD_EXCEED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rogue Client count threshold exceeded for Rogue AP [chars] by client address [chars] detected by AP [chars], slot [dec], current channel [dec], band [chars], state [chars], rogue AP channel [dec]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Number of rogue clients per Rogue AP threshold has been exceeded </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-wips </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROMMON-5-CPLD_UPGRADE_STATUS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CPLD upgrade: [chars], install-id: [chars], message: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog provides the result of the CPLD upgrade </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-srvcability </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> ROMMON-5-ROMMON_UPGRADE_STATUS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> ROMMON upgrade: [chars], install-id: [chars], message: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog provides the result of the ROMMON upgrade </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-srvcability </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-0-FAILEDTIMERCREATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RRM failed to create [chars] timer </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Failed to create timer </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-CHD_INV_RF_PROF </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Coverage message received profile from [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> CHD message was received for a radio which has a non existent RF Profile Configured. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Can be seen during configuration changes,if seen otherwise LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-EWLC_EXEC_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> %% Error: AP [chars] MAC: %02x%02x.%02x%02x.%02x%02x Slot-id [dec] - [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Improper arguments or config </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Arguments to be changed </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-FAILEDCOVERAGEPROFILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Coverage profile violation on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Failed client count: [dec] Total client count: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Coverage profile violation </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-FAILEDINTPROFILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Interference profile violation on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Interference in percentage: [dec] On channel: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Interference profile violation </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-FAILEDLOADPROFILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Load profile violation on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Channel load in percentage: [dec] Number of stations: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Load profile violation </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-FAILEDNOISEPROFILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Noise profile violation on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Noise: [dec] dBm On channel: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Noise profile violation </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-HA_CONFIG_SYNC </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RRM HA Config tables not yet synced: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Some critical RRM configuration was found to be missing, immediately after switchover. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> If the message appears persistently, RRM may not function as configured. System reboot will be required to restore RRM function </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-RRM_AP_DB_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Unable to find AP %02x%02x.%02x%02x.%02x%02x entry in the database, could not process [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The operation being performed for the AP failed because the internal entry for the AP was not found. It is possible that the AP has been removed from the controller. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Use the 'show ap summary' command to determine if the AP is still joined to the controller. If it is not, the message may be ignored. If it is still joined, restart the AP to ensure that it has the latest configuration and contact technical assistance if the problem recurs. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-RRM_AP_INV_SLOT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Invalid slot number [dec] for AP %02x:%02x:%02x:%02x:%02x:%02x could not process [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> AP included wrong slot number </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-RRM_AP_TBL_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Unable to find AP %02x%02x.%02x%02x.%02x%02x slot [dec] [chars] entry in the database, could not process [chars] event </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The operation being performed for the AP failed because the measurement or coverage entry for the radio was not found. recreating the records. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Collect the controller logs and contact technical assistance. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-RRM_CHANNEL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RRM Channel Config Notification: Radio Role is AUTO. So, channel change is not allowed for AP [chars] on slot [dec]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Channel configuration is not allowed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-3-RRM_CONFIG </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RRM Config Notification: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Some critical RRM configuration still not populated. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> If the message appears persistently, for more than 8 times for each phy type, RRM may not function as configured. System reboot will be required to restore RRM function </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-5-PASSEDCOVERAGEPROFILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Coverage profile recovery on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Coverage profile recovery </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-5-PASSEDINTPROFILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Interference profile recovery on [chars] AP %02x%02x.%02x%02x.%02x%02x: Slot: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Interference profile recovery </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-5-PASSEDNOISEPROFILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Noise profile recovery on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Noise profile recovery </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-5-RRM_CAC_IN_PROG </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> AP [chars] slot [dec] [chars] is deferred, till pre-CAC is complete </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Setting channel/channel width/channel mode are deferred until pre-CAC is done. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-5-RRM_NON_PSC_CHANNEL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RRM Channel Config Notification: Non-PSC channel [dec] is configured for 6 GHz radio on slot [dec], Clients might fail to connect. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> When non PSC channel is used for 6GHz radio, it is possible that 6GHz clients may not be able to join the AP. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-6-MODE_SWITCH_LPI_TO_SP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> 6GHZ Power mode switch from LPI to SP AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Channel: [dec] Channel Width: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> 6GHZ Power mode switch from LPI to SP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-afc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-6-MODE_SWITCH_SP_TO_LPI </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> 6GHZ Power mode switch from SP to LPI AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] Channel: [dec] Channel Width: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> 6GHZ Power mode switch from SP to LPI </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-afc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_CLIENT-6-PASSEDLOADPROFILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Load profile recovery on [chars] AP %02x%02x.%02x%02x.%02x%02x Slot: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Load profile recovery </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_COMMON_TRACE_MESSAGE-3-RRM_COMMON_INVALID_SLOT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error encountered: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Invalid slot identifier is found while processing RRM packet </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Please report the error to technical support representative </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_MGR_DB-5-DUPLICATE_IP_WLC </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> WLC: [chars] having duplicate IP: [dec].[dec].[dec].[dec] detected while processing RRM pkt. IP address of the conflicting WLC: [chars] should be changed immediately to avoid impact on RRM functionality </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Another WLC in the rf-network is having duplicate IP, it will impact RRM functionality for the conflicting controllers </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> IP address of the conflicting controller should be changed immediately </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_MGR_TRACE_MESSAGE-0-FAILEDTIMERCREATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RRM failed to create [chars] timer </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Failed to create timer </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_MGR_TRACE_MESSAGE-3-EWLC_EXEC_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> %% Error: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Improper arguments or config </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Arguments to be changed </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_MGR_TRACE_MESSAGE-3-EWLC_GEN_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> General ewlc Error Message. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_MGR_TRACE_MESSAGE-3-HA_CONFIG_SYNC </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> RRM HA Config tables not yet synced: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Some critical RRM configuration was found to be missing, immediately after switchover. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> If the message appears persistently, RRM may not function as configured. System reboot will be required to restore RRM function </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_MGR_TRACE_MESSAGE-3-REG_IP_CHG_NOTIFY_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Unable to register with platform to get Management IP Address Change Notification - error [dec]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Unable to register with platform to get Management Interface IP Address Change Notification. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_MGR_TRACE_MESSAGE-3-REG_RX_PKT_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Unable to register with platform to receive packets - error [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Unable to register with platform to receive packets </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_MGR_TRACE_MESSAGE-3-RRM_IPC_EP_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> IPC Failure: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Failed to find IPC endpoint for AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> If the message appears persistently, RRM will not function as expected. AP should be disconnected to restore RRM function </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_MGR_TRACE_MESSAGE-5-RRM_DUPLICATE_IP_WLC </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> WLC: [chars] having duplicate IP: [chars] detected while processing RRM Hello pkt. IP address of the conflicting WLC: [chars] should be changed immediately to avoid impact on RRM functionality </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Another WLC in the rf-network is having duplicate IP, it will impact RRM functionality for the conflicting controllers </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> IP address of the conflicting controller should be changed immediately </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_UTIL-4-INVALIDCHANNELCONFIG </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Warning: Update of the channel list caused invalid pair in DCA list for [chars] band </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Invalid channel configuration </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_UTIL-6-SETCHANNEL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Set channel on cell %02x%02x.%02x%02x.%02x%02x: [dec] to [chars] chanwidth [dec] to reduce co-channel interference from [dec] to [dec] Reason [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Set channel to reduce co-channel interference </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_UTIL-6-SETCHANNELWIDTH </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Set channel width on 802.11a for AP %02x%02x.%02x%02x.%02x%02x: failed 160MHz channel width supported only for 4x4 antenna mode </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Channel width configuration change </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_UTIL-6-SETCHANNEL_DUALBAND </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Set channel [chars] for AP %02x%02x.%02x%02x.%02x%02x on dual band radio slot: [dec] due to [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Set channel because of Dualband Radio Role/band change </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_UTIL-6-SETCHANNEL_ED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Set channel on cell %02x%02x.%02x%02x.%02x%02x: [dec] to [chars] due to Air Quality voilation reason [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Set channel because of Air Quality Violation </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Investigate the cause of bad air quality on the channel and eliminate if possible </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_UTIL-6-SETCHANNEL_NONOPTIMAL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Set non-optimal channel on cell %02x%02x.%02x%02x.%02x%02x: [dec] to [chars] because of lack of information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Set channel on user input (non-optimal) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_UTIL-6-SETTXPOWER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Tx power changed from [dec] to [dec] for AP %02x%02x.%02x%02x.%02x%02x slot [dec] band [chars] due to [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Set transmit power </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_UTIL-6-UPDATECHANNEL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Set channel on [chars] AP %02x%02x.%02x%02x.%02x%02x: [dec] to [chars] by configuration change due to [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Channel configuration change </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RRM_UTIL-6-UPDATETXPOWER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Tx power changed from [dec] to [dec] for AP %02x%02x.%02x%02x.%02x%02x slot [dec] band [chars] due to [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Transmit power configuration change </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RULE_ENGINE-3-EWLC_GEN_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> General Wireless LAN Controller Error Message. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RULE_ENGINE-3-EWLC_RULE_ENGINE_REGEX_CREATE_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Rule regular expression error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Recreate regular expression correctly </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> RULE_ENGINE-4-EWLC_RULE_ENGINE_PRIORITY_UPDATE_WARN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Warning: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> rule_engine priorities are overridden, old rule_engine will be invalid </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SCOOBY-0-SERIAL_BRIDGE_CRITICAL_ERROR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Reloading [chars] due critical event %#x in block [chars]/[dec] of serial bridge [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A critical serial bridge I/O event has occurred. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> The system automatically reloads the hardware component experiencing the error. If the problem persists, copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SCOOBY-0-SERIAL_BRIDGE_CRITICAL_ERROR_RATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Reloading [chars] due to critically high serial bridge error rate. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A Serial Bridge has experienced a persistently high error rate. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SCOOBY-0-SERIAL_BRIDGE_DRIVER_ERROR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Kernel Module failed in [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A Serial Bridge has experienced a Init failure. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SCOOBY-2-FPGA_VERSION_CHECK_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> LEDA FPGA version does not meet minimum required version. [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> LEDA FPGA minimum version requirement not met. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-ether-lc </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SCOOBY-5-SERIAL_BRIDGE_BLOCK_EVENT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Block [chars]/[dec] of serial bridge [dec] had I/O event %#x </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A serial bridge I/O event has occurred. This event is not serious but is logged for diagnostic purposes. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SCOOBY-5-SERIAL_BRIDGE_EVENT_RATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The [chars] event rate of [dec] has exceeded the threshold of [dec] on serial bridge [dec] interconnect [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A Serial Bridge has experienced a high event rate. This condition is not considered serious, but is logged for diagnostic purposes. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No user action is required. If this message persists, a serial bridge critical message that needs to be addressed will appear. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SERDES-3-SERDES_CRITICAL_ERROR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Critial error [chars] in FRU [chars] when [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A critical error was occurred. The condition is serious and the card must be reloaded. This could be due to bad or unknown hardware (chassis or modules). Chassis Manager could also initialize the Serdes library with incorrect input parameters. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Copy the message exactly as it appears on the console or in the system log. Collect the output of show platform, show verson, show log, sh diag chassis eeprom detail, show diagnostic slot &lt;slot#&gt; eeprom detail, and any other relevant logs. Contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SERDES-5-SERDES_NOTICE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> from FRU [chars], [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> CMAN sends a significant Serdes event to IOSD to log it </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required for this notice. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SERVICES-0-INVALID_OWNERSHIP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error using service handle %p - invalid ownership (%p, %p) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A multi-thread application is trying to incorrectly use the services library. Applications must follow thread confinement strategy with the services library. Each thread of the application must initialize private managed context of the service library. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Copy the error message, tracebacks and version information and contact a Cisco representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SERVICES-2-NOINIT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error initializing services: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An application failed to initialize the core services library. The application will not be able to communicate with other modules on the system. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SERVICES-2-NORESOLVE_ACTIVE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error resolving active FRU: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An application was not able to determine the active FRU. The application was likely started incorrectly. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SERVICES-2-NORESOLVE_LOCAL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error resolving local FRU: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An application was not able to determine its local FRU. The application was likely started incorrectly. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SERVICES-2-NORESOLVE_STANDBY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error resolving standby FRU: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An application was not able to determine the standby FRU. The application was likely started incorrectly. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_RECUR_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SERVICES-3-INVALID_CHASFS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Thread %p has no global chasfs context </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A multi-thread application is trying to incorrectly use the services library. Applications must follow thread confinement strategy with the services library. Each thread of the application must initialize private managed context of the service library. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Copy the error message, tracebacks and version information and contact a Cisco representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-0-CONFIG_CORRUPT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Checksummed interface configuration corruption detected. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Interface configuration field was modified unexpectedly. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-4-ILLEGAL_TRACE_REQ </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Component ID [dec] not registered. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Component ID %d not registered. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-4-TERMINATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Authentication session terminated for client ([chars]) on Interface [chars] AuditSessionID [chars] Reason [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Session is being terminated. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-4-UNAUTH_MOVE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] MAC address ([chars]) from [chars] to [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Move while not authenticated on old IDB </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-5-FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Authorization failed or unapplied for client ([chars]) on Interface [chars] AuditSessionID [chars]. [chars] [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Authorization was unsuccessful. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Authorization was unsuccessful for the client. Collect the smd logs and system console logs </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-5-MACMOVE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> MAC address ([chars]) moved from Interface [chars] to Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Client has moved to a new interface without logging off on the previous one. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-5-MACREPLACE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> MAC address ([chars]) on Interface [chars] is replaced by MAC ([chars]) AuditSessionID [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A new client has triggered a violation causing an existing client to be replaced </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-5-SECURITY_VIOLATION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Security violation on the interface [chars], new MAC address ([chars]) is seen. AuditSessionID [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A host on the specified interface is attempting to gain access into the network or is trying to authenticate in a host mode that does not support the number of hosts attached. This is treated as a security violation and the port has been error-disabled. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Ensure that the port is configured to support the host count attached. Enter the &lt;cmdbold&gt;shutdown&lt;nocmdbold&gt; command followed by &lt;cmdbold&gt;no shutdown&lt;nocmdbold&gt; command to restart the port. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-5-START </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Starting '[chars]' for client ([chars]) on Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Starting an authentication method </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Message notification informing about the session manager client is being started to authenticate the endpoint attached to the interface </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-5-SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Authorization succeeded for client ([chars]) on Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Authorization was successful. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Client connected to the switch has been successfully authorized by the session manager framework </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-5-VLANASSIGN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> VLAN [dec] assigned to Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> VLAN assignment to an interface for the session </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-7-NOMOREMETHODS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Exhausted all authentication methods for client ([chars]) on Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> All available authentication methods have been tried </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SESSION_MGR-7-STOPPING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Stopping [chars] for client [chars] on Interface [chars] AuditSessionID [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Stopping the current authentication method </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-smd </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SHFWD-6-PACKET_TRACE_DONE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Packet Trace Complete: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Packet trace cmd initiated by admin is complete </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SHFWD-6-PACKET_TRACE_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Show fwd is failed at [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Packet trace cmd initiated by admin is fail </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Collect the trace from all the switch using the cli (show platform software trace fed switch &lt;&gt; ) </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SHFWD-6-PACKET_TRACE_FLOW_ID </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Packet Trace Flow id is [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Packet trace instance can be tracked by flowid </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIF_MGR-1-FAULTY_CABLE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> High hardware interrupt seen on switch [dec]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified stack cable is experiencing high hardware interrupts </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Replace the stack cable connected to the stack port. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIF_MGR-1-FAULTY_STACK_CABLE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> High hardware interrupt seen on switch [dec] on stack port [dec]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified stack cable is experiencing high hardware interrupts </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Replace the stack cable connected to the stack port. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIF_MGR-6-STACK_ADAPTER_INSERTED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> stack_mgr: Stack adapter [dec] on switch [dec] is inserted </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specific adapter has been inserted from the mentioned switch. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIF_MGR-6-STACK_ADAPTER_REMOVED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> stack_mgr: Stack adapter [dec] on switch [dec] is removed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specific adapter has been removed from the mentioned switch. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIG-2-SIG_TUNNEL_EVENT_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Cisco Umbrella SIG tunnel: [chars] event failure, [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when a IPSEC tunnel to Cisco Umbrella Secure Internet Gateway runs into failure(s) during state transition </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-sig </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIG-2-TUNNEL_TRACKER_STATUS_DOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Tracker associated with SIG tunnel [chars] is [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when tracker(s) associated with SIG tunnel goes DOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-sig </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIG-2-ZIA_LOCATION_EVENT_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Zscaler location: [chars] event failure, [chars] (additional info: [chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when various REST API(s) to setup ZIA encounter errors </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-sig </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIG-2-ZIA_TUNNEL_EVENT_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Zscaler SIG tunnel: [chars] event failure, [chars] (additional info: [chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when a IPSEC/GRE tunnel to Zscaler Secure Internet Gateway runs into failure(s) during state transition </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-sig </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIG-5-SIG_TUNNEL_EVENT_SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Cisco Umbrella SIG tunnel: [chars] event success, [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when a IPSEC tunnel to Cisco Umbrella Secure Internet Gateway transitions to different states successfully </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-sig </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIG-5-TUNNEL_TRACKER_STATUS_UP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Tracker associated with SIG tunnel [chars] is [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when tracker(s) associated with SIG tunnel comes UP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-sig </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIG-5-ZIA_LOCATION_EVENT_SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Zscaler location: [chars] event success, [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when various REST API(s) to setup ZIA location succeed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-sig </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIG-5-ZIA_TUNNEL_EVENT_SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Zscaler SIG tunnel: [chars] event success, [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when a IPSEC/GRE tunnel to Zscaler Secure Internet Gateway transitions through different states successfully </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-sig </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SIMULATION_ERRMSG-3-rw_err </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Cosim simualation failed to [chars] %zu bytes. ret: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An error occurred during cosim rw operation. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> INVALID </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check if Cima memory io socket is over subscribbed. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SISF_LOG-3-SISF_TRACEBACK </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> General SISF Error Message. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-sisf </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SM-2-INITIALIZATION_FAILED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Session Manager initialization for [chars] failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Initialization of session manager process failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Review SM logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-2-NO_MEMORY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Cannot allocate memory for an internal data structure </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An out-of-memory condition occurred when attempting to create an internal data structure. The daemon encountering the problem will exit, after which the process manager will restart. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the log files for the associated daemon. Monitor processes for excessive memory consumption. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-2-TDL_MESSAGE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Cannot construct an IPC message for library. The message name is [chars] and the reason is: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A problem occurred while constructing a type definition language (TDL) message or setting a field in a TDL message. If the problem occurred during construction of a TDL message, the system is out of memory. If the problem occurred while setting a field in the TDL message, there is a library mismatch issue. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check [uipeer] ERR entries in the log files for message reporting problems. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-CRDU_PATCH_REPLY_TIMEOUT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to receive patch response from peer process [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> During patch operation the Shell Manager broadcasts a request to all affected processes (peers). If a peer does not respond in time then the patch process cannot be completed correctly </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crdu </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check that the process(es) that failed to respond are still active and check their trace files for any potential errors that could prevent them from responding to a patch request in a timely manner </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-CRFT_CLEARCOUNTERS_REQUEST_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT clear counters request finished with one or more failures. Check tracelogs for further details. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> After a request to clear CRFT counters if any program reports an error or fails to respond within the timeout period this message will be emitted. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Inspect btrace logs for information about which programs failed and why </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-CRFT_COLLECT_REQUEST_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT collection request finished with one or more failures. Check tracelogs for further details. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> After a request to collect CRFT data if any program reports an error or fails to respond within the timeout period this message will be emitted. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Inspect btrace logs for information about which programs failed and why </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-CRFT_EXPORT_REQUEST_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT export request finished with one or more failures. Check tracelogs for further details. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> After a request to export CRFT data if an error or failure during the export stage occurs this message will be emitted. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Inspect btrace logs for information about which operation failed and why </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-CRFT_RELOAD_REQUEST_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT reload request capture finished with one or more failures. Check tracelogs for further details. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> After a request to capture CRFT data on reload if an error or failure during the reload stage occurs this message will be emitted. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Inspect btrace logs for information about which operation failed and why </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-CRFT_UNSUPPORTED_REMOTE_PATH_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT remote requested using an unsupported remote path. Check tracelogs for further details. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> After a request to remotely capture CRFT data an error or failure during the remote stage occurs this message will be emitted. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Inspect btrace logs for information about which operation failed and why </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-CRFT_UNSUPPORTED_REMOTE_SCHEME_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT remote requested using an unsupported scheme. Check tracelogs for further details. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> After a request to remotely capture CRFT data an error or failure during the remote archive stage occurs this message will be emitted. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Inspect btrace logs for information about which operation failed and why </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-CRFT_UNSUPPORTED_REMOTE_TAG_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT remote requested using an unsupported tag format. Check tracelogs for further details. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> After a request to remotely capture CRFT data an error or failure during the remote archive stage occurs this message will be emitted. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Inspect btrace logs for information about which operation failed and why </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-HOSTINFO_MONITOR_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error initializing host info monitoring: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> During initialization, the Shell Manager monitors changes to host-related information, such as the hostname. This error occurs if initialization fails. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the Shell Manager trace file for related details. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-HOSTINFO_READ_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error reading host info ([chars]): [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> During process startup and when changes occur, the Shell Manager reads host-related information, such as the hostname. This error occurs if there is a failure reading information. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the Shell Manager trace file for related details. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-INVALID_EPOCH_FILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> An upgrade or installation has produced an invalid messaging configuration file [chars], [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> During an upgrade or installation of a new package, an invalid messaging configuration file was produced. The file is either empty or has invalid permissions and cannot be read. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Repeat the installation or upgrade. If the problem persists, revert to a previous known good package. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-NO_CDL_FILE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Could not access command definition file [chars]: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> During initialization, the Shell Manager loads a XML CDL file to load all the CLI structure. This file is for some reason not found. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the Shell Manager trace file for related details. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-3-PTL_RENDERER_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Rendering error with [chars].[chars]. Transform is missing or invalid for data. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Shell Manager process attempted to render a command response but the transformation failed due to an internal error. The failure may have been caused by a missing transform file or an included file cannot be found. The transformation may also fail if the data returned in the response is binary and has not been processed correctly. In this case, the rendering engine is unable to interpret the data resulting in a failure. The transformation may also fail if there is a mismatch of packages installed on the system. In this case, incompatible messages are exchanged between the Shell Manager and the daemon servicing the command request and incorrect data is passed to the rendering engine. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-shellmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> This error indicates a configuration issue resulting from bad or mismatched packages. Review the Shell Manager trace files and log files. Uninstall, then reinstall, any new packages. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-5-CRFT_CLEARCOUNTERS_REQUEST_SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT clear counters completed successfully. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This message serves to inform the user of exactly when the clearcounters operation completes and they are no longer waiting for additional processes </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action required. This message is expected </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-5-CRFT_COLLECT_REQUEST_INPROGRESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT collection already in progress. Please try again later </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> CRFT collection is something that should happen infrequently so if there is already a collection request in progress we reject the incoming request and emit a message to the user informing them that their request is rejected. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Try the request again later if necessary </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-5-CRFT_COLLECT_REQUEST_NOT_SUPPORTED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT collection request not supported on peer [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Some processes may not support CRFT collection for any of a number of reasons. This message serves to alert the user so that they do not go searching for CRFT stats for the process in question and determine an error has occurred when they cannot find them </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> None. Information only. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-5-CRFT_COLLECT_REQUEST_SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT collection completed successfully. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This message serves to inform the user of exactly when the collection completes and they are no longer waiting for additional processes </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action required. This message is expected </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-5-CRFT_EXPORT_REQUEST_SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT export completed successfully. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This message serves to inform the user of exactly when the export operation completes and they are no longer waiting for additional output/feedback </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action required. This message is expected </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SMAN-5-CRFT_RELOAD_REQUEST_SUCCESS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRFT reload collection completed successfully. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This message serves to inform the user of exactly when the export operation completes and they are no longer waiting for additional output/feedback </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-crft </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action required. This message is expected </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SPECTRUM-3-EWLC_EXEC_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> %% Error: AP %02x%02x.%02x%02x.%02x%02x: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Improper configuration for dual band AP </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> please check the requested configuration against ap type </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SS-2-INITIALIZATION_FAILED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Initialization of [chars] failed for IOx Secure Storage </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Initialization of IOx Secure storage process failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Review ioxss logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLMGR-0-ASYMMETRIC_KEY_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Asymmetric key failure: [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Asymmetric key failure. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action required - forwarding processor (ESP) rebooted automatically. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLMGR-0-N2_VSERVER_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Virtual server context failure: [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Cryptographic coprocessor critical operation failed. Further data processing on ESP is halted </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> forwarding processor (ESP) is rebooted automatically. no action needed </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLMGR-0-SYMMETRIC_KEY_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Symmetric key failure: [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Symmetric key failure. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action required - forwarding processor (ESP) rebooted automatically. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLMGR-3-N2_CONTEXT_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Context failure: [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Coprocessor context operation failed due to resource limit </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Monitoring required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLMGR-5-GATEWAY_UPDOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> sslvpn gateway : [chars] changed state to [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> sslvpn gateway changed state </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLVPNMGR-5-HTTP_REQUEST_NOT_AUTHORIZED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> HTTP request without login cookie. [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This message indicates that HTTP request doesn't have valid login cookie and is not authorized to access the resource </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLVPNMGR-5-LOGIN_AUTH_FAILED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to contact authentication server. [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Authentication server is unavailable because it is down or unreachable </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Verify if routes are configured correctly to reach authentication and the server is configured correctly </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLVPNMGR-5-LOGIN_AUTH_PASSED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Authentication successful, user logged in. [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This message indicates that login authentication succeeded for user </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLVPNMGR-5-LOGIN_AUTH_REJECTED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to authenticate user credentials. [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Authentication server failed to validate credentials provided by the user to login under webvpn context </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check username and password configured on authentication server </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLVPNMGR-5-SSL_CONNECT_OK </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> SSL/TLS connection successful with client [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This message indicates that SSL/TLS handshake with peer was successful </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLVPNMGR-6-CONTEXT_MAX_USERS_LOGIN_DENIED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Login denied for user [chars]. Max users exceeded for context [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This message indicates that user was denied to login because the the max users for the context has been exceeded </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the gateway configuration and reconfigure the maximum allowed users in the context </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLVPNMGR-6-GLOBAL_MAX_USERS_LOGIN_DENIED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Login denied for user [chars]. Global max users limit reached\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This message indicates that user was denied to login because the the max users limit reached </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SSLVPNMGR-6-SESSION_TERMINATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Session terminated. [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> SSLVPN session was terminated </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-ssl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> ACTION_NONE_REQUIRED </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-1-DUAL_ACTIVE_CFG_MSG </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Dual Active Detection [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Switch detected availability or unavailability of Dual Active Detection ports. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-1-EPA_MISMATCH </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars]. The mis-match may caused by hardware failure or different EPA types.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Standby EPA mismatch with Active EPA. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Need to make them match </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-1-FATAL_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Stack manager encountered an unrecoverable error. [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The stack manager process has encountered an unrecoverable error and the switch is being reloaded. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Please ensure valid switch numbers are being used. If you still believe there is an error in the system, please send the system report to a TAC representative </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-1-LIC_MISMATCH </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> License level is [chars] and needs to be upgraded to [chars] for Stackwise Virtual to function.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Current Licnese level on active switch does not support Stackwise Virtual. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Need to be upgraded to supported license level </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-1-RELOAD </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Reloading due to reason [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified switch has received a reload request and is being reloaded. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-1-RELOAD_REQUEST </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Received reload request for [chars], reason [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified switches are being reloaded. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-1-STACK_MERGE_IGNORE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Stack Merge Ignored [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Switch detected multiple Active switches. But stack-merge is being ignored. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-4-SWITCH_ADDED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] has been added to the stack.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified switch has been added to the stack. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-4-SWITCH_REMOVED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] has been removed from the stack.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified switch has been removed from the stack. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-5-CHASSIS_ROLE_UPDATE_FAIL </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to Set [chars] Chassis [dec] chassis_role [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This is used to indicate that update to new role failed </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> This is a rare failure condition. Please reach out to TAC </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-5-FAST_RELOAD_DONE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Fast reload operation completed successfully on entire stack </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This is used to indicate that the fast reload on stack is complete. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> accsw-p-fsu </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action needed. This is not an error. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-ACTIVE_ELECTED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] has been elected ACTIVE.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified switch has been elected active. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-ACTIVE_READY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Active [chars] [dec] is ready.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The active switch is ready. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-CHASSIS_ADDED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] has been added to the stack.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified chassis has been added to the stack. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-CHASSIS_READY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] is ready.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified chassis is ready. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-CHASSIS_REMOVED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] has been removed from the stack.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified chassis has been removed from the stack. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-CHASSIS_REMOVED_KA </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] has been removed from the stack due to keepalive failure. \n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Chassis has been removed due to the keepalive failure. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-DISC_DONE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] has finished stack discovery.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified switch has completed stack discovery and is moving to the election phase. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-DISC_START </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] is starting stack discovery.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified switch is starting stack discovery. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-KA_MISSED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Keepalive missed for [dec] times for [chars] [dec] \n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Chassis has been removed due to the keepalive failure. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-STACK_LINK_CHANGE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Stack port [dec] on [chars] [dec] is [chars]\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified stack port has changed status. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-STANDBY_ELECTED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] has been elected STANDBY.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified switch has been elected standby. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> STACKMGR-6-SWITCH_READY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] [dec] is ready.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The specified switch is ready. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-fwdmgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SUBSYS-3-SUBSYS_CLASS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] subsystem [chars] has class [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The task has detected a subsystem which has an unsupported class in its header. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SUBSYS-3-SUBSYS_RECURSION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] subsystem [chars] maxiumum sequence depth [dec] exceeded </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The task has detected that a subsystem upon insertion has exceeded the depth of insertion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SUBSYS-3-SUBSYS_VERSION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] subsystem [chars] has unsupported version: [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The task has detected a subsystem which has an unsupported version in its header. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SUBSYS-6-SUBSYS_SEQUENCE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> [chars] subsystem [chars] has cross class sequence for [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The task has detected a subsystem which has an incorrect class for which it is being considered for. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SUBSYS-6-SUBSYS_UNORDERED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Subsystem class [dec] ([chars]) has no order </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The task has detected a class which has an unknown order upon initialization. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SWITCH-3-L2_L3_CONVERT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to convert interface [chars] into an [chars] port </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An error occured while changing the port mode from L2 to L3 or vice versa. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-platform </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Try reloading the device. If the reload fails to correct the problem, collect the output of the error message, the logs and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSHW-3-SYSHW_READ </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> A read operation has failed for device: [chars] error: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A syshw read operation failed for the mentioned device </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> The error message indicates a read failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate permanent fault with the specific device/component. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSHW-3-SYSHW_REG_READ </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> A register read operation has failed for device: [chars] register: [chars] error: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A syshw register read operation failed for the mentioned device </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> The error message indicates a read failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate permanent fault with the specific device/component. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSHW-3-SYSHW_REG_WRITE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> A register write operation has failed for device: [chars] register: [chars] error: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A syshw register read operation failed for the mentioned device </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> The error message indicates a read failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate permanent fault with the specific device/component. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSHW-3-SYSHW_WRITE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> A write operation has failed for device: [chars] error: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A syshw write operation failed for the mentioned device </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> The error message indicates a write failure for the device. No action is needed from the user. However, if these errors come continuously or frequently, it may indicate a permanent fault with the specific device/component. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSPLAT-3-PLIM_BRIDGE_CRITICAL_ERROR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Reloading [chars] due critical event %#x in block [chars]/[dec] of PLIM device </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A critical PLIM device I/O event has occurred. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> The system automatically reloads the hardware component experiencing the error. If the problem persists, copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSPLAT-3-PLIM_CRITICAL_ERROR_RATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Reloading [chars] due to critically high PLIM device error rate. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A Serial Bridge has experienced a persistently high error rate. The condition is serious and the card must be reloaded. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Copy the message exactly as it appears on the console or in the system log, collect the output of show tech-support and any other relevant logs, and contact your Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSPLAT-5-PLIM_BLOCK_EVENT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Block [chars]/[dec] of PLIM device had I/O event %#x </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A PLIM device I/O event has occurred. This event is not serious but is logged for diagnostic purposes. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No user action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSPLAT-5-PLIM_EVENT_RATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The [chars] event rate of [dec] has exceeded the threshold of [dec] on interconnect [dec] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A Serial Bridge has experienced a high event rate. This condition is not considered serious, but is logged for diagnostic purposes. This could be due to a hardware or software driver defect. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> asr1k-infra-intrnl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No user action is required. If this message persists, a PLIM device critical message that needs to be addressed will appear. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSTEM-2-REBOOT_ABORTED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> System reboot aborted due to [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when system reboot is aborted due to an error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-install </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> If reboot is aborted due to software error, please contact Cisco TAC </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSTEM-4-SSL_CERT_WARNING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> SSL certificate warning: [chars] (code: [chars]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when self-signed certificates are used for communication. Self signed certificates are not considered secure and must be replaced with certificates provided by verified distributors </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-install </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Customers are expected to delete self-signed certificates and replace with them Enterprise certificates </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSTEM-5-REBOOT_ISSUED </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> System reboot issued, reason: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated when system reboot is issued </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-install </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSTEM-5-SOFTWARE_INSTALL_STATUS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Software install stage: [chars], install-id: [chars], message: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This syslog is generated during software installation which goes through multiple stages </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> cedge-install </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSTEM-6-CLI_COMMIT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CLI commit done by user [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> This info syslog is generated when a user alters config via CLI. CLI is usually locked when a device is managed by Cisco SD-WAN Manager, however when the control connection is down, CLI session is unlocked for users and user can commit via CLI </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSTEM_CONFIG_MESSAGE-2-AP_FILE_TRANSFER_HTTPS_CUST_PORT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> CRITICAL, [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> General WLC critical message </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSTEM_CONFIG_MESSAGE-3-ACL_FLEX_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> ewlc ACL flex push error message. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSTEM_CONFIG_MESSAGE-3-ACL_INDEX_ERR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Error in [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> ewlc ACL flex index error message. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> SYSTEM_CONFIG_MESSAGE-5-UNSUPPORTED_FLEX_ACL_RULE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Unsupported rule: [chars], in flex acl: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> unsupported rule in flex acl </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TAGMGR_DB_SYSLOG-3-TAGMGR_RF_TAG_CREATE_ERROR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failure during RF tag [chars] creation, could not add to rf profile tag list </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Failed to add RF tag to RF profile tag list </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Please delete the RF tag and configure again </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TAGMGR_TRACE_MSG-3-TAG_EASY_PSK_CONFIG_WARNING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Easy-PSK config validation error: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Easy-PSK CONFIG warning message </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-spwifi </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TAGMGR_TRACE_MSG-3-TAG_MPSK_CONFIG_WARNING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> MPSK config validation error: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> MPSK CONFIG warning message </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TAGMGR_TRACE_MSG-4-TAG_CONFIG_WARNING </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Warning: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> General Wireless LAN Controller warning message </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TAGMGR_TRACE_MSG-5-WLC_MODE_CHANGE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Mode Change: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Msg indicating AP reboot during Mode Change </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> ewlc-ap </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TDLDB-3-DATABASE_MEMORY_LEAK </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Database memory leak detected in [chars] database, [chars]/[chars]/[chars] size: [dec] bytes </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A memory leak has been detected in the database memory. The leaked object is identified by name </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STANDARD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TDLDB-3-DBPERSIST_OPERATION_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Operation: [chars], DB: [chars], Failure reason: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Database persistent operation can be triggered by 1. Persist : write memory or reload CLI 2. Delete : write erase CLI 3. Restore : During boot time, when database is first opened When error occurs, it can impact the customer in this way 1. Persist : DB content can not be persisted, data will be lost after system reload. If reload CLI command fails, it does not allow the system getting reloaded. 2. Delete : There may be database residue in the persistent storage media. 3. Restore : Persistent content cab be lost </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TDLDB-3-INVALID_TABLE_FREE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Invalid table free by process [chars] in [chars] on table with luid [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> In shared databases, only the garbage collector should be performing table and record deletes on tables that have read cursors enabled. A non-gc process has performed a table deletion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TDLDB-3-SESSION_LOCK_TIMEOUT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Owner: user-proc: [chars], DB: [chars]. Lock expired [chars] ago. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An application running in a process wishes to have an exclusive write access to DB. It acquires a session lock with for a specific period and is expected to release or renew the session lock. The appication has failed to do so and hence the unexpected timeout has occured </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> This is unexpected. Report this to Cisco TAC. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TDLDB-3-WRITE_ON_SNAPSHOT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Process writing on snapshotted DB [[chars]] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Application is trying to write on a snapshotted DB. A snapshotted DB is read-only and any write operation is not effective. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-mdt-infra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TDLDB-4-LONG_READ_WRITE_LOCK_HELD </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Process held [chars] lock on DB [[chars]] for [[dec]] ns </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Application has held the read/write lock for fairly long time. If this error is thrown, it means that the lock has been held for more than 1 sec. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TDLDB-6-DBPERSIST_OPERATION_INFO </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Cancelled [chars] operation and is intended - DB: [chars], Reason: [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> When this message is observed, the reason can be 1. DB format version mismatched - database format definition can be changed. If mismatched, the operation is cancelled and this is an intended behavior. 2. DB base pointer mismatched - database base pointer can be modified. If changed, the operation is cancelled and this is an intended behavior. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TDLDB-6-SUBSCRIPTION_DAMPENING_INACTIVE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Subscription dampening inactive for DB [chars] on table [chars]. All on-change updates for the table will be sent. Consider re-adjusting the dampening period </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> On-change Subscription enabled with dampening will be temporarily in-active due to load on system or due to incorrect dampening interval configured. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TDLDB-6-SUBSCRIPTION_DAMPENING_REACTIVATE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Dampening subscription re-activated for DB [chars] on table [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> On-change Subscription re-activated with dampening resumed after it got paused </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-db </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> THERMAL-1-THERMAL_GREEN_THRESHOLD </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Hotspot temperature has exceeded GREEN threshold\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The switch is too cold. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> THERMAL-1-THERMAL_RED_THRESHOLD </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 1-Alert </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Hotspot temperature has exceeded RED threshold. Switch will shutdown soon.\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The hotspot temperature is critically overheated. The switch will soon shutdown to prevent permanent damage. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> THERMAL-2-THERMAL_YELLOW_THRESHOLD </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Hotspot temperature has exceeded YELLOW threshold\n </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The hotspot temperature is too high. Improve cooling immediately. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> polaris-platform_mgr </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the switch's environment is a safe operating temperature. If problem persists, replace the switch. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TH_WARN_MGR-2-WIRELESS_CLIENTS_THRESHOLD_CLEAR </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Current percentage of joined wireless clients ([dec]) returned below the configured threshold ([dec]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The number of clients currently joined to the wireless controller returned below the configured threshold for the device </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> If this message occurs, you need to carefully check if you need a more capable controller for the number of wireless clients you are trying to serve </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TH_WARN_MGR-2-WIRELESS_CLIENTS_THRESHOLD_HIT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Current percentage of joined wireless clients ([dec]) exceeded the configured threshold ([dec]) </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The number of clients currently joined to the wireless controller has exceeded the configured threshold for the device </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> If this message occurs, you need to carefully check if you need a more capable controller for the number of wireless clients you are trying to serve </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-IPC_CONNECTION_INVALID </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> An IPC connection has invalid state. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-IPC_CONNECT_MASTER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> IPC connection to the active RSP failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> IPC connection to the active RSP failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-IPC_INITIALIZATION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> IPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> IPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-MESSAGE_REGISTER </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to register with active RSP because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The active RSP failed to register. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-MESSAGE_RELAY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to relay a message because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> Failed to relay a message. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-MESSAGE_RESPONSE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> An invalid message response was received because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> An invalid message response was received. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-MQIPC_ADVANCE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Failed to advance MQIPC queue because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The MQIPC initialization failed. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-MQIPC_INITIALIZATION </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> MQIPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-PEER_TABLE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> A peer table initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TIMINGD-0-RESOURSE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Resource allocation failed in [chars] because [chars] </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The system is unable to allocate the requested resource. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iiot-rtr-timing </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> In most cases, this message is seen as a result of a temporary resource issue. Retry the request for the resource when the system is experiencing lower traffic volumes. If the message persists, reload the router using the reload command. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TLSCD-4-DNS_RESOLVER_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> DNS resolver failed for url [chars] session [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The TLS Client daemon attempted to resolve the server url and API is failing/timing out. The failure may have been caused by a miss configuration of nameserver or url string in crypto tls-tunnel configuration. Daemon shall be retrying to resolve the url periodically. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-tlscdinfra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> This error indicates a configuration issue for url resolution. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TLSCD-4-TPS_CERT_RESP_FAILURE </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> TPS certificate response failed for session session [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The TLS Client daemon process attempted to get the ceritificate from IOSd and API is failing/timing out. The failure may have been caused by a miss configuration of pki trustpoint crypto tls-tunnel configuration. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-tlscdinfra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> This error indicates a configuration issue for pki trustpoint. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TLSCD-5-SESSION_UPDOWN </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Session [[chars]] to TLSGW: [[chars]] is [chars]. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The TLS Client daemon process session status notification. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-p-tlscdinfra </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> The TLS Client daemon process session status. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TTYMON-3-AGETTY </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> Cannot initiate a switch in console ownership. A required program could not be launched successfully. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. Switching ownership of the console port is initiated by the user entering a 'send break' command at a telnet prompt. The Host Manager launches one or more programs to authenticate users and to provide a shell instance. One or more of these programs has not been configured correctly. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Some required programs are either not available or not configured correctly or are failing for some reason. If this occurs after a recent upgrade it is possible that the upgrade has corrupted the current installation. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TTYMON-3-CHASFS </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The software which monitors ownership of the console port cannot [chars] a filesystem configuration value. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for monitoring a change of console ownership uses the filesystem to store various settings. This error indicates that the daemon encountered a problem either reading or writing a value from/to the filesystem. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the log files for the Host Manager and search for entries related to 'ttymon' and 'chasfs' and this should give an indication as to why the operation failed. Check available resources and see if other daemons are also experiencing problems with the chassis filesystem since this may indicate a more pervasive problem. If so the reboot the box. </td> </tr> <tr> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__1 "> TTYMON-3-INIT </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__3 "> The software which monitors ownership of the console port cannot be initialized correctly </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__4 "> The Host Manager process on the Route Processor, and only the Route Processor, is responsible for determining which process has control of the console port, either IOSd or an IOSXE process. A user can initiate a switch in ownership by by entering the 'send break' command at a telnet prompt to switch from IOSd to a shell instance. Control is returned to IOSd by exiting the shell instance. The component within the Host Manager responsible for this has encountered an initialization error and console monitoring is no longer available. </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-p-to-t-syslogs_17161__entry__6 "> Check the status of the Host Manager process. Check the Host Manager log files for further indications as to why the initialization failed and if necessary restart the machine. </td> </tr> </tbody> </table> </section> </div>  <nav role="navigation" class="related-links"></nav>  </article> <article class="topic reference nested2" aria-labelledby="ariaid-title10" lang="en-US" id="r-u-to-z-syslogs_17161"> <h3 class="title topictitle3" id="ariaid-title10"> U to Z </h3> <div class="body refbody"> <section class="section" id="r-u-to-z-syslogs_17161__d54e61666"> <table width="100%" border="1" class="table"> <caption></caption> <colgroup> <col style="width:37.334510150044125%"> <col style="width:8.8261253309797%"> <col style="width:16.504854368932037%"> <col style="width:8.8261253309797%"> <col style="width:8.8261253309797%"> <col style="width:19.68225948808473%"> </colgroup> <thead class="thead"> <tr> <th font-weight="bold" class="entry align-left" id="r-u-to-z-syslogs_17161__entry__1"> Facility-Severity-Mnemonic </th> <th font-weight="bold" class="entry align-left" id="r-u-to-z-syslogs_17161__entry__2"> Severity-Meaning </th> <th font-weight="bold" class="entry align-left" id="r-u-to-z-syslogs_17161__entry__3"> Message </th> <th font-weight="bold" class="entry align-left" id="r-u-to-z-syslogs_17161__entry__4"> Message-Explanation </th> <th font-weight="bold" class="entry align-left" id="r-u-to-z-syslogs_17161__entry__5"> Component </th> <th font-weight="bold" class="entry align-left" id="r-u-to-z-syslogs_17161__entry__6"> Recommended-Action </th> </tr> </thead> <tbody class="tbody"> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UBD-0-EVENT_LIBRARY </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> An event facility initialization or maintenance function failed because [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered inforation to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UBD-0-MQIPC_ADVANCE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Failed to advance MQIPC queue because [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The MQIPC initialization failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UBD-0-MQIPC_INITIALIZATION </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 0-Emergency </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> MQIPC initialization failed because [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> MQIPC initialization failed. This could be due to a software defect or system resource exhaustion. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UBD-2-INITIALIZATION_FAILED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> URSA Bootstrap initialization for [chars] failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Initialization of ursa bootstrap process failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> polaris-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Review UBOOTD logs taking note of the timestamp information to select specific information to review. Copy the message and other related information exactly as it appears on the console or in the system log. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UICFGEXP-3-LIBRARY_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Error loading library '[chars]': [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A configuration message was received which required a library to be loaded. The library failed to load. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-ui </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UICFGEXP-3-MESSAGE_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Unable to process message for '[chars]': [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A message was received by the configuration export module which could not be processed. The message has been discarded. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-ui </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UICFGEXP-3-SYMBOL_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Error loading library symbol '[chars]' from '[chars]': [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A configuration message was received which required a library to be loaded. The library failed to load all required symbols. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-ui </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UICFGEXP-3-WRITE_FAILED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Unable to write configuration for '[chars]': [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The configuration export module failed to write the server configuration files. The server configuration change has not occurred. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-ui </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UICFGEXP-6-SERVER_NOTIFIED_START </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Server [chars] has been notified to start </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The server has been notified to start. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-ui </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UICFGEXP-6-SERVER_NOTIFIED_STOP </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Server [chars] has been notified to stop </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The server has been notified to stop. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-ui </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UIPEER-2-TDL_MESSAGE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Cannot construct an IPC message for library. The message name is [chars] and the reason is: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A problem occurred while constructing a type definition language (TDL) message or setting a field in a TDL message. If the problem occurred during construction of a TDL message, then the system is out of memory. If the problem occurred while setting a field in the TDL message, there is a library mismatch issue. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Check [uipeer] ERR entries in the log files for message reporting problems. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UIPEER-3-INVALID_DEBUG_MESSAGE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> The peer process was unable to process an incoming message for 'debug all' from the shell-manager </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> When the 'debug all' command is issued, the Shell Manager broadcasts a notification of the command request to its peers. If the notification message has been corrupted or incorrectly created, the peers cannot complete the requested operation. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Check the trace files for the Shell Manager failed process. Restart the system. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UIPEER-3-INVALID_EPOCH_MESSAGE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> The peer process was unable to process an incoming epoch update message from the shell-manager </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> For each new type definition language (TDL) epoch, the Shell Manager broadcasts a change notification message to its peers. If the Shell Manager's message is incorrect or corrupt, the peers are unable to identify the new epoch. In this case, the peers reject the proposed epoch. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Check the trace files for the Shell Manager failed process. Check or undo any recently installed packages, then restart the system. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UIPEER-3-INVALID_HOSTINFO_MESSAGE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> The peer process was unable to process an incoming message for host info from the shell-manager </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> When host information, such as the hostname, changes, the Shell Manager broadcasts a notification of the change to its peers. If the notification message has been corrupted or incorrectly created, the peers cannot complete the requested operation. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Check the trace files for the Shell Manager failed process. Restart the system. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UIPEER-3-NO_PEER </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> A process was unable to retrieve a shell-manager peer handle. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A process was attempting to communicate with the Shell Manager daemon using the integrated [uipeer] component. The error occurred because the peer instance could not be found. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Check [uipeer] ERR entries in the log files for message reporting problems. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UIPEER-3-SET_LOG_TRACELOG_NUM </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Tracelog number for process [chars] changed to [dec] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Tracelog number to keep for a process is changed using set logging tracelog-number .. CLI </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> polaris-trace </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UIPEER-5-TIMER_ACCURACY_TEST </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Timer Accuracy Test [chars]. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Test result of Timer Accuracy Test </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required. This is informational message </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-AP_SW_UPDATE_ERR_LOG_MSG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP SW update [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> AP Software Update logging </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> AP software update failed. ISSU image upgrade or SMU patching could be aborted. The user needs to initiate ISSU upgrade/SMU patch again. If the error occured during manual operation, operation can be initiated again </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-AP_UPGRADE_CLEAR_REPORT_NAME_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP Upgrade clear report error, failed to find upgrade report name : &lt;[chars]&gt; from upgrade report table </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Error occured in deleting record from upgrade report table. Operation aborted. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-AP_UPGRADE_CLEAR_REPORT_NAME_IN_PROGRESS_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Staggered AP Upgrade in progress, failed to delete upgrade record with report name : &lt;[chars]&gt; from upgrade report table </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Error occured in deleting record from upgrade report table. Operation aborted. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-AP_UPGRADE_FALLBACK_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP Upgrade fallback error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Error occured in upgrade fallback process. Operation aborted. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-AP_UPGRADE_FALLBACK_INIT_TIMEOUT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Timeout occurred either source controller is not responding or has responded with invalid software version. Aborting fallback process </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Timeout occurred. Source controller is not responding to the upgrade fallback version request message or it has responded with an invalid software version. Aborting fallback process </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Please reload source controller with valid image and initiate upgrade process from destination controller by using CLI: 'ap image move destination &lt;Destination Name&gt; &lt;Destination IPv4/IPv6 address&gt; &lt;Report name&gt;' </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-AP_UPGRADE_FALLBACK_TYPE_MSG_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP upgrade process aborted. Failed to send fallback type message to peer </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Error occured while sending fallback type message to peer. Operation aborted. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Please restore the mobility status between source and destination controller </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-AP_UPGRADE_FALLBACK_VERSION_VALIDATION_FAILURE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Source controller is not responding or has responded with invalid software version </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Source controller is not responding to the upgrade fallback version request message or it has responded with an invalid software version </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Please reload source controller with valid image </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-DESTINATION_NOT_READY </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Destination controller not ready. Aborting upgrade process </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Destination controller may be going through another AP upgrade or move </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Please wait for the current ap upgrade to finish before triggering this command. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-DESTINATION_NOT_RESPONDING </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP upgrade process aborted. Destination controller is not responding </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Destination controller is not responding to the upgrade request message </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Destination Controller may be down or unreachable. Please restore the mobility status between source and destination controllers before initiation of AP move/upgrade to destination </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-MOBILITY_TUNNEL_DOWN </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP upgrade process aborted. Mobility tunnel is down for more than the permissible amount of time </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> If the mobility tunnel with the peer is down for more than the permissible amount of time, the current upgrade process is aborted </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Please restore the mobility status between source and destination controllers before initiation of AP move/upgrade to destination </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-STAGGERED_UPGRADE_ABORT_DEST_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Trigger abort CLI from source WLC, fail to abort AP upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> AP upgrade abort CLI should be triggered from source WLC. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-STAGGERED_UPGRADE_ABORT_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Staggered AP Upgrade not in progress, fail to abort AP upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Error occured in AP upgrade abort process. Operation aborted. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-STAGGERED_UPGRADE_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Staggered AP Upgrade error: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Error occured in upgrade reset process. Operation aborted. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-STAGGERED_UPGRADE_IN_PROGRESS </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP upgrade is in progress. New ap upgrade process is not allowed </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> If an ap upgrade process is already running, either in source or destination mode, new ap upgrade process is not allowed </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Please wait for the current ap upgrade to finish before triggering this command. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-3-STAGGERED_UPGRADE_MOVE_REPORT_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Invalid ap upgrade report name </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Upgrade report name entered is invalid </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Please enter a valid ap upgrade report name. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-5-AP_SW_UPDATE_LOG_MSG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP SW update [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> AP Software Update logging </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-5-AP_UPGRADE_AP_RESET_FAILURE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP with MAC: [chars] has not rejoined after software upgrade. No longer accounting for this AP </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> AP has not rejoined the controller </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-5-AP_UPGRADE_EVENT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Staggered AP upgrade event: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Staggered AP upgrade event message </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-5-AP_UPGRADE_SITE_FILTER_ANY_IGNORE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Site-filters for any-image will be ignored for APSP/APDP. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Site-filters added with any-image are only applicable for N+1 upgrades. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-5-AP_UPGRADE_SSO_FAILURE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Staggered AP upgrade was interrupted due to SSO. The upgrade process will continue shortly. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Staggered AP upgrade was interrupted due to SSO. The process should restart automatically </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-AP_UPGRADE_ANY_IMAGE_DB_DELETE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Site-filters added with image name 'any' deleted. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Existing site-filters with image name 'any' are deleted. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-AP_UPGRADE_AP_RESET </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP: [chars] has incorrect software. AP is going for reset. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> AP is going for a software upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-AP_UPGRADE_CLEAR_REPORT_NAME </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP Upgrade record deleted successfully </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Deleted AP upgrade record. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-AP_UPGRADE_DB_DELETE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Site filters for APSP deleted for the image version [chars]; new image version is [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Existing site-filters for APSP are deleted since the base image is upgraded. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-AP_UPGRADE_FALLBACK_COMPLETE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP Upgrade fallback process completed succesfully </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> AP Upgrade fallback process completed </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-AP_UPGRADE_FALLBACK_START </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> AP Upgrade fallback process started </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Starting AP upgrade fallback process </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-STAGGERED_UPGRADE_ABORT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Aborted AP Upgrade successfully </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Aborted AP upgrade process. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-STAGGERED_UPGRADE_ABORT_DEST </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Aborted AP Upgrade forcibly on destination controller </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> AP upgrade was forcibly stopped on destination controller by the user </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-STAGGERED_UPGRADE_COMPLETE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Staggered AP Upgrade completed succesfully </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> All APs in current upgrade process rebooted with the new version </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-STAGGERED_UPGRADE_START </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Staggered AP Upgrade reboot process started </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Rebooting given APs in staggered way </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> UPGRADE-6-STAGGERED_UPGRADE_WITH_RESET_FALLBACK_COMPLETE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Staggered AP Upgrade with fallback type as either reset or reset with fallback completed succesfully </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> All APs in current upgrade process rebooted with the new version </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-upgrade </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_NO_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-3-NO_ACTIVE_VBOND </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Device does not have an active connection to SD-WAN validator </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This error syslog is generated when there are no active control connections to Cisco SD-WAN Validator. This could be a temporary situation where control connections flap because of some network issue. This could also imply some issue with SD-WAN Validator </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> If the issue persists, i.e. control connections to SD-WAN Validator do not come up for long, use vdiagnose utility to identify the reason </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-3-NO_ACTIVE_VSMART </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Device does not have an active connection to SD-WAN Controller </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This error syslog is generated when there are no active control connections to Cisco SD-WAN Controller. This could be a temporary situation where control connections flap because of some network issue. This could also imply some issue with SD-WAN Controller(s) </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> If the issue persists, i.e. control connections to SD-WAN Controller(s) do not come up for long, use vdiagnose utility to identify the reason </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-3-NO_SDWAN_MODE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Device does not suppport SD-WAN control mode </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This error syslog is generated when SD-WAN Edge virtual machine is instantiated on an unsupported hypervisor </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Please check SD-WAN documentation on which all hypervisors are supported for SD-WAN mode </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-5-CONTROL_CONN_STATE_CHANGE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Control connection to [chars] [chars] (TLOC: [chars]/[dec]/[chars] via [chars]) is [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This notice syslog is generated when control connection to Cisco SD-WAN Validator, Controller or Manager goes down or comes back up </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-5-PEER_AUTH_FAILED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Auth failed for [chars] ([chars]), reason: [chars]. Control connection attempt via [chars] (color: [chars]) </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This notice syslog is generated when control connection to peer device (Cisco SD-WAN Validator, Manager or Controller) cannot be established due to various reasons </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Please refer to https://www.cisco.com/c/en/us/support/docs/routers/sd-wan/214509-troubleshoot-control-connections.html for troubleshooting control connection failures </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-6-DOMAIN_ID_CHANGED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Domain id changed from [dec] to [dec] via config </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This info syslog is generated when domain-id is changed via config </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-6-IPSEC_REKEY </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> IPSec SA [chars] rekey done for tunnel established via [chars] (color: [chars]) </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This info syslog is generated when auto/manual IPSEC rekey is initiated for tunnels established over a WAN interface </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-6-ORG_NAME_CHANGED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Organization name changed from [chars] to [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This info syslog is generated when organization name is changed via config </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-6-SITE_ID_CHANGED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Site id changed from [dec] to [dec] via config </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This info syslog is generated when site-id is changed via config </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-6-SYSTEM_IP_CHANGED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> System IP changed from [chars] to [chars] via config </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This info syslog is generated when system IP is changed via config </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-6-SYSTEM_LICENSE_MISMATCH </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> There is a license association mismatch. [chars] instance is being associated to [chars] license </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This info syslog is generated when there is a license association mismatch. Pay As You Go instance cannot be associated with Bring Your Own instance or vice versa </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Contact Cisco TAC for assistance </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-6-TLOC_IP_CHANGE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Control connection TLOC changed from [chars]:[dec] to [chars]:[dec] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This info syslog is generated when TLOC IP and port changes as a result of static configuration change, DHCP renewal or when the edge device learns about public IP/port via Cisco SD-WAN Catalyst validator (which behaves as STUN server in such cases) </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VDAEMON-6-VMANAGE_CONNECTION_PREF_CHANGED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> vManage connection preference for interface: [chars] (color: [chars]) changed to [dec] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This info syslog is generated when vmanage connection prefernce value for a WAN interface is changed via config </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vip-vdaemon </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VIP_CONFD-3-VIP_CONFD_ERR_LOG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> vip-confd logging : [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> vip-confd error log: </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> cedge-bootstrap </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> The vip-confd process console logging. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VIP_CONFD-5-VIP_CONFD_NOTICE_LOG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> vip-confd logging : [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> vip-confd notice log: </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> cedge-bootstrap </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> The vip-confd process console logging. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-ACTIVATION_STATE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] '[chars]' [chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The activation state of the named virtual service has changed as notified by Virt-manager. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-ALLOC_VIRT_INST_RCS </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A memory allocation request failed to allocate a data structure required to activate the virtual service. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-COMMIT_VIRT_INST_RCS </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The request to commit the resources required by the named virtual service failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-CPUSHARES_LIMIT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-CPUTUNES_INTERNAL_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Virt-manager and its associated infrastructure experienced an internal error. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-CPUTUNES_SHARES_LIMIT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file is requesting more CPU shares than the system has available for virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Deactivate any other virtual services to free up CPU share resources and activate this virtual service. If that does not address the problem, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-CREATE_VIRT_INST_ENTRY </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The request to create a DB entry for the named virtual service failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-DEACT_FOR_ISSU </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] Max ([dec]s) </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> An ISSU event is pending. Any active VMs will be automatically deactivated to allow ISSU preprocessing to validate the environment. Any ISSU-deactivated VMs will be automatically restarted if the ISSU is cancelled. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> None. Allow the ISSU to continue and the VMs will restart when the ISSU completes; or cancel the ISSU and vman will automatically restart the VMs. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-DEFER_VIRT_INST_PROC </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The final activation processing failed to successfully defer. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-DISK_IMAGE_PATH </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file contains an invalid disk image path for one of the disk devices. This may be a Harddisk, CDROM or USB storage device. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-FIND_VIRT_INST_ENTRY </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Failed to find virtual service with id [dec] in the Virt-manager DB </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service with the ID named could not be located in the Virt-manager DB. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-GENERAL_FAILURE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-GUESTSHELL_ENABLED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> The guest shell has been enabled. The command '[chars]' may be used to access it, '[chars] destroy' to remove it. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Informs the user that the guest shell virtual service has been enabled (which is done by default). </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> The user may use or remove the guest shell with the commands specified. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-HA_STATE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> VMAN tries to detect the role/slot of various nodes on HA events from the platform. If any of those event callbacks fail, this notification would be raised. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-HA_SWITCHOVER_STATE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> VMAN HA switchover state related messages for a virtual-service whilst it is being recovered on newly active RP after a HA switchover. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-HA_SYNC_ERR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] '[chars]' [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The ha-sync persistent storage disk for the virtual service cannot be watched for sync to standby RP. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-HA_SYNC_THREAD_STATE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> HA remote sychronize thread has failed and exited. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> VMAN tries to remote sync the OVA repository to all online nodes using a separate thread. If that thread fails, this notification would be raised. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In the failed case, check Virt-manager's logs for the cause of the failure. Check for the pthread error msg and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INCONSISTENT_CPUTUNES_CONFIG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file is requesting invalid CPU tunes parameter. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INCONSISTENT_MEM_CONFIG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file is inconsistent in the specification of required memory via the &lt;memory&gt; and &lt;currentMemory&gt; nodes. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INSERT_VIRT_INST_ENTRY </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Inserting the named virtual service into the virtual service DB tracked by Virt-manager failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INSTALL_FAILURE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The installation of the virtual service failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the installation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INSTALL_LOG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The installation log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INSTALL_MEDIA_RETRY </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> VMAN, VM install media still unavailable.[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The install media was not detected. Waiting for udev to complete install media(harddisk) detection. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> After VMAN exceeds the maximum retry limit, verify if install media (harddisk) is accessible and retry the installation again. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INSTALL_STATE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] '[chars]'[chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The installation state of the named virtual service has changed as notified by Virt-manager. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INVALID_ACT_MSG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service activate message was received, however, the data it contained could not be interpreted </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INVALID_DEACT_MSG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Failed to process virtual service deactivate message </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service deactivate message was received, however, the data it contained could not be interpreted </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INVALID_PACKAGE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The package definition file for the named virtual service has failed to be validated and the virtual service will not run </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. The most likely cause would be that the package file has been corrupted during file transfer. The suggested action would be to redo the file transfer. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-INVALID_UNPROV_MSG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Failed to process virtual service unprovision message </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service unprovision message was received, however, the data it contained could not be interpreted </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation followed by deactivation and then unprovision of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-MACHINE_TYPE_NOT_SUPPORTED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service cannot be activated as the machine type specified is not supported </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the support for the machine type and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-MACH_PARSE_FAILURE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has an invalid parameter specified in the .xml file inside the .ova package </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Fix the .xml file inside the .ova package to have valid values. Then retry installing and activating it </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-MEMORY_LIMIT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file is requesting more memory than the system has available for virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-MEMORY_LIMIT_WARN </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual service ([chars])[chars] defines [dec] MB of Memory exceeding the maximum [dec] MB. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file is requesting more memory for the specified profile, than the system has available for virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-MORETHANONE_CPUTUNES_CONFIG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file is requesting more than one CPU tunes parameter. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Use a different valid machine definition file for the virtual service. If the problem persists, then enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-MOVE_STATE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] '[chars]' [chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The move of the core or log file of the named virtual service has as been successful or failed as notified by Virt-manager. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In the failed case, check Virt-manager's logs for the cause of the failure. In the successful case, this notification can be ignored. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-NETWORK_CONFIG_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A network configuration error has been detected for the named virtual service. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-PROCESS_PKG_DEF </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service package for the named virtual service has failed to be validated and the virtual service will not run. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-PROC_INT_LIST </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The interface list embedded in the activate request for the named virtual service could not be processed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-REMOVE_VIRT_INST_ENTRY </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Removing the named virtual service from the virtual service DB tracked by Virt-manager failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-RESET_FORCE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Services non-recoverable reset command processed </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A 'virtual service reset force' command has been entered and processed. This action initiates a cleanup of last resort. Occasionally a VM will get into an unrecoverable state that prevents it from activating but also from uninstalling. This is a rare event but when it happens the only resort may be to remove the .conf control file and reboot, which forces a cleanup of all previously installed VM files and artifacts. Note that once this command is used, current VMs are considered to be in an unstable or unpredictable state, and all future install, uninstall, upgrade, and activation commands will be blocked. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Once the command is entered and accepted, there is no recourse but to restart the system. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-RESIZE_OPER_STATE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual service '[chars]' [chars][chars] to '[dec]' [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> VMAN attempts to resize various VM parameters like rootfs size, CPU share, memory if requested by user. Success/failure status messages for these resize operations are communicated by this syslog. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In the failed case, check Virt-manager's logs for the cause of the failure. Check for the HA event error msg and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-RSYNC_STATE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> VMAN tries to remote sync the virtual-instance configuration file and the OVA repository to all online nodes. If rsync fails even after consecutive retries, this notification would be raised. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> In the failed case, check Virt-manager's logs for the cause of the failure. Check for the rsync error code and root cause the same. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-SET_VTX_ROMVAR_SPACE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Failed to set ROM monitor variable ENABLE_VTX: No space in table </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Failed to set ENABLE_VTX ROM monitor variable due to no space in Monitor Variable Table. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Verify number of entries in Monitor Variable Table. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-SET_VTX_ROMVAR_STRING </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Failed to set ROM monitor variable ENABLE_VTX: Invalid string format: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Failed to set ENABLE_VTX rom monitor variable due to invalid string format. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Verify format of string from error message. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-START_FAILED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service failed to start. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-UNINSTALL_ALL_VMS </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> All Virtual Services are being uninstalled [chars][chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> All virtual services are being uninstalled by Virt-manager. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Examine the reason given as to why all virtual services are being uninstalled for more information. If the reason indicated is due to some error condition, check Virt-manager's logs for the cause of the failure. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-UPGRADE_LOG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] [chars] [chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The upgrade log of the named virtual service, is to provide more information about long running operation, that could affect the control of CLI </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-VCPU_INVALID </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file is requesting invalid VCPU value. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-VCPU_LIMIT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service machine definition file is requesting more VCPUs than the system has reserved for virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-VIRT_INST_CRIT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> VIRTUAL SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-VIRT_INST_DISK </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service requires Disk Storage in excess of the Free Disk Storage available to virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-VIRT_INST_INTERFACE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The number of configured virtual port group interfaces must match the number of Ethernet Network Interfaces defined in the machine definition file </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-VIRT_INST_LOG_UNTHROTTLE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Failed to unthrottle the log for virtual service [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service had sent overwhelming sys log messages and its log had been throttled as a result, but system has failed to unthrottle it for some reason. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> For debugging collect the virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-VIRT_INST_MEMORY </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The virtual service requires physical memory in excess of the free memory available to virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Enable the Virt-manager trace logs and repeat the activation of the virtual service. Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-VIRT_INST_MGMT_INTERFACE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual service [chars] has no management interface defined but it is configured in CLI. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A management interface is configured but none is defined. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Deactivate the virtual service, remove the management interface configuration CLI, and reactivate the virtual-service. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-2-VIRT_INST_STATE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has failed. It is no longer running either because the guest OS has failed, the guest OS has shut down the machine or the emulator has failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> An attempt at restarting the virtual service can be made from the IOS configuration by doing a no activate/activate. For debugging collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-3-PSS_ERR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Purpose: [chars], URI: [chars], errcode: [dec] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Persistent Storage Service handling error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-3-PSS_SNAPSHOT_ERR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Source URI: [chars], Destination URI: [chars], errcode: [dec] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Persistent Storage Service snapshot error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-3-SDWRAP_ERR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Description: [chars], errcode: [dec] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Debug infrastructure error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Collect the Virt-manager logs and scan them for the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-3-VIRT_INST_ERR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> VIRTUAL SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-4-HA_SYNC_NEEDED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> If using the guest shell, please use 'guestshell sync' if you want to preserve state on standby in case of supervisor switchover </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Message notifying user that he needs to manually synchronize the Virtual service contents to standby supervisor in order to preserve these contents in case of a supervisor switchover. Currently only applicable to the guest shell </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> User can type the 'guestshell sync' command on active supervisor to synchronize it's contents to the standby supervisor if desired. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-4-PACKAGE_SIGNING_LEVEL_CHANGED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Package signing level changed from allow '[chars]' to allow '[chars]' </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The package certificate signing level global setting has been changed via configuration under the virtual-service global sub-mode. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Ensure that this setting has been changed as expected by an authorized user. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-4-UPDATE_WARNING </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-4-VIRT_INST_WARN </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> VIRTUAL SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-4-VIRT_SERV_LIBVIRTD_WARN </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> VMAN not able to connect to the libvirt daemon after '[dec]' attempts </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> VMAN has been unable to connect to the libvirt daemon. Virtualization services will not be available until this connection is made. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Collect the logs produced by 'show virt tech' </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-4-WATCHDOG_TIMER </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> [chars] '[chars]' [chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The watchdog timer configured for the named virtual service has expired. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Check any logs produced by the virtual service to determine the cause. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-5-AUX </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The AUX login to a virtual service may allow the user access to system functions that may not have been tested or may interact with the system in unintended ways. Use with caution. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-5-PACKAGE_SIGNING_LEVEL_ON_INSTALL </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Package '[chars]' for service container '[chars]' is '[chars]', [chars] '[chars]' </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> A service container software package with the certificate signing level described is being installed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Take note of the service container and software package. Verify the software package is expected to be (un)signed as described and has the appropriate contents. Uninstall the package if unsure of the package origins. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-5-PERMISSION_DENIED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Virtual Service '[chars]' is not owned by client IOSd </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> An attempt was made to modify a virtual-service that is not owned by by the client. The request was rejected. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-5-VIRT_INST </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> LOG FROM VIRTUAL SERVICE [chars]: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-5-VIRT_INST_NOTICE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> VIRTUAL SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-6-VIRT_INST_INFO </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> VIRTUAL SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> VMAN-7-VIRT_INST_DEBUG </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 7-Debug </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> VIRTUAL SERVICE [chars] LOG: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The named virtual service has triggered the log. Please interpret the log in the context of the virtual services. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> vman </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WDAD_TRACE_MESSAGE-3-WLC_REGULATORY_FILE_PROCESS_ERR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Error : [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Error in regulatory file processing </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WDAD_TRACE_MESSAGE-4-WLC_REGULATORY_FILE_PROCESS_WARN </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Warning: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Regulatory file processing warning message </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WDAD_TRACE_MESSAGE-5-WLC_REGULATORY_FILE_PROCESS_NOTICE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Notice : [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Regulatory file processing notice message </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-rrm </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSERVER-5-CONNECTION_FAILED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> connection failed from host [chars] - [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Failure reason for SSL connection </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ng-web-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSERVER-5-LOGIN_FAILED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Login Un-Successful from host [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Login unsuccessful when user/password is invalid </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ng-web-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSERVER-5-LOGIN_PASSED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Login Successful from host [chars] by user '[chars]' </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Login successful </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ng-web-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSERVER-5-MAX_CONNECTION_REACHED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> HTTP server maximum connection reached '[dec]' </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Maximum HTTP connection reached. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ng-web-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSERVER-5-SESS_LOGOUT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Successfully logged out from host [chars] by user '[chars]' </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Logout successful </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ng-web-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSERVER-5-SESS_TIMEOUT </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 5-Notice </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Session timeout from host [chars] by user '[chars]' </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Session Timeout </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ng-web-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action is required </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSOCKET_SPACES-3-WS_ONBOARDING_DISCONNECTING </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Onboarding websocket to cisco-spaces is disconnecting for reason:[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Onboarding websocket to cisco-spaces is disconnecting </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> spaces-oa </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> If this message occurs, it means onboarding websocket to cisco-spaces is disconnecting </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSOCKET_SPACES-3-WS_ONBOARDING_ERR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Onboarding websocket to cisco-spaces could not be established for error:[chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Onboarding websocket to cisco-spaces could not be established due to errors </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> spaces-oa </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> If this message occurs, it means onboarding websocket to cisco-spaces could not be established due to errors </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSOCKET_SPACES-6-WS_ONBOARDING_DISCONNECTED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Onboarding websocket to cisco-spaces is disconnected </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Onboarding websocket to cisco-spaces is disconnected </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> spaces-oa </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> If this message occurs, it means Onboarding websocket to cisco-spaces is disconnected </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBSOCKET_SPACES-6-WS_ONBOARDING_SUCCESS </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Onboarding websocket to cisco-spaces is successfully established </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Onboarding websocket to cisco-spaces is successfully established </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> spaces-oa </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> If this message occurs, it means onboarding websocket to cisco-spaces is successfully established </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WEBUI-6-INSTALL_OPERATION_INFO </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> User: [chars], Install Operation: [chars] [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> This message is used to indicate that an install operation is being performed via WebUI </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> web-ui-wireless </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> No action required. This is not an error, it is a log message that an install operation is being performed via WebUI </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WLANMGR_TRACE_MESSAGE-2-EWLC_WLANMGR_CRIT_ERR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Wlanmgr Error: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Wlanmgr ewlc Error Message. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WLANMGR_TRACE_MESSAGE-2-EWLC_WLANMGR_CRIT_ERR_TRACE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> WLANMGR Error: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> WLAN configs are not getting pushed to Access points. Make a note of any recent changes made to the network or the device configuration which may have triggered this and proceed to the suggested action. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information. It is suggested to collect archive traces and live process core to analyse the error. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WLANMGR_TRACE_MESSAGE-3-EWLC_WLANMGR_SCHEDULED_WLAN_DISABLE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> WLANs associated with policy profile [chars] are disabled by calendar profile [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Wlanmgr scheduled WLAN disable message. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WLANMGR_TRACE_MESSAGE-3-EWLC_WLANMGR_SCHEDULED_WLAN_ENABLE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> WLANs associated with policy profile [chars] are enabled by calendar profile [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Wlanmgr scheduled WLAN enable message. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WLANMGR_TRACE_MESSAGE-4-EWLC_WLANMGR_WARN </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 4-Warning </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Wlanmgr Warning: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Wlanmgr ewlc Warning Message. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WNCD_ERROR_MESSAGE-3-WNCD_CONFIG_DONE_IPC_FAILURE </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Error: IPC failure to notify wncmgrd on config_done event. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Critical notification to allow AP join </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-app-infra </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WNCD_EWC_ERRMSG-6-INSTALL_CLEANUP_INFO </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 6-Information </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> INSTALL cleanup after switchover: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> General EWC WNCD message </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewcap-image </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WNCMGRD_ERROR_MESSAGE-3-BULK_SYNC_FAIL </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Error: Bulk sync not complete. Reloading the WLC! </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Switchover happened before bulk sync is complete! </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WNCMGRD_ERROR_MESSAGE-3-HA_PAIR_ERROR </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> Error: Number of wncd instances mismatched between active and standby; HA function will not function correctly. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> Resource provision is different on active and standby </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> ewlc-ha </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WSA_ICAP_MESSAGE-3-EWLC_WSA_ICAP </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 3-Error </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> %% Error: ICap: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> General ewlc ICap config failure </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> LOG_STD_ACTION </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WUILOGIN-2-AUTHENTICATION_SYSTEM_FAILED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> WebUI standalone authentication process failed. Reason: [chars] </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> During the id and password validation phase of the wuilogin access module authentication attempt, an exception occurred. This message usually occurs as a result of a failure of the underlying PAM authentication module. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Note the time of the error and check the web user interface log (wuilogin-*.log) for additional information on why the attempt to access the web user interface failed. </td> </tr> <tr> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__1 "> WUILOGIN-2-INITIALIZATION_FAILED </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__2 "> 2-Critical </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__3 "> WebUI standalone login initialization failed. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__4 "> The attempt to access the web user interface using the wuilogin access module failed. The wuilogin access module is used to authenticate web user interface access only when the IOS integrated webserver, which is enabled using the ip http server command, or the IOS process is down or disabled. </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__5 "> iosxe-binos-utils </td> <td class="entry align-left" headers="r-u-to-z-syslogs_17161__entry__6 "> Note the time of the error and check the web user interface log (wuilogin-*.log) for additional information on why the attempt to access the web user interface failed. </td> </tr> </tbody> </table> </section> </div>  <nav role="navigation" class="related-links"></nav>  </article> </article> <article class="topic reference nested1" aria-labelledby="ariaid-title11" lang="en-US" id="id_129698"> <h2 class="title topictitle2" id="ariaid-title11">Additional References</h2> <div class="body refbody"> <section class="section" id="id_129698__d54e66286"> <h3 class="title sectiontitle">Technical Assistance</h3> When the recommended action of an error message advises that you contact Cisco technical support, open a case with the Cisco Technical Assistance Center (TAC). <table width="100%" border="1" class="table frame-all"> <caption></caption> <colgroup> <col style="width:50%"> <col style="width:50%"> </colgroup> <thead class="thead"> <tr> <th font-weight="bold" class="entry colsep-1 rowsep-1" id="id_129698__entry__1"> Description </th> <th font-weight="bold" class="entry colsep-1 rowsep-1" id="id_129698__entry__2"> Link </th> </tr> </thead> <tbody class="tbody"> <tr> <td class="entry colsep-1 rowsep-1" headers="id_129698__entry__1 "> The Cisco Support website provides extensive online resources, including documentation and tools for troubleshooting and resolving technical issues with Cisco products and technologies. To receive security and technical information about your products, you can subscribe to various services, such as the Product Alert Tool (accessed from Field Notices), the Cisco Technical Services Newsletter, and Really Simple Syndication (RSS) Feeds. Access to most tools on the Cisco Support website requires a Cisco.com user ID and password. </td> <td class="entry colsep-1 rowsep-1" headers="id_129698__entry__2 "> <a class="xref" href="https://www.cisco.com/c/en/us/support/index.html" target="_blank">https://www.cisco.com/c/en/us/support/index.html</a> </td> </tr> </tbody> </table> </section> </div>  <nav role="navigation" class="related-links"></nav>  </article> </article> </article> </main> <footer class="copyright">Copyright 漏 2024, Cisco Systems, Inc. All rights reserved.</footer> <cdc:do action="com.cisco.wem.framework.service.command.eotcontent.EOTResponsiveContent@41e6d3dc" returnTypedAs="eotResponsiveContainerVo" id="eotResponsiveContainerVo" /> <div class="row full visitedlinks" style="padding: 0px; margin:0px"> <div class="col full" > </div> </div> </div> <script> if (window.cdc === undefined) { cdc = {}; } if (cdc.eot === undefined) { cdc.eot = {}; } cdc.eot.isEot = true; cdc.eot.isToc = false; jQuery(document).ready(function () { if (jQuery('.unpublished').length > 0) { let lastRel = "1.0"; if (jQuery('.published').length > 0) { lastRel = Number(jQuery('.published td')[0].innerText) + 1 + ".0"; } jQuery('.preview_revision').text(lastRel); } const linkItemsLen = jQuery("#eot-doc-wrapper link[rel='stylesheet']").length; function addNewTocStyleSheet() { let fileName="/etc/designs/cdc/transformation/wemdcmt_responsive.css", $head = jQuery("head"), linkElement = "<link rel='stylesheet' href='"+fileName+"' type='text/css' >"; $head.append(linkElement); } if (cdc.eot.isToc && !linkItemsLen) { addNewTocStyleSheet(); } else if (cdc.eot.isEot) { jQuery("#eot-doc-wrapper link[rel='stylesheet']").each(function () { const linkTag = jQuery(this), hrefVal = jQuery(linkTag).attr("href"); if (hrefVal != undefined && hrefVal.indexOf("support-responsive.css") == -1 && hrefVal.indexOf("_responsive.css") == -1) { let fileName = hrefVal.substr(hrefVal.lastIndexOf("/") + 1, hrefVal.length).split(".css")[0]; const filePath = "/etc/designs/cdc/transformation/"; if (fileName == "ccimr") { fileName = "techdocs_responsive"; } else if (fileName == "support-docs") { fileName = "support-responsive"; } else if (fileName == "framework") { fileName = "responsiveframework"; } else if (fileName == "dcmt") { fileName = "wemdcmt_responsive"; } else if (fileName == "techdocs_85_11_word") { fileName = "techdocs_85_11_word"; if (cdc.eot.isToc) { addNewTocStyleSheet(); } } else { fileName += "_responsive"; } jQuery(linkTag).attr("href", filePath + fileName + ".css"); } if (hrefVal.indexOf("support-responsive.css") > -1) { jQuery(linkTag).attr("href", "/etc/designs/cdc/transformation/support-responsive.css"); } }); jQuery("#eot-doc-wrapper > table").wrap("<div></div>"); jQuery("#eot-doc-wrapper table:not('.olh_note')").parent().css({ overflowX: "auto" }); } }); </script> </div> <div class="col narrow-v2"> <div class="rightRailComponent base-blowout"> <div class="eotPersonalization"> <section id="eotTDCampaign"></section> </div>   <div> <div class="tac-image"> <script type="text/javascript"> document.getElementsByClassName('tac-image')[0].parentElement.style.display="none"; </script> </div> </div> <div class="hideComponent"> <div class="eot-authors"> <ul> </ul> </div> </div>  <div class="eot-feedback-container"> <div class="eot-feedback"> <h3>Was this Document Helpful?</h3> <button class="eot-feedback-btn eot-feedback-btn-yes" aria-label="Was this Document Helpful?? Yes">Yes</button> <button class="eot-feedback-btn eot-feedback-btn-no" aria-label="Was this Document Helpful?? No">No</button> <a href="javascript: void(0);" class="eot-feedback-ol" onclick="window.open('https://ciscocx.qualtrics.com/jfe/form/SV_be0fHnqDoKM7sto?Ref=' + location.href + '&resize=false', 'feedback', 'width=650, height=460, scrollbars=1, menubar=1, resizable=1'); return false;"> <img id="feedback_img" border="0" style="cursor: pointer;" title="Feedback" src="//www.cisco.com/c/dam/cdc/i/Feedback_OceanBlue.png" alt="Feedback">Feedback</a> </div> </div> <div class="showComponent"> <div class="eot-vav"> <ul> </ul> </div> </div> <div class="showComponent"> <div class="eotLetUsHelp"> <h3>Contact Cisco</h3> <ul> <li><a id="eotLetUsHelpProdDocUrl" href="https://mycase.cloudapps.cisco.com/start?prodDocUrl=">Open a Support Case</a><img src="/etc/designs/cdc/fw/i/icon_lock_small.png" alt="login required"/></li> <li>(Requires a <a href="//www.cisco.com/c/en/us/services/order-services.html">Cisco Service Contract</a>)</li> </ul> </div> <script> jQuery(document).ready(function() { var getURL=jQuery("#eotLetUsHelpProdDocUrl").attr("href"), domInd = location.href.indexOf('cisco.com') ; if ( domInd > -1 && domInd < location.href.search(/\w\/\w/) ) { getURL += encodeURI(location.href); } jQuery("#eotLetUsHelpProdDocUrl").attr("href",getURL); }); </script> </div>  <div id="eotRightRailMBox">  <div> <div class="mboxDefault"></div> <script type="text/javascript"> var test=""; if(test!=undefined && test.trim().length>0){ mboxCreate('en-us_dg_support_eot','type=default',''); }else{ mboxCreate('en-us_dg_support_eot','type=default'); } </script> </div> </div> <div class="showComponent"> <div class="eot-tdatp"> <h3>This Document Applies to These Products</h3> <ul class="eot-tdatp-list"> <li><a href="/c/en/us/support/routers/1000-series-integrated-services-routers-isr/series.html">1000 Series Integrated Services Routers</a></li> <li><a href="/c/en/us/support/routers/4000-series-integrated-services-routers-isr/series.html">4000 Series Integrated Services Routers</a></li> <li><a href="/c/en/us/support/routers/asr-903-series-aggregation-services-routers/series.html">ASR 900 Series Aggregation Services Routers</a></li> <li><a href="/c/en/us/support/routers/asr-920-series-aggregation-services-router/series.html">ASR 920 Series Aggregation Services Router</a></li> <li><a href="/c/en/us/support/routers/asr-1000-series-aggregation-services-routers/series.html">ASR 1000 Series Aggregation Services Routers</a></li> <li><a href="/c/en/us/support/routers/catalyst-8000v-edge-software/series.html">Catalyst 8000V Edge Software</a></li> <li><a href="/c/en/us/support/routers/catalyst-8200-series-edge-platforms/series.html">Catalyst 8200 Series Edge Platforms</a></li> <li><a href="/c/en/us/support/routers/catalyst-8300-series-edge-platforms/series.html">Catalyst 8300 Series Edge Platforms</a></li> <li><a href="/c/en/us/support/routers/catalyst-8500-series-edge-platforms/series.html">Catalyst 8500 Series Edge Platforms</a></li> <li><a href="/c/en/us/support/switches/catalyst-9200-r-series-switches/series.html">Catalyst 9200 Series Switches</a></li> <li><a href="/c/en/us/support/switches/catalyst-9300-series-switches/series.html">Catalyst 9300 Series Switches</a></li> <li><a href="/c/en/us/support/switches/catalyst-9400-series-switches/series.html">Catalyst 9400 Series Switches</a></li> <li><a href="/c/en/us/support/switches/catalyst-9500-series-switches/series.html">Catalyst 9500 Series Switches</a></li> <li><a href="/c/en/us/support/switches/catalyst-9600-series-switches/series.html">Catalyst 9600 Series Switches</a></li> <li><a href="/c/en/us/support/wireless/catalyst-9800-series-wireless-controllers/series.html">Catalyst 9800 Series Wireless Controllers</a></li> <li><a href="/c/en/us/support/switches/catalyst-ess9300-embedded-series/series.html">Catalyst ESS9300 Embedded Series Switch</a></li> <li><a href="/c/en/us/support/switches/catalyst-ie3200-rugged-series/series.html">Catalyst IE3200 Rugged Series</a></li> <li><a href="/c/en/us/support/switches/catalyst-ie3300-rugged-series/series.html">Catalyst IE3300 Rugged Series</a></li> <li><a href="/c/en/us/support/switches/catalyst-ie3400-heavy-duty-series/series.html">Catalyst IE3400 Heavy Duty Series</a></li> <li><a href="/c/en/us/support/switches/catalyst-ie3400-rugged-series/series.html">Catalyst IE3400 Rugged Series</a></li> <li><a href="/c/en/us/support/routers/1100-series-industrial-integrated-services-routers/series.html">Catalyst IR1100 Rugged Series Routers</a></li> <li><a href="/c/en/us/support/routers/catalyst-ir1800-rugged-series-routers/series.html">Catalyst IR1800 Rugged Series Routers</a></li> <li><a href="/c/en/us/support/routers/catalyst-ir8100-heavy-duty-series-routers/series.html">Catalyst IR8100 Heavy Duty Series Routers</a></li> <li><a href="/c/en/us/support/routers/6300-series-embedded-service-routers/series.html">ESR6300 Embedded Series Routers</a></li> <li><a href="/c/en/us/support/switches/embedded-service-3000-series-switches/series.html">Embedded Services 3300 Series Switches</a></li> <li><a href="/c/en/us/support/ios-nx-os-software/ios-xe-17-16-1/model.html">IOS XE 17.16.1</a></li> <li><a href="/c/en/us/support/routers/network-convergence-system-500-series-routers/series.html">Network Convergence System 500 Series Routers</a></li> <li><a href="/c/en/us/support/routers/sd-wan/series.html">SD-WAN</a></li> <li><a href="/c/en/us/support/wireless/wireless-lan-controller-software/series.html">Wireless LAN Controller Software</a></li> </ul> <button class="eot-show5" showing5="true"></button> </div> </div> <div class="showClass"> </div> </div> </div> </div>   </div> <script type="module" src="/site/web-components/us/en/cdc-footer.js"></script> <cdc-footer></cdc-footer> <script type="text/javascript"> if(document.querySelector('#privacy-manager')!=null){ document.querySelector('#privacy-manager').href='#cookies'; } </script> <div id="fw-overlay"></div> <script src="/etc/designs/cdc/fw/b/responsive/js/eot.min.js"></script> <script src="/c/dam/cdc/t/ctm.js" type="text/javascript"></script>  <noscript><img src="//cisco.112.2o7.net/b/ss/cisco-mobile/5/12345" width="2" height="2" border="0" alt=""/></noscript> </body> </html>

CINXE.COM

System Message Guide for Cisco IOS XE 17.16.x - Cisco