Configuring Capabilities Manager

Capabilities Manager only discovers whether a capability is supported on the local system. It does not discover whether the capability is configured or enabled or discover any other information about the capability for other routers in the network.

Capabilities information will be installed into the local Network Information Base (NIB) as service routing data and made available for advertisement by any SAF Forwarder to the Service Routing network. Capabilities information is passed to the Service Routing infrastructure in XML format and stored in the local NIB.

Capabilities Manager does not advertise capabilities information to the Service Routing network. A SAF Forwarder performs the functions to distribute capabilities information. However, a SAF Forwarder is not required for Capabilities Manager to function. If a SAF Forwarder is not configured, the capabilities information is bound to the local router and is not distributed to other routers in the network. When a SAF Forwarder is configured, it will distribute all capabilities information by default.

Capabilities information is installed in the Network Information Base (NIB) as service routing data. It is identified by a SAF address in the form of:

• service ID--Capabilities Manager uses service ID 100.
• subservice ID--Capability group ID. The subservice ID indicates the group ID of the capabilities data type.
• Instance number--Unique identifier for the local router. It is assigned in order of the hardware serial number, default MAC address, IPv4 router ID, or IPv6 router ID.

Capabilities Manager classifies capabilities by group to facilitate query and retrieval, and assigns each group a unique ID. Capabilities Manager provides the following capability groups:

• 1 (HARDWARE)
• 2 (SOFTWARE)

• Hardware Group Information
• Software Group Information

If you have an Extensible Messaging Client Protocol (XMCP) client (external client) connected to a SAF Forwarder, you can subscribe to the Capabilities Manager, which is service ID 100. The data can be interpreted using the following XML schema:

<?xml version="1.0" encoding="UTF-8"?>

<xs:schema xmlns:xs='http://www.w3.org/2001/XMLSchema'>

<xs:element name="Capabilities" type="CapabilitiesType" />

<xs:complexType name="CapabilitiesType">

<xs:sequence>

<xs:element ref="Group" minOccurs="1" maxOccurs="unbounded" />

</xs:sequence>

</xs:complexType>

<xs:element name="Group" type="GroupType" />

<xs:complexType name="GroupType">

<xs:sequence>

<xs:element ref="Capability" minOccurs="1" maxOccurs="unbounded" />

</xs:sequence>

<xs:attribute name="Name" type="xs:normalizedString" use="required" />

</xs:complexType>

<xs:element name="Capability" type="CapabilityType" />

<xs:complexType name="CapabilityType">

<xs:sequence>

<xs:element name="Value" type="xs:normalizedString" />

</xs:sequence>

<xs:attribute name="Name" type="xs:normalizedString" use="required" />

</xs:complexType>

</xs:schema>

Example:

<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>63683Kbytes</Value>

</Capability>

</Group>

<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(20110323:093227)</Value>

</Capability>

<Capability Name="ipmulticast">

<Value>Subsystem loaded</Value>

</Capability>

<Capability Name="eigrp_ipv4">

<Value>Subsystem loaded</Value>

</Capability>

</Group>

</Capabilities>

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    no service-routing capabilities-manager

4.    service-routing capabilities-manager

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	no service-routing capabilities-manager Example: Router(config)# no service-routing capabilities-manager	Disables Capabilities Manager.
Step 4	service-routing capabilities-manager Example: Router(config)# service-routing capabilities-manager	Enables Capabilities Manager.

SUMMARY STEPS

1.    show service-routing plugins capman

2.    show service-routing capabilities-manager internal

3.    show service-routing capabilities-manager [group value] [local]

DETAILED STEPS

	Command or Action	Purpose
Step 1	show service-routing plugins capman Example: Router> show service-routing plugins capman	Displays information about Capabilities Manager plugins.
Step 2	show service-routing capabilities-manager internal Example: Router# show service-routing capabilities-manager internal	Displays information about Capabilities Manager.
Step 3	show service-routing capabilities-manager [group value] [local] Example: Router# show service-routing capabilities-manager group 1 local	Displays information about registered capabilities.

SUMMARY STEPS

1.    enable

2.    configure terminal

3.    clear service-routing capabilities-manager

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	clear service-routing capabilities-manager Example: Router(config)# clear service-routing capabilities-manager	Clears the current capabilities information from the NIB database. Capabilities Manager will automatically rediscover new capabilities.