Cisco-Juniper Ping Problem

[itatdanagas]

Dears,

 Our problem seems strange , we have 2x 6807 Core Switches configured as VSS and mix of Edge Switches Juniper EX3200 and Cisco C2960X connected to Core Switches through trunk links.

One of Our ESX Servers - hosting multiple virtual machines -  is connected to the Primary Core Switch Only through 10G interface configured access in Vlan 226.

All edge switches have SVI interface in Vlan 226 as well as indicated in the attached diagram

Problem Description

- All Cisco Edge Switches connected to Primary Core Switch can ping All Servers in Vlan 226

- All Cisco Edge Switches connected to Secondary Core Switch can ping All Servers in Vlan 226

- All Juniper Edge Switches connected to Secondary Core Switch can ping All Servers in Vlan 226

- All Juniper Edge Switches connected to Primary Core Switch can ping some Servers only  in Vlan 226 and can't ping others !!!

Any help for that ?

[johnd2310]

Hi,

Can the servers ping the switches? Do the arp entries on the switches and server match up. Have you traced mac address on the switches and ensured they are on the correct ports?

Thanks

John

[itatdanagas]

Hi John,

only arp of the pingable servers appear , other servers not appear.

i have tried to make mac address trace from the core switch and it seems ok , but ping from the juniper not working

from the servers side , not able to ping the juniper switch connected to the first core , but able to ping Junipers connected to second core .. also able to ping all cisco switches.

[pwwiddicombe]

Can we see the definition of the trunk to the juniper from the first core?  Is there a difference in the native vlan definition between the 2 cisco core switches?

[itatdanagas]

EGCOCSW#sh run int Te1/1/7
Building configuration...

Current configuration : 108 bytes
!
interface TenGigabitEthernet1/1/7
 description EX3200-SW-51
 switchport
 switchport mode trunk
end

all trunk interfaces in both core switches to Juniper or Cisco edge switches are configured in the same manner with native vlan 1 with no change

[johnd2310]

Hi,

Can you try to span some ports and do a network capture of traffic. Capture traffic to and from the servers on the interface to the primary core as well as traffic to and from the juniper that is not working. Check where the pings are disappearing.

Thanks

John

[paul driver]

Hello

All Juniper Edge Switches connected to Primary Core Switch can ping some Servers only  in Vlan 226 and can't ping others !!!

I guess by this statement that the other switches Cisco or Juniper can ping  devices in OTHER vlans also?

My first thought would be a misconfiguration on the Juniper switch , Do these interfaces on the juniper connecting to the Cisco vss have the correct switching mode set with all the relevant vlan members applied, also does it have a default route set?

Can you post the config of the affected juniper switch:

set cli screen-length 0
sh configuration | display set

res
paul

[itatdanagas]

Hi Paul,

Yes other switches cisco or Juniper can ping devices in other Vlans , only the problem in Vlan 226

Due to Security reasons , i will paste only configuration related to the Vlan and trunk interfaces.

Juniper1 (connected to Primary Core can ping some servers in Vlan 226 but not all of them)

> show configuration interfaces xe-0/1/2 | display set
set interfaces xe-0/1/2 description Uplink-EGCOCSW01
set interfaces xe-0/1/2 unit 0 family ethernet-switching port-mode trunk
set interfaces xe-0/1/2 unit 0 family ethernet-switching vlan members all

> show configuration | display set | match 226
set interfaces vlan unit 226 family inet address 10.11.226.191/24
set vlans Apps vlan-id 226
set vlans Apps l3-interface vlan.226

> ping 10.11.226.10
PING 10.11.226.10 (10.11.226.10): 56 data bytes
^C
--- 10.11.226.10 ping statistics ---
1 packets transmitted, 0 packets received, 100% packet loss

> ping 10.11.226.11
PING 10.11.226.11 (10.11.226.11): 56 data bytes
^C
--- 10.11.226.11 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss

> ping 10.11.226.12
PING 10.11.226.12 (10.11.226.12): 56 data bytes
^C
--- 10.11.226.12 ping statistics ---
2 packets transmitted, 0 packets received, 100% packet loss

> ping 10.11.226.13
PING 10.11.226.13 (10.11.226.13): 56 data bytes
64 bytes from 10.11.226.13: icmp_seq=0 ttl=64 time=5.002 ms
^C
--- 10.11.226.13 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 5.002/5.002/5.002/0.000 ms

> ping 10.11.226.14
PING 10.11.226.14 (10.11.226.14): 56 data bytes
64 bytes from 10.11.226.14: icmp_seq=0 ttl=64 time=4.587 ms
^C
--- 10.11.226.14 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max/stddev = 4.587/4.587/4.587/0.000 ms

[itatdanagas]

any update

[itatdanagas]

Thanks all for help , I have opened case with cisco TAC , and we found it's IOS bug , we will change IOS