I'm using entservicesk9-12.4(13b). It shows the vlans on the command 'show vlan-switch,' but It will not allow a Vlan nn interface. There is NO ESW module. The router only has two FE ports. I thought that you could only define vlan interfaces on systems with a switch module.
You don't need to create vlan if you are using physical interfaces. Just give ip address for each interface in respective vlan. If you want to use subinterfaces (router-on-a-stick), then you can assign that subinterface to a vlan and need to have a trunk link between the router and switch. In gns3 you can configure a router with switchports (has a module with 16 ports) to act as a switch, where you configure ports, vlans and assign them to vlans. The switch in gns3 is not configurable, except to add ports to it.
I wanted to do this WITHOUT a switch module. After a few hours of tweaking...here is the relavant part of the config:
! bridge irb ! ! ! interface FastEthernet0/0 no ip address no ip route-cache cef no ip route-cache duplex auto speed auto ! interface FastEthernet0/0.10 encapsulation dot1Q 10 ip unnumbered BVI1 no ip route-cache bridge-group 1 ! interface FastEthernet0/1 no ip address no ip route-cache cef no ip route-cache duplex auto speed auto ! interface FastEthernet0/1.10 encapsulation dot1Q 10 ip unnumbered BVI1 no ip route-cache bridge-group 1 ! interface FastEthernet0/1.20 encapsulation dot1Q 20 ip unnumbered BVI1 no ip route-cache bridge-group 1 ! interface BVI1 ip address 10.0.0.254 255.255.255.0 secondary ip address 192.168.0.254 255.255.255.0 ! ! ! no ip http server no ip http secure-server ! ! ! ! control-plane ! bridge 1 protocol ieee bridge 1 route ip ! !
This 'seems' to work, but I'm open to any sugestions to clean it up, and perhaps, add some filtering! I've read that this will put a processing strain on the router, too.
If the requirements are to use bridged interfaces than your config should work. Usualy routers provide intervlan routing and since you have only 2 vlans in your network I would configure each interface with ip addresses in each vlan and reduce the strain on the CPU. But that is just an opinion, you should consider other advice as well.
I need to 'split the subnets' because I must feed the streams into another box that will NOT accept two subnets on the same VLAN. Each subnet must have a seperate VLAN. The sad part is that it IS a Cisco box.
The bridged setup is just the first thing that crossed my mind. I tried placing the IP addresses on the individual sub-interfaces, but I would get IOS errors doing that. I had to work with the single IP address/subnets, and adding more would just mess up the rest of the network. All of my searching on the Net for some other solution would turn up information on routing stuff like LAT or IPX.
On a Cisco, there's always more than one way to do something. It's just a matter of 'sharing' it with the rest of the community. This is my quick & dirty solution. As I learn more, I can refine it! I hope it helps someone else out.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...