Creates the routing entity. For information about the Routing
entity and its subentities, refer to HELP ENTITY ROUTING.
create [node node-id] routing type routing-type
The Type argument is required. It determines the value
of the type characteristic attribute. These are the possible
routing-type values:
endnode The node is an end system.
L1router The node is a level 1 router.
L2router The node is a level 2 router.
Example:
create routing type endnode
Select circuit for information on creating routing circuit,
routing circuit adjacency, and routing circuit reachable
address subentities.
Select egp_group for information on creating routing egp
group and routing egp group egp neighbor subentities.
Select permitted_neighbor for information on creating
routing permitted neighbor subentities.
1 – Exception Messages
o already exists
A routing entity already exists.
o invalid router type
The type argument specifies an invalid router type on the create
command.
2 – circuit
Creates an instance of a routing circuit entity which represents
a data link to another node, specified by the simple name
circuit-name.
create [node node-id] routing circuit circuit-name -
type circuit-type
The Type argument is required. Possible circuit-type values are:
csma-cd - a broadcast circuit
ddcmp - a DDCMP circuit
fddi - an FDDI large packet circuit
hdlc - an HDLC circuit
x25 da - a dynamically allocated X.25 circuit
x25 permanent - an X.25 permanent virtual circuit
x25 static incoming - a static incoming X.25 circuit
x25 static outgoing - a static outgoing X.25 circuit
On OpenVMS for FDDI routing circuits, the type should only be
fddi if large packet support is in use, otherwise the type should
be csma-cd.
Examples:
create routing circuit fddi-1 type csma-cd
create routing circuit fddi-1 type fddi ! for large packet support
Select adjacency for information on creating routing circuit
adjacency subentities.
Select reachable_address for information on creating routing
circuit reachable address subentities.
2.1 – Exception Messages
o invalid circuit type
The specified circuit type is invalid.
Argument:
reason Reason why the circuit type is invalid.
1 A dynamically allocated X.25 circuit type is not
permitted for a level 1 router.
o maximum circuits exceeded
An attempt has been made to create more than the maximum number
of circuits allowed.
2.2 – adjacency
Creates an instance of a routing circuit adjacency. An
adjacency describes a neighboring node that is accessible
through a particular circuit.
This create command is allowed only if the circuit is a
csma-cd circuit and the type is L1router or L2router.
create [node node-id] routing circuit circuit-name -
adjacency adjacency-name, -
endnode ids {id[,id...]}, -
LAN address LAN-address [,data format string]
The required Endnode IDs argument is a set of source system
IDs. The required LAN Address argument is the Data Link
address from which the adjacency receives end system hellos.
The optional Data Format argument is the format of the reachable
address.
2.3 – reachable_address
Creates a routing circuit reachable address entity instance
which contains information about a manually entered address
prefix accessible over that circuit. It exists only on L2
routers and end nodes.
create [node node-id] routing circuit circuit-name -
reachable address simple-name -
address prefix address-prefix
On an end system, the type may be "outbound" or (for a
broadcast circuit only) "filter". A reachable address of
type outbound behaves in a way similar to that on an L2
router except that the routing information is used to
control the operation of the ES cache. A reachable address
of type filter (for the broadcast circuit only) specifies
the permitted LAN addresses of routers on the LAN that will
be used by the reverse path cache algorithm. To switch
between outbound and filter types, the reachable address
must first be disabled. For either outbound or filter type,
the mapping attribute should be set to manual because the
default is X.121.
The address prefix argument is required. It specifies the
address prefix to which this reachable address corresponds.
Example:
create routing circuit csmacd-1 reachable address to-bulean -
address prefix 49::4
2.3.1 – Exception Messages
o address prefix not unique
A reachable address already exists with the specified address
prefix.
o invalid address prefix
Specified address prefix has more than two digits, and does not
correspond to a valid AFI.
o non DA circuit
A reachable address on an endnode can only be created on a DA
circuit.
3 – egp_group
Creates a routing egp group defining a set of systems in the same
autonomous system with which this sytem may exchange EGP messages.
create [node node-id] routing egp group group-name
This entity is supported only on Level 2 routers that support dual
routing (and, in particular, the EGP routing protocol).
3.1 – egp_neighbor
Creates a routing egp group egp neighbor entity which defines one of
the systems in the same autonomous group defined by the owning egp
group entity.
create [node node-id] routing egp group group-name egp neighbor -
neighbor-name ip address ip-address
This entity is supported only on Level 2 routers that
support dual routing (and, in particular, the EGP routing protocol).
3.1.1 – Exception Messages
o duplicate ip address
An EGP neighbor with this IP address already exists in this EGP
group.
4 – permitted_neighbor
Creates a routing permitted neighbor entity instance which
represents a neighboring node on a nonbroadcast circuit that
is permitted to connect to this node. Neighbor-name is a
simple name. ID is the node ID of a potential neighbor node.
create [node node-id] routing -
permitted neighbor neighbor-name -
id node-id
Examples:
create routing permitted neighbor nashua_decnet-osi -
id 08-00-2b-12-34-56
create routing permitted neighbor nashua_phase_iv -
id aa-00-04-00-12-34
4.1 – Exception Messages
o duplicate node id
A routing permitted neighbor entity with the specified node ID
already exists.
Argument:
name The name of the permitted neighbor that already has
this node ID.
o permitted neighbor already exists
A routing permitted neighbor entity with the specified name
already exists.