From: Kevin Baumgartner (kbaumgar@xxxxxxxxx)
Date: Tue Jan 30 2001 - 00:40:00 GMT-3
Actually that's not totally true. Depends what type of interface is
on the other side of the framerelay link.
For ISIS there are just two broadcast types.
Broadcast - This is for physical interfaces (no subinterfaces)
and also includes Multipoint interfaces.
Point-to-Point - Point-to-Point subinterfaces, and also
PPP and HDLC interfaces.
So if had a multipoint interface connected to a physical interface
no problem. Both are ISIS Broadcast types.
However if a multipoint interface is connected to a point-to-point
interface, this is a problem. Broadcast type to Point-to-Point type.
So need to convert multipoint interface to point-to-point, or convert
point-to-point to physical.
Kevin
>
> Yes, I think ISIS will not work on multipoint interfaces. You have use point
> to point.
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> Robert DeVito
> Sent: Tuesday, January 30, 2001 2:10 AM
> To: abasinge@swbell.net; ccielab@groupstudy.com
> Subject: RE:ISIS cciebootcamp lab #17
>
>
> I beleive you have two options,
>
>
> 1.) add "frame-relay map clns" commands (never tried, but heard it works)
> 2.) you point-to-point sub interfaces.
>
> I hope this helps, let me know if you have any luck with #1
>
> Cheers,
> Robert
>
>
> ----Original Message Follows----
> From: Alan Basinger <abasinge@swbell.net>
> Reply-To: Alan Basinger <abasinge@swbell.net>
> To: Ccielab <ccielab@groupstudy.com>
> Subject: RE:ISIS cciebootcamp lab #17
> Date: Mon, 29 Jan 2001 18:32:00 -0600
>
> Hi all,
> I am having an issue with getting ISIS operational in the lab. Between
> router 14 and router 5 over a frame link we are supposed to run ISIS type 1.
> I have the link up frame map shows good and can ping the line. I configure
> bother routers with the command "router isis" use a net number of
> 49.0001.7777.7777.7777.00 on 14 and 49.0001.5555.5555.5555.00 on router 5. I
> then configure the interface with "ip router isis" on the appropriate
> interfaces and loopbacks. No luck no isis routes in my routing table. I then
> added type 1 and 2 support to the config no luck. So I do a debug isis adj
> on r 14 and see it is sending a request for adj but does not get a reply. So
> I go to r5 and do the same and now I see something much worse.
>
> 02:49:47: ISIS-Adj: rcvd state DOWN, old state INIT, new state INIT
> 02:49:47: ISIS-Adj: Action = GOING UP, new type = L1L2
> 02:49:48: ISIS-Adj: Encapsulation failed for level 1 IIH on Serial0/0
> 02:49:50: ISIS-Adj: Encapsulation failed for level 2 IIH on Serial0/0
> 02:49:50: ISIS-Adj: Encapsulation failed for level 1 IIH on Serial0/0
> 02:49:52: ISIS-Adj: Sending L1 IIH on Loopback0
> 02:49:53: ISIS-Adj: Encapsulation failed for level 2 IIH on Serial0/0
> 02:49:53: ISIS-Adj: Encapsulation failed for level 1 IIH on Serial0/0
> 02:49:54: ISIS-Adj: Sending L2 IIH on Loopback0
> 02:49:56: ISIS-Adj: Encapsulation failed for level 2 IIH on Serial0/0
> 02:49:56: ISIS-Adj: Rec serial IIH from DLCI 105 (Serial0/0), cir type L1L2,
> cir
> id 00
>
> My router is having encapsulation failures and the link is flapping but only
> for ISIS. I enable eigrp on the link on both ends and viola it works fine
> but still no ISIS.
>
> Please look at the configs and see if you can spot the issue???
>
> Regards,
>
> Alan Basinger
> Systems Engineer
> SBC DataComm
> Houston Texas
> abasinge@swbell.net
>
> | |
> ||| |||
> .|||||. .|||||.
> .:|||||||||:.:|||||||||:.
> C i s c o S y s t e m s
> Certified Gold Partner
>
>
>
> Current configuration:
> !
> version 12.0
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname r5
> !
> logging buffered 4096 debugging
> enable secret 5 $1$vf3N$7F8tFRZCDERvvrQjqh2jA.
> !
> memory-size iomem 20
> ip subnet-zero
> no ip domain-lookup
> !
> clns routing
> isdn switch-type basic-ni
> !
> !
> interface Loopback0
> ip address 15.15.5.5 255.255.255.0
> no ip directed-broadcast
> ip router isis
> !
> interface Ethernet0/0
> no ip address
> no ip directed-broadcast
> shutdown
> !
> interface Serial0/0
> ip address 10.1.12.194 255.255.255.240
> no ip directed-broadcast
> ip router isis
> encapsulation frame-relay
> no ip mroute-cache
> no fair-queue
> frame-relay map ip 10.1.12.193 105 broadcast
> frame-relay map ip 10.1.12.194 105 broadcast
> no frame-relay inverse-arp
> frame-relay lmi-type ansi
> !
> interface BRI0/0
> ip address 10.1.35.5 255.255.255.252
> no ip directed-broadcast
> encapsulation ppp
> dialer map ip 10.1.35.6 name r6 broadcast 8358661
> dialer map ip 10.1.35.6 name r6 broadcast 8358663
> dialer-group 1
> isdn switch-type basic-ni
> isdn spid1 0835866201 8358662
> isdn spid2 0835866401 8358664
> ppp multilink
> !
> router eigrp 5
> passive-interface BRI0/0
> network 10.0.0.0
> no auto-summary
> !
> router ospf 5
> network 10.1.35.0 0.0.0.255 area 5
> !
> router isis
> net 49.0001.5555.5555.5555.00
> log-adjacency-changes
> !
> ip classless
> no ip http server
> !
> dialer-list 1 protocol ip permit
> !
> alias exec s show ip route
> alias exec sx sh ipx route
> alias exec so sh ip ospf
> alias exec son sh ip ospf nei
> alias exec sb sh ip bgp
> alias exec sbn sh ip bgp nei
> alias exec w wr mem
> alias exec r sh run
> alias exec u undebug all
> alias exec ct config t
> alias exec cb clear ip bgp *
> alias exec c clear ip route *
> !
> line con 0
> exec-timeout 0 0
> login
> transport input none
> line aux 0
> line vty 0 4
> exec-timeout 0 0
> password cisco
> login
> !
> no scheduler allocate
> end
>
> r5#
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:48 GMT-3