cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
337
Views
0
Helpful
1
Replies

Latency Problem

tarun209
Level 1
Level 1

Hi Friends

I have got a setup where there are two core switches with vlans created on them.when i try to ping from a pc which is directly connected to core switch i got 10ms to 15ms response in between.This is happening in all vlans

Here is the core config

Using 4247 out of 524280 bytes, uncompressed size = 22351 bytes

Uncompressed configuration from 4247 bytes to 22351 bytes

!

version 12.2

no service pad

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

service compress-config

!

hostname EVS-Core1

!

boot-start-marker

boot-end-marker

!

enable password cisco

!

no aaa new-model

ip subnet-zero

!

!

!

!

no file verify auto

spanning-tree mode pvst

spanning-tree extend system-id

power redundancy-mode redundant

!

!

!

vlan internal allocation policy ascending

!

interface Port-channel1

switchport

switchport trunk encapsulation dot1q

switchport mode trunk

!

interface GigabitEthernet1/1

switchport trunk encapsulation dot1q

switchport mode trunk

channel-group 1 mode on

!

interface GigabitEthernet1/2

switchport trunk encapsulation dot1q

switchport mode trunk

channel-group 1 mode on

!

interface GigabitEthernet2/1

switchport trunk encapsulation dot1q

switchport mode trunk

!

interface GigabitEthernet2/2

!

interface GigabitEthernet2/3

!

interface GigabitEthernet2/4

!

interface GigabitEthernet2/5

!

interface GigabitEthernet2/6

!

interface FastEthernet3/1

switchport access vlan 3

switchport mode access

spanning-tree portfast

!

interface FastEthernet3/2

switchport access vlan 3

switchport mode access

spanning-tree portfast

!

interface FastEthernet3/3

switchport access vlan 3

switchport mode access

spanning-tree portfast

!

interface FastEthernet3/4

switchport access vlan 3

switchport mode access

spanning-tree portfast

!

interface FastEthernet3/5

switchport access vlan 3

switchport mode access

spanning-tree portfast

!

interface FastEthernet3/6

switchport access vlan 3

switchport mode access

spanning-tree portfast

!

interface FastEthernet3/7

switchport access vlan 3

switchport mode access

spanning-tree portfast

!

interface FastEthernet3/8

switchport access vlan 3

switchport mode access

spanning-tree portfast

!

interface FastEthernet3/9

switchport access vlan 3

switchport mode access

spanning-tree portfast

!

interface GigabitEthernet6/48

switchport access vlan 10

switchport mode access

!

interface Vlan1

ip address

!

interface Vlan2

ip address

ip helper-address

no ip redirects

standby 2 ip

standby 2 priority 110

standby 2 preempt

!

interface Vlan3

ip address

ip helper-address

no ip redirects

standby 3 ip

standby 3 priority 110

standby 3 preempt

!

interface Vlan4

ip address

ip helper-address

no ip redirects

standby 4 ip

standby 4 priority 110

standby 4 preempt

!

interface Vlan5

ip address

ip helper-address

no ip redirects

standby 5 ip

standby 5 priority 110

standby 5 preempt

!

interface Vlan6

ip address

ip helper-address

no ip redirects

standby 6 ip

standby 6 priority 110

standby 6 preempt

!

interface Vlan10

ip address

ip helper-address

no ip redirects

standby 10 ip

standby 10 priority 110

standby 10 preempt

!

ip route

ip http server

!

!

!

!

!

line con 0

stopbits 1

line vty 0 4

no login

!

ntp authentication-key xxx

ntp authenticate

ntp trusted-key 1

ntp clock-period 17179342

ntp server 172.16.1.1

!

end

Can anybody suggest whatmay be the issue

Regards

Tarun

1 Reply 1

Prashanth Krishnappa
Cisco Employee
Cisco Employee

ICMP destined for the switch itself is a low priority task. Try pinging from a device to another device(this way the ping packet is like any other data packet for the switch).

http://www.cisco.com/warp/public/473/82.html#ping