I have a 2801 the two onboard FastEths and a HWIC-4esw card in it. I need two wans and one trunk to my switches. I had been planning on using the to Fasts for WANs and then one interface on the HWIC-4esw as the Lan trunk.
But I soon noticed that I couldn't put IP's on the HWIC interfaces, did a search and read this thread telling me what I feared... Since I don't have a HWIC-1FE, SVI's come into play.
Now I'm reading what is involved in using SVI's to make it work.. that's all.
int Vlan 100
ip address 1.1.1.1 255.255.255.0
ip nat outside
int vlan 101
ip address 2.2.2.2 255.255.255.0
ip nat outside
etc, etc, etc...
To bind them to specific ports on the ESW do this
int fa 0/0/0
switchport access vlan 100
int fa 0/0/1
switchport access vlan 101
now you can use them as outside interfaces. The thing that sucks about this is not being able to use OER to control the routing. The reason this works is you are setting the ports to listen to traffic and assume that it belongs to the right vlan. It would be best to think of
int vlan 100
ip address 1.1.1.1 255.255.255.0
int fa 0/0/0
switchport access vlan 100
the same way you would think of
int fa 0/1
ip address 1.1.1.1 255.255.255.0
the difference is not that big when you are not trying to load balance the traffic.
Shawn
That was a great explanation, Wingatesl. So basically, if I made the 4esw port a trunk port I could listen to all the vlans like a FE port with sub-interfaces, no?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.