Symantec 10521146 Administration Guide - Page 77

Table 4-1, Description, Details, Customer IDs, Node number, User name and, passphrases

Page 77 highlights

Populating the topology database 77 About the network topology You can save time if you review both the general information, and each procedure, and verify that you have all the necessary data before starting the procedure. The following table describes the kind of information you will need to provide when populating the topology tree: Table 4-1 Information to gather Field Description Name Description Customer IDs Node number User name and passphrases For all objects in the topology tree, you can provide a descriptive name of up to 40 characters. This is the object name displayed in the topology tree. Before you begin populating the topology database, establish a naming convention for all object types. A consistent and logical naming convention speeds the process of populating the topology database, and ensures that every object is uniquely named, thus making the topology tree easier to navigate. For all objects in the topology tree, you can provide an optional description of up to 255 characters. You may want to establish a convention regarding the type(s) of required and optional information to provide for each type of object. When you select an object in the topology tree, the Details pane displays your description, as well as other details about the object, such as its IP address or subnet mask, if applicable. For most objects in the topology tree, except monitoring interfaces and network segments, you can provide an optional customer ID of up to 40 characters; for example, to describe its physical location. This labels the device. If you set a customer ID at a location object, all device objects created under it inherits that customer ID by default. Likewise, interface objects inherit the customer ID of the parent device objects. You can edit the customer IDs on any individual object. For software and appliance nodes in the topology tree, you must provide a unique node number. Make a note of this number, because you must provide the same number when you perform the physical installation. The first node added defaults to 1 and to master status, if in a cluster. All subsequent nodes default to slave status if in a cluster, and you must assign unique numbers between 2 and 120, inclusive. For some objects in the topology tree, you must provide an established username and passphrase, or enable a passphrase for accessing device activity logs, if the device was set up in that way. Create a passphrase of up to 30 characters.

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392

77
Populating the topology database
About the network topology
You can save time if you review both the general information, and each
procedure, and verify that you have all the necessary data before starting the
procedure.
The following table describes the kind of information you will need to provide
when populating the topology tree:
Table 4-1
Information to gather
Field
Description
Name
For all objects in the topology tree, you can provide a descriptive
name of up to 40 characters. This is the object name displayed in
the topology tree. Before you begin populating the topology
database, establish a naming convention for all object types. A
consistent and logical naming convention speeds the process of
populating the topology database, and ensures that every object
is uniquely named, thus making the topology tree easier to
navigate.
Description
For all objects in the topology tree, you can provide an optional
description of up to 255 characters. You may want to establish a
convention regarding the type(s) of required and optional
information to provide for each type of object. When you select an
object in the topology tree, the
Details
pane displays your
description, as well as other details about the object, such as its IP
address or subnet mask, if applicable.
Customer IDs
For most objects in the topology tree, except monitoring
interfaces and network segments, you can provide an optional
customer ID of up to 40 characters; for example, to describe its
physical location. This labels the device. If you set a customer ID
at a location object, all device objects created under it inherits
that customer ID by default. Likewise, interface objects inherit
the customer ID of the parent device objects. You can edit the
customer IDs on any individual object.
Node number
For software and appliance nodes in the topology tree, you must
provide a unique node number. Make a note of this number,
because you must provide the same number when you perform
the physical installation. The first node added defaults to 1 and to
master status, if in a cluster. All subsequent nodes default to slave
status if in a cluster, and you must assign unique numbers
between 2 and 120, inclusive.
User name and
passphrases
For some objects in the topology tree, you must provide an
established username and passphrase, or enable a passphrase for
accessing device activity logs, if the device was set up in that way.
Create a passphrase of up to 30 characters.