Switching

I am merging to segragated networks.

I am trying to setup vlans through our ex4200 and Procurve 2650. On the EX4200 I have Vlan 0, 99, 220(management), 600-700, on the Procurve I have vlan 1 and 221(management), 500-600.

I am just trying to get 99 active to do some testing. I can get connectivity if I set the interface on the EX as an access port and the vlan is 99. On the procurve side I have the port set as untagged on vlan 99.

If I try to set it as tagged 99 on the procurve and a trunk with vlan 99(no native) then it does not work.

Please post your config (Juniper and HP). Should work without problems. I have done so several times.

Regards,

Dominik

HP

; J4899B Configuration Editor; Created on release #H.08.83

hostname "access01"
ip default-gateway 10.70.220.1
vlan 1
   name "mgmt"
   untagged 1-49
   ip address 10.70.220.21 255.255.255.0
   tagged 50
   exit
vlan 99
   name "test"
   untagged 1
   ip address 192.168.99.2 255.255.255.0
   tagged 50
   exit
spanning-tree

Juniper

version 10.0S1.1;
system {
    host-name coresw01;
}
interfaces {
    ge-0/0/0 {
        description "DC Crossconnect";
        unit 0 {
            family ethernet-switching {
                port-mode trunk;
                vlan {
                    members [ test access01-default ];
                }
            }
    }
    vlan {
        unit 1 {
            family inet {
                address 10.70.220.6/24;
            }
        }
        unit 99 {
            family inet {
                address 192.168.99.1/24;
            }
}
}
routing-options {
    static {
        route 0.0.0.0/0 next-hop 10.70.128.1;
    }
}
protocols {
    rstp {
        interface ge-0/0/14.0 {
            mode point-to-point;
        }
        interface ge-1/0/14.0 {
            mode point-to-point;
        }
    }

ethernet-switching-options {
    secure-access-port {
        interface ge-0/0/14.0 {
            dhcp-trusted;
        }
        interface ge-1/0/14.0 {
            dhcp-trusted;
        }
    }

vlans {
    access01-default {
        vlan-id 1;
        l3-interface vlan.1;
    }
    test {
        vlan-id 99;
        l3-interface vlan.99;
    }

}
poe {
    interface all;

rstp status on both sides is forwarding.

Hi,

first I notice that on the HP side, it looks like your interface 1 belongs to both (VLAN 1 and VLAN 99) but is designated as untagged what is not possibly for obvious reasons. On the Juniper side, everything looks OK.

How did you try to test respectability of VLAN 99? Did you ping from ProCurve the Juniper IP address or have you attached a PC on the ProCurve device (provided that you reconfigured a port to belong to VLAN 99 in access mode)?

Regards,

Dominik

I ping from one switch to the other.

I add a device to an untagged port on vlan 99 on the procurve. I am able to ping the procurve but not the Juniper. So the trunk link isn't working.

Hi,

as mentioned, your trunk configuration looks fine. So I don't have a good idea what is failing. Although you said that all ports have spanning tree state forwarding, it might be worth to try it out to disable spanning tree completly and use just one connection between the two switches.

In addition, you could the monitor traffic interface statement to verify if packets are received on the interface.

Regards,

Dominik

You are right it's not with the configuration. This is going over metroethernet and I didn't know that would have been important. This is my first experience with metro and I thought it was going to use ethernet like standard ethernet would and allow vlan tagging. The isp needs to enable QinQ to have this work for us.