Cannot Assign IP to a vlan interface SG-300 28MP

hI all a very simple configurations ... bought 10 smb sg-300 28mp switches . every thing goes fine in vlan configuration, port assigning .. but when I try to assign ip to one of the created vlan interface switch hangs GUI or CLI. Layer 3 is enabled. regards

Configure as below
Login to CLI:
switch(config):int vlan 1
switch(int-config):ip address 192.168.1.254 255.255.255.0
switch(int-config):no ip dhcp relay enable
switch(config):do wr
switch(config):int vlan 2  -----------------------> New vlan 
switch(int-config):ip address 192.168.2.xx 255.255.255.0
switch(int-config):no ip dhcp relay enable
switch(config):do wr

Similar Messages

  • ASA 5505 Unable to assign ip to DMZ vlan interface

    hi all,
    I have ASA  5505 with base license.
    I created 3rd  vlan on it.it was created.
    but i am unable to assign IP to it.
    i assign ip address it takes it.
    But when i do sh int ip brief it does not show any ip.
    ciscoasa# sh int ip brief
    Interface                  IP-Address      OK? Method Status                Prot
    ocol
    Ethernet0/0                unassigned      YES unset  up                    up
    Ethernet0/1                unassigned      YES unset  up                    up
    Ethernet0/2                unassigned      YES unset  up                    up
    Ethernet0/3                unassigned      YES unset  administratively down down
    Ethernet0/4                unassigned      YES unset  administratively down down
    Ethernet0/5                unassigned      YES unset  administratively down down
    Ethernet0/6                unassigned      YES unset  administratively down down
    Ethernet0/7                unassigned      YES unset  administratively down down
    Internal-Data0/0           unassigned      YES unset  up                    up
    Internal-Data0/1           unassigned      YES unset  up                    up
    Vlan1                      192.168.1.1     YES CONFIG up                    up
    Vlan2                      192.168.11.2    YES CONFIG up                    up
    Vlan3                      unassigned      YES manual up                    up*************************************************************
    Virtual0                   127.0.0.1       YES unset  up                    up
    ciscoasa# config t
    ciscoasa(config)# int vlan 3
    ciscoasa(config-if)# ip ad
    ciscoasa(config-if)# ip address 192.168.12.2 255.255.255.0
    ciscoasa(config-if)# end
    ciscoasa# wr mem
    Building configuration...
    Cryptochecksum: 808baaba ced2a226 07cfb41f 9f6ec4f8
    4608 bytes copied in 1.630 secs (4608 bytes/sec)
    [OK]
    ciscoasa# sh int ip brief
    Interface                  IP-Address      OK? Method Status                Prot
    ocol
    Ethernet0/0                unassigned      YES unset  up                    up
    Ethernet0/1                unassigned      YES unset  up                    up
    Ethernet0/2                unassigned      YES unset  up                    up
    Ethernet0/3                unassigned      YES unset  administratively down down
    Ethernet0/4                unassigned      YES unset  administratively down down
    Ethernet0/5                unassigned      YES unset  administratively down down
    Ethernet0/6                unassigned      YES unset  administratively down down
    Ethernet0/7                unassigned      YES unset  administratively down down
    Internal-Data0/0           unassigned      YES unset  up                    up
    Internal-Data0/1           unassigned      YES unset  up                    up
    Vlan1                      192.168.1.1     YES CONFIG up                    up
    Vlan2                      192.168.11.2    YES CONFIG up                    up
    Vlan3                      unassigned      YES manual up                    up
    Virtual0                   127.0.0.1       YES unset  up                    up
    ciscoasa# sh ver
    Cisco Adaptive Security Appliance Software Version 8.2(5)
    Device Manager Version 6.4(9)
    Compiled on Fri 20-May-11 16:00 by builders
    System image file is "disk0:/asa825-k8.bin"
    Config file at boot was "startup-config"
    ciscoasa up 3 days 17 hours
    Hardware:   ASA5505, 256 MB RAM, CPU Geode 500 MHz
    Internal ATA Compact Flash, 128MB
    BIOS Flash M50FW080 @ 0xffe00000, 1024KB
    Encryption hardware device : Cisco ASA-5505 on-board accelerator (revision 0x0)
                                 Boot microcode   : CN1000-MC-BOOT-2.00
                                 SSL/IKE microcode: CNLite-MC-SSLm-PLUS-2.03
                                 IPSec microcode  : CNlite-MC-IPSECm-MAIN-2.05
    0: Int: Internal-Data0/0    : address is 001d.a24d.ed0e, irq 11
    1: Ext: Ethernet0/0         : address is 001d.a24d.ed06, irq 255
    2: Ext: Ethernet0/1         : address is 001d.a24d.ed07, irq 255
    3: Ext: Ethernet0/2         : address is 001d.a24d.ed08, irq 255
    4: Ext: Ethernet0/3         : address is 001d.a24d.ed09, irq 255
    5: Ext: Ethernet0/4         : address is 001d.a24d.ed0a, irq 255
    6: Ext: Ethernet0/5         : address is 001d.a24d.ed0b, irq 255
    7: Ext: Ethernet0/6         : address is 001d.a24d.ed0c, irq 255
    8: Ext: Ethernet0/7         : address is 001d.a24d.ed0d, irq 255
    9: Int: Internal-Data0/1    : address is 0000.0003.0002, irq 255
    10: Int: Not used            : irq 255
    11: Int: Not used            : irq 255
    Licensed features for this platform:
    Maximum Physical Interfaces    : 8
    VLANs                          : 3, DMZ Restricted
    Inside Hosts                   : Unlimited
    Failover                       : Disabled
    VPN-DES                        : Enabled
    VPN-3DES-AES                   : Enabled
    SSL VPN Peers                  : 2
    Total VPN Peers                : 10
    Dual ISPs                      : Disabled
    VLAN Trunk Ports               : 0
    Shared License                 : Disabled
    AnyConnect for Mobile          : Disabled
    AnyConnect for Cisco VPN Phone : Disabled
    AnyConnect Essentials          : Disabled
    Advanced Endpoint Assessment   : Disabled
    UC Phone Proxy Sessions        : 2
    <--- More --->
    Need to know does this License support IP  to 3rd vlan ?
    Thanks
    Mahesh

    Hi Julio,
    I tried to config namef if but here is result
    ciscoasa# sh run int vlan 3
    interface Vlan3
    description DMZ  to 3550 New Switch
    no nameif
    security-level 50
    ip address 192.168.12.2 255.255.255.0
    ciscoasa# config t
    ciscoasa(config)# int vlan 3
    ciscoasa(config-if)# name
    ciscoasa(config-if)# namei
    ciscoasa(config-if)# nameif DMZ
    ERROR: This license does not allow configuring more than 2 interfaces with
    nameif and without a "no forward" command on this interface or on 1 interface(s)
    with nameif already configured.

  • Ipv6 Vlan Interface EUI-64 assignation problem

    Hello, I have 2 routers 1800 series with switch modules incorporated connected with IPv6. Everything is working fine except for the problem that when I assign an IPv6 address to a Vlan (using the EUI-64 format to the switch ports), it assigns the SAME interface id (last 64 bits of the IPv6) of a fastEthernet port (FE 0/0), to the vlan, causing an error problem of duplicity:
    " c..T, overlaps with another prefix "
    Why does the EUI-64 assigns the MAC address of the FastEthernet ports instead of the ones in the switch modules?

    Thanks for the reply, but I just solved the problem. The problem was with the command IPV6 ADDRESS AUTOCONFIGURATION. This command definitely brings up a lot of trouble with VLAN ipv6 address assignation.
    After some testing I concluded that:
    1- If one interface has the IPV6 ADDRESS AUTOCONFIGURATION mode on, the interface could end up with more than one ipv6 global interface address.
    2- You cannot assign this mode to a vlan interface without getting into configuration problems.
    3- If a FastEthernet Interface has this mode on(IPV& A. A.), the router does not let you assign a global unicast address to the vlan interface, and gives the following error message:
    %IPV6-6-ADDRESS: 3FFE:C00:C18:F100:213:C4FF:FE44:4961/64 can not be configurex
    4- For the VLAN`s Interface ID you have to manually assign the link local address with the command line
    IPV6 ADDRESS FE80::1 (or any other unique link local address) LINK-LOCAL.
    This is for Vlans that are in a switch module of the same router.
    All this testing was for a Cisco router 1800 series with a switch module integrated in the router.
    Could be that this command is used for other specific occasions which I am not aware of.
    Regards,
    Grupo GTD

  • MSFC - cannot ping vlan interface

    Hi,
    We have several vlans defined on the mfsc. On the msfc we could ping all the vlans interface except 1 vlan. The interface is up and just recently we weren't able to ping it. Any help is much appreciated.
    TIA.
    PF

    Hi PF,
    AFAIK, When you are pinging a particular interface stting on the MSFC the source IP would be of any other available interfaces. If you are pinging vlan 110 it will take source ip of any other available vlan interface and the destination is Vlan 110, but ACL defined on the interface doesnot have any ACE for the same so that packets will be dropped.
    Removing the ACL worked as explained above.
    regards,
    -amit singh

  • OVM 3.0.3 - cannot add new server to VLAN group with bonded VLANs

    I have a new OVS 3.0.3 server built with 2 bonded interfaces and a single VLAN running on top for the management interface. It gets discovered fine by OVM Manager (I'm running Version: 3.0.3.126, Build: 20111214_126)
    I am trying to add it to a VLAN group with two VLANs -- the existing management VLAN (ID=300) plus one other (ID=301). (I already have one identical server assigned to the VLAN group, with both VLAN interfaces configured and running fine.) This works OK, and I can see VLAN 301 for the new server in Oracle VM Manager with no IP address assigned to it.
    However, when I try to apply an IP address to the VLAN (via Hardware / Resources / VLAN Groups / Edit VLAN Group / Configure IP Addresses / VLAN Interfaces) it fails with this error:
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: dispatch to server: whyovmprd02 failed. OVMAPI_4004E Server Failed Command: dispatch https://?uname?:[email protected]:8899/api/1 ovs_br_config start 0004fb0010be2df bond0.301, Status: org.apache.xmlrpc.XmlRpcException: exceptions.RuntimeError:Command ['/etc/xen/scripts/ovs-network-bridge', 'start', 'bridge=0004fb0010be2df', 'netdev=bond0.301'] failed (1): stderr: ovs-network-bridge Start: No such device bond0.301
    Oracle VM Manager seems to be expecting the subinterface for VLAN 301 to exist on the server already - which it doesn't of course, because the server has just been built, so it only has its management interface VLAN in place (VLAN ID 300)
    I have managed to work around this by removing VLAN segment 301 from the VLAN group completely, then adding it back in with the IP addresses for both servers in place. This seems to convince Oracle VM Manager that it needs to create the bond0.301 subinterface before it configures it. However, I obviously had to shut down all VMs to do this, and it was really messy as VLAN 301 is the storage network, so my original server lost contact with the NFS storage for a while which caused it to fence etc.
    There must be another way??! Any pointers would be very much appreciated.

    Avi Miller wrote:
    It's fixed in 3.1. In the meantime, if you can remove and reapply the Virtual Machine role on that network, it'll recreate the bridges for you.Thanks for replying Avi. (I won't ask you for a release date for 3.1 :))
    I did try that initially, but it didn't seem to help - I got this error back:
    Job Internal Error (Operation)com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_4010E Attempt to send command: dispatch to server: whyovmprd02 failed. OVMAPI_4004E Server Failed Command: dispatch https://?uname?:[email protected]:8899/api/1 ovs_if_meta bond0.301 ethernet:0004fb00100a35f{why-be-301}:STORAGE, Status: org.apache.xmlrpc.XmlRpcException: exceptions.Exception:ovs_set_metadata: interface /sys/class/net/bond0.301 does not exists
    This appears to be from ovs_if_meta in /opt/ovs-agent-3.0/OVSVMNetConfig.py, which looks to be where the agent tries to write out the new roles for the network into the metadata file - it seems to be expecting the VLAN to exist already, and specifically checks in /sys to make sure that it is there.
    Should / could I add a step to my kickstart build to force the 301 VLAN to be created maybe? This would bring it into line with the other VLAN that is used for management, which is of course sitting there ready and waiting as soon as the server is built.

  • VLAN Interface Command

    Ok, I thought I had the reason for the VLAN interface command down. I thought it was either used for switch management or routing between VLANS? However, now I realized that some communication wont work with out this command which doesnt make sense. If I have a VLAN, then the switch will only switch packets to ports on the same VLAN. The only way, communication would work between VLANS is if I either enabled routing between VLANs with the VLAN Interface command, connected the switch to another multi-layer switch that did do routing between VLANS, or connected the switch to a router which routed between the VLANs.
    However, I just got this new 3550 switch in, configured the correct ports with the assigned VLANs, and the only way my cisco ip phone would work is if the VLAN Interface for my voice-ip VLAN was configured. The 3550 is connected to a 4507. Now, can someone tell my why this is? You shouldnt have to configure the VLAN Interface, right?(unless I wanted to route between VLANs, which could be done by the 4507)

    Sounds to me like you either dont have the dot1q trunk interface between your 4506 and 3550 working properly, or your 3550 is running the enhanced image which allows routing.
    It would be nice to see your config on both the 3550 and the 4500 to determine the reason. Just a stab at how it should be configured is that on your 4506, you have it running VTP server or transparent with the defined Data and Voice Vlan's. You have a port configured for trunking (which connects to the 3550). On your 3550, you have configured it as a vtp client or transparent and have verified that it has received (or if transparent VTP you have configured) the appropriate VLAN's. You than specified "interface VLAN #" or whatever number for switch management and configured the port that connects to the 4500 as a trunk. Your port connected to the port has the auxillary or voice vlan configured. If this is how your equipment is configured and it still does not work, than look for the line "ip routing" in your 3550 and negate it with "no ip routing".
    If still no worky worky, post your config.
    Cheers,

  • Ath9k wireless card "Cannot assign requested address"

    # ip link set wlan0 up
    RTNETLINK answers: Cannot assign requested address
    #ip addr
    1: lo: <LOOPBACK,UP,LOWER_UP> ntu 16436 qdisc noqueue state UNKNOWN
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope list lo
    2: wlan0 <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
        link/ether 01:08:ca:e6:bc:76 brd ff:ff:ff:ff:ff:ff
    #iwconfig
    lo      no wireless extensions
    wlan0   IEEE 802.11bgn  ESSID:off/any
            Mode:Managed Access Point: Not-Associated  TX-Power-0dBm
            Retry long limit:7  RTS thr:off  Fragment thr:off
            Encryption key:off
            Power Management:on
    Please do excuse if there's a silly typo somewhere in those; not knowing how to do it any better, I've simply re-typed the terminal output into this computer, so I can't promise it free of mistakes. (There's got to be a better way to do that, right?
    Asus UX31E-DH72 Zenbook
    clean install of the 2011.08.19-core-x86_64 release
    There is no ethernet port; only WiFi and a ASIX AX88772B USB-to-ethernet that shipped with the system. (no optical drive either; but that's not really relevant to this)
    My current system has never been on the internet (well, since I wiped the Windows off of it...), and so I haven't been able to pacman properly. When I try to use makepkg, it claims it's missing a dependency on Linux-Headers. However, I do know that the wireless card works, seeing as how it had been working just fine under Windows.
    If it's relevant: during install, I left the NETWORKING section of rc.conf blank (as the Beginner's Guide says to do for DHCP), like so:
    HOSTNAME="zen"
    interface=wlan0
    address=
    netmask=
    broadcast=
    gateway=
    #NETWORKS=(main)
    Disclaimer: I'm rather new to the forums here and entirely new to Arch (which is my first Linux distro after years of OSX and a few weeks of Windows). Not scared of the command-line, but you may have to spell things out. Also, I understand if you'd rather not spend time explaining yourself, but I'm a strong believer in teach-a-man-to-fish, so if you'd like to explain rather than just walk through, it'd be much appreciated. Thanks!

    Welcome and congrats on your decision to grace your sleek new laptop with an equally sleek OS :-)
    Just in case you have not found that yet: there is actually a wiki page on your notebook for later setup specifics: https://wiki.archlinux.org/index.php/Asus_Zenbook_UX31E
    BTW: I just read there that the usb ethernet is supported in later/newer kernels out-the-box (if setting up wifi really does fail, you can get a later ISO maybe and use that for starters).
    As I understand your current setup state, you have installed the system with the core August release and it boots fine? Please confirm.
    Also please confirm the exact wifi card the notebook has:
    lspci -nn | grep net
    or
    lspci -nn >> ryebookpcidevices.txt
    The later pipes the output to a file. Doing the command again, appends to the file. We only need the exact PCI ID of the wifi card to double check. To save typing even that ID you can maybe copy the file you created "ryebookpcidevices.txt"  to an usb stick, if that automounts under /media/...
    Next, please quote here any errors you get when re-loading the ath9k module (all commands below need root/sudo):
    rmmod ath9k
    modprobe ath9k
    If you get errors, check whether
    rfkill list
    gives valid output (not sure if that package is on the ISO, i doubt it actually).
    If modprobe does without error, please retry your trial to connect with the card by directly issuing
    iwlist wlan0 scan
    Give us feedback on what happens then. If there is an error, try
    ip link set down
    and start from step 0 in the wireless wiki: https://wiki.archlinux.org/index.php/Wi … nual_setup
    Your output says "Mode:managed", so something seems working there already..
    For "makepkg" you indeed need the headers, but you dont say what you want to compile at this stage.

  • WLC - 4402/4 - Vlan Interface Addressing

    I currently have 7 WLCs with the same Vlan interfaces defined across all 7 controllers. Does anyone know the best practice for addressing these interfaces on each of the WLCs. I currently have each unique Vlan interface assigned with the same IP address across all 7 WLCs. This is working. Should I leave it this way or should I assign each controller with a different address for the Vlan interface?

    The controllers, assuming you have it configured as such, act as dhcp relay agents. Presumably, if the router got the wrong mac address in its arp entry, the dhcp message would be lost.
    Clients could have taken a while before getting a dhcp addr (race condition for router arp entry) and not been able to work if dhcp was required.
    That said, I've seen the controllers work with the dhcp server set to 255.255.255.255 so the ip helper addresses on the routers would pick up the requests.

  • How can I solve this problem? logical vlan interface shutdown

    our backbone system is 5509, 6509 ,
    5509 and 6509 os is cat os.
    we make a 2 static routes to specific destination.
    I make a vlan 209, 211 and put a port 3/13, 3/14
    I assign ip address in vlan 209, 211 in msfc mode
    and config 2 static route like this
    ip route 1.1.1.0 255.255.255.0 10.1.6.1
    ip route 1.1.1.0 255.255.255.o 10.1.7.2 100
    when we are testing backup link test..
    we extract port in 3/13(this is vlan209)
    but vlan 209 interface is not shutdowned
    so routing table does not change
    we must make vlan209 shutdown in 6509 msfc routing
    and pass 10.1.7.0 network!.
    how can i slove this problem?
    help me!

    hi there
    if u r making a vlan and giving an IP address u r creating an SVI, switched virtual interface, this interface will not go down even if u take out a port from the vlan, that port will go down but not the SVI.
    u need to give the shutdown command in the SVI to put it down.
    an SVI is not a physical interface so u need to make arrangements accordingly.
    Shukky
    India

  • Vlan Interface state constantly disabled

    Hi.
    I have a SF500 in layer 3 mode. I have 5 vlans (10,100,200,201,202)
    Of these 5 vlans, each one has a vlan interface configured.
    However, vlan 10 and 202 don't have an IPv4 route (which is created automatically I believe).
    I had a look and the vlan interface state is set to 'Disabled' (yes I'm using the GUI...)
    Whenever I click 'Edit', it brings up the new window, but it has a tick in the Enabled box. Unchecking and applying and then checking and applying makes no difference.  I just can't seem to change the state of the vlan interface.
    Am I missing something weird?
    Cheers.
    Andy

    Hi.
    Thanks forumers!! 
    Turns out that even thought it was assigned to an interface, the static route never appeared until the end device was connected (even if you tried to access that vlan from a different vlan).
    For example, the internal interface vlan 1 (192.168.1.254) would never have a route added until a device appeared on a vlan1 port - even if a device on a vlan2 port had access to vlan1,  it didn't recognise it as being valid.
    Many thanks for your help!
    Andrew

  • 3750X - Dropped multicat traffic flooding on all switchport vlan interfaces

    Hello forum, 
    I have a problem on source  multicast blocking. I have a switch with a vlan interface (Ex. vlan 20 )and on that vlan interface an extended ACL is present. That ACL block specific multicast groups. Furtehrmore I have many switchport access interfaces on vlan 20 with different sources connected. 
    If one source start streaming with multicast destination IP blocked  by ACL, dropped traffic is flooaded on all switchports on source's vlan
    IGMP snooping on this vlan is enabled but seems that dropped  traffic stay on L2 vlan without it.
    Device used: C3750X
    IOS:  15.0(2)SE5
    Thank you for help

    Hi Michal,
    thanks for your reply!
    Yes, probably i've captured all lines of access-list... but I've to change my approach because my access-list is a extended "named" access-list and, on other post, I've read that "named" access-list cannot be debugged...
    Now i've deleted all access-lists entries that refer to vlan2 and I've created new one "numerical":
    #ip access-list extended 100
    #10 ip permit 172.16.2.0 0.0.0.15 any log
    In this mode the debug shows only access-list 100 traffic + bcast + mcast.
    But, the strange thing is another one now...
    I've bought a multifunction printer, that send scanned document to a email account, the printer haven't internal smtp, it makes a connection to hp servers that forward scans to real destination address...
    I was curious to find out how this connection works because, my private/confidential documents are send on internet and, i would hope that hp use a secure connection from my printer to its server...
    Well, if I add "log" switch command at the end of access-list, or I enable access-list debug, the printer stop to comunicate to hp services/server... if I turn off debug or rewrite access-list without "log" feature, incredibly the printer re-start to comunicate with hp...
    Have you any idea that explain that? I'm going crazy...

  • EA6200 assigning private IP to LAN interface

    Cannot assign private IP address to router's LAN interface, for example 172.16.30.1 Router shows saying "invalid IP address range" I have an office LAN with this IP range, so changing to default 192.168.x.x is not a good option. Is there any fix?

    droonek121 wrote:
    Cannot assign private IP address to router's LAN interface, for example 172.16.30.1 Router shows saying "invalid IP address range" I have an office LAN with this IP range, so changing to default 192.168.x.x is not a good option. Is there any fix?
    Hi,
    I'm just wondering how did you assign that IP. I tried it on my friend's router and it accepted it without any issue. Please see screenshot below:
    If everyone needs to believe in something, I believe I'll have another beer..

  • 2612 - vlan interfaces

    I just recently bought a couple 2612s for a home lab. I intended on creating layer 3 interfaces on them to route between vlans. I can creat a subinterface off of e0/0, but I cannot configure encapsulation (dot1q or isl). Can I create a VLAN interface on a 2612?
    Thanks!

    According to below info. starting from 12.2(2)T, 2612 can support 802.1q.
    http://www.cisco.com/en/US/products/hw/routers/ps259/prod_bulletin09186a00800921e4.html
    Hope this helps.

  • Force a svi vlan interface

    HI..
    Is there a way to force a svi vlan interface to up if no physical link is connected on a ws-c3650 version 03.03.02se.
    /Lasse

    You will need to have the vlan configured and assigned to an interface before the svi will be up/up.

  • Assign DHCP Pools to VLAN on SG500

    Hello,
    I want to use the internal DHCP Server of a SG500-Stack (Layer3-Mode) to assign addresses to several VLANs.
    I was able to create several Pools, but I didn't find any option to assign these pools to VLANs or Ports.
    For Example:
    Addresses from Pool 192.168.0.0/24 are assigned to VLAN10
    Addresses from Pool 10.0.0.0/24 are assigned to VLAN20
    Addresses from Pool 10.128.128.0/24 are assigned to VLAN30
    Is this possible with a SG500?
    If it is, please give me a hint where I can set this up as I didn't find anything about this.
    Thanks in advance,
    Christoph

    This is an example to create Vlan and DHCP per vlan and how to assign the port to vlan
    but before please change the mode of the router to layer 3 and ensure you have the latest firmware
    1. Create a vlan
    #configure terminal
    #vlan database
    #vlan 10
    #vlan 20
    #vlan 30
    #exit
    2. Create interface of the Vlan's
    #interface vlan 10
    #ip address 192.168.0.254 255.255.255.0
    #interface vlan 20
    #ip address 10.0.0.254 255.255.255.0
    #interface vlan 30
    #ip address 10.128.128.254 255.255.255.0
    #exit
    3. Enable DHCP server on vlan's in this example the range is from 100 to 200 hosts
    #address low 192.168.0.100 high 192.168.0.200 /24
    #address low 10.0.0.100 high 10.0.0.200 /24
    #address low 10.128.128.100 high 10.128.128.200 /24
    #exit
    4. Assign the port to Vlan 10 and 20 and 30 in my example I assign port 1 to vlan 10 , port 2 to vlan 20 and port 3 to vlan 30
    #interface gigabitethernet 1/1
    #switchport mode access
    #switchport access vlan 10
    #exit
    #interface gigabitethernet 1/2
    #switchport mode access
    #switchport access vlan 20
    #exit
    #interface gigabitethernet 1/3
    #switchport mode access
    #switchport access vlan 30
    #exit
    So now connect pc with on port 1,2,3 to make a test
    Please lets me know and please rate the post and mark answered to help other customers
    Thanks
    Mehdi

Maybe you are looking for