EIGRP TO EIGRP REDISTRIBUTION Anomaly
Hi There
I have a situation whereby I am redistributing between 2 EIGRP instances and seeing unexpected results. I have labbed up the scenario which is occurring in a production environment and am seeing the same results.
Please refer to the attached jpeg.
As you can see R2 is redistributing into EIGRP 30 from EIGRP 20 via a route map. R2 learns the 172.17.0.0/16 via EIGRP 20 by way of the network command on R1.
The route map on R2 references ACL 10 which has one entry access-list 10 permit 172.17.0.0 0.0.7.255
This route map does not specifically matc the 172.17.0.0/16 network however I am seeing the 172.17.0.0/16 redistributed and learned via the R3 router. I would only have expected an exact match in the route map/ACL 10 Eg. 172.17.0.0 0.0.255.255 to allow redistribution to R3 as opposed to the entry for 172.17.0.0 0.0.7.255. It is as though the route map is acting classfully and ignoring the wildcard mask
R3
R3#sh ip route eigrp 30
172.17.0.0/16 is subnetted, 1 subnets
D EX 172.17.0.0 [170/2588160] via 192.168.10.2, 00:29:24, FastEthernet0/0
I can resolve this to achieve the desired blocking of 172.16.0.0/16 net, but was wondering if this is expected or normal behaviour
this is observed on cisco 2851, flash:c2800nm-adventerprisek9-mz.124-5a.bin ios
Thanks
Hi,
In my view the redistribution is performed as configured.
To achieve what you aim (if I understand it correctly) the ip prefix-list should be used instead of ACL.
You can try to modify your config as follows and see if that is what you have intended:
ip prefix-list DENY-17 permit 172.17.0.0/18
route-map DENY-17 permit 10
match ip address prefix-list DENY-17
Best regards,
Antonin
Similar Messages
-
Hello everyone,
Many pages describing EIGRP say that one of used metrics is the interface MTU. However, the formula for calculating the composite metric does not take MTU into account so the MTU can not affect the composite metric of a route.
I would like to ask how exactly is the MTU used in the EIGRP, then. Thank your for any insights!
With best regards,
PeterPeter
You ask a very good question and I believe that you are on the right track in trying to understand it. Your observation is correct that MTU is a required parameter in specifying EIGRP metric (for redistribution) and is one of the parameters that is advertised. You are also correct in observing that there is nothing in the EIGRP calculation that uses MTU. So the real answer is that the EIGRP specification included MTU but that it does not play any active role in the path selection done by EIGRP.
HTH
Rick -
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 8cJon,
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? -
EIGRP in a NBMA hub and spoke configuration ?
Hi,
Is there a way to configure EIGRP for a Frame Relay NBMA network using a hub and spoke topology ?
I'm curious that I cannot find any config examples for this, whereas with OSPF in this environment there are plenty of examples.
I'm wondering if EIGRP being a distance-vector protocol this shouldn't be attempted.
PS: I've been at this all day and have only managed to get EIGRP to work in one cofiguration and that was using physical interfaces on all routers and switching off split horizon at the hub router. I used frame-relay map statements with broadcast enabled also.
Any pointers would be appreciated.
Cheers,
Phil.hi phil,,,
here is the configuration for the HUB router
! hostname ABC
interface Ethernet1
ip address 192.168.2.1 255.255.255.0
interface Serial0
no ip address
encapsulation frame relay
no ip mroute cache
interface Serial0.1 multipoint
ip address 192.168.1.1 255.255.255.0
no ip split horizon eigrp 2001 Split Horizons disabled
bandwidth 112 Bandwidth set to the sum of the remote PVCs
frame relay map ip 192.168.1.5 110 broadcast
frame relay map ip 192.168.1.6 130 broadcast
router eigrp 2001 EIGRP routing process
network 192.168.1.0 Networks running EIGRP
you can have appropriate IP addressing as per your design...
you can have some easy configuration at spoke side with compere to HUB router....
regards
Devang -
DMVPN Question on NHRP and EIGRP neighbor relations
First of all thank you for your answer, in a DMVPN network, running EIGRP over GRE, will a spoke consider another spoke an EIGRP neighbor? or will it just consider the hub to be an EIGRP neighbor when it comes to sending/receiving eigrp queries/updates? given that in dmvpn setup one spoke can establish a direct tunnel with another spoke.
If you are running EIGRP, under EIGRP type in
no split-horizon eigrp ; where x is the as #.
Also, if your dmvpn routers have default routes ie 0.0.0.0/0 pointing to the ISP on all routers that is ok. IF you have specific static routes for DMVPN hub public on DMVPN spoke router, you would also need to add a static route for the other dmvpn spoke public address on your first dmvpn spoke and vice versa. Hope this helps. -
EIGRP vs BGP route path selection scenario
I am looking for a routing solution to the following scenario. It is a fairly simple design.
I have two WAN connections between sites A and B. One is a 20 Meg Metro Ethernet Circuit running EIGRP. The other is a 10 Meg MPLS running BGP. What do I need to do in my configuration to make sure that the 20 Meg connection is the chosen path based off the fact that it has better speed and bandwidth? It appears to me that the MPLS is the preferred path even though it is slower.
See attached Diagram:
Site A Config
interface GigabitEthernet1/0/12
description PADC COX P2P 20 Meg
no switchport
bandwidth 20480
ip address 172.20.1.1 255.255.255.252
interface GigabitEthernet2/0/2
description LEVEL 3 MPLS
no switchport
bandwidth 10240
ip address 172.22.0.2 255.255.255.252
router eigrp 1
network 10.0.1.0 0.0.0.255
network 172.20.1.0 0.0.0.3
network 192.168.76.8 0.0.0.3
redistribute bgp 65003 metric 100 1 255 1 1500 route-map MPLS_NETWORKS
redistribute static route-map DEFAULT_ROUTE
router bgp 65003
bgp log-neighbor-changes
redistribute static
redistribute eigrp 1
neighbor 172.22.0.1 remote-as 1
default-information originate
Site B Config
interface GigabitEthernet0/1
description COX Communications 10 Meg to Venyu
bandwidth 20480
ip address 172.20.1.2 255.255.255.252
duplex auto
speed auto
service-policy output VOIP
interface GigabitEthernet0/2
description Level 3 MPLS
bandwidth 10240
ip address 172.22.1.2 255.255.255.252
duplex full
speed 100
router eigrp 1
network 10.3.1.0 0.0.0.31
network 10.52.1.0 0.0.0.255
network 10.76.6.0 0.0.0.255
network 172.20.1.0 0.0.0.3
network 192.168.63.64 0.0.0.63
network 192.168.76.249 0.0.0.0
passive-interface default
no passive-interface GigabitEthernet0/0
no passive-interface GigabitEthernet0/1
router bgp 65003
bgp log-neighbor-changes
network 10.3.1.0 mask 255.255.255.224
network 10.52.1.0 mask 255.255.255.0
network 10.76.6.0 mask 255.255.255.0
network 192.168.76.249 mask 255.255.255.255
neighbor 172.22.1.1 remote-as 1If each router is receiving advertisements for the same networks/subnet masks from both BGP and EIGRP it will always choose the BGP routes because they have a lower AD ie. 20 vs EIGRP 90.
Doesn't matter what the bandwidth is.
If you want to prefer the 20Mbps links then there are a number of options -
1) if you can summarise each sites subnets then advertise the summary via BGP and the more specific via EIGRP. More specific will be chosen even before AD is taken into account.
2) change the AD of either BGP or EIGRP so EIGRP ends up with the lower AD
3) run BGP on both links although you would still need to manipulate the attributes to make sure the link you want is used.
Jon -
Hi,
I'm trying to do some lab testing and tested named EIGRP. I was able to understand the EIGRPv6 configuration where you configure the EIGRP statement under the interface and by issuing "no shutdown" under the EIGRP process created. So basically all IPv6 networks that has to be advertised via EIGRP has to have the "ip eigrp xxx" statement under the interface.
Now, I'm trying to do named EIGRP. By simply creating the EIGRP multi-af process and by issuing "no shutdown" under the address-family ipv6 autonomous-system, all interfaces with IPv6 address are being advertised right away and EIGRP peering gets established as well.
Is this the normal behavior? So is it a general practice to shutdown the address-family ipv6 process first and af-interface default to shutdown state, then individually turn on specific af-interface for EIGRP IPv6 processing?
Thanks,
JL
Configuration Below:
R1#sh run
Building configuration...
Current configuration : 1030 bytes
! Last configuration change at 16:23:15 UTC Wed Oct 8 2014
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
hostname R1
boot-start-marker
boot-end-marker
no aaa new-model
ip cef
ipv6 unicast-routing
ipv6 cef
multilink bundle-name authenticated
interface Loopback0
ip address 150.1.1.1 255.255.255.255
ipv6 address 2001:1:1:1::1/128
interface Loopback1
no ip address
ipv6 address 2001:1:1:1::11/128
interface FastEthernet0/0
no ip address
shutdown
speed auto
duplex auto
interface FastEthernet0/1
ip address 155.1.12.1 255.255.255.0
speed auto
duplex auto
ipv6 address 2001:1:1:12::1/64
router eigrp multi_af
address-family ipv6 unicast autonomous-system 100
topology base
exit-af-topology
exit-address-family
ip forward-protocol nd
no ip http server
no ip http secure-server
control-plane
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
end
R1#
R2#sh running-config
Building configuration...
Current configuration : 969 bytes
! Last configuration change at 16:23:26 UTC Wed Oct 8 2014
version 15.2
service timestamps debug datetime msec
service timestamps log datetime msec
hostname R2
boot-start-marker
boot-end-marker
no aaa new-model
ip cef
ipv6 unicast-routing
ipv6 cef
multilink bundle-name authenticated
interface Loopback0
ip address 150.1.2.2 255.255.255.255
delay 1
ipv6 address 2001:1:1:1::2/128
interface FastEthernet0/0
no ip address
shutdown
speed auto
duplex auto
interface FastEthernet0/1
ip address 155.1.12.2 255.255.255.0
speed auto
duplex auto
ipv6 address 2001:1:1:12::2/64
router eigrp multi_af
address-family ipv6 unicast autonomous-system 100
topology base
exit-af-topology
exit-address-family
ip forward-protocol nd
no ip http server
no ip http secure-server
control-plane
line con 0
stopbits 1
line aux 0
stopbits 1
line vty 0 4
login
end
R2#
R1#sh ipv6 route
IPv6 Routing Table - default - 6 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, H - NHRP, I1 - ISIS L1
I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP
EX - EIGRP external, ND - ND Default, NDp - ND Prefix, DCE - Destination
NDr - Redirect, O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1
OE2 - OSPF ext 2, ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, l - LISP
LC 2001:1:1:1::1/128 [0/0]
via Loopback0, receive
D 2001:1:1:1::2/128 [90/107520]
via FE80::C80C:10FF:FEF4:6, FastEthernet0/1
LC 2001:1:1:1::11/128 [0/0]
via Loopback1, receive
C 2001:1:1:12::/64 [0/0]
via FastEthernet0/1, directly connected
L 2001:1:1:12::1/128 [0/0]
via FastEthernet0/1, receive
L FF00::/8 [0/0]
via Null0, receive
R1#
R2#sh ipv6 route
IPv6 Routing Table - default - 6 entries
Codes: C - Connected, L - Local, S - Static, U - Per-user Static route
B - BGP, R - RIP, H - NHRP, I1 - ISIS L1
I2 - ISIS L2, IA - ISIS interarea, IS - ISIS summary, D - EIGRP
EX - EIGRP external, ND - ND Default, NDp - ND Prefix, DCE - Destination
NDr - Redirect, O - OSPF Intra, OI - OSPF Inter, OE1 - OSPF ext 1
OE2 - OSPF ext 2, ON1 - OSPF NSSA ext 1, ON2 - OSPF NSSA ext 2, l - LISP
D 2001:1:1:1::1/128 [90/103040]
via FE80::C80A:10FF:FEF4:6, FastEthernet0/1
LC 2001:1:1:1::2/128 [0/0]
via Loopback0, receive
D 2001:1:1:1::11/128 [90/103040]
via FE80::C80A:10FF:FEF4:6, FastEthernet0/1
C 2001:1:1:12::/64 [0/0]
via FastEthernet0/1, directly connected
L 2001:1:1:12::2/128 [0/0]
via FastEthernet0/1, receive
L FF00::/8 [0/0]
via Null0, receive
R2#The only way I found to disable the automatic route advertisement is to shut the routing process right away after it was created. Go to IPv6 address-family and shut the af-interface default and turn on individual interface that needs to participate. If the routing process is turned on and you added an IPv6 address-family, all interfaces with IPv6 address will automatically participate. So if you already have an IPv4 address-family running in the first place and you want to add IPv6 under the same EIGRP process then it would be ideal to plot it through notepad and paste it to ensure you can have absolute control of the IPv6 advertisement.
That's how I see it and just correct me if I am wrong. -
EIGRP vs Multilink for Load Balancing
I'm planning on implement a solution of VoIP over a 2 parallel WAN links.
Because the bandwidth on both links is less than 512kbps, its important to load balance the traffic between both.
EIGRP its implemented over all the network, so i have the option to use variance to load balance between this links (512kbps and 384kbps)
My second option is tu join both link with MULTILINK.
I want to know which of this options is recomended considering that Data and VoIP will go trought this conection.
Anothe consideration is that i need to implement QoS.
Thanks
Osvaldo U.Hello,
My personal recommendation is to use EIGRP. EIGRP has a feature called Unequal Cost Load Balancing, which basically unequally loads the links between two neighbors based on the link's bandwidth. In the event that one link goes down, EIGRP would immediately redirect all flow over a single link.
Please note that EIGRP is a proprietary routing protocol, so if an ISP is involved between the endpoints, it is unlikely to be supported (look at MLPPP some more) and that with low-bandwidth links, some pretty aggresive QoS settings involving Weighted Random Early Detection (WRED), and Low Latency Queuing (LLQ) will definitely be needed to make the links usable with the lowest amount of jitter as possible.
Something like...
router eigrp
network
network
variance 5
no auto-summary
class-map voicestream
match ef
policy-map wan512
class voicestream
priority 200
class class-default
fair-queue
random-detect dscp-based
policy-map wan384
class voicestream
priority 153
class class-default
fair-queue
random-detect dscp-based
interface serial0/0
ip address
service-policy out wan512
max-reserved-bandwidth 90
interface serial0/1
ip address
service-policy out wan384
max-reserved-bandwidth 90
Ryan -
Cisco 3270 MAR WGB and EIGRP Neighbors
I'm setting up a lab environment where I want to have a 3270 MAR connect to a 1524 MESH AP on the 4.9 Public Safety frequency and form an EIGRP neighbor relationship and perform routing. So far, I can get the MAR associated to the 1524, which is connected to a 2106 running 4.1.192.22M. I have configured the 4.9 Radio on the MAR as a workgroup bridge and infrastructure-client. The radio interface is up, and it is associated. I have defined EIGRP neighbors, the AS numbers and K values match. I can't figure out why the EIGRP neighbor relationship won't come up? I've also configured the MAR as a stub network. I had this working in my lab several months ago, but restoring the configs on each of the devices doesn't result in neighbor formation. Attached is some config info and show commands.
3560_8Port_PoE ---- 2106 ---- 1524_AP )))) (((( ----- 3270_4.9Radio_WGB ---- 3270_MAR
Regards,
ScottUpdate -
Here's an output from back in January when I had it working:
3270_MAR#
*Mar 2 21:41:15.656: %DUAL-5-NBRCHANGE: IP-EIGRP(0) 90: Neighbor 192.168.1.1 (Vlan1) is up: new adjacency <-----------------------LOOK HERE
THIS MEANS THAT THE TWO ROUTERS EXCHANGED 'HELLOS' AND BECAME BUDDIES, SHARING THEIR ROUTING TABLES
3270_MAR#sh 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 192.168.1.1 to network 0.0.0.0
C 192.168.4.0/24 is directly connected, Vlan4
C 192.168.5.0/24 is directly connected, Vlan5
D 192.168.6.0/24 [90/28416] via 192.168.1.1, 00:01:31, Vlan1 <----------------------------- This route was updated using EIGRP
C 192.168.7.0/24 is directly connected, FastEthernet0/0
C 192.168.1.0/24 is directly connected, Vlan1
D 192.168.3.0/24 [90/28416] via 192.168.1.1, 00:01:31, Vlan1
S* 0.0.0.0/0 [1/0] via 192.168.1.1
3270_MAR# -
EIGRP IPv6 and VLAN interfaces
We've found that we have to set static link local IPs when two routers might peer over multiple VLAN interfaces.
The issue is that the routers, 6500s with sup720s, utilize the same autoconfig'd link local address on each VLAN interface. EIGRP IPv6 refuses to peer with the other router on multple VLANs when the link local are the same.
Anyone else encounter this? Did we miss a config option that would force unique link locals on different VLANs interfaces?
Because of this issue, we've made it our best practice to configure static link local for all inter-router transits.HI Gary,
I had a setup with SU720 on 2 7600s and I am able to enable the neighborship without any issues. I didnt configure static link local as below,
Ryanair#show ipv6 int vlan 500 | inc FE
IPv6 is enabled, link-local address is FE80::21C:B0FF:FEB5:6D00
Ryanair#sho ipv6 int vlan 501 | inc FE
IPv6 is enabled, link-local address is FE80::21C:B0FF:FEB5:6D00
Ryanair#show ipv6 eigrp nei
EIGRP-IPv6 neighbors for process 100
H Address Interface Hold Uptime SRTT RTO Q Seq
(sec) (ms) Cnt Num
1 Link-local address: Vl501 11 00:15:51 816 4896 0 13
FE80::222:55FF:FE17:25C0
0 Link-local address: Vl500 11 00:17:14 1 200 0 12
FE80::222:55FF:FE17:25C0
Ryanair#
Can you let us know the version on oth the devices?.
Regards,
Nagendra -
RIP/EIGRP maximum number of Equal cost routes
I am looking for documentation on:
If a router has 20 equal cost routing paths and only 4 show up in the routing table, what is the determining factor that chooses which four and where are the other 16 put in case the 4 routes become unusable.
Most documentation will tell you the maximum amount and how to change it but I have not found any documentation on how EIGRP or RIP chooses the routes.You can have up to 4 by default, but you can configure the routing table to accept up to 6 on older code, and up to 8 on newer code, using the command "maximum-paths" under router eigrp. EIGRP will attempt to install all of the available paths, but the routing table will only allow it to install the first x that it installs.
The routes which are not installed by EIGRP are placed in a "backup table." If one route fails, each routing protocol running on the router is notified, and will attempt to install any routes (which match the destination, of course) back into the routing table. Again, the frst x paths would win.
Be careful with this much redundancy in eigrp--you're playing with fire if you have 15 or 20 links between a pair of routers.Russ -
Hoping someone can help me out here. We have 2-6500 running VSS and also running VRF Lite. The IOS version we are running is: s72033-advipservicesk9_wan-mz.122-33.SXJ2. We have recently enabled IPv6 and I am trying to enable "IPv6 router eigrp x" which works fine but when i try to enable "IPv6 eigrp x" on a Vlan I recieved an unsupported error. Example below:
ipv6 router eigrp 1
eigrp router-id 1.1.1.1
no shut
Vlan100
vrf forwarding DMZ
ip address 192.1168.1.1 255.255.252.0
ipv6 address 2444:4444:4444:4444::1/56
ipv6 enable
end
When i enter the "ipv6 eigrp 1" on the the SVI it errors out. Any idea's?
Thanks!To use EIGRP as a PE-CE protocol for IPv6 you need to use the named EIGRP configuration. Please check out the info at the following URL -
http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_eigrp/configuration/15-sy/ire-ip6-vrf-lte.html. Note here that this feature is not supported in the release that you mention. You will need to upgrade to 15.1(1)SY which is the first release to support both the Sup 2T and Sup 720.
hth,
-jim -
It appears EIGRP only sends the classic-scale-metrics while operating in non-named configuration mode (E.G. router eigrp # ) AND Always sends the wide-metric format while operating in Named Configuration mode (E.G. router eigrp ROCKS) regardless of the 15.2 IOS version.
When my router is running in Named config mode, sh eigrp protocols reveals K6=0,
when I remove the Named config and use the legacy router eigrp # config mode, the same sh eigrp protocols does not list the K6=0 value (only K1 - K5).
The reason I ask is the Cisco white paper (EIGRP Wide Metrics) dated Nov 2012, states if a legacy EIGRP peer is interfacing with a new EIGRP peer, the new EIGRP peer will send both formats. - Is this doc outdated by a newer doc?
Thanks
FrankUpdate- The original title should be referred to as EIGRP Virtual-Instance (that does support the legacy 32-bit metric and just might also support the 64-bit wide metrics; depending on your configuration).
Viewing the show command (Show command 1) based on EXAMPLE CONFIG 1 below, it's clear the K6 value is not used; only the K1 - K5 values.
If address-family vrf was implemented, as shown in EXAMPLE 2, it's clear the new wide-metric is in effect.
The question still remains, how does an EIGRP peer configured to recognize link speeds greater than 10Gbps interact with EIGRP peers that are not operating in 64-bit mode? What do the configurations look like for each of the peers?
ANYONE know?
Thanks
Frank
EXAMPLE CONFIG 1:
router eigrp TEN-GIG
address-family ipv4 unicast autonomous-system 200
topology base
exit-af-topology
network 192.168.1.1 0.0.0.255
exit-address-family
service-family ipv4 autonomous-system 200
sf-interface GigabitEthernet0/1
authentication mode md5
authentication key-chain MD5-PASS
exit-sf-interface
topology base
exit-sf-topology
exit-service-family
SHOW COMMAND 1:
R40#sh eigrp protocols
EIGRP-IPv4 VR(TEN-GIG) Address-Family Protocol for AS(200)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 10.74.10.5
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170
Maximum path: 4
Maximum hopcount 100
Maximum metric variance 1
Total Prefix Count: 6
Total Redist Count: 0
EIGRP-SFv4 VR(TEN-GIG) Service-Family Protocol for AS(200)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 10.74.10.5
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170
Maximum path: 1
Maximum hopcount 100
Maximum metric variance 1
Total Prefix Count: 0
Total Redist Count: 0
EXAMPLE 2:
R-64-bit#sh ip eigrp vrf DMZ topology 192.168.1.0 255.255.255.0
EIGRP-IPv4 VR(DMZ) Topology Entry for AS(200)/ID(10.74.10.5)
Topology(base) TID(0) VRF(DMZ)
EIGRP-IPv4(200): Topology base(0) entry for 192.168.1.0/24
State is Passive, Query origin flag is 1, 1 Successor(s), FD is 1310720, RIB is 10240
Descriptor Blocks:
192.168.1.1 (GigabitEthernet0/1), from 192.168.1.2, Send flag is 0x0
Composite metric is (1310720/65536), route is Internal
Vector metric:
Minimum bandwidth is 1000000 Kbit
Total delay is 10000000 picoseconds
Reliability is 0/255
Load is 1/255
Minimum MTU is 1500
Hop count is 1 -
EIGRP issue "Ignore multicast Hello"
Hi,
The ASA5515 isn't detectng eigrp routes. I have checked and rechecked and can't seem to figure out what the issue is. Below is the output for troubleshooting. Why is it ignoring multicast?
router eigrp 101
neighbor 10.10.YY.3 interface ENS
neighbor 10.10.YY.6 interface ENS
network 10.10.nn.0 255.255.255.0
network 10.10.YY.0 255.255.255.0
redistribute connected
redistribute static
ASA5515-FW#sh eigrp ne
EIGRP-IPv4 neighbors for process 101
ASA5515-FW# debug eigrp packets
EIGRP Packets debugging is on
(UPDATE, REQUEST, QUERY, REPLY, HELLO, PROBE, ACK, STUB, SIAQUERY, SIAREPLY)
ASA5515-FW# EIGRP: Received HELLO on GigabitEthernet0/1 nbr 10.10.YY.3
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 477/456
EIGRP: Ignore multicast Hello GigabitEthernet0/1 10.10.YY.3
EIGRP: Sending HELLO on GigabitEthernet0/1 nbr 10.10.YY.3
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 465/506 iidbQ un/rely 0/0
EIGRP: Sending HELLO on GigabitEthernet0/1 nbr 10.10.YY.6
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 465/506 iidbQ un/rely 0/0
EIGRP: Received HELLO on GigabitEthernet0/1 nbr 10.10.YY.2
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 500/476
EIGRP: Ignore multicast Hello GigabitEthernet0/1 10.10.YY.2
EIGRP: Received HELLO on GigabitEthernet0/1 nbr 10.10.YY.1
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 466/483
EIGRP: Ignore multicast Hello GigabitEthernet0/1 10.10.YY.1
EIGRP: Sending HELLO on GigabitEthernet0/2
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 492/459 iidbQ un/rely 0/0
EIGRP: Received HELLO on GigabitEthernet0/1 nbr 10.10.YY.6
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 482/492
EIGRP: Ignore multicast Hello GigabitEthernet0/1 10.10.YY.6
EIGRP: Received HELLO on GigabitEthernet0/1 nbr 10.10.YY.4
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 511/460
EIGRP: Ignore multicast Hello GigabitEthernet0/1 10.10.YY.4
EIGRP: Received HELLO on GigabitEthernet0/1 nbr 10.10.YY.3
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 508/457
EIGRP: Ignore multicast Hello GigabitEthernet0/1 10.10.YY.3
EIGRP: Sending HELLO on GigabitEthernet0/1 nbr 10.10.YY.3
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 503/451 iidbQ un/rely 0/0
EIGRP: Sending HELLO on GigabitEthernet0/1 nbr 10.10.YY.6
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 503/451 iidbQ un/rely 0/0
EIGRP: Received HELLO on GigabitEthernet0/1 nbr 10.10.YY.2
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 494/502
EIGRP: Ignore multicast Hello GigabitEthernet0/1 10.10.YY.2
EIGRP: Received HELLO on GigabitEthernet0/1 nbr 10.10.YY.1
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 471/467
EIGRP: Ignore multicast Hello GigabitEthernet0/1 10.10.YY.1
EIGRP: Sending HELLO on GigabitEthernet0/2
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 498/466 iidbQ un/rely 0/0
EIGRP: Received HELLO on GigabitEthernet0/1 nbr 10.10.YY.6
AS 6619137, Flags 0x0, Seq 0/0 interfaceQ 477/463
ASA5515-FW# sh eigrp traffic
EIGRP-IPv4 Traffic Statistics for AS 101
Hellos sent/received: 7834702/19594442
Updates sent/received: 0/763
Queries sent/received: 0/287
Replies sent/received: 0/0
Acks sent/received: 0/0
Input queue high water mark 9, 0 drops
SIA-Queries sent/received: 0/0
SIA-Replies sent/received: 0/0
Hello Process ID: 163
PDM Process ID: 162
ASA5515-FW# sh eigrp top
EIGRP-IPv4 Topology Table for AS(101)/ID(75.146.246.107)
Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply,
r - reply Status, s - sia Status
P 0.0.0.0 0.0.0.0, 1 successors, FD is 2816
via Rstatic (2816/0)
P 10.10.zz.0 255.255.255.0, 1 successors, FD is 2816
via Rstatic (2816/0)
P 10.10.cc.0 255.255.255.0, 1 successors, FD is 2816
via Rstatic (2816/0)
P 10.10.bb.0 255.255.255.0, 1 successors, FD is 2816
via Rstatic (2816/0)
P 50.xx.xx.xx 255.255.255.252, 1 successors, FD is 2816
via Rconnected (2816/0)
P 10.10.nn.0 255.255.255.0, 1 successors, FD is 2816
via Connected, GigabitEthernet0/2
via Rconnected (2816/0)
P 75.mm.mm.mm 255.255.255.248, 1 successors, FD is 2816
via Rconnected (2816/0)
P 10.10.YY.0 255.255.255.0, 1 successors, FD is 2816
via Connected, GigabitEthernet0/1
via Rconnected (2816/0)Hey,
Its because you have both static and network statement for neighbor 10.10.YY.3 so EIGRP is communicating on unicast and ignoring multicast.
HTH.
Regards,
RS. -
Problems with running EIGRP as PE-CE routing protocol 2
Dear all,
I am facing with the exact problem as a previous user of running EIGRP as the PE-CE routing protocol for a MPLS VPN customer, but in different hardware. The PE router is a 7609-S RSP720-3CXL-GE running IOS 12.2(33)SRC3.
(When I have 33 prefixes or more in the VRF table on the PE, and I try to advertise this network to the CE router (by redistributing BGP into EIGRP), the EIGRP process begins to flap.
I can't advertise prefix more that 32 subnets at a time why?????
The very weird part here, is that when I do debug ip eigrp on the PE and the CE, I can see that the PE router is sending the routes to the CE, but on the CE I can see nothing.)
In my case there is 16 prefixes. When redistributing BGP into EIGRP on allready adjasent EIGRP neighbors everything works perfect, until some side clears it then it begans flaping. On PE router debug is show "retry limit exceeded" ,on CE "Interface Goodbye received"
If solution will be same what software should I use?
Thanks,
George ShiukashviliGeorge,
Let me ask a few questions:
What is the link layer technology that interconnects the PE and CE that are currently experiencing these issues?
Are there any devices inside the PE-CE path that could at least possibly (and randomly) block multicasts and/or large packets?
Is it possible to modify the EIGRP configuration both on PE and CE to manual neighbor definition using the neighbor commands? This would force all EIGRP comunication between the PE and CE to run as unicast, possibly avoiding some issues with multicast packet delivery.
Is it possible for you to post some show commands from both the PE and CE? I would be interested in seeing the show ip interface, show interfaces, show running-config interface regarding the particular interfaces on PE and CE that connect to each other, and also, I would like to see the EIGRP configuration on both devices.
I agree with the assessment of Mahesh - the preliminary information we have suggest that either the PE packets are not arriving at the CE, or the ACK packets from CE are not arriving back at the PE. Your own debug analysis furthermore revealed that there are no EIGRP Update packets arriving from the PE at the CE. Problems with MTU could indeed cause these problems but it is necessary to inspect the entire path between PE and CE.
Best regards,
Peter
Maybe you are looking for
-
Render time changed from 10 to 56 hours. Help!
Hi, we are working on a wedding video of 3 hours. Earlier when we rendered it last week, it took around 11 hours to finish. After that, we have only very few changes to the video. For example, we installed Red Gaint Looks and also used Lumitri Looks
-
CBO (optimizer) nest-loop join question
OS: Red Hat Linux DB: 11gR1 I have gotten two conflicting answers while reading books by Don Burleson and Dan Hotka. It has to do with the CBO and nested-joins: One says the CBO will choose the 'smaller' table as the driving table, the other states t
-
SAP Screen Personas Performance in the real world
I've read the blogs, Personas are amazing the user does much less clicking, etc, but in the real world is anyone using this in production, for a widescale deployment? I've tried this in my system and although it's cute, and at first people have fun c
-
After Mav update, all options under the Erase tab in Disk Utility are greyed out. I want to erase free space from the startup drive, and this was permitted under earlier OS versions. That drive is an SSD (does it matter?). If I wanted to erase an ext
-
Any insights to this problem would be greatly appreciated: I had developed an application that reads from a text file consisting of millions of INSERT statements and writing them into an Access database. The application uses the JdbcOdbc Bridge. I kn