So D3 and D4 are correctly getting the static routes?

Yes, they get two static routes as expected, but originating routers are DW1 and DW2 instead of core-1 and core-2. 

What switch is the config above from ?

If it is one of the core switches then from DW1s IP routing table it is getting those routes.

Note that with the statics in the config above you have the same route twice but one has a higher AD so this would not be installed in the routing table and so would not be redistributed.

So if the config is from a core switch then DW1s routing table looks correct to me.

Perhaps you could clarify exactly what the issue is you are seeing.

Jon

yes, it is core-1 switch config. 

I expected two equal distance static routes in DW1 and DW2, but they only has one static routes and the originating routers are each other. But for DW3-6, they have equal distance static routes, and originating routers are DW1 and DW2 instead of core-1 and core-2. 

It's really not clear what you mean.

When you say you expect equal distance static routes do you mean each core switch is redistributing those static routes into EIGRP ?

If so are the links the same speed from DW1 and DW2 to both core switches ?

Are you doing any redistribution of statics on any of the DW switches ?

Jon

Yes, each core switch is redistributing their static routes to EIGRP. 

the link speeds are the same. 

there are no static routes configured in DW switches nor redistribute static routes. 

following is partial config for DW1. 

DW1(other DW switch configs are about the same.)

vlan 50
!
vlan 200
!
vlan 210
!

!
!
interface Port-channel1
 switchport trunk encapsulation dot1q
 switchport trunk allowed vlan 50,200,210,260,1203
 switchport mode trunk
!

interface GigabitEthernet1/1/1
 no switchport
 ip address 10.111.207.82 255.255.255.252
 srr-queue bandwidth share 10 10 60 20
 queue-set 2
 priority-queue out 
 mls qos trust device cisco-phone
 mls qos trust dscp
 auto qos voip cisco-phone 
 service-policy input AutoQoS-Police-CiscoPhone
!
interface GigabitEthernet1/1/2
 no switchport
 ip address 10.111.207.86 255.255.255.252
 srr-queue bandwidth share 10 10 60 20
 queue-set 2
 priority-queue out 
 mls qos trust device cisco-phone
 mls qos trust dscp
 auto qos voip cisco-phone 
 service-policy input AutoQoS-Police-CiscoPhone
!
interface GigabitEthernet1/1/3
 switchport trunk encapsulation dot1q
 switchport trunk allowed vlan 50,200,210,260,1203
 switchport mode trunk
 channel-group 1 mode desirable
!
interface GigabitEthernet1/1/4
 switchport trunk encapsulation dot1q
 switchport trunk allowed vlan 50,200,210,260,1203
 switchport mode trunk
 channel-group 1 mode desirable

interface Vlan50
 description OA_GUEST
 ip address 192.168.50.2 255.255.255.0
 ip helper-address 10.111.205.143
 standby 50 ip 192.168.50.1
 standby 50 priority 105
 standby 50 preempt
!
interface Vlan200
 description OA_DATA
 ip address 10.111.200.2 255.255.255.0
 ip helper-address 10.111.205.143
 standby 200 ip 10.111.200.1
 standby 200 priority 105
 standby 200 preempt
!
interface Vlan210
 description OA_VOICE
 ip address 10.111.201.2 255.255.255.0
 ip helper-address 10.111.205.143
 standby 201 ip 10.111.201.1
 standby 201 priority 105
 standby 201 preempt

!
router eigrp 100
 network 10.111.200.0 0.0.0.255
 network 10.111.201.0 0.0.0.255
 network 10.111.207.80 0.0.0.3
 network 10.111.207.84 0.0.0.3
 network 192.168.50.0
 eigrp stub connected summary

core1(core2's config is identical)

vlan 270

interface GigabitEthernet3/13
 no switchport
 ip address 10.111.207.81 255.255.255.252
 auto qos voip trust 
 service-policy input AutoQos-VoIP-Input-Dscp-Policy
 service-policy output AutoQos-VoIP-Output-Policy
!

interface GigabitEthernet3/15
 no switchport
 ip address 10.111.207.89 255.255.255.252
 auto qos voip trust 
 service-policy input AutoQos-VoIP-Input-Dscp-Policy
 service-policy output AutoQos-VoIP-Output-Policy

interface GigabitEthernet3/25
 no switchport
 ip address 10.111.207.97 255.255.255.252

!
interface GigabitEthernet3/27
 no switchport
 ip address 10.111.207.105 255.255.255.252
!

interface GigabitEthernet3/47
 switchport trunk allowed vlan 270
 switchport mode trunk
 channel-group 1 mode desirable
!
interface GigabitEthernet3/48
 switchport trunk allowed vlan 270
 switchport mode trunk
 channel-group 1 mode desirable

!
interface GigabitEthernet5/45
 no switchport
 ip address 10.111.207.41 255.255.255.252
 speed 100
 duplex full

!
interface Vlan1
 no ip address
!
interface Vlan270
 ip address 10.111.207.2 255.255.255.240
 standby ip 10.111.207.1
 standby priority 105
 standby preempt

router eigrp 100
 network 10.111.207.0 0.0.0.15
 network 10.111.207.16 0.0.0.3
 network 10.111.207.20 0.0.0.3
 network 10.111.207.64 0.0.0.31
 network 10.111.207.96 0.0.0.15
 no auto-summary
 redistribute static
!
ip route 0.0.0.0 0.0.0.0 10.111.207.4
ip route 10.0.0.0 255.0.0.0 10.111.207.42
ip route 10.0.0.0 255.0.0.0 10.111.207.3 10

ip route 0.0.0.0 0.0.0.0 10.111.207.4
ip route 10.0.0.0 255.0.0.0 10.111.207.42

what are these next hops ie. which switches or other L3 devices.

I think we can only get to the bottom of this if we know all the IPs.

Jon

Thanks Jon for your prompt replies. 

ip route 0.0.0.0 0.0.0.0 10.111.207.4 - this is Cisco ASA connected to ISP
ip route 10.0.0.0 255.0.0.0 10.111.207.42 - this is Cisco router for MPLS.
ip route 10.0.0.0 255.0.0.0 10.111.207.3 10 - this is core-2 switch. 

How are the ASA and core MPLS router connected to the core switches. Are they dual honed to both core switches ?

Can you from each DS switch post a -

"sh ip eigrp topology <network/mask> all-links"

for both the routes.

You can post the outputs into a file and attach it to the post to keep the thread manageable but don't worry if not, just post into the thread.

Also you say DSW3/4 are showing all routes but with DSW1/2 as the originating routers.

What happens if you do a traceroute to the core MPLS router from DSW3. Does it go to one of the core switches and then to the MPLS router ?

Finally i am assuming the schematic you provided is complete ie. there are no other connections between the DSW switches other than to the core switches ?

Jon

We have two ASAs, one ASA(Active) is connected to core-1 and the other ASA(standby) is connected to core-2.

We have one MPLS router. one of the interfaces is connected to core-1, and another interface is connected to core-2. 

I have attached the output of "sh ip eigrp topology all-links" and sh ip eigrp topology 0.0.0.0/0 and 10.0.0.0/8". 

If I traceroute to the MPLS router, below is the output. it goes to core switches. 10.111.207.65 and 69 is core switch interface IPs.

traceroute 10.111.207.42

Type escape sequence to abort.
Tracing the route to 10.111.207.42

  1 10.111.207.65 0 msec
    10.111.207.69 0 msec
    10.111.207.65 8 msec
  2  *  *  *
  3  *  *  *
  4  *  *  *
  5  *
CCR-3750X-1#ping 10.111.207.42

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.111.207.42, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/8 ms

There are no connections between DSW groups, but connections within the groups. ie. DSW1 <-> DSW2, DSW3 <->DSW4, DSW5 <-> DSW6

Paul

Paul

Thanks for the additional information.

However i cannot read your attachements. I have downloaded a unzip utility and it still won't read them.

Not sure how to open them but could you not save them simply as text files and then zip that up ?

Edit - okay i just needed to add a suffix to the files. I can read them now.

Jon

Paul

Just in case you didn't see the edit i can read the files now.

Jon

DSW1/2 are only seeing the one route even in the full topology table.

So if you do a "sh ip eigrp neigh" on those switches do you see a neighborship with each core switch ?

Compare the same with DSW3/4.

Jon