6

The problem is not the traffic from the server to the switch, but the return traffic, from the switch to the server. Since the VLAN is native, the switch will sent the traffic for this VLAN untagged, while the server expect it tagged. So this cannot work as is. You should probably use this VLAN only for PXE boot and configure your server Operating ...


3

BPDUs are not forwarded, generally. BPDUs are generated and sent on all links, including blocked ones. Topology information contained in the BPDUs can be considered to be forwarded, but the BPDUs themselves aren't. "Dumb" (unmanaged) switches often forward BPDUs even though they're not suppposed to - see IEEE 802.1Q 8.6.3: The [...] group address ...


3

This question has been asked at least a dozen times. We can only guess why the spec says what it says -- no one here wrote it. Despite what the spec says, no one does that -- "ingress filtering" is always enabled on a VLAN aware switch: if vlan 20 isn't not assigned to the port, anything tagged 20 will be dropped. As for untagged traffic, yes, it too (...


3

You can use: show interface status If you want to see MAC addresses show mac address [dynamic] For a specific interface: show mac address [dynamic] interface <interface-name> For a specific vlan: show mac address [dynamic] vlan <vlan number>


2

Ok, I think I found the answer (finally...) here: Manually configured and auto-generated sticky MAC address entries are automatically saved in a .ztbl or .ctbl file every 10 minutes. Alternatively, you can run the save command to manually save them. The saved file is not discarded after the device restarts. The file name must be the same as that of the ...


2

Why does a chain of switches having proper trunk configuration between them DROP packets? It doesn't unless there's congestion, or the trunk configuration is not proper. In your case the key is "the active VLAN interface is not up". Depending on the exact behavior of the switch, either all interfaces associated with the VLAN are down or the VLAN itself is ...


2

Cisco created SPAN (Switch Port ANalyzer) for its switches as an aid to troubleshooting things on a network. It is designed to be enabled while troubleshooting, then disabled. Some other switch vendors do something similar, and others do not. Even with a particular vendor, some models may be able to do it, and some not, and it may be differently configured ...


2

Based on your comments, you do not seem to understand that any frames sent to that MAC address will arrive on that switch interface, regardless of whether or not the switch has the MAC address in its MAC address table. Switches will flood unknown unicast MAC addresses (those not in its MAC address table) to every switch interface A frame sent by Host2 will ...


2

There were, in fact, dedicated X.25 hardware switches produced by the likes of BBN (and others) in the late 70's and into the 80's. Pictures of this sort of thing would be the domain of various museums out there, as dedicated X.25 switches were retired by the early 90's (nb - obviously some amount of this stuff probably persisted in some dusty corner, likely ...


1

Historically, Frame and ATM used purpose built devices. X.25 is a bit before my time, so I don't know if anyone had hardware switches for it. Today, almost everything is done with "soft switch" gear -- i.e. software. A Cisco IOS router can be configured to perform frame-relay, atm, and x.25 switching. MPLS is functionally just a fancy [simpler, ...


1

Switches learn MAC addresses from the frames they receive. If you could find a way to flood a frame with the MAC of your server, every switch would learn it.


1

An access port that receives tagged traffic will drop the tagged frames.


1

Whenever you want to use VLANs, make sure that the VLANs were created on the switches that use those VLANs. You can look at the VLAN database (vlan.dat file) to make sure. If you use VTP, it may spread the created VLANs to all the switches, but VTP is sometimes problematic, and it can be a security risk, so a best practice is to set the VTP to Transparent ...


1

You will need to add those VLANs to the Dell Switch. The commands to do so are likely the same (or you could try managing the device via the web browser which is likely easier if you are not comfortable.) Once you have created those VLANs on the switch, you need to make sure the connection between the Dell and the HP is a trunk link. There are access ports ...


1

Yes ! Vlan 10 connected host on different switch communicate each other . But following Configuration is required on switches Ensure both switch connected with access ports and allow Vlan 10 In Switch1 Swith1(config)#int ethernet 0/0 Switch1(config)#switchport mode access Switch1(config)#switchport access vlan 10 Switch1(config)#no shutdown Switch2 Swith2(...


Only top voted, non community-wiki answers of a minimum length are eligible