SG200-18 <-> C2960S trunked - SG200 cut off the net
Still trying to figure out how to connect our new SG200-18 to an existing Cisco network, in particular a C2960S.
Here's what I've got:
<----- Rest of network ------- C2960S ----------- SG200 ----- (PC connected directly to the SG200)
On the C2960S-side here's what I've got on the corresponding interface:
switchport mode trunk
On the SG200-side I've set the IP-address and default-gateway accordingly, however:
From the SG200 I can't ping any other host on the same IP-subnet as the switch
From the SG200 can't ping the default-gateway
can't ping from any other host or the default-gateway *to* the switch
On the SG200 I've got plenty of MAC-addresses under "Dynamic Address Table" - however only MAC-addresses that belong to the management-VLAN of the SG200 (i.e. VLAN9 in my case)
The MAC-address table on the SG200 even includes the MAC-addresses of hosts on the same VLAN I tried to ping without success. For example: I tried a PING from a host having a MAC-address of 00:19:bb:31:91:30. This MAC shows up in the arp table of the SG200.
To cross check I connected a dedicated PC to the SG200 and assign it an IP-address out of the management-LAN-range of the SG200 - in this case I can access the switch (i.e. PING, WEB etc.)
So to summarize:
Connectivity is OK when going from directly connected devices to the SG200.
No connectivity from devices that are behind the C2960S towards the SG200 and vice versa. (The problem is definitely not with the C2960S-side since we've got plenty of them hooked together without problems.)
I'm enclosing the screenshots of the corresponding definitions on the SG200.
Introduction:Topology Diagram:Configuration Overview:Related
Information: Introduction: This document describes how to connect SG300
with Catalyst switch via STP. Spanning Tree Protocol (STP) is a Layer 2
protocol that runs on mainly on switches. The spec...
The Sx500 Series Stackable Switches offers different port features. You
can add security to a port, make the port more energy efficient, map a
VLAN to a port, make a port available or not to a specific network
portion, and so forth. The next set of articl...
Recently, HP Networking published a blog post attempting to counter the
favorable third party Miercom report on our Cisco® 200 and 300 Series
Smart and Managed switches: