01-23-2011 11:00 PM - edited 03-06-2019 03:08 PM
Hi,
I'm running up four Nexus 7010s with version 5.1(2)
I've configured my eigrp process in the usual IOS way as follows
router eigrp 100
network 172.16.0.0/16
This works fine, every interface I create with a 172.16.x.x address is advertised by eigrp and I configure "ip passive-interface router eigrp 100" on all the interfaces I dont want to form neighbors on. All my neighbors come up, routing is fine etc etc
Now I'm told that the network statement is not supported in NXOS and I should be putting "ip router eigrp 100" on every interface instead.
nexus-01# sh ip eigrp 100
IP-EIGRP AS 100 ID 172.16.0.1 VRF default
Process-tag: 100
Status: running
Authentication mode: md5
Authentication key-chain: RCH-EIGRP
Metric weights: K1=1 K2=0 K3=1 K4=0 K5=0
IP proto: 88 Multicast group: 224.0.0.10
Int distance: 90 Ext distance: 170
Max paths: 8
Number of EIGRP interfaces: 4 (0 loopbacks)
Number of EIGRP passive interfaces: 4
Number of EIGRP peers: 4
Redistributing:
static route-map static-into-eigrp
Graceful-Restart: Enabled
Stub-Routing: Disabled
NSF converge time limit/expiries: 120/0
NSF route-hold time limit/expiries: 240/0
NSF signal time limit/expiries: 20/0
Redistributed max-prefix: Disabled
Network commands:
172.16.0.0/16
So what's the story with the EIGRP network command in NX-OS. Is it supported? If not, why is it in the software, and why does it work?
01-24-2011 04:21 AM
Hi,
actually I'm not so much informed about the Nexus ;-)
But the network command obviously doesn't exist anymore... you enable EIGRP with (feature eigrp), then create the instance with (router eigrp xxx) and so on.
And like you said, you have to enable the network distribution with the (ip router eigrp tag) in interface mode.
Hope I could help you.
Regards
Martin
01-24-2011 04:52 AM
Hi Martin, the eigrp network statement is not mentioned in the 5.x configuration guide or the command reference.
However it is accepted by the switch in config-router mode, it works exactly the same as it does in IOS and it appears in the running configuration.
It also continues to work across a full power cycle of the switch.
So there is a discrepancy between the documentation and the reality.
01-24-2011 05:01 AM
hi,
ok, so I was wrong about the statement... sorry.
I only read the documentation and a certification book of cisco in which they don't mention the network statement.
Maybe the guys should update the documentation, or it depens on Versions, don't know exactly.
But thanks for your reply so I know more about the reality ;-)
greets
Martin
01-24-2011 11:02 AM
Here's a document comparing nxos with ios for eigrp that should help you out:
http://docwiki.cisco.com/wiki/Cisco_NX-OS/IOS_EIGRP_Comparison
Here's the comparsion for a lot of features:
http://docwiki.cisco.com/wiki/Cisco_Nexus_7000_NX-OS/IOS_Comparison_Tech_Notes
-Matt
01-25-2011 12:13 AM
Hi Matt,
thanks for the links, I know the documentation but our problem is, that the documentation told the configuration for the network is as follows... interfacex/x ip router eigrp etc. Everything makes sense, but why is the command network x.x.x.x in eigrp configuration? Like in the old IOS versions.
Greets Martin
01-25-2011 03:35 AM
I've reconfigured my equipment in accordance with the doco (using interface commands instead of network statement). Works the same.
Maybe Cisco should look at removing the network statement from the software if you're not supposed to use it?
04-25-2018 11:45 PM
Not used Nexus but as far as I am aware you still need to enable EIGRP under the interface.
So using your example above -
int vlan 3
ip router eigrp 100
ip passive-interface eigrp 100
ie. you need to run EIGRP on the interface but then make it passive with the additional command.
Just using the passive-interface command on it's own does not mean EIGRP runs on that interface.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide