SG300 & AutoSmart ports for VLAN

I have a couple of questions regarding the use of the voice VLAN & autosmart ports. I was running into some issues getting this to work %100 in my environment. Here is my network in a nutshell,
Single SG300 52 port switch, ports 1-47 are configured Untagged VLAN110 (my PC LAN) and Tagged allowed VLAN 140 (my voice VLAN)  the default VLAN on the switch is 1 and I have no IP assigned to it and have it shut.
Doing various reading I found this on the forums:
"The Macro's just get in the way most of the time. From a default state on the switch a user will set the voice vlan id with the commands
(config)#voice vlan id 100
** this will create vlan 100
voice vlan ? ** you can use to change your default dscp and cos settings a long with any other settings.
(config)#voice vlan state auto-enabled
(config)#interface range fa1-24
(config-if-range)#switchport trunk native vlan 101
(config-if-range)#switchport trunk allowed vlan add 100
** this will set the native vlan on the trunk port to 101 for data and the tagged vlan will be 101 for voice.
CDP is automatically enabled and should learn the capabilities of the phone and join the phone to vlan 101 on that port."
This worked well for my except in the scenario where I would have a  phone plugged into the switch and a desktop plugged into the back of the phone. I would have to set the macro for IP Phone + Desktop and set the VLAN value for the desktop to 110. If I did not it would stay at VLAN ID of 1.  Is this my only option? Should I change the default VLAN to 110 and just delete VLAN 1? I was also running into a random issue with my laptop only where certain ports I would connect to (even though 1-47 are all configured the same) would just put my laptop on VLAN 1, I would look at the autosmart port and it would just say "Default". I also unchecked all of the macro options except for IP Phone & IP Phone + Desktop. I really only want to use this for phones, I don't need the autosmart ports doing anything else. Any suggestions or tips for this?

Yes, by default the "phone - PC" macro will set the default of untagged Vlan on the port to Vlan 1.  You should just edit this macro and change the native_vlan parameter to 110.  Thus when this macro is executed the untagged Vlan will be 110.
No, you should not need to change the default Vlan
Correct uncheck all the type expect the IP Phone & IP Phone + Desktop

Similar Messages

  • Sg300 define IP for VLAN

    I have SG300 Switch running on L3 mode. I can`t assign IP to VLANS .when I try it through CLI or GUI switch crashes and needs reboot.

    Hi skasiri,
    Am having the same problem that I losing connection after you assign IP to a Vlan. But lets try:
    Lets say if your switch ip that you connect to is: 192.168.1.254 which is default ip for switch.
    And you try for example assign 10.0.1.1 to your 2nd vlan and lost connection, you can try to change your ip on your PC to 10.0.1.2-254(choose an ip in range of 2-254) if you can connect with 10.0.1.2 try to check if your vlan been assign.
    "Notice" if your 10.0.1.1 vlan port to GE1, you need to connect your cable from pc to GE1 on the switch.
    hope its help

  • Span Port (For Whole Vlan)

    Hi All,
    I have a similar setup to the attached. I want to make sure that I mirror all traffic going through vlan 1. The Server is my device that I will be mirroring all traffic to. How do I ensure that traffic from all switches on VLAN 1 is mirrored to the port the server is plugged into? 
    On the Core switch I currently have the following -
    monitor session 1 source vlan 1
    monitor session 1 destination interface Gi4/0/22  (This is where my server is plugged into)
    But I don't think I'm actually monitoring traffic from the other switches. Is there something else I need to add / configure on my access switching to ensure I'm spanning all VLAN 1 traffic from all switches to my server?
    Thanks

    Are you monitoring on an egress switch like the switch that the default gateway is for all of your users? If so, you should be capturing everything. If not, you'll possibly need to move your capture. This type of capture is local to a switch. The only other way that I know if is to create an RSPAN session on every switch that you want to capture from. You create a special remote span vlan. On the edge switch, monitor for vlan 1 as the source, and the destination is that special vlan. Do that for every switch. On your capture switch, monitor the source of the special vlan and then your destination would be your port. You would capture all traffic at that point..
    HTH,
    John

  • Is it better to use router port versus vlan member port?

    Hi CSC,
    This is more of a philosophical or "best practices" question.
    I have a Cisco 3550 at the home office. Connected to the 3550 is a number of branch offices by way of T1 circuits or VDSL modems. They all come to the home office, where we have a central internet connection and server farm for our entire organization.
    Except for one special case branch office, we don't forsee the need for appearances of the  home office vlan at the branch office sites. In that case, we bring it  into a trunk port at the home office, and at the special case branch office we have a dell 3024  switch and tag some ports as vlan 18 (the home office) or vlan 27 (the  special case branch office).
    We also do not forsee a need for the vlan from one branch office to appear at another branch office.
    They are all (except for the special case mentioned above) currently configured something like this:
    interface FastEthernet0/1
    description home office
    switchport access vlan 18
    switchport mode access
    interface FastEthernet0/2
    description t1 to branch office 1
    switchport access vlan 19
    switchport mode access
    interface Vlan18
    description subnet for home office
    ip address 192.168.18.1 255.255.255.0
    interface Vlan19
    description subnet for branch office 1
    ip address 192.168.19.1 255.255.255.0
    Is it better, in terms of reduced network complexity or performance on my 3550, to do something like this instead?
    That is, to make the interfaces router ports as opposed to vlan member ports?
    Of course, if we ever DID need to have appearances of the home office vlan at branch office sites, or appearances of one branch office's vlan at another branch office, we would lose that flexibility.
    interface FastEthernet0/1
    description home office
    switchport access vlan 18
      switchport mode access
    interface FastEthernet0/2
    description t1 to branch office 1
    ip address 192.168.19.1 255.255.255.0
    interface Vlan18
    description subnet for home office
    ip address 192.168.18.1 255.255.255.0
    no vlan 19

    Hello,
    In my opinion there is no 100% right answer here. I think it depends also about network forecast. I'll try to add here some thoughts:
    - if you use trunk interfaces from home to branch and SVI for L3 connection, in terms of scalability is much easier to expand (you have now only one p2p L3 link, but in future you'll need another one; if the port is a trunk one, you just configure another SVI interface, allow vlan on trunk and your good to go)
    - trunk interfaces involve more configuration (L2 interface and SVI L3 interface)
    - if you add in the home office another switch to existing one, and for some reason you have misconfiguration in STP / VTP, then you can run into problems like loops, vlan database modification (e.g. VTP server mode and the new added switch has a higher revision number than existing one)
    - L3 physical interfaces are easier to configure and less complex, but in case you want to scale to additional p2p link will be harder
    - L3 configuration is easier to troubleshoot as you avoid the L2 complexity
    - in terms of packet exchange a L3 interface will exchange less packets than a L2 trunk with SVI (I'm talking here about control traffic, not user traffic)
    - with L2 trunk you can have other problems like if somebody is "smart enough" to add a new switch into the existing switch (if you have a switch there) at the branch location; imagine that the new switch due to misconfigurated STP became root bridge; you have a large STP domain.
    As I said, there is no good or bad approach. You have to guide yourself about forecasts in your network. For example if you know that a branch location will not be extended in the next 2 years, then go ahead with L3 interface and that's it. On the other hands if you have doubts you can add for another location L2 trunk with SVI. You can mix this two solution to obtain the best results for your network characteristics.
    Cheers,
    Calin

  • SG300 - Separating network using vlan?

    I am wondering what the best way to separate a network, both data, on a cisco SG300. I do not want network 1 to able to communicate with network 2 or vice versa.  I have one server for DHCP for network 1, 192.168.1.X. I would like network 2 to have ip of 10.0.0.X, can the cisco SG300 do dhcp for this vlan?
    Thank you for your help,
    Brian

    Hello Brian, the SX300 series do not support any DHCP service, you will need a router or a DHCP box for this. The SX300 can separate traffic with VLAN. However, as the default layer 2, all request will go to your router then route to the destinations. As the switch in layer 3 mode, you may have local connectivity, however, if your router does not support the vlans or dot1q encapsulation, the router would require static routes for those subnets to be able to correctly route to the internet.
    -Tom
    Please rate helpful posts

  • Using Appliance Ports for NAS

    Using Appliance Ports for NAS
    Hey all connecting a NAS to UCS. Would like to plug in directly to FI’s using the Appliance Port option.
    Are the steps basically
    Turn on Ports use as Appliance Ports
    Make PIN Group through Appliance Ports (this will only be one port per FI, I am guess Port-Channels can be used if NAS supports that?)
    Make VLAN internal to UCS
    Make vNIC Template and use newly created VLAN and PIN Group
    Boom!
    Right?
    Thanks!
    Craig

    I have made port 20 on each 6120 an Appliance Ports.
    Each port is assigned to a VLAN made under the Appliances tab.
    Cannot seem to make a PIN group using these Appliance ports. They are not a option.
    Is there something I am missing?
    Thanks!
    Craig

  • Using ACS for VLAN assignment

    Hi Guys, I have been looking at the use of Cisco ACS server for VLAN assignment. So far I have searched through a number of threads and no found what I am looking for specifically so here it goes.
    1) When the RADIUS attributes have been configured in ACS (64, 65 + 81), and in my case I have them in the group configuration. For the VLANs to be assigned to the various users at their ports will every VLAN name in the RADIUS settings have to in the switches which are used for access?
    2) Is there a limit to the number of VLANs that can be assigned by the RADIUS(IETF) portion of ACS or would it be better to use RADIUS(IOS/PIX)? I am thinking of about 15 VLANS.
    I am using a Catalyst 4500 (IOS supervisor) and 2950s and 2970s at the closets.
    Thanks for any help...
    Kelvin

    Access Control Lists..I am thinking it is better to apply the ACLs at the closet (access) switches where I can specify the servers that should be reached by the hosts my test VLAN and deny those which they should not.
    I used a named extended ACL for my tests however, it did not go well. With the ACL below applied I cannot reach anything including the server I actually want to reach. My intention was to allow the hosts in the test VLAN 172.16.12.0/24 to reach 2 particular servers and their gateway however with the list applied I cannot reach anything at all. The setup is one 2950 connected to a 4507 the 2 VLANs I am working with are trunked to the 2950 and dhcp is running. I have IP routing enable on the 4507 and it is the server for the VTP domain.
    ip access-list extended guest
    permit ip 172.16.12.0 255.255.255.0 host 172.16.12.1
    permit ip 172.16.12.0 255.255.255.0 host 172.16.2.254
    permit udp 172.16.12.0 255.255.255.0 host 172.16.2.245 eq 53
    deny ip any any
    Any advice on how I can restrict the hosts which will be on this VLAN from accessing the rest of the network?

  • Control and management port for nm-cids

    Can any body help me to find the difference between the ip address that we use at the interface ids-sensore 1/0 and the ip address of the sensor and its default gateway
    10.10.10.2/24,10.10.10.1

    NM-CIDS information:
    There are 3 interfaces that you need to be aware of with the NM-CIDS.
    The NM-CIDS module has 2 interfaces (FastEthernet0/0 and FastEthernet0/1).
    The 3rd interface actually belongs to the router (IDS-sensor1/0)
    The Fa0/0 interface of the NM-CIDS is the external port of the NM-CIDS. When an IP Address is assigned to the NM-CIDS through the "setup" command, the IP is assigned to this Fa0/0 interface.
    The Fa0/0 interface is the external interface and so will need to be plugged into a hub (or switch), and the IP addresses assigned to it must be an address within the network address range for that network (vlan). The default gateway should be the same default gateway for the other boxes on that network, the default gateway may be one of the addresses of the router in which the NM-CIDS was installed, or could be a completely different router. The NM-CIDS Fa0/0 interface could have been plugged into a completely different network than any of the interfaces of it's parent router.
    Say for example that FastEthernet2/1 of the router is connected to vlan 10 on the switch and assigned an IP Address of 10.1.1.1. The Fa0/1 interface of the NM-CIDS is also plugged into the same switch on vlan 10. Because Fa0/1 of the NM-CIDS is plugged into the same network as Fa2/1 of the router, then both ip addresses can be in the same network and the router IP can be the gateway for the NM-CIDS. The Fa0/1 can have IP 10.1.1.30 with gateway 10.1.1.1 (Fa2/1 of the router).
    Alternatively the Fa0/1 of the NM-CIDS could have been plugged into vlan 30 (network 192.168.1.0) of the switch where the router does not have any of interfaces. In this case the Fa0/1 of the NM-CIDS won't be in the same network as any of the router interfaces. So the Fa0/1 of the NM-CIDS will need an IP address with that network: 192.168.1.27 for example. And the gateway for the NM-CIDS would need to be whatever OTHER router is the default gateway on that network: 192.168.1.1 for example.
    The Fa0/1 interface of the NM-CIDS is the internal interface of the NM-CIDS on the backplane of the router. The Analysis Engine should be configured to monitor this interface.
    The "IDS-Sensor1/0" interface is the router's backplane interface to the NM-CIDS, and has 2 functions.
    1) When the router is configured to send packets to the NM-CIDS for analysis the packts will be sent through the router's IDS-Sensor1/0 interface to the router backplane into the Fa0/1 interface of the NM-CIDS. You can almost think of IDS-Sensor1/0 and Fa0/1 as having a wire between (the wire being the router backplane).
    2) The IDS-Sensor1/0 also serves a second purpose. The IDS-Sensor1/0 ALSO connects to a special part of the NM-CIDS hardware that acts as a console port for the NM-CIDS. When you "session" to the NM-CIDS what is actually happening is a telnet through this IDS-Sensor1/0 interface into the backplane of the router to that special part of the NM-CIDS hardware. So when you session to the NM-CIDS it looks like a console port. It is because of this "telneting" as part of the session command that the router needs an address for the IDS-Sensor1/0 interface.
    The address assigned to the IDS-Sensor1/0 interface is never seen by the IPS software on the NM-CIDS, it is only used by the router inorder to support the session command. This IDS-Sensor1/0 address does not need to be routable so it can be an internal loopback address as seen in this example: http://www.cisco.com/univercd/cc/td/doc/product/iaabu/csids/csids12/cliguide/clinmcid.htm#wp1030678
    The loopback address is just a single address on a network that you are never going to use and never need to route packets to.
    This IP Address for IDS-Sensor1/0 should NOT be confused with the IP Address that was assigned to the Fa0/1 interface of the NM-CIDS.

  • Lync Client uses wrong RTP Ports for calls from/to RGS with Agent Anonymity

    We have QoS implemented and client ports for audio, video und application defined by Set-CsConferencingConfiguration. We also use firewalls in our LAN between the different VLANs for Clients, Servers and Gateways/SBC. Only RTP from the client with the defined
    ports are allowed by the firewall. Media ByPass is enabled.
    In all normal cases, the right ports will be used and marked by GPO with the right DSCP value. But if an agent get a call from a RGS which has agent anonymity enabled, the client uses a port in the range 1024-65535 for audio. Also if you make a call on behalf
    of the RGS, the client use a random port between 1024-65535. As soon, as the source of the call is in another VLAN (e.g. a call from PSTN which comes in over a SBC in e separate VLAN), the firewall between the two VLANs block the RTP traffic.
    We see the deny on the firewall log and in the SBC log we see, the reinvite for the media by pass with the IP of the agent and a not valid port. We also see, that no RTP from the client/agent will arrive the SBC and no RTP from the SBC will arrive the client/agent.
    So the call will be disconnected, as soon as an agent wants accept the call.
    Is there an additional setting to make sure, the Lync client always use the valid RTP port range?
    This behavior exist in Lync 2010 and Lync 2013 clients.

    Hi Holger,
    Thanks for reply!
    Sure! I set all AudioPorts on all Services, but the problem are not the ports used by the server, the problem are the ports used by the client. We set the client ports to 49152 with a count of 40. The client (2013 and also 2010) use these ports correctly in all
    cases exept for call from/on behalf of an RGS with Agent Anonymity.
    If we disable the RGS agent anonymity, restart the client of the agent, then the client uses also the correct source ports for RTP.
    I've checked this behaviour now on 3 customer installations, our own productive installation and in our lab.
    Because until now only one of our customers have firewalls between the internal VLANs, only this single customer have the issues...
    Regards,
    Stephan

  • Using separate ethernet ports for LAN and internet

    Following scenario:
    A couple of Lion clients and a Lion server connected to a switch. Switch connected to router for internet access. All devices, clients, server and router are in the same C-Class net.
    I'd like to connect the Lion server with 2 ethernet ports to the switch, so that one port is solely used for connections to the Lion clients (aka LAN) and the other port is solely used for connections to the internet. That way heavy LAN traffic to/from the server cannot bog down internet access to the server. Any ideas how to acomplish that?
    Usually you would configure the Lion server as a router and connect the Lion clients (via a switch) to one port and the cable modem to the other, so both ports are in different subnets. But I don't want all internet traffic from the clients going through the Lion server.
    The best I've come up so far was to configure both ethernet ports with static IP addresses. The one connecting to the clients with a 255.255.255.0 netmask but no router IP given. The one for internet with a 255.255.255.255 netmask and the router IP set to my physical router IP. It seems to work, but I'm not sure, whether this is the suggested way to do such a setup.
    Maybe some manual editing of the routing table is are more solid solution?
    Any tips appreciated.
    Pete

    What you want to do can be done but maybe not the way you are trying.
    First yes, you would use two Etherner ports on the Mac, if it is a Mac Pro or XServe it has two built-in, other Mac models can do this using a USB Ethernet interface.
    Next, the way I would normally do this is to have a separate switch for the WAN router, this would make the setup look like the following
    LAN Switch ----- Server ------------ Router --- Internet
           | |                             |
           | |                            NAT    
           | +-----------------------------+
           |
           +------ Client Devices
    The router could be doing NAT via one interface, or a separate Firewall box could do the NAT.
    Another possible way would involve segmenting the lan switch by setting up a VLAN and putting one port for the Servers second Ethernet connection on to that VLAN (using public IP addresses and the a connection to the router on that VLAN, the LAN switch could then route between the two VLANs. Cheaper LAN switches do not have this ability.

  • Trunk Port for 2950 and 2960G

    Hi Guys,
    I have tried connecting 2 switch using a trunk port in able for VLAN to run on 2950 switch, 2950 and 2960G, but the problem is, it keeps going up and down when I check the logs. The client experienced intermittent network connection by this problem. What seems to be the problem here? I already replaced the cables.
    Here is the config:
    They are connected via cross-cable
    2950:
    Int f0/24 --> 100mbps port
    switchport mode trunk
    2960G:
    Int G0/1 --> 1Gbps port
    switchport mode trunk
    *I believe they will auto negotiate their current speed and duplex.
    Thanks in advance.
    Cheers!

    Yes, they have the same settings.
    Here it is:
    int g0/2
    MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation ARPA, loopback not set
    Keepalive set (10 sec)
    Full-duplex, 100Mb/s, media type is 10/100/1000BaseTX
    input flow-control is off, output flow-control is unsupported
    ARP type: ARPA, ARP Timeout 04:00:00
    Last input 00:00:23, output 00:00:00, output hang never
    Last clearing of "show interface" counters 5d18h
    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 21000 bits/sec, 21 packets/sec
    5 minute output rate 495000 bits/sec, 180 packets/sec
    5180581 packets input, 1243581478 bytes, 0 no buffer
    Received 62493 broadcasts (0 multicast)
    0 runts, 0 giants, 0 throttles
    2 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
    0 watchdog, 30119 multicast, 0 pause input
    0 input packets with dribble condition detected
    179416978 packets output, 2694243274 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
    int f0/24
    MTU 1500 bytes, BW 100000 Kbit, DLY 1000 usec,
    reliability 255/255, txload 1/255, rxload 1/255
    Encapsulation ARPA, loopback not set
    Keepalive set (10 sec)
    Full-duplex, 100Mb/s, media type is 100BaseTX
    input flow-control is unsupported output flow-control is unsupported
    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 5d18h
    Input queue: 2/75/0/0 (size/max/drops/flushes); Total output drops: 0
    Queueing strategy: fifo
    Output queue: 0/40 (size/max)
    5 minute input rate 504000 bits/sec, 180 packets/sec
    5 minute output rate 22000 bits/sec, 22 packets/sec
    179389710 packets input, 2690183405 bytes, 0 no buffer
    Received 26481884 broadcasts (0 multicast)
    0 runts, 0 giants, 0 throttles
    4510 input errors, 3566 CRC, 243 frame, 0 overrun, 0 ignored
    0 watchdog, 17984825 multicast, 0 pause input
    0 input packets with dribble condition detected
    5180070 packets output, 1243477217 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

  • Span port destination vlan

    Hi All, I need to span a port for sniffer. Src port where server is located : gi 1/11(vlan 100) Dest port where sniffer pc is located: gi 1/25 My question is does the port gi1/25 needs to ve on a specific vlan? Can it be on the same vlan as source port I.r. vlan 100 ? Or should it be on any non-source vlan? thanks in advance

    Hi Thomas,
    Which model of switch are you enabling this span?
    Anyways you can have the destination port on any vlan depending on what interface you are monitoring. Only problem is that when you are monitoring a  VLAN rather than physical interface you need to be aware that "A destination port that belongs to a source VLAN of any SPAN session is excluded from the source list and is not monitored"
    Hope that helps.
    Regards
    Najaf

  • Does the SLM224G switch support port-based VLAN's?

    I am looking for a simple solution to create two LAN's. One for my own and one for my customers, who will be able to use desktop PC's with internet access. I have only one internet connection (DSL over ISDN) and wil not getting another just for my customers.
    My own network should not be accessible or visible to users who are using the customers-PC's. The other way around is allowed, but not really necessary. My setup requires me to hook up the switch to the (ISP) router, and that router just has one LAN port not able to do anything related to VLAN's.
    I read about port-based VLAN's here, where it is stated that creating seperate LAN's is just putting ports into VLAN's on the switch, nothing else needs to be done... However, they used a NetGear smart switch.
    I checked out Cisco's SLM224G as it is affordable, has 24 ports (instead of 8 for the NetGear) and should support VLAN's. I have read a lot about VLAN's, including:
    "- Port-based VLAN's means that you can reconfigure ports to be in different VLAN's. Port-based VLAN's do not confirm 802.1q VLAN support.
    - 802.1q VLAN's means that you can tag VLAN's with 802.1q headers to create a trunk between two devices that carries frames for multiple VLAN's. 802.1q VLAN's confirm that there is also Port-based VLAN support."
    I known from the spec sheets that the SLM224G supports 802.1q (tagged) trunking. So it should, given found text above, also support port-based VLAN's.
    My question is whether it indeed will support port-based VLAN's?
    Am I able to use it directly behind my ISP's router and create two seperate LAN's?
    If so, one extra question: how are the PC's behind the switch (inside the two VLAN's) get their IP-adresses from the ISP-router? Or will it service only one of the two LAN's and should I install a DHCP-server in the other LAN?
    Any information is very welcome!
    Thank you.

    Thanks for your responce, mr. Carr.
    I have read more about vlan's and their setup. I think the article about port based vlan's was lacking some information about the router/firewall. May be it was set up to work with different vlan's from the start. Strangely, in the text it is said that nothing needs to be set up besides the (Netgear) vlan-capable switch.
    So, from your response and other texts I learned I needed a vlan-capable router. I have to say that I need to be able to manage a server on the LAN from the outside (internet). I already tried to set up a Cisco/Linksys WRT54G router behind the ISP's (ZyXel) single LAN-ported router and that would not work at all (even when the Linksys was set in router-mode). I lost the connection to internet setting it up that way. I even tried to setup the Linksys in the DMZ of the ZyXel, with no luck. I was unable to set that up with working internet-access form the LAN. So I was not too happy with the suggestion to set up a (second) vlan-capable gigabit router behind the ISP's router....
    Eventually, I bridged the ZyXel to get rid of the double NAT/gateway mode of the two routers as routing mode did not work on the Linksys. The Linksys is now getting the WAN-ip from the ISP on it's WAN port and I furthermore used DD-WRT's firmware to enable the build-in vlan-capabilities of the Linksys.
    Now I have set up the Linksys with two vlan's and I bought the SLM224G as an inexpensive manageable 24-port vlan-capable switch to provide the number of ports I needed. I devided the SLM in two vlan's and used two wires from the Linksys to the SLM. So the SLM does support port-based vlan's by simply setting up two ranges of ports with different PVID settings. Trunking and 802.1q tagging isn't needed that way. I know I could have used two dumb switches to get two separate subnetted networks, but this way I get just enough ports in a single device where I have ample space to put it.
    Anyway, thanks for helping me understanding the way vlan-capable switches work.

  • 4500 Aggregate policers and Per-Port Per-VLAN QoS

    Hello,
    I want to limit the aggregate traffic of multiple VLANs on a trunk using an aggregate policer. I also need Per-Port Per-VLAN QoS for other VLANs on the same trunk.
    To cut a long story short, will the example config below work?
    qos aggregate-policer pol_aggr_10Mbit 10m 12.5k conform-action transmit exceed-action drop
    policy-map Aggr_10Mbit
    class class-default
    police aggregate pol_aggr_10Mbit
    policy-map Limit_10M
    class class-default
    police 10m 12.5k conform-action transmit exceed-action drop
    interface GigabitEthernetx/y
    switchport trunk encapsulation dot1q
    switchport mode trunk
    ! Aggregate 10Mbit VLANs
    vlan-range 208, 316, 909
    service-policy output Aggr_10Mbit
    ! 10 Mbit VLANs
    vlan range 20, 50-100
    service-policy output Limit_10M
    Regards, Jan

    Your config looks good . Actually Per-port per-VLAN QoS (PVQoS) offers differentiated quality-of-services to individual VLANs on a trunk port. It enables service providers to rate limit individual VLAN-based services on each trunk port to a business or a residence. In an enterprise Voice-over-IP environment, it can be used to rate limit voice VLAN even if an attacker impersonates an IP phone. A per-port per-VLAN service policy can be separately applied to either ingress or egress traffic.

  • I have a Mac OSX version 10.75 with just one Thunderbolt port. and it has been my Thunderbolt port to connect with Blackmagic wear my intensity. and I no longer can use the port for mini-DVI adapter to connect with me. I do not want to ask any other way f

    i have a Mac OSX version 10.75 with just one Thunderbolt port. and it has been my Thunderbolt port to connect with Blackmagic wear my intensity. and I no longer can use the port for mini-DVI adapter to connect with me. I do not want to ask any other way for me to use to use my monitor. I monitor LG FLATRON E2041 brand .. PLEASE Helpp ME

    i have a Mac OSX version 10.75 with just one Thunderbolt port. and it has been my Thunderbolt port to connect with Blackmagic wear my intensity. and I no longer can use the port for mini-DVI adapter to connect with me. I do not want to ask any other way for me to use to use my monitor. I monitor LG FLATRON E2041 brand .. PLEASE Helpp ME

Maybe you are looking for