Cisco7 WS-C350G-48TS Switch/VLAN Issue

Our C3705 has 4 VLANs configured on it. The subnet for VLAN1 is 192.168.1.x and I'm connected to a port on this switch on that VLAN. My connection goes from the switchport, to patch panel, to dataport on wall. From there I've ran another patch cable to a small D-link switch in order to enable a few extra ports for attaching my test systems. My workstation is also attached to this D=Link switch. I can get a DHCP address through this D_Link switch but if I connect any other workstations to it they cannot get a DHCP address. Instead they get the APIPA 169.x.x.x address. I swapped out the D-Link with another generic switch just to make sure that the D-Link wasn't the problem but still getting the same result. If I change my connection to another VLAN, my workstation and other test systems connected to the small switch can get a DHCP address. I'm suspecting that there is a misconfiguration or missing configuration on VLAN1 which is causing the anomaly but having some difficulty trying to determine what that is. Also note that our DHCP server is a Windows DC, also on VLAN1. Would greatly appreciate any input that could possibly shed some light on this.
Thanks!
RA

Sure.
Switch01#sh run int vlan1
Building configuration...
Current configuration : 61 bytes
interface Vlan1
ip address 192.168.1.7 255.255.255.0
end
Switch01#sh vlan
VLAN Name                             Status    Ports
1    default                          active    Gi1/0/3, Gi1/0/4, Gi1/0/5
                                                Gi1/0/10, Gi1/0/12, Gi1/0/14
                                                Gi1/0/15, Gi1/0/16, Gi1/0/31
                                                Gi1/0/32, Gi1/0/49, Gi1/0/50
                                                Gi1/0/51, Gi1/0/52
2    VLAN0002                         active    Gi1/0/24, Gi1/0/25, Gi1/0/26
                                                Gi1/0/28, Gi1/0/33, Gi1/0/34
3    VLAN0003                         active    Gi1/0/35, Gi1/0/37, Gi1/0/38
                                                Gi1/0/39, Gi1/0/40
4    VLAN0004                         active    Gi1/0/41, Gi1/0/42, Gi1/0/43
                                                Gi1/0/44
5    VLAN0005                         active    Gi1/0/45, Gi1/0/46, Gi1/0/47
                                                Gi1/0/48
100 VLAN0100                         active
200 VLAN0200                         active
300 VLAN0300                         active
600 VLAN0600                         active
700 VLAN0700                         active
900 VLAN0900                         active
1002 fddi-default                     act/unsup
VLAN Name                             Status    Ports
1003 token-ring-default               act/unsup
1004 fddinet-default                  act/unsup
1005 trnet-default                    act/unsup
VLAN Type SAID       MTU   Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
1    enet 100001     1500 -      -      -        -    -        0      0
2    enet 100002     1500 -      -      -        -    -        0      0
3    enet 100003     1500 -      -      -        -    -        0      0
4    enet 100004     1500 -      -      -        -    -        0      0
5    enet 100005     1500 -      -      -        -    -        0      0
100 enet 100100     1500 -      -      -        -    -        0      0
200 enet 100200     1500 -      -      -        -    -        0      0
300 enet 100300     1500 -      -      -        -    -        0      0
600 enet 100600     1500 -      -      -        -    -        0      0
700 enet 100700     1500 -      -      -        -    -        0      0
900 enet 100900     1500 -      -      -        -    -        0      0
1002 fddi 101002     1500 -      -      -        -    -        0      0
1003 tr    101003     1500 -      -      -        -    srb      0      0
1004 fdnet 101004     1500 -      -      -        ieee -        0      0
VLAN Type SAID       MTU   Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2
1005 trnet 101005     1500 -      -      -        ibm -        0      0
Remote SPAN VLANs
Primary Secondary Type              Ports

Similar Messages

SG200 Small business switch - vlan issue

I have the wonderous task of remotely configuring a few SG200 small business switches.
I need to create a vlan and move a few ports into that vlan, doesn't sound too difficult.
I have created the vlans but when I go to add the ports into the vlan the only option I seem to have is General?
If I specify access I can't say what vlan the port should be in?
What am I doing wrong?
All ports are currently in VLAN 1 and are in mode trunk
I have created 2 new vlans and just want to put 4 ports in VLAN 2 and 4 ports in VLAN 4
Can anyone impart any wisdom?
Thanks
Roger

