Table Of Contents
default-information originate (IS-IS)
isis retransmit-throttle-interval
Integrated IS-IS Commands
Use the commands in this chapter to configure and monitor Intermediate System-to-Intermediate System (IS-IS) protocol. For IS-IS configuration information and examples, refer to the "Configuring Integrated IS-IS" chapter of the Network Protocols Configuration Guide, Part 1.
area-password
To configure the IS-IS area authentication password, use the area-password command in router configuration mode. To disable the password, use the no form of this command.
area-password password
no area-password [password]
Syntax Description
Defaults
No area password is defined and area password authentication is disabled.
Command Modes
Router configuration
Command History
Usage Guidelines
Using the area-password command on all routers in an area will prevent unauthorized routers from injecting false routing information into the linkstate database.
This password is exchanged as plain text and thus this feature provides only limited security.
This password is inserted in Level 1 (station router level) link state PDUs (LSPs), complete sequence number PDUs (CSNPs), and partial sequence number PDUs (PSNP).
Examples
The following example assigns an area authentication password:
router isisarea-password angelRelated Commands
Configures the IS-IS routing domain authentication password.
Configures the authentication password for an interface.
default-information originate (IS-IS)
To generate a default route into an IS-IS routing domain, use the default-information originate command in router configuration mode. To disable this feature, use the no form of this command.
default-information originate [route-map map-name]
no default-information originate [route-map map-name]
Syntax Description
route-map map-name
(Optional) Routing process will generate the default route if the route map is satisfied.
Defaults
This command is disabled by default.
Command Modes
Router configuration
Command History
Usage Guidelines
If a router configured with this command has a route to 0.0.0.0 in the routing table, IS-IS will originate an advertisement for 0.0.0.0 in its LSPs.
Without a route-map, the default is only advertised in L2 LSPs. For L1 routing, there is another mechanism to find the default route, which is to look for the closest L1L2 router. The closest L1L2 router can be found by looking at the attached-bit (ATT) in L1 LSPs.
A route-map can be used for two things: 1) make the router generate default in its L1 LSPs.
2) advertise 0/0 conditionally. With a match ip address standard-access-list command, you can specify one or more IP routes that must exist before the router will advertise 0/0.Examples
The following example forces the software to generate a default external route into an IS-IS domain:
router isis! BGP routes will be distributed into IS-ISredistribute bgp 120! access list 2 is applied to outgoing routing updatesdistribute-list 2 outdefault-information originate! access list 2 defined as giving access to network 10.105.0.0access-list 2 permit 10.105.0.0 0.0.255.255Related Commands
redistribute
Redistributes routes from one routing domain into another routing domain.
Displays the IS-IS link state database.
domain-password
To configure the IS-IS routing domain authentication password, use the domain-password command in router configuration mode. To disable a password, use the no form of this command.
domain-password password
no domain-password [password]
Syntax Description
Defaults
No password is specified and no authentication is enabled for exchange of L2 routing information.
Command Modes
Router configuration
Command History
Usage Guidelines
This password is exchanged as plain text and thus this feature provides only limited security.
This password is inserted in Level 2 (area router level) link state PDUs (LSPs), complete sequence number PDUs (CSNPs), and partial sequence number PDUs (PSNPs).
Examples
The following example assigns an authentication password to the routing domain:
router isisdomain-password flowerRelated Commands
Configures the IS-IS area authentication password.
Configures the authentication password for an interface.
ip router isis
To configure an IS-IS routing process for IP on an interface, use the ip router isis command in interface configuration mode. To disable IS-IS for IP, use the no form of this command.
ip router isis [tag]
no ip router isis [tag]
Syntax Description
Defaults
No routing processes are specified.
Command Modes
Interface configuration
Command History
Usage Guidelines
Before the IS-IS router process is useful, a NET must be assigned with the net command and some interfaces must be enabled with IS-IS.
If you have IS-IS running and at least one ISO-IGRP process, the IS-IS process and the ISO-IGRP process cannot both be configured without a tag. The null tag can be used by only one process. Therefore, if you do not use ISO-IGRP, the IS-IS tag should be null. If you run ISO-IGRP and IS-IS, a null tag can still be used for IS-IS, but not for ISO-IGRP at the same time.
Examples
The following example specifies IS-IS as an IP routing protocol for a process named Finance, and specifies that the Finance process will be routed on interfaces Ethernet 0 and serial 0:
router isis Financenet 49.0001.aaaa.aaaa.aaaa.00interface Ethernet 0ip router isis Financeinterface serial 0ip router isis FinanceRelated Commands
Configures an IS-IS network entity title (NET) for the routing process.
Enables the IS-IS routing protocol.
isis circuit-type
To configure the type of adjacency, use the isis circuit-type command in interface configuration mode. To reset the circuit type to Level l and Level 2, use the no form of this command.
isis circuit-type {level-1 | level-1-2 | level-2-only}
no isis circuit-type
Syntax Description
Defaults
A Level 1 and Level 2 adjacency is established.
Command Modes
Interface configuration
Command History
Usage Guidelines
Normally, this command does not need to be configured. The proper way is to configure a router as an L1-only, L1L2 or L2-only system. Only on routers that are between areas (L1L2 routers) should you configure some interfaces to be L2-only to prevent wasting bandwidth by sending out unused L1 hellos. Note that on point-to-point interfaces, the L1 and L2 hellos are in the same packet.
Examples
In the following example, other routers on Ethernet interface 0 are in the same area. Other routers on Ethernet interface 1 are in other areas, so the router will stop sending L1 hellos.
interface ethernet 0ip router isisinterface ethernet 1isis circuit-type level-2-onlyisis csnp-interval
To configure the IS-IS complete sequence number PDUs (CSNP) interval, use the isis csnp-interval command in interface configuration mode. To restore the default value, use the no form of this command.
isis csnp-interval seconds {level-1 | level-2}
no isis csnp-interval {level-1 | level-2}
Syntax Description
Defaults
10 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
It is very unlikely you will need to change the default value of this command.
This command applies only for the designated router (DR) for a specified interface. Only DRs send CSNP packets in order to maintain database synchronization. The CSNP interval can be configured independently for Level 1 and Level 2. This feature does not apply to serial point-to-point interfaces. It does apply to WAN connections if the WAN is viewed as a multiaccess meshed network.
For multi-access WAN interfaces (such as ATM, Frame Relay, and X.25), it is highly recommended you configure the NBMA cloud as multiple point-to-point subinterfaces. Doing so will make routing much more robust if one or more PVCs fail.
The isis csnp-interval command on point-to-point subinterfaces only makes sense when using it in combination with the IS-IS mesh-group feature.
Examples
The following example configures Ethernet interface 0 for transmitting CSN PDUs every 30 seconds.
interface ethernet 0isis csnp-interval 30 level-1isis hello-interval
To specify the length of time between hello packets that the Cisco IOS software sends, use the isis hello-interval command in interface configuration mode. To restore the default value, use the no form of this command.
isis hello-interval seconds {level-1 | level-2}
no isis hello-interval {level-1 | level-2}
no isis csnp-interval {level-1 | level-2}
Syntax Description
Defaults
10 seconds
Command Modes
Interface configuration
Command History
Usage Guidelines
The hello interval can be configured independently for Level 1 and Level 2, except on serial point-to-point interfaces. (Because there is only a single type of hello packet sent on serial links, it is independent of Level 1 or Level 2.) The level-1 and level-2 keywords are used on X.25, SMDS, and Frame Relay multiaccess networks or LAN interfaces.
A faster hello interval gives faster convergence, but increases bandwidth and CPU usage. It might also add to instability in the network. A slower hello interval saves bandwidth and CPU. Especially when used in combination with a higher hello multiplier, this may increase overall network stability.
It makes more sense to tune the hello interval and hello multiplier on point-to-point interfaces than on LAN interfaces.
Examples
The following example configures serial interface 0 to advertise hello packets every 5 seconds. The router is configured to act as a station router. This will cause more traffic than configuring a longer interval, but topological changes will be detected faster.
interface serial 0isis hello-interval 5 level-1Related Commands
Specifies the number of IS-IS hello packets a neighbor must miss before the router should declare the adjacency as down.
isis hello-multiplier
To specify the number of IS-IS hello packets a neighbor must miss before the router should declare the adjacency as down, use the isis hello-multiplier command in interface configuration mode. To restore the default value, use the no form of this command.
isis hello-multiplier multiplier {level-1 | level-2}
no isis hello-multiplier {level-1 | level-2}
Syntax Description
Defaults
multiplier is 3
Command Modes
Interface configuration
Command History
Usage Guidelines
The "holding time" carried in an IS-IS hello packet determines how long a neighbor waits for another hello packet before declaring the neighbor to be down. This time determines how quickly a failed link or neighbor is detected so that routes can be recalculated.
Use the isis hello-multiplier command in circumstances where hello packets are lost frequently and IS-IS adjacencies are failing unnecessarily. You can raise the hello multiplier and lower the hello interval (isis hello-interval command) correspondingly to make the hello protocol more reliable without increasing the time required to detect a link failure.
On point-to-point links, there is only one hello for both Level 1 and Level 2, so configuring different hello-multipliers only makes sense for multi-access networks, such as Ethernet, FDDI, etc. Separate Level 1 and Level 2 hellos are also sent over NBMA networks in multipoint mode, such as X.25, Frame Relay and ATM. However, it is recommended to run IS-IS over point-to-point subinterfaces over WAN NBMA media.
Examples
In the following example, the network administrator wants to increase network stability by making sure an adjacency will go down only when many (10) hellos are missed. The total time to detect link failure is 60 seconds. This will ensure that the network remains stable, even when the link is fully congested.
interface serial 1ip router isisisis hello-interval 6 level-1isis hello-multiplier 10 level-1Related Commands
Specifies the length of time between hello packets that the Cisco IOS software sends.
isis lsp-interval
To configure the time delay between successive IS-IS link state packet transmissions, use the isis lsp-interval command in interface configuration mode. To restore the default value, use the no form of this command.
isis lsp-interval milliseconds
no isis lsp-interval
Syntax Description
Defaults
33 milliseconds
Command Modes
Interface configuration
Command History
Usage Guidelines
In topologies with a large number of IS-IS neighbors and interfaces, a router may have difficulty with the CPU load imposed by link state packet (LSP) transmission and reception. This command allows the LSP transmission rate (and by implication the reception rate of other systems) to be reduced.
Examples
The following example causes the system to transmit LSPs every 100 milliseconds (10 packets per second) on serial interface 0:
interface serial 0isis lsp-interval 100Related Commands
Configures the time between retransmission of each LSP (IS-IS link state PDU) over point-to-point links.
isis metric
To configure the metric for an interface, use the isis metric command in interface configuration mode. To restore the default metric value, use the no form of this command.
isis metric default-metric {level-1 | level-2}
no isis metric {level-1 | level-2}
Syntax Description
Defaults
If level-1 or level-2 is not specified, level-1 is assumed.
Command Modes
Interface configuration
Command History
Usage Guidelines
Specifying the level-1 or level-2 keywords resets the metric only for Level 1 or Level 2 routing, respectively.
It is highly recommended to configure metrics on all interfaces. If you do not do so, the IS-IS metrics are similar to hop-count metrics.
Examples
The following example configures serial interface 0 for a default link-state metric cost of 15 for Level 1:
interface serial 0isis metric 15 level-1isis password
To configure the authentication password for an interface, use the isis password command in interface configuration mode. To disable authentication for IS-IS, use the no form of this command.
isis password password {level-1 | level-2}
no isis password {level-1 | level-2}
Syntax Description
Defaults
This command is disabled by default.
If no keyword is specified, the default is level-1.Command Modes
Interface configuration
Command History
Usage Guidelines
This command enables you to prevent unauthorized routers from forming adjacencies with this router, and thus protects the network from intruders.
The password is exchanged as plain text and thus provides only limited security.
Different passwords can be assigned for different routing levels using the level-1 and level-2 kewords.
Specifying the level-1 or level-2 keywords disables the password only for Level 1 or Level 2 routing, respectively.
Examples
The following example configures a password for Ethernet interface 0 at Level 1:
interface ethernet 0isis password frank level-1isis priority
To configure the priority of designated routers, use the isis priority command in interface configuration mode. To reset the default priority, use the no form of this command.
isis priority value {level-1 | level-2}
no isis priority {level-1 | level-2}
Syntax Description
value
Sets the priority of a router and is a number from 0 to 127. The default value is 64.
level-1
Sets the priority for Level 1 independently.
level-2
Sets the priority for Level 2 independently.
Defaults
Priority of 64
Command Modes
Interface configuration
Command History
Usage Guidelines
Priorities can be configured for Level 1 and Level 2 independently. Specifying the level-1 or level-2 keywords resets priority only for Level 1 or Level 2 routing, respectively.
The priority is used to determine which router on a LAN will be the designated router or Designated Intermediate System (DIS). The priorities are advertised in the hellos. The router with the highest priority will become the DIS.
In IS-IS, there is no backup designated router. Setting the priority to 0 lowers the chance of this system becoming the DIS, but does not prevent it. If a router with a higher priority comes on line, it will take over the role from the current DIS. In the case of equal priorities, the highest MAC address breaks the tie.
Examples
The following example shows Level 1 routing given priority by setting the priority level to 80. This router is now more likely to become the DIS.
interface ethernet 0isis priority 80 level-1isis retransmit-interval
To configure the time between retransmission of each LSP (IS-IS link-state PDU) over point-to-point links, use the isis retransmit-interval command in interface configuration mode. To restore the default value, use the no form of this command.
isis retransmit-interval seconds
no isis retransmit-interval seconds
Syntax Description
Defaults
5 seconds
Interface configuration
Command History
Usage Guidelines
The setting of the seconds argument should be conservative, or needless retransmission will result.
This command has no effect on LAN (multipoint) interfaces. On point-to-point links, the value can be increased to enhance network stability.
Retransmissions occur only when LSPs are dropped. So setting this to a higher value has little effect on reconvergence. The more neighbors routers have, and the more paths over which LSPs can be flooded, the higher this value can be made.
The value should be larger for serial lines.
Examples
The following example configures serial interface 0 for retransmission of IS-IS LSP, every 60 seconds for a large serial line:
interface serial 0isis retransmit-interval 60Related Commands
isis retransmit-throttle-interval
To configure the amount of time between retransmissions of any IS-IS link-state PDUs (LSPs) on a point-to-point interface, use the isis retransmit-throttle-interval command in interface configuration mode. To restore the default value, use the no form of this command.
isis retransmit-throttle-interval milliseconds
no isis lsp-interval
Syntax Description
Defaults
The delay is determined by the isis lsp-interval command.
Command Modes
Interface configuration
Command History
Usage Guidelines
This command may be useful in very large networks with many LSPs and many interfaces as a way of controlling LSP retransmission traffic. This command controls the rate at which LSPs can be retransmitted on the interface.
The isis retransmit-throttle-interval command is distinct from the rate at which LSPs are transmitted on the interface (controlled by the isis lsp-interval command) and the period between retransmissions of a single LSP (controlled by the isis retransmit-interval command). These commands may all be used in combination to control the offered load of routing traffic from one router to its neighbors.
Examples
The following example configures serial interface 0 to limit the rate of LSP retransmissions to one every 300 milliseconds:
interface serial 0isis retransmit-throttle-interval 300Related Commands
is-type
To configure the IS-IS level at which the Cisco IOS software operates, use the is-type command in router configuration mode. To reset the default value, use the no form of this command.
is-type {level-1 | level-1-2 | level-2-only}
no is-type {level-1 | level-1-2 | level-2-only}
Syntax Description
Defaults
Router acts as both a station router and an area router.
Command Modes
Router configuration
Command History
Usage Guidelines
It is highly recommended that you configure the type of an IS-IS router.
If there is only one area, there is no need to run two copies of the same algorithm. You have the option to run L1-only or L2-only everywhere. If IS-IS is used for CLNS routing, L1-only must be used everywhere. If IS-IS is used for IP routing, only, it is slightly preferred to run L2-only everywhere, as this allows easy addition of other areas later.
Examples
The following example specifies an area router:
router isisis-type level-2-onlylsp-refresh-interval (IS-IS)
To set the link-state packet (LSP) refresh interval, use the lsp-refresh-interval command in router configuration mode. To restore the default refresh interval, use the no form of this command.
lsp-refresh-interval seconds
no lsp-refresh-interval
Syntax Description
seconds
Interval (in seconds) at which LSPs are refreshed.The range is 1 to 65535 seconds. The default value is 900 seconds (15 minutes).
Defaults
900 seconds (15 minutes)
Command Modes
Router configuration
Command History
Usage Guidelines
The refresh interval determines the rate at which Cisco IOS software periodically transmits in LSPs the route topology information that it originates. This is done to keep the database information from becoming too old.
LSPs must be periodically refreshed before their lifetimes expire. The value set for the lsp-refresh-interval command should be less than the value set for the max-lsp-lifetime command; otherwise, LSPs will time out before they are refreshed. If you misconfigure the LSP lifetime to be too low compared to the LSP refresh interval, the software will reduce the LSP refresh interval to prevent the LSPs from timing out.
Reducing the refresh interval reduces the amount of time that undetected link state database corruption can persist at the cost of increased link utilization. (This is an extremely unlikely event, however, because there are other safeguards against corruption.) Increasing the interval reduces the link utilization caused by the flooding of refreshed packets (although this utilization is very small).
Examples
The following example configures the IS-IS LSP refresh interval to be 1080 seconds (18 minutes):
router isislsp-refresh-interval 1080Related Commands
Sets the maximum time that link-state packets (LSPs) can remain in a router's database without being refreshed.
max-lsp-lifetime (IS-IS)
To set the maximum time that link-state packets (LSPs) can remain in a router's database without being refreshed, use the max-lsp-lifetime command in router configuration mode. To restore the default lifetime, use the no form of this command.
max-lsp-lifetime seconds
no max-lsp-lifetime
Syntax Description
seconds
Lifetime of the LSP in seconds. The range is 1 to 65535 seconds; the default is 1200 seconds (20 minutes).
Defaults
1200 seconds (20 minutes)
Command Modes
Router configuration
Command History
Usage Guidelines
If the lifetime is exceeded before a refresh LSP arrives, the LSP is dropped from the database.
You might need to adjust the maximum LSP lifetime if you change the LSP refresh interval with the lsp-refresh-interval (IP) command. The value set for the lsp-refresh-interval command should be less than the value set for the max-lsp-lifetime command; otherwise, LSPs will time out before they are refreshed.If you misconfigure the LSP lifetime to be too low compared to the LSP refresh interval, the software will reduce the LSP refresh interval to prevent the LSPs from timing out.
You might prefer higher values for each command in order to reduce control traffic, at the expense of holding stale LSPs from a crashed or unreachable router in the database longer (thus wasting memory) or increasing the risk of undetected bad LSPs staying active (very rare).
Examples
The following example configures an LSP lifetime of 40 minutes:
router isismax-lsp-lifetime 2400Related Commands
net
To configure an IS-IS network entity title (NET) for the routing process, use the net command in router configuration mode. To remove a NET, use the no form of this command.
net network-entity-title
no net network-entity-title
Syntax Description
network-entity-title
NET that specifies the area address and the system ID for an IS-IS routing process. This argument can be either an address or a name.
Defaults
No NET is configured and the IS-IS process will not start. A NET is mandatory.
Command Modes
Router configuration
Command History
Usage Guidelines
Under most circumstances, one and only one NET must be configured.
A NET is an NSAP where the last byte is always zero. On a Cisco router running IS-IS, a NET can be 8 to 20 bytes. The last byte is always the n-selector and must be zero.
The six bytes in front of the n-selector are the system ID. The system ID length is a fixed size and cannot be changed. The system ID must be unique throughout each area (L1) and throughout the backbone (L2).
All bytes in front of the system ID are the area ID.
Even when IS-IS is used to do IP routing only (no CLNS routing enabled), a NET must still be configured. This is needed to instruct the router about its system ID and area ID.
Multiple NETs per router are allowed, with a maximum of three. In rare circumstances, it is possible to configure two or three NETs. In such a case, the area this router is in will have three area addresses. There will still be only one area, but it will have more area addresses.
Configuring multiple NETs can be temporarily useful in the case of network reconfiguration where multiple areas are merged, or where one area is in the process of being split into more areas. Multiple area addresses enable you to renumber an area slowly, without the need of a flag day.
Examples
The following example configures a router with system ID 0000.0c11.11 and area ID 47.0004.004d.0001:
router isis CHESNUTnet 47.0004.004d.0001.0000.0c11.1111.00router isis
To enable the IS-IS routing protocol and to specify an IS-IS process, use the router isis command in global configuration mode. To disable IS-IS routing, use the no form of this command.
router isis [tag]
no router isis [tag]
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Global configuration
Command History
Usage Guidelines
This command is needed to configure a NET and configure an interface with clns router isis or ip router isis.
You can specify only one IS-IS process per router. Only one IS-IS process is allowed whether you run it in integrated mode, ISO CLNS only, or IP only.
Examples
The following example configures IS-IS for IP routing, with system ID 0000.0000.0002 and area ID 01.0001, and enables IS-IS to form adjacencies on Ethernet 0 and serial 0 interfaces. The IP prefix assigned to Ethernet 0 will be advertised to other IS-IS routers:
router isis net 01.0001.0000.0000.0002.00is-type level-1!interface ethernet 0ip address 10.1.1.1 255.255.255.0ip router isis!interface serial 0ip unnumbered ethernet0ip router isisRelated Commands
set-overload-bit
To configure the router to signal other routers not to use it as intermediate hop in their SPF calculations, use the set-overload-bit command in router configuration mode. To remove the designation, use the no form of this command.
set-overload-bit
no set-overload-bit
Syntax Description
This command has no arguments or keywords.
Defaults
The overload bit is not set.
Command Modes
Router configuration
Command History
Usage Guidelines
This command forces the router to set the overload bit (also known as the hippity bit) in its non-pseudonode LSPs. Normally the setting of the overload bit is allowed only when a router runs into problems. For example, when a router is experiencing a memory shortage, it might be that the Link State database is not complete, resulting in an incomplete or inaccurate routing table. By setting the overload bit in its LSPs, other routers can ignore the unreliable router in their SPF calculations until the router has recovered from its problems.
The result will be that no paths through this router are seen by other routers in the IS-IS area. However, IP and CLNS prefixes directly connected to this router will be still be reachable.
This command can be useful when you want to connect a router to an ISIS network, but don't want real traffic flowing through it under any circumstances. Examples are:
•
A test router in the lab, connected to a production network.
•
•
Examples
The following example configures the set-overload bit:
router isisset-overload-bitshow isis database
To display the IS-IS link state database, use the show isis database command in EXEC mode.
show isis database [level-1] [level-2] [l1] [l2] [detail] [lspid]
Syntax Description
Command Modes
EXE
Command History
Usage Guidelines
Each of the options shown in brackets for this command can be entered in an arbitrary string within the same command entry. For example, the following are both valid command specifications and provide the same output: show isis database detail l2 and show isis database l2 detail.
Examples
The following is sample output from the show isis database command when it is specified with no options or as show isis database:
Router# show isis databaseIS-IS Level-1 Link State DatabaseLSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL0000.0C00.0C35.00-00 0x0000000C 0x5696 792 0/0/00000.0C00.40AF.00-00* 0x00000009 0x8452 1077 1/0/00000.0C00.62E6.00-00 0x0000000A 0x38E7 383 0/0/00000.0C00.62E6.03-00 0x00000006 0x82BC 384 0/0/00800.2B16.24EA.00-00 0x00001D9F 0x8864 1188 1/0/00800.2B16.24EA.01-00 0x00001E36 0x0935 1198 1/0/0IS-IS Level-2 Link State DatabaseLSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL0000.0C00.0C35.03-00 0x00000005 0x04C8 792 0/0/00000.0C00.3E51.00-00 0x00000007 0xAF96 758 0/0/00000.0C00.40AF.00-00* 0x0000000A 0x3AA9 1077 0/0/0Table 35 describes significant fields shown in the display
.
Example Using Show IS-IS Database Detail
The following is sample output from the show isis database detail command.
Router# show isis database detailIS-IS Level-1 Link State DatabaseLSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL0000.0C00.0C35.00-00 0x0000000C 0x5696 325 0/0/0Area Address: 47.0004.004D.0001Area Address: 39.0001Metric: 10 IS 0000.0C00.62E6.03Metric: 0 ES 0000.0C00.0C35--More--0000.0C00.40AF.00-00* 0x00000009 0x8452 608 1/0/0Area Address: 47.0004.004D.0001Metric: 10 IS 0800.2B16.24EA.01Metric: 10 IS 0000.0C00.62E6.03Metric: 0 ES 0000.0C00.40AFIS-IS Level-2 Link State DatabaseLSPID LSP Seq Num LSP Checksum LSP Holdtime ATT/P/OL0000.0C00.0C35.03-00 0x00000005 0x04C8 317 0/0/0Metric: 0 IS 0000.0C00.0C35.00--More--0000.0C00.3E51.00-00 0x00000009 0xAB98 1182 0/0/0Area Address: 39.0004