cannot ping between interfaces on ME3600X

[jtowry]

I have a ME3600X with AdvancedMetroIPAccess license. I don't seem to be able to ping between hosts from 1 interface to another. The gateway for the hosts is this device. When I do a debug packet on the 3600 the only packets that are showing up are the pings to the 3600, the traffic going to the other host doesn't show even though on the remote switch the debugs show it being sent.

[Reza Sharifi]

Try changing the port-type to uni for the interfaces and test again.

interface xxx

port-type uni

HTH

[jtowry]

Thanks for the quick response. I tried to change the port-type to uni but only have the option for nni.

(config-if)#port-type ?
  nni  Set port-type to NNI

Tried also to add "no port-type nni" under the interface but it made no difference.

[Reza Sharifi]

Are the 2 ports in a vlan?

can you post the config for these ports?

[jtowry]

The 3600 and 2960 are connected by a trunk. The servers are connected via a trunk also.

ME3600X#sh run int vlan 999

Current configuration : 113 bytes
!
interface Vlan999
 ip address 168.31.64.102 255.255.255.248
end

ME3600X#sh run int vlan 650

Current configuration : 207 bytes
!
interface Vlan650
 description Mgmt OAM SVI
 ip address 172.16.169.65 255.255.255.224
end

ME3600X#sh run int t0/1

Current configuration : 171 bytes
!
interface TenGigabitEthernet0/1
 description Fulton Co BOE (New)
 port-type nni
 switchport trunk allowed vlan 650,700,999
 switchport mode trunk
 load-interval 30
end

ME3600X#sh run int g0/24
Building configuration...

Current configuration : 139 bytes
!
interface GigabitEthernet0/24
 description Server Data
 port-type nni
 switchport trunk allowed vlan 650,999
 switchport mode trunk
end

2960#sh run int t1/0/1

Current configuration : 162 bytes
!
interface TenGigabitEthernet1/0/1
 description Uplink to ME3600X
 switchport trunk allowed vlan 650,700,999
 switchport mode trunk
 load-interval 30
end

2960#sh run int vlan650

Current configuration : 93 bytes
!
interface Vlan650
 description Mgmt OAM SVI
 ip address 172.16.169.66 255.255.255.224
end

I also have the same problem if I try to ping addresses in those vlans from the other end of the GRE tunnel that terminates on the 3600. From the address that is on the 3600X side of the tunnel it works.

interface Tunnel2
 description Main site
 ip address 172.16.250.14 255.255.255.252
 tunnel source 168.31.64.102
 tunnel destination 24.179.0.66

ping 172.16.169.66 source 172.16.250.14

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.169.66, timeout is 2 seconds:
Packet sent with a source address of 172.16.250.14
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/3/8 ms

From the other end of the tunnel it fails.

ASR-1
interface Tunnel108
 description Remote side
 ip address 172.16.250.13 255.255.255.252
 tunnel source 24.179.0.66
 tunnel destination 168.31.64.102
end

ASR-1#sh ip ro 172.16.169.64
Routing entry for 172.16.169.64/27
  Known via "static", distance 1, metric 0
  Redistributing via ospf 16, eigrp 21
  Routing Descriptor Blocks:
  * 172.16.250.14
      Route metric is 0, traffic share count is 1

ASR-1#ping 172.16.169.65 source 172.16.250.13
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.169.65, timeout is 2 seconds:
Packet sent with a source address of 172.16.250.13
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 38/38/39 ms

ASR-1#ping 172.16.169.66 source 172.16.250.13
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.169.66, timeout is 2 seconds:
Packet sent with a source address of 172.16.250.13
.....
Success rate is 0 percent (0/5)