SAF Forwarder with L2 Adjacency Configuration Example
From DocWiki
(Difference between revisions)
| Line 12: | Line 12: | ||
==Related show Commands== | ==Related show Commands== | ||
| - | show eigrp service-family | + | show eigrp service-family ipv4 neighbors |
Example(s): | Example(s): | ||
Latest revision as of 15:39, 7 June 2010
Contents |
Introduction
This configuration example demonstrates how to configure SAF Forwarders that share a common multi-access segment.
Example
Related show Commands
show eigrp service-family ipv4 neighbors
Example(s):
Commonly Asked Question
Q: Does SAF have to run EIGRP?
A: Although SAF requires that an EIGRP virtual-instance be configured ("SAF-fwdr" in the example above), EIGRP as a routing protocol is not required in order for SAF to operate properly. SAF is responsible for advertising services and not IP prefixes. SAF can run with any routing protocol (eg: static, RIP, EIGRP, OSPF, BGP).
Related Information
Technical Support & Documentation - Cisco Systems SAF Product Page - Cisco Systems Cisco IOS SAF Configuration Guide - Cisco Systems
