I was thinking maybe it has something to do with the propagation of L2 broadcasts but it appears that the ISIS-all-level-1-ISs and ISIS-all-level-2-ISs are used regardless of whether the circuit is configured as p2p or left as b-cast
The two way communication is formed whe you se your own ID in the the IS Neighbor TLV-6 in the IIH adam -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Walter Keen Sent: Saturday, May 28, 2011 2:39 AM To: [email protected] Subject: [c-nsp] IS-IS on L3 vlan interfaces I'm having some trouble getting (integraded) IS-IS to form an adjacency over a L3 vlan that has 3 routers in it. It's on a Cisco 7600 series with 12.2(33)SRE code, however if I configure the vlan interface with the network type point-to-point, it comes up as expected. Since they all have dot1q trunks to a metro ethernet provider, I could certainly make vlans to form point to point connections to all of them, but I don't really want to unless I have to. Does anyone have experience with this sort of issue? I get as far as, with debug isis adj, I can see router A send packets, and B/C (all in the same ethernet segment/broadcast domain) receive it and transmit packets, presumabely in response, but A 's debug never indicates receiving an isis packet. isis and clns neighbor state on B and C get stuck in INIT _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
