- Finding Feature Information
- Prerequisites for Cisco SAF
- Restriction for Cisco SAF
- Information About Cisco SAF
- How to Configure a Cisco SAF Forwarder
- Enabling Cisco SAF
- Configuring Interface-Specific Commands for Cisco SAF
- Configuring Cisco SAF for Multi-Topology Networks
- Configuring Static Neighbor Relationships for Cisco SAF
- Configuring Stub Routing for Cisco SAF
- Configuring Route Authentication for Cisco SAF
- Configuring Logs for Neighbor Changes and Warnings
- Configuring the Percentage of Link Bandwidth Used for Cisco SAF
- Setting Metric Dampening Intervals for Cisco SAF Interfaces
- Adjusting the Interval Between Hello Packets and the Hold Time
- Disabling Split Horizon
- Setting Metric Maximum Hops
- Configuring a Cisco SAF External Client
- Displaying Cisco SAF Statistics
- Deleting Information from a Cisco SAF Configuration
- Configuration Examples for Cisco SAF
- Example: Enabling Cisco SAF
- Examples: Configuring Cisco SAF Interfaces
- Example: Configuring Cisco SAF Topology
- Example: Configuring Cisco SAF Stub Routing
- Example: Configuring Cisco SAF with IP-RIP
- Example: Configuring Cisco SAF with OSPF
- Example: Configuring Cisco SAF with EIGRP
- Example: Configuring Cisco SAF Forwarders Located on Separate LANs
- Example: Configuring a Centralized Cisco SAF Forwarder
- Examples: Configuring a Cisco SAF Client
- Additional References
- Feature Information for Cisco SAF
Configuring Cisco SAF
Cisco Service Advertisement Framework (SAF) provides a framework that allows applications to discover the existence, location, and configuration of networked resources within networks. Cisco SAF allows a timely and reliable awareness of the services within networks, while applications advertise and discover services on networks. Service information distributes through a network of Cisco SAF cooperative nodes that assume specific functions to efficiently distribute knowledge of services and facilitate their discovery.
Finding Feature Information
Your software release may not support all the features documented in this module. For the latest caveats and feature information, see Bug Search Tool and the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the feature information table at the end of this module.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Prerequisites for Cisco SAF
Restriction for Cisco SAF
Information About Cisco SAF
- Cisco SAF Overview
- Cisco SAF Service Identifier Number Formats
- Cisco SAF and the Role of Domains in a Network
- Cisco SAF Virtual Routers
- Cisco SAF Neighbor Relationships
- Benefits of Cisco SAF
Cisco SAF Overview
Cisco Service Advertisement Framework (SAF) provides a framework that allows applications to discover the existence, location, and configuration of networked resources within networks. Cisco SAF allows a timely and reliable awareness of the services within networks, while applications advertise and discover services on networks. Service information distributes through a network of Cisco SAF cooperative nodes that assume specific functions to efficiently distribute knowledge of services and facilitate their discovery.
A non-SAF node is any node in a network that does not understand SAF. Non-SAF nodes are called "dark nets" and are required to traverse ISPs. Cisco SAF messages are IP-based and therefore are unaffected by dark nets.
Cisco SAF cooperative network nodes are grouped into two major functional responsibilities:
- Cisco SAF forwarder--Distributes service information through the network and makes these services discoverable by clients in the network.
- Cisco SAF client--Advertises and discovers services.
An effective Cisco SAF network requires both roles to be configured.
- Cisco SAF Forwarder Overview
- Cisco SAF Client Overview
- External Cisco SAF Client Using XMCP Overview
Cisco SAF Forwarder Overview
A Cisco SAF forwarder receives services advertised by Cisco SAF Clients, distributes the services reliably through the network, and makes services available for Cisco SAF clients. A Cisco SAF forwarder:
- Ensures reliable delivery of service advertisements.
- Maintains knowledge of path redundancy.
- Is scalable.
- Minimizes the use of network bandwidth by using targeted multicast and unicast messages.
The Cisco SAF forwarder can propagate service advertisements to other Cisco SAF forwarders and can propagate across a LAN, campus network, WAN, or ISP.
A basic Cisco SAF forwarder provides the relationship between Cisco SAF clients and the framework. A Cisco SAF forwarder is normally located at the edges or boundaries of a network. The Cisco SAF forwarder receives service advertisements and stores a copy before forwarding the advertisement to its neighbor SAF nodes. The client and forwarder relationship is to maintain the advertisement. If a client removes a service or disconnects from the forwarder node, the node will inform the framework about the services that are no longer available. When the forwarder node receives advertisements from other forwarder nodes, it will keep a copy of the entire advertisement (header and opaque data) and forward it to other SAF peers.
You can configure a Cisco SAF forwarder on a LAN to automatically allow dynamic discovery of services to all enabled interfaces and, at the same time, specify interfaces (static configuration) that you want blocked to other interfaces attempting to discover their services.
You can configure a Cisco SAF forwarder across a non-SAF node to automatically allow dynamic discovery of services. For example, Cisco SAF forwarders can join a common peer group. You can also create static configurations (unicast) between pairs of Cisco SAF forwarders.
 Note |
