Subnets on single switch problem

Hi i recently completed a CCENT and am now moving onto to CCNA. I came across a network recently shown in the attachment that had a problem and i have a few questions and am trying to debug it. Any suggestions would be appreicated.
Device a sends info to device b every second over tcp/ip (few packets of info). If the link to Switch 1 is not connected the 192.168.1 network works fine and device a and device b function as normal.
When the link from switch 3 is plugged into switch 1 after approx 2 hours device b stops working as it does not receive infomation from device a.
This is repeatable plugging into switch 1 always causes an issue on device b.
All the switches are unmanaged switches.
The server needs to communicate with the 10.0.1.x and to the 192.168.1.x network but the other deices on the 10 network and 192 network do not have to communicate with each other. The server runs monitoring software and needs to "see" all devices. The server has one NIC with an alternate IP set up and can ping the devices on the 192,.168.1.x network and the 10.0.1.x network.
I was wondering is there a potential issue with the two subnets on the switch or is there possibly an issue with broadcast traffic?
The devices are not PC but industrial communication devices so im am unsure how to debug the issue.Also cannot view any logs on the switches as they are unmanaged.
One though i had was to put a cisco 3550 switch i have for testing in there and connect device a,device b on the cisco switch, then create a SPAN port and connect wireshark/dumcap to the SPAN port to monitor the traffic being sent between the two.
If anyone has any suggestions please let me know thanks

One characteristic that is generally true of unmanaged switches is that they have no concept of VLANs and that all of their ports are all in the same VLAN (same broadcast domain). So although you may have some devices configured as part of 192.168.1 network and other devices configured as part of 10.0.1 network the reality is that all of the devices are part of one big flat network.
If you put a Layer 3 switch into the network then you create the opportunity to actually separate these networks. You could configure vlan 10 and assign some ports on the layer 3 switch as access ports in vlan 10. If you connect switches 2 and 3 to ports that are access ports in vlan 10 then all the ports in switches 2 and 3 will be in vlan 10. You could configure vlan 20 on the layer 3 switch and make vlan 20 have subnet 10.0.1.
You could connect switch 4 to an access port in whatever vlan you choose. You suggest that it might go into vlan 10 which is certainly possible. But you then suggest setting the IP of the server as part of 10.0. But in the preceding paragraph you suggested that 10.0 would be associated with vlan 20. You need to be clear and consistent about the relationship between vlan and subnet.
If you associate 10.0 subnet with vlan 20 then any device in vlan 20 should have an IP address in 10.0. And all devices in the vlan and subnet would easily communicate with each other.
I am somewhat unclear about the server. At some places you seem to indicate that it needs to communicate with devices in network 10.0 and in some places it seems that it should communicate with 192. If it really needs to communicate with both then you will need some layer 3 device that allows routing between the subnets.
HTH
Rick

