set [node node-id] routing ...
Modifies attributes of the routing entity. Support for the
various attributes depends upon the routing type of the
node (End, L1, L2, IP). The modifiable routing attributes
and their data types [in brackets] are:
area authentication type [none or simple]
area receive passwords [set of hex-string]
area send password [hex-string]
autonomous system number [integer]
dna address format [boolean]
default eshello timer [integer]
domain authentication type [none or simple]
domain receive passwords [set of hex-string]
domain send password [hex-string]
generate checksums [boolean]
lifetime [integer]
manual area addresses [set of area addresses]
manual L1 algorithm [string]
manual L2 algorithm [string]
manual network entity titles [set of NETs]
maximum buffers [integer]
maximum path splits [integer]
phaseiv address [ph4-address]
phaseiv prefix [address-prefix]
phaseiv area maximum cost [integer]
phaseiv area maximum hops [integer]
phaseiv broadcast routing timer [integer]
phaseiv buffer size [integer]
phaseiv maximum address [integer]
phaseiv maximum area [integer]
phaseiv maximum cost [integer]
phaseiv maximum hops [integer]
phaseiv maximum visits [integer]
probe rate [integer]
protocols [IP or ISO 8473]
redirect holding time [integer]
routing mode [integrated or segregated]
segment buffer size [integer]
send source quench [boolean]
source quench interval [boolean]
summary addresses [set of summary-address]
time to live [integer]
Refer to the specific attributes for more information.
Select circuit to view the modifiable attributes of a routing
circuit, a routing circuit ip reachable address, or a routing
circuit reachable address.
Select egp_group to view the modifiable attributes of a
routing egp group.
Select permitted_neighbor for information on modifying the
verifier attribute of a routing permitted neighbor.
1 – area_authentication_type
Support: L1,IP
Default: None Value: None or simple
Type of authentication to be used for level 1 LSPs, PSNPs, and
CSNPs.
2 – area_receive_passwords
Support: L1,IP
Default: No passwords Value: Set of hex-string
Set of passwords that are valid in level 1 LSPs, PSNPs, and CSNPs
when simple authentication is in use. You cannot use the show
command to display the value of this attribute.
3 – area_send_password
Support: L1,IP
Default: No password Value: Hex-string
Password to be sent in level 1 LSPs, PSNPs, and CSNPs when simple
authentication is in use. You cannot use the show command to
display the value of this attribute.
4 – autonomous_system_number
Support: IP
Default: 0 Value: 0-65535
Autonomous system number of the local system. This characteristic
is supported only if the value of the routing protocols supported
characteristic includes EGP. You can modify this characteristic
only when the status attribute routing state is off.
5 – dna_address_format
Support: End
Default: True Value: True or false
If true, specifies that NSAP addresses are DNA structured, and
that NSAP address autoconfiguring is possible. If false, this
specifies that NSAP addresses for this node are constructed
from the characteristic manual network entity titles and the
selectors supplied by the transport protocol module (NSP and/or
OSI transport).
The DNA address format attribute controls only the interpretation
of address structuring and no longer controls autoconfiguration.
To control autoconfiguration, you need to use the manual network
entity titles attribute by manually adding or removing NETs.
set [node node-id] routing dna address format boolean
Example:
set routing dna address format true
6 – default_eshello_timer
Default: 600 Value: 1-65535
Value to be used for current suggested hello timer in the absence
of any suggested values from the IS.
set [node node-id] routing default eshello timer integer
Example:
set routing default eshello timer 600
7 – domain_authentication_type
Support: L2,IP
Default: None Value: None or simple
Type of authentication to be used for level 2 LSPs, PSNPs, and
CSNPs.
8 – domain_receive_passwords
Support: L2,IP
Default: No passwords Value: Set of hex-string
Set of passwords that are valid in level 2 LSPs, PSNPs, and CSNPs
when simple authentication is in use. You cannot use the show
command to display the value of this attribute.
9 – domain_send_password
Support: L2,IP
Default: No password Value: Hex-string
Password to be sent in level 2 LSPs, PSNPs, and CSNPs when simple
authentication is in use. You cannot use the show command to
display the value of this attribute.
10 – generate_checksums
Support: All
Default: False Value: True or false
If true, specifies that checksums are generated for data, error
report, and ES-IS PDUs initiated by this node. If false, these
checksums are not generated. It is strongly recommended that,
for performance reasons, you use the default value (indicating no
checksum generation).
11 – lifetime
Support: All
Default: 63 Value: 2-255
Value to be placed in the "lifetime" field of originating data
packets. This value should be greater than the maximum number of
hops in any path in the network, plus the maximum packet lifetime
in half-seconds.
12 – manual_area_addresses
Support: L1,L2
Default: No area Value: Set of area addresses
addresses
Area addresses to be used for this node. An area address cannot
be a Phase IV address or the address DefaultArea.
If the characteristic manual L1 algorithm has the value routing
vector, this set must be empty, and the characteristic phase iv
address must not be 0.0. If the characteristic phase iv address
is 0.0, there must be at least one area address.
13 – manual L1 algorithm
Support: L1
Default: Routing Value: See description
vector
Type of routing algorithm to be used within the area. You can
modify this characteristic only when the entity is disabled.
link state The DECnet-Plus link-state algorithm is used.
routing The Phase IV routing-vector algorithm is used.
vector
14 – manual L2 algorithm
Support: L2
Default: Routing Value: See description
vector
Type of routing algorithm to be used at level 2. You can modify
this characteristic only when the entity is disabled.
link state The DECnet-Plus link-state algorithm is used.
routing The Phase IV routing-vector algorithm is used.
vector
15 – manual_network_entity_titles
Support: End
Default: No NETs Value: Set of NETs
Network entity titles (NETs) to be used for this node. If the
characteristic dna address format is set to false, there must be
at least one NET.
set [node node-id] routing manual network entity titles {NET[,NET...]}
Example:
set routing manual network entity titles -
{49::00-04:AA-00-04-00-45-13:00}
16 – maximum_buffers
Default: 100 Value: 0-65535
Specifies the guaranteed number of buffers for forwarding. More
buffers may be used if they are available. You can only increase
the characteristic value.
17 – maximum_path_splits
Support: L1,L2
Default: 2 Value: 1-32
Maximum number of equal cost paths to split traffic between. You
can modify this characteristic only when the entity is disabled.
18 – phaseiv_address
Support: All
Default: 0.0 Value: PhaseIV address
Specifies a Phase IV compatible address for communication with
other Phase IV nodes. The default address, 0.0, indicates that
no Phase IV compatible address is provided for the node. You can
modify this characteristic only when the entity is disabled.
set [node node-id] routing phaseiv address phiv-address
Example:
set routing phaseiv address = 4.863
19 – phaseiv_area_maximum_cost
Support: L2
Default: 1022 Value: 1-1022
Maximum cost of a path to a reachable Phase IV area. This
characteristic is only used by the Phase IV routing algorithm
(that is, the routing-vector algorithm).
20 – phaseiv_area_maximum_hops
Support: L2
Default: 30 Value: 1-30
Maximum number of hops in a path to a reachable Phase IV
area. This characteristic is only used by the Phase IV routing
algorithm (that is, the routing-vector algorithm).
21 – phaseiv_broadcast_routing_timer
Support: L1,L2
Default: 10 Value: 1-65535
Maximum interval, in seconds, between broadcast routing messages
on broadcast circuits. This characteristic is only used by
the Phase IV routing algorithm (that is, the routing-vector
algorithm).
22 – phaseiv_buffer_size
Support: All
Default: 576 Value: 1-65535
Size, in octets, of buffers used for routing to adjacent Phase IV
nodes. This value is actually six octets greater than the maximum
buffer size, and does not include the headers for the Routing and
Data Link layers.
23 – phaseiv_maximum_address
Support: L1,L2
Default: 1023 Value: 1-1023
Maximum node number within the Phase IV area. This characteristic
is only used by the Phase IV routing algorithm (that is, the
routing-vector algorithm).
24 – phaseiv_maximum_area
Support: L2
Default: 63 Value: 1-63
Maximum Phase IV area number. This characteristic is only used
by the Phase IV routing algorithm (that is, the routing-vector
algorithm).
25 – phaseiv_maximum_cost
Support: L1,L2
Default: 1022 Value: 1-1022
Maximum cost of a path to a reachable node within the Phase IV
area. This characteristic is only used by the Phase IV routing
algorithm (that is, the routing-vector algorithm).
26 – phaseiv_maximum_hops
Support: L1,L2
Default: 30 Value: 1-30
Maximum number of hops in a path to a reachable node within the
Phase IV area. This characteristic is only used by the Phase IV
routing algorithm (that is, the routing-vector algorithm).
27 – phaseiv_maximum_visits
Support: All
Default: 63 Value: 1-63
Maximum number of visits that a packet can make to this node
before Routing assumes that the packet is looping. This
characteristic is only used by the Phase IV routing algorithm
(that is, the routing-vector algorithm).
28 – phaseiv_prefix
Support: All
Default: Hex 49 Value: Address prefix
Prefix for Phase IV addresses. If the characteristic phase iv
address is not 0.0, a DECnet area address is formed by adding
the area portion of the Phase IV address to this prefix.
You can modify this characteristic only when the entity is
disabled.
set [node node-id] routing phaseiv prefix address-prefix
Example:
set routing phaseiv prefix = 49::
29 – probe_rate
Support: End
Default: 20 Value for Tru64 UNIX: 10-1000
Default: 20 Value for OpenVMS: 1-65535
Number of packets after which a probe is sent. This
characteristic is used only on multilink end systems, on
circuits without cache entries for the destination.
30 – protocols
Support: IP Value: IP or ISO8473
The protocol stacks that are enabled on this system. These
can be either or both of the above values. The value of this
characteristic derives from an argument to the create command.
You cannot modify this characteristic.
31 – redirect_holding_time
Support: L1,L2
Default: 600 Value: 1-65535
Holding time, in seconds, to be specified in Redirect PDUs
generated by this node.
32 – rip_receive_metric_class
Support: L2,IP
Default: External Value: External or Internal
The class to be associated with routes received through RIP.
This value may be overridden by a routing receive route entity.
This characteristic is supported only if the routing protocols
supported characteristic includes the RIP routing protocol.
33 – rip_send_local_metric
Support: L2,IP
Default: 1 Value: 0-16
The metric value used by RIP when announcing routes derived from
local information. This value is used unless it is overridden by
a routing send route entity. This characteristic is supported
only if the routing protocols supported characteristic includes
the RIP routing protocol.
34 – rip_send_metric_classes
Support: L2,IP
Default: Internal Value: Set of external, internal
Routes received through routing protocols other than RIP with metric
classes in this set are candidates for announcement in RIP messages
subject to the route propagation policy in force. Routes with metric
classes not in this set will not be announced. Each value in this
set may be overridden separately by a more specific propagation
policy specified by a routing send route or routing send route route
source entity. This characteristic is supported only if the routing
protocols supported characteristic includes the RIP routing protocol.
35 – rip_send_replacement_metric
Support: L2,IP
Default: 1 Value: 0-16
The metric value used by RIP when announcing routes derived through
other routing protocols. This value is used unless it is overridden
by a routing send route entity. This characteristic is supported
only if the routing protocols supported characteristic includes the
RIP routing protocol.
36 – route_propagation
Support: L2,IP
Default: No Route Propagation Value: Set of protocol pairs
The default route propagation to be performed. The set may include
the following protocol pairs:
EGP to IS-IS IS-IS to RIP
EGP to RIP RIP to EGP
IS-IS to EGP
If a particular value is not present in the set, routes are not
propagated between those two protocols in that direction. This
characteristic is supported only if the routing protocols
supported characteristic includes either of the EGP or RIP
routing protocols.
37 – routing_mode
Support: End
Default: Integrated (OpenVMS) Value: Segregated or
Segregated (Tru64 UNIX) Integrated
Determines the behavior of the forwarding algorithm. When the
routing mode is set to Segregated, data being transmitted to
Phase IV destination addresses is sent in Phase IV format packets,
to the adjacent Phase IV router, if available. In Integrated mode,
data is sent to Phase V (OSI) router adjacencies in CLNP packets,
if possible.
This characteristic can only be set when Routing is disabled.
For example, to switch to segregated mode from the default:
NCL> disable routing
NCL> set routing routing mode = segregated
NCL> enable routing
NCL> enable routing circuit *
38 – routing_protocols_supported
Support: L2,IP
The set of routing protocols supported by this implementation. You
cannot modify this characteristic.
EGP
IS-IS
RIP
39 – segment_buffer_size
Support: All
Default: 570 Value: 0-65535
Maximum segment size, in octets, to be used by the Transport
layer. A value of zero means that the segment size is unlimited.
40 – send_source_quench
Support: L1,L2,IP
Default: False Value: True or false
Specifies whether an ICMP source quench packet is sent when an IP
packet is discarded because of congestion. If false, ICMP source
quench packets are never sent.
41 – source_quench_interval
Support: L1,L2,IP
Default: 100 Value: 1-65535
Minimum time, in milliseconds, between transmission of successive
ICMP source quench packets.
42 – summary_addresses
Support: L2,IP
Default: No addresses Value: Set of summary addresses
Summary address information to be included in level 2 link state
packets sent by this node.
43 – time_to_live
Support: IP
Default: 35 Value: 1-255
Specifies the value to be placed in the time to live field of
originating IP packets. This value should be greater than the
maximum number of hops in any path on the network.
44 – circuit
set [node node-id] routing circuit circuit-name ...
Modifies attributes of the routing entity which represents
a data link to another node. Support for the various attributes
depends upon the routing type of the node (End, L1, L2, IP).
The modifiable routing circuit attributes and their data types
[in brackets] are:
data link entity [local-entity-name]
dna neighbor [boolean]
enable phaseiv address [boolean]
explicit receive verification [boolean]
hello timer [integer]
idle timer [integer]
inactive area address [set]
initial minimum timer [integer]
isis hello timer [integer]
L1 cost [integer]
L1 router priority [integer]
L2 cost [integer]
L2 router priority [integer]
manual data link sdu size [integer]
manual L2only mode [boolean]
manual routers [set]
maximum call attempts [integer]
maximum svc adjacencies [integer]
originating queue limit [integer]
recall timer [integer]
receive verifier [hex-string]
reserved adjacency [boolean]
reserve timer [integer]
template [template-id]
transmit verifier [hex-string]
x.25 filters [set]
Select reachable_address to view the modifiable attributes of a
routing circuit reachable address subentity.
Selecte ip_reachable_address to view the modifiable attributes
of a routing circuit ip reachable address subentity.
44.1 – data_link_entity
Support: All
Default: No data link Value: Local-entity-name
Name of the entity within the data link module to be created when
a port is opened for that data link type. You can modify this
characteristic only when the entity is disabled. This attribute
is supported for all types of circuits, however for X.25 circuits
set the attribute to x25 access.
set [node node-id] routing circuit circuit-name -
data link entity [local entity name]
Examples:
set routing circuit csmacd-1 -
data link entity csma-cd station csmacd-1
set routing circuit x25_circuit-1 data link entity x25 access
44.2 – dna_neighbor
Support: L1,L2
Default: True Value: True or false
If true, specifies that the neighbor is expected to be DNA
compliant, and so proprietary mechanisms are possible. If
false, no router-to-router Hellos or LSPs will be sent over
this circuit. This characteristic is supported only if the
characteristic type is not x25 da. You can modify this
characteristic only when the entity is disabled.
44.3 – enable_phaseiv_address
Support: All
Default: True Value: True or false
Specifies whether the physical LAN address is to be set to the
Phase IV style LAN address (that is, AA-00-04-00-xx-xx). The
LAN address is set only if this attribute is true and the value
of the Phase IV Address characteristic is not 0.0. If Phase IV
Address is not 0.0 and there are multiple adaptors to the same
LAN, only one circuit may have this attribute set to true. This
characteristic is supported only if the characteristic type is
set to csma-cd.
set [node node-id] routing circuit circuit-name -
enable phaseiv address boolean
Example:
set routing circuit csmacd-1 enable phaseiv address true
44.4 – explicit_receive_verification
Support: All
Default: True Value: True or false
Type of password verification performed at circuit
initialization. If true, the received verifier is checked
against the value of the characteristic receive verifier for
this circuit, if any. If false, the received verifier is checked
against the set of verifiers specified in the routing permitted
neighbor entities. This attribute is supported only if the
characteristic type is set to ddcmp, hdlc, x25 static incoming,
x25 static outgoing, and x25 permanent.
44.5 – hello_timer
Support: L1,L2
Default: 10 Value: 1-32767
Interval, in seconds, between IS Hello messages.
44.6 – idle_timer
Support: All
Default: 30 Value: 1-65535
Number of seconds of idle time before a call is cleared. This
attribute is supported only if the characteristic type is x25 da.
44.7 – inactive_area_address
Support: All
Default: No area Value: Set of area addresses
address
Area address associated with the use of the inactive subnet of
ISO 8473. Maximum area address that may be present is 1. This
characterisitic is supported only if the characteristic type is
set to csma-cd.
set [node node-id] routing circuit circuit-name -
inactive area address {one_area_address}
Example:
set routing circuit csmacd-1 inactive area address {49::FF-00}
44.8 – initial_minimum_timer
Support: All
Default: 55 Value: 1-65535
Period, in seconds, for which an X.25 call remains connected
after being established, irrespective of traffic. This should be
set small enough that the call is cleared before the start of the
next charging interval. This attribute is supported only if the
characteristic type is x25 da.
44.9 – isis_hello_timer
Support: L1,L2
Default: 3 Value: 1-32767
Interval, in seconds, between LAN level 1 and level 2 router-to-
router Hello messages. This value is also used as the interval
between IS Hello messages when polling the ES configuration.
44.10 – L1 cost
Support: L1,L2
Default: 20 Value: 1-63
Cost of this circuit for level 1 traffic.
44.11 – L1 router priority
Support: L1,L2
Default: 64 Value: 1-127
Priority for becoming LAN level 1 designated router. This
attribute is supported only if the circuit's characteristic type
is csma-cd.
44.12 – L2 cost
Support: L2
Default: 20 Value: 1-63
Cost of this circuit for level 2 traffic.
44.13 – L2 router priority
Support: L2
Default: 64 Value: 1-127
Priority for becoming LAN level 2 designated router. This
attribute is supported only if the circuit's characteristic type
is csma-cd.
44.14 – manual_data_link_sdu_size
Support: All
Default: 1492 Value: 128-65535
Preferred maximum data-link block size, in octets. You can modify
this characteristic only when the entity is disabled. If the
characteristic type is csma-cd, this characteristic is a read-
only attribute whose value is fixed at 1492.
set [node node-id] routing circuit circuit-name -
manual data link sdu size
Example:
set routing circuit fddi-1 manual data link sdu size 4352
44.15 – manual L2only mode
Support: L2
Default: False Value: True or false
If true, specifies that this circuit is to be used only for level
2 traffic. If false, the circuit may be used for both level 1 and
level 2 traffic. You can modify this characteristic only when the
entity is disabled.
44.16 – manual_routers
Support: End
Default: No router Value: Set of LAN addresses
IDs
Manually entered IDs of routers. If this set is empty, the
circuit will auto-configure the routers. This characteristic is
supported only if the circuit's characteristic type is csma-cd.
For Tru64 UNIX, a maximum of 5 routers can be in the set.
set [node node-id] routing circuit circuit-name -
manual routers {address[,address...]}
Example:
set routing circuit csmacd-1 manual routers {aa-00-04-00-12-34}
44.17 – maximum_call_attempts
Support: All
Default: 10 Value: 0-255
Maximum number of successive X.25 call failures before the
circuit is regarded as being halted. A value of zero means that
there is no limit to the number of retries.
This attribute is supported only if the characteristic type is
set to x25 static outgoing. You can modify this characteristic
only when the entity is disabled. Also, you can only increase the
characteristic value.
44.18 – maximum_svc_adjacencies
Support: All
Default: 1 Value: 1-65535
Number of routing circuit adjacency entities to reserve for
SVCs on this circuit. This is effectively the maximum number
of simultaneous calls possible on this circuit. This attribute is
supported only if the characteristic type is x25 da.
44.19 – originating_queue_limit
Support: L1,L2
Default: 2 Value: 1-50
Maximum number of data PDUs originated by this node that can
be on this circuit's transmit queue. This should be set to the
minimum number required to keep the data link from idling. You
can modify this characteristic to a higher value when the entity
is disabled; you can never modify it to a lower value.
44.20 – recall_timer
Support: All
Default: 60 Value: 0-65535
Interval, in seconds, that must elapse between a call failure and
a recall. This attribute is supported only if the characteristic
type is set to x25 static outgoing, x25 da, hdlc, or ddcmp.
44.21 – receive_verifier
Support: All
Default: No verifier Value: Hex string, length 0-38
Value against which a neighbor node's received verifier is
to be checked. If no verifier is specified, no verification
is performed. This attribute is supported only if the
characteristic type is either ddcmp, hdlc, x25 static incoming,
x25 static outgoing, or x25 permanent. You cannot display this
characteristic.
44.22 – reserved_adjacency
Support: End
Default: False Value: True or false
If true, specifies that one SVC must be reserved for connection
to a router. If false, no SVC needs to be reserved for
this purpose. This characteristic is supported only if the
circuit's characteristic type is x25 da). You can modify this
characteristic only when the entity is disabled.
44.23 – reserve_timer
Support: All
Default: 600 Value: 1-65535
Interval, in seconds, during which the SVC remains reserved for
the previous DTE address after a call is cleared due to lack of
traffic. This attribute is supported only if the characteristic
type is x25 da.
44.24 – template
Support: All
Default: No template Value: Template-id
name
Name of the template to be used when a port is opened for this
data-link type. If no template name is specified, no template is
used. You can modify this characteristic only when the entity is
disabled.
44.25 – transmit_verifier
Support: All
Default: No verifier Value: Hex-string, length 0-38
Value to be transmitted for verifying the identity of this node.
If no verifier is specified, no verifier is transmitted. This
characteristic is supported only if the characteristic type is
either ddcmp, hdlc, x25 static outgoing, x25 static incoming, or
x25 permanent. You cannot display this characteristic.
44.26 – x.25_filters
Default: See Value: Set of simple names
description
Specifies the set of X.25 filters to be used when a port is
opened to the X.25 module. Typically, there will be two sets: one
to specify the selection on the Call User Data field for DECnet-Plus
and the other to specify the selection on the subaddress
for Phase IV. This attribute is valid only if the characteristic
type is x25 static incoming or x25 da.
44.27 – ip_reachable_address
Support: L2,IP
set [node node-id] routing circuit circuit-name
ip reachable address destination
44.28 – reachable_address
set [node node-id] routing circuit circuit-name -
reachable address simple-name ...
Modifies attributes of a routing circuit reachable address entity
which contains information about a manually entered address prefix
accessible over that circuit. It exists only on L2 routers and
end nodes. The modifiable routing circuit reachable address
attributes and their data types [in brackets] are:
block size [integer]
cost [integer]
data format [PhaseIV or Phasev]
DTE addresses [set of dte addresses]
ISDN address [isdn-address]
LAN address [id]
metric type [metric-type]
mapping [string]
modem addresses [modem-address]
modem address prefix [modem-address-prefix]
modem address suffix [modem-address-suffix]
permitted lan address [lan-address]
type [string]
44.28.1 – block_size
Support: End, type outbound
Default: 0 Value: 0-65536
The data link block size to be used for this prefix.
For an end system, the data link block size to be used for this
prefix. If the block size is set to the default, the manual
block size of the circuit will be used instead. This attribute
is supported only if the type characteristic is set to outbound.
set [node node-id] routing circuit circuit-name -
reachable address simplename block size integer
Example:
set routing circuit csmacd-1 -
reachable address to-area4 block size 500
44.28.2 – cost
Support: L2
Default: 20 Value: 1-63
Cost of reaching this address prefix over this circuit.
44.28.3 – data_format
Support: L2
Default: PhaseV Value: PhaseIV (1) or PhaseV (0)
The PDU data format to be used when forwarding data (or
error report) NPDUs using this reachable address.
This attribute is supported only if the type characteristic
is set to outbound. You can modify this characteristic only
when the entity is disabled.
44.28.4 – dte_addresses
Support: End,L2
Default: No DTE addresses={ } Value: Set of DTE addresses
A set of DTE addresses to which a call may be directed in order
to reach an address that matches the address prefix of this
reachable address.
This characteristic is supported if the node is a level 2 router,
where the owning circuit's characteristic type is one of the X.25
circuit types, and the reachable address's characteristic type
is outbound. It is also supported by end nodes operating over an
x25 da circuit. You can modify this characteristic only when the
entity is disabled.
set [node node-id] routing circuit circuit-name reachable -
address simplename dte address {dte-address[dte-address...]}
Example:
set routing circuit x25_circuit-1 reachable address ughh_v -
dte address { 2267643 }
44.28.5 – ISDN address
Support: L1,L2
Default: { } Value: Set of ISDN addresses
A full set of E.164 ISDN network addresses that a call may be
directed in order to reach a network number that matches the
address prefix of the parent reachable address entity. Associated
with each ISDN network address, but not visible to Network
Management, is a variable last failure of type binary absolute
time. This attribute is supported only if access type is ISDN DA.
44.28.6 – LAN address
Support: L2,End
Default: 00-00-00-00-00-00 Value: ID
A single LAN address to which an NPDU can be directed in order
to reach an address that matches the address prefix of the parent
reachable address entity. This attribute is supported only if the
type characteristic is set to outbound on broadcast circuits only.
A valid address is required here.
You can modify this characteristic only when the entity is
disabled.
set [node node-id] routing circuit circuit-name reachable -
address simplename lan address aa-00-04-00-xx-xx
Example:
set routing circuit csmacd-1 reachable address to-area4 -
lan address aa-00-04-00-12-34
44.28.7 – mapping
Support: End,L2
Default: X.121 Value: Manual or X.121
Type of mapping used to determine the SNPA address to which a
call should be placed for this address prefix. You can modify
this characteristic only when the entity is disabled. If the
circuit is a broadcast circuit, this attribute must have the
value manual.
manual The mapping uses the set of addresses in the
characteristic dte addresses or the address in the
characteristic LAN address.
X.121 The mapping uses the X.121 address extraction algorithm.
This characteristic is supported only if either of the following
conditions is satisfied:
o The node is a level 2 router or an end node, and the owning
circuit's characteristic type is one of the X.25 circuit
types; or
o The node is a level 2 router, the owning circuit's
characteristic type is csma-cd, and the reachable address's
characteristic type is outbound.
set [node node-id] routing circuit circuit-name reachable -
address simplename mapping manual_or_x.121
Example:
set routing circuit csmacd-1 reachable address to-area4 -
mapping manual
44.28.8 – metric_type
Support: L2
Default: Internal Value: Internal, external
The metric type of the cost metric for the circuits. If internal,
the I/E bit for the metric in the Prefix Neighbors option of
L2 LSPs is set to 0, otherwise (external) is set to 1.
44.28.9 – modem_addresses
Support: L1,L2
Default: { } Value: Set of modem addresses
A set of full dial sequence that contains the address (PSTN or
ISDN) to which a call may be directed in order to reach a
network number that matches the address prefix of the parent
reachable address) entity. Associated with each modem address,
but not visible to Network Management, is a variable last
failure of type binary absolute time. This is valid only if
mapping is manual and the parent circuit entity's access time
is Modem DA.
44.28.10 – modem_address_prefix
Support: L1,L2
Default: L1,L2 Value: Address string
The address that is to be inserted to the beginning of the address
extracted from the NSAP address. This is valid only if mapping is
not manual and the parent circuit entity's access type is Modem
DA. It is used in conjunction with modem access suffix to form the
complete dial sequence.
44.28.11 – modem_address_suffix
Support: L1,L2
Default: L1,L2 Value: Address string
The address that is to be inserted to the end of the address
extracted from the NSAP address. This is valid only if mapping
is not manual and the parent circuit entity's access type is
Modem DA. It is used in conjunction with modem access prefix
to form the complete dial sequencence.
44.28.12 – permitted LAN address
Support: End
Default: { } Value: Set of LAN addresses
The set of LAN addresses corresponding to routers that are
permitted to be used for forwarding to this prefix. This
attribute is supported only if the type characteristic is
set to filter on broadcast circuits only. The default is
an empty set, and at least one LAN address is required.
set [node node-id] routing circuit circuit-name -
reachable address simplename -
permitted lan address {lan-address[,lan-address...]}
Example:
set routing circuit csmacd-1 reachable address to-area4 -
type filter, -
permitted lan address {aa-00-04-00-23-45,aa-00-04-00-BC-DE}
44.28.13 – type
Support: L2,End
Default: Outbound Value: Inbound, outbound, or filter
Type of the reachable address. You can modify this characteristic
only when the entity is disabled.
inbound For L2 only, the address prefix corresponds to a
Phase IV area that is reachable through this node
and circuit by inbound traffic.
outbound The address prefix is in an external domain
that is reachable over this circuit by outbound
traffic.
filter The address prefix defines a set of addresses that
should be reached via the set of routers listed in
the permitted LAN address characteristic.
set [node node-id] routing circuit circuit-name -
reachable address simplename -
type reachable-addr-type
Example:
set routing circuit csmacd-1 -
reachable address to-area4 type filter
45 – egp_group
set [node node-id] routing egp group group-name ...
Modifies the attributes of a routing egp group entity, which
defines a set of systems in the same autonomous system with which
this system may exchange EGP messages. The modifiable attributes
and their data types [in brackets] are:
autonomous system number [integer]
external routes [set of send,receive]
maximum active neighbors [integer]
receive metric class [internal or external]
send local metric [integer]
send metric classes [set of external,internal]
send replacement metric [integer]
45.1 – autonomous_system_number
Support: L2,IP
Default: 0 Value: 0-65535
The autonomous system number common to members of this group. You
can modify this characteristic only when the entity is disabled.
This attribute is supported only if the node is a level 2 router,
and if the system supports dual routing (both DECnet and IP
routing).
45.2 – external_routes
Support: L2,IP
Default: Receive Value: Set of send,receive
If the set includes receive, external gateway routes are accepted
from neighbors in the group; if the set does not include receive,
external gateway routes are discarded. If the set includes send,
external gateway routes will be sent to neighbors in this group;
if the set does not include send, external gateway routes are not
sent. You can modify this characteristic only when the entity is
disabled.
45.3 – maximum_active_neighbors
Support: L2,IP
Default: 1 Value: 0-255
The maximum number of neighbor systems in the group that this
system will attempt to acquire and maintain in the Up state at
any given time. You can modify this characteristic only when the
entity is disabled.
45.4 – receive_metric_class
Support: L2,IP
Default: External Value: Internal or external
The class to be associated with routes received from EGP
neighbors in this group (unless overridden by a routing receive
route entity). You can modify this characteristic only when the
entity is disabled.
45.5 – send_local_metric
Support: L2,IP
Default: 1 Value: 0-255
The metric value to be used when announcing routes derived from
local information (unless overridden by a routing send route
entity). You can modify this characteristic only when the entity
is disabled.
45.6 – send_metric_classes
Support: L2,IP
Default: Internal Value: Set of external,internal
Routes received through routing protocols other than EGP with
metric classes in this set are candidates for announcement
in EGP messages sent to neighbors in this group, subject to
route propagation policy. Routes with metric classes not
specified in this set will not be announced. You can modify this
characteristic only when the entity is disabled.
45.7 – send_replacement_metric
Support: L2,IP
Default: 1 Value: 0-255
Specifies the metric value to be used when announcing routes
derived from non-EGP routing protocols (unless overridden by a
routing send route entity). You can modify this characteristic
only when the entity is disabled.
46 – permitted_neighbor
set [node node-id] routing permitted neighbor neighbor-name -
verifier hex-string
46.1 – verifier
Support: All
Default: No verifier Value: hex-string, length 0-38
Verifier to be checked from this neighbor. You may change this
characteristic at any time; however, the change will not take
effect until the circuit is next initialized. You cannot
display this characteristic.
If the verifier is not set, then a connection to the neighboring
node whose ID matches the ID in this entry is allowed. If the
verifier is set, the connection is allowed only if the verifier
sent by the remote node matches the one in this entry.
Examples:
create routing permitted neighbor nashua_decnet-osi -
id 08-00-2b-12-34-56
set routing permitted neighbor nashua_decnet-osi -
verifier %x1234
create routing permitted neighbor nashua_phase_iv -
id aa-00-04-00-12-34
set routing permitted neighbor nashua_phase_iv -
verifier %x1234