candie
Uploaded by
1 SLIDES
139 VUES
10LIKES

Fault Scenario Management: Node Trigger Actions and Message Handling in Networks

DESCRIPTION

This document explores fault scenario management in network systems, focusing on the entry and trigger actions of nodes. It details how specific actions occur upon certain message triggers and the consequences of message loss and mutilation. We examine the migration of messages and data, logging actions for monitoring purposes, and handling memory mutilation. Additionally, we cover how to address memory content changes and document the process of migrating to specific nodes while ensuring data integrity.

1 / 1

Télécharger la présentation

Fault Scenario Management: Node Trigger Actions and Message Handling in Networks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

Playing audio...

  1. fault scenario → entry + entry → ON node trigger action + node → NODEnumber trigger → AT_TIMEnumber | ON_MESSAGEmessage name action → fi_action| migration | log_action| TERMINATE fiaction → message_loss| message_mutilation| memory_mutilation messageloss → LOSE_MESSAGE message_name messagemutilation → CHANGE_MESSAGE_CONTENTmessage_nameTOdata memory mutilation → CHANGE_EMORY_CONTENTlocation TO data migration → MIGRATE_TO node log action → message_log| memory_log message log → LOG_MESSAGE_CONTENTmessage_name memory log → LOG_MEMORY_CONTENTlocation location → address | variable_name address → number variable name → /* identifier */ message name → /* arbitrary character sequence */ data → /* bytesequence */ number → /* sequenceofdigits */

More Related