Problem routing VLAN

Reference Dell 6024

The switch has several local networks VIRTUAL, including VLAN 1 172.16.0.0 255.255.0.0 and VLAN 50 172.16.8.0 255.255.255.0. In the past, we have not need route between all the VLANS, but now I want to access the VLAN 50 of VLAN 1. All VLANS have a static IP address in the switch. Some configs:

SH ip route
Maximum parallel paths: 4 (4 after reboot)

Code: C - connected, S - static, R - RIP, O - OSPF, E - OSPF external

C 172.16.0.0/16 is directly connected vlan 1
C 172.16.5.0/24 is directly connected vlan 2
C 172.16.8.0/24 is directly connected vlan 50
C 192.168.7.0/24 is directly connected vlan 40

SH vlan

VLAN name Ports type permission
---- ----------------- --------------------------- ------------ -------------
1 1 g (1, 3-12, 17-24), ch(1-7) other required
2 phone switch g (13, 15-16, 24) permanently required
40 g (23-24) IDN Vlan permanent required
50 g (2,14,17) VLAN Voip permanent required

The router configuration
-----------------------------

interface ethernet g18
Description ConfCtr
output
serial interface ethernet g (1-2, 17)
switchport mode general
output
serial interface ethernet g(23-24)
switchport mode trunk
output
database of VLAN
VLAN 2,40,50
output
interface ethernet g2
pvid switchport General 50
output
serial interface ethernet g (13: 15-16)
switchport access vlan 2
output
interface ethernet g24
switchport trunk allowed vlan add 2
output
serial interface ethernet g(23-24)
switchport trunk allowed vlan add 40
output
interface ethernet g2
VLAN allowed switchport General add 50 unidentified
output
interface ethernet g14
switchport access vlan 50
output
interface ethernet g17
VLAN allowed switchport General add 50
output
interface vlan 2
name 'phone switch '.
output
interface vlan 40
name "Vlan IDN.
output
interface vlan 50
the name "Voip VLAN.
output
interface vlan 1
IP 172.16.0.39 255.255.0.0
output
interface vlan 2
IP 172.16.5.2 255.255.255.0
output
interface vlan 40
IP 192.168.7.43 255.255.255.0
output
interface vlan 50
IP 172.16.8.2 255.255.255.0
output
the 172.16.8.2 interface IP
broadcast-address 0.0.0.0
directed broadcast to the
output
> Gigabit Ethernet ports
=============================
> no stop
> 1000 speed
> full duplex
> negotiating
> flow control to the wide
> auto mdix
> no pressure
 
> interface vlan 1
> interface port-channel 1-7
 
> no router RIP
 
> do not allow no router OSPF
 
> spanning tree
> spanning tree mode PLEASE

> basic qos
 
> Host OOB Configuration
-------------------------
 
> out-of-band-eth interface
> no stop
> 100 speed
> full duplex
> negotiating
> flow control to the wide
> no pressure
> output

I can't ping from VLAN 1 to 50 of VLAN. Based on another poster who said that the VLAN 1 is not routable, I configured a port to VLAN 2 and tried to do a ping of 50 VLAN port, without success. I am really puzzled. There seems to be a fairly common config and I'm sure it's something really simple... but what? »


Tags: Dell Switches

