 | Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |
When a line module receives an MDL message string, it stores the strings for a period of 10 seconds after the last message was received. If the line module does not receive another message of any type containing the same string within 10 seconds, it erases the local copy of the message.
Most MDL message strings are common to all three types of messages that can be transmitted: path identifications, idle signals, and test signals. Certain message strings, however, are unique to a particular message type. Table 6 briefly describes each MDL message string and indicates (with a a) the types of messages in which it can be sent.
Table 6: MDL Message Strings and Message Types
As long as another message of any type containing the same string is received within 10 seconds, the line module retains the local copy of the message string and resets the 10-second timer for that string.
For example, if a line module receives an MDL test signal message containing an eic string, and then receives a idle signal message within 10 seconds that also contains an eic string, it retains the local copy of the most recent eic string received and resets the 10-second timer for that message. However, if 10 seconds pass without the line module receiving a path identification, test signal, or idle signal message containing an eic string, the line module erases the local copy of the eic message string.
For message strings that are unique to a particular message type, the line module must receive another message of the same type containing this string in order to retain the local copy of the string and reset the timer. For example, if the line module receives a test signal message containing a generator string and does not receive another test signal message within 10 seconds, it will erase the local copy of the generator string.
| Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice. | |