Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Attention: The Community will be in read-only mode on 12/14/2017 from 12:00 am pacific to 11:30 am.

During this time you will only be able to see content. Other interactions such as posting, replying to questions, or marking content as helpful will be disabled for few hours.

We apologize for the inconvenience while we perform important updates to the Community.

New Member

EIGRP on Nexus 7k's

So I'm still stuggling with this, with a 'go live' deadline of this evening...

Current sitatuion:

we have a 6513 at the core of our network, with  2 MPLS networks servicing our branch offices.  We have provider A and B routers doing BGP across the MPLS, and EIGRP locally.  We redistribute the routes across the protocols.  Life is good.

Now, we are replacing 6513's with 2 new Nexi's  (what is the plural of Nexus anyway?)  I  thought it would be a simple fork-lift.  Set up a peer-keep alive and a VPC between the 2 nexus units, connect one router to each nexus (each router has only 1 link to the internal network so there is no redundancy in that regard), and configure EIGRp on the nexus.

Not exactly.  I learned variance won't work and got kind help on this forum around that.

Now though, I come across an article from Brad Hedlund on routing across the Nexus units that threw me a curve.  The article says that a link like we are talking about won't work, in fact,  it looks like from that article that our set up won't work and the best we can do is HSRP with static routes?!  

That may be true if your routers have multiple links and you are trying to do VPC from each router, one link to each Nexus.  That's not what we are trying to do. Meanwhile our SE says we need a layer 3 link (another vlan or SVI) for our eigrp network that we deliberately stop from traversing all other trunk links...but why?  what does that do for us? That's going to put a lot of readdressing on us at a time when it's late and we are tired and error prone.

I'm trying to make this as close to  'fork lift' operation as I possibly can, with as little reconfiguring as possible.  In less than a month we hope to have a pFr based answer and anyting I do tonight would be undone anyway.  Would I be better at this point putting both routers on a single nexus and dealing with the potential risks if that nexus failed?  I'm looking for SIMPLE and DEPENDABLE.

1 REPLY
New Member

EIGRP on Nexus 7k's

correction, DEPENDABLE is probably the wrong word.  I'm looking for PREDICTABLE behavior when I move my routers off the 6513 and onto the nexus units.

Until I can get to a fully redundant physical layer connect there is no 'dependable'per se, only 'quickly fail over' to the other router.  I can live with that for the short duration.

What I can't live with is a 48 hour troubleshooting session this weekend like I had last weekend we we tried to make MEC work between the Nexus and our disk sans.  That was a nightmare.  We just don't have that kind of time and our team is exhausted going in.  I just want a quick configuration to make EIGRP work across the MPLS routers/Nexus boxes.

299
Views
0
Helpful
1
Replies
CreatePlease to create content