[c-nsp] ISIS parallel P2P adjacency over tunnel

[Shiraz]

Hi all,

 

I'm running ISIS on an E3 link (only L2 adjacency) between two Cisco 7206
boxes (acting as L1/L2 IS). Things are pretty fine and traffic is moving.
Recently I created 2 tunnels out of the boxes to each other via their
upstream providers (as backup of the P2P E3 circuit) Tunnels are up and
running, however I'm unable to establish parallel/simultaneous ISIS L2
adjacency between the boxes over the tunnels.

 

I get the following message when I run "sh clns neighbor detail" on 1 box:

 

-----------------------------------------------------------------------

gwi          Tu51        <ip address>      Up     27        L2   IS-IS

  Area Address(es): 49.0051

  IP Address(es):  <ip address of remote tunnel interface>*

  Uptime: 03:38:40

  NSF capable

  IP parallel adjacency suppressed

gwi          Se2/1       *HDLC*              Up     27        L2   IS-IS

  Area Address(es): 49.0051

  IP Address(es):  <ip address of remote E3 interface>*

  Uptime: 1d00h

  NSF capable

  IPv6 parallel adjacency suppressed

----------------------------------------

 

 

Since I'm not running IPv6 on these boxes, I can just ignore the v6 message.
However, I do need to establish parallel adjacency on the tunnel besides the
E3 link.

 

Please also note that I'm not trying to load share traffic over E3 link and
tunnels. I'm using "isis metric 110 level-2" in tunnel configuration at both
ends. How can I ensure that all ISIS routes are available via tunnel as well
with metric 110 (+10 for every IS) all the time. I've also seen few docs
which say that only best adjacency will be reported...?

 

Any comments/help?

 

Thanks.

 

 

 

--

Shiraz Anjum Malik