2

Let me start by saying that I am not looking to load balance between 2 ISPs.

I have a site where we get an MPLS ethernet handoff from our ISP. For some reason, our marketing dept. gave a contract company the green light to have their own service dropped in to support a contractor for the next 2 years. I'm still fighting to get my supervisor to shut this down and just let the contractor run on our network as we currently do, but I need to have a solution in hand in case I can't win this battle.

What I am thinking of doing is running their internet connection into my switch stack in order to get from MPOE to contractor cubicles. (company will not pay for cabling) I obviously need a separate IP scope for this VLAN. My thoughts on this are that I should be able to make it work with a unique IP scope, a static route and maybe a couple of ACLs.

Short version:new network on my equipment, separate ISP/gateway, unique IP scope, new vlan, no intervlan routing.

Improve this question
2
  • @Robert-currently running ipbase. That would be a great solution, thank you.
    – Rex Sheffield
    Commented May 12, 2015 at 18:53
  • well, when faced with upgrading IOS or pulling an extended DMARC and utilizing dedicated hardware as a 'best solution', they have opted to go with pulling cable and hardware. thank you very much for the insight.
    – Rex Sheffield
    Commented May 13, 2015 at 15:54

1 Answer 1

Reset to default
5

If you put their L3 interfaces in a separate VRF you would not need ACLs. No need to even mix the routing tables.

However you would need to be running IP Services IOS.

Improve this answer
1
  • 1
    VRF is the way to go, I second that.
    – RedShift
    Commented May 12, 2015 at 19:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.