Similar Questions

  • The problems of routing VLAN?

    Hello

    I'm trying to get our network out of a topology of flat to work with the hardware I have on the spot I have setup the network and local networks virtual, but could not get any other VLAN to carry. Here is what I use:

    Reference Dell PowerConnect 6248 as my router from Layer 3 and three PowerConnect 2748 detach the 6248 in three GAL groups all with four ports together. I have VLAN 10-50 for various average things regime 192.168.10.0/24, 192.168.20.0/24, 192.168.30.0/24 ect.

    Here's the question: 10.0 network works fine, but on any other VLAN, I get an IP address from the DHCP server, but I can't ping my gateway let alone ping another VLAN.

    Heres my living room will be output:

    console#show run
    !Current Configuration:
    !System Description "PowerConnect 6248, 3.3.11.2, VxWorks 6.5"
    !System Software Version 3.3.11.2
    !Cut-through mode is configured as disabled
    !
    configure
    vlan database
    vlan 5,10,20,30,40,50
    vlan routing 20 1
    vlan routing 30 2
    vlan routing 40 3
    vlan routing 50 4
    vlan routing 1 5
    vlan routing 10 6
    exit
    stack
    member 1 2
    exit
    ip address 192.168.6.6 255.255.255.0
    ip default-gateway 192.168.6.1
    ip address vlan 5
    ip routing
    ip route 0.0.0.0 0.0.0.0 192.168.1.1
    interface vlan 1
    routing
    ip address 192.168.1.2 255.255.255.0
    exit
    interface vlan 10
    name "Servers"
    routing
    ip address 192.168.10.1 255.255.255.0
    bandwidth 10000
    ip mtu 1500
    exit
    interface vlan 20
    name "Production"
    routing
    ip address 192.168.20.1 255.255.255.0
    ip helper-address 192.168.10.110
    exit
    interface vlan 30
    name "WD Staff"
    routing
    ip address 192.168.30.1 255.255.255.0
    exit
    interface vlan 40
    name "Non WD Offices"
    routing
    ip address 192.168.40.1 255.255.255.0
    exit
    interface vlan 50
    name "Church"
    routing
    ip address 192.168.50.1 255.255.255.0
    exit
    username "misterp" password beda28c8e29f04603da19eb1b3b239ee level 15 encrypted
    !
    dhcp l2relay vlan 20
    dhcp l2relay circuit-id vlan 20
    dhcp l2relay remote-id 1 vlan 10
    dhcp l2relay remote-id 20 vlan 20
    !
    interface ethernet 1/g1
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g2
    spanning-tree portfast
    switchport mode general
    switchport general allowed vlan add 20,30,40,50 tagged
    exit
    !
    interface ethernet 1/g3
    channel-group 1 mode on
    exit
    !
    interface ethernet 1/g4
    channel-group 1 mode on
    exit
    !
    interface ethernet 1/g5
    channel-group 1 mode on
    exit
    !
    interface ethernet 1/g6
    channel-group 1 mode on
    exit
    !
    interface ethernet 1/g7
    channel-group 2 mode on
    exit
    !
    interface ethernet 1/g8
    channel-group 2 mode on
    exit
    !
    interface ethernet 1/g9
    channel-group 2 mode on
    exit
    !
    interface ethernet 1/g10
    channel-group 2 mode on
    exit
    !
    interface ethernet 1/g11
    channel-group 3 mode on
    exit
    !
    interface ethernet 1/g12
    channel-group 3 mode on
    exit
    !
    interface ethernet 1/g13
    channel-group 3 mode on
    exit
    !
    interface ethernet 1/g14
    channel-group 3 mode on
    exit
    !
    interface ethernet 1/g15
    switchport mode trunk
    switchport trunk allowed vlan add 10,20,30
    exit
    !
    interface ethernet 1/g16
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g17
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g18
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g19
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g20
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g21
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g22
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g23
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g24
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g25
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g26
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g27
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g28
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g29
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g30
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g31
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g32
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g33
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g34
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g35
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g36
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g37
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g38
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g39
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g40
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g41
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g42
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g43
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g44
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g45
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g46
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g47
    switchport access vlan 10
    exit
    !
    interface ethernet 1/g48
    switchport access vlan 10
    exit
    !
    interface port-channel 1
    spanning-tree disable
    spanning-tree mst 0 external-cost 5000
    switchport mode general
    switchport general pvid 10
    switchport general allowed vlan add 10
    switchport general allowed vlan add 20,30,40,50 tagged
    switchport general allowed vlan remove 1
    exit
    !
    interface port-channel 2
    spanning-tree disable
    spanning-tree mst 0 external-cost 5000
    switchport mode general
    switchport general pvid 20
    switchport general allowed vlan add 10
    switchport general allowed vlan add 20,30,40,50 tagged
    switchport general allowed vlan remove 1
    exit
    !
    interface port-channel 3
    spanning-tree disable
    spanning-tree mst 0 external-cost 5000
    switchport mode general
    switchport general pvid 10
    switchport general allowed vlan add 10
    switchport general allowed vlan add 20,30,40,50 tagged
    switchport general allowed vlan remove 1
    exit
    exit

    As a side note, I don't have really messed with other VLAN only 20.

    Any help would be great. I'm just puzzled.

    Thanks Daniel, I understand this problem. on the 27xx series switches I was marking traffic on clients without realizing it was not labeled. New network equipment in collaboration with a Cisco and DELL all this background I've ever had to deal with THIS a marking was done automatically.

  • EMS 2010 routing problem inter vlan

    OK, back to the base, I tried to install complicated things that did not work so now, I'm leaving the base.

    I am trying to configure my SGE2010 48 ports Gigabit cisco / switch for routing inter - vlan.

    so far, I put the mode switch layer 3 from the telnet console and rebooted, it.

    entered the interface web and changed the ip of the vlan by default management 192.168.2.3

    added the vlan 70 and vlan bridging 180, section of mangement of vlan

    under the IP, IPv4 interface address, I've added the IP address for each virtual local area network as follows:

    IP Interface Mask

    192.168.70.3 255.255.255.0 VLAN 70

    192.168.180.3 255.255.255.0 VLAN 180

    then I went in transition, management of VLANs, vlan to the port:

    set the port g1 get access to the vlan 70

    sets the g2 as an access port for vlan 180

    connected A computer to port g1 with static IP 192.168.70.200 mask 255.255.255.0 Gateway 192.168.70.3

    connected computer B to port g2 with static IP 192.168.180.180 mask 255.255.255.0 Gateway 192.168.180.3

    I'll then in the routing static routing: I see the 192.168.70.0 destination IP address 24 as a type of local railway and even for 192.168.180.0 24 as the type of local railway

    on a computer, I ping the gateway 192.168.70.3 and it works

    on computer B, I ping the gateway 192.168.180.3 and it works

    problem is that they cannot ping each other, windows firewall is disabled on both computers.

    If I do a tracert on any of the computer he reach the gateway by default but then expire on the second jump.

    any suggestions what I could have done wrong and the solution to the problem would be appreciated.

    Edit: Here's the running configuration if it helps:

    Cisco-SGE2010 # show running-config

    database of VLAN

    VLAN 70 180

    output

    g ethernet serial interface (1.26)

    switchport access vlan 70

    output

    interface ethernet g2

    switchport access vlan 180

    output

    interface vlan 70

    printer name

    output

    interface vlan 180

    name wireless

    output

    interface vlan 1

    IP 192.168.2.3 address 255.255.255.0

    output

    interface vlan 70

    IP 192.168.70.3 255.255.255.0

    output

    interface vlan 180

    IP 192.168.180.3 255.255.255.0

    output

    Cisco-SGE2010 hostname

    location of the Server SNMP here

    SNMP Server contact me

    Cisco-SGE2010 #.

    If you can test both the interface switches the routing works correctly. You need to maybe turn off the Windows Firewall or open the firewall to allow ICMP to a different subnet. Windows Vista and 7 by default will block ICMP from any other subnet then their own.

    Cisco Small Business Support Center

    Randy Manthey

    CCNA, CCNA - security

  • I would like to help with what I believe, it is a problem of routing VLANS on a SLM2008 and RVS4000

    Please see attached Word documentfor a full description.  Thank you!

    Hi Michael,

    All those who say the VLANS within the first hour is a person much smarter than me.

    I have to admit with great humility, I think it took me nagging questions for some patients (AR) and weeks and weeks until finally I have a bit of understanding of the functioning of VLAN.

    So don't feel concerned, many people there are in the same "boat" as you.

    But VLAN, when you get the feel for them, are so so helpful.

    I like under 'acceptable frame type' tick 'all '.

    The value PVID tells me basically what VLAN not signposted port is underway.

    This means that in the image below, 3 ports, 6-8 will be I hope, expecting to received and transmit frames Ethernet labeled with a tag VLAN 2.

    But on the diagram above, I can now make room for the following table.

    without tag vlan tagged vlan

    3-1-2 switch port

    6 2 2 switch port can not be marked and unidentified on the same switch port

    7 2 2 switch port can not be marked and unidentified on the same switch port

    8-1-2 switch port

    In the diagram above, I can see that 1 and 2 switch ports are ifor untagged VLAN 3 so the packages roll inside the switch for VLAN 3 will have their VLAN TAGs removed from the Ethernet frame as the traver packets on the switch to an IP host.

    I also see that the switch port 3 unidentified in the VLAN 1, but you have set the acceptable frame on tagged only type.

    Unless I read this all in fact wrong.

    Note: I have to admit that has the big brother to the SG200 SG300 series switch,

    Don't forget about PC / security cameras (except Cisco, hey I'm system engineer have to give my equipment fitted with a plug) in most of the cases do not send frames labeled Ethernet in the switch, which is why I like the idea of accepting all types of frames. I guess that the default VLAN settings are the acceptable frame types = all

    When we add a vlan to a switch port, as the image below, switch to these ports are added as a vlan tagged, because the port if already reside in one VLAN not tagged...  This means that in the case below, 3 ports, 6-8 will be I hope, expecting to received and transmit frames ethernet labeled with a tag VLAN 2.

    You said it, not easy, you need to play and practice with switching and routing

    .  But the general rule that I follow for VLAN's.

    A switch port can be untagged in a single vlan, but at the same time marked on several VLANs.

    With respect to the limitation of the camera, my camera, I have not used my filters. But there is the possibility of limiting access by IP address or network.

    I guess you can find an article on your DLINK camera to filter. Reset the default camera and try to add it again.

    Routing between VLANS will occur at the RVS4000, it routes packets between different VLANs, the SG200 cannot be put in Layer 3 mode like its big brother the 300 series (SRWXXX-K9-NA)...

    Best regards, Dave

  • help config VLANs and inter routing VLANs on SF - 300

    Hi all.

    I divided the routing problem "SF-300 (Layer 3) can be connected to the bridge." I did not put in the entry door. Too bad, I have encountered with Packet Tracer 5. I can attach a file. Leave everything to me.

    Thank you.

    # config - code

    IP routing

    VLAN 10

    VLAN 20

    VLAN 30

    interface FastEthernet0/1

    switchport access vlan 10

    switchport mode access

    interface FastEthernet0/6

    switchport access vlan 20

    switchport mode access

    interface FastEthernet0/11

    switchport access vlan 30

    switchport mode access

    interface Vlan10

    IP 192.168.10.1 255.255.255.0

    interface Vlan20

    address 192.168.20.1 255.255.255.0

    Vlan30 interface

    192.168.30.1 IP address 255.255.255.0

    The configuration of the switch is fine. My only question is your computers. Example of

    Computer on fa1.

    Should be something like

    192.168.10.100

    255.255.255.0

    192.168.10.1

    Computer on Fa6

    192.168.20.100

    192.168.20.1

    255.255.255.0

    Also avoid any simultaneous wireless connection and you may want to disable things like firewalls of the window.

    -Tom
    Please mark replied messages useful

  • two questions of routing VLAN fast

    Let's say that I have spend a routing 4 L3 VLAN

    VLAN 1 192.168.10.0/24, virtual interface of the switch is 192.168.10.254 inside this vlan
    VLAN 2 is 192.168.20.0/24, the virtual interface of the switch is 192.168.20.254 inside this vlan
    VLAN 3 is 192.168.30.0/24, the virtual interface of the switch is 192.168.30.254 inside this vlan
    VLAN 4 192.168.40.0/24, virtual interface of the switch is 192.168.40.254 inside this vlan

    There is that a single router out of this switch at the net, and lets say that it is in VLAN 1 and its address is 192.168.10.1

    first question - inside the L3 switch I need to add a default route 0.0.0.0 0.0.0.0 192.168.10.1

    to ensure that all traffic not matching only a 192.168.x.x address not know where to go to the net, correct?

    Second - when this router, is there a difference if I use the following static route:

    192.168.20.0 255.255.255.0 192.168.10.254

    Instead of

    192.168.20.0 255.255.255.0 192.168.20.254

    ?

    Whatever happens, the package comes to switch L3, but in one case, what happened to it through the interface VLAN 1 VLAN and in the other case, he gets there through the interface VLAN VLAN for which traffic is intended anyway. is what im trying to figure out, this will make a difference at all? especially with regard to broadcast packets?

    If it makes no difference, then it is safe to say that the following static route would be optimal?

    192.168.0.0 255.255.0.0 192.168.10.254

    Re "of all". Fix. The L3 switch will route traffic based on its routing table. By default, he knows all IP subnets, it is directly connected to, i.e. all subnets VLAN. If you must add a route by default manually or not depends on the exact implementation. It would be nice if the L3 switch will use the no default for routing gateway that you use for the switch IP parameters itself (if there is an option in the web interface to set a default gateway). If you cannot define a default gateway on the L3 switch, you might have to manually add a static route. The easiest way would be to check the current routing table and see if there is a default or not gateway.

    Re "then." A router can only transfer the packets to the next hop router. The next hop router must be connected to this router. The route "192.168.20.0 255.255.255.0 192.168.10.254" is correct for a router with IP address 192.168.10.1 and 255.255.255.0 as 192.168.10.254 subnet mask is connected to the router. "192.168.20.0 255.255.255.0 192.168.20.254" is not correct. The router cannot learn the path to a subnet specific 192.168.20.0/255.255.255.0 using a gateway on that subnet. It is not correct to use this kind of a route and do not use it even if it might work even (because the router is a simple query ARP to find the MAC address of the 192.168.20.254 and your L3 switch will respond to the ARP request, even if it's on the internet of 192.168.10.254). At the same time that another router between 10 and 20 subnets it would work no more...

    Re your conclusion: I recommend to keep four static routes to subnets existing on the L3 switch instead of put in a single subnet more great which includes a lot of addresses that are not connected here. Technically, this works if you only use working IP addresses. But you will see some loops if you send something to 192.168.55.50 or similar. The gateway router it will send to the L3 switch that will return to the catwalk. They should understand it's a loop, but still, I would not recommend this type of installation... Add routes for each of the L3 switch subnet...

  • connection problems router WRT310N and wrt54gs * with DSL

    Until I can return to my apartment and after IPconfig etc. returns I wanted to see if anyone has had the following problem.

    I had a home wireless network set up with a wrt54gs v 5... I think it was BOM.

    A few days ago I tried to get the network key for the new smartphone and my roommate kind of stupidly locked myself and disconnected my phone then my Office Wireless adapted. passing through the standard power recycles and resets all him remains disconnected in the apartment as well.

    I have DSL through verizon, a toshiba satellite a135 with vista installed, all updates of drivers, and a westell 6100 dsl modem provided by my phone company.

    highlights include:

    (1) two nights now troubleshooting and browsing the forum. I have already exhausted simple corrections of linksys on his questions and help section.

    (2) new router, I wanted anyway a new and estimated that he was the problem. So I bought a wrt310N, hung, and he now obtained, there no longer updated set of firmware

    (3) internet connection is fine when I connect to my laptop directly to a dsl modem.

    router 4) implements the home network wireless very well, but with no internet connectivity

    (5) computer wired to the modem connects to the internet. wired computer for router modem does not connect to the internet. with two routers. If it connects not wired and wireless won't be better.

    I'm getting a little tired and tired, not to mention, I didn't my XBOX live fix to remove the stress of working in a military office all day lol

    everything seems to work until the router tries to connect to my dsl provider, at least as far as I can tell.

    and I'll be on the phone/forums with my ISP as well to make sure that I am not he mess up simply forgetting to fill in an optional field with info mandatory lol.

    so... help?

    still, when I go home for lunch I'll post information and specifications of real hardware if someone a little more savvy I know what to ask.

    Any ideas on where I'm wrong now?

    Fixed issue...

    in the end, it's a problem between the ISP's modem and the router that they helped me understand.

    My DSL service had changed their service, so TRP was no longer how they did the connections. Automatic DHCP was the current form. Following configurations of router DSL online provided inaccurate information. I didn't have the time to check with the ISP until yesterday afternoon when I was finally able to make a phone call and clarify things.

    We put the modem into bridge mode, checked some settings on the router, and then everything is back up now.

  • Inter routing VLANs with this config

    Hi all

    I'm looking for clarification, I understand two Vlan need a device to layer 3 to enable routing between them.

    I wanted so check if this set up works or not.

    Router - Switch A-SwitchB-SwitchC

    All the link between router and switch are ports of junction and allows said we have VLAN 10 to 20 on switch C

    And two for the router interface to these VLANs.

    Device of two different VLANS on switch C can communicate?

    If this is not why. I guess, I'm rationalizing is traffic belonging to VLAN 10 crossbar router base and scope and is achieved through the trunk even join router

    Please specify.

    Thank you

    L

    Yes they should be able to communicate if done correctly. VLAN 10 and 20 must be resources shared by all switches to the router with the L3 interface.

    So for host on VLAN 10 to get a host on VLAN 20, the package would take VLAN 10 overall of all switches to the router, where it would get "routed" to VLAN 20 and again on the switches to the host to VLAN 20.

  • Problem with VLAN between Cisco Catalyst (3560G) and SG300-52

    I am having trouble with the creation of a trunk of vlan between a SG300-52 and a Cisco Catalyst 3560 G.  I have 4 VLANS (1, 2, 10 and 11) on the 3650 and I need ports on the SG300 to be able to communicate with them.

    On the 3560, port 14 is defined as:

    interface GigabitEthernet0/14

    switchport trunk encapsulation dot1q

    switchport mode trunk

    spanning tree portfast

    On the Sg300 port 52 is defined as:

    interface GigabitEthernet52

    point to point link type spanningtree

    switchport trunk allowed vlan add 1,2,10,11

    description macro switch

    Try to understand what the problem... Any help would be appreciated.

    Thank you

    Chris

    Hi Chris, the first problem is the spanning tree portfast, it shouldn't be on an interconnection network switch. You may have a mismatch of vlan native as well, but that shouldn't matter.

    A suggestion, however, the value of the port SG300 general mode and disable the input filter.

    -Tom
    Please mark replied messages useful

  • Routing VLANS on multiple routers

    Hello

    I'm trying to get a vlan to share more than two routers, but I'm stuck. I read on tons of things, but nothing seems to fit. I was wondering if someone could help me.

    I have attached both the packet trace and the jpeg of topology. It is 20 of VLANS I try to share, my goal is that PC13 on VLAN 20 (independent) should be able to request an IP address from the router 0 (which is the DHCP server) as well as all communication between other hosts on VLAN 20.

    Thanks in advance.

    Hi Ben,

    In principle, it is not possible between 2 routers. Packet tracer does not support this kind of thing between routers - as Gregory mentioned you could use L2TP that is not supported in packages or other tracers improved protocols. You may not use the same network range i.e. 192.168.3.0 IP on both sides without switch / switches catering to transport frames across on the other side.

    I had a go at your laboratory - was great fun! I enclose my version in this post.

    I had the same vlan on both sides, BUT:

    one side had the 192.168.3.0 rank - on vlan 20 but inaccessible from the other side, because there is no layer 2 connectivity.

    the other side had 20.20.20.0 rank - even once again, on the vlan 20, but nothing to cary managers through - where another IP subnet

    Things I changed were:

    • deleted the servers (not sure what purpose they were sailing - maybe it was for DHCP?)
    • OSPF changed between R0 and R1 for contiguity on the network 1.1.1.0/30
    • installation of new pools the 192.168 dhcp R0 and R1 20.20.20.0's
    • VLAN 20 exist in both places, but with different intellectual property regimes
    • everything is able to ping everything else.
    • changed the configuration of switches so they trunking VLAN relevant (which was not the case in your example)
    • some configurations of the trunk on the switches and sub interfaces.

    R0 on the left:

    DHCP excluded-address 192.168.2.1 IP 192.168.2.100

    DHCP excluded-address IP 192.168.3.1 192.168.3.100

    DHCP excluded-address IP 192.168.4.1 192.168.4.100

    !

    IP dhcp SALES pool

    network 192.168.2.0 255.255.255.0

    default router 192.168.2.1

    IP dhcp ADMIN pool

    network 192.168.3.0 255.255.255.0

    default router 192.168.3.1

    pool IP dhcp STUDENTS

    network 192.168.4.0 255.255.255.0

    default router 192.168.4.1

    !

    interface GigabitEthernet0/0

    no ip address

    !

    interface GigabitEthernet0/0.10

    encapsulation dot1Q 10

    IP 192.168.2.1 255.255.255.0

    !

    interface GigabitEthernet0/0.20

    encapsulation dot1Q 20

    address 192.168.3.1 IP 255.255.255.0

    !

    interface GigabitEthernet0/0.30

    encapsulation dot1Q 30

    192.168.4.1 IP address 255.255.255.0

    !

    interface GigabitEthernet1/0

    IP 1.1.1.1 255.255.255.252

    !

    router ospf 1

    Log-adjacency-changes

    1.1.1.1 to network 0.0.0.0 area 0

    network 192.168.0.0 0.0.255.255 area 0

    R1 on the right side:

    DHCP excluded-address IP 20.20.20.1 20.20.20.100

    !

    dhcp VLAN_20 IP pool

    network 20.20.20.0 255.255.255.0

    router by default - 20.20.20.1

    !

    !

    interface GigabitEthernet1/0

    no ip address

    !

    interface GigabitEthernet1/0.20

    encapsulation dot1Q 20

    IP 20.20.20.1 255.255.255.0

    !

    interface GigabitEthernet2/0

    IP 1.1.1.2 255.255.255.252

    !

    router ospf 1

    Log-adjacency-changes

    1.1.1.2 network 0.0.0.0 area 0

    0.0.0.0 network 20.20.20.1 area 0

    Hope that this is of interest to us

    Please note the useful messages and don't forget to mark resolved all questions answers. Thank you.

  • Routing VLAN of the Internet

    Hi all

    I am facing a problem since a few days now and can't seem to get the hang of it.

    -

    On my host, I have a physical NETWORK card with Internet access.

    I installed VMWare Server 2.0.

    I configured an address network 172.16.0.0 with a subnet 255.255.252.0 VMnet2, so I 172.16.0.1 - available for my virtual machine 172.16.3.254.

    My host / bridged network address is 192.168.2.0 with a subnet of 255.255.255.0.

    -

    I created 2 VM:

    -

    VM1 has 2 NETWORK interface card:

    NIC1 is bridged (((192.168.2.130) VMnet0) so this virtual machine to the internet).

    NIC2 with address 172.16.0.10 (VMnet2) I want to use for the virtual local area network with its own IP address / subnet.

    The other VM (VM2) has only 1 NIC (172.16.0.11) and connects to VMnet2, 172.16.0.0 network.

    So far, it works fine; the VM 2 can communicate via VMnet2 and use the virtual network to expand all. VM1 I also have Internet, since it is filled with my host. If I add the VMnet2 eCard to my host, I can also connect to the virtual machine via RDP with their 172,16 addresses.

    Now the question: I am trying to get internet from my host / transit network on the VMnet0 virtual LAN VMnet2, so my virtual network 172.16.0.0 has internet connection.

    I tried everything so far; Set the VM1 VM2 bridge, I installed RRAS on VM1, I added a static route on NIC2 to destination: 192.168.2.0, 255.255.255.0 Gateway 172.16.0.10, etc etc, but I just can't seem to get internet routed to the address 172.16.0.0 network.

    What I am doing wrong? I can give all VM a nic VMnet0 bridged, but I want them to use the 172.16 network - only-, with the exception of the VM1 who would work as a gateway through which they connect / route internet traffic to 192.168.2.0.

    Is my wrong setting, do I have to set up networks of VM servers different or is - this all simply not possible to deliver a 192.168.2.0/24 network to a network of 172.16.0.0/22 (which, to my knowledge, should be possible using the static routes)?

    Any help would be appreciated.

    With sincere friendships.

    Kami.

    KrazeyKami wrote:

    I am able to ping 192.168.2.130 from VM2. I can not however, ping 192.168.2.100 (my host PC) or 192.168.2.1.

    It's normal, your host does not have a return path, it will send the answers to queries its default gateway ping and who does not know how to reach 172.16.0.0.

    You have two options:

    1. If possible, you should indicate the default "main", a physical bridge, where yout host points etc. for a route to your virtual network, or

    2. you must add this route on all the systems that should be able to send packets back to 172.168.0.0.

    "Route add 172.16.0.0 mask 255.255.0.0 192.168.2.130 Pei."

    So I guess that the gateway properly functions, 192.168.2.130 are on VM1.

    Yes.

    Now for the next step, shouldn't there be any routing adds or ISA / RRAS to send data to my 192.168.2.1 on this NIC.130?

    The problem will be that your default physical bridge must be aware of the route back. If you are unable to add a route to this device, it (Internet connection) does not work.

    In this case, only NAT can help, as the packets appear to come from the 192.168.2.130 and the physical default gateway knew how to get to this address.

    AWo

    VCP 3 & 4

    \[:o]===\[o:]

    = You want to have this ad as a ringtone on your mobile phone? =

    = Send 'Assignment' to 911 for only $999999,99! =

  • Problemas con VLAN ID

    I have a con lost an ESX Server.

    El servidor Fisico're an IBM 3650 con while red Broadcom NetXtreme II BCM5708 server.

    Los equipos networking son Cisco 6500 is 4500.

    In a principio is pidio than boca in donde is instala Service Console tenga las made VLAN 1-2-3. Por lo veo main solo una sola Vlan number 1

    Luego lo what pedi are me conectaran otra con red boca the same presentation of VLAN. Y no veo none Vlan. Pero in ese instante cambio the config of the Plaça in donde tengo el Service Console y veo las 3 VLAN.

    I need no saber if're compatibility Québec problema no creo porque realmente me ifej junto al sector comunicaciones y Telnet appears las bocas his trunk, pero sigo sin ver config en the placa fr 2.

    Hola, not be TR sos ARE o EM (ponele has a firma che as no cuesta nada y uno sabe con quien habla) Québec tenes that hacer lo're pedir the time of networking you ponga boca del switch donde la o. conectas las los ESX en modo trunk while y por ese port you already pasar todas las VLANS that need usar (1,2,3 etc.).

    Dale UN rato y a VAS from las ahi a poder ver pero todas formas not you guies por lo that appeared in los "Observed the IP ranges" in mi experiencia porque no siempre muestran todos los rangos available for.

    Saludos has the muchachada.

    Nicolas Solop

    Buenos Aires, Argentina

    -

  • HP 6100 on extended connection problem router wireless

    We have two printers a 8600 while one and a new printer 6100. My Office I use a mac OSX Mavericks on the network SSID 'Outhouse' my wifes machine is in another building with the 6100 and the extended network SSID "outhouse_EXT".  We both need to be able to print to other printers. His laptop that runs Windows 7 works very well and can print on both machines. However I can't print its 6100. In an attempt to discover his printer nothing comes.

    Any help greatly appriciated.

    Hi detaylor12,

    I understand that you have a 8600 Officejet and an Officejet 6100 and want to be able to print to each of them, but have problems. I'm sorry to hear that, but I'm absolutely going to do my best to help you!

    The latrines and outhouse_EXT that both appear as options of connection on your Mac? If they do, I think that's the problem. You must be connected to the same network that the printer is turned on in order to access it. When you want to print to the printer of your wife, you would have to make sure that your Mac is connected to the network rather than the Outhouse network as your printer and your Mac are normally on outhouse_EXT.

    Give that a try and let me know if it helps

  • Problem router Cisco and Checkpoint VPN

    Hello

    I couldn't establish vp from site to site between cisco and checkpoint. Can you please check the logs?

    Thank you.

    * 29 sept 08:17:22.627: IPSEC (sa_request):,.
    (Eng. msg key.) Local OUTGOING = Y.Y.Y.Y:500, distance = X.X.X.X:500,
    local_proxy = 192.168.222.0/255.255.255.0/256/0,
    remote_proxy = 10.0.10.0/255.255.255.0/256/0,
    Protocol = ESP, transform = esp - aes 256 esp-sha-hmac (Tunnel),
    lifedur = 3600 s and KB 4608000,
    SPI = 0 x 0 (0), id_conn = 0, keysize = 256, flags = 0 x 0
    * 29 sep 08:17:22.631: ISAKMP: (0): profile of THE request is (NULL)
    * 29 sep 08:17:22.631: ISAKMP: created a struct peer X.X.X.X, peer port 500
    * 29 sep 08:17:22.631: ISAKMP: new created position = 0x88AD1AB0 peer_handle = 0 x 80000004
    * 29 sep 08:17:22.631: ISAKMP: lock struct 0x88AD1AB0, refcount 1 to peer isakmp_initiator
    * 29 sep 08:17:22.631: ISAKMP: 500 local port, remote port 500
    * 29 sep 08:17:22.631: ISAKMP: set new node 0 to QM_IDLE
    * 29 sep 08:17:22.631: ISAKMP: (0): insert his with his 88AF7D94 = success
    * 29 sep 08:17:22.631: ISAKMP: (0): cannot start aggressive mode, try the main mode.
    * 29 sep 08:17:22.631: ISAKMP: (0): pre-shared key found peer corresponding X.X.X.X
    * 29 sep 08:17:22.631: ISAKMP: (0): built of NAT - T of the seller-rfc3947 ID
    * 29 sep 08:17:22.631: ISAKMP: (0): built the seller-07 ID NAT - t
    * 29 sep 08:17:22.631: ISAKMP: (0): built of NAT - T of the seller-03 IDexit
    Router (config) #n
    * 29 sep 08:17:22.631: ISAKMP: (0): built the seller-02 ID NAT - t
    * 08:17:22.631 Sept. 29: ISAKMP: (0): entry = IKE_MESG_FROM_IPSEC, IKE_SA_REQ_MM
    * 08:17:22.631 Sept. 29: ISAKMP: (0): former State = new State IKE_READY = IKE_I_MM1

    * 29 sep 08:17:22.631: ISAKMP: (0): Beginner Main Mode Exchange
    * 29 sep 08:17:22.631: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:17:22.631 Sept. 29: ISAKMP: (0): a Packet.o IKE IPv4 send

    * 29 sep 08:17:32.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:17:32.631: ISAKMP (0): increment the count of errors on his, try 1 5: retransmit the phase 1
    * 29 sep 08:17:32.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE
    * 29 sep 08:17:32.631: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:17:32.631 Sept. 29: ISAKMP: (0): sending of a CPVPN IKE IPvaccess lists

    * 29 sep 08:17:42.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:17:42.631: ISAKMP (0): increment the count of errors on his, try 2 of 5: retransmit the phase 1
    * 29 sep 08:17:42.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE
    * 29 sep 08:17:42.631: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:17:42.631 Sept. 29: ISAKMP: (0): sending a packet IPv4 IKE...
    * 29 sep 08:17:52.627: IPSEC (key_engine): request timer shot: count = 1,.
    local (identity) = Y.Y.Y.Y:0, distance = X.X.X.X:0,
    local_proxy = 192.168.222.0/255.255.255.0/256/0,
    remote_proxy = 10.0.10.0/255.255.255.0/256/0
    * 29 sept 08:17:52.627: IPSEC (sa_request):,.
    (Eng. msg key.) Local OUTGOING = Y.Y.Y.Y:500, distance = X.X.X.X:500,
    local_proxy = 192.168.222.0/255.255.255.0/256/0,
    remote_proxy = 10.0.10.0/255.255.255.0/256/0,
    Protocol = ESP, transform = esp - aes 256 esp-sha-hmac (Tunnel),
    lifedur = 3600 s and KB 4608000,
    SPI = 0 x 0 (0), id_conn = 0, keysize = 256, flags = 0 x 0
    * 29 sep 08:17:52.627: ISAKMP: set new node 0 to QM_IDLE
    * 29 sep 08:17:52.627: ISAKMP: (0): SA is still budding. Attached new request ipsec. (local Y.Y.Y.Y, distance X.X.X.X)
    * 29 sep 08:17:52.627: ISAKMP: error during the processing of HIS application: failed to initialize SA
    * 29 sep 08:17:52.627: ISAKMP: error while processing message KMI 0, error 2.
    * 29 sep 08:17:52.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:17:52.631: ISAKMP (0): increment the count of errors on his, try 3 of 5: retransmit the phase 1
    * 29 sep 08:17:52.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE
    * 29 sep 08:17:52.631: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:17:52.631 Sept. 29: ISAKMP: (0): sending a packet IPv4 IKE.
    * 29 sep 08:18:02.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:18:02.631: ISAKMP (0): increment the count of errors on his, try 4 out 5: retransmit the phase 1
    * 29 sep 08:18:02.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE
    * 29 sep 08:18:02.631: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:18:02.631 Sept. 29: ISAKMP: (0): sending a packet IPv4 IKE.
    * 29 sep 08:18:12.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:18:12.631: ISAKMP (0): increment the count of errors on his, try 5 of 5: retransmit the phase 1
    * 29 sep 08:18:12.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE
    * 29 sep 08:18:12.631: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:18:12.631 Sept. 29: ISAKMP: (0): sending a packet IPv4 IKE.
    * 29 sep 08:18:22.627: IPSEC (key_engine): request timer shot: count = 2,.
    local (identity) = Y.Y.Y.Y:0, distance = X.X.X.X:0,
    local_proxy = 192.168.222.0/255.255.255.0/256/0,
    remote_proxy = 10.0.10.0/255.255.255.0/256/0
    * 29 sep 08:18:22.631: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:18:22.631: ISAKMP: (0): the peer is not paranoid KeepAlive.

    * 29 sep 08:18:22.631: ISAKMP: (0): removal of reason ITS status of 'Death by retransmission P1' (I) MM_NO_STATE (peer X.X.X.X)
    * 29 sep 08:18:22.631: ISAKMP: (0): removal of reason ITS status of 'Death by retransmission P1' (I) MM_NO_STATE (peer X.X.X.X)
    * 29 sep 08:18:22.631: ISAKMP: Unlocking counterpart struct 0x88AD1AB0 for isadb_mark_sa_deleted(), count 0
    * 29 sep 08:18:22.631: ISAKMP: delete peer node by peer_reap for X.X.X.X: 88AD1AB0
    * 29 sep 08:18:22.631: ISAKMP: (0): node-930113685 error suppression FALSE reason 'IKE deleted.
    * 29 sep 08:18:22.631: ISAKMP: (0): error suppression node 661004686 FALSE reason 'IKE deleted.
    * 08:18:22.631 Sept. 29: ISAKMP: (0): entry = IKE_MESG_INTERNAL, IKE_PHASE1_DEL
    * 08:18:22.631 Sept. 29: ISAKMP: (0): former State = new State IKE_I_MM1 = IKE_DEST_SA

    * 29 sep 08:18:22.631: IPSEC (key_engine): had an event of the queue with 1 KMI message (s)
    * 29 sept 08:18:27.559: IPSEC (sa_request):,.
    (Eng. msg key.) Local OUTGOING = Y.Y.Y.Y:500, distance = X.X.X.X:500,
    local_proxy = 192.168.222.0/255.255.255.0/256/0,
    remote_proxy = 10.0.10.0/255.255.255.0/256/0,
    Protocol = ESP, transform = esp - aes 256 esp-sha-hmac (Tunnel),
    lifedur = 3600 s and KB 4608000,
    SPI = 0 x 0 (0), id_conn = 0, keysize = 256, flags = 0 x 0
    * 29 sep 08:18:27.559: ISAKMP: (0): profile of THE request is (NULL)
    * 29 sep 08:18:27.559: ISAKMP: created a struct peer X.X.X.X, peer port 500
    * 29 sep 08:18:27.559: ISAKMP: new created position = 0x85EDF1F0 peer_handle = 0 x 80000005
    * 29 sep 08:18:27.559: ISAKMP: lock struct 0x85EDF1F0, refcount 1 to peer isakmp_initiator
    * 29 sep 08:18:27.559: ISAKMP: 500 local port, remote port 500
    * 29 sep 08:18:27.559: ISAKMP: set new node 0 to QM_IDLE
    * 29 sep 08:18:27.559: ISAKMP: find a dup her to the tree during the isadb_insert his 88C1CE60 = call BVA
    * 29 sep 08:18:27.559: ISAKMP: (0): cannot start aggressive mode, try the main mode.
    * 29 sep 08:18:27.559: ISAKMP: (0): pre-shared key found peer corresponding X.X.X.X
    * 29 sep 08:18:27.559: ISAKMP: (0): built of NAT - T of the seller-rfc3947 ID
    * 29 sep 08:18:27.559: ISAKMP: (0): built the seller-07 ID NAT - t
    * 29 sep 08:18:27.559: ISAKMP: (0): built of NAT - T of the seller-03 ID
    * 29 sep 08:18:27.559: ISAKMP: (0): built the seller-02 ID NAT - t
    * 08:18:27.559 Sept. 29: ISAKMP: (0): entry = IKE_MESG_FROM_IPSEC, IKE_SA_REQ_MM
    * 08:18:27.559 Sept. 29: ISAKMP: (0): former State = new State IKE_READY = IKE_I_MM1

    * 29 sep 08:18:27.559: ISAKMP: (0): Beginner Main Mode Exchange
    * 29 sep 08:18:27.559: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:18:27.559 Sept. 29: ISAKMP: (0): sending a packet IPv4 IKE.
    * 29 sep 08:18:37.559: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:18:37.559: ISAKMP (0): increment the count of errors on his, try 1 5: retransmit the phase 1
    * 29 sep 08:18:37.559: ISAKMP: (0): transmit phase 1 MM_NO_STATE
    * 29 sep 08:18:37.559: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:18:37.559 Sept. 29: ISAKMP: (0): sending a packet IPv4 IKE.
    * 29 sep 08:18:47.559: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:18:47.559: ISAKMP (0): increment the count of errors on his, try 2 of 5: retransmit the phase 1
    * 29 sep 08:18:47.559: ISAKMP: (0): transmit phase 1 MM_NO_STATE
    * 29 sep 08:18:47.559: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:18:47.559 Sept. 29: ISAKMP: (0): sending a packet IPv4 IKE.

    * 29 sep 08:18:57.559: IPSEC (key_engine): request timer shot: count = 1,.
    local (identity) = Y.Y.Y.Y:0, distance = X.X.X.X:0,
    local_proxy = 192.168.222.0/255.255.255.0/256/0,
    remote_proxy = 10.0.10.0/255.255.255.0/256/0
    * 29 sept 08:18:57.559: IPSEC (sa_request):,.
    (Eng. msg key.) Local OUTGOING = Y.Y.Y.Y:500, distance = X.X.X.X:500,
    local_proxy = 192.168.222.0/255.255.255.0/256/0,
    remote_proxy = 10.0.10.0/255.255.255.0/256/0,
    Protocol = ESP, transform = esp - aes 256 esp-sha-hmac (Tunnel),
    lifedur = 3600 s and KB 4608000,
    SPI = 0 x 0 (0), id_conn = 0, keysize = 256, flags = 0 x 0
    * 29 sep 08:18:57.559: ISAKMP: set new node 0 to QM_IDLE
    * 29 sep 08:18:57.559: ISAKMP: (0): SA is still budding. Attached new request ipsec. (local Y.Y.Y.Y, distance X.X.X.X)
    * 29 sep 08:18:57.559: ISAKMP: error during the processing of HIS application: failed to initialize SA
    * 29 sep 08:18:57.559: ISAKMP: error while processing message KMI 0, error 2.
    * 29 sep 08:18:57.559: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:18:57.559: ISAKMP (0): increment the count of errors on his, try 3 of 5: retransmit the phase 1
    * 29 sep 08:18:57.559: ISAKMP: (0): transmit phase 1 MM_NO_STATE
    * 29 sep 08:18:57.559: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    Router #.
    Router #.
    * 08:18:57.559 Sept. 29: ISAKMP: (0): sending a packet IPv4 IKE.
    * 29 sep 08:19:07.559: ISAKMP: (0): transmit phase 1 MM_NO_STATE...
    * 29 sep 08:19:07.559: ISAKMP (0): increment the count of errors on his, try 4 out 5: retransmit the phase 1
    * 29 sep 08:19:07.559: ISAKMP: (0): transmit phase 1 MM_NO_STATE
    * 29 sep 08:19:07.559: ISAKMP: (0): package to X.X.X.X my_port 500 peer_port 500 (I) sending MM_NO_STATE
    * 08:19:07.559 Sept. 29: ISAKMP: (0): sending a packet IPv4 IKE.
    Router #.
    Router #un all
    All possible debugging has been disabled

    The log shows main mode setup has failed.  See if this helps: http://www.itcertnotes.com/2011/04/ipsec-stuck-in-mmsasetup-and-mmnostat...

  • Problems with VLAN...

    Hello

    I try to get a controller 2106 (latest firmware) and 3 1252 to our network access points. We have 3560 switches to base with a few VIRTUAL networks. I can put it all fine on its own with my laptop on the WAC himself, but connect it to a switch port in our server VLAN does work at all. Its not accessible via ping, telnet, HTTP.

    I have for this kind of work. I created a switchport mode trunk and I ALSO HAD to TAG management/access point interfaces. It's the only way I can telnet/HTTP in to the WAC. BUT I can't do now within this server VLAN. I can't reach our client device, VLAN, or I can reach the WAC to our client VLAN. Even with the trunkport game, if I put the interfaces on the WAC to unlabeled, I can't do anything on the WAC at all! Any ideas what I'm missing?

    Thank you

    Make sure you have all the VLAN defined on the switch. Make sure all connections to the switch are attached to the trunk. Each vlan must also a layer 3 interface. management and the ap-Manager should be on the same vlan and the dot1q trunk port must be defined on vlan native x where X is the vlan, management and ap-Manager ip is on. On the WLC, you must set the tag of vlan '0' unidentified. Who should you get.

    Place the access point on the same subnet as the management and the ap Manager and make sure that there is a for this subnet dhcp scope to the ap can obtain an ip address and be able to join the WLC. Then, you can move the access point to a different subnet if you wish.

Maybe you are looking for