Multicast routing is required to allow dynamic discovery of services. |
Note |
With CSCts55778 and CSCtq71851, the Cisco SAF forwarder can send service metadata to its neighbor SAF nodes. Metadata is XML information, and service data is information that a server communicates to a client about itself. The service metadata does not propagate in mixed software release environments until such time that the version of EIGRP and SAF is upgraded. |
Cisco SAF Client Overview
A Cisco SAF client is a producer (advertises to the network) or a consumer of services (requests a service from the network), or both. When a Cisco SAF client sends a register message to a Cisco SAF forwarder, it establishes a relationship with the Cisco SAF forwarder. The Cisco SAF forwarder uses this register message to obtain a unique handle that distinctly identifies this Cisco SAF client from others connected to the same forwarder. Only after a Cisco SAF client registers is it able to advertise (publish) or request (subscribe to) services. The figure below shows a typical Cisco SAF network.
When advertising a service, a Cisco SAF client publishes (sends) advertisements, to the Cisco SAF forwarder, that contain information about the service it offers. Services are identified by a unique service ID, sub-service ID, and instance ID and are described by service data. For more information on service identifiers, see Cisco SAF Service Identifier Number Formats. The Cisco SAF client can send multiple publish requests, each advertising a distinct service. The Cisco SAF forwarder advertises all services published by the Cisco SAF client. The Cisco SAF client can update an existing service advertisement by sending a new publish request for the same service. The client can also generate an unpublish request, which removes one of its existing service advertisements.
When requesting a service, the Cisco SAF client sends a request notification of services using a subscribe request. The subscribe request contains a filter that describes the set of services in which the Cisco SAF client is interested. In response to this request, the Cisco SAF forwarder sends the current set of services that match the filter to the Cisco SAF client in a series of notify requests. As with a publish request, the Cisco SAF client can generate multiple subscribe requests, each with a different filter. The Cisco SAF client can also generate an unsubscribe request, which removes one of its existing subscriptions.
Cisco SAF clients can be internal (existing within a Cisco SAF forwarder) or external (existing on a separate device and communicating with a Cisco SAF forwarder using the XMCP protocol). Internal Cisco SAF clients include Capabilities Manager (see Configuring Capabilities Manager) and Cisco Unified Communications Manager Express (Cisco Unified CME). External Cisco SAF clients using XMCP include Cisco Unified Communications Manager.
External Cisco SAF Client Using XMCP Overview
An external Cisco SAF client initiates a TCP connection to a Cisco SAF forwarder that has been configured as an XMCP server. Once the TCP connection is established, the client begins an XMCP session over this connection by sending an XMCP register message to the Cisco SAF forwarder.
When an XMCP server receives a request, it locates the username attribute in that request and uses it to access its local copy of the password, and then it computes its own message-integrity value for the request. If the computations match, the passwords must match and the request is authenticated, permitting the XMCP client to act as a Cisco SAF client. If they do not match, the password is incorrect and the request will be rejected.
Once the XMCP session has been established successfully, the XMCP client may send XMCP publish, unpublish, subscribe, and unsubscribe requests. When the server receives and successfully authenticates these requests, it translates the requests into the equivalent Cisco SAF client requests and sends them to the Cisco SAF forwarder. Similarly, Cisco SAF client notify requests from the forwarder are translated into XMCP notify requests and sent to the XMCP client.
Because an external Cisco SAF client may lose connectivity to the Cisco SAF network in the event of a network outage, a Cisco SAF forwarder requires periodic verification regarding the liveliness of the Cisco SAF client to advertise its services to the Cisco SAF network. In XMCP, this is accomplished by exchanging a liveliness timer between the client and the server at the time of registration. The XMCP client is responsible for ensuring that the interval between requests never exceeds this value. An XMCP client has no data (publish or subscribe) to send, so it generates a small keepalive message to refresh the timer on the server.
A Cisco SAF forwarder considers that an external Cisco SAF client has failed if it has not seen an XMCP request from the client in a time period equal to the liveliness timer. When a Cisco SAF forwarder detects that the Cisco SAF client has failed, it withdraws the services advertised on behalf of that Cisco SAF client from the network and removes any subscriptions that the Cisco SAF client had established. As an alternative to waiting for the liveliness timer to expire, a Cisco SAF client can be manually unregistered (sending an unregister request to terminate the XMCP session) to gracefully cause a Cisco SAF forwarder to withdraw all services and subscriptions.
Cisco SAF Service Identifier Number Formats
A service is any information that a Cisco SAF client application wishes to advertise, which can then be used by other Cisco SAF client applications. A service advertisement consists of service data. Service advertisements are propagated between forwarders using header data. Cisco SAF clients that are interested in a service receive, and may inspect, service header and service data.
A service identifier number uniquely identifies the service on a network. The following example shows the format of a service identifier number:
service:sub-service:instance.instance.instance.instance
The service identifier is a 16-bit decimal identifier for the major service being advertised. A major service refers to a specific technology area, such as Cisco Unified Communications (UC). Service identifiers are assigned by Cisco to various customers who require an SAF client.
The following example shows the service ID values for IP Everywhere and Cisco Unified Communications:
Cisco Defined Numbers
SAF_SERVICE_ID_IPE = 100 ! IP Everywhere
SAF_SERVICE_ID_UC = 101 ! Unified Communications
The sub-service identifier is a 16-bit decimal identifier for the minor service being advertised. A sub-service (also referred to as a minor service) refers to the type of service within a technology. For example, within UC:
- Sub-service 1 is TDM gateway.
- Sub-service 2 is hosted-DN.
- Instance identifies a specific service advertisement for this kind of service.
For example, service identifier 101:1:abcd.1234.ef.678 could be an advertisement of a UC (service 101) TDM gateway (sub-service 1) announced by the Communications Manager cluster in a certain location (instance abcd.1234.ef.678). The instance identifier is a unique 128-bit number that identifies the specific service advertised.
Client teams define the use of sub-service and instance values for their applications. Clients must ensure instance uniqueness within a Cisco SAF domain.
Cisco SAF and the Role of Domains in a Network
As the variety and number of network services grow, providing timely and reliable awareness of these services starts to play a more significant role in increasing productivity and efficiency. One of the biggest challenges in propagating service availability awareness over a WAN is one of scalability. As networks grow, the services offered by the devices on these networks increase. Protocols responsible for the service advertisement need to scale to handle this increased load. These protocols also need to react efficiently to rapid changes and propagate the new information in a timely manner.
Cisco SAF is designed to be a scalable solution for enterprise service locations and is capable of spanning LAN and WAN Internet segments. As an enterprise solution, you can configure Cisco SAF to use domains to scale for very large networks. Just as Cisco Enhanced Interior Gateway Routing Protocol (EIGRP) defines the concept of an autonomous system in which routes can be searched for in a hierarchical manner, Cisco SAF employs the similar concept of a domain and subdomains.
Cisco SAF provides a dynamic peer discovery and service advertisement propagation technique known as IP multicast. IP multicast requires the cooperation of IP Cisco SAF forwarders (the devices that connect IP subnets together to form intranets). IP multicasting, however, may not be completely implemented across some intranets. In the absence of IP multicasting, Cisco SAF operates within the configured subnet or within the groups of subnets over which IP multicast is supported.
Cisco SAF forwarders offer two primary types of administrative domains (ADs); a domain and a subdomain. A domain and a subdomain function the same with one notable exception; subdomains do not form unique neighbor relationships, but instead rely on a single peering.
Ideally, a network would require only a single domain for advertising all services. However, because of scaling and policy issues, some networks require the creation of multiple domains. The recommendation is to use a single domain. Consider using multiple domains when:
- More than 30,000 services are registered in a single domain.
- Logical grouping of services is needed to restrict propagation of services.
Closed groups are needed to prevent users from browsing services that they are not allowed to access.
Service redistribution allows different domains to exchange service information. Services may need to be bound to specific areas of the network, or the number of services in a given network may need to be limited. If you cannot use a single domain, service advertisement redistribution might be the solution.
Each domain on a network is separated into an AD. All Cisco SAF forwarders in the same AD (running the same domain) have complete knowledge of the entire AS. A Cisco forwarder that connects two (or more) administrative domains is known as a border forwarder. A border forwarder advertises service information from one AS to another AS. Proper design should also be considered if multiple border forwarders are used to avoid loops (information learned from one AD being sent back to the same AD).
Cisco SAF Virtual Routers
Cisco EIGRP service-family support extends the named configuration to allow configuration of multiple instances that operate independently. The addition of a Virtual Router ID (VRID) to the base Cisco EIGRP packet encoding allows for multiple instances.
As each virtual device is created, a VRID is assigned to the top-level router and shared with the address families and service families that are configured under it.
Cisco SAF Neighbor Relationships
Cisco SAF forwarders can operate in networks that do not have devices that support the Cisco SAF forwarder protocol. These networks are referred to as "dark nets." There are two methods for configuring Cisco SAF forwarders over IP networks that do not support Cisco SAF (IP clouds); unicast Cisco SAF neighbors and multicast Cisco SAF neighbors.
You can use a unicast configuration to provide a reliable point-to-point adjacency with neighbors. As the number of Cisco SAF forwarders increases, you can use multicast to provide an efficient transport between multiple Cisco SAF neighbors. A single IP multicast group address can be used for multiple Cisco SAF neighbors to exchange SAF information in a peer-group.
Benefits of Cisco SAF
Traditionally, to locate services on a network, network applications must be configured with the hostname and the network address of the desired service or must use an overlay mechanism such as DNS. Existing protocols that support service advertisement provide periodic-based announcements of resource utilization. These network services are typically LAN-based.
The figure below shows a Cisco Unified Communications Manager network that requires a traditional configuration methodology.
Cisco SAF provides a framework that allows networking applications to automatically discover the existence, location, and configuration of networked services within networks. This automated discovery of services replaces the manual entry of complex configurations such as dial plans that often require repetitive configuration changes. Cisco SAF also allows applications to advertise and discover their services. Cisco SAF allows you to create a configuration once and then have it propagate to all devices that require the information.
The figure below shows a Cisco Unified Communications Manager network that uses Cisco SAF.
You can configure a Cisco SAF client either on the same device as the Cisco SAF forwarder or on an external device.
How to Configure a Cisco SAF Forwarder
- Enabling Cisco SAF
- Configuring Interface-Specific Commands for Cisco SAF
- Configuring Cisco SAF for Multi-Topology Networks
- Configuring Static Neighbor Relationships for Cisco SAF
- Configuring Stub Routing for Cisco SAF
- Configuring Route Authentication for Cisco SAF
- Configuring Logs for Neighbor Changes and Warnings
- Configuring the Percentage of Link Bandwidth Used for Cisco SAF
- Setting Metric Dampening Intervals for Cisco SAF Interfaces
- Adjusting the Interval Between Hello Packets and the Hold Time
- Disabling Split Horizon
- Setting Metric Maximum Hops
- Configuring a Cisco SAF External Client
- Displaying Cisco SAF Statistics
- Deleting Information from a Cisco SAF Configuration
Enabling Cisco SAF
To enable Cisco SAF and create a Cisco SAF service-discovery process, use the following commands.
DETAILED STEPS
Configuring Interface-Specific Commands for Cisco SAF
Cisco SAF provides an inheritance precedence for interface-specific commands. Configurations made in service-family interface configuration mode have priority over specific service-family interface and factory default configurations. To configure interface-specific commands under the service family for Cisco SAF, use the following commands:
DETAILED STEPS
Configuring Cisco SAF for Multi-Topology Networks
Use the following configuration to register clients and publish or subscribe services into a named topology. If you configure a second topology using an existing topology name, but with a different ID, it will replace the existing topology, rather than create two IDs for the same topology.
Note |
With CSCts55778 and CSCtq71851, the Cisco SAF forwarder can send service metadata to its neighbor SAF nodes. Metadata is XML information, and service data is information that a server communicates to a client about itself. The service metadata does not propagate in mixed software release environments until such time that the version of EIGRP and SAF is upgraded. |
To configure Cisco SAF for multi-topology networks, use the following commands.
DETAILED STEPS
Configuring Static Neighbor Relationships for Cisco SAF
Use the following commands to configure static neighbor adjacencies between Cisco SAF forwarders.
DETAILED STEPS
Configuring Stub Routing for Cisco SAF
You can configure a Cisco SAF forwarder as a stub device. For complete information on Cisco EIGRP stub routing, see the "Configuring EIGRP" module in the IP Routing: EIGRP Configuration Guide.
To create an Cisco SAF stub device, use the following commands.
DETAILED STEPS
Configuring Route Authentication for Cisco SAF
Cisco SAF route authentication provides Message Digest 5 (MD5) authentication of routing updates from the routing protocol. The MD5 keyed digest in each packet prevents the introduction of unauthorized or false routing messages from unapproved sources. To configure route authentication for Cisco SAF, use the following commands.
DETAILED STEPS
Configuring Logs for Neighbor Changes and Warnings
By default, the system logs neighbor adjacency changes to help you monitor the stability of the routing system and detect problems. If you disabled logging of such changes and want to re-enable logging, use the following commands.
DETAILED STEPS
Configuring the Percentage of Link Bandwidth Used for Cisco SAF
By default, packets consume a maximum of 50 percent of the link bandwidth, as configured with the bandwidth interface configuration command. You may want to change the value if a different level of link utilization is required or if the configured bandwidth does not match the actual link bandwidth (it may have been configured to influence route metric calculations). Use the following commands to configure the percentage of link bandwidth used for Cisco SAF.
DETAILED STEPS
Setting Metric Dampening Intervals for Cisco SAF Interfaces
Because metric components can be changed rapidly, the frequency of the changes can have an impact on the network. Frequent changes require that prefixes learned though the SAF interface be updated and sent to all adjacencies. This update can result in further updates and, in a worst-case scenario, cause network-wide churn. To prevent such effects, metrics can be dampened or thresholds set so that any change that does not exceed the dampening threshold is ignored.
Network changes that cause an immediate update include when a device selects a new nexthop or a down interface or device.
Thresholds can be configured based on a change or on a time interval. If the dampening method is:
- Change-based, changes in routes learned though a specific interface or in the metrics for a specific interface will not be advertised to adjacencies until the computed metric changes from the last advertised value are significant enough to cause an update to be sent.
- Interval-based, changes in routes learned though a specific interface or in the metrics for a specific interface will not be advertised to adjacencies until the specified interval is met or unless the change results in a new route path selection. When the timer expires, routes that have outstanding changes to report are sent. If a route changes and the final metric of the route matches the last updated metric, no updated routes are sent.
Refer to the following sections for information on configuring change-based and interval-based metric dampening parameters.
Change-based Dampening Configuration
Use the following commands to set the maximum change-based dampening percentage for Cisco SAF interfaces.
DETAILED STEPS
Interval-based Dampening Configuration
Use the following commands to configure interval-based dampening for Cisco SAF interfaces. The value that you configure sets the interval when updates occur for topology changes that affect Cisco SAF interfaces and peers.
DETAILED STEPS
Adjusting the Interval Between Hello Packets and the Hold Time
Routing devices periodically send hello packets to each other to dynamically learn of other devices on their directly attached networks. This information is used to discover neighbors and to learn when neighbors become unreachable or inoperative.
By default, hello packets are sent every 5 seconds. The exception is on low-speed, nonbroadcast multiaccess (NBMA) media on which the default hello interval is 60 seconds. Low speed is considered to be a rate of T1 or slower as specified in the bandwidth interface configuration command. The default hello interval remains at 5 seconds for high-speed NBMA networks. Note that for the purposes of Frame Relay and Switched Multimegabit Data Service (SMDS), networks may or may not be considered to be NBMA. These networks are considered NBMA if the interface has not been configured to use physical multicasting; otherwise they are not considered NBMA.
The hold time is advertised in hello packets and indicates to neighbors the length of time for which they should consider the sender valid. The default hold time is three times the hello interval, or 15 seconds. For slow-speed NBMA networks, the default hold time is 180 seconds. On congested and large networks, the default hold time might not be sufficient time for all devices to receive hello packets from their neighbors. In this case, you may want to increase the hold time. Do not adjust the hold time without advising your technical support personnel. To change the hold time on a specific interface for a particular routing process designated by an autonomous system number, use the hold time command.
You can adjust the interval between hello packets and the hold time. To change the interval between hello packets and the hold time, use the following commands.
DETAILED STEPS
Disabling Split Horizon
When split horizon is enabled on an interface, it blocks route information (such as update and query packets) from being advertised by a device out of any interface from which that information originates. Controlling update and query packets in this manner reduces the possibility of routing loops.
This behavior usually optimizes communications among multiple routing devices, particularly when links are broken. However, with nonbroadcast networks (such as Frame Relay and SMDS), situations can arise for which this behavior is less than ideal. For these situations, including networks in which you have Cisco SAF configured, you may want to disable split horizon.
By default, split horizon is enabled on all interfaces. To disable split horizon, use the no split-horizon command in interface configuration mode.
DETAILED STEPS
Setting Metric Maximum Hops
The maximum number of hops limits the number of hops a service can propagate to advertise its service. The default number of maximum hops is 100.
To limit the number of hops used to advertise a service, use the following commands.
DETAILED STEPS
Configuring a Cisco SAF External Client
To configure a Cisco SAF external client, use the following commands.
DETAILED STEPS
Displaying Cisco SAF Statistics
To display Cisco SAF statistics, use the following commands in privileged EXEC mode.
DETAILED STEPS
| Command or Action | Purpose | |
|---|---|---|
|
|
Example: Device# show service-routing xmcp clients detail |
Displays information about connected XMCP clients. |
|
|
Example: Device# show service-routing xmcp server |
Displays information about clients, external clients, or subscriptions configured for Cisco SAF. |
|
|
Example: Device# show eigrp service-family ipv4 4453 accounting |
Displays accounting information about Cisco SAF. |
|
|
Example: Device# show eigrp service-family ipv4 4453 clients |
Displays information about Cisco SAF Clients. |
|
|
Example: Device# show eigrp service-family ipv4 4453 events |
Displays information about Cisco SAF events. |
|
|
Example: Device# show eigrp service-family ipv4 4453 interfaces |
Displays information about Cisco SAF interfaces. |
|
|
Example: Device# show eigrp service-family ipv4 4453 subscriptions |
Displays information about Cisco SAF subscriptions. |
|
|
Example: Device# show eigrp service-family ipv4 4453 timers |
Displays information about Cisco SAF timers. |
|
|
Example: Device# show eigrp service-family ipv4 4453 summary |
Displays summary information about Cisco SAF. |
|
|
Example: Device# show eigrp service-family ipv4 4453 zero successors |
Displays information about Cisco SAF zero successors. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology |
Displays information about the Cisco SAF topology table. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology active |
Displays only active entries for a Cisco SAF topology table. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology all-links |
Displays all active link entries for a Cisco SAF topology table. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology base clients detail |
Displays all active link entries for a Cisco SAF topology base. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology detail-links |
Specifies all links in the topology table. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology events |
Specifies all events in the topology table. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology pending |
Displays all active entries in the topology table that are waiting either for an update or reply from a neighbor. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology service-type connected |
Displays information about the specified service type for a Cisco SAF topology table. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology sia-events |
Displays logged Stuck in Active (SIA) events in the Cisco SAF topology table. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology sia-statistics 10.10.10.1 |
Displays Stuck in Active (SIA) events for a Cisco SAF topology table. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology summary |
Displays a summary of a Cisco SAF topology table. |
|
|
Example: Device# show eigrp service-family ipv4 4453 topology zero-successors |
Displays information about available services that have zero successors in a Cisco SAF topology table. |
Deleting Information from a Cisco SAF Configuration
To delete service-family information from a Cisco SAF configuration, use the following commands in EXEC mode.
DETAILED STEPS
Configuration Examples for Cisco SAF
- Example: Enabling Cisco SAF
- Examples: Configuring Cisco SAF Interfaces
- Example: Configuring Cisco SAF Topology
- Example: Configuring Cisco SAF Stub Routing
- Example: Configuring Cisco SAF with IP-RIP
- Example: Configuring Cisco SAF with OSPF
- Example: Configuring Cisco SAF with EIGRP
- Example: Configuring Cisco SAF Forwarders Located on Separate LANs
- Example: Configuring a Centralized Cisco SAF Forwarder
- Examples: Configuring a Cisco SAF Client
Example: Enabling Cisco SAF
The following example enters router configuration mode, configures a Cisco SAF forwarder, enables the service-family forwarder process, and configures an autonomous system named 4533.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533
Examples: Configuring Cisco SAF Interfaces
The following example places the device in service-family configuration mode and enables all interfaces.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# sf-interface default Device(config-router-sf-interface)# no shutdown
The following example places the device in service-family configuration mode and enables Ethernet interface 0/0.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# sf-interface ethernet0/0
The following example places the device in service-family configuration mode and enables SAF on all interfaces, except Ethernet0/0 interface.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 3 Device(config-router-sf)# interface default Device(config-router-sf)# sf-interface ethernet0/0 Device(config-router-sf-interface)# shutdown Device(config-router-sf-interface)# end
The following example places the device in service-family configuration mode, enables SAF on Ethernet interfaces 2/0 and 2/1, and disables SAF on all other interfaces.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 2 Device(config-router-sf)# sf-interface default Device(config-router-sf-interface)# shutdown Device(config-router-sf-interface)# sf-interface ethernet2/0 Device(config-router-sf-interface)# no shutdown Device(config-router-sf-interface)# sf-interface ethernet2/1 Device(config-router-sf-interface)# no shutdown Device(config-router-sf-interface)# end
Example: Configuring Cisco SAF Topology
The following examples configures a Cisco SAF topology base.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# sf-interface default Device(config-router-sf-interface)# no shutdown Device(config-router-sf-interface)# topology base
Example: Configuring Cisco SAF Stub Routing
The following examples configures a Cisco SAF forwarder as a stub device.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# eigrp stub connected
Example: Configuring Cisco SAF with IP-RIP
The following configuration example enables Cisco SAF with IP RIP routing on network 10.0.0.0.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# topology base Device(config-router-sf-topology)# exit-sf-topology Device(config-router-sf)# exit-service-family Device(config-router)# router rip Device(config-router)# network 10.0.0.0
Example: Configuring Cisco SAF with OSPF
The following configuration example enables Cisco SAF with OSPF routing on network 10.0.0.0, area 0.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# topology base Device(config-router-sf-topology)# exit-sf-topology Device(config-router-sf)# exit-service-family Device(config-router)# router ospf 787 Device(config-router)# network 10.0.0.0 0.0.0.255 area 0
Example: Configuring Cisco SAF with EIGRP
The following configuration example enables Cisco SAF with EIGRP routing on network 10.0.0.0.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 6476 Device(config-router-sf)# network 10.0.0.0 0.0.0.255 Device(config-router-sf)# topology base Device(config-router-sf-topology)# exit-sf-topology Device(config-router-sf)# exit-service-family Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# topology base
Note |
There is no requirement to run routing over the same interfaces or networks in which services are distributed; however this could lead to services being distributed to areas where reachability is not guaranteed. |
Example: Configuring Cisco SAF Forwarders Located on Separate LANs
The following example configures two Cisco SAF forwarders located on separate LANs.
Note |
Use loopback mode to configure remote neighbors. |
Cisco SAF Forwarder 1
Device(config)# interface loopback1 Device(config-if)# ip address 10.1.1.1 255.255.255.255 Device(config-if)# exit Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 1 Device(config-router-sf)# neighbor 10.2.2.2 loopback1 remote 10
Cisco SAF Forwarder 2
Device(config)# interface loopback1 Device(config-if)# ip address 10.2.2.2 255.255.255.255 Device(config-if)# exit Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 1 Device(config-router-sf)# neighbor 10.1.1.1 loopback1 remote 10
Note |
This example assumes that IP routing is configured between the two devices and that the devices can ping both loopbacks. |
Example: Configuring a Centralized Cisco SAF Forwarder
The following example configures a centralized Cisco SAF forwarder that sends all service advertisements to neighbors on IP addresses 10.4.15.5 and 10.4.15.1.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# sf-interface loopback0 Device(config-router-sf-interface)# no split-horizon Device(config-router-sf-interface)# exit-sf-interface Device(config-router-sf)# topology base Device(config-router-sf-topology)# exit-sf-topology Device(config-router-sf)# neighbor 10.4.15.5 Loopback0 remote 20 Device(config-router-sf)# neighbor 10.4.15.1 Loopback0 remote 20 Device(config-router-sf)# exit-service-family
Examples: Configuring a Cisco SAF Client
The following example configures a Cisco SAF external client named example, with a username of username_example, a password of password_example, and a keepalive setting of 360,000 seconds.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# topology base Device(config-router-sf-topology)# external-client example Device(config-router-sf-topology)# exit-sf-topology Device(config-router-sf)# exit-service-family Device(config-router)# exit Device(config)# service-family external-client listen ipv4 3444 Device(config-external-client)# external-client example Device(config-external-client-mode)# username username_example Device(config-external-client-mode)# password password_example Device(config-external-client-mode)# keepalive 360000
The following example configures five Cisco SAF external clients named example1 through example5, with usernames of username_example1 through username_example5, passwords of password_example1 through password_example5, and keepalive settings of 360,000 seconds.
Device(config)# router eigrp saf Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# topology base Device(config-router-sf-topology)# external-client example1 Device(config-router-sf-topology)# external-client example2 Device(config-router-sf-topology)# external-client example3 Device(config-router-sf-topology)# external-client example4 Device(config-router-sf-topology)# external-client example5 Device(config-router-sf-topology)# exit-sf-topology Device(config-router-sf)# exit-service-family Device(config-router)# exit Device(config)# service-family external-client listen ipv4 3444 Device(config-external-client)# external-client example1 Device(config-external-client-mode)# username username_example1 Device(config-external-client-mode)# password password_example1 Device(config-external-client-mode)# keepalive 360000 Device(config-external-client-mode)# external-client example2 Device(config-external-client-mode)# username username_example2 Device(config-external-client-mode)# password password_example2 Device(config-external-client-mode)# keepalive 360000 Device(config-external-client-mode)# external-client example3 Device(config-external-client-mode)# username username_example3 Device(config-external-client-mode)# password password_example3 Device(config-external-client-mode)# keepalive 360000 Device(config-external-client-mode)# external-client example4 Device(config-external-client-mode)# username username_example4 Device(config-external-client-mode)# password password_example4 Device(config-external-client-mode)# keepalive 360000 Device(config-external-client-mode)# external-client example5 Device(config-external-client-mode)# username username_example5 Device(config-external-client-mode)# password password_example5 Device(config-external-client-mode)# keepalive 360000
Additional References
Related Documents
| Related Topic | Document Title |
|---|---|
| Cisco IOS commands |
|
| Service Advertisement Framework commands |
Cisco IOS Service Advertisement Framework Technology Command Reference |
| Cisco EIGRP stub routing |
Configuring EIGRP |
Technical Assistance
| Description | Link |
|---|---|
| The Cisco Support and Documentation website provides online resources to download documentation, software, and tools. Use these resources to install and configure the software and to troubleshoot and resolve technical issues with Cisco products and technologies. Access to most tools on the Cisco Support and Documentation website requires a Cisco.com user ID and password. |
Feature Information for Cisco SAF
The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
| Table 1 | Feature Information for Cisco Service Advertisement Framework |
| Feature Name |
Software Releases |
Feature Configuration Information |
|---|---|---|
| Cisco Service Advertisement Framework |
12.2(33)SRE 12.2(33)SXI4 12.2(33)XNE 12.2(50)SY 15.0M 15.0(1)S 15.1(1)SG 15.1(2)S 15.1T 15.2(1)T 15.2(2)S 15.2(3)T Cisco IOS XE Release 2.5 Cisco IOS XE Release 3S, Cisco IOS XE Release 3.3SG Cisco IOS XE Release 3.4S Cisco IOS XE Release 3.6S |
This feature allows applications to discover the existence, location, and configuration of networked resources within networks, and it provides a timely and reliable awareness of the services within networks, as applications advertise and discover services on networks. This feature was introduced in Cisco IOS Release 15.0M. In Cisco IOS XE Release 2.5, this feature was introduced on the Cisco ASR 1000 Series Aggregation Services Routers. The following commands were introduced in this feature:
|
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
Feedback