Hello Chris,
Are you saying all clients having issue are directly connected to the core or just this virtual server?
Also you haven't stated what interface the Virtual server is connected too?
I can see from the outputs you have posted that spanning tree on the trunk link connection from core switch gig0/50 connecting to sw00-3560-02 gig0/49 is only allowing vlan 10,172
Is this the switch the clients that cannot ping the server are located?
Also your core switch logs are reporting a traceback error - cisco output interpreter suggests this:
%IP-3-LOOPPAK (x1): Looping packet detected and dropped - src=[int], dst=[int],hl=[int], tl=[int], prot=[int], sport=[int], dport=[int] in=[chars], nexthop=[int],out=[chars]options=[chars]Explanation: A looping packet has been detected. A very common cause is misconfiguration
of an IP helper address. The helper address should be the same address as that
of the server of the intended service. Putting the address of the router in the
helper address causes a routing loop to be created.
Recommended Action: Analyze the source and destination addresses of the looped
packets and verify that the configuration of the IP helper addresses in the router
is correctly pointing to the proper device and is not pointing to the router itself.
On the switches
sw00-3560-01 and sw00-3560-02
can you post :
sh spanning-tree summary
sh spanning-tree vlan 4,10,104
sh spanning-tree blockedports
and on sw00-3560-02 also
Sh int trunk
sh cdp neigbours
Sh vlan brief
Sh log
res
Paul
Please don't forget to rate any posts that have been helpful.
Thanks.
Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.
Kind Regards
Paul
