Mistral-3-error
Catalyst 6500 Series SwitchesTroubleshoot and AlertsTroubleshooting TechNotes Troubleshooting Hardware and Related Issues on the MSFC, MSFC2, and MSFC2a Download Print Available Languages Download Options PDF (97.8 KB) View with Adobe Reader on a variety of devices Updated:Aug 17, 2006 Document ID:18000 Contents Introduction Prerequisites Requirements Components Used Conventions Platform Description Capture Information Troubleshoot General Issues MSFC or MSFC2 Is Not in the show module Command Output MSFC or MSFC2 Does Not Respond to the telnet or session x Command MSFC or MSFC2 throws SYS-6-READ_BOOTFILE_FAIL error while booting Format of the Bootflash Causes %SYS-3-CPUHOG Messages MSFC Reloads and Goes into ROMmon Mode After the Error "PFC Version Detected Does Not Match Configured Version" An Unsupported Memory Configuration Message Displays After a Memory Upgrade %IPC-5-NULL: Registering Control Port Id=0x2210003 Message Displays Every 30 Seconds %AAAA-3-BADREG: Illegal registry call Message Displays MSFC2a Goes into ROMmon Mode After Conversion of the Supervisor Engine 32 from CatOS to Cisco IOS Software Disable Telnet Access to MSFC Unable to Read the External Flash Card from MSFC2 How to Disable the MSFC or Routing Module Troubleshoot MSFC Crash Issues MSFC2 Crashes with Mistral-3-Error Messages in the Crashinfo File MSFC Crashes with a Parity Error MSFC2 Crashes with a Parity Error MSFC Crashes with a Bus Error Exception Related Information Introduction This document helps to troubleshoot issues with the Multilayer Switch Feature Card (MSFC) and the MSFC2 for the Cisco Catalyst 6500/6000 series switches and the Cisco 7600 series routers. Note:This document does not contain information about how to troubleshoot the software configuration or troubleshoot Multilayer Switching (MLS) or Cisco Express Forwarding (CEF) issues on the MSFC. Refer to these documents for more information: Configuring and Troubleshooting IP MLS on Catalyst 6500/6000 Switches with an MSFC Troubleshoot Unicast IP Routing Involving CEF on Catalyst 6500/6000 Series Switches with a Supervisor Engine 2 and Running CatOS System Software In order to troubleshoot the Supervisor Engine, refer to these documents: Troubleshooting Catalyst 6500/6000 Series Switches Running CatOS on the Supervisor Engine and Cisco IOS on the MSFC Hardware Failure Checklist for Catalyst 4500/4000, 5500/5000, and 6500/6000 Series Switches Running CatOS Prerequisites Requirements A thorough product overview ahead of time can prevent the hardware problems that occ
7300 Series RoutersTroubleshoot and AlertsError and System Messages System Error Messages for the Cisco 7304 Router Download Print Available Languages Download Options PDF (541.4 KB) View with Adobe Reader on a variety of devices Updated:May 04, 2007 System Error Messages for the Cisco 7304 Router Table Of Contents System Error Messages for the Cisco 7304 Router System Error Messages for the Cisco 7304 Router Note This document only covers system error messages for the messages in pre-Cisco IOS Release 12.2S release trains. For the system messages on Cisco 7304 routers using Cisco IOS Release 12.2S, see System Messages for 12.2S. This document provides explanations and recommended actions for all of the system error messages that are http://www.cisco.com/c/en/us/support/docs/switches/catalyst-6000-series-switches/18000-hwts-msfc-18000.html unique to the Cisco 7304 router. This document currently provides explanations and recommended actions for all of the system error messages that were introduced in the Early Deployment software releases that can be used to run the Cisco 7304 router. These releases include: •Cisco IOS Releases 12.1(9)EX through 12.1(13)EX3 •Cisco IOS Release 12.2(11)YZ •Cisco IOS Release 12.2(14)SZ through 12.2(14)SZ3 This document only covers system error messages for the messages in pre-Cisco IOS Release 12.2S release trains. For http://www.cisco.com/c/en/us/td/docs/routers/7300/troubleshooting/7304_troubleshooting_guides/1669err.html the system messages on Cisco 7304 routers using Cisco IOS Release 12.2S, see System Messages for 12.2S. Many of the Cisco IOS releases that run the Cisco 7304 router are based on Cisco IOS Release 12.1E. Therefore, many of the error messages that could occur in Cisco IOS Release12.1E can also occur in these software releases. These error messages, however, are not covered in this document. Similarly, the error messages that could occur in Cisco IOS Release 12.2 can also occur on the Cisco 7304 running Cisco IOS Release 12.2(11)YZ but are not covered in this document. Error Message %ATMLC-1-INITFAIL : The ATM linecard in slot [dec] failed to initialize (cause [chars]) Explanation The ATM line card has failed its initialization as indicated in the message. The problem can be any one of the following: 1) memory allocation failure for control data, 2) framer, ATM SAR devices, or line card FPGA access failure, 3) uncorretable multi-bit ECC errors in line card memory, 4) PCI bus timeout, 5) failure of downloading ATM SAR firmware to the SAR devices, or 6) ATM SAR device (reassembler or segmenter) does not boot up or does not respond to configuration commands. Recommended Action Consult your line card installation and configuration guide and make sure the line card is properly installed and configured. If the line card is properly installed, perform an online insertion and
today. "Nov 7 08:52:28: %MISTRAL-3-ERROR: Error condition detected: TM_DATA_PARITY_ERROR" this appears only one time, and i checked the cisco.com, and found this explanation: "The most common errors from the Mistral ASIC on the MSFC are TM_DATA_PARITY_ERROR, SYSDRAM_PARITY_ERROR, http://www.velocityreviews.com/threads/tm_data_parity_error.709001/ SYSAD_PARITY_ERROR, and TM_NPP_PARITY_ERROR. Possible causes of these parity errors are random static discharge or other external https://github.com/StackStorm/st2/blob/master/contrib/examples/actions/workflows/mistral-handle-error-task-default.yaml factors." has anyone had come across this error before? do i have to do anything except monitoring the switch syslog to confirm whether the error message was an isolated one? Ethan Mao, Dec 17, 2009 #1 Advertisements bod43 Guest On 17 Dec, 04:48, Ethan Mao <> wrote: > i found this error in syslog when i check the cisco 6509 today. > > "Nov 7 08:52:28: %MISTRAL-3-ERROR: Error condition detected: > TM_DATA_PARITY_ERROR" > > this appears only one time, and i checked the cisco.com, and found > this explanation: > "The most common errors from the Mistral ASIC on the MSFC are > TM_DATA_PARITY_ERROR, > SYSDRAM_PARITY_ERROR, SYSAD_PARITY_ERROR, and TM_NPP_PARITY_ERROR. > Possible causes of these parity errors are random static discharge or > other external factors." > > has anyone had come across this error before? do i have to do anything > except monitoring the switch syslog to confirm whether the error > message was an isolated one? I wouldn't be concerned unless the message was repeated. bod43, Dec 17, 2009 #2 Advertisements Show Ignored Content Want to reply to this thread or ask your own question? It takes just 2 minutes to sign up (and it's free!). Just click the sign up button to choose a username and then you can ask your own questions on the forum. Sign Up Now! Your name or email address: Do you already have an account? No, create an account now. Yes, my password is: Forgot your password? Stay logged in Welcome to Velocity Reviews! Welcome to the Velocity Reviews, the place to come for the latest tech news and reviews. Please join our friendly community by clicking the button below - it only takes a few seconds and is totally free. You'll be able to chat with other enthusiasts and get tech help from other members. Sign up now! Member Login Remember Me Forgot your password? Advertisements Latest Threads Rosewill Cullinan Gaming Case Becky posted Oct 20, 2016 at 5:40 PM PlayStation VR Becky posted Oct 19, 2016 at 4:51 PM Samsung 960 Pro 2TB NVMe M.2... Becky posted Oct 18, 2016 at 6:03 PM MSI GeForce GTX 1070 GAMING X... Becky posted Oct 17, 2016 at 5:43 PM Roccat Skeltr Smart RGB Gaming... Beck
Sign in Pricing Blog Support Search GitHub This repository Watch 93 Star 1,621 Fork 186 StackStorm/st2 Code Issues 141 Pull requests 12 Projects 0 Pulse Graphs Permalink Branch: master Switch branches/tags Branches Tags 07 DZ/add_chatops_to_st2ctl Itxaka-add_keystone_backend add_user api_key_qs_docs bundle_newer_version_of_virtualenv certifi-storage chatops-review-fixes cli_updates deploy_from_repo docker_compat drop_obsolete_indexes_in_db_setup_step e_fix el7_support extra-fix-14 extra-fix feature/complete_script feature/execution_route feature/pack_api feature/pack_config_2 feature/packs_register_unified feature/packs feature/rest_services_v2 fix-launchdev fix-mistral-querier fix-self-check fix_action_service_datastore_access fix/always_remove_auth_query fix_bug_with_api_server_not_shutting_down fix_config_and_service_argument_consistency fix_notification_empty_check fix/rerun_param_exclusion fix/st2ctl-hubot-status fix/web_services functools32_fix hook_up_runner_disable increase_sleep install-index-repair jamiees2-windows_script_args local_runner_changes local_runner_sudo_use_login_shell master mistral-abstract-auth mistral-cancel-state model-adjustments pack_configuration_from_datastore pack_configuration_v2_pack_configs packs_install_reload_timeout pkg_test port_file_watch_sensor_to_use_trigger_with_parameters reduce_logging_verbosity_in_views remove_old_fabric_runner_code rename-st2bundle-to-st2 revert-2165-st2tests_branch revert-2281-rule_list_display_fixes revert-2474-localhost_to_127.0.0.1 revert-2497-v1.3.2 revert-2763-STORM-2195/user_scoped_params_as_jinja revert-2766-v1.5_user_scoped_params_as_jinja runner_migration_script self-check-fix-v13 self_check_script sensor-instances sensor_wrapper_fix set-e-no-more specify_min_pip_version st2-exchange start_webui_in_launchdev upda