Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cisco 3640 "port binding"?

Status
Not open for further replies.

eddiejclayton

Technical User
Aug 29, 2006
3
US
Hello all,

Is there a way to "bind" ports together? We have a 3640 with 4 ethernet ports, 2 serial ports, and 2 T1 WIC's. We are upgrading our WAN connectivity with 2 T1 circuits (separate ISP's) and I would like to use this router for the connections.

This router is currently providing some LAN routing between 2 of our internal networks. Is there a way to "bind" (for lack of a better term) 1 T1 WIC to 1 fastethernet port so that they can only talk to each other? I have an external Sonicwall that will do all of the load balancing, I just need something to get my 2 T1 connections to the Sonicwall.

I'm currently reading up on policy routing and this looks like it may be an option. Does anyone have any suggestions? Thanks in advance for any help or advice that is offered.
 
You could use a static route to force traffic from one interface to go out another.

router config# ip route source_add 0.0.0.0 dest_add

Where source_add = T-1 interface network
Where dest_add = Fasteth interface ip
 
Hmm....it's not allowing me to do that, gives me "unrecognized command". I had a feeling that would be entirely too easy. :( Anyone else?
 
Were you in "Global Configuration Mode"??? (type config terminal while in priveleged mode).

You have to be in the global configuration context to issue "ip route" commands. Otherwise, it will give you the "unrecognized command" error.
 
Hi,

You can use the "route-map" or policy-based routing feature where you can virtually tie traffic to strictly flow from one interface to another specific interface.

Example:

!
interface FastEthernet0/0
ip address 192.168.1.1 255.255.255.0
!
interface FastEthernet0/1
ip address 192.168.2.1 255.255.255.0
!
interface serial0/0
ip address 202.75.xx.1 255.255.255.252
!
interface serial0/1
ip address 218.208.xx.1 255.255.255.252
!
access-list 10 permit ip 192.168.1.0 0.0.0.255
access-list 20 permit ip 192.168.2.0 0.0.0.255
!
route-map MYMAP permit 10
match ip address 10
set interface serial0/0
!
route-map MYMAP permit 20
match ip address 20
set interface serial0/1
!
route-map MYMAP permit 30



Rgds,
AK
 
@amrihk

Thanks for the heads up! I figured that policy based routing would be the most likely option. Hopefully I'll get a chance to work on this tomorrow to test everything out. Thanks again!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top