|
|
An enhancement has been made to NLSP that allows the router to interpret the maximum lifetime field in a Level 1 link-state packet (LSP) in hours or seconds. Previously, the field was interpreted in seconds only.
By being able to interpret the maximum lifetime field in hours, the router will be able to keep LSP packets for a much longer time which will reduce overhead on slower-speed serial links and keep ISDN links from becoming active unnecessarily.
This feature is supported on these platforms:
To set the maximum time that LSPs persist without being refreshed, perform the following task in router configuration mode:
| Task | Command |
|---|---|
| Set the maximum time LSPs persist. | max-lsp-lifetime [hours] value |
The following example sets the maximum time that the LSP persists to 11,000 seconds (more than 3 hours):
max-lsp-lifetime 11000
The following example sets the maximum time that the LSP persists to 15 hours:
max-lsp-lifetime hours 15
This section documents the following modified commands:
All other commands used with this feature are documented in the Cisco IOS Release 11.2 command references.
To set the maximum time that link-state packets (LSPs) persist without being refreshed, use the max-lsp-lifetime router configuration command. To restore the default time, use the no form of this command.
max-lsp-lifetime [hours] value| hours | (Optional) If specified, the lifetime of the LSP is set in hours. If not specified, the lifetime is set in seconds. |
| value | Lifetime of LSP in hours or seconds. It can be a number in the range 1 to 32767. The default is 7500 seconds. |
7500 seconds (2 hours, 5 minutes)
Router configuration
This command first appeared in Cisco IOS Release 11.2 F.
You might need to adjust the maximum LSP lifetime if you change the LSP refresh interval with the lsp-refresh-interval router configuration command. The maximum LSP lifetime must be greater than the LSP refresh interval.
The following example sets the maximum time that the LSP persists to 11,000 seconds (more than 3 hours):
max-lsp-lifetime 11000
The following example sets the maximum time that the LSP persists to 15 hours:
max-lsp-lifetime hours 15
ipx router nlsp
lsp-refresh-interval
To display the entries in the link-state packet (LSP) database, use the show ipx nlsp database EXEC command.
show ipx nlsp [tag] database [lspid] [detail]| tag | (Optional) Names the NLSP process. The tag can be any combination of printable characters. |
| lspid | (Optional) Link-state protocol ID (LSPID). You must specify this in the format xxxx.xxxx.xxxx.yy-zz. The components of this argument have the following meaning:
· xxxx.xxxx.xxxx is the system identifier. · yy is the pseudo identifier. · zz is the LSP number. |
| detail | (Optional) Displays the contents of the LSP database entries. If you omit this keyword, only a summary display is shown. |
EXEC
This command first appeared in Cisco IOS Release 11.2 F.
When you specify an NLSP tag, the router displays the link-state packet (LSP) database entries for that NLSP process. An NLSP process is a router's databases working together to manage route information about an area. NLSP version 1.0 routers are always in the same area. Each router has its own adjacencies, link-state, and forwarding databases. These databases operate collectively as a single process to discover, select, and maintain route information about the area. NLSP version 1.1 routers that exist within a single area also use a single process.
NLSP version 1.1 routers that interconnect multiple areas use multiple processes to discover, select, and maintain route information about the areas they interconnect. These routers manage an adjacencies, link-state, and area address database for each area to which they attach. Collectively, these databases are still referred to as a process. The forwarding database is shared among processes within a router. The sharing of entries in the forwarding database is automatic when all processes interconnect NLSP version 1.1 areas.
Configure multiple NLSP processes when a router interconnects multiple NLSP areas.
If you omit all options, a summary display is shown.
The following is sample output from the show ipx nlsp database command:
Router# show ipx nlsp database detail
LSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL
0000.0C00.3097.00-00* 0x00000042 0xC512 699 0/0/0
0000.0C00.3097.06-00* 0x00000027 0x0C27 698 0/0/0
0000.0C02.7471.00-00 0x0000003A 0x4A0F 702 0/0/0
0000.0C02.7471.08-00 0x00000027 0x0AF0 702 0/0/0
0000.0C02.7471.0A-00 0x00000027 0xC589 702 0/0/0
0000.0C02.747D.00-00 0x0000002E 0xC489 715 0/0/0
0000.0C02.747D.06-00 0x00000027 0xEEFE 716 0/0/0
0000.0C02.747D.0A-00 0x00000027 0xFE38 716 0/0/0
0000.0C02.74AB.00-00 0x00000035 0xE4AF 1059 0/0/0
0000.0C02.74AB.0A-00 0x00000027 0x34A4 705 0/0/0
0000.0C06.FBEE.00-00 0x00000038 0x3838 1056 0/0/0
0000.0C06.FBEE.0D-00 0x0000002C 0xD248 1056 0/0/0
0000.0C06.FBEE.0E-00 0x0000002D 0x7DD2 99h 3576s 0/0/0
0000.0C06.FBEE.17-00 0x00000029 0x32FB 99h 3576s 0/0/0
0000.0C00.AECC.00-00* 0x000000B6 0x62A8 7497 0/0/0
IPX Area Address: 00000000 00000000
IPX Mgmt Info 87.0000.0000.0001 Ver 1 Name oscar
Metric: 45 Lnk 0000.0C00.AECC.06 MTU 1500 Dly 8000 Thru 64K PPP
Metric: 20 Lnk 0000.0C00.AECC.02 MTU 1500 Dly 1000 Thru 10000K 802.3 Raw
Metric: 20 Lnk 0000.0C01.EF90.0C MTU 1500 Dly 1000 Thru 10000K 802.3 Raw
0000.0C00.AECC.02-00* 0x00000002 0xDA74 3118 0/0/0
IPX Mgmt Info E0.0000.0c00.aecc Ver 1 Name Ethernet0
Metric: 0 Lnk 0000.0C00.AECC.00 MTU 0 Dly 0 Thru 0K 802.3 Raw
0000.0C00.AECC.06-00* 0x00000002 0x5DB9 7494 0/0/0
IPX Mgmt Info 0.0000.0000.0000 Ver 1 Name Serial0
Metric: 0 Lnk 0000.0C00.AECC.00 MTU 0 Dly 0 Thru 0K PPP
Metric: 1 IPX Ext D001 Ticks 0
Metric: 1 IPX SVC Second-floor-printer D001.0000.0000.0001 Sock 1 Type 4
Table 12 explains the fields in the display.
| Field | Description |
|---|---|
| LSPID | System ID (network number), pseudonode circuit identifier, and fragment number. |
| LSP Seq Num | Sequence number of this LSP. |
| LSP Checksum | Checksum of this LSP. |
| LSP Holdtime | Time until this LSP expires, in hours or seconds. |
| ATT/P/OL | Indicates which of three bits are set. A "1" means the bit is set, and a "0" means it is not set.
ATT is the L2-attached bit. P is the partition repair bit. This bit is not used in NLSP. OL is the overload bit. |
| IPX Area Address: | Area address of the router advertising the LSP. |
| IPX Mgmt Info | Management information. For nonpseudonode LSPs, the internal network number is advertised in this field. For pseudonode LSPs, the network number of the associated interface is advertised. |
| Ver | NLSP version running on the advertising router. |
| Name | For nonpseudonode LSPs, the name of the router. For pseudonode LSPs, the name (or description, if configured) of the associated interface. |
| Link Information | |
| Metric: | NLSP metric (cost) for the link. Links from a pseudonode to real nodes have a cost of 0 so that this link cost is not counted twice. |
| Lnk | System ID of the adjacent node. |
| MTU | MTU of the link in bytes. For pseudonode LSPs, the value in this field is always 0. |
| Dly | Delay of the link in microseconds. For pseudonode LSPs, the value in this field is always 0. |
| Thru | Throughput of the link in bits per second. For pseudonode LSPs, the value in this field is always 0. |
| 802.3 Raw, Generic LAN | Link media type. |
| External (RIP) Networks | |
| Metric: | Received RIP hop count. |
| IPX Ext | IPX network number. |
| Ticks | Received RIP tick count. |
| SAP Services | |
| Metric: | Received SAP hop count. |
| IPX SVC | Name of the IPX service. |
| D001.0000.0000.0001 | IPX address of the server advertising this service. |
| Sock | Socket number of the service. |
| Type | Type of service. |
For more information on modifying LSP parameters, see the Cisco IOS Release 11.2 Network Protocols Configuration Guide, Part 2.
|
|