show [node node-id] routing attribute [,attribute...] all [attributes] all characteristics all counters all status Examples: show routing type, phaseiv address show routing all
1 – Characteristics
o 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. o 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. o 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. o 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. o 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. o 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. o 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. o 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. o 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). o ip reassembly time Support: IP Default: 10 Value: 1-255 Maximum time, in seconds, for which IP fragments are held while awaiting reassembly. o 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. o 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. o 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 o 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 o 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. o 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. o 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. o minimum lsp transmission interval Support: L1,L2 Specifies the minimum interval (in seconds) between transmissions of an LSP from a particular source. When changed the timer must be reset. o 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. o 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). o 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). o 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). o 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. o 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). o 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). o 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). o 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). o 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). o 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-Plus 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. o 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. o 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. o 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. o 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. o 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. o 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. o 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. o routing mode Support: End Default: Integrated propogation Value: Segregated or 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 * o route propagation Support: L2,IP Default: No route Value: Set of protocol pairs (see below) propagation 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. o routing mode Support: End Default: Integrated Value: Segregated or 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 * o routing protocols supported Support: L2,IP The set of routing protocols supported by this implementation. You cannot modify this characteristic. EGP IS-IS RIP o 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. o 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. o source quench interval Support: L1,L2,IP Default: 100 Value: 1-65535 Minimum time, in milliseconds, between transmission of successive ICMP source quench packets. o 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. o 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. o type Support: All Default: No default Value: See description Routing type of this node. You cannot modify this characteristic. endnode The node is an end node. L1router The node is a level 1 router. L2router The node is a level 2 router. o version Default: Current version number Version number of the DNA Network Routing layer architecture specification to which this implementation conforms. You cannot modify this characteristic.
2 – Counters
o address unreachable pdus discarded Support: All Number of data PDUs that have been discarded because the destination was unreachable. o aged ip packets discarded Support: IP Number of IP packets that have been discarded because their time of life has expired. o aged pdus discarded Support: L1,L2 Number of data PDUs that have been discarded because their lifetime has expired. o attempts to exceed maximum sequence number Support: L1,L2 Number of times an attempt was made to increase the sequence number of a link state packet beyond the maximum allowed. o corrupted lsps detected Support: L1,L2 Number of times that the corrupted lsp detected event has been generated. o creation time Support: All Time this entity was created. o error reports generated Support: All Number of error report PDUs (or Phase IV data packets with RTS set) that have been generated. o icmp address mask reply messages received Support: IP Number of ICMP Address Mask Reply messages received. o icmp address mask reply messages sent Support: IP Number of ICMP Address Mask Reply messages sent. o icmp address mask request messages received Support: IP Number of ICMP Address Mask Request messages received. o icmp address mask request messages sent Support: IP Number of ICMP Address Mask Request messages sent. o icmp destination unreachable messages received Support: IP Number of ICMP Destination Unreachable messages received. o icmp destination unreachable messages sent Support: IP Number of ICMP Destination Unreachable messages sent. o icmp echo reply messages received Support: IP Number of ICMP Echo Reply messages received. o icmp echo reply messages sent Support: IP Number of ICMP Echo Reply messages sent. o icmp echo request messages received Support: IP Number of ICMP Echo Request messages received. o icmp echo request messages sent Support: IP Number of ICMP Echo Request messages sent. o icmp message send errors Support: IP Number of ICMP messages that could not be sent because of problems in the ICMP layer. Note that this value does not include errors that occur outside the ICMP layer, such as forwarding errors. o icmp messages received Support: IP Number of ICMP messages received. This value includes those messages counted by the icmp received message errors counter. o icmp messages sent Support: IP Number of ICMP messages of all types that the node has attempted to send. Note that this figure includes the value of the icmp message send errors counter. o icmp received message errors Support: IP Number of ICMP messages received with any type of error. o icmp parameter problem messages received Support: IP Number of ICMP Parameter Problem messages received. o icmp parameter problem messages sent Support: IP Number of ICMP Parameter Problem messages sent. o icmp redirect messages received Support: IP Number of ICMP Redirect messages received. o icmp redirect messages sent Support: IP Number of ICMP Redirect messages sent. o icmp source quench messages received Support: IP Number of ICMP Source Quench messages received. o icmp source quench messages sent Support: IP Number of ICMP Source Quench messages sent. o icmp time exceeded messages received Support: IP Number of ICMP Time Exceeded messages received. o icmp time exceeded messages sent Support: IP Number of ICMP Time Exceeded messages sent. o icmp timestamp reply messages received Support: IP Number of ICMP Timestamp Reply messages received. o icmp timestamp reply messages sent Support: IP Number of ICMP Timestamp Reply messages sent. o icmp timestamp request messages received Support: IP Number of ICMP Timestamp Request messages received. o icmp timestamp request messages sent Support: IP Number of ICMP Timestamp Request messages sent. o icmp unknown message types received Support: IP Number of ICMP messages received with an unknown message type. o ip address unreachable packets discarded Support: IP Number of IP packets discarded because their destination was unreachable. o ip destination address error packets discarded Support: IP Number of IP packets discarded because of an invalid destination address or the address of an unsupported class. o ip packets discarded Support: IP Number of IP packets discarded for either of the following reasons: o Error in the IP header, such as bad checksum or version number mismatch. Note, however, that format errors and time to live expired are excluded. o Packet received through data link broadcast when forwarding is not allowed. o ip packet format errors Support: IP Number of IP packets discarded because of a format error in the IP header. o ip protocol unreachable packets discarded Support: IP Number of IP packets received for the local system and discarded because there was no port with the protocol type specified in the IP datagram PROTO field. o ip source address error packets discarded Support: IP Number of IP packets discarded because of an invalid source address or the address of an unsupported class. o lsp L1 database overloads Support: L1,L2 Number of times that the lsp level 1 database overload event has been generated. o lsp L2 database overloads Support: L2 Number of times that the lsp level 2 database overload event has been generated. o manual addresses dropped from area Support: L1,L2 Number of times an address in the manual area addresses set is ignored when computing an area address (each address that is ignored is counted separately). o own lsp purges Support: L1,L2 Number of times that the own lsp purged event has been generated. o pdu format errors Support: All Number of data PDUs that have been discarded because of format errors. o phaseiv translation failures Support: All Number of times the phase iv translation failures event has been generated. o sequence number skips Support: L1,L2 Number of times that the sequence number skipped event has been generated. o unsupported options Support: All Number of data PDUs that have been discarded because they specified unsupported options in their header.
3 – Preset attributes
Preset attributes are similar to characteristics, in that their values control the way in which the routing module operates. However, unlike characteristics, you cannot alter preset attribute values using the set command. NOTE These characteristics are preset attributes. They should only be set by an expert. o broadcast lsp transmission interval Support: L1,L2 Default: 33 Value: 1-65535 Interval, in milliseconds, between the transmission of Link State Packets (LSPs) on a broadcast circuit. o complete snp interval Support: L1,L2 Default: 10 Value: 1-600 Interval, in seconds, between generation of Complete Sequence Number Packets (SNPs) by a designated router on a broadcast circuit. o default es hello timer Support: All Default: 600 Value: 1-65535 Value to be used for the current suggested Hello timer, in the absence of any suggested value from the intermediate system (IS). On routers, this is the value to be suggested when the router is not required to poll the ES configuration. In routers, this value is suggested by the Suggested ES Configuration Timer option in IS Hellos. o dr isis hello timer Support: L1,L2 Default: 1 Value: 1-65535 Interval, in seconds, between the generation of IS-IS Hello PDUs by the designated router. o es cache holding time Support: End Default: 600 Value: 1-65535 Holding time, in seconds, for an entry in the node's end-node cache database. o es cache width Support: End Default: 3 Value for Tru64 UNIX: 1-4294967295 Default: 3 Value for OpenVMS: 1-65535 Maximum number of LAN address entries in the node's end-node cache database on a broadcast circuit. o holding multiplier Support: All Default: 3 Value: 2-63 Value by which to multiply the Hello timer to obtain the holding timer value for ES and IS Hellos and for point-to-point, router- to-router Hellos. o inactive selector Support: All Default: 33 Value: 2-255 This is the selector value identifying the port to which incoming Inactive Subset PDUs are to be sent. o initialization timer Support: All Default: 6 Value: 1-63 Delay, in seconds, between initialization of a data link and sending a DECnet-Plus message on a DDCMP circuit. o isis format Support: L1,L2 Default: 0 (ISO) Value: (ISO) or 1 (DNA Private) This attribute controls the protocol identification to be used for "DNA Private" PDUs. On broadcast circuits, this characteristic also controls the SAP on which they are transmitted. o isis holding multiplier Support: L1,L2 Default: 10 Value: 2-63 Value by which to multiply the ISIS Hello timer to obtain the value of the holding timer for LAN level 1 and level 2 router-to- router Hellos. o maximum age Support: L1,L2 Default: 1200 Value: 1-65535 Number of seconds before an LSP is considered to be expired. o maximum lsp generation interval Support: L1,L2 Default: 900 Value: 60-900 Maximum interval, in seconds, between link state packets (LSPs) generated by this node. o minimum lsp generation interval Support: L1,L2 Default: 30 Value: 1-65535 Minimum time, in seconds, between generation of LSPs by this node. o minimum lsp transmission interval Support: L1,L2 Default: 5 Value: 5-30 Minimum interval, in seconds, between retransmissions of an LSP. o multicircuit es hello timer Support: End Default: 10 Value: 1-65535 Value to be used for the current suggested Hello timer on a multicircuit end node with more than one circuit enabled, in the absence of any suggested values from the IS. o originating L1 lsp buffer size Support: L1,L2 Default: 1492 Value: 128-1492 Maximum size of level 1 LSPs and SNPs originated at this node. o originating L2 lsp buffer size Support: L2 Default: 1492 Value: 128-1492 Maximum size of level 2 LSPs and SNPs originated at this node. o partial snp interval Support: L1,L2 Default: 2 Value: 1-65535 Minimum interval, in seconds, between sending partial SNPs. o poll es hello rate Support: All Default: 50 Value: 1-65535 Interval, in seconds, between ES Hellos when a router requires to poll the ES configuration. o queue threshold Support: L1,L2 Default: 1 Value: 1-63 Average queue length at a router, above which the "congestion experienced" bit will be set in a forwarded data PDU. o waiting time Support: L1,L2 Default: 60 Value: 1-65535 Delay, in seconds, between routing databases being in the waiting state and entering the on state. o zero age lifetime Support: L1,L2 Default: 60 Value: 1-65535 Time, in seconds, for which the purge header of an expired LSP is retained.
4 – Status
o area addresses Support: All A set of area addresses. If the node is an end node, these are the area address portions of the NETs of all adjacent routers. If the node is a level 1 or level 2 router, this set is the union of the sets of manual area addresses reported in all level 1 LSPs received by this router. o egp port Support: IP Name of the routing port entity used for sending and receiving EGP messages. This attribute is set when a routing egp group entity is enabled. o icmp port Support: IP Name of the routing port entity used for sending and receiving ICMP messages. This attribute is set when the routing module is enabled and the protocols characteristic includes the value IP. o L1 state Support: L1,L2 State of the level 1 database. off Routing is disabled. on Routing is enabled and operating correctly. waiting Routing has received routing information that it cannot store and is waiting for the overload to be removed. o L2 state Support: L2 State of the level 2 database. off Routing is disabled. on Routing is enabled and operating correctly. waiting Routing has received routing information that it cannot store and is waiting for the overload to be removed. o nearest L2 router adjacencies Support: L1,L2 Names of adjacencies to be used for forwarding to the nearest level 2 router. If the node is a level 2 router adjacent to other areas, or if it is a level 1 router in an area with no attached level 2 routers, this set is empty. o rip port Support: IP Name of the udp port entity used by the routing module for sending and receiving RIP messages. This attribute is set when a routing circuit entity is enabled with its rip state characteristic set to any value other than off. o state Support: All State of the routing entity. off The entity is disabled. on The entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created.
5 – circuit
show [node node-id] routing - circuit circuit-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status Examples: show routing circuit * name, state show routing circuit csmacd-1 all
5.1 – Identifier
o name Simple name assigned to the circuit when it is created.
5.2 – Characteristics
o alternative subnet addresses Support: L1,L2,IP Default: No addresses Value: Set of subnet-address A set of alternative IP addresses and subnet masks for this interface. You can modify this characteristic only when the entity is disabled. o arp holding time Support: IP Default: 600 Value: 30-65535 Number of seconds to hold on to a routing circuit ip address translation entity. This characteristic is supported only if the circuit's type characteristic is csma-cd. o arp response waiting time Support: IP Default: 3 Value: 1-10 Number of seconds to wait for an ARP response when an ARP request has been sent. This characteristic is supported only if the circuit's type characteristic is csma-cd. o authentication type Support: L1,L2,IP Default: None Value: None or simple Type of authentication to be used for LAN L1 Hellos, LAN L2 Hellos, or PtPt Hellos on this circuit. o data link entity Support: All Default: No data link Value: Local-entity-name 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. o directed broadcast Support: L1,IP Default: On Value: Off or On Specifies how an IP packet is to be forwarded on a broadcast link. off Discard the packet silently. on Broadcast the packet using data level link broa that either of the following conditions is true: o The packet's subnet address matches the value of the subnet address characteristic. o The packet's subnet address matches one of the values of the alternative subnet addresses characteristic. This characteristic is supported only if the characteristic type is set to csma-cd. o 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. o 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. o 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. o hello timer Support: L1,L2 Default: 10 Value: 1-32767 Interval, in seconds, between IS Hello messages. o 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. o 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. o 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. o 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. o L1 cost Support: L1,L2 Default: 20 Value: 1-63 Cost of this circuit for level 1 traffic. o 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. o L2 cost Support: L2 Default: 20 Value: 1-63 Cost of this circuit for level 2 traffic. o 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. o 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. o manual data link sdu size for ip Support: IP Default: See Value: 128-65535 description Preferred maximum DSDU size, in octets, for the transmission of IP packets. The DSDU size includes the size of the packet containing the IP header. On point-to-point HDLC links, the DSDU size also includes the 1-octet link encapsulation (that is, the maximum IP packet size is the value of this attribute minus 1). The default value depends on the circuit type, as follows: csma-cd 1500 ddcmp 1500 hdlc 1500 X.25 (all 576 types) You can modify this characteristic only when the entity is disabled. o 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. o 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. o maximum arp retries Support: IP Default: 3 Value: 1-10 Maximum number of times that an ARP request can be sent for the same IP address. This characteristic is supported only if the circuit's characteristic type is set to csma-cd. o 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. o 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. o 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. o 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. o receive passwords Support: L1,L2,IP Default: No passwords Value: Set of hex-string Set of passwords that are valid in received LAN L1 Hellos, LAN L2 Hellos, and PtPt Hellos when simple authentication is in use on this circuit. You cannot use the show command to display the value of this attribute. o 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. o 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. o 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. o rip generated default route Support: L1,L2,IP Default: False Value: True or false If true, this specifies that the default route is announced in RIP messages sent on this circuit, with the metric value specified in the RIP generated default route metric characteristic. If false, the default route is not generated. o rip generated default route metric Support: L1,L2,IP Default: 1 Value: 0-16 Specifies the metric to be used when announcing a generated default route through RIP on this circuit. o rip neighbors Support: L2,IP Default: No addresses Value: Set of IP-addresses IP addresses of neighboring systems with which RIP will be exchanged on this circuit. If the circuit is a point-to-point circuit, this set must contain a single IP address if the rip state characteristic is to be set to send and receive. Also, you must disable the entity before altering this characteristic. If the rip send type characteristic is set to broadcast, only RIP messages from addresses specified in this set will be received; other messages will be silently discarded. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol. o rip poisoned reverse Support: L2,IP Default: True Value: True or false Specifies whether poisoned reverse routes are to be sent in RIP messages on this circuit. If false, poisoned reverse routes are not sent. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol. o rip receive default route Support: L2,IP Default: True Value: True or false Specifies whether the default route is accepted from RIP messages on this circuit. If false, the default route from RIP messages on this circuit is discarded. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol. o rip send type Support: L2,IP Default: Broadcast Value: Broadcast or point-to-point Specifies how RIP messages are sent on this circuit. broadcast RIP messages are sent via data link broadcast. point-to- RIP messages are sent directly to each IP address point specified in the rip neighbors characteristic. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol and if the circuit's type characteristic is csma-cd. o rip state Support: L2,IP Default: Off Value: See description Specifies how RIP messages are treated on this circuit. off RIP messages cannot be sent or received on this circuit. receive RIP messages can be received but not sent on this circuit. send and RIP messages can be sent and received on this receive circuit. This characteristic is supported only if the routing protocols supported characteristic of the routing entity includes the RIP routing protocol. o send password Support: L1,L2,IP Default: No password Value: Hex-string Password to be sent in LAN L1 Hellos, LAN L2 Hellos, and PtPt Hellos when simple authentication is used on this circuit. You cannot use the show command to display the value of this attribute. o subnet address Support: IP Default: 0.0.0.0 Value: Subnet address IP address and subnet mask of this interface. You can modify this characteristic only when the entity is disabled. o 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. o 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. o type Support: All Type of circuit. You cannot modify this characteristic. This characteristic is set by means of an argument to the create command. csma-cd The circuit is a broadcast circuit. ddcmp The circuit is a DDCMP circuit. hdlc The circuit is an HDLC circuit. x25 da The circuit is a dynamically allocated X.25 circuit. x25 X.25 permanent virtual circuit. permanent x25 static Static incoming X.25 circuit. incoming x25 static Static outgoing X.25 circuit. outgoing o 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.
5.3 – Counters
o authentication failures Support: L1,L2,IP Number of times a PDU has been received on this circuit with an Authentication Information field that is incompatible with the PDU type. o calls failed Support: All Number of unsuccessful call attempts on this circuit. This attribute is supported only if the characteristic type is x25 da. o calls placed Support: All Number of call attempts (successful and unsuccessful) on this circuit. This attribute is supported only if the characteristic type is x25 da. o changes in adjacency state Support: All Number of times the status attribute state of an adjacency belonging to this circuit changes from Up to Down (or Initializing), or the reverse. o changes in ip adjacency state Support: IP Number of times the status attribute state of an IP adjacency belonging to this circuit changes from Up to some other state, or the reverse. o changes in rip neighbor state Support: L2,IP Specifies the number of times the RIP state of IP adjacencies belonging to this circuit have changed. This attribute is supported only if the routing entity's characteristic routing protocols supported includes the routing protocol RIP. o circuit changes Support: All Number of times that the status attribute state has changed from on to off, or vice versa. o congestion discards Support: L1,L2 Number of data-and error-report NPDUs that have been discarded, before or after fragmentation, because of congestion. Any other discarding will already have been done by the forwarding process. This number includes all PDUs recognized by the receive process as data PDUs (DECnet-Plus data- and error-report PDUs and Phase IV data packets), even though they may subsequently be discarded for some reason. o control pdus received Support: All Number of control PDUs that have been received on this circuit. This number includes all Network layer PDUs, with the exception of DECnet-Plus data and error report PDUs and Phase IV data PDUs. o control pdus sent Support: All Number of control PDUs that have been sent on this circuit. o corrupted lsps received Support: L1,L2 Number of times a corrupted link state packet has been received on this circuit. o corrupted hello pdus received Support: All Number of times an ES-IS (end system to intermediate system) or IS-IS (intermediate system to intermediate system) Hello PDU has been received on this circuit that either cannot be parsed or contains an incorrect checksum. o creation time Support: All Time this entity was created. o da adjacency changes Support: All Number of DA adjacency change events that have been generated. o data pdus forwarded Support: L1,L2 Number of data- and error-report NPDUs that have been forwarded onto this circuit (either from another circuit or from a local port). This number includes all PDUs recognized by the receive process as data PDUs (DECnet-Plus data- and error-report PDUs and Phase IV data packets), even though they may subsequently be discarded for some reason. o data pdus fragmented Support: All Number of data NPDUs that have been fragmented on this circuit. o data pdus received Support: All Number of data- and error-report NPDUs that have been received on this circuit. This number includes all PDUs recognized by the receive process as data PDUs (DECnet-Plus data and error report PDUs and Phase IV data packets), even though they may subsequently be discarded for some reason. o data pdus transmitted Support: All Number of data- and error-report NPDUs, after fragmentation, that have been delivered to the port for transmission on this circuit. This number includes all PDUs recognized by the receive process as data PDUs (DECnet-Plus data- and error-report PDUs and Phase IV data packets), even though they may subsequently be discarded for some reason. o exceeded maximum svc adjacencies Support: End,L2 Number of exceeded maximum svc adjacency events that have been generated. This counter is supported only if the circuit's type is set to x25 da; only for nodes that are end nodes; and if the system supports dual routing (both DECnet and IP routing). o id reachablity changes Support: All Number of ID reachability change events that have been generated. o initialization failures Support: All Number of times that an attempt to initialize an adjacent node over this circuit has failed, either because of version skew or area mismatch. o ip fragmentation failure discards Support: IP Number of IP packets discarded because fragmentation was required to transmit them, but the IP header requested "do not fragment." This attribute is supported only if the system supports dual routing (both DECnet and IP routing). o ip fragments created Support: IP Number of IP fragments created for transmission on this circuit. o ip packets forwarded Support: IP Number of IP packets forwarded on this circuit before fragmentation. These IP packets may be from another circuit or from a local port. Note that this value includes those IP packets counted in the ip send discards counter. o ip packets fragmented Support: IP Number of IP packets that have been fragmented on this circuit. o ip packets received Support: IP Number of IP packets received on this circuit. This value includes all types of IP packet (control, data, etc.), and those that may subsequently be discarded for any reason. o ip received discards Support: IP Number of IP packets that have been received and then discarded because of congestion. o ip send discards Support: IP Number of IP packets for transmission that have been discarded because of congestion. o irrecoverable svc failures Support: All Number of times that the number of re-call attempts on this circuit has become equal to the value of the characteristic maximum call attempts. This attribute is supported only if the characteristic type is set to x25 static outgoing. o LAN l1 designated router changes Support: L1,L2 Number of times the local node has either elected itself or resigned as the LAN level 1 designated router on this circuit. This attribute is supported only if the circuit's characteristic type is set to csma-cd. o LAN l2 designated router changes Support: L2 Number of times the local node has either elected itself or resigned as the LAN level 2 designated router on this circuit. o LAN phaseiv designated router changes Support: L1,L2 Number of times the local node has either elected itself or resigned as the LAN Phase IV designated router on this circuit. o redirect discards Support: End Number of Redirect PDUs that have been discarded because of insufficient cache memory. o rejected adjacencies Support: All Number of times an attempt to create a new adjacency using this circuit has failed because of insufficient resources. o rejected ip adjacencies Support: L2,IP Number of times an attempt to automatically create a new IP adjacency to an IP router has failed because of lack of resources. o rip errors received Support: L2,IP Number of RIP messages received with any kind of received error on this circuit. This attribute is supported only if the routing entity's characteristic routing protocols supported includes the routing protocol RIP. o segmentation failure discards Support: L1,L2 Number of data NPDUs that have been discarded because segmentation was required to send them on this circuit but was not permitted in the NPDU header. o verification reject events Number of verification reject events that have been generated. This attribute is supported only if the characteristic type is set to ddcmp, hdlc, x25 static incoming, x25 static outgoing, or x25 permanent.
5.4 – Status
o data link port Support: All Name of the data link port used for this circuit. Not supported on DA circuits. o data link sdu size Support: All Maximum size, in octets, of a Data Link SDU for this circuit. This includes the Network layer header, but excludes the Data Link layer header. The value of this status is the lesser of the value of the characteristic manual data link sdu size and any limit imposed by the Data Link layer. o LAN L1 id Support: L1,L2 LAN ID allocated by the LAN level 1 designated router. This attribute is supported only if the circuit's characteristic type is csma-cd. o LAN L2 id Support: L2 LAN ID allocated by the LAN level 2 designated router. This attribute is supported only if the circuit's characteristic type is csma-cd. o L1 designated router Support: L1,L2 ID of the DECnet-Plus level 1 designated router on this circuit. This attribute is supported only if the circuit's characteristic type is csma-cd. If this node does not participate in the router election process, the value returned is 00-00-00-00-00-00. o L2 designated router Support: L2 ID of the DECnet-Plus level 2 designated router on this circuit. This attribute is supported only if the circuit's characteristic type is csma-cd. If this node does not participate in the router election process, the value returned is 00-00-00-00-00-00. o phaseiv designated router Support: L1,L2 ID of the Phase IV designated router on this circuit. This attribute is supported only if the circuit's characteristic type is csma-cd. If this node does not participate in the router election process, the value returned is 00-00-00-00-00-00. o point-to-point id Support: L1,L2 ID allocated to the circuit during its initialization. This attribute is supported only if the circuit's characteristic type is hdlc, ddcmp, or x25 static. o state State of the routing circuit entity. Support: All off The circuit is disabled. on The circuit is enabled. o uid Entity's unique identifier, which is generated when the entity is created.
5.5 – adjacency
show [node node-id] routing - circuit circuit-name - adjacency adjacency-name attribute [,attribute...] all [attributes] all identifiers all status Examples: show routing circuit csmacd-1 adjacency * name, state, lan address show routing circuit csmacd-1 adjacency RTG$0001 all
5.5.1 – Identifier
o name Simple name assigned to the adjacency when it is created.
5.5.2 – Status
o data link port Support: All Name of the data link port used for this X.25 data adjacency. This attribute is supported only if the owning routing circuit entity's characteristic type is set to x25 da. o dte address Support: All DTE address of the neighboring node on an X.25 circuit. This status is supported only if the owning circuit entity's characteristic type is x25 da. o endnode ids Support: All System IDs of neighboring end nodes. This attribute is supported only if the node is an end node and the owning circuit entity's characteristic type is not x25 da. o endnode nets Support: All NETs computed from the system IDs in the endnode ids status and the set of area addresses in the owning routing entity's manual area addresses set. This attribute is supported only if the node is an end node and the owning circuit entity's characteristic type is not x25 da. o holding timer Support: L1,L2 Holding time for this adjacency, updated from the router-to- router Hello messages. This attribute is supported only if both the node and the adjacency are routers. o ip addresses Support: IP IP addresses of the neighbor node. If these are not known, the set is empty. o LAN address Data link address of the neighboring node on a broadcast circuit. This status is supported only if the owning circuit entity's characteristic type is csma-cd. o LAN priority Support: L1,L2 Priority of the neighbor of this adjacency for becoming the LAN level 1 designated router (if the adjacency is a DECnet-Plus level 1 router) or the LAN level 2 designated router (if the adjacency is a DECnet-Plus level 2 router). This status is supported only if the owning circuit entity's characteristic type is csma-cd; and the adjacency is a router rather than an end node. o level Support: L1,L2 The level of the adjacency. This attribute is supported only if both the node and the adjacency are routers. Level 1 The adjacency is used for level 1 routing. Level 2 The adjacency is used for level 2 routing. Level 1 & 2 The adjacency is used for level 1 and level 2 routing. Level 0 The usage is undefined. o neighbor areas Support: L1,L2 Area addresses of the neighboring node. This attribute is supported only if both the node and the adjacency are routers and the owning circuit entity's characteristic type is not x25 da. o neighbor node id Support: L1,L2 Node ID of the neighboring node. o neighbor node type Support: All Type of the neighboring node. This status is supported only if the owning circuit entity's characteristic type is not x25 da. non-dna The node is not a DNA router. router phase iv The node is a Phase IV end node. endnode phase iv The node is a Phase IV level 1 router. level 1 router phase iv The node is a Phase IV level 2 router. level 2 router DECnet-Plus The node is a DECnet-Plus end node. endnode DECnet-Plus The node is a DECnet-Plus level 1 router. level 1 router DECnet-Plus The node is a DECnet-Plus level 2 router. level 2 router DECnet-Plus The node is a DECnet-Plus router. router unknown The node type is unknown. phase iv The node is a Phase IV router. router o neighbor protocols supported Support: IP Network protocols supported by the neighboring node (either IP or ISO8473). o router nets Support: End Network Entity Title(s) (NETs) of a neighboring router. This status is supported only if the adjacency is a level 1 or level 2 router, and the owning circuit entity's characteristic type is not x25 da. o state Support: All State of the routing circuit adjacency entity. May be one of the following: failed initializing up up/dormant o type Type of adjacency. autoconfigured Created by autoconfiguration. manual Created manually by a create command. This attribute indicates whether the adjacency has been manually created, or whether the adjacency was created by means of hello PDUs. It will always have the value manual when it has been created by the create command; otherwise, it will have the value autoconfigured.
5.6 – ip_address_translation
show [node node-id] routing - circuit circuit-name - ip address translation ip-address attribute [,attribute...] all [attributes] all identifiers all status
5.6.1 – Identifier
o ip address IP address of the neighbor.
5.6.2 – Status
o LAN address Support: IP LAN address that corresponds to the IP address of this neighbor.
5.7 – ip_reachable_address
show [node node-id] routing - circuit circuit-name - ip reachable address ip-address attribute [,attribute...] all [attributes] all characteristics all identifiers all status
5.7.1 – Characteristics
o destination Support: L2,IP The IP address and subnet mask to which this reachable address refers. This value is derived from the destination argument of the create command. You cannot modify this characteristic. o dte addresses Support: L2,IP Default: No DTE Value: Set of DTE addresses addresses A set of DTE addresses to which a call may be directed in order to reach an address that matches the subnet address given by the subnet address characteristic. You can modify this characteristic only when the entity is disabled. This characteristic is supported only if the owning circuit is an X.25 circuit. o metric Support: L2,IP Default: 20 Value: 1-maximum link cost Default metric value for reaching the specified subnet over this circuit. You can modify this characteristic only when the entity is disabled. o metric class Support: L2,IP Default: External Value: External or internal Class of the default metric, which controls the preference for this route in the decision process. external The I/E bit for the default metric in the External Reachability Information option of level 2 link state packets is set to 1. The subnet address specified by this IP reachable address will have the same preference as level 2 external routes. internal The I/E bit for the default metric in the External Reachability Information option of level 2 link state packets is set to 0. The subnet address specified by this IP reachable address will have the same preference as level 2 internal routes. You can modify this characteristic only when the entity is disabled. o next hop Support: L2,IP Default: 0.0.0.0 Value: IP-address IP address of the neighboring node through which the destination is reachable. When you create this entity, this characteristic is set to the value of the IP address component of the destination argument of the create command if the IP reachable address is to an IP host. This characteristic is not used on circuits of type x25 da. You can modify this characteristic only when the entity is disabled.
5.7.2 – Identifier
o name Simple name assigned to the IP reachable address when it is created.
5.7.3 – Status
o state Status of the routing circuit reachable address entity. off The IP reachable address is disabled. on The IP reachable address is enabled.
5.8 – reachable_address
show [node node-id] routing - circuit circuit-name - reachable address simple-name attribute [,attribute...] all [attributes] all characteristics all identifiers all status
5.8.1 – Characteristics
o address prefix Support: L2,End Default: None Value: Address Prefix Address prefix to which this reachable address refers. You cannot modify this characteristic. This characteristic is set by means of an argument to the create command. The value of this characteristic derives from an argument to the create command. This characteristic is supported only if the owning circuit has type set to x25 da. o 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. o cost Support: L2 Default: 20 Value: 1-63 Cost of reaching this address prefix over this circuit. o data format Support: L2 Default: Phase V Value: Phase IV (1) or Phase V (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. o 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. o 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. o 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. o 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. o 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. o 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. o 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. o 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. o 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. o 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.
5.8.2 – Identifier
o name Simple name assigned to the reachable address when it is created.
5.8.3 – Status
o state State of the routing circuit reachable address entity. off The reachable address is disabled. on The reachable address is enabled.
6 – destination_area
show [node node-id] routing - destination area address-prefix attribute [,attribute] all [attributes] all identifiers all status This is supported only on nodes that are Level 2 routers.
6.1 – Identifier
o name Address prefix associated with this destination area.
6.2 – Status
o cost Support: L2 Cost of the least cost path(s) to this destination area. o output adjacencies Support: L2 Set of routing circuit and routing circuit adjacency (or routing circuit reachable address) entity names that represent the forwarding decisions for this destination area.
7 – destination cache (Tru64 UNIX)
show [node node-id] routing - destination cache address-prefix attribute [,attribute...] all [attributes] all identifiers all status
7.1 – Identifier
o name Address prefix associated with this destination area.
7.2 – Status
o information The set of records containing cache information relating to this address.
8 – destination_node
show [node node-id] routing - destination node node-id attribute [,attribute...] all [attributes] all identifiers all status This is supported on only on Level 1 and Level 2 routers.
8.1 – Identifier
o name System ID associated with this destination node.
8.2 – Status
o cost Support: L1,L2 Cost of the least cost path(s) to this destination node. o nets Support: L1,L2 Set of NETs computed from the system ID that is the entity's name and the area addresses in the routing entity's manual area addresses set. o output adjacencies Support: L1,L2 Set of routing circuit and routing circuit adjacency entity names representing the forwarding decisions for this destination node.
9 – egp_group
show [node node-id] routing - egp group group-name attribute [,attribute...] all [attributes] all characteristics all identifiers all status This is supported only on Level 2 routers that support dual routing (and, in particular, the EGP routing protocol).
9.1 – Characteristics
o 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). o 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. o 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. o 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. o 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. o 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. o 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.
9.2 – Identifier
o name Simple name assigned to the EGP group when it is created.
9.3 – Status
o state Specifies the state of the routing egp group entity. off The entity is disabled. on The entity is enabled.
9.4 – egp_neighbor
show [node node-id] routing - egp group group-name - egp neighbor neighbor-name attribute [,attribute...] all [attributes] all characteristics all counters all identifiers all status This is supported only on Level 2 routers that support dual routing (and, in particular, the EGP routing protocol).
9.4.1 – Characteristics
o circuit Default: None Value: Circuit name Simple-name of the circuit. o ip address Support: L2,IP Internet address of this EGP neighbor. The value of this characteristic is derived from the ip address argument of the create command. You cannot modify this characteristic. o next hop Default: 0.0.0.0 Value: IP address IP address and the next routing node. o source network Default: 0.0.0.0 Value: Network number Network number to query.
9.4.2 – Counters
o creation time Support: L2,IP Time at which this entity was created. o error messages received Support: L2,IP Number of EGP error messages received from this neighbor. o error messages sent Support: L2,IP Number of EGP error messages sent to this neighbor. o messages received Support: L2,IP Number of EGP messages received without error from this neighbor. o messages sent Support: L2,IP Number of EGP messages sent to this neighbor. Note that this value does not include EGP messages counted by the counter send messages discarded. o received messages discarded Support: L2,IP Number of EGP messages received from this neighbor with any kind of error. o send messages discarded Support: L2,IP Number of EGP messages not sent to this neighbor because of resource limitations within the egp entity. o start events Support: L2,IP Number of times the EGP neighbor has been manually started. o stop events Support: L2,IP Number of times the EGP neighbor has been manually stopped.
9.4.3 – Identifier
o name Simple name assigned to the EGP neighbor when it is created.
9.4.4 – Status
o egp state Support: L2,IP EGP state of the system with respect to this EGP neighbor. acquisitionidle cease up down o hello time Support: L2,IP Interval, in hundredths of a second, between retransmissions of EGP Hellos. This value represents the t1 timer defined in RFC 904. o last event Support: L2,IP Specifies whether the last event issued on this EGP neighbor was a start or a stop event. start The last event was a start. stop The last event was a stop. This is the value with which an EGP neighbor is created, before either a start or stop command has been issued. o polling mode Support: L2,IP Polling mode of the EGP entity with respect to this neighbor as either active or passive. o poll time Support: L2,IP Interval, in hundredths of a second, between retransmissions of EGP polls. This value represents the t3 timer defined in RFC 904. o state State of the routing egp group egp neighbor entity. off The entity is disabled. on The entity is enabled. o uid Entity's unique identifier, which is generated when the entity is created.
10 – ip_destination_address
show [node node-id] routing - ip destination address address-name attribute [,attribute...] all [attributes] all identifiers all status This is supported only on routers that support dual routing.
10.1 – Identifier
o name Subnet address of a destination subnetwork.
10.2 – Status
o level Support: L1,L2,IP Level at which the shortest path exists in the shortest paths database. Level 1 Level 2 External Level 2 Internal o metric Support: L1,L2,IP Default metric value for the shortest path to the destination subnetwork. o paths Support: L1,L2,IP Equal cost paths for this route. For each path the following information is given: 1. The name of the entity pair that represents the forwarding decision for this path (circuit and one of adjacency, IP adjacency, or IP reachable address). 2. The routing mechanism through which the route was learned: o Local: the route is derived from the subnet address or alternative subnet addresses characteristics of a local circuit. o Netmgnt: the route is derived from manually configured information on the local system. 3. The number of seconds since the route was last updated.
11 – permitted_neighbor
show [node node-id] routing - permitted neighbor neighbor-name attribute [,attribute...] all [attributes] all characteristics all identifiers
11.1 – Characteristics
o id Support: All Default: No default Value: Node ID Node ID of a potential neighbor node. You cannot modify this characteristic. This characteristic is set by means of an argument to the create command. o 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.
11.2 – Identifier
o name Simple name assigned to the permitted neighbor when it is created.
12 – port
show [node node-id] routing - port port-name attribute [,attribute...] all [attributes] all counters all identifiers all status Examples: show routing port * name, client show routing port RTG$PORT21 all
12.1 – Counters
o creation time Support: All Time the entity was created. o data sdus received Support: All Number of data NSDUs delivered across Transport interface (after reassembly). o error reports received Support: All Number of error report PDUs delivered across Transport interface. o expired segments discarded Support: All Number of segments discarded because lifetime expired during reassembly. o ip packets reassembled Support: IP Number of IP packets that have been successfully reassembled from fragments. o sdus transmitted Support: All Number of data NSDUs requested for transmission across Transport interface. o segments discarded Support: All Number of segments (data- or error-report) discarded before delivery across the Transport interface, including segments discarded for any reason other than lifetime expiration during reassembly. o segments received Support: All Number of data- and error-report NPDUs received before reassembly.
12.2 – Identifier
o name Simple name assigned to the port when it is created.
12.3 – Status
o client Support: All Name given by the user of the port when the port was opened. o nsap addresses Support: All Set of NSAP addresses to be received at this port. This attribute is supported only if the status attribute type is not set to IP. o nsap selector Support: All Network service access point (NSAP) selector octet supplied by the client. This attribute is supported only if the status attribute type is not set to ip. o protocol type Support: IP Value of the IP protocol field specified by the client. o type Support: IP Type of connectionless network service to be used: IP or ISO8473. o uid Entity's unique identifier, which is generated when the entity is created.