Hi Roger,
Did you try this guide?
http://sbkb.cisco.com/CiscoSB/Loginr.aspx?login=1&pid=2&app=search&vw=1&articleid=80
Are you configuring it from GUI or CLI ?
Regards
Mariusz

L2VPN Local Switching VLAN to VLAN issue on 7200VXR/NPE-G1

I've been working with a client trying to get this working. We tried 12.2(31)SB6, 12.4(15)T1 IP Services and 12.4(15)T1 Advanced IP Services.
It works fine for Ethernet to Ethernet, or Ethernet to VLAN, but it doesn't work for VLAN to VLAN either on the same interface or on different interfaces. We've tried this on both a Cat5505 as well as a Cat294XL thinking that maybe there would be some issues with one platform or the other.
Here's an example:
! VXR (12.4(15)T1 Adv. IP Services)
interface GigabitEthernet0/1
no ip address
duplex full
speed 100
media-type rj45
no negotiation auto
interface GigabitEthernet0/1.202
encapsulation dot1Q 202
interface GigabitEthernet0/1.203
encapsulation dot1Q 203
connect test GigabitEthernet0/1.202 GigabitEthernet0/1.203
! Cat 5505
set vlan 202 9/1
set vlan 203 9/2
set port name 9/1 PC1
set port name 9/2 PC2
set port name 9/3 VXR-G0/1TRUNK
clear trunk 9/3 1-201,204-999
set trunk 9/3 on dot1q 202-203,1000-1005
We seem to be able to sequeeze a few packets through every once in awhile - like 1 or 2 every 20 or 30 packets:
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.604 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=0.638 ms
64 bytes from 192.168.1.1: icmp_seq=40 ttl=64 time=0.621 ms
64 bytes from 192.168.1.1: icmp_seq=48 ttl=64 time=0.608 ms
64 bytes from 192.168.1.1: icmp_seq=70 ttl=64 time=0.605 ms
64 bytes from 192.168.1.1: icmp_seq=78 ttl=64 time=0.630 ms
As you can see from the below show interface, the interface is receiving lots more packets than it's sending:
Router#show int g0/1
GigabitEthernet0/1 is up, line protocol is up
Hardware is BCM1250 Internal MAC, address is 001c.b0fa.101b (bia 001c.b0fa.101b)
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation 802.1Q Virtual LAN, Vlan ID 1., loopback not set
Keepalive set (10 sec)
Full Duplex, 100Mbps, RJ45, media type is RJ45
output flow-control is unsupported, input flow-control is XON
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 00:00:15
Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 1000 bits/sec, 2 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
40 packets input, 2836 bytes, 0 no buffer
Received 36 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 19 multicast, 0 pause input
8 packets output, 672 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 PAUSE output
0 output buffer failures, 0 output buffers swapped out
Router#
Does L2VPN Local Switching VLAN to VLAN not work on VXRs or something?
This link seems to indicate that E-E VLAN is supported in 12.4(11)T.
http://www.cisco.com/univercd/cc/td/doc/product/software/ios120/120newft/120limit/120s/120s27/fslocal.htm#wp1149105
What am I missing?

Hi,
In ASR9k, VLAN is port significant so yes you can match the same VLAN on different port.
For your untagged traffic, both UPE fo site 1 will think they are directly connected via two links so yes STP should take care about the loop
For your VPLS domain, if you are not using VLAN 100 on site 3, you need to pop the tag on both ASR9k. Also do you extend STP to site 3 ?
SVI is not supported in ASR9k today so you have to use unumbered interfaces instead:
interface Loopback1
ipv4 address a.b.c.d 255.255.255.255
interface g0/7/0/0.200
encapsulation dot1q 200
ipv4 point-to-point
ipv4 unnumbered Loopback1
proxy-arp
interface g0/7/0/1.200
encapsulation dot1q 200
ipv4 point-to-point
ipv4 unnumbered Loopback1
proxy-arp
I never tested it in this situation but from STP perspective those links should be seen as host connection.
Let me know if it works
HTH
Laurent.

Setting Locally Switched VLAN Id for HREAP'd ap's?

