The ES-IS ROUTING information is maintained in six tables: (1) the SUBNET table (2) the LOCAL NSAP table (3) the ES table (4) the IS table (5) the STATIC-IS table (6) The NSAP-REACHABLE table Use the 'A' (again) and 'M' (more) commands to view the tables. 'Again' repeats the current screen, 'More' displays the next screen. A null command defaults to 'More'. The 'More' command is not listed if the current screen is the last screen. SET command defines a new table entry or changes a table entry, depending on the particular table (see individual table descriptions). The DELETE command deletes an entry from a table. The SET and DELETE commands require parameters. If you are not sure of the syntax, just type the SET or DELETE command and you will be prompted for all the relevant parameters. The expert user who knows the syntax can type the command followed by the parameters, thus bypassing the prompt messages. $ The fields marked with a '*' in the table headers are the fields that must be specified in SET commands. Further help can be obtained on the following topics (enter any unambiguous abbreviation): SUBNET-TABLE LOCAL-NSAP ES-TABLE IS-TABLE NSAP-REACHABLE TOPICS From the ROUTER MANAGEMENT screen, it is possible to request help directly on one of these topics by typing HELP . $$ SUBNET-TABLE LOCAL-NSAP ES-TABLE IS-TABLE STATIC-IS-TABLE NSAP-REACHABLE TOPICS $$ SUBNET TABLE. A station is usually part of only one subnet and therefore has one entry in the subnet table. A station with several entries in the subnet table is usually an Intermediate System (i.e. IS, i.e. router). Subnets can't be added to or deleted from the subnet table, but some of the characteristics of a subnet can be altered via the SET command: LIFETIME: USE PROTOCOL: Specify 0 if this subnet does not have a multicast facility and is therefore unable to use the ES-IS protocol. Specify non-zero if this subnet supports multicasting. Standard Intel 802.X subnets support multicasting. SSAP PREFIX If LOCAL ADDRESSING is true (see object 3922), NSAPs beginning with this prefix will be considered local. $$ LOCAL NSAP TABLE ---------------- Before this station can communicate with other stations, it needs to have one or more local NSAP addresses assigned. A local NSAP can be assigned in two ways: (1) Automatically at start-up time. If object 3924 is true, the station will be assigned an iNA960 R2 style NSAP address. (2) By means of the SET LOCAL-NSAP command. The local NSAP is a hex byte string of maximum length 15. It can be typed with or without spaces in between the bytes. DO NOT APPEND AN NSAP SELECTOR. $$ LOCAL ES TABLE ------------- When the ES-IS protocol is used or when local addressing applies, stations will find each other without an explicit definition of the NSAPs. However, if a remote station does not use the ES-IS protocol and can't be found through the local addressing scheme, it is necessary to define its NSAP in the LOCAL ES TABLE. The following parameters must be entered: NSAP ADDRESS: hex byte string INCLUDING NSAP SELECTOR. Can be typed with or without spaces in between the bytes. SUBNET NAME: must be one of the valid subnet names as seen in the subnet table. SUBNET ADDRESS: the station subnet address. On standard intel 802.X subnets, the subnet address is the 6 byte MAC address followed by FE. Can be typed with or without spaces in between the bytes. $$ IS TABLE -------- This table is present in End Systems only. When an End System is unable to resolve an NSAP, it will forward it to an Intermediate system if one is defined in the IS TABLE. Intermediate Systems that use the ES-IS protocol need not be explicitly defined in this table because they will make themselves known though the use of the protocol. However, Intermediate Systems that do not use the ES-IS protocol must be defined with the SET IS-TABLE command. The following parameters must be entered: NETWORK ENTITY TITLE: this is a 'logical address' of the IS, much like an NSAP, which will be needed to refer to this IS in a DELETE IS command. Hex string. Can be typed with or without spaces in between the bytes. SUBNET NAME: must be one of the valid subnet names as seen in the subnet table. SUBNET ADDRESS: the IS's subnet address. On standard intel 802.X subnets, the subnet address is the 6 byte MAC address followed by FE. Hex string. Can be typed with or without spaces in between the bytes. $$ STATIC IS TABLE --------------- This table usually exists on Intermediate Systems, although it can also exist on End Systems. Together with the NSAP REACHABLE table, the STATIC IS TABLE contains the information on how to forward frames to remote subnets. The difference between the IS TABLE and the STATIC IS TABLE is that the former is used by ES systems to find an IS, whereas the latter is used by IS systems to decide which other IS to forward a frame to. The following parameters must be entered: NETWORK ENTITY TITLE: this is a 'logical address' of the IS, much like an NSAP. It is not used but must be entered. Hex string. Can be typed with or without spaces in between the bytes. ROUTER NAME: arbitrary ASCII name that will be needed to refer to this static IS in the DELETE STATIC-IS command and in the NSAP-REACHABLE table. SUBNET NAME: must be one of the valid subnet names as seen in the subnet table. SUBNET ADDRESS: the IS's subnet address. On standard intel 802.X subnets, the subnet address is the 6 byte MAC address followed by FE. Hex string. Can be typed with or without spaces in between the bytes. $$ NSAP REACHABLE TABLE -------------------- Together with the STATIC IS table, the NSAP REACHABLE table contains the information on how to forward frames to remote subnets. An entry in this table specifies that NSAPs beginning with the specified prefix are to be forwarded to the specified router. The router must be specified by means of a valid static router name as defined in the STATIC IS table. $$ Further help can be obtained on the following topics (enter any unambiguous abbreviation): SUBNET-TABLE LOCAL-NSAP ES-TABLE IS-TABLE STATIC-IS-TABLE NSAP-REACHABLE TOPICS