This type is not a standard SMI/SNMP base type and is not defined as a documented TEXTUAL-CONVENTION in this MIB.
It was extracted as raw syntax from the source MIB file and could not be resolved to a known type definition.
When summary or cluster routes are specified this field
will provide additional information about the fully
qualified routes within the specified clusters. Since,
summary or cluster routes represent a group of
destinations it is necessary to collect and maintain
status information on routes that are not available.
Additional, route statements are created dynamically
whenever a TFP or TFR is received on a fully qualified
route represented by a defined summary route. There are
three four types of dynamic route as follows.
List of the possible route status values.
'unknown': Undefined type of route.
'static': A fully-qualified route configured by system
administrator.
'cluster': An ANSI cluster route. A DPC and mask
with length of 16 bits configured by system
administrator.
'summary': An DPC and a mask with length 0-10 for ITU and
0-15,17-23 for ANSI. A summary route is configured by
a system administrator.
'xlist': This route is dynamic and is create whenever TFP
or TFR is received for a point-code represented by a
ANSI cluster route.
'shadow': When a TFP or TFR is received for a point-code
represented by a summary or cluster route all route
statements specified for the summary or cluster
destination are copied. These new routes appear
under the specific fully-qualified destination.
The route will be marked as a shadow when a TFP or
TFR has not been received for that particular route.
'management' : When a TFP or TFR is received for a
point-code represented by a summary route all route
statements specified for the summary destination are
copied. The new routes appear under the
fully-qualified destination specified in the TFR or
TFP. The route specified in the TFR or TFP will be
marked as a dynamic to indicate that MTP3 route
management information is available for this route.
'alias': Route statement is created in response
to conversion statements defined to alias point-codes
across networks.