I am using HREAP on a number of AP's to fulfill a need of my end-users to have wireless devices connect to a locally hosted resource on a sites network. Getting the AP's to operate correctly has not been an issue (for the most part), and getting the "Locally Switched VLAN's" functional was not a problem. However, when I routinely go back through my AP's to check on them or to look t-shoot an unrelated issue I have noticed that some of the AP's have retained the Locally Switched VLAN mapping (i.e.: WLAN Id=5, Profile Name = test ssid, VLAN Id = 123) and some of them resolve the VLAN Id to 1 (for example).
Is the anyone that may have experienced this and can offer or point me towards a resolution?
I am also curious if I can configure the Locally switched vlans directly to my WiSM's instead of to each individual HREAP'd AP?
BTW: I have a wireless environment of 1242, 1252, and 1142 ap's with WiSM's on a 65xx w/ sup720.
Thanks for the help.

I saw similar behavior at a client site running 6.0.181.0 & 6.0.196.0 code, what I found the issue to be was that when you set the native vlan and hit apply the AP took a minute to initate a reboot (or so it appeared) and when I set the VLAN Mappings they weren't actually being applied.
I found if I set the AP to H-REAP and applied that then waited about 3-4 minutes, then enabled VLAN Support and set Native VLAN, apply that, wait 3-4 minutes, then set my VLAN Mappings that the issue went away.
Not sure if that's the same issue your running into but it's worth a shot.. I tried tons of things before discovering that pattern.. Incidentally it didn't seem to behave that way in 4.0 code nor does it seem to behave that way in 7.0 code.
Hope this helps...
Please rate useful posts.
Thanks,
Kayle

7936 not showing software version and vlan issue

I have a 7936 that does not show the software version. I have installed the newest load on the callmanager, but still cannot see what version it is running on the phone.
My main issue with the phone is that I have to set the switchport access vlan to the voice vlan, if I try to let the phone use the swithport voice vlan, it will pull an IP address off of the data vlan and not the voice vlan.
Any help with either of these issues would be greatly appreciated. I do rate all helpful posts.
Thanks,
Robert

