Re: Problem with VLAN

John

I am not clear from your posting whether you want the switches to process as layer 2 switches or as layer 3 switches. And what you have seems to be a combination of both.

Both switches declare VLAN 44 as the management VLAN and configure addresses in that VLAN and trunk that VLAN so that part is good. The router configuration is done on the physical interface and there is no trunking so it can not access any other VLAN and can not do inter-VLAN routing. And the switch configures Fa0/24 as a routed port not a VLAN port. So the router ports are not part of VLANs and are not carried over the trunk.

There is a VLAN 7 configured but there is no VLAN interface for it on the switches and no ability to route for it on the routers. So something needs to be done if the devices in that VLAN need to communicate with anything outside that VLAN.

It seems to me that there are several possible solutions:

- you can make the switch to router connection into a trunk, enable trunking on the router, and do inter-VLAN routing on the routers. (let the switches operate as layer 2 switches)

- you can make the switch ports connecting to the routers access ports, configure a VLAN interface for that VLAN and do inter-VLAN routing on the switches. (Let the switches operate as layer 3 switches)

Either approach can work, but it needs to be consistently implemented.

This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
"Th...
view more

Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
1. commandoversms.tcl
2. PDF with instructions on how to load and use the .tcl file.