ā10-24-2011 11:58 PM - edited ā03-04-2019 02:02 PM
We recently installed a Catalyst 6500-e core for our school's network. The VLAN service for the Apple servers is running super slow. It takes between 4 - 8 seconds to connect to our file servers and about everyone week we have to restart our Open Directory server. We just installed this replacing a older Catalyst 4500 moved over the same setting files but all is not well. We never had any of these issues before. We don't know what is causing the poor performance. Any help would be greatly appreciated.
ā10-27-2011 05:45 AM
Hi,
I would start checking interface on 6k for drops. Also would check "sh span det | i exec|of top|from" for any STP TCNs. Please also check if CPU is stable.
If you can pls attch:
sh tech
sh span det | i exec|of top|from
small diagram with port connected to apple servers and users mentioned
Nik
ā10-27-2011 03:09 PM
Thanks for the tips, I'll work on getting that info. Here is a recent Pic of CPU history. This was taken at 2011-10-27 at 5.26.37 PM
ā10-27-2011 08:47 PM
here's the out put for:
sh span det | i exec|of top|from
VLAN0001 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 26 last change occurred 00:51:13 ago
from TenGigabitEthernet1/2
VLAN0004 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0010 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0020 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0030 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 3 last change occurred 3d01h ago
from GigabitEthernet9/3
VLAN0051 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0052 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 9 last change occurred 2d02h ago
from TenGigabitEthernet1/8
VLAN0053 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 17 last change occurred 2d02h ago
from GigabitEthernet3/4
VLAN0054 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0055 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0056 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0059 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0064 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0068 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0072 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 18 last change occurred 2d02h ago
from TenGigabitEthernet1/6
VLAN0074 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 113 last change occurred 1d22h ago
from TenGigabitEthernet1/2
VLAN0080 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 49 last change occurred 1d23h ago
from TenGigabitEthernet1/8
VLAN0090 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 7 last change occurred 2d22h ago
from TenGigabitEthernet1/1
VLAN0092 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 10 last change occurred 2d05h ago
from TenGigabitEthernet1/3
VLAN0100 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0150 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0160 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0170 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0192 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
VLAN0200 is executing the ieee compatible Spanning Tree protocol
Number of topology changes 1 last change occurred 3d19h ago
from GigabitEthernet3/1
ā10-27-2011 03:25 PM
The VLAN service for the Apple servers is running super slow.
I hope your servers are all connected to a 6748 blade and not a 6148 or 6548.
ā10-27-2011 03:33 PM
that's the first thing I'll check this morning. Thanks for the tip
ā10-27-2011 06:41 PM
Good news the xServers are connected to WS-X6748-GE-TX
ā10-27-2011 07:39 PM
That's good news.
So if you can post the output to the command "sh interface
ā10-27-2011 08:44 PM
got this reponse from that command:
catalyst6509E#sh interface
^
% Invalid input detected at '^' marker.
ā10-27-2011 08:46 PM
that didn't show correct it looks like this
ā10-27-2011 09:05 PM
Hi Brian
Please include the interface number e.g Gi1/0/2 for the Interface which connects physically to the Apple Server....
sh int Gi1/0/2 ---replace Gi1/0/2 by actual interface number please.
Regards
Varma
ā10-27-2011 09:14 PM
this is the vlan for the Servers, I'll working finding the details for the actual interface. The picture above is the actual interface for the servers. Would I use what is seen in the picture?
ā10-27-2011 09:17 PM
This isn't right. This is the VLAN interface.
The data for the physical interface would be good.
ā10-27-2011 09:21 PM
Hi Brian
Do you know the Apple Server's IP. If yes then please do as below:
sh arp | in x.x.x.x ---------replace x.x.x.x by Apple Server IP..
Note and copy the mac-address from above and issue below command
show mac-address-table | in xxxx.yyyy.zzzz ----replacex it by mac-address captured above and you will see the actual physical interface for the apple server .
Other way rouund will be to note the port number on the x6748 card and note the slot in which x6748 is installed in c6500 and we can find port as
GiSlot/0/Port
You can try both and if the results match so we are double confirmed to go ahead. Please find out the interface and capture the sh int snapshot so the experts working with you can help you out in your issue
Hope this helps to answer your query.
Regards
Varma
ā10-30-2011 07:29 PM
excellent, thanks for the tips for here are the results:
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide