ISIS Network Best Practice using 3 Platforms over CISCO

[jorgemartinez]

Hello there, I will like to know if some of you can share a Best practice using 3 different platforms (Alcatel, Nortel and Siemens) over a Cisco ISIS Network. Right now we are using that scenario, but we are having a lot of issues trying to add more elements (nodes) to the ISIS Network ...

- The Network has all three NETs over a single area, here's an example

router isis Alcatel-Nortel

net 47.0005.8000.0000.0000.0001.0001.0050.534a.aaff.00

net 49.0001.0050.534a.aaff.00

is-type level-1

log-adjacency-changes

!

router isis Siemens

net 47.0099.0548.4000.0100.0000.0100.0050.534a.aaff.00

is-type level-1

log-adjacency-changes

And I have these is applied to two LANs

Any help, will be a lot appreciated

[a-vazquez]

There is no seperate configuration for different platforms.Make sure Area ID and IS-type matches.Refer the following URL for configuring IS-IS http://www.cisco.com/warp/public/97/is-is-ip-config.html.

[mheusinger]

Hi,

I am not sure about your statement "single area". To my knowledge ISIS area is the same on two devices, when the network portion of the NSAP (NET) address is the same.

If different NET addresses need to be connected then a Level2 router is needed.

So can you try to remove "is-type level-1" from your config? The router will then be Level1 as well as Level2 router and should be able to route between different areas.

Also, why do you have two ISIS processes started?

You could try to use the following config to interconnect all areas:

clns routing

router isis all

net 47.0005.8000.0000.0000.0001.0001.0050.534a.aaff.00

net 49.0001.0050.534a.aaff.00

net 47.0099.0548.4000.0100.0000.0100.0050.534a.aaff.00

interface FastEthernet0/0

clns router isis all

You need to adjust this to your interfaces.

Hope this helps! Please rate all posts.

Regards, Martin