EIGRP Topology Table

I'm getting a little confused about the EIGRP topo table. The successor is the best route to a destination. The feasible succesor is the next best route to a destination as long as it's AD is less than the FD. When you do a "show ip eigrp topo", and it shows the topology table, do they consider all routes in here to be feasible successors? Lets say that for a 10.200.1.6, it saids it has one successor, but shows two routes. Looking through Cisco eyes, are both of those routes considered feasible successors, and of course the one with the lowest FD is the successor and is put in the routing table? Or...out of those two routes, does Cisco considered one to be a successor, and one to be considered a feasible successor. The later is how I thought Cisco looked at it. However, I was reading in one of the CCIE books, and it "seemed" like it was saying both routes in the topo table are considered feasible successors, and then the one with the lowest AD is also the successor and is put into the routing table. So what I'm asking is lets say I was given a topo table and CISCO asks how many feasible successors does this destination have and which route is it it? Lets say it shows the destination to have one successor, but it shows two routes. So are there two feasible successors with one being the successor, or is there one successor and one feasible successor. Does Cisco consider them segregated?

Hello,
is this a question for an exam ? If you have the following example:
P 172.16.100.0/24, 1 successors, FD is 2707456
via 172.16.250.2 (2707456/2195456), Serial0
via 172.16.251.2 (46251776/281600), Serial1
If the question is: how many feasible successors do you have, my answer would be that this destination has two feasible successors. If the question is: how many successors do you have, my answer would be one.
HTH,
GNT

