Ethernet Switches & Routers

Reply
Occasional Contributor
Posts: 7
Registered: ‎10-27-2016

Can a FESX448 route between vlans?

I have a FESX448 running Version 03.2.00iT3e3.

I have two virtual interfaces attached to two difference vlans.

int ve 1 is attached to vlan 19  <<--I didn't create this, I would've made the ve and vlan match, does it matter?

int ve 44 in attached to vlan 44

 

ve 1 has an ip address of 172.30.40.1/24

ve 44 has an ip address of 172.30.170.1/24

 

I thought that since both of these interfaces are connected that I wouldn't have to create a static route for them, but I can't pass traffic between them.  What do I need to do in order to pass traffic between vlan 19 and vlan 44?

 

Thanks!

Contributor
Posts: 66
Registered: ‎02-25-2016

Re: Can a FESX448 route between vlans?

Did you attach it like
vlan 44
router-interface ve 44?

The vlan id does not need to match the ve interface id.
Regards
Jörg Kost
Occasional Contributor
Posts: 7
Registered: ‎10-27-2016

Re: Can a FESX448 route between vlans?

Yes,

 

vlan 19 name vlan19 by port
 tagged ethe 49
 untagged ethe 1 to 30 ethe 32 to 43 ethe 45 to 48
 router-interface ve 1
!
vlan 44 name vlan44 by port
 tagged ethe 31 ethe 49
 router-interface ve 44

Frequent Contributor
Posts: 134
Registered: ‎07-20-2015

Re: Can a FESX448 route between vlans?

To be honest, normally people match the VE number to the VLAN number...  Here is how I woudl do it

 

vlan 19 name SOMENAME by port

tagged ethe 49

untagged ethe 1 to 30 ethe 32 to 43 ethe 45 to 48

router-interface ve 19

|

vlan 44 name OTHERNAME by port

tagged ethe 31 ethe 49

router-interface ve 44

!

 

interface ve 19

port-name Some Description Here

ip address 172.30.40.1 255.255.255.0

!

 

interface ve 44

port-name Some Other Description Here

ip address 172.30.170.1 255.255.255.0

!

 

 

Your issue is probably having to do with the tagging of the interfaces.  To route between them, you need to connect something on 31 or 49 that sets an 802.1q VLAN identifyer tag to 44.  I.e. You need a trunk port, which is typically a switch.

 

Most computers do not do this unless you go out of your want to change the network adapter parameters.

 

This should work perfectly fine to route between these two directly connected subnets:

 

SSH@LAB#sh ip route
Total number of IP routes: 2
Type Codes - B:BGP D:Connected O:OSPF R:RIP S:Static; Cost - Dist/Metric
BGP Codes - i:iBGP e:eBGP
OSPF Codes - i:Inter Area 1:External Type 1 2:External Type 2
Destination         Gateway Port  Cost Type Uptime
1 172.30.40.0/24    DIRECT  ve 19 0/0  D    1h
2 172.30.170.0/24   DIRECT  ve 44 0/0  D    1h

 

Occasional Contributor
Posts: 7
Registered: ‎10-27-2016

Re: Can a FESX448 route between vlans?

I do have a switch connected to eth 31 that is 802.1q tagging with vlan 44.

 

 

Occasional Contributor
Posts: 7
Registered: ‎10-27-2016

Re: Can a FESX448 route between vlans?

SSH@FESX-sw#sho ip route
B:BGP D:Connected  R:RIP  S:Static  O:OSPF *:Candidate default
        Destination     NetMask         Gateway         Port       Cost   Type
 1      172.29.40.0     255.255.255.0   0.0.0.0         v1         1      D
 2      172.30.170.0    255.255.255.0   0.0.0.0        v44       1     D

Occasional Contributor
Posts: 7
Registered: ‎10-27-2016

Re: Can a FESX448 route between vlans?

I just wanted to add a little more info.

 

I am able to ping from a host on vlan44 to the IP address of the virtual interface ve1 of vlan19, but I cannot ping beyond to anything else in vlan19.  Why?

Contributor
Posts: 66
Registered: ‎02-25-2016

Re: Can a FESX448 route between vlans?

Does the hosts from vlan19 actually have a route or a default route set to vlan44?
Regards
Jörg Kost

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.

vADC is now Pulse Secure
Download FREE NVMe eBook