Switches / Hubs
--
Questions
--
Followers
Top Experts
Bridge/Trunking/Switch problem [Diagram Inside]
I'm trying to figure out a problem. Are my labels correct? Do the ports on the switches connecting to the bridge need to be trunked? I want to pass the VLAN's to the switch on the other side of the non-root bridge. The problem I'm having now is getting the bridge and switch on the non-root side to talk to each other. The bridge authenticates against the root bridge but I can't telnet from the non-root bridge to the switch directly connected to it.
Should the ports be trunked? If so, is this a correct config?
switchport trunk native vlan 55
switchport mode trunk
Drawing1.jpg
Should the ports be trunked? If so, is this a correct config?
switchport trunk native vlan 55
switchport mode trunk
Drawing1.jpg
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
if you need to pass vlans, then ports should be trunked, but with additional option:
switchport trunk native vlan 55
switchport mode trunk
switchport trunk allowed vlan 55,51 <possibly others you want to transmit>
switchport trunk native vlan 55
switchport mode trunk
switchport trunk allowed vlan 55,51 <possibly others you want to transmit>
Still not sure what the problem is. I dont think its a switching problem.
I moved the configured switch to another closet with an existing 350 nonroot bridge and the switch works fine.
When I put it back in the closet with the NEW 1310 nonroot bridge, it doesnt work.
The weird thing is, the 1310 associates fine with the root bridge. I can even ping everything from the CLI of the 1310.
Seems to be a problem between the 1310 and the switch. Any ideas?
I moved the configured switch to another closet with an existing 350 nonroot bridge and the switch works fine.
When I put it back in the closet with the NEW 1310 nonroot bridge, it doesnt work.
The weird thing is, the 1310 associates fine with the root bridge. I can even ping everything from the CLI of the 1310.
Seems to be a problem between the 1310 and the switch. Any ideas?
possibly 1310 is misconfigured to pass tagged frames...
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
any idea on how to do that?
please provide config of 1310
!
version 12.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname ap
!
enable secret 5 xxx
!
ip subnet-zero
!
!
no aaa new-model
!
dot11 ssid PSJABR
  authentication open
  infrastructure-ssid
!
!
!
username Cisco password 7 xxx
!
bridge irb
!
!
interface Dot11Radio0
 no ip address
 no ip route-cache
 !
 encryption key 1 size 128bit 7 xxx transmit-key
 encryption mode wep mandatory
 !
 ssid PSJABR
 !
 speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0
 station-role non-root bridge
 bridge-group 1
!
interface FastEthernet0
 no ip address
 no ip route-cache
 bridge-group 1
 hold-queue 80 in
!
interface BVI1
 ip address 10.30.20.50 255.255.252.0
 no ip route-cache
!
ip default-gateway 10.30.20.1
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
!
!
control-plane
!
bridge 1 protocol ieee
bridge 1 route ip
!
!
!
line con 0
line vty 0 4
 login local
!
end
version 12.3
no service pad
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname ap
!
enable secret 5 xxx
!
ip subnet-zero
!
!
no aaa new-model
!
dot11 ssid PSJABR
  authentication open
  infrastructure-ssid
!
!
!
username Cisco password 7 xxx
!
bridge irb
!
!
interface Dot11Radio0
 no ip address
 no ip route-cache
 !
 encryption key 1 size 128bit 7 xxx transmit-key
 encryption mode wep mandatory
 !
 ssid PSJABR
 !
 speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0
 station-role non-root bridge
 bridge-group 1
!
interface FastEthernet0
 no ip address
 no ip route-cache
 bridge-group 1
 hold-queue 80 in
!
interface BVI1
 ip address 10.30.20.50 255.255.252.0
 no ip route-cache
!
ip default-gateway 10.30.20.1
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
!
!
control-plane
!
bridge 1 protocol ieee
bridge 1 route ip
!
!
!
line con 0
line vty 0 4
 login local
!
end
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
So, we enabled VLANs on the root and the non-root bridges. Now the switchs can communicate but we cannot hit the managment interfaces for the root or the non-root bridges.
Here is the config of the nonroot 1310. We can hit the switch connected to it now, but we can't hit the web interface of the bridge.
Here is the config of the nonroot 1310. We can hit the switch connected to it now, but we can't hit the web interface of the bridge.
service timestamps debug datetime msec
service timestamps log datetime msec
service password-encryption
!
hostname ap
!
enable secret 5 xxx
!
ip subnet-zero
!
!
no aaa new-model
dot11 vlan-name DATA vlan 51
dot11 vlan-name VOICE vlan 52
dot11 vlan-name WIRELESS vlan 53
!
dot11 ssid PSJABR
vlan 53
authentication open
infrastructure-ssid
!
!
!
username Cisco password 7 xxx
!
bridge irb
!
!
interface Dot11Radio0
no ip address
no ip route-cache
!
encryption key 1 size 128bit 7 xxx transmit-key
encryption mode wep mandatory
!
encryption vlan 53 key 1 size 128bit 7 xxx transmit-key
encryption vlan 53 mode wep mandatory
!
ssid PSJABR
!
speed basic-1.0 basic-2.0 basic-5.5 6.0 9.0 basic-11.0
station-role non-root bridge
!
interface Dot11Radio0.51
encapsulation dot1Q 51
no ip route-cache
bridge-group 51
!
interface Dot11Radio0.52
encapsulation dot1Q 52
no ip route-cache
bridge-group 52
!
interface Dot11Radio0.53
encapsulation dot1Q 53 native
no ip route-cache
bridge-group 1
!
interface FastEthernet0
no ip address
no ip route-cache
hold-queue 80 in
!
interface FastEthernet0.51
encapsulation dot1Q 51
no ip route-cache
bridge-group 51
!
interface FastEthernet0.52
encapsulation dot1Q 52
no ip route-cache
bridge-group 52
!
interface FastEthernet0.53
encapsulation dot1Q 53 native
no ip route-cache
bridge-group 1
!
interface BVI1
ip address 10.30.20.50 255.255.252.0
no ip route-cache
!
ip default-gateway 10.30.20.1
ip http server
no ip http secure-server
ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag
!
!
control-plane
!
bridge 1 protocol ieee
bridge 1 route ip
bridge 51 protocol ieee
bridge 52 protocol ieee
!
!
!
line con 0
line vty 0 4
login local
!
endASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
actually, yepp, as I have pointed you in my first and second comments ;)
good luck!
good luck!
I appreciate your comments but I didn't feel that they warrented any points. If you feel other wise, please object because i can't cancel my selection!
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
no-no, no problems with that :)
good luck!
good luck!
Switches / Hubs
--
Questions
--
Followers
Top Experts
A switch is a device that filters and forwards packets of data between LAN segments. Switches operate at the data link layer or the network layer of the Open Systems Interconnection (OSI) Reference Model and therefore support any packet protocol. LANs that use switches to join segments are called switched LANs or, in the case of Ethernet networks, switched Ethernet LANs. A hub is a connection point for devices in a network. Hubs are commonly used to connect segments of a LAN. A hub contains multiple ports; when a packet arrives at one port, it is copied to the other ports so that all segments of the LAN can see all packets.