RE: Sanity Check - Redistributing BGP into an IGP [7:66018]
Hi Chuck, I don't know what scenario you are working on, so its hard to give a specific answer. It might be that you ran into the issue that by default I-BGP learned routes are NOT redistributed unless you use the command below. (E-BGP routes are redistributed without it !!) bgp redistribute-internal To allow the redistribution of internal Border Gateway Protocol (iBGP) routes into an Interior Gateway Protocol (IGP) such as Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF), use the bgp redistribute-internal command in address family configuration mode. To restore the system to the default condition, use the no form of this command. bgp redistribute-internal no bgp redistribute-internal But this also needed for EIGRP, so it might not apply to your scenario as you say that it works with EIGRP. Cheers, Willy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of The Long and Winding Road Sent: zondag 23 maart 2003 8:38 To: [EMAIL PROTECTED] Subject: Sanity Check - Redistributing BGP into an IGP [7:66018] Yes I know it's not a bright idea ;- I'm working on a practice lab which appears to me to be poorly written. Some of the solutions are out of left field, but I suppose that's to be expected of CCIE practice labs. Question - redistribution of BGP into OSPF? Problematic? Impossible on a Cisco router? I checked TAC and found the docs on OSPF into BGP writings. But nothing the other way around. I am unable to successfully redistribute BGP into OSPF, although it works just fine if I redistribute BGP into EIGRP, for example. The command takes. All the proper switches are there. But no route in OSPF or in the OSPF database. Incidentally, the book solution to this lab is to manually place the particular interface into the OSPF process with a network statement, in addition to placing it manually into the BGP process with a network / mask statement. What am I missing that I can't seem to find on TAC? Thanks. -- TANSTAAFL there ain't no such thing as a free lunch Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=66024t=66018 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Sanity Check - Redistributing BGP into an IGP [7:66018]
Hi Chuck, The command does work on 2500's, I used IOS 12.2(13)T. I did a clear ip bgp when using the command. bb#sh ver Cisco Internetwork Operating System Software IOS (tm) 2500 Software (C2500-IS-L), Version 12.2(13)T, RELEASE SOFTWARE (fc1) TAC Support: http://www.cisco.com/tac Copyright (c) 1986-2002 by cisco Systems, Inc. Compiled Sat 16-Nov-02 07:47 by ccai Image text-base: 0x0307A6E8, data-base: 0x1000 ROM: System Bootstrap, Version 5.2(8a), RELEASE SOFTWARE BOOTLDR: 3000 Bootstrap Software (IGS-RXBOOT), Version 10.2(8a), RELEASE SOFTWARE (fc1) bb uptime is 15 hours, 0 minutes System returned to ROM by power-on System image file is flash:/c2500-is-l.122-13.T cisco 2511 (68030) processor (revision L) with 14336K/2048K bytes of memory. Processor board ID 02361575, with hardware revision Bridging software. X.25 software, Version 3.0.0. 1 Ethernet/IEEE 802.3 interface(s) 2 Serial network interface(s) 16 terminal line(s) 32K bytes of non-volatile configuration memory. 16384K bytes of processor board System flash (Read ONLY) Cheers, Willy -Original Message- From: Willy Schoots [mailto:[EMAIL PROTECTED] Sent: zondag 23 maart 2003 12:30 To: 'The Long and Winding Road'; '[EMAIL PROTECTED]' Subject: RE: Sanity Check - Redistributing BGP into an IGP [7:66018] Hi Chuck, I don't know what scenario you are working on, so its hard to give a specific answer. It might be that you ran into the issue that by default I-BGP learned routes are NOT redistributed unless you use the command below. (E-BGP routes are redistributed without it !!) bgp redistribute-internal To allow the redistribution of internal Border Gateway Protocol (iBGP) routes into an Interior Gateway Protocol (IGP) such as Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF), use the bgp redistribute-internal command in address family configuration mode. To restore the system to the default condition, use the no form of this command. bgp redistribute-internal no bgp redistribute-internal But this also needed for EIGRP, so it might not apply to your scenario as you say that it works with EIGRP. Cheers, Willy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of The Long and Winding Road Sent: zondag 23 maart 2003 8:38 To: [EMAIL PROTECTED] Subject: Sanity Check - Redistributing BGP into an IGP [7:66018] Yes I know it's not a bright idea ;- I'm working on a practice lab which appears to me to be poorly written. Some of the solutions are out of left field, but I suppose that's to be expected of CCIE practice labs. Question - redistribution of BGP into OSPF? Problematic? Impossible on a Cisco router? I checked TAC and found the docs on OSPF into BGP writings. But nothing the other way around. I am unable to successfully redistribute BGP into OSPF, although it works just fine if I redistribute BGP into EIGRP, for example. The command takes. All the proper switches are there. But no route in OSPF or in the OSPF database. Incidentally, the book solution to this lab is to manually place the particular interface into the OSPF process with a network statement, in addition to placing it manually into the BGP process with a network / mask statement. What am I missing that I can't seem to find on TAC? Thanks. -- TANSTAAFL there ain't no such thing as a free lunch Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=66037t=66018 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: EIGRP for CCIE Written [7:64707]
Maybe the fact that EIGRP has an option to turn SPLIT HORIZON on/off is a big clue towards it being a DV protocol. Last time I checked OSPF/ISIS didn't have this option ;-) Cheers, Willy -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of The Long and Winding Road Sent: vrijdag 7 maart 2003 16:54 To: [EMAIL PROTECTED] Subject: Re: EIGRP for CCIE Written [7:64707] Peter van Oene wrote in message news:[EMAIL PROTECTED] At 12:11 PM 3/7/2003 +, Johan Bornman wrote: Is EIGRP a Hybrid or Distance Vector protocol? Cisco calls it Hybrid. It looks pretty distance vector to me though. in what way? the hop count is pretty well hidden in the dark interior of the code. all those cost numbers, the ( also somewhat hidden ) topology table, and the ( somewaht hidden ) successor table certainly give it the appearance of link state. Chuck who considers all this stuff a kind of magic A hello mechanism and adjacencies does not a link state one make. Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=64729t=64707 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: MPLS Vs EIGRP [7:54507]
Hi, The question should be what you want to do with MPLS, so what is the reason you want to implement MPLS in the first place. - MPLS VPN's: EIGRP could be used - Make core BGP free: EIGRP can be used - MPLS Traffic Engineering: EIGRP can NOT be used, only OSPF/ISIS For the first 2 you could use EIGRP. The discussion then would be how EIGRP compares to OSPF/ISIS in your network. Normal items like scalability, stability etc are then your decision criteria. If MPLS VPNs are your main reason for using MPLS, you might want to look at the supported routing protocols between the PE-CE. At this point, afaik, EIGRP is not yet available. It is on the roadmap but not yet available. For MPLS Traffic engineering (TE) the only option is a link state protocol. This is because they give complete visibility into (parts) of the network. Both ISIS and OSPF have extensions that make them MPLS TE capable. Cheers, Willy Schoots -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Kohli, Jaspreet Sent: maandag 30 september 2002 2:16 To: [EMAIL PROTECTED] Subject: MPLS Vs EIGRP [7:54507] I am looking for a comparative design question: Why a large corporation should or should not use MPLS over EIGRP . Any useful links will be greatly appreciated . Thanks as always Jaspreet _ Consultant Andrew NZ Inc Box 50 691, Porirua Wellington 6230, New Zealand Phone +64 4 238 0723 Fax +64 4 238 0701 e-mail [EMAIL PROTECTED] WARNING: The contents of this e-mail and any attached files may contain information that is legally privileged and/or confidential to the named recipient. This information is not to be used by any other person and/or organisation. The views expressed in this document do not necessarily reflect those of Andrew NZ Inc If you have received this e-mail and any attached files in error please notify the sender by reply e-mail and destroy your copy of this message. Thank you. This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately and delete the original. Any unauthorized use of this email is prohibited. Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=54530t=54507 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: HSRP running states.... [7:14074]
Hi Mark, There is actually an RFC about HSRP it is RFC2281: http://www.ietf.org/rfc/rfc2281.txt?number=2281 From this RFC, this might clear most of your confusion: + If the virtual IP address is configured, set state 3 (Listen) If the virtual IP address is not configured, set state 2 (Learn). Look at the RFC for all the details. Willy Schoots -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mark Odette II Sent: Sunday, July 29, 2001 11:08 AM To: [EMAIL PROTECTED] Subject: HSRP running states [7:14074] Howard, Priscilla, et al.- I'm working on knocking out the BCMSN exam, and am re-covering HSRP -(which I have read many on this list to state that it probably won't hardly be on the test, but I don't care) Here's my delima I'm a logical thinker, and going over the 6 different states of HSRP, I find myself asking WHY about a specific statement made in all the study materials... the WHY is about the following. Taken from Sybex Switching Study Guide, Pg 314, it explains the 6 states in simple terms. Specifically, it says the router enters the Learn state when it has not heard from the Active router... this part I can accept, and it makes since. It continues to say It does not know the active router [which still makes since, since it hasn't heard from it yet] and does not know the IP of the Virtual Router. The second half of this last statement is what I don't understand. When configuring HSRP, you configure on the Interface (ex: FastEthernet 0/0) [Standby] -- HSRP [1] -- HSRP Group assignment id, which is also optional [IP 10.1.0.200] -- Virtual Router ip address. If you specify the VR IP address, why on earth does the router NOT know the VR IP address in the Learn State. Does it simply ignore this config parameter when initializing HSRP and only reference it when it A) finds itself to be the first one to be Active router after already going through all the other states, or B) When it finds itself to be next in line (because of priority) when the Active router disappears for longer than the hello/holdtime interval, and it suddenly experiences amnesia and has to look at its own config to go 'Oh yeah, Everybody, I'm now the active router for... uh... let see. oh, right, virtual router 10.1.0.200... got it!' I guess my logic failure is in that I don't see anything about when the VR IP Addr part of the config statement is referenced, if in fact the way the whole group gets together and decides on who's big man on campus is from hello messages with elections being dependent upon Priority specs. Reading the definition of the next state in the process eludes to the understanding that it learns of both the active router's address and the virtual router's address from the hello message. Is this a human error on my part in that it appears to be an assumption I'm making?? Since this is a Cisco Protocol, is there an RFC on it that I could reference for my clarification needs?? Thanks, Mark Odette II Message Posted at: http://www.groupstudy.com/form/read.php?f=7i=14076t=14074 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Can anyone clarify the difference of these two?
There is a difference as not both the source and destination port are the same. Lets say Station A wants to telnet to station B: Source port A: 1024Destination Port: 23 (telnet) So to come back to your access-lists it DOES make a difference. See this partial trace below: Station A: 192.168.1.1 Station B: 192.168.1.22 In the trace you will see the 3-way handshake (Frame 1-3) and after that you will see the Telnet negotiation starting - - - - - - - - - - - - - - - - - - - - Frame 1 - - - - - - - - - - - - - - - - - - - - Frame Status Source AddressDest. Address Size Rel. Time Delta TimeAbs. Time Summary 1 M [192.168.1.1] [192.168.1.22] 60 0:00:00.000 0.000.000 03/02/2001 08:48:19 AM TCP: D=23 S=2909 SYN SEQ=11781196 LEN=0 WIN=8192 DLC: - DLC Header - DLC: DLC: Frame 1 arrived at 08:48:19.6300; frame size is 60 (003C hex) bytes. DLC: Destination = Station Cisco14A4BFA DLC: Source = Station NGC 0DD6BC DLC: Ethertype = 0800 (IP) DLC: IP: - IP Header - IP: IP: Version = 4, header length = 20 bytes IP: Type of service = 00 IP: 000. = routine IP: ...0 = normal delay IP: 0... = normal throughput IP: .0.. = normal reliability IP: ..0. = ECT bit - transport protocol will ignore the CE bit IP: ...0 = CE bit - no congestion IP: Total length= 44 bytes IP: Identification = 65107 IP: Flags = 4X IP: .1.. = don't fragment IP: ..0. = last fragment IP: Fragment offset = 0 bytes IP: Time to live= 128 seconds/hops IP: Protocol= 6 (TCP) IP: Header checksum = 7910 (correct) IP: Source address = [192.168.1.1] IP: Destination address = [192.168.1.22] IP: No options IP: TCP: - TCP header - TCP: TCP: Source port = 2909 TCP: Destination port= 23 (Telnet) TCP: Initial sequence number = 11781196 TCP: Next expected Seq number= 11781197 TCP: Data offset = 24 bytes TCP: Flags = 02 TCP: ..0. = (No urgent pointer) TCP: ...0 = (No acknowledgment) TCP: 0... = (No push) TCP: .0.. = (No reset) TCP: ..1. = SYN TCP: ...0 = (No FIN) TCP: Window = 8192 TCP: Checksum= 244B (correct) TCP: TCP: Options follow TCP: Maximum segment size = 1460 TCP: - - - - - - - - - - - - - - - - - - - - Frame 2 - - - - - - - - - - - - - - - - - - - - Frame Status Source AddressDest. Address Size Rel. Time Delta TimeAbs. Time Summary 2[192.168.1.22][192.168.1.1]60 0:00:00.008 0.008.408 03/02/2001 08:48:19 AM TCP: D=2909 S=23 SYN ACK=11781197 SEQ=1056999666 LEN=0 WIN=4128 DLC: - DLC Header - DLC: DLC: Frame 2 arrived at 08:48:19.6384; frame size is 60 (003C hex) bytes. DLC: Destination = Station NGC 0DD6BC DLC: Source = Station Cisco14A4BFA DLC: Ethertype = 0800 (IP) DLC: IP: - IP Header - IP: IP: Version = 4, header length = 20 bytes IP: Type of service = 00 IP: 000. = routine IP: ...0 = normal delay IP: 0... = normal throughput IP: .0.. = normal reliability IP: ..0. = ECT bit - transport protocol will ignore the CE bit IP: ...0 = CE bit - no congestion IP: Total length= 44 bytes IP: Identification = 0 IP: Flags = 0X IP: .0.. = may fragment IP: ..0. = last fragment IP: Fragment offset = 0 bytes IP: Time to live= 255 seconds/hops IP: Protocol= 6 (TCP) IP: Header checksum = 3864 (correct) IP: Source address = [192.168.1.22] IP: Destination address = [192.168.1.1] IP: No options IP: TCP: - TCP header - TCP: TCP: Source port = 23 (Telnet) TCP: Destination port= 2909 TCP: Initial sequence number = 1056999666 TCP: Next expected Seq number= 1056999667 TCP: Acknowledgment number = 11781197 TCP: Data offset = 24 bytes TCP: Flags = 12 TCP: ..0. = (No urgent pointer) TCP: ...1 = Acknowledgment TCP: 0... = (No push) TCP: .0.. = (No reset) TCP: ..1. = SYN TCP: ...0 = (No FIN) TCP: Window = 4128 TCP: Checksum=
RE: Frame Relay
I would disagree with the statement below. Ethernet, Token Ring etc are interacting with the upper layers. For example Ethernet II has an Ethertype value that identifies the upper layer for 0x0800 is IP, the same goes for DSAP/SSAP values in the 802.3 header. The OSI layers are somewhat independent of each other except at the borders where they interact. For IP the interaction between the layer 3 and higher uses a Protocol ID field in the header to specify TCP UDP EIGRP etc. Regarding Frame Relay this is done in the encapsulation part. For example if you would use the IETF encapsulation method you (the system) would use a NLPID that identifies the upper layer protocol. For more info on this see http://andrew2.andrew.cmu.edu/rfc/rfc1490.html . Cisco uses a proprietary encapsulation as well where 2 bytes are used for indicating packet type. Willy Schoots -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Rik Guyler Sent: Thursday, February 01, 2001 3:29 PM To: Cisco Groupstudy (E-mail) Subject: RE: Frame Relay Layer 2 Seriously, FR is a Layer 2 protocol, as is Ethernet, Token Ring, etc. As those other protocols support numerous Layer 3 (or higher) protocols, so will FR. The beauty of the OSI model is that there is separation of the layers without too much interaction between them. In other words, the Layer 4 datagrams get encapsulated into the Layer 3 packets, which in turn get encapsulated into Layer 2 frames. FR doesn't care for the most part what is "inside" the Layer 3 stuff coming down the pipe. ;-} Rik -Original Message- From: Pierre-Alex [mailto:[EMAIL PROTECTED]] Sent: Thursday, February 01, 2001 8:41 AM To: [EMAIL PROTECTED] Subject: Frame Relay What element in a frame relay packet allows support for multiple protocols? Pierre-Alex _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] , This mail was processed by Mail essentials for Exchange/SMTP, the email security management gateway. Mail essentials adds content checking, email encryption, anti spam, anti virus, attachment compression, personalised auto responders, archiving and more to your Microsoft Exchange Server or SMTP mail server. For more information visit http://www.mailessentials.com _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: A question
Here is a link with some more info on it for Win2000 (also applicable to Win98/ME) about this http://www.microsoft.com/TechNet/network/tcpip2k.asp If a Microsoft TCP/IP client is installed and set to dynamically obtain TCP/IP protocol configuration information from a DHCP server (instead of being manually configured with an IP address and other parameters), the DHCP client service is engaged each time the computer is restarted. The DHCP client service now uses a two-step process to configure the client with an IP address and other configuration information. When the client is installed, it attempts to locate a DHCP server and obtain a configuration from it. Many TCP/IP networks use DHCP servers that are administratively configured to hand out information to clients on the network. If this attempt to locate a DHCP server fails, the Windows 2000 DHCP client autoconfigures its stack with a selected IP address from the IANA-reserved class B network 169.254.0.0 with the subnet mask 255.255.0.09 . The DHCP client tests (using a gratuitous ARP) to make sure that the IP address that it has chosen is not already in use. If it is in use, it selects another IP address (it does this for up to 10 addresses). Once the DHCP client has selected an address that is verifiably not in use, it configures the interface with this address. It continues to check for a DHCP server in the background every 5 minutes. If a DHCP server is found, the autoconfiguration information is abandoned, and the configuration offered by the DHCP server is used instead. This autoconfiguration feature is known as Automatic Private IP Addressing (APIPA) and allows single subnet home office or small office networks to use TCP/IP without static configuration or the administration of a DHCP server. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Chuck Larrieu Sent: Friday, January 05, 2001 7:48 PM To: Saswata Mohapatra; [EMAIL PROTECTED] Subject: RE: A question I believe the 169.250.0.0 is a Microsoft reserved address. Microsoft, if memory serves, uses it in conjunction with their automatic network configuration A search of the RFC's did not reveal anything. A search of ARIN whois indicated that the block itself is assigned to "linklocal" Microsoft claims it is theirs http://msdn.microsoft.com/library/wcedoc/wcecomm/tcpip_50.htm e.g. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Saswata Mohapatra Sent: Friday, January 05, 2001 10:13 AM To: [EMAIL PROTECTED] Subject:A question Hi Networker I have couple of questions. 1. We recently received a router preconfigured from one of our client. The moment we connect the router to our network, all of our PC in our internal network got a message about IP conflict with another IP address which is not our internal IP address. We use 10.210.X.X as our internal IP and the conflicting IP was 169.254.X.X. We use DHCP server internally. This router was connected to our network through Sonicwall Firewall which disallows all the incoming traffic. So, we removed the router and everything worked fine. So, my question is "Is there a DHCP server in the router?" 2. How should I connect my PC to the console. I have the console cables with me. I am using Windows NT server. I tried to connect the cable to the com2 and when I tries to use the Hyper terminal it took most of the processor time. So please help me out. Somebody please help me. I have to finish this work by the end of the day. TIA. Saswata __ Do You Yahoo!? Yahoo! Photos - Share your holiday photos online! http://photos.yahoo.com/ _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] _ FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Difference in Broadcast Domain and Collision Domain......
Collision domains: Station A sends out a frame, this frame can collide with an other frame from station X on the "wire". Station A and all other stations that could be station X form a collision domain, this includes ports from routers and switches. A collision domain means all the stations that share the same physical "wire" directly or indirectly through a repeater (hub). Bridges, switches and routers break up collision domains Broadcast domains: Station A sends out a broadcast, this broadcast can be received by station X. Station A and all other stations that could be station X form a broadcast domain. Broadcasts are normally forwarded by bridges and switches. Routers normally filter broadcasts (not always, think about IP HELPER function). However switches do also VLANs, this means that not all broadcasts are forwarded out all ports. A broadcast stays within its VLAN !!!. -- switches can break up collision domains and by using VLANs also can break up broadcast domains. Willy Schoots Lucent NPS -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Suresh Uniyal Sent: Wednesday, August 30, 2000 9:18 AM To: Cisco (E-mail) Subject: Difference in Broadcast Domain and Collision Domain.. Hi all, How we r going to differentiate between a broadcast domain and a collision domain. Can we co-relate this to a router and a switch or a bridge. -SU ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED] ___ UPDATED Posting Guidelines: http://www.groupstudy.com/list/guide.html FAQ, list archives, and subscription info: http://www.groupstudy.com Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
