Troubleshooting The Client For The Interface Manager; Troubleshooting The Rules For The Interface Manager - Cisco CRS-1 - Carrier Routing System Router Troubleshooting Manual

Ios xr troubleshooting guide
Hide thumbs Also See for CRS-1 - Carrier Routing System Router:
Table of Contents

Advertisement

Chapter 3
Troubleshooting Forwarding

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
-------------------- ------- ------- ----------------------- ------- ----------
pfi_ifh_server
sysldr
driver_infra_partner
ether_caps_partner
qos_ma
driver_infra_partner
aib
ipv4_fib_mgr
arp
arp
ipv4_io
ntpd
cdp
cdp
mpls_lfd
tcp
clns
parser_server
bundlemgr_distrib
nd_partner
ipv6_io
null_caps_partner
ipv6_nd
ipv6_grp
mpls_lsd
fint_partner

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.
OL-21483-02
PID
JID
Context
53321
246 pfi_ifh
53297
287 slr_im_evc
24603
54 di-node0_0_CPU0-2
61515
154 ether
61517
254 qos_ma
24603
54 caps_netio_0
61520
100 aib
61525
188 ipv4_fib_cfg_im_connect alive
61522
102 arp
61522
102 arp_ipv4_caps_reg
65623
189 ipv4
65632
192 ntpv4
65633
125 cdp
65633
125 cdp_caps
65631
227 mpls_lfd
65640
294 tcp
65643
130 clns_transport
65657
244 parser
65653
124 BM-DISTRIB_LOCAL
65671
235 Null0
65670
202 ipv6-fint
69770
239 null_caps_partner
65672
204 ipv6-nd
69785
201 ipv6-grp
69788
229 mpls_lsd
53302
157 FINT
Cisco IOS XR Troubleshooting Guide for the Cisco CRS-1 Router
Troubleshooting the Interface Manager
Status
Handle
alive
0x30000001
alive
0x30000002
alive
0x30000003
alive
0x30000004
alive
0x30000005
alive
0x30000006
alive
0x30000007
0x30000008
alive
0x30000009
alive
0x3000000a
alive
0x3000000b
alive
0x3000000c
alive
0x3000000d
alive
0x3000000e
alive
0x3000000f
alive
0x30000010
alive
0x30000011
alive
0x30000012
alive
0x30000013
alive
0x30000014
alive
0x30000015
alive
0x30000016
alive
0x30000017
alive
0x30000018
alive
0x30000019
alive
0x30000000
3-101

Advertisement

Table of Contents

Troubleshooting

loading

Table of Contents