Similar Messages

  • Subnet config and switch layout for windows 2012 ISCSI server

    I would like to ask about subnet design and switch layout in regards to using a Windows 2012 ISCSI solution. When you guys design subnets for ISCSI configurations do you use one subnet or multiple subnets?  Also do you link the switches together when
    designing your ISCSI layouts? These types of things are normally discussed in vendor deployment guides.  However, I have not come across a best practices guide for deploying Server 2012 ISCSI.

    I would like to ask about subnet design and switch layout in regards to using a Windows 2012 ISCSI solution. When you guys design subnets for ISCSI configurations do you use one subnet or multiple subnets?  Also do you link the switches together
    when designing your ISCSI layouts? These types of things are normally discussed in vendor deployment guides.  However, I have not come across a best practices guide for deploying Server 2012 ISCSI.
    For iSCSI you typically create a separate subnets around physical NICs you use for iSCSI traffic (assuming they are used by iSCSI target for MPIO of course). Here are few guides on how to do that (some for Windows Server 2008 R2 but you can ignore that fact
    as target itself did not change much and concepts are still the same). See:
    Configure iSCSI MPIO on Windows (full)
    http://blogs.technet.com/b/migreene/archive/2009/08/29/3277914.aspx
    (make sure you have at leas one connection before you try to enable MPIO)
    Setting up a Target and Initiator
    http://www.server-log.com/blog/2011/7/26/setting-up-an-microsoft-iscsi-target-and-initiator-using-mpi.html
    You need however be aware of a couple of facts... 
    1) MSFT does not see much future in iSCSI and is replacing it with SMB3 where it can. So if you want to use iSCSI to provide shared storage to your guest VMs you need to use shared VHDX hosted on SMB3 share, see:
    Shared VHDX for guest VM Cluster
    http://technet.microsoft.com/en-us/library/dn265980.aspx
    If you plan to use iSCSI to host CSV and VM images there you again can use SMB3 share, see:
    Hyper-V over SMB
    http://technet.microsoft.com/en-us/library/jj134187.aspx
    That's both simpler to manage (you don't configure anything except teaming for NICs to enable SMB Multichannel and create a shared folder in a few clicks) and faster: MSFT iSCSI target is not cached @ server side while (OK, Hyper-V ovens VMs in a pass-thru
    mode but other users typically don't do that). SQL Server is the same as Hyper-V in terms of SMB3 support, Windows clusters support SMB3 share as a witness and so on.
    2) That's a single point of failure. Think about using SoFS instead of a single SMB3 share and think about clustering your target (you'll need a separate fault tolerant back end of that) to increase uptime. See:
    MSFT iSCSI Target Failover Cluster
    http://techontip.wordpress.com/2011/05/03/microsoft-iscsi-target-cluster-building-walkthrough/
    Good luck! :)
    StarWind VSAN [Virtual SAN] clusters Hyper-V without SAS, Fibre Channel, SMB 3.0 or iSCSI, uses Ethernet to mirror internally mounted SATA disks between hosts.

  • Dot1q trunk from single switch to multiple switches

    Hi,
    Hope you can help please !
    I have a single switch with 6 vlans and one trunk port at the main site  This has to connect to a 3 separate locations each with its own switch with a trunked port via a microwave network.
    I have run it in packet tracer using a hub as the microwave network.  It works fine in that, I just want to check it would 'actually' work or could it cause problems ?
    Diagram from PT below with 3 vlans just for clarification.

    First of all   'This is not a school related work' Leo Laohoo. There is no conspiracy here, calm yourself down.  
    We are loosing quite a few E1 circuits and they are being replaced with only a few ethernet, so we need to conserve them.
    It is indeed a L2 network.  The VLANs don't need to communicate with each other and will terminate into a firewall.  I used the PC's on the left as an interface just.
    I was concerned about having one trunk port connect to 3 other switches.  I wasn't sure how they would react as I've ever only used trunks point to point.  
    Hence why I used the hub in PT to break a single trunk into 3.  I just wasn't sure how the switches would react to this.
     Thanks !
    Mark

  • Single Switch for multiple clusters

    We currently have multiple independent RAC clusters, each with a low cost switch for the interconnect.
    For example server1 and server2 is the development RAC. Server3 and server4 are the test RAC
    and server5 and server6 are the production rac.
    Can a single 24 port switch handle the interconnect traffic for these 3 separate RACs?
    We will have a second switch for redundancy, but can the single switch handle the traffic for
    3 separate RAC clusters?
    Sincerely
    Dan Clark

    Can a single 24 port switch handle the interconnect traffic for these 3 separate RACs?That depends on the number of nodes in each cluster, and the redundancy of the Interconnect.
    If you are running a single cable from the HCA on the node into the switch, your switch can support 24 nodes in total. If you are running dual connections, then only 12.
    Performance.. well, I doubt that it will be a problem as a 24 port switch is designed to handle 24 connections. As the Interconnect needs to be fast, this switch is not a normal switch, but one that supports higher speeds and bigger pipes like Gig ethernet or Infiniband for example.
    On the latter you can use Sockets Direct Protocol (SDP) or SCSI RDMA Protocol (SRP) - which is significantly faster than UDP (which is considered the faster protocol itself in the IP suite).
    In your shoes, my biggest concern would be redundancy. If that switch fails for whatever reason, 3 clusters are down. And that is IMO unacceptable. I would instead consider either a more expensive switch with inbuilt redundancy (dual CPUs, PSUs, etc), or look at using 2 switches (which is a saving of 1 switch for 3 clusters).
    Remember that RAC is only as good as the h/w architecture. If that is not adequate ito redundancy (or performance), it is clearly going to be shown by RAC itself.

  • How do I set up multiple VLANs on a single switch?

    I have two 3750G-24PS switches and three Huawei S2300 switches. I have configured VLANs (15 nos.) in 3750. Is it possible for me to use those three switches for all VLANs or do I have to use separate switches for each VLAN?

    Got this answer.
    You can have as many as 1024 VLANs on a single switch and you need not create the same on Huawei S2300  switches. Create a VTP domain and specify one switch as server and others as transparent. All the VLANs created on server switch will get replicated to other switches.

  • Multiple PWWN on single switch port

    Hi,
    I wanted to know, how its possible to have multiple PWWN on single switch port..??
    Whats the concept behind it..
    Thanks
    Rajeev.

    Hi Rajeev,
    The concepts that you are looking for is N Port virtualization (NPV) and N-Port ID Virtualization (NPIV).
    Fuurther details can be found via the following Cisco White paper
    http://www.cisco.com/en/US/prod/collateral/ps4159/ps6409/ps5989/ps9898/white_paper_c11-459263.html
    Hope that helps.
    Regards,
    Michael

  • Device Switch problem from Z10 to Z30

    Device Switch problem from Z10 to Z30
    Hi Dears,
    I got my new Z30 and I tried to switch my old Z10 without luck, so I appreciate your help.
    Both devices are identical OS Release (10.2.1.2102) version (10.2.1.2141)
    I set up my Blackberry ID in the new Z30
    I used BB-Link via my PC and everything started fine and smooth, and I followed all instructions step by step.
    Until reaching to step (8 of 9 ) in the BB-Link, a popup windows appear in my Z30 saying “RESTORE IN PROGRESS”
    But after 5 seconds, BB-Link cancel the restore process !!!
    Also, I tried to connect my Z30 to my PC and restore previous Z10 backup directly through BB-Link, but same issue and message “the operation was cancelled”
    One more thing, I noticed that, the BBM is empty and showing message “restoring your BBM information” since yesterday.
    I wiped my device and try several time but no luck L,
    Please I need your help 

    Is the new Z30 upgraded with the latest BBM version 10.3?
    If not, upgrade that first through App World, then try the Switch Device or restore again.
    1. If any post helps you please click the below the post(s) that helped you.
    2. Please resolve your thread by marking the post "Solution?" which solved it for you!
    3. Install free BlackBerry Protect today for backups of contacts and data.
    4. Guide to Unlocking your BlackBerry & Unlock Codes
    Join our BBM Channels (Beta)
    BlackBerry Support Forums Channel
    PIN: C0001B7B4   Display/Scan Bar Code
    Knowledge Base Updates
    PIN: C0005A9AA   Display/Scan Bar Code

  • 2 different subnets on single vlan

    I have this setup.
    2 3750G switches stacked.
    I have 2 servers with IP 10.10.10.1/30 and 10.10.10.2/30 connected into port g1/0/1 and g1/0/2 respectivily on switch1 both in vlan 100
    I have another 2 servers with IP 10.10.20.1/30 and 10.10.20.2/30 connected into port g2/0/1 and g2/0/2 respectivily on switch2 both also in vlan 100.
    I need to keep this same vlan across the stack. In theory servers on same subnet in vlan 100 should be able to communicate properly, or am I wrong?
    What can I do to prevent broadcasts from propagating between subnets of this single vlan?

    Edison
    Perhaps I read the post from Sparky slightly differently than you do. The first pair of servers are in the same logical subnet and in the same VLAN so they should communicate with each other fine. And the second pair of servers are in the same logical subnet and in the same VLAN so they should communicate with each other fine.
    But I agree with you that there are flaws in this implementation. First, since the subnets are /30 they only allow two hosts and with two servers in the subnet there is nothing to act as a gateway and to provide access to "remote" addresses. Also this implementation breaks the assumption that there is a correlation between subnet and VLAN. We tend to assume that a correlation exists and that a subnet is related to a VLAN and a VLAN is related to a subnet. But VLAN is a layer 2 concept and subnet is a layer 3 concept and they are not necessarily related. There is no rule that says that a VLAN have only 1 subnet (though that is common practice). A VLAN interface with a primary IP address and a secondary IP address would certainly support 2 (or more) subnets.
    Note that this implementation does not provide the isolation that we tend to assume when we talk about subnets. We generally assume that devices in 1 subnet do not communicate directly with devices in a different subnet (because we tend to assume that each subnet is a separate broadcast domain). But this implementation puts both subnets into the same broadcast domain. So the first pair of servers will hear all the broadcasts (including ARP) from the second pair of servers and any of these servers could communicate directly with any other of the servers - certainly not bounded by the subnet.
    Sparky
    There is no way to isolate the broadcasts within the same VLAN. The basic definition of VLAN is that it is a broadcast domain. And any broadcast generated will be flooded thoughout the entire broadcast domain. The only way to restrict the broadcasts is to create 2 VLANs.
    HTH
    Rick

  • ACS - Replace IP Subnet with Single IP's

    Hi Everyone,
    I have been charged with a task to create individual entries in our ACS for each of our network devices. I am new to the ACS and the documentation does not seem to cover this scenario. Right now we have all our devices fall under a single subnet.
    When I try to create a device within the subnet, it tells me IP subnets overlap with those defined for device.
    If I try to change the existing IP Subnet to an IP range so I can exclude some devices from the IP Subnet, it tells me I cannot switch from IP Mask mode to IP Range mode.
    I am guessing I need to delete the the record for the IP subnet and add each device back individually. My concern is that none of my devices will work until I add each one back.
    Is this correct or is there a better way to go about this?
    Thanks,
    DC

    You can configure the default network device with the same settings ad your subnet, remove the subnet definition and re-add the hosts one by one. You can also use file import to reduce time.
    Sent from Cisco Technical Support Android App

  • NM-16ESW switching problem !!!

    Hi,
    We have a problem using an NM-16ESW in a 2811 routeur. Actually this network module works perfectly in routing mode (no switchport on the interfaces) but we are not able to use it in switching mode; Our configuration is very simple: We have configured vlan 100 in vlan database, we have configured interface vlan 100 and set an ip address to this interface vlan 100, then we have put the interface Fa1/0 (first int of the NM-16ESW) in vlan 100 (switchport mode acces, switchport access vlan 100). But there is nothing to do and we are still unable to ping (of course we've checked that interfaces are up)!!! Thanks for your help because this problem is going to drive us crazy !
    Regards,
    Adrien
    Pau, FRANCE

    Hi !
    Thanks for your response. We entered the same commands as you to create vlan and to configure interface vlan.
    As requested, here is output of "sh run" command related to the NM-16ESW configuration. As you can see configuration is very simple.
    interface FastEthernet0/0
    no ip address
    shutdown
    duplex auto
    speed auto
    interface FastEthernet0/1
    no ip address
    duplex auto
    speed auto
    interface FastEthernet0/0/0
    switchport access vlan 100
    interface FastEthernet0/0/1
    switchport access vlan 100
    interface FastEthernet0/0/2
    interface FastEthernet0/0/3
    interface FastEthernet1/0
    switchport access vlan 100
    interface FastEthernet1/1
    description *** Sectorielle 1 ***
    switchport access vlan 100
    interface FastEthernet1/2
    description *** Sectorielle 2 ***
    switchport access vlan 100
    interface FastEthernet1/3
    description *** Sectorielle 3 ***
    switchport access vlan 100
    interface FastEthernet1/4
    description *** Sectorielle 4 ***
    switchport access vlan 100
    interface FastEthernet1/5
    interface FastEthernet1/6
    interface FastEthernet1/7
    interface FastEthernet1/8
    interface FastEthernet1/9
    interface FastEthernet1/10
    interface FastEthernet1/11
    interface FastEthernet1/12
    interface FastEthernet1/13
    interface FastEthernet1/14
    interface FastEthernet1/15
    interface Vlan1
    no ip address
    shutdown
    interface Vlan100
    ip address 192.168.38.252 255.255.255.0
    standby 100 ip 192.168.38.254
    standby 100 priority 110
    standby 100 preempt
    Here is output of show command in the vlan database... as you can see we are able to see VLAN 100 which has been created with "vlan 100" command in vlan database mode.
    Router(vlan)#sh
    VLAN ISL Id: 1
    Name: default
    Media Type: Ethernet
    VLAN 802.10 Id: 100001
    State: Operational
    MTU: 1500
    Translational Bridged VLAN: 1002
    Translational Bridged VLAN: 1003
    VLAN ISL Id: 100
    Name: VLAN0100
    Media Type: Ethernet
    VLAN 802.10 Id: 100100
    State: Operational
    MTU: 1500
    It seems to be very simple but unable to ping anything. We tried to connect a pc, a routeur on interfaces within vlan 100 (Fa1/0 - 4), configured of course with an ip address within the subnet 192.168.38.0/24, but it doesn't work-> impossible to ping. Worst; when we connect a router we are able to see it with sh cdp nei command (but ping doesn't work)!
    Thanks for your help.

  • DVI to VGA via Belkin SOHO Switch Problems

    Hi, I've searched and emailed Belkin support and no luck.
    I am using DVI out through a DVI -> VGA adapter (tried Apple® branded and non) then through the company supplied Belkin SOHO VGA KVM switch.
    My MBP detects the external display fine, but no video is displayed.
    Other monitors/projectors without the Belkin switch are fine using the DVI->VGA adaptor. And I've used the DVI straight out for years without a problem.
    Belkin's tech support couldn't figure it out and just recommended that I buy a DVI KVM switch. Nice.
    Anyone?
    Thanks in advance!

    My MBP detects the external display fine, but no video is displayed.
    What kind of display is it?
    Other monitors/projectors without the Belkin switch are fine using the DVI->VGA adaptor.
    Other monitors? What about the one connected to the Belkin switch? Does it work fine when driven directly without the Belkin switch?

  • XML invalid character -  a single quote problem

    Hi, I am reading in an xml file, then write the file to output. The problem is that the input file has a strange single quote character [ *�*  ] - lets call it single quoate A, which is different from [  *'*  ] , that is the key next to the [ ; ] key on an English keyboard - lets call it single quate B. And in fact there isnt a key to input single quote A, I guess the appearance of single quote A is due to encoding.
    If I open the input xml file in browser, it works ok and displays the single quote A.
    Once I read in the xml file into memory, by debugging I can still see that single quote A is corrected encoded;
    However once I rewrite the same content to output, the single quote A character is changed, and if i open the file in browser, it says 'invalid character' because single quote A were changed when written to output and cannot be rendered.
    Both input and output xml are using UTF-8 encoding. How can I solve this problem please?
    The xml file looks:
    <?xml version="1.0" encoding="UTF-8" ?>
    <content>....1980�s (Peacock and Williams, 1986; Keay, 1984)</content> My code for reading
    String _xquery ="//content/text()";
    Document _xmlDoc= DocumentBuilderFactory.newInstance().newDocumentBuilder().parse("myxml.xml");
    XPath _xpath = XPathFactory.newInstance().newXPath();
    NodeList nodes = (NodeList) _xpath.compile(query).evaluate(_xmlDoc, XPathConstants.NODESET);
    List<String> res = new ArrayList<String>(nodes.getLength());
    for (int i = 0; i < nodes.getLength(); i++) {
        res.add(nodes.item(i).getNodeValue());
    String valueToOuput=res.toString() //this is the value to be output to xml, it shoud look like "[....1980�s (Peacock and Williams, 1986; Keay, 1984)]"my code for writing xml
    Element root=new Element("root");;
    Element content= new Element("output-content")
    content.setText(valueToOutput);
    root.addContent(content);
    PrintWriter writer = new PrintWriter(new FileWriter(f));
    new XMLOutputter().output(domDocument, writer);
    writer.close();

    Hi, sorry I have fixed the problem... instead of using PrintWriter, I used Fileoutputstream, and it solved the problem. Thanks!

  • Mssql single quote problem!

    Hi,
    I user servlet to update MS SQL2000. My problem is there is a single quote inside a text string!
    I can't use double quote for string, as it is not a valid statement for MSSQL. I need to use single quote, but there is single quote inside the string, how can I handle the string?
    String mstrnig="I'm a boy";
    String mSQL = "UPDATE news SET " + "title='" + mstring + "' WHERE code =" + mcode;
    Thanks

    the cleanest and easiest soln is to use preparedStatement.
    PreparedStatement ps = con.prepareStatement("update table comment=? where id = ?");
    ps.setString(1,"That's way to do it");
    ps.setInt(1,8);//some itn value
    ps.execute();

  • SG-300 28P switches problem with VLAN Data and Voice, working all the time as Voice VLAN

    Hi Everyone,
    Thank you very much for your help in advance. I’m pulling my hair to fix the problem.
    I  just got the new SG-300 28P switches. My Bios ordered for me. I did not  know how it runs until now... not an IOS based. I really do not know  how to configure it.
    I have 2 VLAN are Data and Voice.
    -          Data VLAN ID is 2 IP 192.168.2.X/255.255.255.0
    -          Voice VLAN ID is 200 IP 192.168.22.X/255.255.255.0
    -          I created two vlans, in switch, Data and Voice.
    -          On the port number 28, it is trunk by default, so I add Data vlan ID 2 tagged.
    -          On the port number 26, it is trunk by default, so I add Voice vlan ID 200 tagged.
    -          On the port number 27, I add Data vlan ID 2 tagged for Data vlan out.
    -          Port settings No.1
    I set it up as Trunk with Data vlan 2 untagged, and  200  Tagged (voice vlan). I plugged in a phone with a pc attached. But the  PC will get to the vlan 200 to get the DHCP address, but no from vlan 2.  The Phone works with correct vlan ip.
    -          Port settings No.2
    Trunk with vlan 1UP, 2T, and 200T. The phone is even worse. Would never pick up any IP from DHCP.
    -          Port settings No.3
    Access  with 200U...of course the phone will work... and the PC could not get  to its own vlan. Instead, the PC got an ip from the voice vlan. Not from  VLAN 2.
    I have Linksys phone I’m not sure if this help.
    For more information I setup in switch,
                - enable voice vlan
    - set the port on auto voice vlan
    - enable LLDP-MED globally
    - create a network policy to assign VLAN 200
    - assign this network policy to the port the phone is connected to.
    I  hope this information help to help me to setup Data and Voice vlans, to  plug the phone to work with vlan Voice 200 (IP rang 192.168.22.X), from  phone to Pc and pc work as Data vlan 2 (IP rang 192.168.2.X).

    I just got done setting up voice VLANs on an SF 300-24P and verified working.  This was working with Cisco 7900 series phones connected to a Cisco UC setup.
    Here's my sample config.
    Note that I edited this by hand before posting, so doing a flat out tftp restore probably won't work.  However, this should give you a clue.  Also, don't take this as 100% accurate or correct.  I've only been working with these things for about a week, though I've worked with the older Linksys SRW switches for a couple of years.  I'm a CCNP/CCDP.
    VLAN 199 is my management VLAN and is the native VLAN on 802.1q trunks.
    VLAN 149 is the data/computer VLAN here.
    VLAN 111 is the voice/phone VLAN here.
    VLAN 107 does nothing.
    interface range ethernet e(1-24)
    port storm-control broadcast enable
    exit
    interface ethernet e1
    port storm-control include-multicast
    exit
    interface ethernet e2
    port storm-control include-multicast
    exit
    interface ethernet e3
    port storm-control include-multicast
    exit
    interface ethernet e4
    port storm-control include-multicast
    exit
    interface ethernet e5
    port storm-control include-multicast
    exit
    interface ethernet e6
    port storm-control include-multicast
    exit
    interface ethernet e7
    port storm-control include-multicast
    exit
    interface ethernet e8
    port storm-control include-multicast
    exit
    interface ethernet e9
    port storm-control include-multicast
    exit
    interface ethernet e10
    port storm-control include-multicast
    exit
    interface ethernet e11
    port storm-control include-multicast
    exit
    interface ethernet e12
    port storm-control include-multicast
    exit
    interface ethernet e13
    port storm-control include-multicast
    exit
    interface ethernet e14
    port storm-control include-multicast
    exit
    interface ethernet e15
    port storm-control include-multicast
    exit
    interface ethernet e16
    port storm-control include-multicast
    exit
    interface ethernet e17
    port storm-control include-multicast
    exit
    interface ethernet e18
    port storm-control include-multicast
    exit
    interface ethernet e19
    port storm-control include-multicast
    exit
    interface ethernet e20
    port storm-control include-multicast
    exit
    interface ethernet e21
    port storm-control include-multicast
    exit
    interface ethernet e22
    port storm-control include-multicast
    exit
    interface ethernet e23
    port storm-control include-multicast
    exit
    interface ethernet e24
    port storm-control include-multicast
    exit
    interface range ethernet g(1-4)
    description "Uplink trunk"
    exit
    interface range ethernet g(1-4)
    switchport default-vlan tagged
    exit
    interface range ethernet e(21-24)
    switchport mode access
    exit
    vlan database
    vlan 107,111,149,199
    exit
    interface range ethernet g(1-4)
    switchport trunk allowed vlan add 107
    exit
    interface range ethernet e(21-24)
    switchport access vlan 111
    exit
    interface range ethernet g(1-4)
    switchport trunk allowed vlan add 111
    exit
    interface range ethernet e(1-20)
    switchport trunk native vlan 149
    exit
    interface range ethernet g(1-4)
    switchport trunk allowed vlan add 149
    exit
    interface range ethernet g(1-4)
    switchport trunk native vlan 199
    exit
    voice vlan aging-timeout 5
    voice vlan oui-table add 0001e3 Siemens_AG_phone________
    voice vlan oui-table add 00036b Cisco_phone_____________
    voice vlan oui-table add 00096e Avaya___________________
    voice vlan oui-table add 000fe2 H3C_Aolynk______________
    voice vlan oui-table add 0060b9 Philips_and_NEC_AG_phone
    voice vlan oui-table add 00d01e Pingtel_phone___________
    voice vlan oui-table add 00e075 Polycom/Veritel_phone___
    voice vlan oui-table add 00e0bb 3Com_phone______________
    voice vlan oui-table add 108ccf MyCiscoIPPhones1
    voice vlan oui-table add 40f4ec MyCiscoIPPhones2
    voice vlan oui-table add 8cb64f MyCiscoIPPhones3
    voice vlan id 111
    voice vlan cos 6 remark
    interface ethernet e1
    voice vlan enable
    exit
    interface ethernet e1
    voice vlan cos mode all
    exit
    interface ethernet e2
    voice vlan enable
    exit
    interface ethernet e2
    voice vlan cos mode all
    exit
    interface ethernet e3
    voice vlan enable
    exit
    interface ethernet e3
    voice vlan cos mode all
    exit
    interface ethernet e4
    voice vlan enable
    exit
    interface ethernet e4
    voice vlan cos mode all
    exit
    interface ethernet e5
    voice vlan enable
    exit
    interface ethernet e5
    voice vlan cos mode all
    exit
    interface ethernet e6
    voice vlan enable
    exit
    interface ethernet e6
    voice vlan cos mode all
    exit
    interface ethernet e7
    voice vlan enable
    exit
    interface ethernet e7
    voice vlan cos mode all
    exit
    interface ethernet e8
    voice vlan enable
    exit
    interface ethernet e8
    voice vlan cos mode all
    exit
    interface ethernet e9
    voice vlan enable
    exit
    interface ethernet e9
    voice vlan cos mode all
    exit
    interface ethernet e10
    voice vlan enable
    exit
    interface ethernet e10
    voice vlan cos mode all
    exit
    interface ethernet e11
    voice vlan enable
    exit
    interface ethernet e11
    voice vlan cos mode all
    exit
    interface ethernet e12
    voice vlan enable
    exit
    interface ethernet e12
    voice vlan cos mode all
    exit
    interface ethernet e13
    voice vlan enable
    exit
    interface ethernet e13
    voice vlan cos mode all
    exit
    interface ethernet e14
    voice vlan enable
    exit
    interface ethernet e14
    voice vlan cos mode all
    exit
    interface ethernet e15
    voice vlan enable
    exit
    interface ethernet e15
    voice vlan cos mode all
    exit
    interface ethernet e16
    voice vlan enable
    exit
    interface ethernet e16
    voice vlan cos mode all
    exit
    interface ethernet e17
    voice vlan enable
    exit
    interface ethernet e17
    voice vlan cos mode all
    exit
    interface ethernet e18
    voice vlan enable
    exit
    interface ethernet e18
    voice vlan cos mode all
    exit
    interface ethernet e19
    voice vlan enable
    exit
    interface ethernet e19
    voice vlan cos mode all
    exit
    interface ethernet e20
    voice vlan enable
    exit
    interface ethernet e20
    voice vlan cos mode all
    exit
    interface ethernet e1
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e2
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e3
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e4
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e5
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e6
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e7
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e8
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e9
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e10
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e11
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e12
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e13
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e14
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e15
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e16
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e17
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e18
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e19
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e20
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e21
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e22
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e23
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e24
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g1
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g2
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g3
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet g4
    lldp optional-tlv port-desc sys-name sys-desc sys-cap 802.3-mac-phy 802.3-lag 802.3-max-frame-size
    exit
    interface ethernet e1
    lldp med notifications topology-change enable
    exit
    interface ethernet e2
    lldp med notifications topology-change enable
    exit
    interface ethernet e3
    lldp med notifications topology-change enable
    exit
    interface ethernet e4
    lldp med notifications topology-change enable
    exit
    interface ethernet e5
    lldp med notifications topology-change enable
    exit
    interface ethernet e6
    lldp med notifications topology-change enable
    exit
    interface ethernet e7
    lldp med notifications topology-change enable
    exit
    interface ethernet e8
    lldp med notifications topology-change enable
    exit
    interface ethernet e9
    lldp med notifications topology-change enable
    exit
    interface ethernet e10
    lldp med notifications topology-change enable
    exit
    interface ethernet e11
    lldp med notifications topology-change enable
    exit
    interface ethernet e12
    lldp med notifications topology-change enable
    exit
    interface ethernet e13
    lldp med notifications topology-change enable
    exit
    interface ethernet e14
    lldp med notifications topology-change enable
    exit
    interface ethernet e15
    lldp med notifications topology-change enable
    exit
    interface ethernet e16
    lldp med notifications topology-change enable
    exit
    interface ethernet e17
    lldp med notifications topology-change enable
    exit
    interface ethernet e18
    lldp med notifications topology-change enable
    exit
    interface ethernet e19
    lldp med notifications topology-change enable
    exit
    interface ethernet e20
    lldp med notifications topology-change enable
    exit
    interface ethernet e21
    lldp med notifications topology-change enable
    exit
    interface ethernet e22
    lldp med notifications topology-change enable
    exit
    interface ethernet e1
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e2
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e3
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e4
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e5
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e6
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e7
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e8
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e9
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e10
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e11
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e12
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e13
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e14
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e15
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e16
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e17
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e18
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e19
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e20
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e21
    lldp med enable network-policy poe-pse
    exit
    interface ethernet e22
    lldp med enable network-policy poe-pse
    exit
    lldp med network-policy 1 voice vlan 111 vlan-type tagged
    interface range ethernet e(1-22)
    lldp med network-policy add 1
    exit
    interface vlan 199
    ip address 199.16.30.77 255.255.255.0
    exit
    ip default-gateway 199.16.30.3
    interface vlan 1
    no ip address dhcp
    exit
    no bonjour enable
    bonjour service enable csco-sb
    bonjour service enable http  
    bonjour service enable https 
    bonjour service enable ssh   
    bonjour service enable telnet
    hostname psw1
    line console
    exec-timeout 30
    exit
    line ssh
    exec-timeout 30
    exit
    line telnet
    exec-timeout 30
    exit
    management access-list Management1
    permit ip-source 10.22.5.5 mask 255.255.255.0
    exit
    logging 199.16.31.33 severity debugging description mysysloghost
    aaa authentication enable Console local
    aaa authentication enable SSH tacacs local
    aaa authentication enable Telnet local
    ip http authentication tacacs local
    ip https authentication tacacs local
    aaa authentication login Console local
    aaa authentication login SSH tacacs local
    aaa authentication login Telnet local
    line telnet
    login authentication Telnet
    enable authentication Telnet
    password admin
    exit
    line ssh
    login authentication SSH
    enable authentication SSH
    password admin
    exit
    line console
    login authentication Console
    enable authentication Console
    password admin
    exit
    username admin password admin level 15
    power inline usage-threshold 90
    power inline traps enable
    ip ssh server
    snmp-server location in-the-closet
    snmp-server contact [email protected]
    ip http exec-timeout 30
    ip https server
    ip https exec-timeout 30
    tacacs-server host 1.2.3.4 key spaceballz  timeout 3  priority 10
    clock timezone -7
    clock source sntp
    sntp unicast client enable
    sntp unicast client poll
    sntp server 199.16.30.1
    sntp server 199.16.30.2
    ip domain-name mydomain.com
    ip name-server  199.16.5.12 199.16.5.13
    ip telnet server

  • MSI has a serious KVM switch problem.

    On the K8N the iogear USB KVM switches DO NOT WORK. I have two computers.. one with an asus board and one with an MSI. Works fine on the asus board. I did a search and noticed another guy was having the same problems. So its a error that MSI needs to fix. Have they fixed it yet? If not it really needs to be looked into.

    Quote
    Originally posted by suaZman
    Quote
    Originally posted by Sharkbait
    I should mention that the Linkskey 2-Port Slim Desktop KVM Switch is a PS2 KVM, not USB.
    Sharkbait
    Well the PS/2 type Iogear works fine. It is just the USB version that does not with this board. That sux because I need the USB version so it will recognize my MX 500 mouse. If you place an adaptor on the PS/2 version it just sees it as a standard mouse thus not enabling the other buttons.
    The belkin USB 2 port KVM works fine but the damn thing has no hot key switching and it is slow.
    Could you not use a USB > PS2 adapter for your mouse and run your mouse off PS2 and use a PS2 KVM? I use a MX700 mouse on the PS2 port and with mouseware installed, all my extra (5) buttons work fine

Maybe you are looking for

  • Imported ical from outlook and the date across the top of the weekly view all show the date i imported..

    imported ical from outlook and the date across the top of the weekly view all show the date i imported..

  • Problem with new line

    Hi, I'm trying to write a note for a contact.I have written following code contact.addString(Contact.NOTE, contact.ATTR_NONE, "bla bla bla");it works, but when i write contact.addString(Contact.NOTE, contact.ATTR_NONE, "bla \n bla \n bla");it doesn't

  • Wiping hard drive clean

    I'm preparing to sell my iBook G3 and would like to find out how to clean everything on my hard drive, or at least have the computer the way it was when I received it from the factory. Any suggestions????

  • Apple TV icon in AirPlay

    I have an iPad2 and just purchased the tv2. I got the audio working, but I can't get the video to work. When i select the "Apple TV" in air play, there is a speaker icon in front of it instead of the TV icon. How do I get it to have theTV icon? Than

  • MIRO PO Reference Delivery Note

    Dear Gurus, we have a problem with PO Reference using Delivery Note when there are multiple PO with the same Delivery note on 1 vendor, for some reason SAP taking the old PO(finished PO) as reference the problem is the old PO having old Payment term