802.1q VLAN tagging (more info)

From: Marco Greene (ML) (mweg_at_sympatico.ca)
Date: 11/30/05

  • Next message: PNathan: "Killing the zombie process"
    To: <crist.clark@globalstar.com>, "'List, Sun Managers'" <sunmanagers@sunmanagers.org>
    Date: Wed, 30 Nov 2005 06:59:58 -0500
    
    

    Here is some more info:

    1) For the other VLANs (at this point I am only talking about local traffic
    for each vlan) i.e. VLAN 247 is for 172.16.247.0/24. When I try to ping a
    host on that VLAN, the name resolves alright at the system level (hosts
    file). But then the arp requests go unanswered. I tried hosts that are on
    the same switch as well as hosts that are on different switches in order to
    ensure that it wasn't a trunking issue between the switches.

    2) Basically most of my tests were ping related...if I can not ping on the
    local subnet, I can not do anything else.

    3) It seems that on the switch it always defaulted to VLAN249 so either
    there is something wrong with the switch config or 802.1q isn't working
    properly on this server itself.

    4) I suppose I should have also mentioned the version of Solaris. Solaris
    8 64-bit on an E420R with lastest recommended patches as of June...and then
    a some security patches that have come out since.

    5) The Gig card on this server was originally a ge card which I replaced
    about 2 months ago with a ce card.

    Regards,
    Marco

    -----Original Message-----
    From: Crist Clark [mailto:crist.clark@globalstar.com]
    Sent: November 29, 2005 6:03 PM
    To: Marco Greene (ML)
    Subject: Re: 802.1q VLAN tagging

    Marco Greene (ML) wrote:
    > Hi all,
    >
    > I have a curious problem. I installed a CE card (ce1) and configured it
    to
    > use three different VLANs. 247,248,249. All of the 249 stuff seemed to
    > work; however, the communications to the other VLANs did not. ifconfig
    > reveals
    >
    > ce249001
    > ce248001
    > ce247001
    >
    > all configured with the proper IP addresses, gateways and subnet masks.

    Or so you think. If one VLAN worked and the others did not, it seems quite
    possible that it could be a routing issue. What do you mean by the others
    didn't work? What kind of tests did you do? Did you do any network captures?

    >>From a switch perspective...they are CISCO 3500 series switches (5 of
    them).
    > The trunk ports have been setup for 802.1q between the switches and the
    > ports for this sun server is also setup as a 802.1q trunk. I also have a
    > Windows box which also was setup for VLAN tagging and it seemed to work OK
    > across all three VLANs. So I am pretty sure that my switch configuration
    is
    > setup properly. (Not 100% sure but pretty sure).
    >
    > Because we were making the change to a production environment, I needed to
    > rollback the changes. I am going to try again in a few weeks but I would
    > like to armed with a little more information than the one pager that sun
    > provides with their documentation.
    >
    > Any thoughts and will summarize.

    My first thought is that you'll likely need to offer a lot more information
    to get some help on this. You should probably do some network captures
    to see what is actually going out on the wire. Also, looking at counters
    on the switch could help.

    --
    Crist J. Clark                               crist.clark@globalstar.com
    Globalstar Communications                                (408) 933-4387
    The information contained in this e-mail message is confidential,
    intended only for the use of the individual or entity named above.
    If the reader of this e-mail is not the intended recipient, or the
    employee or agent responsible to deliver it to the intended recipient,
    you are hereby notified that any review, dissemination, distribution or
    copying of this communication is strictly prohibited.  If you have
    received this e-mail in error, please contact postmaster@globalstar.com
    _______________________________________________
    sunmanagers mailing list
    sunmanagers@sunmanagers.org
    http://www.sunmanagers.org/mailman/listinfo/sunmanagers
    

  • Next message: PNathan: "Killing the zombie process"

    Relevant Pages

    • Re: Catalyst 3750 with 2 vlans. Only vlan1 drop packet when ping
      ... when I ping to the ip onvlan1, about 10% come back with "Request ... Are you pinging the hsrp vlan 1 address, ... ping vlan 140's interface with no problems? ... how does the other switch know how to get ...
      (comp.dcom.sys.cisco)
    • Re: Catalyst 3750 with 2 vlans. Only vlan1 drop packet when ping
      ... when I ping to the ip onvlan1, about 10% come back with "Request ... Are you pinging the hsrp vlan 1 address, ... ping vlan 140's interface with no problems? ... how does the other switch know how to get ...
      (comp.dcom.sys.cisco)
    • Re: Need guidance on Cisco 6513 install
      ... having this switch set up on Tuesday by noon, ... The switch itself (and other future network hardware) will be on the ... but you can always choose another vlan number and same ... In a two core environment, ...
      (comp.dcom.sys.cisco)
    • Re: bond interface arp, vlan and trunk / network question
      ... So far vlan and trunking works as expected. ... The exact problem is that the bonding driver don't switch the ... interface because the mii-tool don't recognize that the connection ... No, from your configuration information, you're running the ARP ...
      (Linux-Kernel)
    • Re: probably an easy routing question, so please help
      ... non-contiguous subnets into one VLAN and avoid having to run out to the ... router for intra-VLAN traffic, ... VLAN capable Layer 2 switches ignore VLAN tags on unicast traffic. ... A Layer 3 switch can route intraVLAN/interVLAN unicast traffic AS ...
      (comp.dcom.sys.cisco)