Similar Messages

  • Network lost in local eigrp vrf topology table

    We are running 12.3.5 IOS on the majority of our routers and MPLS with three different networks or VRF's in the core. At an edge site, we have two of the three defined (the globabl routing table and another VRF called lgnet.) It is running 12.3.5. In order to correctly advertise the lgnet 172.x.x.x net out into the network, we are using predominently secondary addresses. The problem is that sometimes the 172 address just disappears from the distribution router routing table. I then check the edge router routing table for the 172 net which is part of the lgnet vrf and it is there but when I check the eigrp topology table for the lgnet vrf, it is NOT there. I then remove and re-install the network statement under the address family and it fixes it. I cannot find any problem on cisco where it specifically defines this problem. Any ideas or thoughts would be appreciated.

    The problem could be due to the use of secondary address. Try and see if you can reconfigure without using secondary ip address and see what happens.

  • WAAS no peers in topology table

    Anyone run into this? If you look at the topology under the core WAE's, there is nothing but mac aadresses. However under the edge devices it sees the the cores fine. I am running into optimization issues, CIFS is not working and I cannot pre-pop athough everything looks fine. No firewall either. Something with autodiscovery? Asymetrical routing? All the edge devices as well as the core devices are in the central manager and look fine. Really weird.

    4.0.13. The only thing that appears to be optimized is www and thats just TFO. Not sure what you mean by system report, but if you do a "show tfo connection summ" you see the 4050 connections fron the core to the edges, however when you go to the edges you do not see any 4050 connections back to the cores(we have 2. All the basic stuff I have checked, no firewalls, the WAEs are on their own subnet and have exclude in and the subnets are int herouting table and reachable by everyone. WCCP looks fine as does all the configs on the wae. All of the devices are in the Central manager and are online. Again all the edge peer show up as mac addresses on the cores, the core devices show up on the edge peer topology table fine. I have a TAC case open for 10 days now and still nothing the customer is not too happy..

  • Having an issue adding network to eigrp

    I'm doing a class project using a network simulator and am asked to: Design and implement an network for company RoutersCourseMatters.  The names of the department names at this company are Faculty, Staff, and Students.  For security reasons, each department must be isolated from each other's broadcast domain on the network.  The Faculty have 50 end devices that need to be connected to the network.  Staff has 26 end devices and the Students have 100 end devices.  The network spaced provided by the ISP is 192.168.0.0/24.  The dynamic protocol used for this network must be for Cisco-only equipment.  Test each department network with just one end device and ensure full connectivity across the entire network
    So we have our network topology setup for the class project(see picture attached). We are using one router for faculty+staff. Faculty has ip/mask of 192.168.0.1/26 and staff is: 192.168.0.65/27. we have a seperate router for students which the IP subnet for students is 192.168.0.150/25. The routers are directly connected and are using ips 192.168.0.98/29 & 192.168.0.100/29 so since the two routers are directly connected on the same subnet they have no issue pinging each other. The problem is pinging hosts from a subnet to hosts on a different subnet. When I try and add ANY 192.168.0.* subnet to eigrp it instead adds 192.168.16.* network. For instance on the faculty/student router if i do a 'router eigrp 1' command followed by 'network 192.168.0.0 0.0.0.63' it shows network 192.168.16.0 has been added to eigrp under show run. here is show run command:
    faculty/staff Con0 is now available
    Press RETURN to get started!
    faculty/staff>en
    faculty/staff#show run
    Building configuration...
    Current configuration : 874 bytes
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname faculty/staff
    boot-start-marker
    boot-end-marker
    no aaa new-model
    ip cef
    ip subnet-zero
    interface FastEthernet0/0
      description blank
      ip address 192.168.0.65 255.255.255.224
      no ip directed-broadcast
    interface FastEthernet0/1
      description link to switch
      ip address 192.168.0.1 255.255.255.192
      no ip directed-broadcast
    interface Serial0/0/0
      ip address 192.168.20.2 255.255.255.0
      no ip directed-broadcast
      clockrate 2000000
    interface Serial0/0/1
      no ip address
      no ip directed-broadcast
      shutdown
      clockrate 2000000
    interface Serial0/1/0
      no ip address
      no ip directed-broadcast
      shutdown
      clockrate 2000000
    interface Serial0/1/1
      ip address 192.168.0.98 255.255.255.248
      no ip directed-broadcast
    router eigrp 1
     network 0.0.0.0
     network 192.168.1.1 0.0.0.0
     network 192.168.16.0
     network 192.168.20.0
     no auto-summary
    ip classless
    no ip http server
    no ip http secure-server
    control-plane
    line con 0
    line aux 0
    line vty 0 4
      login
    line vty 5 1180
      login
    scheduler allocate 20000 1000
    end
    faculty/staff#config t
    Enter configuration commands, one per line.  End with CNTL/Z
    faculty/staff(config)#router eigrp 1
    faculty/staff(config-router)#network 192.168.0.0 0.0.0.63
    faculty/staff(config-router)#exit
    faculty/staff(config)#exit
    faculty/staff#show run
    Building configuration...
    Current configuration : 874 bytes
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname faculty/staff
    boot-start-marker
    boot-end-marker
    no aaa new-model
    ip cef
    ip subnet-zero
    interface FastEthernet0/0
      description blank
      ip address 192.168.0.65 255.255.255.224
      no ip directed-broadcast
    interface FastEthernet0/1
      description link to switch
      ip address 192.168.0.1 255.255.255.192
      no ip directed-broadcast
    interface Serial0/0/0
      ip address 192.168.20.2 255.255.255.0
      no ip directed-broadcast
      clockrate 2000000
    interface Serial0/0/1
      no ip address
      no ip directed-broadcast
      shutdown
      clockrate 2000000
    interface Serial0/1/0
      no ip address
      no ip directed-broadcast
      shutdown
      clockrate 2000000
    interface Serial0/1/1
      ip address 192.168.0.98 255.255.255.248
      no ip directed-broadcast
    router eigrp 1
     network 0.0.0.0
     network 192.168.1.1 0.0.0.0
     network 192.168.16.0
     network 192.168.20.0
     no auto-summary
    ip classless
    no ip http server
    no ip http secure-server
    --More--
    project.jpg
    Reply Reply to Main Discussion
        Cody Robinson
        Cody Robinson
        2:36pm
    Here is 'show ip eigrp topology' on staff/faculty router:
    faculty/staff Con0 is now available
    Press RETURN to get started!
    faculty/staff>en
    faculty/staff#show ip interface
    FastEthernet0/0 is up, line protocol is up
      Internet address is 192.168.0.65/27
      Broadcast address is 255.255.255.255
      Address determined by setup command
      MTU is 1514 bytes
      Helper address is not set
      Directed broadcast forwarding is disabled
      Outgoing access list is not set
      Inbound access list is not set
      Proxy ARP is enabled
      Local Proxy ARP is disabled
      Security level is default
      Split horizon is disabled
      ICMP redirects are always sent
      ICMP unreachables are always sent
      ICMP mask replies are never sent
      IP fast switching is enabled
      IP fast switching on the same interface is enabled
      IP Flow switching is disabled
      IP CEF switching is enabled
      IP CEF Fast switching turbo vector
      IP multicast fast switching is enabled
      IP multicast distributed fast switching is disabled
      IP route-cache flags are Fast, CEF
      Router Discovery is disabled
      IP output packet accounting is disabled
      IP access violation accounting is disabled
      TCP/IP header compression is disabled
      RTP/IP header compression is disabled
      Policy routing is disabled
      Network address translation is disabled
      BGP Policy Mapping is disabled
      WCCP Redirect outbound is disabled
      WCCP Redirect inbound is disabled
      WCCP Redirect exclude is disabled
    FastEthernet0/1 is up, line protocol is up
      Internet address is 192.168.0.1/26
      Broadcast address is 255.255.255.255
      Address determined by setup command
      MTU is 1514 bytes
      Helper address is not set
      Directed broadcast forwarding is disabled
      Outgoing access list is not set
      Inbound access list is not set
      Proxy ARP is enabled
      Local Proxy ARP is disabled
      Security level is default
      Split horizon is disabled
      ICMP redirects are always sent
      ICMP unreachables are always sent
      ICMP mask replies are never sent
      IP fast switching is enabled
      IP fast switching on the same interface is enabled
      IP Flow switching is disabled
      IP CEF switching is enabled
      IP CEF Fast switching turbo vector
      IP multicast fast switching is enabled
      IP multicast distributed fast switching is disabled
      IP route-cache flags are Fast, CEF
      Router Discovery is disabled
      IP output packet accounting is disabled
      IP access violation accounting is disabled
      TCP/IP header compression is disabled
      RTP/IP header compression is disabled
      Policy routing is disabled
      Network address translation is disabled
      BGP Policy Mapping is disabled
      WCCP Redirect outbound is disabled
      WCCP Redirect inbound is disabled
      WCCP Redirect exclude is disabled
    Serial0/0/0 is down, line protocol is down
      Internet address is 192.168.20.2/24
      Broadcast address is 255.255.255.255
      Address determined by setup command
      MTU is 1514 bytes
      Helper address is not set
      Directed broadcast forwarding is disabled
      Outgoing access list is not set
      Inbound access list is not set
      Proxy ARP is enabled
      Local Proxy ARP is disabled
      Security level is default
      Split horizon is disabled
      ICMP redirects are always sent
      ICMP unreachables are always sent
      ICMP mask replies are never sent
      IP fast switching is enabled
      IP fast switching on the same interface is enabled
      IP Flow switching is disabled
      IP CEF switching is enabled
      IP CEF Fast switching turbo vector
      IP multicast fast switching is enabled
      IP multicast distributed fast switching is disabled
      IP route-cache flags are Fast, CEF
      Router Discovery is disabled
      IP output packet accounting is disabled
      IP access violation accounting is disabled
      TCP/IP header compression is disabled
      RTP/IP header compression is disabled
      Policy routing is disabled
      Network address translation is disabled
      BGP Policy Mapping is disabled
      WCCP Redirect outbound is disabled
      WCCP Redirect inbound is disabled
      WCCP Redirect exclude is disabled
    Serial0/0/1 is administratively down, line protocol is down
      Internet protocol processing disabled
    Serial0/1/0 is administratively down, line protocol is down
      Internet protocol processing disabled
    Serial0/1/1 is up, line protocol is up
      Internet address is 192.168.0.98/29
      Broadcast address is 255.255.255.255
      Address determined by setup command
      MTU is 1514 bytes
      Helper address is not set
      Directed broadcast forwarding is disabled
      Outgoing access list is not set
      Inbound access list is not set
      Proxy ARP is enabled
      Local Proxy ARP is disabled
      Security level is default
      Split horizon is disabled
      ICMP redirects are always sent
      ICMP unreachables are always sent
      ICMP mask replies are never sent
      IP fast switching is enabled
      IP fast switching on the same interface is enabled
      IP Flow switching is disabled
      IP CEF switching is enabled
      IP CEF Fast switching turbo vector
      IP multicast fast switching is enabled
      IP multicast distributed fast switching is disabled
      IP route-cache flags are Fast, CEF
      Router Discovery is disabled
      IP output packet accounting is disabled
      IP access violation accounting is disabled
      TCP/IP header compression is disabled
      RTP/IP header compression is disabled
      Policy routing is disabled
      Network address translation is disabled
      BGP Policy Mapping is disabled
      WCCP Redirect outbound is disabled
      WCCP Redirect inbound is disabled
      WCCP Redirect exclude is disabled
    faculty/staff#show ip eigrp ?
      <1-65535>   Autonomous System
      accounting  IP-EIGRP Accounting
      interfaces  IP-EIGRP interfaces
      neighbors   IP-EIGRP neighbors
      topology    IP-EIGRP Topology Table
      traffic     IP-EIGRP Traffic Statistics
      vrf         Select a VPN Routing/Forwarding instance
    faculty/staff#show ip eigrp topology
    IP-EIGRP Topology Table for AS(1)/ID(192.168.20.2)
    Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
           r - reply Status, s - sia Status
    P 192.168.0.0/26, 1 successors, FD is 2172416
             via Connected, FastEthernet0/1
    P 192.168.0.64/27, 1 successors, FD is 2172416
             via Connected, FastEthernet0/0
    P 192.168.0.96/29, 1 successors, FD is 2172416
             via Connected, Serial0/1/1
    faculty/staff#
        Cody Robinson
        Cody Robinson
        2:37pm
    Here is show run on students router:
    Students Con0 is now available
    Press RETURN to get started!
    Students>sh run
                ^
    % Invalid input detected at '^' marker.
    Students>en
    Students#sh run
    Building configuration...
    Current configuration : 874 bytes
    version 12.4
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname Students
    boot-start-marker
    boot-end-marker
    no aaa new-model
    ip cef
    ip subnet-zero
    interface FastEthernet0/0
      no ip address
      no ip directed-broadcast
      shutdown
    interface FastEthernet0/1
      description link to switch
      ip address 192.168.0.150 255.255.255.128
      no ip directed-broadcast
    interface Serial0/0/0
      ip address 192.168.10.1 255.255.255.0
      no ip directed-broadcast
      clockrate 2000000
    interface Serial0/0/1
      no ip address
      no ip directed-broadcast
      shutdown
      clockrate 2000000
    interface Serial0/1/0
      no ip address
      no ip directed-broadcast
      shutdown
      clockrate 2000000
    interface Serial0/1/1
      ip address 192.168.0.100 255.255.255.248
      no ip directed-broadcast
      clockrate 2000000
    router eigrp 1
     network 0.0.0.0
     network 192.168.1.1 0.0.0.0
     network 192.168.10.0
    ip classless
    no ip http server
    no ip http secure-server
    control-plane
    line con 0
    line aux 0
    line vty 0 4
      login
    line vty 5 1180
      login
    scheduler allocate 20000 1000
    end
    Students#

    Hello lolwar,
    From your setup and description you provided I see some mismatch in IP subneting you calculated.
    For instance in your diagram you have networks 192.168.0.0/26 (FACULTY), 192.168.0.64/27 (STAFF), 192.168.0.96/29 (point-to-point link between routers) and 192.168.0.128/25 (STUDENTS).
    First, you're wasting IP addresses, because you have unused space between point-to-point link and STUDENTS subnet. It's a good practice, when calculating subnets first calculate the biggest, subnet, then smaller one until the smallest one (usually some point-to-point cross-connects). For more about this see this guide.
    Now, the issue I see as the most important is, that you have in your diagram networks as I mentioned above, but into your EIGRP process you're adding completely different subnets (192.168.16.x, 192.168.20.x,...).
    I entered following:
    STUDENT ROUTER =------------>
    router eigrp 1
    network 192.168.0.96 0.0.0.7
    network 192.168.0.128 0.0.0.127
    FACULTY/STAFF ROUTER =------------->
    router eigrp 1
    network 192.168.0.0 0.0.0.63
    network 192.168.0.64 0.0.0.31
    network 192.168.0.96 0.0.0.7
    And all works just fine, computer's are able to ping each other. Also although it's not necessary, it's good to includes network wildcard mask into the "network" command under EIGRP (or OSPF) configuration.
    I hope this will help you (please rate if this is the case. Thanks.)

  • Ipv6, how to view eigrp Id

    Hi everybody
    How is everyone doing?
    Is there any command  to display eigrp 's id for ipv6?
    I googled it but could not find any command.
    thanks and have a great weekend

    Hi Sarah,
    Use the show ipv6 eigrp topology command:
    R1#show ipv6 eigrp topology
    IPv6-EIGRP Topology Table for AS(1)/ID(223.255.255.1)
    Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
           r - reply Status, s - sia Status
    P 2001::/64, 1 successors, FD is 128256
            via Connected, Loopback0
    Best regards,
    Peter

  • Nexus 6004 EIGRP Relationship between the two switches

    Hi All,
    I will try to explain this as best as I can. In our current TEST LAB we have a Pair of Cisco ASA5585x running in Active/Passive mode. We use a VRF transit to connect the 10 GB interface to a Pair of Cisco Nexus 6004 (L3) switches running vPC between them. Downstream we also have a pair of Cisco 9372 switches (L2) also running vPC between the two.
    As of right now we have EIGRP neighbor relationship formed between the two N6K's and the ASA.
    ASA
    ciscoasa# sh eigrp neighbors
    EIGRP-IPv4 neighbors for process 100
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    1 172.16.230.9 Te0/8.451 12 01:30:25 1 200 0 52
    0 172.16.230.10 Te0/8.451 12 01:30:25 1 200 0 48
    The ASA formed relationship with both N6K's
    SWITCH1
    Nexus6-1# sh ip eigrp neighbors vrf inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    0 172.16.8.3 Vlan680 11 01:28:28 1 50 0 45
    1 172.16.230.10 Vlan451 13 01:28:28 1 50 0 46
    2 172.16.230.11 Vlan451 10 01:28:00 4 50 0 13
    Nexus6-1#
    SWITCH2
    Nexus6-2# sh ip eigrp neighbors vrf Inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    2 172.16.8.2 Vlan680 14 01:30:11 23 138 0 48
    0 172.16.230.9 Vlan451 13 01:30:11 480 2880 0 50
    1 172.16.230.11 Vlan451 13 01:29:48 1598 5000 0 13
    Nexus6-2#
    Both Nexus Switches formed EIGRP neighbors using the vPC Peer-Link. There is enough documentation out there that strongly suggest not to use vPC Peer-Links for EIGRP anything.
    We do have additional interfaces available on the 6K's that we can use as a cross connect for EIGRP. What we are having trouble understanding how we can force EIGRP traffic over those ports?
    Here is a complete Switch config:
    Switch1
    Nexus6-1# sh run
    feature telnet
    cfs eth distribute
    feature eigrp
    feature interface-vlan
    feature lacp
    feature vpc
    feature lldp
    vlan 1
    vlan 451
    name P2P_VRF_SVI
    vlan 652
    name Management
    vlan 680
    name Inside
    vrf context Inside
    vrf context management
    ip route 0.0.0.0/0 172.16.52.1
    vrf context peer-keepalive
    vpc domain 99
    role priority 1
    peer-keepalive destination 10.200.50.2 source 10.200.50.1 vrf peer-keepalive
    delay restore 120
    interface Vlan1
    interface Vlan451
    description Inside p2p to ASA
    no shutdown
    vrf member Inside
    ip address 172.16.230.9/29
    ip router eigrp 100
    no ip passive-interface eigrp 100
    interface Vlan651
    interface Vlan680
    description Inside Network
    no shutdown
    vrf member Inside
    ip address 172.16.8.2/22
    ip router eigrp 100
    interface port-channel99
    switchport mode trunk
    spanning-tree port type network
    vpc peer-link
    interface port-channel102
    switchport mode trunk
    vpc 102
    interface Ethernet1/1
    description vPC Peer Link 1.1
    switchport mode trunk
    speed auto
    channel-group 99
    interface Ethernet1/6
    interface Ethernet1/7
    description vPC Peer Link 1.7 to Nexus 9372 PRI
    switchport mode trunk
    speed auto
    channel-group 102 mode active
    interface Ethernet1/8
    interface Ethernet1/9
    interface Ethernet2/1
    description vPC Peer Link 2.1
    switchport mode trunk
    speed auto
    channel-group 99
    interface Ethernet2/2
    interface Ethernet2/7
    description vPC Peer Link 2.1 to Nexus SEC
    switchport mode trunk
    speed auto
    channel-group 102 mode active
    interface Ethernet2/8
    interface Ethernet8/1
    description keep-alive peer-link to ALNSWI02
    no switchport
    vrf member peer-keepalive
    ip address 10.200.50.1/30
    interface Ethernet8/2
    description Uplink to ASA
    switchport mode trunk
    interface Ethernet8/3
    interface mgmt0
    vrf member management
    ip address 172.16.52.3/23
    line console
    line vty
    boot kickstart bootflash:/n6000-uk9-kickstart.7.0.1.N1.1.bin
    boot system bootflash:/n6000-uk9.7.0.1.N1.1.bin
    router eigrp 100
    passive-interface default
    default-information originate
    vrf Inside
    autonomous-system 100
    default-information originate
    poap transit
    Nexus6-1#
    Nexus6-1# sh ip eigrp neighbors vrf inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    0 172.16.8.3 Vlan680 11 01:28:28 1 50 0 45
    1 172.16.230.10 Vlan451 13 01:28:28 1 50 0 46
    2 172.16.230.11 Vlan451 10 01:28:00 4 50 0 13
    Nexus6-1#
    Nexus6-1# sh ip eigrp topology vrf Inside
    IP-EIGRP Topology Table for AS(100)/ID(172.16.8.2) VRF Inside
    Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
    r - reply Status, s - sia Status
    P 172.16.8.0/22, 1 successors, FD is 2816
    via Connected, Vlan680
    P 172.16.230.8/29, 1 successors, FD is 2816
    via Connected, Vlan451
    Nexus6-1# sh vpc
    Legend:
    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id : 99
    Peer status : peer adjacency formed ok
    vPC keep-alive status : peer is alive
    Configuration consistency status : success
    Per-vlan consistency status : success
    Type-2 consistency status : success
    vPC role : primary
    Number of vPCs configured : 1
    Peer Gateway : Disabled
    Dual-active excluded VLANs : -
    Graceful Consistency Check : Enabled
    Auto-recovery status : Disabled
    vPC Peer-link status
    id Port Status Active vlans
    1 Po99 up 1,451,652,680
    vPC status
    id Port Status Consistency Reason Active vlans
    102 Po102 up success success 1,451,652,6
    80
    Nexus6-1# sh spanning-tree
    VLAN0001
    Spanning tree enabled protocol rstp
    Root ID Priority 32769
    Address 1005.caf5.88ff
    Cost 2
    Port 4197 (port-channel102)
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
    Address 8c60.4f2d.2ffc
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Root FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    Eth8/3 Desg FWD 2 128.1027 P2p
    VLAN0451
    Spanning tree enabled protocol rstp
    Root ID Priority 33219
    Address 8c60.4f2d.2ffc
    This bridge is the root
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 33219 (priority 32768 sys-id-ext 451)
    Address 8c60.4f2d.2ffc
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Desg FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    VLAN0652
    Spanning tree enabled protocol rstp
    Root ID Priority 33420
    Address 1005.caf5.88ff
    Cost 2
    Port 4197 (port-channel102)
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 33420 (priority 32768 sys-id-ext 652)
    Address 8c60.4f2d.2ffc
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Root FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    VLAN0680
    Spanning tree enabled protocol rstp
    Root ID Priority 33448
    Address 1005.caf5.88ff
    Cost 2
    Port 4197 (port-channel102)
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 33448 (priority 32768 sys-id-ext 680)
    Address 8c60.4f2d.2ffc
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Desg FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Root FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    Nexus6-1#
    Switch2
    Nexus6-2# sh run
    !Command: show running-config
    !Time: Sat Feb 12 19:02:44 2011
    version 7.0(1)N1(1)
    hostname Nexus6-2
    feature telnet
    cfs eth distribute
    feature eigrp
    feature interface-vlan
    feature lacp
    feature vpc
    feature lldp
    vlan 1
    vlan 451
    name P2P_VRF_SVI
    vlan 652
    name Management
    vlan 680
    name Inside
    vrf context Inside
    vrf context P2P_Inside_VRF
    vrf context management
    ip route 0.0.0.0/0 172.16.52.1
    vrf context peer-keepalive
    vpc domain 99
    role priority 2
    peer-keepalive destination 10.200.50.1 source 10.200.50.2 vrf peer-keepalive
    delay restore 120
    interface Vlan1
    interface Vlan451
    description Inside p2p to ASA
    no shutdown
    vrf member Inside
    ip address 172.16.230.10/29
    ip router eigrp 100
    no ip passive-interface eigrp 100
    interface Vlan680
    description Inside Network
    no shutdown
    vrf member Inside
    ip address 172.16.8.3/22
    ip router eigrp 100
    interface port-channel99
    switchport mode trunk
    spanning-tree port type network
    vpc peer-link
    interface port-channel102
    switchport mode trunk
    vpc 102
    interface Ethernet1/1
    description vPC Peer Link 1.1
    switchport mode trunk
    speed auto
    channel-group 99
    interface Ethernet1/2
    interface Ethernet1/6
    interface Ethernet1/7
    description vPC Link 1.7 to Nexus 9372 SEC
    switchport mode trunk
    speed auto
    channel-group 102 mode active
    interface Ethernet1/8
    interface Ethernet1/12
    interface Ethernet2/1
    description vPC Peer Link 2.1
    switchport mode trunk
    speed auto
    channel-group 99
    interface Ethernet2/2
    interface Ethernet2/6
    interface Ethernet2/7
    description vPC Link 2.1 to Nexus PRI
    switchport mode trunk
    speed auto
    channel-group 102 mode active
    interface Ethernet2/8
    interface Ethernet2/12
    interface Ethernet8/1
    description keep-alive peer-link to ALNSWI01
    no switchport
    vrf member peer-keepalive
    ip address 10.200.50.2/30
    interface Ethernet8/2
    description Uplink to ASA
    switchport mode trunk
    switchport trunk allowed vlan 1,451,652,680
    interface Ethernet8/3
    interface Ethernet8/20
    interface mgmt0
    vrf member management
    ip address 172.16.52.4/23
    line console
    line vty
    boot kickstart bootflash:/n6000-uk9-kickstart.7.0.1.N1.1.bin
    boot system bootflash:/n6000-uk9.7.0.1.N1.1.bin
    router eigrp 100
    vrf Inside
    autonomous-system 100
    default-information originate
    poap transit
    logging logfile messages 6
    Nexus6-2#
    Nexus6-2#
    Nexus6-2# sh ip eigrp neighbors vrf Inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H Address Interface Hold Uptime SRTT RTO Q Seq
    (sec) (ms) Cnt Num
    2 172.16.8.2 Vlan680 14 01:30:11 23 138 0 48
    0 172.16.230.9 Vlan451 13 01:30:11 480 2880 0 50
    1 172.16.230.11 Vlan451 13 01:29:48 1598 5000 0 13
    Nexus6-2#
    Nexus6-2# sh ip eigrp topology vrf Inside
    IP-EIGRP Topology Table for AS(100)/ID(172.16.8.3) VRF Inside
    Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
    r - reply Status, s - sia Status
    P 172.16.8.0/22, 1 successors, FD is 2816
    via Connected, Vlan680
    P 172.16.230.8/29, 1 successors, FD is 2816
    via Connected, Vlan451
    Nexus6-2#
    Nexus6-2#
    Nexus6-2# sh vpc
    Legend:
    (*) - local vPC is down, forwarding via vPC peer-link
    vPC domain id : 99
    Peer status : peer adjacency formed ok
    vPC keep-alive status : peer is alive
    Configuration consistency status : success
    Per-vlan consistency status : success
    Type-2 consistency status : success
    vPC role : secondary
    Number of vPCs configured : 1
    Peer Gateway : Disabled
    Dual-active excluded VLANs : -
    Graceful Consistency Check : Enabled
    Auto-recovery status : Disabled
    vPC Peer-link status
    id Port Status Active vlans
    1 Po99 up 1,451,652,680
    vPC status
    id Port Status Consistency Reason Active vlans
    102 Po102 up success success 1,451,652,6
    80
    Nexus6-2#
    Nexus6-2#
    Nexus6-2# sh spanning-tree
    VLAN0001
    Spanning tree enabled protocol rstp
    Root ID Priority 32769
    Address 1005.caf5.88ff
    Cost 3
    Port 4194 (port-channel99)
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Bridge ID Priority 32769 (priority 32768 sys-id-ext 1)
    Address 8c60.4f2d.777c
    Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec
    Interface Role Sts Cost Prio.Nbr Type
    Po99 Root FWD 1 128.4194 (vPC peer-link) Network P2p
    Po102 Root FWD 1 128.4197 (vPC) P2p
    Eth8/2 Desg FWD 2 128.1026 P2p
    Eth8/3 Desg FWD 2 128.1027 P2p
    VLAN0451
    Spanning tree enabled protocol rstp
    Root ID Priority 33219
    Address 8c

    Jon,
    Are you ready for the mass confusion?
    when Looking at the ASA EIGRP neighbors output here is what I see.
    ASA# sh eigrp neighbors
    EIGRP-IPv4 neighbors for process 100
    H   Address                 Interface       Hold Uptime   SRTT   RTO  Q  Seq
                                                (sec)         (ms)       Cnt Num
    3   172.16.230.1            Te0/8.450        13  16:45:14 1    200   0   64
    2   172.16.230.2            Te0/8.450        11  16:45:14 1    200   0   84
    1   172.16.230.10           Te0/8.451        11  16:45:20 1    200   0   178
    0   172.16.230.9            Te0/8.451        13  16:45:20 1    200   0   148
    For simplicity sake lets just concetrate on Interface TenGigabit0/8.451 which is the SVI on the Nexus switch that is VLAN451
    From the Nexus Switch 6004 that is directly connected to the ASA here is what I see
    SWI01# sh ip eigrp neighbors vrf Inside
    IP-EIGRP neighbors for process 100 VRF Inside
    H   Address                 Interface       Hold  Uptime  SRTT   RTO  Q  Seq
                                                (sec)         (ms)       Cnt Num
    0   172.16.8.3              Vlan680         10   17:04:30  54   324   0   177
    1   172.16.230.10           Vlan451         11   16:59:10  819  4914  0   178
    2   172.16.230.11           Vlan451         14   16:53:48  24   144   0   20
    The Inside VRF that is tied to both SVI's on the Switch vlans 451 and 680 is in EIGRP 100 on the switch
    SWI01# sh run int vlan 451
    interface Vlan451
      description Inside p2p to ASA
      no shutdown
      vrf member Inside
      ip address 172.16.230.9/29
      ip router eigrp 100
      no ip passive-interface eigrp 100
    SWI01# sh run int vlan 680
    interface Vlan680
      description Inside Network
      no shutdown
      vrf member Inside
      ip address 172.16.8.2/22
      ip router eigrp 100
      hsrp 1
        authentication text test
        preempt
        priority 250
        ip 172.16.8.1
    so you with me so far?
    If you are you have noticed that on the ASA neighbors the ASA sees 172.16.230.11 as a neighbor which is the Secondary Nexus SW. That is becauise they all share the same subnet.
    172.16.230.8/29
    Brakedown:
    PRI Nexus 6004 - 172.16.230.9
    SEC NEXUS 6004 - 172.16.230.10
    PRI ASA 5585x  - 172.16.230.11
    SEC ASA 5585x  - 172.16.230.12
    Because the ASA EIGRP network is a /29 it learns the Secondary Nexus via the Primary Nexus.
    I am not sure that the link we created between the two Nexus Switches is doing anything but consuming ports right now.
    SWI01# sh run int ethernet 8/9
    interface Ethernet8/9
      description EIGRP PORT to Secondary Nexus
      switchport mode trunk
      switchport trunk allowed vlan 450-451
    SWI02# sh run int ethernet 8/9
    interface Ethernet8/9
      description EIGRP PORT to Primary Nexus
      switchport mode trunk
      switchport trunk allowed vlan 450-451
    So the SVI's that go up to the ASA for inspection are 450 and 451. The network SVI's are 600 and 680 all of them live on the switch, and 680, and 600 are extended over the peer links down to the 9372's.
    I think that we are breaking the golden rule of vPC BUT.. I am not 100% sure. Some of the documents read that we should not be allowing network vlans over peer links, but then how do you extend the vlans down to the leaf switch?
    This is giving me nightmares at the moment…
    does this make sense? 

  • Route not showing up in routing table.

    I have my core switch connecting to my router which connects to our MPLS provider. My router has a BGP default route going to the MPLS provider edge router B*   0.0.0.0/0 [20/0] via 172.30.252.78, 1w4d .... This route is not showing up in my core switch. Shouldnt it show up as an eigrp ex default route? Can anyone assist me? my routing table for each device is below. Thank you!
    Router
    USJONELAWTN01R#sho ip route
    Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, * - candidate default, U - per-user static route
           o - ODR, P - periodic downloaded static route
    Gateway of last resort is 172.30.252.78 to network 0.0.0.0
         68.0.0.0/32 is subnetted, 1 subnets
    S       68.142.83.236 is directly connected, Null0
         198.63.196.0/32 is subnetted, 1 subnets
    S       198.63.196.103 is directly connected, Null0
         64.0.0.0/32 is subnetted, 1 subnets
    S       64.234.192.40 is directly connected, Null0
         172.26.0.0/16 is variably subnetted, 3 subnets, 2 masks
    D       172.26.82.0/24 [90/28416] via 172.28.82.10, 1w5d, GigabitEthernet0/1
                           [90/28416] via 172.28.80.10, 1w5d, GigabitEthernet0/0.1
                           [90/28416] via 172.28.80.9, 1w5d, GigabitEthernet0/0.1
    D       172.26.83.0/24 [90/28416] via 172.28.82.10, 1w5d, GigabitEthernet0/1
                           [90/28416] via 172.28.80.10, 1w5d, GigabitEthernet0/0.1
                           [90/28416] via 172.28.80.9, 1w5d, GigabitEthernet0/0.1
    D       172.26.80.0/23 [90/28416] via 172.28.82.10, 1w5d, GigabitEthernet0/1
                           [90/28416] via 172.28.80.10, 1w5d, GigabitEthernet0/0.1
                           [90/28416] via 172.28.80.9, 1w5d, GigabitEthernet0/0.1
         172.28.0.0/16 is variably subnetted, 4 subnets, 2 masks
    C       172.28.176.0/23 is directly connected, GigabitEthernet0/0.6
    C       172.28.80.0/23 is directly connected, GigabitEthernet0/0.1
    C       172.28.82.0/23 is directly connected, GigabitEthernet0/1
    D       172.28.80.20/32
               [90/30720] via 172.28.176.3, 1w5d, GigabitEthernet0/0.6
               [90/30720] via 172.28.82.3, 1w5d, GigabitEthernet0/1
               [90/30720] via 172.28.80.3, 1w5d, GigabitEthernet0/0.1
         172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
    C       172.30.252.78/32 is directly connected, Multilink1
    C       172.30.252.76/30 is directly connected, Multilink1
    D       172.30.252.114/32
               [90/3415808] via 172.28.176.3, 4d00h, GigabitEthernet0/0.6
               [90/3415808] via 172.28.82.3, 4d00h, GigabitEthernet0/1
               [90/3415808] via 172.28.80.3, 4d00h, GigabitEthernet0/0.1
    D       172.30.252.112/30
               [90/3415808] via 172.28.176.3, 4d00h, GigabitEthernet0/0.6
               [90/3415808] via 172.28.82.3, 4d00h, GigabitEthernet0/1
               [90/3415808] via 172.28.80.3, 4d00h, GigabitEthernet0/0.1
    D       172.30.254.24/32
               [90/156160] via 172.28.176.3, 1w5d, GigabitEthernet0/0.6
               [90/156160] via 172.28.82.3, 1w5d, GigabitEthernet0/1
               [90/156160] via 172.28.80.3, 1w5d, GigabitEthernet0/0.1
    C       172.30.254.25/32 is directly connected, Loopback10
    C    192.168.202.0/24 is directly connected, GigabitEthernet0/0.1
         10.0.0.0/8 is variably subnetted, 3 subnets, 2 masks
    S       10.192.254.0/24 [1/0] via 172.28.82.10, GigabitEthernet0/1
    S       10.201.0.0/16 [1/0] via 172.28.82.10, GigabitEthernet0/1
    S       10.200.1.0/24 [1/0] via 172.28.82.10, GigabitEthernet0/1
    C    192.168.203.0/24 is directly connected, GigabitEthernet0/0.1
    C    192.168.51.0/24 is directly connected, GigabitEthernet0/0.1
    B*   0.0.0.0/0 [20/0] via 172.30.252.78, 1w4d
    B    200.200.0.0/16 [20/0] via 172.30.252.78, 1w4d
    B    201.1.0.0/16 [20/0] via 172.30.252.78, 1w4d
    B    172.16.0.0/12 [20/0] via 172.30.252.78, 1w4d
    B    198.30.0.0/16 [20/0] via 172.30.252.78, 1w4d
    B    192.168.0.0/16 [20/0] via 172.30.252.78, 1w4d
    Core Switch
    TNLAW-TN1COREA# sho ip route
    Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, * - candidate default, U - per-user static route
           o - ODR, P - periodic downloaded static route
    Gateway of last resort is 10.192.61.1 to network 0.0.0.0
         172.26.0.0/16 is variably subnetted, 3 subnets, 2 masks
    C       172.26.82.0/24 is directly connected, Vlan601
    C       172.26.83.0/24 is directly connected, Vlan603
    C       172.26.80.0/23 is directly connected, Vlan602
         172.28.0.0/16 is variably subnetted, 4 subnets, 2 masks
    D       172.28.176.0/23 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                            [90/28416] via 172.28.82.2, 7w0d, Vlan2
                            [90/28416] via 172.28.80.3, 7w0d, Vlan1
                            [90/28416] via 172.28.80.2, 7w0d, Vlan1
    C       172.28.80.0/23 is directly connected, Vlan1
    C       172.28.82.0/23 is directly connected, Vlan2
    D       172.28.80.20/32 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                            [90/28416] via 172.28.80.3, 7w0d, Vlan1
         172.30.0.0/16 is variably subnetted, 6 subnets, 2 masks
    D       172.30.252.78/32 [90/3413504] via 172.28.82.2, 1w4d, Vlan2
                             [90/3413504] via 172.28.80.2, 1w4d, Vlan1
    D       172.30.252.76/30 [90/3413504] via 172.28.82.2, 1w4d, Vlan2
                             [90/3413504] via 172.28.80.2, 1w4d, Vlan1
    D       172.30.252.114/32 [90/3413504] via 172.28.82.3, 4d00h, Vlan2
                              [90/3413504] via 172.28.80.3, 4d00h, Vlan1
    D       172.30.252.112/30 [90/3413504] via 172.28.82.3, 4d00h, Vlan2
                              [90/3413504] via 172.28.80.3, 4d00h, Vlan1
    D       172.30.254.24/32 [90/130816] via 172.28.82.3, 7w0d, Vlan2
                             [90/130816] via 172.28.80.3, 7w0d, Vlan1
    D       172.30.254.25/32 [90/130816] via 172.28.82.2, 7w0d, Vlan2
                             [90/130816] via 172.28.80.2, 7w0d, Vlan1
    D    192.168.202.0/24 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                          [90/28416] via 172.28.82.2, 7w0d, Vlan2
         10.0.0.0/8 is variably subnetted, 4 subnets, 3 masks
    S       10.192.254.0/24 [1/0] via 10.192.61.1, GigabitEthernet3/47
    S       10.201.0.0/16 [1/0] via 10.192.61.1, GigabitEthernet3/47
    S       10.200.1.0/24 [1/0] via 10.192.61.1, GigabitEthernet3/47
    C       10.192.61.0/28 is directly connected, GigabitEthernet3/47
    D    192.168.203.0/24 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                          [90/28416] via 172.28.82.2, 7w0d, Vlan2
    D    192.168.51.0/24 [90/28416] via 172.28.82.3, 7w0d, Vlan2
                         [90/28416] via 172.28.82.2, 7w0d, Vlan2
    S*   0.0.0.0/0 [250/0] via 10.192.61.1, GigabitEthernet3/47

    Hello,
    The core switch has got a static default route pointing to 10.192.61.1. It has got a better AD value than the EIGRP routes.
    Even if you are redistributing the BGP routes into EIGRP, EIGRP default route will not make it to the routing table because of the higher AD value than the static route.
    However, you can view that it the EIGRP topology table. Check 'Sh ip ei topo'.
    Krishna

  • EIGRP (OTP)

    Hi,
    I am trying to do load sharing between tow link
    first link connect through MPLS cloud 
    the EIGRP OTP   working fine on it . 
    second link connect through P2P 
    also at P2P eigrp running 
    in my routing table only show me one valid route 
    is't possible to make load sharing thought 2 link 

    Hi Ehsan,
    With EIGRP, you can achieve load sharing if both paths to the same destination have the same best metric (equal-cast load balancing), or if the worse paths go through feasible successors and you configure the variance command (unequal-cost load balancing). In general, this is not trivial to achieve and may require a fair share of smart metric tweaking.
    So the first thing to check is the output of the show ip eigrp topology table on the router with the two links (MPLS and P2P) and verify whether all destinations you want to load-balance for have at least one successor and one feasible successor identified. If yes then doing the load balancing is just a matter of activating the variance with a sensible value. If, however, the destinations only have a single successor and no feasible successor identified in the topology table then you will first need to start modifying metrics so that the neighbors first pass the feasibility condition and only then you can ask for load sharing.
    I understand that this answer is just a very rough indication of where to focus your efforts, and is not a clean list of commands to apply to make the magic work. Tuning EIGRP metrics is not a routine task and it depends very strongly on your topology. What could perhaps help us suggest the more precise way of modifying your EIGRP metrics would be a listing of your show ip eigrp topology focusing on one particular network for which you'd like to achieve the load balancing. In that case please post the output of show ip eigrp topology X.X.X.X/M output so that we can see the component metrics in detail.
    Best regards,
    Peter

  • 3850 Stack EIGRP Problem

    I am seeing strange behavior from a 3850 stack running EIGRP to a couple of 4507's. Let me start out by saying that over the past couple of weeks, we have replaced 5 stacks using the same configuration template, code version, etc. with no issues. Before we execute the change to install these switches, we always run failover testing to prove routing. Last night, on the 6th switch stack, failover testing did not succeed. Maybe you can help me figure out why.
    Here is what happened. I have a loopback configured on the stack. We connect the stack to each of the 4507's at the distribution layer and bring up an eigrp adjacency. I start a continuous ping from another site to the loopback. Then we pull the first link and the ping continues successfully. Plug it back in, bring up the adjacency. Then we pull the second uplink and the ping begins failing (TTL Lost in transit). The route at the source of the ping was lost so it was using the default route which led to nowhere. When I check the route against the table on the 4507's the subnet is not in the table but the adjacency is up.   
    I have attached a topology drawing of the relevant devices (as I see it). Again, we never experienced this issue with the 5 previous stacks which are all connected to the 4507's the same way.                

    Joshua
    So you have equal cost paths on the 4507 to the loopback. You pull the first link and the ping continues because it still has one route. You reconnect the link and an adjacency is formed but no routes are passed from the 3850 to the 4500 and then when you pull the second link the only remaining routes is lost on the 4507 ?
    When you plug the first link back in -
    1) what do you see in the EIGRP topology tables on the 4507
    2) You may need to run debugging on EIGRP to see what is happening from the 4500 and 3850 end
    Jon

  • Relationship between LIB,FIB and LFIB

    Hi all
    I am having a little trouble understanding the relationship between the LIB, FIB and LFIB as part of the MPLS architecture. As far as I understand it, within the MPLS cloud at the ingress LSR, the FIB is a replica of the standard IP RIB and does not contain any label information.
    At this point, if the LSR in question has an interface as part of an MPLS network, label information is added to specific destination prefixes. This information is then used by the LFIB to forward the packet to the next LSR.
    Further reading tells me I must now worry about another table - the LIB. Can somebody clarify if my understanding above is accurate and if so, how does the LIB fit into the picture.
    Thanks!
    M

    Hello,
    Is the CEF table the same thing as the LIB?
    No, not at all. The CEF is an optimized routing table (in fact, a tree structure if implemented in software, or a hashing array if implemented in hardware). The LIB is more similar to an EIGRP topology table. The EIGRP topology table holds the list of all known networks and distances to these networks through individual neighbors that have advertised them. In a similar fashion, the LIB holds the list of networks and label mappings as advertised by individual neighbors. Recall that all your neighbors know the same set of networks and each of these neighbors assigns its own labels to these networks. The LIB holds the collection of all these mappings: a network and all labels as advertised by your individual neighbors.
    When you construct the LFIB entry for a particular network, you first look into your routing table and find the next hop towards that network (plain IP routing). Then you look into the LIB and find out the label this next hop assigned to this network. Then you can construct the LFIB entry - the incoming label will be your own label that you assigned to the network, the outgoing label will be the label the next hop assigned to it, found in the LIB.
    And where does the FEC come in all these?
    The FEC is an abstract term covering the set of all packets that are going to be forwarded in the exactly same way. Authors of MPLS needed to create this term because once a certain flow of packets gets the same label and is forwarded to the same neighboring router, they all are going to be forwarded through a single Label Switched Path and arrive at the same destination where they will be unlabeled. In the most basic MPLS, FECs are identical to individual destination networks. Each destination network would be a single FEC. However, because the sequence of labels defining an LSP through the MPLS network can be built using some other mechanisms that "detach" themselves from the plain routing tables, you suddenly get a whole new world in which not just the destination but also other policies define LSPs and resulting FECs. This is extensively used, for example, in MPLS Traffic Engineering where the LSP follows not just a path towards a particular destination but also goes through a path that guarantees a certain available bandwidth. The term "destination network" is no longer descriptive enough of the path here. Hence, the FEC term is born as a class of equivalently forwarded packets, and labels in fact bind to FECs.
    Best regards,
    Peter

  • EIGRP Multiple Sucessors - Which topology entry is sent to neighbor peer

    All,
    If you have two EIGRP sucessors in your topology table (and selected in RT table, EIGRP has to update its peers with the update.
    The topo table will have two entries in with its external data (assuming is external route from BGP). The external data may be different ie BGP MED may have been ported into the EIGRP external data. ie, one topo entry has a BGP MED of 5000 in the external portion of the EIGRP update and one has a BGP MED of 4000. (not that this matters cause nothing is routed based on this information)
    Which topo entry is sent to the peer?
    Is it based on the external router ID in the external data, as I always see the same external data throughout my AS1 and from only one of the routers that were imported from BGP.
    If further info is needed, I can post a diagram :)
    Kindest regards,
    Ken

    Guys, Many thx indeed,
    Paresh, just to clarify
    I have the following router 2 connects to router 3 - router 3 has multiple sucessors to 133.133.133.0/24
    Router 2 received the last entry (which may have been the only entry at a point in time) in router 3s topo table, as this is probably the entry that router 3 received first and then triggered an update to router 2 correct???? This is originating router 10.10.0.1)
    So, in terms of multiple sucessors, the one you see in the LAST entry in the topo table (orig 10.10.0.1) MEANS that this was the topo entry first to get into router 3s topo DB and then router3 sent this to router2.
    If for some reason, the link (or eigrp peer) between router 2 and router 3 went down, the first entry now in the topo table (the newest one originated from 10.10.0.3) would be sent to router 2.
    Please can you confirm I have this correct and it makes sense.
    Many many kind regards as always,
    Ken
    Router2>sh ip eigrp top 1 133.133.133.0 255.255.255.0
    IP-EIGRP (AS 1): Topology entry for 133.133.133.0/24
    State is Passive, Query origin flag is 1, 0 Successor(s), FD is 282112
    Routing Descriptor Blocks:
    10.11.1.1 (GigabitEthernet1/2), from 10.11.1.1, Send flag is 0x0
    Composite metric is (282112/281856), Route is External
    Vector metric:
    Minimum bandwidth is 10000 Kbit
    Total delay is 1020 microseconds
    Reliability is 255/255
    Load is 1/255
    Minimum MTU is 1500
    Hop count is 2
    External data:
    Originating router is 10.10.0.1
    AS number of route is 1000
    External protocol is BGP, external metric is 5000
    Administrator tag is 1000
    Router2>
    router1>sh ip eigrp topo 133.133.133.0 255.255.255.0
    IP-EIGRP topology entry for 133.133.133.0/24
    State is Passive, Query origin flag is 1, 2 Successor(s), FD is 281856
    Routing Descriptor Blocks:
    10.12.1.3 (Vlan41), from 10.12.1.3, Send flag is 0x0
    Composite metric is (281856/281600), Route is External
    Vector metric:
    Minimum bandwidth is 10000 Kbit
    Total delay is 1010 microseconds
    Reliability is 255/255
    Load is 1/255
    Minimum MTU is 1500
    Hop count is 1
    External data:
    Originating router is 10.10.0.3
    AS number of route is 1000
    External protocol is BGP, external metric is 4000
    Administrator tag is 1000
    10.12.1.1 (Vlan41), from 10.12.1.1, Send flag is 0x0
    Composite metric is (281856/281600), Route is External
    Vector metric:
    Minimum bandwidth is 10000 Kbit
    Total delay is 1010 microseconds
    Reliability is 255/255
    Load is 1/255
    Minimum MTU is 1500
    Hop count is 1
    External data:
    Originating router is 10.10.0.1
    AS number of route is 1000
    External protocol is BGP, external metric is 5000
    Administrator tag is 1000
    router1>

  • Multiple Autonomous Systems using EIGRP Named Mode

    I have an EIGRP network that has multiple AS numbers. Lets says they are AS 200 and 201. AS 200 exists only in the default VRF and AS 201 exists in both the default VRF and well as a dedicated server VRF. I need to configure both AS numbers to run concurrently on our core 6500 switch.
    With the older way to configure EIGRP I would just create 2 EIGRP intstances as follows:
    router eigrp 200
    router eigrp 201
    With named mode, would I create 1 or 2 named instances for EIGRP? And would every address family need a separate router-id or can both AS nubmers in the default VRF share a router ID?
    example: 1 name mode instance
    router eigrp named1
     address-family ipv4 unicast autonomous-system 200
      af-interface default
       passive-interface
      exit-af-interface
      network 10.10.0.0 0.0.255.255
      eigrp router-id 10.1.1.1
     address-family ipv4 unicast autonomous-system 201
      af-interface default
       passive-interface
      exit-af-interface
      network 10.20.0.0 0.0.255.255
      eigrp router-id 10.1.1.1
    address-family ipv4 unicast vrf server autonomous-system 201
      af-interface default
       passive-interface
      exit-af-interface
      network 10.30.0.0 0.0.255.255
      eigrp router-id 10.3.1.1
    Example 2: 2 named mode instances
    router eigrp named1
     address-family ipv4 unicast autonomous-system 200
      af-interface default
       passive-interface
      exit-af-interface
      network 10.10.0.0 0.0.255.255
      eigrp router-id 10.1.1.1
    router eigrp named2
     address-family ipv4 unicast autonomous-system 201
      af-interface default
       passive-interface
      exit-af-interface
      network 10.20.0.0 0.0.255.255
      eigrp router-id 10.1.1.1
    address-family ipv4 unicast vrf server autonomous-system 201
      af-interface default
       passive-interface
      exit-af-interface
      network 10.30.0.0 0.0.255.255
      eigrp router-id 10.3.1.1
    Any Thoughts? Any help would be appreciated.
    Ben

    Hi Ben,
    Personally, I do not see a significant difference between the two options you have, i.e. having multiple per-VRF EIGRP processes under a single router eigrp instance-name, as opposed to having a separate instance for each VRF. Recall that even in classic numbered configuration mode, you can have multiple per-VRF processes configured under a single numbered EIGRP instance so there is really no specific difference here.
    That being said, I think that you would like the second option better, that is, having a separate EIGRP name mode section for each VRF. In fact, I have found it confusing in the numbered mode to have several VRFs grouped under a single numbered instance whose autonomous system number did not even relate in any way to the autonomous system number in the per-VRF processes.
    Regarding the uniqueness of Router IDs - that's a good question. In EIGRP, the Router ID is used to prevent a router from processing information originated by itself, possibly causing a routing loop. I have always found this explanation somewhat strange, as EIGRP has different mechanisms for loop prevention, and I could never come up with an example where this mechanism would actually be useful. In any case, in newer EIGRP implementations, the RID is attached to each internal and external route as it is advertised throughout the EIGRP domain. This has two important consequences:
    By looking at the show ip eigrp topology X.X.X.X/M.M.M.M output, you can always find out which router originates that particular network
    If a router receives an update about a network marked with its own RID, it will ignore the update.
    If your network and your VRFs are intended to remain perfectly isolated at all times, i.e. no routes from a VRF will ever be advertised across the network so that they leak from one VRF to another, or between a global routing table and a VRF, then a single router can use the same RID in all its EIGRP processes, both in global table and in a VRF. However, if there is an intended possibility of a route existing in one VRF to be advertised over a series of routers and being intentionally received by the same router in a different VRF then using the same RID in multiple EIGRP processes on that router would prevent it from accepting the update. In such case, you would need to use unique RID per each VRF process.
    I hope this helps - please feel welcome to ask further!
    Best regards,
    Peter

  • Setting advertisement / split horizon direction in EIGRP routing

    Hello all,
    I am trying to work out if I am being a bit rubbish or if split horizon is my new worst enemy.
    Below is a diagram of my (simplified) problem scenario using EIGRP.
    The solution I am looking for is that Router R3 learns of the 10.0.0.0/8 network from both R1 and R2, then does not advertise it to either. Simple with split horizon enabled.
    But when either R1 or R2 are rebooted, a decision somehow takes place, and may well determine that R3 should advertise 10/8 to the new (rebooted) neighbour, at which point split horizon prevents it from being advertised back again. This means the topology table on R3 doesn't contain this route for this neighbour and is slow to converge if the other neighbour is lost.
    Is there a way to control in which direction routes are advertised first on a neighbour link? and then I can let split horizon do its thing
    Or is there something I am not thinking of...
    many thanks,
    Paul

    This is what i think would work.
    Two assuptions i'm making -
    1)  R1 and R2 have full routes in terms of the remote branch subnets which from what we have talked about seems to be the case.
    2) R1 will advertise the specific subnets it is primary for (see below) to R3 which then advertises them to R2 and R2 will do the same for it's primary subnets.
    R1 is primary for 32 - 63 summary address 192.168.32.0 255.255.224.0
    R2 is primary for 64 - 95 summary address 192.168.64.0 255.255.224.0
    Each router is secondary for the other router's primary subnets.
    on R1 configure a summary address for R2's subnets on the interface connecting to R3 -
    ip summary-address eigrp <AS no> 192.168.64.0 255.255.224.0
    on R2 do the same for R1's subnets -
    ip summary-address eigrp <AS no> 192.168.32.0 255.255.224.0
    So now -
    R1 points to R3 and R3 points to R2 for 192.168.32.0/19
    R2 points to R3 and R3 points to R1 for 192.168.64.0/19
    Because you have used a summary address this suppresses the advertisement of the more specific routes within that summary range.
    R1 will therefore advertises it's specific subnets for which it is primary to R3 and a summary address only for R2's subnets.
    And R2 does the same ie. it advertises it's specific subnets and a summary for R1's.
    R3 then obviously passes these summaries via EIGRP to R1 and R2.
    R3's routing table will have specific branch routes pointing to the respective
    primary router but only a summary route for the same subnets pointing to the secondary router.
    Because a router will always pick the longest match it will use the more specific subnets unless there isn't a matching route.
    Which means no need to use metrics to load balance traffic.
    In addition the summary route is already in the routing table so no need for either R1 or R2 to send a query to R3 if one of their branch links fail.
    I may well have overlooked something so let me know whether you think this will work for you or not.
    Jon

  • Offset-list to change EIGRP Metrics

    I've got a sup720 that I would like to control which routes in the eigrp topology database get injected into the routing table. There are about 20 entries in the topology database for a specific route all with the same composite metric.
    Any suggestions on how to control which routes populate the routing table?
    Will using the offset-list command and a acl do it? If you guys think that will work could you give me an example of what the acl would look like?
    My network is running just one eigrp process, with no route distribution.
    Thanks in advance!

    Craig
    What you are asking for can be done but it will be a bit tedious. You describe having 20 entries in the topology table and you want to control which one gets placed into the routing table. To do that you can either make the composite metric of the one entry more attractive or you can make the composite metric of the other 19 less attractive.
    When you use an offset list you add to the metric of an entry. It will not make any entry be more attractive but it can make other entries less attractive. So you could configure an offset list identifying the route in question and apply some offset (100 should work for example). Then you would need to apply this offset to the 19 neighbors who are advertising the route.
    HTH
    Rick

  • EIGRP , successor and feasible successor

    what happen in EIGRP if a successor fails and a Feasible successor is not present ?
    i mean if ther'es  route in the topology table but the route for the destination is not a Feasible Successor.
    does the router discard che packet or use the route without the feasibility condition ?

    Hi Joseph,
    You are welcome!
    why when the link R1-R3 was active the link R2-R3 did not met the FC ?
    This question goes back to the definition of the Feasible Distance. The Feasible Distance is a record of the lowest distance towards a particular destination since the last time the destination went from Active to Passive state. The Feasible Distance is therefore not necessarily the current distance, rather, it is a historical minimum of the distance (with the history starting anew with the Active->Passive transition). The Feasible Distance can be reset and newly initialized in the moment of Active->Passive transition (meaning it can also increase during this transition) but otherwise, during a stable Passive state, the Feasible Distance can only decrease.
    If we understand the Feasible Distance as the minimal historical distance to a destination then the Feasibility Condition that says: RD < FD can be put into words as follows:
    Any neighbor who is closer to the destination than we have ever been is not on a routing loop.
    Assuming that in your network, R2 was not considered a feasible successor to 192.168.1.0/24, this tells us that the R2 is not closer to the destination than we have ever been. Why would that be? Well, we can always construct a network in which the link metrics are chosen so that while R2 is not going to route packets back to R1, it won't pass the FC check, like here:
    R1's FD to the destination LAN behind R3 is 16, following the shortest path R1-R3. R2's distance to the same LAN is 18. Notice that R2 is certainly not using the path via R1 - that path would be much longer (20+15+1=36). However, at this point, R2 does not meet the FC check from R1's viewpoint. R1's FD is 16, R2's reported distance is 18, so R1 can not be sure if R2 is or is not using R1 to reach the destination. This is the exact situation where the FC check is actually more strict than necessary but it is better to be too cautious against routing loops than to be too trusting.
    So in this network, R1 does not consider R2 to be a feasible successor because it is not closer to the destination than R1 has ever been (the RD of R2, 18, is more than the FD of R1, 16).
    When the link from R1 to R3 fails, R1 loses its successor, and because the next router, in this case R2, provides the next least cost path but does not meet the FC check, R1 will put the network into active state and start sending Queries. These Queries simply contain the current increased distance of R1 to the destination (in this case, infinity because the path has been totally lost). Basically, R1 is informing its neighbors that its own distance has increased, and expects the neighbors to reevaluate their own choices of successors (subject to their own FDs and FC checks). If R1's increased distance does not influence the neighbor's selection of successor, it simply sends a Reply with the current distance. If, however, R1 has been a successor for some neighbor up to the moment of the distance increase and now, because of the increased distance, R1 does not meet the FC check from that neighbor's viewpoint anymore, that neighbor has just lost a successor and must deal with it exactly in the way I've explained in my first reply. It is possible that this neighbor will also have to put the destination into Active state and start sending Queries itself. This is what is called a Diffusing Computation in EIGRP.
    In this network, after the R1-R3 link is torn down, R1 will indeed send a Query to R2, indicating its current infinite distance to the LAN. However, R2 does not currently consider R1 a successor - it is using R3 as its successor. So, for R2, the increased distance of R1 to the destination is irrelevant as it does not influence its own choice of successor. Here, R2 merely sends back a Reply immediately, indicating its current distance to R1, saying that the distance stays at 18 despite R1's increase of distance. Because R2 is R1's only neighbor, this Reply is the last expected Reply, after which R1 can put the route back into Passive state and reset the FD to the newly found shortest path metric, in this case, the route through R2, with the metric being 20+17+1=38.
    This is why the Active->Passive transition allows you to reset and reinitialize, even increase the FD - because as a result of sending Queries, you have forced your neighbors to reevaluate their own choice of successors. If a neighbor sends you a Reply, you can be sure that it has taken your new increased distance into account and has modified its routing table accordingly - in any case, in such a way there is no routing loop, subject to that neighbor's own FD and its own FC check. Therefore, now you simply choose the least cost path and set the FD to its cost.
    Note that the situation will be different if we change the metrics like this:
    The R1's FD to the LAN is still 16. However, R2's reported distance is 11, so here, it meets the FC check even though it is not considered to be a successor by R1 because the total path through it would be 31. It it still a feasible successor, though.
    Here, if the link between R1 and R3 is torn down, R1 will find in its topology table that R2 provides the next least cost path and it is a feasible successor as well. So here, the route will never enter the Active state - it will remain Passive, just the successor will be changed to R2 and the current distance on R1 will increase to 31. Notice, however, that because we have not gone through the Active state (we did not need to), the FD at R1 will not change and will remain on the previous value of 16!
    This example shows the true behavior of FD. It is a record of the minimum distance to the destination since the last time it entered the Passive state, and is used for FC checks only. It does not necessarily represent the current distance, contrary to the popular - and incorrect - belief.
    Now let's modify this network a little more:
    R1's shortest path to the destination LAN is via R3, with the FD being set to 16. R2's shortest path is via R3 and its distance is 11, therefore, R2 is a feasible successor. R4's shortest path is via R3 as well, and its distance is 18, but because 18 is more than R1's FD of 16, R4 is not considered a feasible successor.
    Note, however, that while R2 is a feasible successor here, the route from R1 through R2 to the destination would have the metric of 31, while the route through R4 - even though R4 is not considered a feasible successor - would have the metric of 23. Quite a difference, isn't it? Now, if R1-R3 link fails, what should R1 do?
    If it decides to go with R2 as the feasible successor, it will surely be using a loop free path but at the same time, that path won't be the shortest one that is available. The path through R4 at this point seems to be shorter but because R4 fails the FC check, R1 is not sure - is R4 actually using R1 as its next hop, or is it using a different router? That is why R1 has to make sure.
    So in this network, if R1-R3 link fails, R1 will find out that the router providing the next least cost path is R4, not R2, and that the R4 does not meet the FC check. So R1 will again go Active and start sending out Queries, indicating its current (infinite) distance to the LAN network. Both R2 and R4 will receive this Query, and because neither of them is using R1 as its next hop, the increased distance on R1 is irrelevant to them, so they immediately send a Reply with their current metrics: R2 replies with 11 and R4 replies with 18. When R1 receives both Reply messages, it goes back to Passive state, resets the FD and chooses the neighbor that provides the least cost path - in this case, R4. The current metric will be set to 23 including the FD, as the FD has been reset. Note that R2 was and has remained a feasible successor all the time - it has never been promoted to successor role.
    Quite a lengthy explanation, I admit - but these are not intuitive facts so it takes a little to digest them.
    Please feel welcome to ask further!
    Best regards,
    Peter

Maybe you are looking for

  • HT1899 I am trying to install Windows 7 via new Full version disc on Macbook Air via Bootcamp.

    I have downloaded the installation guide but am not able to get past the partition stage. Windows partition to 20GB hit install but I get "installation disc not found" continually. I can "see" the Windows DVD on my Remote DVD on my IMAC.

  • Iphone 3gs in recovery mode and gets error on itunes

    Hi my iphone 3gs in stuck recovery mode and gets an unknown error on itunes when afterdownloading ios6 and trying to restore. My phone is useless right now:( I did have a uncomplete cloud backup inprogress when I tried ti update the ios

  • How do I print iPhoto books in another country?

    My iPhoto '09 automatically points to the US site for printing books. I would like to get it to use the UK site and have delivery in the UK. How do I change the settings to achieve this? Regards Jim

  • TV-Out feature in Nokia Phones

    Hello, I was about to buy Nokia N79 or Nokia 5800 Xpress Music, and came to know that the TV out feature has been removed from most of the Nokia phones except higher end ones. I was in despair because this feature was really a important for me and ma

  • I need to create a report using only one record

    I have all this records in my database but i would like to create a layout where it will automatically fill it up with the information of a record i would chose. example: i got a list of over 200 hundred products and i would like to see in a personal