All Vlans from Network 1 seem to be communicating properly between the 3550 and SF300-24 and is isolated from the Transport Network by QnQ. I am having one problem, I can not ping the SF300-24 or get to the management interface. I am able to access other devices on the SF300-24 Vlan1 from devices on the 3550 Vlan1 and vice versa. Any suggestions and/or comments?
Re: Can't Access Management Interface on SF300-24 over QnQ?
I am now able to PING the SF300-24, but network traffic is not working as desired.
When we have the Trunk ports of the Transport Switches connected by Ethernet Cable everything works as desired. When we put the Wireless Bridge in place we have issues. Devices on each side of the Customer switches get DHCP from their respective Vlans, some data flows, some does not. Able to get Internet from the correct Gateway, able to connect to Exchange, able to Ping Servers and devices back and forth. Not able to connect to network folders, SIP registrations, or GUI based devices. Again, this all works when the Wireless Bridge is removed and both transport switches are connected by Ethernet.
Any suggestions on what could be causing these problems?
[toc:faq]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 specification for STP is
IEEE 802.1D. The main purpose of STP is to e...
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...
On a technical level, Cisco 300 Series is far superior to the HP 1910
and 2530 products. This document provides evidence that Cisco has >100
features not supported by the HP platforms. Check this out and decide
for yourselves. Notes (2/5/2014):- Informati...