![]() |
Cisco IOS Service Advertisement Framework Command Reference
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
SAF Commands: send-lifetime through username SAF
![]() |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Contents
SAF Commands send-lifetime through username SAF send-lifetimeTo set the time period during which an authentication key on a key chain is valid to be sent, use the send-lifetime command in key chain key configuration mode. To revert to the default value, use the no form of this command.
send-lifetime
start-time
{infinite | end-time | duration seconds}
no send-lifetime
start-time
{infinite | end-time | duration seconds}
Syntax DescriptionCommand History
Usage GuidelinesSpecify a start-time value and one of the following values: infinite, end-time, or duration seconds. We recommend running Network Time Protocol (NTP) or some other time synchronization method if you intend to set lifetimes on keys. If the last key expires, authentication will continue and an error message will be generated. To disable authentication, you must manually delete the last valid key. ExamplesThe following example configures a key chain named chain1. The key named key1 will be accepted from 1:30 p.m. to 3:30 p.m. and be sent from 2:00 p.m. to 3:00 p.m. The key named key2 will be accepted from 2:30 p.m. to 4:30 p.m. and be sent from 3:00 p.m. to 4:00 p.m. The overlap allows for migration of keys or a discrepancy in the set time of the router. There is a 30-minute leeway on each side to handle time differences. Router(config)# interface ethernet 0 Router(config-if)# ip rip authentication key-chain chain1 Router(config-if)# ip rip authentication mode md5 ! Router(config)# router rip Router(config-router)# network 172.19.0.0 Router(config-router)# version 2 ! Router(config)# key chain chain1 Router(config-keychain)# key 1 Router(config-keychain-key)# key-string key1 Router(config-keychain-key)# accept-lifetime 13:30:00 Jan 25 1996 duration 7200 Router(config-keychain-key)# send-lifetime 14:00:00 Jan 25 1996 duration 3600 Router(config-keychain-key)# exit Router(config-keychain)# key 2 Router(config-keychain-key)# key-string key2 Router(config-keychain-key)# accept-lifetime 14:30:00 Jan 25 1996 duration 7200 Router(config-keychain-key)# send-lifetime 15:00:00 Jan 25 1996 duration 3600 The following example configures a key chain named chain1 for EIGRP address-family. The key named key1 will be accepted from 1:30 p.m. to 3:30 p.m. and be sent from 2:00 p.m. to 3:00 p.m. The key named key2 will be accepted from 2:30 p.m. to 4:30 p.m. and be sent from 3:00 p.m. to 4:00 p.m. The overlap allows for migration of keys or a discrepancy in the set time of the router. There is a 30-minute leeway on each side to handle time differences. Router(config)# eigrp virtual-name Router(config-router)# address-family ipv4 autonomous-system 4453 Router(config-router-af)# network 10.0.0.0 Router(config-router-af)# af-interface ethernet0/0 Router(config-router-af-interface)# authentication key-chain trees Router(config-router-af-interface)# authentication mode md5 Router(config-router-af-interface)# exit Router(config-router-af)# exit Router(config-router)# exit Router(config)# key chain chain1 Router(config-keychain)# key 1 Router(config-keychain-key)# key-string key1 Router(config-keychain-key)# accept-lifetime 13:30:00 Jan 25 1996 duration 7200 Router(config-keychain-key)# send-lifetime 14:00:00 Jan 25 1996 duration 3600 Router(config-keychain-key)# exit Router(config-keychain)# key 2 Router(config-keychain-key)# key-string key2 Router(config-keychain-key)# accept-lifetime 14:30:00 Jan 25 1996 duration 7200 Router(config-keychain-key)# send-lifetime 15:00:00 Jan 25 1996 duration 3600 Related Commands
service-familyTo configure virtual routing and forwarding (VRF) metrics for a Cisco SAF service-family, use the service-family command in router configuration mode. To disable the service-family configuration, use the no form of this command.
service-family
{ipv4 | ipv6}
[vrf vrfname]
autonomous-system
autonomous-system number
no service-family
{ipv4 | ipv6}
[vrf vrfname]
autonomous-system
autonomous-system number
Syntax Description
Command History
Usage GuidelinesUse the service-family command to enter service-family configuration mode.
service-family external-client listenTo configure a Cisco SAF External-Client TCP port, use the service-family external-client listencommand in global configuration mode. To remove the associated external-client configuration, use the no form on this command.
service-family
external-client
listen
{ipv4 | ipv6}
tcp-port-number
vrf-name
no
service-family
external-client
listen
Command History
Usage GuidelinesUse the service-family external-client listencommand to configure a TCP port on which the Cisco SAF Forwarder is to listen. The no form of this command removes all clients from the Cisco SAF network, the External-Client database, tears down all sockets, and removes the TCP listen socket.
Use the show eigrp service-family external-client command to verify information on EIGRP external clients. service-routing xmcp listenTo enable XMCP (Extensible Messaging Client Protocol) on a port and to configure parameters for accepting client connections, use the service-routing xmcp listen command in global configuration mode. To disable XMCP on a port, use the no form of this command. Syntax Description
Usage GuidelinesThe service-routing xmcp listen command is used to configure a router to listen for XMCP client connections, optionally under a specific transport protocol. If neither the ipv4 nor the ipv6 keyword is specified, clients are permitted to connect over either protocol. Only a single service-routing xmcp listen command can be configured on a router. Once configured, you can only change this command by configuring the no service-routing xmcp listen command. ExamplesThe following example configures XMCP with its default behavior, which is to accept IPv4 and IPv6 connections over TCP on port 4788: Router(config)# service-routing xmcp listen Router(config-xmcp)# end The following example configures XMCP to accept only client connections using TCP over IPv6 on port 2100: Router(config)# service-routing xmcp listen ipv6 transport tcp port 2100 Router(config-xmcp)# end sf-interfaceTo configure interface-specific commands for a Cisco SAF service family, use the sf-interface command in service-family configuration mode. To disable the service-family mode, use the no form on this command.
sf-interface
{interface-type interface-number | default}
no
sf-interface
{interface-type interface-number | default}
Command History
Usage GuidelinesUse the sf-interface defaultcommand to set the Cisco SAF default configuration for all interfaces on the router. Use the sf-interface interface-type interface-numbercommand to apply a Cisco SAF configuration to a specific interface. Any configuration using this command overrides the default configuration. ExamplesThe following example places a router in service-family configuration mode and enables Ethernet interface 0/0, while disabling all other interfaces: Router(config)# router eigrp virtual-name Router(config-router)# service-family ipv4 autonomous-system 4533 Router(config-router-sf)# sf-interface default Router(config-router-sf-interface)# shutdown Router(config-router-sf-interface)# Ethernet 0/0 Router(config-router-sf-interface)# no shutdown Related Commands
show eigrp pluginsTo display general information including the versions of the Enhanced Interior Gateway Routing Protocol (EIGRP) protocol features that are currently running, use the show eigrp plugins command in user EXEC or privileged EXEC mode. Syntax DescriptionCommand History
Usage GuidelinesUse the show eigrp plugins command in user EXEC or privileged EXEC mode to determine if a particular EIGRP feature is available in your Cisco IOS image. This command displays a summary of information about EIGRP service families and address families. This command is useful when contacting Cisco technical support. ExamplesThe following example shows how to display EIGRP plugin information:
Router# show eigrp plugins
EIGRP feature plugins:::
eigrp-release : 5.00.00 : Portable EIGRP Release
: 19.00.00 : Source Component Release(rel5)
igrp2 : 3.00.00 : Reliable Transport/Dual Database
bfd : 1.01.00 : BFD Platform Support
mtr : 1.00.01 : Multi-Topology Routing(MTR)
eigrp-pfr : 1.00.01 : Performance Routing Support
ipv4-af : 2.01.01 : Routing Protocol Support
ipv4-sf : 1.01.00 : Service Distribution Support
external-client : 1.02.00 : Service Distribution Client Support
ipv6-af : 2.01.01 : Routing Protocol Support
ipv6-sf : 1.01.00 : Service Distribution Support
snmp-agent : 1.01.01 : SNMP/SNMPv2 Agent Support
The table below describes the significant fields shown in the display.
Related Commands
show eigrp protocolsTo display general information about Enhanced Interior Gateway Routing Protocol (EIGRP) protocols that are currently running, use the show eigrp protocols command in user EXEC or privileged EXEC mode. Command History
Usage GuidelinesUse the show eigrp protocolscommand in user EXEC or privileged EXEC mode to see a summary of information on EIGRP IPv4 service families or address families. ExamplesThe following example shows how to display general EIGRP information:
Router# show eigrp protocols
EIGRP-IPv4 Protocol for AS(10)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 1.1.1.1
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170
Maximum path: 4
Maximum hopcount 100
Maximum metric variance 1
EIGRP-IPv4 Protocol for AS(5) VRF(red)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 1.1.1.1
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170
Maximum path: 4
Maximum hopcount 100
Maximum metric variance 1
Total Prefix Count: 0
Total Redist Count: 0
The following example shows how to display general EIGRP information for VRF1:
Router# show eigrp protocols vrf vrf1
EIGRP-IPv4 Protocol for AS(5) VRF(vrf1)
Metric weight K1=1, K2=0, K3=1, K4=0, K5=0
NSF-aware route hold timer is 240
Router-ID: 1.1.1.1
Topology : 0 (base)
Active Timer: 3 min
Distance: internal 90 external 170
Maximum path: 4
Maximum hopcount 100
Maximum metric variance 1
Total Prefix Count: 0
Total Redist Count: 0
The table below describes the significant fields shown in the display.
Related Commands
show eigrp service-family external-clientTo display information about Cisco Service Advertisement Framework (Cisco SAF) external clients, use the show eigrp service-family external-clientcommand in user EXEC or privileged EXEC mode. Command History
Usage GuidelinesUse the show eigrp service-family external-clientcommand in user or privileged EXEC mode to see a summary of the information about Cisco SAF external clients that are currently registered with the Cisco SAF system. ExamplesThe following is sample output from the show eigrp service-family external-clientcommand if any clients are registered:
Router# show eigrp service-family external-client
SAF External Clients
example-using-basename (basename)
Client Socket Keep Address Port Tag
Handle FD (ms)
1 1 3268319 10.1.1.1 47519 @12
2 2 3268347 192.168.100.101 36997 @1
example-configured-but-no-clients-connected
No connected clients
example-client-without-basename
Client Socket Keep Address Port Tag
Handle FD (ms)
3 3 208373 10.1.1.2 51294 --
The table below describes the significant fields shown in the display.
The following is sample output from the show eigrp service-family external-client client-labelcommand if the specified client is registered:
Router# show eigrp service-family external-client example-using-basename@12
SAF External Client "example-using-basename" (basename)
Listening on port 1024, keepalive time 3600000 ms
VR(saf) SFv4 AS(1) Topology(base)
Client Socket Keep Address Port Tag
Handle FD (ms)
1 1 3322871 10.1.1.1 47519 @12
Client name "thisistheclientnameweprovided"
Page size 1, currently allowed to send 1
Protocol version 1.0
2 subscriptions
The table below describes the significant fields shown in the display.
Related Commands
show eigrp service-family ipv4 topologyTo display topology information for an Enhanced Interior Gateway Routing Protocol (EIGRP) IPv4 service family, use the show eigrp service-family ipv4 topologycommand in user EXEC or privileged EXEC mode. show eigrp service-family ipv4 [vrf vrf-name] autonomous-system-number topology [service-instance-number | active | all-links | detail-links | pending service-type [connected | external | internal | local | redistributed | summary] | summary | zero-successors]
Syntax Description
Command History
Usage GuidelinesUse the show eigrp service-family ipv4 topologycommand in user EXEC or privileged EXEC mode to see a summary of information on EIGRP IPv4 service-families services. ExamplesThe following is sample output from the show eigrp service-family ipv4 topology command: Router> enable Router# show eigrp service-family ipv4 4453 topology EIGRP-SFv4 Topology Table for process 4453 Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - Reply status P 1:2:0.0.0.3, 2 successors, FD is 0 via 10.16.80.28 (46251776/46226176), Ethernet0 via 10.16.81.28 (46251776/46226176), Ethernet1 via 10.16.80.31 (46277376/46251776), Serial0 P 4:5:0.0.0.6, 1 successors, FD is 37200 via Connected, Ethernet1 via 10.16.81.28 (307200/281600), Ethernet1S via 10.16.80.28 (307200/281600), Ethernet0 via 10.16.80.31 (332800/307200), Serial0 The following is sample output from the show eigrp service-family ipv4 topology command for a specified service: Router> enable Router# show eigrp service-family ipv4 4453 topology 1:2:0.0.0.3 EIGRP-SFv4 VR(example) Topology Table entry for AS(4453)/ID(10.1.1.1)1:2:0.0.0.3 State is Passive, Query origin flag is 1, 1 Successor(s), FD is 409600 Service Description Blocks: 1:2:3.0.0.0.3 (Ethernet0/0), from 10.2.1.1, Send flag is 0x0 Composite metric is (409600/128256), Route is External Vector metric: Minimum bandwidth is 10000 Kbit Total delay is 6000 microseconds Reliability is 255/255 Load is 1/255 Minimum MTU is 1500 Hop count is 1 External data: Originating router is 10.89.245.1 AS number of route is 0 External protocol is Connected, external metric is 0 Administrator tag is 0 (0x00000000) Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - Reply status P 1:2:0.0.0.3, 2 successors, FD is 0 via 10.16.80.28 (46251776/46226176), Ethernet0 via 10.16.81.28 (46251776/46226176), Ethernet1 via 10.16.80.31 (46277376/46251776), Serial0 P 4:5:0.0.0.6, 1 successors, FD is 37200 via Connected, Ethernet1 via 10.16.81.28 (307200/281600), Ethernet1S via 10.16.80.28 (307200/281600), Ethernet0 via 10.16.80.31 (332800/307200), Serial0 The table below describes the significant fields shown in the show eigrp service-family ipv4 topologycommand output.
Related Commands
show eigrp service-family ipv6 topologyTo display topology information for an Enhanced Interior Gateway Routing Protocol (EIGRP) IPv6 service family, use the show eigrp service-family ipv6 topologycommand in user EXEC or privileged EXEC mode. show eigrp service-family ipv6 [vrf vrf-name] autonomous-system-number topology [service-instance-number | active | all-links | detail-links | pending service-type [connected | external | internal | local | redistributed | summary] | summary | zero-successors]
Syntax Description
Command History
Usage GuidelinesUse the show eigrp service-family ipv6 topologycommand in user EXEC or privileged EXEC mode to see a summary of information on EIGRP IPv6 service-family topology services.
ExamplesThe following is sample output from the show eigrp service-family ipv6 topology command: Router> enable Router# show eigrp service-family ipv6 4453 topology EIGRP-SFv4 Topology Table for process 4453 Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - Reply status P 1:2:0.0.0.3, 2 successors, FD is 0 via 10.16.80.28 (46251776/46226176), Ethernet0 via 10.16.81.28 (46251776/46226176), Ethernet1 via 10.16.80.31 (46277376/46251776), Serial0 P 4:5:0.0.0.6, 1 successors, FD is 37200 via Connected, Ethernet1 via 10.16.81.28 (307200/281600), Ethernet1S via 10.16.80.28 (307200/281600), Ethernet0 via 10.16.80.31 (332800/307200), Serial0 The following is sample output from the show eigrp service-family ipv6 topology command for a specified service: Router> enable Router# show eigrp service-family ipv6 4453 topology 1:2:0.0.0.3 EIGRP-SFv4 VR(example) Topology Table entry for AS(4453) State is Passive, Query origin flag is 1, 1 Successor(s), FD is 409600 Service Description Blocks: 1:2:3.0.0.0.3 (Ethernet0/0), from 10.2.1.1, Send flag is 0x0 Composite metric is (409600/128256), Route is External Vector metric: Minimum bandwidth is 10000 Kbit Total delay is 6000 microseconds Reliability is 255/255 Load is 1/255 Minimum MTU is 1500 Hop count is 1 External data: Originating router is 10.89.245.1 AS number of route is 0 External protocol is Connected, external metric is 0 Administrator tag is 0 (0x00000000) Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - Reply status P 1:2:0.0.0.3, 2 successors, FD is 0 via 10.16.80.28 (46251776/46226176), Ethernet0 via 10.16.81.28 (46251776/46226176), Ethernet1 via 10.16.80.31 (46277376/46251776), Serial0 P 4:5:0.0.0.6, 1 successors, FD is 37200 via Connected, Ethernet1 via 10.16.81.28 (307200/281600), Ethernet1S via 10.16.80.28 (307200/281600), Ethernet0 via 10.16.80.31 (332800/307200), Serial0 The table below describes the significant fields shown in the show eigrp service-family ipv6 topologycommand output.
Related Commands
show eigrp tech-supportTo generate a report of the Enhanced Interior Gateway Routing Protocol (EIGRP) internal state information, use the show eigrp tech-support command in privileged EXEC mode. Command History
Usage GuidelinesUse the show eigrp tech-support command in privileged EXEC mode to display various internal EIGRP states.
ExamplesThe following is sample output from the show eigrp tech-support detailed command:
Router# show eigrp tech-support detailed
EIGRP feature plugins:::
eigrp-release : 8.00.00 : Portable EIGRP Release
: 3.00.21 : Source Component Release(dev8)
+ HMAC-SHA-256 Authentication
parser : 2.02.00 : EIGRP Parser Support
igrp2 : 2.00.00 : Reliable Transport/Dual Database
+ Wide Metrics
eigrp-nsf : 2.00.00 : Platform Support
bfd : 1.01.00 : BFD Platform Support
mtr : 1.00.01 : Multi-Topology Routing(MTR)
eigrp-pfr : 1.00.01 : Performance Routing Support
+ IPv4 PFR
EVN/vNets : 1.00.00 : Easy Virtual Network (EVN/vNets)
+ IPv4 EVN/vNets
ipv4-af : 2.01.01 : Routing Protocol Support
ipv4-sf : 1.02.00 : Service Distribution Support
+ Dynamic Remote Neighbors
ipv6-af : 2.01.01 : Routing Protocol Support
+ IPv6 VRF
ipv6-sf : 2.01.00 : Service Distribution Support
+ Dynamic Remote Neighbors
+ IPv6 VRF
vNets-parse : 1.00.00 : EIGRP vNets Parse Support
snmp-agent : 1.01.01 : SNMP/SNMPv2 Agent Support
EIGRP Internal Process States
procinfoQ:
1: 0x1FC6EB4C vrid:0 afi:1 as:46 tableid:0 vrfid:0 tid:0 name:virtual-name
topo_ddbQ(1) 0x1FCC478C tableid:0 name:base
topo_ddbQ.count: 1
procinfoQ.count: 1
deadQ:
ddbQ:
1: 0x1FCC478C name:base
ddbQ.count: 1
---------------------------------------------------------
EIGRP Memory Usage:
EIGRP Memory In-use Asked-For/Allocated Count Size Cfg/Max
----------------------------------------------------------------------------
EIGRP IP pdb : 8216 8216/8268 1 8216 --/--
EIGRP-Core: DDB : 2440 2440/2492 1 2440 --/--
EIGRP-Core: Dual Events : 30000 30000/30052 1 30000 --/--
EIGRP-Core: IIDB : 928 928/980 1 928 --/--
EIGRP-Core: IIDB Scratc : 24 24/76 1 24 --/--
EIGRP-Core: Peer Handle : 76 76/180 2 38 --/--
EIGRP-Core: Peer Sub-To : 32 32/84 1 32 --/--
EIGRP-Core: Topology II : 104 104/156 1 104 --/--
EIGRP-IPv4: Proto Priva : 24 24/76 1 24 --/--
EIGRP-IPv4: Protocol In : 3464 3464/3516 1 3464 --/--
EIGRP-IPv4: VR-Router : 32 32/84 1 32 --/--
EIGRP-Parser: dBase Hdr : 1740 1740/2052 6 290 --/--
EIGRP-v4: Work Entry : -- 4260/4728 -- 60 50/71
EIGRP: Anchor entries : -- 7404/10052 -- 12 500/617
EIGRP: Dummy thread ent : -- 8892/10052 -- 36 200/247
EIGRP: ExtData : -- 1320/1708 -- 24 50/55
EIGRP: Input packet hea : -- 2304/3052 -- 16 100/144
EIGRP: Large packet buf : -- 57512/65588 -- 8216 100/7
EIGRP: List Large : -- 1332/1552 -- 148 5/9
EIGRP: List Medium : -- 1296/1604 -- 72 10/18
EIGRP: Max packet buffe : -- 49224/65588 -- 16408 5/3
EIGRP: Medium packet bu : -- 64856/65588 -- 536 100/121
EIGRP: Packet descripto : -- 4260/4728 -- 60 50/71
EIGRP: Queue elements : -- 11788/13640 -- 28 200/421
EIGRP: Small Pool : 32 624/956 2 16 32/39
EIGRP: Small packet buf : -- 4444/5052 -- 44 100/101
EIGRP: cmd handles : 56 56/160 2 28 --/--
EIGRP: mgd_timer : 1600 1600/2640 20 80 --/--
Total : 48768 268252/304704 42 -- --/--
Total allocated: 0.290 Mb, 297 Kb, 304704 bytes
---------------------------------------------------------
EIGRP-IPv4 VR(virtual-name) Address-Family Protocol for AS(46)
{vrid:0 afi:1 as:46 mode:3 tableid:0 vrfid:0 tid:0 name:virtual-name }
PIDs: Hello: (no process) PDM: (no process)
Router-ID: 10.4.9.87
Threads: procinfo: 0x1FC72E58 ddb: 0x1FC73050
workQ:
iidbQ:
passive_iidbQ:
peerQ:
unicast_peerQ:
suspendQ:
networkQ:
RedistStructs: src:(0)default distflag:0x4 ipdb->pdb->mask:0x4
count: 1
summaryQ:
Socket Queue: %EIGRP(ERROR): invalid socket
Input Queue: 0/2000/0/0 (current/max/highest/drops)
GRS/NSF: enabled hold-timer: 240
Active Timer: 3 min
Distance: internal 90 external 170
Max Path: 4
Max Hopcount: 100
Variance: 1
Rib-scale: 1
Metric Ver: 32bit
-------------------------------------------------------------------
show service-routing capabilities-managerTo display information about registered capabilities, use the show service-routing capabilities-manager command in user EXEC or privileged EXEC mode. ExamplesThe following example shows how to display information about all registered capabilities and groups 1 (Hardware) and 2 (Software):
Router# show service-routing capabilities-manager
Router# show service-routing capabilities-manager
Service-Routing Capabilities Manager
====================================
Registered Capabilities
=======================
Group/ID: HARDWARE/1
Service: 100:1:31343134.34333137.32000000.0
Originator: 1.1.1.1
Capability Data:
<Capabilities>
<Group Name="HARDWARE">
<Capability Name="HostName">
<Value>R100</Value>
</Capability>
<Capability Name="Platform">
<Value>Solaris Unix (Sparc) processor</Value>
</Capability>
<Capability Name="MainMemorySize">
<Value>63682Kbytes</Value>
</Capability>
</Group>
</Capabilities>
Group/ID: SOFTWARE/2
Service: 100:2:31343134.34333137.32000000.0
Originator: 1.1.1.1
Capability Data:
<Capabilities>
<Group Name="SOFTWARE">
<Capability Name="HostName">
<Value>R100</Value>
</Capability>
<Capability Name="Software">
<Value>Cisco IOS Software</Value>
</Capability>
<Capability Name="Image">
<Value> Solaris Software (UNIX-ADVENTERPRISE-M)</Value>
</Capability>
<Capability Name="Version">
<Value> Experimental Version 15.1(20110404:193816) </Value>
</Capability>
<Capability Name="ipmulticast">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="eigrp_ipv4">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="eigrp_ipv6">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="ospf">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="ospfv3">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="isis">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="isis_ipv6">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="bgp_ipv4">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="bgp_ipv6">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="fh_fd_ipsla">
<Value>Subsystem Loaded</Value>
</Capability>
<Capability Name="service_routing">
<Value>Subsystem Loaded</Value>
</Capability>
</Group>
</Capabilities>
The following example shows how to display information for only the local router and for only group 1 (Hardware):
Router# show service-routing capabilities-manager group 1 local
Service-Routing Capabilities Manager
====================================
Registered Capabilities
=======================
Group/ID: HARDWARE/1
Service: 100:1:31343134.34333137.32000000.0
Originator: 1.1.1.1
Capability Data:
<Capabilities>
<Group Name="HARDWARE">
<Capability Name="HostName">
<Value>R100</Value>
</Capability>
<Capability Name="Platform">
<Value>Solaris Unix (Sparc) processor</Value>
</Capability>
<Capability Name="MainMemorySize">
<Value>63682Kbytes</Value>
</Capability>
</Group>
</Capabilities>
The table below describes the significant fields shown in the display.
show service-routing capabilities-manager internalTo display information about Capabilities Manager, use the show service-routing capabilities-manager internal command in user EXEC or privileged EXEC mode. Usage GuidelinesUse the show service-routing capabilities-manager internal command in user or privileged EXEC mode to see a summary of the information about Cisco SAF external clients that are currently registered with the Cisco SAF system. ExamplesThe following is sample output from the show service-routing capabilities-manager internal command.
Router# show service-routing capabilities-manager internal
Service-Routing Capabilities Manager
====================================
Major Version: 1 Minor Version: 0 Edit Version: 0
Reachability: 2.2.2.2:0
Local Instance GUID: 31343134-3433-3137-3200-000000000000
The table below describes the significant fields shown in the display.
show service-routing plugins capmanTo display Capabilities Manager plugin information, use the show service-routing plugins capman command in user EXEC or privileged EXEC mode. Usage GuidelinesUse the show service-routing plugins capman command in user or privileged EXEC mode to determine if SAF and Capabilities Manager are available. When Capabilities Manager is available, the version is also displayed. show service-routing xmcp clientsTo display information about connected XMCP (Extensible Messaging Client Protocol) clients, use the show service-routing xmcp clients command in user EXEC or privileged EXEC mode. Syntax Description
Usage GuidelinesThe show service-routing xmcp clients command is used to display detailed information about currently connected XMCP clients. Include an IP address to show a single client. Include the detail keyword to display additional information. ExamplesThe following is sample output from the show service-routing xmcp clients command:
Router# show service-routing xmcp clients
XMCP Clients
Codes: A - Authenticated, T - TCP
Handle Address Port Keepalive
AT 1 10.1.1.1 47519 24/30
Client name: UCM/CM_ccmbeijing/NodeId=1/8.5.1.10000-26
23 2001:0DB8:E123:1000:3615:9EFF:FE0B:AFA4 3478 3120/3600
Client name: CapMan Viewer/glmatthe-mac.example.com/Mac OS X 10.6.6 (10J567)
The following is sample output from the show service-routing xmcp clients detail command:
Router# show service-routing xmcp clients detail
XMCP Clients
Codes: A - Authenticated, T - TCP
Handle Address Port Keepalive
AT 1 10.1.1.2 47532 22/30
Client name: UCM/CM_ccmbeijing/NodeId=1/8.5.1.10000-26
XMCP version: 1.0
Page-size: 5 (11/5 requests enqueued/awaiting response)
Username: CUCM_CLIENT
Socket FD: 1
Domain: 100
Nonce: lifetime 51/800 seconds
23 2001:0DB8:E123:1000:3615:9EFF:FE0B:AFA4 3478 3120/3600
Client name: CapMan Viewer/glmatthe-mac.example.com/Mac OS X 10.6.6 (10J567)
XMCP version: 2.0
Page-size: 3 (0/2 requests enqueued/awaiting response)
Socket FD: 2
Domain: 123
Nonce: none
The table below describes the significant fields shown in the display.
show service-routing xmcp serverTo display information about the XMCP (Extensible Messaging Client Protocol) server status, use the show service-routing xmcp server command in user EXEC or privileged EXEC mode. Usage GuidelinesThe show service-routing xmcp server command displays an overview of the XMCP server configuration and status. For more detailed information about individual XMCP client sessions, use the show service-routing xmcp clients command. ExamplesThe following is sample output from the show service-routing xmcp server command:
Router# show service-routing xmcp server
XMCP Server listening on port 4788
Socket descriptors: 0 (TCP/IPv4), 1 (TCP/IPv6)
Connected clients: 1 unauthenticated, 2 total
Maximum clients: 5 unauthenticated, 10 total
Allow-lists: "v4nacl" (IPv4), "naclv6" (IPv6)
Clients configured:
Username "a", 1 client(s) connected
Unauthenticated, 1 client(s) connected
The table below describes the significant fields shown in the display.
split-horizon (EIGRP)To enable Enhanced Interior Gateway Routing Protocol (EIGRP) split-horizon, use the split-horizon command in address-family interface configuration mode or service-family interface configuration mode. To disable EIGRP split-horizon, use the no form of this command. Command DefaultEIGRP split-horizon is enabled by default. However, for ATM interfaces and subinterfaces split-horizon is disabled by default. Command ModesAddress-family interface configuration (config-router-af-interface) Service-family interface configuration (config-router-sf-interface) Command History
Usage GuidelinesThe split-horizon rule prohibits a router from advertising a route through an interface that the router itself uses to reach the destination. The following are general rules for EIGRP split-horizon:
To configure split-horizon for an EIGRP address family, use the split-horizoncommand in address-family interface configuration mode. To configure split-horizon for an EIGRP service family, use the split-horizoncommand in service-family interface configuration mode. ExamplesThe following example disables EIGRP split-horizon for serial interface 3/0 in address-family 5400: Router(config)# router eigrp virtual-name Router(config-router)# address-family ipv4 autonomous-system 5400 Router(config-router-af)# af-interface serial3/0 Router(config-router-af-interface)# no split-horizon The following example disables EIGRP split-horizon for serial interface 3/0 in service-family 5400: Router(config)# router eigrp virtual-name Router(config-router)# service-family ipv4 autonomous-system 5400 Router(config-router-sf)# sf-interface serial3/0 Router(config-router-sf-interface)# no split-horizon Related Commands
timers graceful-restart purge-timeTo set the graceful-restart purge-time timer to determine how long a nonstop forwarding (NSF)-aware router that is running the Enhanced Interior Gateway Routing Protocol (EIGRP) must hold routes for an inactive peer, use the timers graceful-restart purge-time command in router configuration, address family configuration, or service-family configuration mode. To return the graceful-restart purge-time timer to the default value, use the no form of this command. Command ModesRouter configuration (config-router) Address family configuration (config-router-af) Service-family configuration (config-router-sf) Command History
Usage GuidelinesThe graceful-restart purge-time timer sets the maximum period of time for which the NSF-aware router must hold known routes for an NSF-capable neighbor during a switchover operation or a well-known failure condition. The graceful-restart purge-time timer is configurable so that you can tune network performance and avoid undesired effects, such as "black holing" routes if the switchover operation takes too much time. When this timer expires, the NSF-aware router scans the topology table and discards any stale routes, allowing EIGRP peers to find alternate routes instead of waiting during a long switchover operation.
ExamplesThe following example shows how to set the graceful-restart purge-time timer to 60 seconds for an NSF-aware IPv4 address family: Device(config)# router eigrp virtual-name Device(config-router)# address-family ipv4 autonomous-system 1 Device(config-router-af)# timers graceful-restart purge-time 60 The following example shows how to set the graceful-restart purge-time timer to 300 seconds for an NSF-aware-service family configuration: Device(config)# router eigrp virtual-name Device(config-router)# service-family ipv4 autonomous-system 4533 Device(config-router-sf)# timers graceful-restart purge-time 300 The following example shows how to set the graceful-restart purge-time timer to 200 seconds for an NSF-aware IPv6 address family configuration: Device(config)# router eigrp e1 Device(config-router)# address-family ipv6 autonomous-system 4 Device(config-router-af)# timers graceful-restart purge-time 300 Related Commands
topologyTo configure topology-specific commands for an Enhanced Interior Gateway Routing Protocol (EIGRP) service family, use the topologycommand in service-family interface configuration mode. To disable the service-family topology configuration mode, use the no form of this command. Command History
Usage GuidelinesUse the topologycommand to configure Cisco SAF for multitopology networks.
Use the show eigrp service-family ipv4 topologycommand to verify the topology base configuration. ExamplesThe following example configures the base topology: Router(config)# router eigrp virtual-name Router(config-router)# service-family ipv4 autonomous-system 4533 Router(config-router-sf)# sf-interface default Router(config-router-sf-interface)# no shutdown Router(config-router-sf-interface)# exit -sf-interface Router(config-router-sf)# topology base Related Commands
username (SAF)To configure username for a Cisco SAF External-Client, use the usernamecommand in external-client label configuration mode. To negate the username, use the no form of this command. Command History
Usage GuidelinesUse the usernamecommand to configure Cisco SAF External Clients. Entering a new username value overwrites the old value, but the new value will only take affect after the Cisco SAF External Client re-registers. Use the show eigrp service-family ipv4 external-clientcommand to verify the Cisco SAF External Client configuration. © 2012 Cisco Systems, Inc. All rights reserved.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|