I read the OP and
this and know how to set up the device via TFTP. I dont see where any config guide is listed on how to set up L3, VLANs, etc. I checked
Resources --> Getting Started, --> How-to Guides, --> Reference Materials and dont see any config guide.
Anyway, thanks for the help.
Serious question, where is the documentation?? Asking
after spending much time trying to find it first. If there is a document that I can read and follow, I'll spend the time doing it. If it is between 320 pages of back and forth forum posts, no one has that kind of time, Brocade is not for me and I'll keep it moving.
OK, to be fair, I did just go back and check that "Advanced" section of the docs and VLANS and Inter-VLAN routing are both "Coming soon" placeholders. As klui notes, the manual in Fohdeesha's master ZIP file are comprehensive.
Brocade is like HPE in that you define a VLAN, then enter the VLAN and tag or untag ports to it. This is the opposite of Cisco, where you define a VLAN, then enter the port and add your VLANs there
Brocade example:
Code:
SSH@core(config)#vlan 100
SSH@core(config-vlan-100)#tag ethernet 1/1/39
This can be ... annoying if you have a lot of ports that are trunks as you have to enter each VLAN individually and tag the ports. You can tag a range or list of interfaces, but you cannot edit a range of VLANs.
Edit: I am wrong, just double checked and the syntax for a VLAN range selection is:
Code:
SSH@core(config)#vlan 1 4 6 10
SSH@core(config-mvlan-1*10)#
or
Code:
SSH@core(config)#vlan 1 to 10
SSH@core(config-mvlan-1-10)#
The * appears to indicate a non-contiguous range, vs the dash in the second example.
Brocade indexing starts at 1, so the notation for 1/1/39 is: Stack Unit 1, Module 1, Port 39. Even unstacked, it will always be this notation.
Cisco example:
Code:
core-40g#conf t
core-40g(config)#vlan 100
core-40g(config-vlan-100)#name Test
core-40g(config-vlan-100)#interface int range gi 1/0/1-22
core-40g(config-if-range)#switchport mode trunk
core-40g(config-if-range)#switchport trunk allowed vlan 2,4-6,100
Above may not be exact given differences in iOS versions and switches, but should be close enough.
In this example, I am able to grab a range of interfaces and tag all the necessary VLANs to them in one shot.
Inter-VLAN routing: The Short Version
Image I knocked together for another post related:
And here are some absolutely barebones L3 inter-VLAN routing config with DCHP helper statements. May or may not work, I have been too busy to lab this out and validate it completely, but it's incredibly similar to a config I had on a Cisco switch before I flattened my network:
Modify a VLAN and define a VE:
Code:
conf t
VLAN 1
router-interface ve 1
int ve 1
ip address 192.168.1.1 255.255.255.0
end
To set the default route for the switch:
Code:
conf t
ip route 0.0.0.0/0 172.31.255.1
end
Assumes one DHCP server managing multiple subnets:
Code:
conf t
int ve 1
ip helper-address 1 172.31.255.1
int ve 2
ip helper-address 1 172.31.255.1
< ... and so on ... >
end
If you have things on your network that depend on mDNS, uPNP (SSDP), or other broadcast/discovery protocols, these are typically NOT routable and you will have to proxy them or live with those services not being available outside of their respective subnets. If you do any gaming (PC or console) be aware that many games use uPNP for setting firewall rules for peering and you may break things. uPNP/SSDP can be handled if the switch supports multicast routing, but I haven't dug into Brocade to see if it does that.
If you've never configured an enterprise grade switch before, then this will be an experience because VLANs and routing (ignoring even fancier stuff like iBGP or OSPF) are potential headscratchers when starting from nothing ("Wait, was that interface tagged or untagged? Is the client device tagging a VLAN? Did I forget to include that VLAN in my trunk? Is my subnet prefix the correct size? Did I set the wrong prefix in the route?") The manuals from the Rucksu/Commscope site or packaged in Fohdeesha's ZIP assume that you have a passing familiarity with the concepts.
The manufacturer's documentation is not going to have a full "here's how you go from first start to routed VLAN" example; it's mostly a command reference that will have specific, basic examples of a given command.
