OSI/MHS Configuration and Management Manual

Planning Your OSI/MHS Subsystem

OSI/MHS Configuration and Management Manual—424827-003

3-13

Link Retries and Route Retries

If a message or probe cannot be delivered before the retry time limit specified by the

appropriate RETRY-TIME attribute, the subsystem generates a nondelivery report. If

a report cannot be delivered, the subsystem generates an error event.

Figure 3-5. Link and Route-Retry Attribute Relationships

MTA1

MTA2

MTA3

9 10

PRMD 1

Message arrives at MTA 3 from MTA4, for delivery to user at MTA1. Retrieve arrival time in

domain from message; ROUTE-RETRY-TIME is measured from that time.

Try link 1 on route 1. LINK-RETRY-TIME is measured from here.

Try link 2 on route 1.

Try link 3 on route 1.

Wait LINK-RETRY-DELAY. If LINK-RETRY-TIME has not expired, go back to 2, but don't reset

LINK-RETRY-TIME. If LINK-RETRY-TIME has expired, go to 6.

Try link 1 on route 2. LINK-RETRY-TIME is measured from here.

Try link 2 on route 2.

Try link 3 on route 2.

Try link 4 on route 2.

Wait LINK-RETRY-DELAY. If LINK-RETRY-TIME has not expired, go back to 6, but don't reset

LINK-RETRY-TIME. If LINK-RETRY-TIME has expired, go to 11.

Wait xxx-ROUTE-RETRY-DELAY * (1 + xxx-ROUTE-RETRY-GROW/100) ^ attempts. If ROUTE-

RETRY-TIME has not expired, go back to 2. If ROUTE-RETRY-TIME has expired, send

nondelivery notification.

Route 1

links)

Route 2

links)

From

MTA4

057VST .VSD