3-101
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
OL-21483-02
Chapter 3 Troubleshooting Forwarding
Troubleshooting the Interface Manager
Troubleshooting the Client for the Interface Manager
A client must be connected to use any of the IM services. If the client is an owner of the nodes in the IM
or is registered for the notifications with the IM, the client must specify a callback handle. The show im
client command is used to find which clients are connected and have registered callback handles.
Note The context is a unique parameter that the IM uses to identify a client and the registration. The IM is
allowed to know when a client has reconnected to the IM after a process restart. Because the IM tracks
the client’s status, the show im client command is also used to display which clients have previously
connected to the IM. If there is no connection, the status is dead.
The following sample output from the show im client command shows which clients are connected:
RP/0/RP0/CPU0:router# show im client info
INTERFACE MANAGER ACTIVITY CLIENT-INFO
--------------------------------------
Process PID JID Context Status Handle
-------------------- ------- ------- ----------------------- ------- ----------
pfi_ifh_server 53321 246 pfi_ifh alive 0x30000001
sysldr 53297 287 slr_im_evc alive 0x30000002
driver_infra_partner 24603 54 di-node0_0_CPU0-2 alive 0x30000003
ether_caps_partner 61515 154 ether alive 0x30000004
qos_ma 61517 254 qos_ma alive 0x30000005
driver_infra_partner 24603 54 caps_netio_0 alive 0x30000006
aib 61520 100 aib alive 0x30000007
ipv4_fib_mgr 61525 188 ipv4_fib_cfg_im_connect alive 0x30000008
arp 61522 102 arp alive 0x30000009
arp 61522 102 arp_ipv4_caps_reg alive 0x3000000a
ipv4_io 65623 189 ipv4 alive 0x3000000b
ntpd 65632 192 ntpv4 alive 0x3000000c
cdp 65633 125 cdp alive 0x3000000d
cdp 65633 125 cdp_caps alive 0x3000000e
mpls_lfd 65631 227 mpls_lfd alive 0x3000000f
tcp 65640 294 tcp alive 0x30000010
clns 65643 130 clns_transport alive 0x30000011
parser_server 65657 244 parser alive 0x30000012
bundlemgr_distrib 65653 124 BM-DISTRIB_LOCAL alive 0x30000013
nd_partner 65671 235 Null0 alive 0x30000014
ipv6_io 65670 202 ipv6-fint alive 0x30000015
null_caps_partner 69770 239 null_caps_partner alive 0x30000016
ipv6_nd 65672 204 ipv6-nd alive 0x30000017
ipv6_grp 69785 201 ipv6-grp alive 0x30000018
mpls_lsd 69788 229 mpls_lsd alive 0x30000019
fint_partner 53302 157 FINT alive 0x30000000
Troubleshooting the Rules for the Interface Manager
A process that calls the IM to create an interface or add a capsulation is defined as an owner. The owners
own sets of triplets from an interface, protocol, or capsulation. The triplets are secure domain router
(SDR) unique identifiers to control the nodes.
The interface handle is displayed in hexadecimal and contains platform-specific mapping for the node
ID, virtual bit, and interface instance number for the node ID.
To Next Page
Loading...
Need help?
General
