1datadm(1M)              System Administration Commands              datadm(1M)
2
3
4

NAME

6       datadm - maintain DAT static registry file
7

SYNOPSIS

9       /usr/bin/datadm [-v] [-u] [-a service_provider.conf]
10            [-r service_provider.conf]
11
12

DESCRIPTION

14       The datadm utility maintains the DAT static registry file, dat.conf(4).
15
16
17       This   administrative   configuration   program  allows  uDAPL  service
18       providers to add and remove themselves to the dat.conf file.
19
20
21       You can add or remove interface adapters that a service  provider  sup‐
22       ports  from  a  system  after  its  installation. You can use datadm to
23       update the dat.conf file to reflect the current state of the system.  A
24       new  set  of interface adapters for all the service providers currently
25       installed is regenerated.
26

OPTIONS

28       The following options are supported:
29
30       -a service_provider.conf    Enumerate each device  entry  in  the  ser‐
31                                   vice_provider.conf(4)  file  into a list of
32                                   interface adapters, that is, interfaces  to
33                                   external  network  that  are  available  to
34                                   uDAPL consumers.
35
36
37       -r service_provider.conf    Remove the list of interface adapters  that
38                                   corresponds to the device entry in the ser‐
39                                   vice_provider.conf(4) file.
40
41
42       -u                          Update the dat.conf to reflect the  current
43                                   state  of the system with an up to date set
44                                   of  interface  adapters  for  the   service
45                                   providers  that are currently listed in the
46                                   DAT static registry.
47
48
49       -v                          Display  the  DAT  static  registry   file,
50                                   dat.conf.
51
52

EXAMPLES

54       Example 1 Enumerating a Device Entry
55
56
57       The   following   example   enumerates  a  device  entry  in  the  ser‐
58       vice_provider.conf(4) file into interface adapters in  the  dat.conf(4)
59       file.
60
61
62
63       Assume  that  SUNW  has  a  service  provider library that supports the
64       device tavor. It has a service_provider.conf(4) file installed  in  the
65       directory  /usr/share/dat/SUNWudaplt.conf  with  a single entry as fol‐
66       lows:
67
68
69         driver_name=tavor u1.2 nonthreadsafe default\
70             udapl_tavor.so.1 SUNW.1.0 ""
71
72
73
74
75       tavor is an Infiniband Host Channel Adapter with  two  ports.  Both  IB
76       ports  exist  in  a  single IB partition, 0x8001. If an IP interface is
77       plumbed to each port, there are two IPoIB device  instances,  ibd0  and
78       ibd1:
79
80
81         # ls -l /dev/ibd*
82         /dev/ibd0 -> /devices/pci@1/pci15b3,5a44@0/ibport@1,8001,ipib:ibd0
83         /dev/ibd1 -> /devices/pci@1/pci15b3,5a44@0/ibport@2,8001,ipib:ibd1
84
85
86
87
88       Running  the  command, datadm -a /usr/share/dat/SUNWudaplt.conf appends
89       two  new  entries  (if  they   do   not   already   exists])   in   the
90       /etc/dat/dat.conffile:
91
92
93         ibd0 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
94         "driver_name=tavor"
95         ibd1 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
96         "driver_name=tavor"
97
98
99       Example  2  Updating  the  dat.conf to Reflect the Current State of the
100       System
101
102
103       A new IB partition, 0x8002 is added to the above example covering  port
104       1 of the Host Channel Adapter. If a new IP interface is plumbed to port
105       1/partition 0x8002, there is a third IPoIB device instance: ibd2.
106
107
108         # ls -l /dev/ibd*
109          /dev/ibd0 -> /devices/pci@1/pci15b3,5a44@0/ibport@1,8001,ipib:ibd0
110          /dev/ibd1 -> /devices/pci@1/pci15b3,5a44@0/ibport@2,8001,ipib:ibd1
111          /dev/ibd2 -> /devices/pci@1/pci15b3,5a44@0/ibport@1,8002,ipib:ibd2
112
113
114
115
116       Running datadm -u command, updates the /etc/dat/dat.conf  file  with  a
117       new entry added reflecting the current state of the system.
118
119
120
121       datadm   -v   shows   that   there   are   now  three  entries  in  the
122       /etc/dat/dat.conf file:
123
124
125         ibd0 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
126         "driver_name=tavor"
127         ibd1 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
128         "driver_name=tavor"
129         ibd2 u1.2 nonthreadsafe default udapl_tavor.so.1 SUNW.1.0 ""
130         "driver_name=tavor"
131
132
133

FILES

135       /etc/dat/dat.conf    DAT static registry file
136
137

ATTRIBUTES

139       See attributes(5) for descriptions of the following attributes:
140
141
142
143
144       ┌─────────────────────────────┬─────────────────────────────┐
145       │      ATTRIBUTE TYPE         │      ATTRIBUTE VALUE        │
146       ├─────────────────────────────┼─────────────────────────────┤
147       │Availability                 │SUNWudaplu                   │
148       ├─────────────────────────────┼─────────────────────────────┤
149       │Interface Stability          │Evolving                     │
150       └─────────────────────────────┴─────────────────────────────┘
151

SEE ALSO

153       pkgadd(1M),     pkgrm(1M),     libdat(3LIB),     dat.conf(4),      ser‐
154       vice_provider.conf(4). attributes(5)
155
156
157
158SunOS 5.11                        18 Jun 2004                       datadm(1M)
Impressum