Your config is wrong - notice there are two mappings for each one. example: 2:204 = 4:402 4:402 = 2:204
5:506 = 6:605 6:605 = 5:506 1:215 = 5:512 5:512 = 1:215 5:516 = 6:615 6:612 = 1:216 6:615 = 5:516 However only 5 and 6 will work since these are the ones that are mapped in your .net file. so to correct 1:215 = 5:512 should be 2:215 = 5:512 and 5:512 = 1:215 should be 5:512 = 2:215 On Thu, Aug 13, 2009 at 2:10 PM, Tahir Bashir <[email protected]>wrote: > > > > Attached is the correct snap of Frame Relay configuration. > > > > ------------------------------ > From: [email protected] > To: [email protected] > Date: Thu, 13 Aug 2009 23:59:09 +0600 > CC: [email protected] > Subject: Re: [OSL | CCIE_RS] Frame Relay Problem > > Hi Bryan, Following is the complete configuration of Routers, > > > > *Hub Router R2* > > interface Serial1/0 > ip address 100.100.100.2 255.255.255.0 > encapsulation frame-relay > serial restart-delay 0 > frame-relay map ip 100.100.100.2 204 > frame-relay map ip 100.100.100.4 204 broadcast > frame-relay map ip 100.100.100.5 205 broadcast > frame-relay map ip 100.100.100.6 206 broadcast > no frame-relay inverse-arp > ! > interface Serial1/0.110 multipoint > ip address 100.100.110.2 255.255.255.0 > frame-relay map ip 100.100.110.2 215 > frame-relay map ip 100.100.110.5 215 broadcast > frame-relay map ip 100.100.110.6 216 broadcast > ! > > *Spoke Router R4* > interface Serial1/0 > ip address 100.100.100.4 255.255.255.0 > encapsulation frame-relay > serial restart-delay 0 > frame-relay map ip 100.100.100.2 402 broadcast > frame-relay map ip 100.100.100.4 402 > frame-relay map ip 100.100.100.5 402 > frame-relay map ip 100.100.100.6 402 > no frame-relay inverse-arp > ! > > *Spoke Router R5* > > interface Serial1/0 > ip address 100.100.100.5 255.255.255.0 > encapsulation frame-relay > serial restart-delay 0 > frame-relay map ip 100.100.100.2 502 broadcast > frame-relay map ip 100.100.100.4 502 > frame-relay map ip 100.100.100.5 502 > frame-relay map ip 100.100.100.6 502 > no frame-relay inverse-arp > ! > interface Serial1/0.110 multipoint > ip address 100.100.110.5 255.255.255.0 > frame-relay map ip 100.100.110.2 512 broadcast > frame-relay map ip 100.100.110.5 512 > frame-relay map ip 100.100.110.6 512 > no frame-relay inverse-arp > ! > > *Spoke Router R6* > > interface Serial1/0 > ip address 100.100.100.6 255.255.255.0 > encapsulation frame-relay > serial restart-delay 0 > frame-relay map ip 100.100.100.2 602 broadcast > frame-relay map ip 100.100.100.4 602 > frame-relay map ip 100.100.100.5 602 > frame-relay map ip 100.100.100.6 602 > no frame-relay inverse-arp > ! > interface Serial1/0.110 multipoint > ip address 100.100.110.6 255.255.255.0 > frame-relay map ip 100.100.110.2 612 broadcast > frame-relay map ip 100.100.110.5 612 > frame-relay map ip 100.100.110.6 612 > ! > > > Note: R4 Router is not participating in second subnet i.e. > 100.100.110.0/24. For subnet 100.100.100.0/24 evrything is working pretty > gud. but not for subnet 100.100.110.0/24. R2 (HUB), R5 & R6 (SPOKE) for > subnet 100.100.110.0/24. > > Following is the output of some usefull commands, > ** > *Hub R2* > R2# sh fr pvc | inc DLCI > DLCI = 204, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0 > DLCI = 205, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0 > DLCI = 206, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0 > *DLCI = 215, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE = > Serial1/0.110 > DLCI = 216, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE = > Serial1/0.110* > > R2#sh fr map > Serial1/0 (up): ip 100.100.100.2 dlci 204(0xCC,0x30C0), static, > CISCO, status defined, active > Serial1/0 (up): ip 100.100.100.4 dlci 204(0xCC,0x30C0), static, > broadcast, > CISCO, status defined, active > Serial1/0 (up): ip 100.100.100.5 dlci 205(0xCD,0x30D0), static, > broadcast, > CISCO, status defined, active > Serial1/0 (up): ip 100.100.100.6 dlci 206(0xCE,0x30E0), static, > broadcast, > CISCO, status defined, active > *Serial1/0.110 (down): ip 100.100.110.2 dlci 215(0xD7,0x3470), static, > CISCO, status deleted > Serial1/0.110 (down): ip 100.100.110.5 dlci 215(0xD7,0x3470), static, > broadcast, > CISCO, status deleted > Serial1/0.110 (down): ip 100.100.110.6 dlci 216(0xD8,0x3480), static, > broadcast, > CISCO, status deleted* > > R2#sh ip int br > Interface IP-Address OK? Method Status > Prot > ocol > FastEthernet0/0 unassigned YES NVRAM administratively down > down > *Serial1/0 100.100.100.2 YES NVRAM > up up* > *Serial1/0.110 100.100.110.2 YES NVRAM down > down* > Serial1/1 unassigned YES NVRAM administratively down > down > Serial1/2 unassigned YES NVRAM administratively down > down > Serial1/3 unassigned YES NVRAM administratively down > down > Serial1/4 unassigned YES NVRAM administratively down > down > Serial1/5 unassigned YES NVRAM administratively down > down > Serial1/6 unassigned YES NVRAM administratively down > down > Serial1/7 unassigned YES NVRAM administratively down > down > > > *Spoke Router R5* > > R5#show fr pvc | inc DLCI > DLCI = 502, DLCI USAGE = LOCAL, PVC STATUS = ACTIVE, INTERFACE = Serial1/0 > DLCI = 512, DLCI USAGE = LOCAL, PVC STATUS = DELETED, INTERFACE = > Serial1/0.110 > > R5#show ip int b > Interface IP-Address OK? Method Status > Prot > ocol > FastEthernet0/0 unassigned YES NVRAM administratively down > down > *Serial1/0 100.100.100.5 YES NVRAM > up up* > *Serial1/0.110 100.100.110.5 YES NVRAM > down down* > Serial1/1 unassigned YES NVRAM administratively down > down > Serial1/2 unassigned YES NVRAM administratively down > down > Serial1/3 unassigned YES NVRAM administratively down > down > Serial1/4 unassigned YES NVRAM administratively down > down > Serial1/5 unassigned YES NVRAM administratively down > down > Serial1/6 unassigned YES NVRAM administratively down > down > Serial1/7 unassigned YES NVRAM administratively down > down > > R5#show fr map > Serial1/0 (up): ip 100.100.100.2 dlci 502(0x1F6,0x7C60), static, > broadcast, > CISCO, status defined, active > Serial1/0 (up): ip 100.100.100.4 dlci 502(0x1F6,0x7C60), static, > CISCO, status defined, active > Serial1/0 (up): ip 100.100.100.5 dlci 502(0x1F6,0x7C60), static, > CISCO, status defined, active > Serial1/0 (up): ip 100.100.100.6 dlci 502(0x1F6,0x7C60), static, > CISCO, status defined, active > Serial1/0.110 (down): ip 100.100.110.2 dlci 512(0x200,0x8000), static, > broadcast, > CISCO, status deleted > Serial1/0.110 (down): ip 100.100.110.5 dlci 512(0x200,0x8000), static, > CISCO, status deleted > Serial1/0.110 (down): ip 100.100.110.6 dlci 512(0x200,0x8000), static, > CISCO, status deleted > > Note: Router 6 situation is same as Router R5 > GNS3 configuration of Frame-Relay switch is attached please find attached > file. thanks all of you for nice support. > > > > Regards, > Tahir > ------------------------------ > Date: Thu, 13 Aug 2009 11:07:18 -0600 > Subject: Re: [OSL | CCIE_RS] Frame Relay Problem > From: [email protected] > To: [email protected] > CC: [email protected] > > Hi Tahir, > > I am more familiar with dynagen than GNS3, but in the first example you use > DLCIs 204,205,206, etc. In the second example you are using 214,215,216...do > you have these DLCIs mapped out properly in the GNS3 frame-switch? Do you > have a .net file we could look at? > > Thanks, > > > > On Thu, Aug 13, 2009 at 9:36 AM, Tahir Bashir <[email protected]>wrote: > > > > Hi All, > > > > I have designed a frame relay archetecture on GNS3. with the following > configuration, > > > > R2 > int s1/0 > ip address 100.100.100.2 255.255.255.0 > encap fr > no fr inv > fr map ip 100.100.100.4 204 broad > fr map ip 100.100.100.5 205 broad > fr map ip 100.100.100.6 206 broad > fr map ip 100.100.100.2 204 > no shut > > R4 > int s1/0 > ip address 100.100.100.4 255.255.255.0 > encap fr > no fr inv > fr map ip 100.100.100.2 402 broad > fr map ip 100.100.100.5 402 > fr map ip 100.100.100.6 402 > fr map ip 100.100.100.4 402 > no shut > R5 > int s1/0 > ip address 100.100.100.5 255.255.255.0 > encap fr > no fr inv > fr map ip 100.100.100.2 502 broad > fr map ip 100.100.100.4 502 > fr map ip 100.100.100.5 502 > fr map ip 100.100.100.6 502 > no shut > > R6 > int s1/0 > ip address 100.100.100.6 255.255.255.0 > encap fr > no fr inv > fr map ip 100.100.100.2 602 broad > fr map ip 100.100.100.4 602 > fr map ip 100.100.100.5 602 > fr map ip 100.100.100.6 602 > no shut > ------------------ For Blue Line in IPExpert Exercise > R2 > int s1/0.110 multipoint > ip add 100.100.110.2 255.255.255.0 > fr map ip 100.100.110.5 215 broad > fr map ip 100.100.110.6 216 broad > fr map ip 100.100.110.2 215 > > R5 > int s1/0.110 multipoint > ip add 100.100.110.5 255.255.255.0 > fr map ip 100.100.110.5 512 > fr map ip 100.100.110.6 512 > fr map ip 100.100.110.2 512 broad > > R6 > int s1/0.110 multipoint > ip add 100.100.110.6 255.255.255.0 > fr map ip 100.100.110.5 612 > fr map ip 100.100.110.6 612 > fr map ip 100.100.110.2 612 broad > > > > > Note: R2 is Hub and remaining two are spokes. With Physical interface its > working pretty gud but with subinterface it is showing that Subinterface is > down. Advance thanks for help. > > > > Regards, > > Tahir > > > > ------------------------------ > See all the ways you can stay connected to friends and > family<http://www.microsoft.com/windows/windowslive/default.aspx> > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > > > > > -- > Bryan Bartik > CCIE #23707 (R&S), CCNP > Sr. Support Engineer - IPexpert, Inc. > URL: http://www.IPexpert.com <http://www.ipexpert.com/> > > ------------------------------ > See all the ways you can stay connected to friends and > family<http://www.microsoft.com/windows/windowslive/default.aspx> > ------------------------------ > What can you do with the new Windows Live? Find > out<http://www.microsoft.com/windows/windowslive/default.aspx> > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com > >
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