Hi Robert,
Here is some info that may help;
Verifying Firmware Version Information
You can obtain information about the firmware version installed on the IP Conference Station.
Follow these steps to verify the firmware version on an IP Conference Station:
Step 1 Press the Menu button.
Step 2 Press the Up or Down scroll button to select the Admin Setup menu.
Step 3 Press the Select button.
Step 4 Enter the administrator password. (The default administrator password is **#.)
Step 5 Press the Enter softkey.
Step 6 Press the Up or Down scroll button to select System Information.
Step 7 Press the Select button.
Step 8 Press the Up or Down scroll button to select SW Version.
The firmware version number is displayed.
Or if that is not working try accessing this way;
Using the Web Interface
Follow these steps to access the Cisco IP Conference Station 7936 web interface:
Step 1 Open your web browser.
Step 2 In the address field enter:
http:// IP address of the IP Conference Station:
Configuration information applies to the specific IP Conference Station associated with the IP address you enter.
Note If you changed the HTTP port number, you need to use that number as a suffix to the IP address. If you did not change the HTTP port number, then you do not need to enter a suffix.
The web interface appears, and the initial login page is displayed.
Step 3 To log in as the administrator, enter the administrator password and click Login.
The default administrator password is **#.
Note When logged in to the IP Conference Station web pages, the web pages will time out after approximately 20 minutes of inactivity. You will then have to log back in.
Step 4 To log off, click Administrator Logout.
Information Available on All Web Pages
The top right portion of the Cisco IP Conference Station 7936 web interface includes a separate section that displays consistent information for all of the web pages.
This section contains the following information; example text appears next to each item in the list:
Software Version: 3.3(2.00)
Protocol Type: SCCP
Boot Load ID: PC0503031418
Application Load ID: CMTERM_7936.3-3-2-0
IP Address: 10.1.1.11
MAC Address: 00c742655892
Local Number: 2022
As far as the VLAN issue goes, this has always been the case for our 7935's as well and I'm sure the 7936 is the same.
Switchport mode access
Switchport access VLAN XXX
Hope this helps!
Rob
Please remember to rate helpful posts........

Multicast issues through L2 Switched Vlan

Hi,
I have attached a high level design diagram which represents the network topology and multicasting is introduced on the network for camera streams. For multicast using “sparse-dense-mode” and OSPF is used as the routing protocol.
Multicast works good when we had a single receiver “Receiver-1” and this receiver is connected to a access switch which directly connects to the core 6500 switch through a L3 Vlan. Mroutes looks good and works as expected.
When a second receiver “Receiver-2” was introduced on the network and the configuration is no different to the previous configuration and the receiver is not getting any streams and the multicast doesn’t work as expected. The only difference between is the presence of a L2 switch which acts as a bridge between the Access and the Core 6500 switch.
I believe, the simplest option is to enable routing and multicast on the switch called “Core-2” instead of using it as a L2 transparent switch. But, I would like to explore the possible options before enabling multicast throughout the network.
Your thoughts and help will be highly appreciated.
Thanks
Rajesh

Hi,
If Core-2 is pure L2 switch and we are running PIM between C-3750-2 and Core-1, it should not play any role in forwarding multicast traffic. Please share
from Core-1,C-3750-1 and C-3750-2
- show ip mroute <group>
- show ip pim nei
- show ip pim rp mapping
From C-3750-1 and C-3750-2
- show ip igmp group
Regards,
Akash

RV042G (router), SG200-26 (switch) vpn vlan issue

HI,
I have a RV042G (router), SG200-26 (switch)
ISP Modem on cable have dual wan static ip
Switch have 4 Vlan
vlan1 default
vlan2 networkA
vlan3 networkB
vlan5 Modem
port (1UP,2T) management port
port 2-12 (2UP) Network A
port 13 (5UP,2T,3T) wan cable plug
port 14 (5UP,2T) go back to router wan port assign IP to network A
port 18 (5UP,3T)
port 19-26 (3UP) Network B
port25 (2UP,1T) router lan1 port connect to the switch port 25
it can separate 2 different network, if i plug a cable to port1 i can manage the switch
but if i use vpn to connect the router i wont able to ping or see the switch, but i can ping the router and all other computers are on vlan2, and vlan2 not able to go to manage the switch too or ping it
what should i change to let vpn can access to vlan1 to manage the switch, thanks

Hello Gianluca,
In order for this setup to work, you will have to have a router that supports multiple vlans. You did not mention the model of the router or if it does this so I wanted to first mention that.
I understand your setup to be as follows- Internet -> Router -> Switch 1 -> Switch 2
On each port that connects a network device you will want to set the following-
Trunk port
Vlan settings of 1U, 2T, 3T
This allows default vlan of 1 and also other vlans
On other ports (1-4 , 7-9) you want to set them as follows-
Access port
Vlan of 2U OR 3U
This puts that port into the vlan of your choice
This will be the configuration needed, but again, you must have a router that will support vlans or multiple subnets.

VLANS ISSUE on Cisco switches

Hi,
We have WS-C4507R+E switch and WS-C2960X-24PS-L and we configured VLANs and VTP on 4507 switch we connected 2960X switch on 2960 we configured VTP vlan are communicated on 2960 switch.
Vlan details :38,40.41.42,43,and 44
4507 switch ip 192.168.38.1
2960 switch ip 192.168.38.2
Ip phone ip 192.168.44.2
Server ip 192.168.44.3
all vlan s are communication is running on both switches only data. On 2960X POE switch ip phone given ip 192.168.44.2 we are unable to ping ip 192.168.44.2 from other vlans we able to ping server ip 192.168.44.3 ip any configuration required on ip phone suggest me.

Hi,
Thanks for your replay
We have 2 routers in this scenario
1st router ip address 192.168.38.1 MPLS Router ,Second 192.168.38.3 2911 V K9 4507 switch ip 192.168.38.2 and 2960X poe switch ip 192.168.38.27

Strange VLAN issue on aironet access points

I'm setting up some access points for WPA. I've ran into a strange issue. The client VLAN (VLAN that the users will be put into) is 1, and the native VLAN is 10. The RADIUS server is in VLAN 1 (but I have a test RADIUS server in VLAN 10 as well). I can connect from the access point to a RADIUS server in either VLAN, and from the RADIUS servers to the access point as well. When I point to a RADIUS server in VLAN10 authentication works fine. If I point to a RADIUS server that is located in VLAN1, and I put the wireless clients in VLAN10 it works fine. But for some reason when I have the RADIUS server and the clients in VLAN (1) and the native (BVI1) interface in VLAN 10 the authentication packets never seem to get to the RADIUS server. It is as if the authentication is being sources out of the wrong VLAN. I can?t find any docs to say that this isn?t a supported configuration.

Hi Shannon,
have a look here:
http://www.cisco.com/en/US/products/hw/wireless/ps4570/products_configuration_example09186a00801d0815.shtml#apconfig
- - - Snipp - - -
Significance of Native VLAN
When you use an IEEE 802.1Q trunk port, all frames are tagged except those on the VLAN configured as the "native VLAN" for the port. Frames on the native VLAN are always transmitted untagged and are normally received untagged. Therefore, when an AP is connected to the switchport, the native VLAN configured on the AP must match the native VLAN configured on the switchport.
Note: If there is a mismatch in the native VLANs, the frames are dropped.
This scenario is better explained with an example. If the native VLAN on the switchport is configured as VLAN 12 and on the AP, the native VLAN is configured as VLAN 1, then when the AP sends a frame on its native VLAN to the switch, the switch considers the frame as belonging to VLAN 12 since the frames from the native VLAN of the AP are untagged. This causes confusion in the network and results in connectivity problems. The same happens when the switchport forwards a frame from its native VLAN to the AP.
- - - Snapp - - -
Best regards,
Frank

Weird VLAN issues

The device doing the routing between the vlans should know how to get to each vlan, either by explicit or dynamic routes being set to the ingress/egress point of this vlan. Or by being directly connected, so the routing device would Ideally in a small network on one site would have an IP in vlan 200 and be the default gateway, and ip for communication on the original network and an ip to communicate with the firewall or if firewall is inbuilt on the internet. You should have a route for 0.0.0.0 set to the external next hop. Start from the device doing the routing and see if it can ping devices in each subnet.
From there ensure the default gateway for the devices are on the same vlan and in the same subnet as the vlan interface for the device doing the routing

Ok, so I have asked vlans questions before and I thank you all for your help.My issue today is odd. I've scratched my brain for awhile on this.Here is the scenario.I added VLAN 200 to our router and all switches in the house.Gateway is the router at 10.20.x.1Only thing that has changed hardware wise is I added a HP 2920 for a SAN/Vmware implementation.I am not able to ping/communicate with devices in VLAN 200 from other VLANs.If I try from my PC which is in VLAN122, I can only ping the router/gateway 10.20.x.1If I setup a laptop in VLAN200 and plug into our "main switch" which the router is connected to directly, I can ping the VLAN200 devices, but I CANNOT ping the router interface of 10.20.x.1It makes no sense to me at all, and I have had a reliable IT contact look at the issue as well, and it's been a hassle.I need to access VLAN200...
This topic first appeared in the Spiceworks Community

Multiple switch vlan routing, almost there!

Hello,
I'm hoping this is a blatantly obvious issue, but we all know how late night thinking tends to be fairly foggy!
Anyway, I have 3 3400cl HP switches and a 2610 Poe switch. One of the 3400's is acting as the core, with the other 3 switches lacp trunked into it.
Currently trying to get vlan 40 traffic properly routed for internet access. This is a leap into vlan configs, so the existing domain traffic is still on vlan 1 (yes I know, not ideal).
The config so far successfully allows clients on vlan 40 to receive DHCP addresses via the ip helper, but no access to internet sites. I can resolve a dns address just can't see any hopes beyond the vlan 40 IP.
Two other points if anyone wishes to comment:
The HP 2610 is slotted to be replaced with a Cisco 3750 Poe switch. Any comments and making cisco and HP play nicely together?
And second, if anyone wants to suggest best practice words of wisdom for migrating existing services into a more detailed vlan setup, please type away!
Here is the config: The 'lower' named switch will mirror the 3rd 3400 so I didn't see the need to include that one.
hostname "NHB-Core"
interface 19
   no lacp
exit
interface 20
   no lacp
exit
interface 21
   no lacp
exit
interface 22
   no lacp
exit
interface 23
   no lacp
exit
interface 24
   no lacp
exit
trunk 19-20 Trk1 LACP
trunk 21-22 Trk2 LACP
trunk 23-24 Trk3 LACP
ip routing
snmp-server community "public" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-18,Trk1-Trk3
   ip address 10.10.4.59 255.255.255.0
   exit
vlan 40
   name "VLAN40"
   ip address 10.10.10.1 255.255.255.0
   ip helper-address 10.10.4.29
   tagged Trk1-Trk3
   exit
ip route 0.0.0.0 0.0.0.0 10.10.4.98
spanning-tree Trk1 priority 4
spanning-tree Trk2 priority 4
spanning-tree Trk3 priority 4
hostname "NHB-Poe"
trunk 25-26 Trk1 LACP
ip default-gateway 10.10.4.59
snmp-server community "public" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged 1,3-24,27-28,Trk1
   ip address 10.10.4.62 255.255.255.0
   no untagged 2
   exit
vlan 40
   name "VLAN40"
   untagged 2
   tagged Trk1
   exit
spanning-tree Trk1 priority 4
hostname "NHB-lower"
interface 23
   no lacp
exit
interface 24
   no lacp
exit
trunk 23-24 Trk1 LACP
ip default-gateway 10.10.4.59
snmp-server community "public" Unrestricted
vlan 1
   name "DEFAULT_VLAN"
   untagged 1-22,Trk1
   ip address dhcp-bootp
   exit
vlan 40
   name "VLAN40"
   tagged Trk1
   exit
spanning-tree Trk1 priority 4

I am sorry, but to get your issue more exposure, I would suggest posting it in the commercial forums, since this is a commercial product. You can click here for the link.
TwoPointOh
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom to say “Thanks” for helping!

Nexus 1010 + 1000v control vlan issue

Hi,
I have Nexus 1000v installed on nexus 1010. The nexus 1010 is in cluster and working fine. I have made network uplink option 3.
My VSM is configured to be on L3 mode. Hence I set control and packet vlan to 1 (on vsm). while creating the VSB too I have choosen control and packet vlan to be 1 (keeping in mind my mode will be L3).
Now The vsm is not coming up in HA. The redandancy log says degraded mode is true.
Is it because, the control packet coming from VSM after reaching the N1010, the packets are getting tagged with vlan 1. Since I have not set any native vlan on 1010, might be control vlan 1 is also tagged one. Is it this the case ?
help needed on this issue.
regards
Prasad K

Control vlan is a totally seperate VLAN then your System Console. The VLAN just needs to be available to the ESX host through the upstream physical switch and then make sure the VLAN is passed on the uplink port-profile that you assign the ESX host to.
We only need an interface on the ESX host if you decide to use L3 control. In that instance you would create or use an existing VMK interface on the ESX host.

Problem in switching vlan

Hello gentlemen,
I have a problem in my topology, one at a time about if there is no traffic on the vlan, router R2 fails to ping the ip of the remote end svi, issu cause disorders seen everything so normalizes after I ping from (Vlan10)-R1 to ip in svi R2 - (Vlan10). when the problem another vlan trunk occurs at the same link with the switching hub continues normally. the arp table set out their macs and addresses. In troubleshooting at layer 2 and not detected any problems. Someone already I witness such a problem?
I am using switch module in any senario model HWIC-4ESW.

Hi,
Can you post "sh run" from all 3 routers?
Are you using separate subnet for each vlan?
Are all 1841 routers have the same module installed?
What version of IOS are you running.

1532 Autonomous Outdoor link DFS and vlans issue

Hi all,
I have a fresh installation of a Point to Point (1km distance) link using autonomous Aps 1532 and directional antennas 14dbi.
The regulatory domain is Europe and the only usable channels are 100 104 108 112 116 132 136 140 (DFS channels).
The link is near military area and DFS is triggered very often which causes frequent disconnections near every minute.
From the logs i see that there is no available channel:
%DOT11-6-DFS_TRIGGERED: DFS: triggered on frequency 5540 MHz
%DOT11-2-NO_CHAN_AVAIL_NON_OCCP: Interface Dot11Radio1, no channel available.
So if all channels are occupied by the radars why carrier busy test does show anything?
ROOT#dot11 dot11Radio 1 carr bu
Frequency Carrier Busy %
   5500          0
   5520          0
   5540          0
   5560          0
   5580          0
   5660          0
   5680          0
   5700          0
The second issue is regarding vlans.
3 Vlans: Data vlan 1 ,Voice vlan 2 , Management vlan 100 (native vlan for bridging).
After rebooting the non-root bridge data vlan 1 doesn't works even though management and voice are ok.
The workaround i found is to manually change the bridge group to different number.
After the change connectivity is comes back... (maybe bug???)
interface Dot11Radio1.2
encapsulation dot1Q 2
bridge-group 2
bridge-group 2 spanning-disabled
interface Dot11Radio1.4
encapsulation dot1Q 1
bridge-group 4
bridge-group 4 spanning-disabled
interface Dot11Radio1.100
encapsulation dot1Q 100 native
bridge-group 1
bridge-group 1 spanning-disabled
Any thoughts?
Best regards,
Christos.

Below is the output from one of my APs in the -E regulatory domain:
Carrier Set: ETSI (OFDM) (EU) (-E)
Uniform Spreading Required: Yes
Configured Frequency: 0 MHz Channel 0
Allowed Frequencies: 5180(36) 5200(40) 5220(44) 5240(48) 5260(52) 5280(56) 5300(60) 5320(64) 5500(100) 5520(104) 5540(108) 5560(112) 5580(116) 5660(132) 5680(136) 5700(140)
Listen Frequencies: 5180(36) 5200(40) 5220(44) 5240(48) 5260(52) 5280(56) 5300(60) 5320(64) 5500(100) 5520(104) 5540(108) 5560(112) 5580(116) 5660(132) 5680(136) 5700(140) 5745(149) 5765(153) 5785(157) 5805(161) 5825(165)
It seems to be a limitation of the 1530 series:
http://www.cisco.com/c/en/us/products/collateral/wireless/aironet-1530-series/data_sheet_c78-728356.html
Frequency Band and 20-MHz Operating Channels
-E Domain:
● 2.401 to 2.4835 GHz; 13 channels
● 5.470 to 5.725 GHz; 8 channels
Regarding your issue with vlan 1, I can't see anything wrong in your configuration. This could indeed be a bug. I made a little research in the bug tool, but couldn't find anything related.
However, you should check the following before opening a case with the TAC:
check the logs from the AP immediately after a reboot
check your switch port status on each side
Is the bridge setting a loop in your network? I have worked on architectures with redundant wireless bridge uplinks using STP. A STP blocked port for vlan 1 could be a lead in that case.
Moreover, in your configuration, I can't see the usual bridge-group configuration under your subinterfaces. Not sure if this is of any use here as you have a 1532 AP, but I would try to add it for each subinterface:
interface GigabitEthernet0.100
encapsulation dot1Q 100 native
no ip route-cache
bridge-group 1
no bridge-group 1 source-learning
bridge-group 1 spanning-disabled
interface Dot11Radio0.100
encapsulation dot1Q 100 native
no ip route-cache
bridge-group 1
bridge-group 1 subscriber-loop-control
bridge-group 1 block-unknown-source
no bridge-group 1 source-learning
no bridge-group 1 unicast-flooding
bridge-group 1 spanning-disabled

Vlan issue

Hi
I have different vlans spread out edge switches, recently i had issues with a specific vlan. some switchports that are assigned to this vlan stop working, they appear connected ( green ) but don't respond to ping requests even with clients on the same vlan, actually they are access control readers also they can't communicate with their controller. I tried my laptop on the same switchports with ip of the same vlan i still cannot ping to any thing except my gateway ( virtual interface) on core switch. when i use these switchports with another vlan they just working normally !!
any help ?

Hi saad.mahmoud,
I'm trying to understand the issue you're having and need some clarification. What do you mean by the switchports stopped working? Can a host connected to one of these edge switches, assigned to the specific VLAN, ping the SVI on the same edge switch?
Are only some switchports assigned to this specific VLAN are having problems, or is it all ports assigned to the VLAN?

Cisco7 WS-C350G-48TS Switch/VLAN Issue

Similar Messages

Maybe you are looking for