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.
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
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.
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
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.
5 – hello_timer
Support: L1,L2
Default: 10 Value: 1-32767
Interval, in seconds, between IS Hello messages.
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.
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}
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.
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.
10 – L1 cost
Support: L1,L2
Default: 20 Value: 1-63
Cost of this circuit for level 1 traffic.
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.
12 – L2 cost
Support: L2
Default: 20 Value: 1-63
Cost of this circuit for level 2 traffic.
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.
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
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.
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}
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
27 – ip_reachable_address
Support: L2,IP
set [node node-id] routing circuit circuit-name
ip reachable address destination
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]
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
28.2 – cost
Support: L2
Default: 20 Value: 1-63
Cost of reaching this address prefix over this circuit.
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.
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 }
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.
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
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
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.
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.
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.
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.
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}
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