Comware

 View Only
Expand all | Collapse all

5406zl vlan Routing

This thread has been viewed 0 times
  • 1.  5406zl vlan Routing

    Posted Apr 20, 2010 08:16 AM
    Hello and welcome to HP ressources,i am new here cause i always administrates procurve since a half a year.
    Before two weeks i install two parallel networks,which should be at first divided by hardware,so different subnet,and different procurves,uplinks and panels,lwl,and its own 5406zl switch,Every Firm has its own vlan,router, and ip ranges on the 5406.
    Now the chiefs whishes to cross the two 5406 to avoid that local traffic between this vlans goes across the wan,so if someone from firm ZOLL wants to administrate a client from firm B it should goes directly across the core switches and than maybe to the access area.
    We make a link(rj45 1000mbit) from 5406 to the other,giving both coreswitches an adress from the other vlan,tagged this port for the vlan and there is a connect.
    the core switches directly communicate without using there gateways but every other pc,and access switch uses his gateway and so the wan traffic.
    to my opinion there muzst be a special routing command to the cores or better on the routers to avoid that traffic between the firms go across the gateway and wan.
    Maybe someone knows what do i have to configure on the cores or routers.
    Core Firm A Vlan50 10.178.50.50 255.255.254.0
    gateway 10.178.50.1
    Core Firm B Vlan176 10.180.176.111
    255.255.248.0
    Gateway 10.180.176.1
    Every core either has another vlan and address from the other subnet ,port b2 from every core is tagged on both vlans.
    sh ip routing says that there is a connect,but the traffic goes over the gateways and on the wan and takes to long to arrive at the end.100ms and so.
    Thanks for your help Peter
    Firm B Vlan 176


  • 2.  RE: 5406zl vlan Routing

    Posted Apr 20, 2010 03:28 PM
    Paste your config from both


  • 3.  RE: 5406zl vlan Routing

    Posted Apr 21, 2010 12:19 AM
    Core 1

    ip default-gateway 10.180.176.1
    vlan 1
    name "DEFAULT_VLAN"
    no untagged A1-A24,B1-B24,C1-C24,D1-D24
    no ip address
    exit
    vlan 176
    name "VLAN176"
    untagged A1-A24,B1,B3-B24,C1-C24,D1-D24
    ip address 10.180.176.111 255.255.248.0
    tagged B2
    exit
    vlan 50
    name "VLAN50"
    ip address 10.178.50.71 255.255.254.0
    tagged B2
    primary-vlan 176




    Core 2

    ip default-gateway 10.178.50.1
    vlan 1
    name "DEFAULT_VLAN"
    no untagged A1-A24,B1-B24,C1-C24,D1-D24
    no ip address
    exit
    vlan 50
    name "VLAN50"
    untagged A1-A24,B1,B3-B24,C1-C24,D1-D24
    ip address 10.178.50.50 255.255.254.0
    tagged B2
    exit
    vlan 176
    name "VLAN176"
    ip address 10.180.176.143 255.255.248.0
    tagged B2
    primary-vlan 50

    Every Core and Lan has its own cisco router,so its like a campus with two buildings
    where we want to connect the two buildings to force traffic between the two buildings not to go over the routers and the wan.

    Thanks Peter