defaria.com/blogs/Status/archives/2004_08.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   2    "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
   3 <html xmlns="http://www.w3.org/1999/xhtml" id="sixapart-standard">
   4 <head>
   5    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
   6    <meta name="generator" content="Movable Type 5.2.3" />
   7
   8    <link rel="stylesheet" href="http://defaria.com/blogs/Status/styles-site.css" type="text/css" />
   9    <link rel="alternate" type="application/atom+xml" title="Atom" href="http://defaria.com/blogs/Status/atom.xml" />
  10    <link rel="alternate" type="application/rss+xml" title="RSS 2.0" href="http://defaria.com/blogs/Status/index.xml"$>" />
  11
  12    <title>Status for Andrew DeFaria: August 2004 Archives</title>
  13
  14    <link rel="start" href="http://defaria.com/blogs/Status/" title="Home" />
  15    <link rel="prev" href="http://defaria.com/blogs/Status/archives/2004_07.html" title="July 2004" />
  16    <link rel="next" href="http://defaria.com/blogs/Status/archives/2004_09.html" title="September 2004" />
  17 </head>
  18 <body class="layout-one-column">
  19    <div id="container">
  20       <div id="container-inner" class="pkg">
  21
  22          <div id="banner">
  23             <div id="banner-inner" class="pkg">
  24                <h1 id="banner-header"><a href="http://defaria.com/blogs/Status/" accesskey="1">Status for Andrew DeFaria</a></h1>
  25                <h2 id="banner-description">Searchable status reports and work log</h2>
  26             </div>
  27          </div>
  28
  29          <div id="pagebody">
  30             <div id="pagebody-inner" class="pkg">
  31                <div id="alpha">
  32                   <div id="alpha-inner" class="pkg">
  33
  34                      <p class="content-nav">
  35                         <a href="http://defaria.com/blogs/Status/archives/2004_07.html">&laquo; July 2004</a> |
  36                         <a href="http://defaria.com/blogs/Status/">Main</a>
  37                         | <a href="http://defaria.com/blogs/Status/archives/2004_09.html">September 2004 &raquo;</a>
  38                      </p>
  39
  40
  41
  42
  43                      <h2 class="date-header">August 30, 2004</h2>
  44                      <a id="a000239"></a>
  45                      <div class="entry" id="entry-239">
  46                         <h3 class="entry-header">Informatica/CLEARCASE_PRIMARY_GROUP</h3>
  47                         <div class="entry-content">
  48                            <div class="entry-body">
  49                               <ul>
  50
  51 <li>Rearranged Informatica script code to be more oriented to what Don needs</li>
  52
  53 <li>Helped William Dean with issues regarding Clearcase. I think we are all OK now so I closed the Paragrine ticket for this. This has, however, opened up the issue that CLEARCASE_PRIMARY_GROUP needs to be set in some cases</li>
  54
  55 </ul>
  56
  57                               <p>In order to make the pushing of Rational Tools more automatic it's important to either eliminate all user specific settings or to come up with a way to determine the setting for the user at login time. As such I have been researching if the CLEARCASE_PRIMARY_GROUP needs to be set at all. In most cases it doesn't need to be. (It was thought that mkelem would make the element and that the protect trigger would -chgrp &lt;<i>vob group owner</i>&gt; of the element. But if the user does not have CLEARCASE_PRIMARY_GROUP set then they are often considered part of <i>Domain Users</i> which isn't usually on the vob's group list). However today I found out a case where it needs to be. <a href="http://www.ibm.com/support/docview.wss?rs=0&q1=CLEARCASE_PRIMARY_GROUP&uid=swg21135509&loc=en_US&cs=utf-8&cc=us&lang=en">According to What is the CLEARCASE_PRIMARY_GROUP variable used for?</a></p>
  58
  59 <blockquote>
  60   <p>If the vob is owned by <b>more than one group</b> and a user is a
  61   member of <b>more than one</b> of those groups and the user's group list
  62   does <b>not</b> exceed 32,  they need the CLEARCASE_PRIMARY_GROUP
  63   variable set in order to create elements in that vob.</p>
  64
  65   <p>If the vob is owned by <b>more than one</b> group and a user is a
  66   member of <b>more than one</b> of those groups and the user's group list
  67   <b>does</b> exceed 32, they need the CLEARCASE_PRIMARY_GROUP &
  68   CLEARCASE_GROUPS variable set in order to create elements in that vob.
  69   </p>
  70 </blockquote>
  71
  72 <p>Unfortunately this is the situation that we have. In particular Core_automation is owned by more than one group and users are members of more than one of those groups. Thus CLEARCASE_PRIMARY_GROUP needs to be set.</p>
  73
  74 <p>Also, we tend to have many groups and if we have more than 32 groups we can run into problems. Setting CLEARCASE_GROUPS helps narrow the problem down but a user can only be a member of at the maximum 33 Clearcase oriented groups or else they will need to be shifting around CLEARCASE_GROUPS in order to operate.</p>
  75
  76 <p>So what I'm proposing is that the Clearquest Tools database functionality be expanded yet again to provide for associating a userid to the appropriate CLEARCASE_PRIMARY_GROUP and appropriate CLEARCASE_GROUPS. Some of this functionality is already present in the Tools database. What it lacks is the ability to designate which of the groups is the users primary group.</p>
  77
  78 <p>There's also the issue of backfilling the Tools database and filling out the necessarily information for the users currently entered into the Tools database as well as filling the Tools database from that Access database...</p>
  79
  80                               <p class="entry-footer">
  81                                  <span class="post-footers">Posted by  at  6:11 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000239.html">Permalink</a>
  82
  83
  84                               </p>
  85                            </div>
  86                         </div>
  87                      </div>
  88
  89
  90
  91                      <h2 class="date-header">August 26, 2004</h2>
  92                      <a id="a000237"></a>
  93                      <div class="entry" id="entry-237">
  94                         <h3 class="entry-header">Permissions problems</h3>
  95                         <div class="entry-content">
  96                            <div class="entry-body">
  97                               <ul>
  98
  99 <li>Spent most of the day wrestling with permissions problems. Anje was having problems as vobadm with EAG vobs in a UCM view. Attempted to recreate the problem and understand why it's not allowing her to create elements. Seems the EAG_VMS vob is owned by AsapAdm and group CC-EAG-VMS but vobadm is not the owner. vobadm is in the group and the group has write permission but vobadm can't write.</li>
 100
 101 <li>Started writing WSH keystroke module for the Informatica process that Don is working on</li>
 102
 103 </ul>
 104
 105                               <p class="entry-footer">
 106                                  <span class="post-footers">Posted by  at  7:21 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000237.html">Permalink</a>
 107
 108
 109                               </p>
 110                            </div>
 111                         </div>
 112                      </div>
 113
 114
 115
 116                      <h2 class="date-header">August 25, 2004</h2>
 117                      <a id="a000238"></a>
 118                      <div class="entry" id="entry-238">
 119                         <h3 class="entry-header">Implementing Groups</h3>
 120                         <div class="entry-content">
 121                            <div class="entry-body">
 122                               <ul>
 123
 124 <li>Noticed the CC-TTE-EMP-* groups have been created. One has the wrong name (should be CC-TTE-EMP-SCR but is CC-TTE-EMP-SRC. My fault! Typo when I requested the group). Applied these groups to the folders in Core_automation</li>
 125
 126 <li>Changed protect trigger to set group owner to that of the parent directory. This is needed for this fix</li>
 127
 128 <li>Removed Permissions trigger. This trigger was ineffective and is no longer needed</li>
 129
 130 </ul>
 131
 132                               <p class="entry-footer">
 133                                  <span class="post-footers">Posted by  at  7:28 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000238.html">Permalink</a>
 134
 135
 136                               </p>
 137                            </div>
 138                         </div>
 139                      </div>
 140
 141
 142
 143                      <h2 class="date-header">August 23, 2004</h2>
 144                      <a id="a000236"></a>
 145                      <div class="entry" id="entry-236">
 146                         <h3 class="entry-header">cmverify/protect</h3>
 147                         <div class="entry-content">
 148                            <div class="entry-body">
 149                               <ul>
 150
 151 <li>Changed cmverify to report username in the logfile name and in report itself</li>
 152
 153 <li>Changed protect trigger to use the parent directoy's group as the group owner for new elements</li>
 154
 155 </ul>
 156
 157                               <p class="entry-footer">
 158                                  <span class="post-footers">Posted by  at 11:19 AM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000236.html">Permalink</a>
 159
 160
 161                               </p>
 162                            </div>
 163                         </div>
 164                      </div>
 165
 166
 167
 168                      <h2 class="date-header">August 19, 2004</h2>
 169                      <a id="a000235"></a>
 170                      <div class="entry" id="entry-235">
 171                         <h3 class="entry-header">Group Permissions/mktriggers</h3>
 172                         <div class="entry-content">
 173                            <div class="entry-body">
 174                               <ul>
 175
 176 <li>Started documenting usage of groups within groups</li>
 177
 178 <li>Helped John with mktriggers modifications</li>
 179
 180 <ul>
 181
 182                               <p class="entry-footer">
 183                                  <span class="post-footers">Posted by  at  7:10 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000235.html">Permalink</a>
 184
 185
 186                               </p>
 187                            </div>
 188                         </div>
 189                      </div>
 190
 191
 192
 193                      <h2 class="date-header">August 18, 2004</h2>
 194                      <a id="a000234"></a>
 195                      <div class="entry" id="entry-234">
 196                         <h3 class="entry-header">Group Permissions/cmconfig</h3>
 197                         <div class="entry-content">
 198                            <div class="entry-body">
 199                               <ul>
 200
 201 <li>Wrapped up the 3 things we want to do to configure during install into a cmd script - cmconfig.cmd</lI>
 202
 203 <li>Performed a lot of investigation regarding group permissions problem - writing web page for this</li>
 204
 205 </ul>
 206
 207                               <p class="entry-footer">
 208                                  <span class="post-footers">Posted by  at  5:06 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000234.html">Permalink</a>
 209
 210
 211                               </p>
 212                            </div>
 213                         </div>
 214                      </div>
 215
 216
 217
 218                      <h2 class="date-header">August 17, 2004</h2>
 219                      <a id="a000233"></a>
 220                      <div class="entry" id="entry-233">
 221                         <h3 class="entry-header">cqverify/TOOLS</h3>
 222                         <div class="entry-content">
 223                            <div class="entry-body">
 224                               <ul>
 225
 226 <li>Submitted a few task for improvements with the TOOLS database</li>
 227
 228 <li>Changed cqverify to deliniate between username not found and password wrong. Changed return status such that if the username is not in the Clearquest database that's an error. But if the user is in the Clearquest database but the password is not default then that's just a warning</li>
 229
 230 <li>Assisted TTE member to add ASAP_WinRunner to his view</li>
 231
 232 </ul>
 233
 234                               <p class="entry-footer">
 235                                  <span class="post-footers">Posted by  at  6:42 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000233.html">Permalink</a>
 236
 237
 238                               </p>
 239                            </div>
 240                         </div>
 241                      </div>
 242
 243
 244
 245                      <h2 class="date-header">August 16, 2004</h2>
 246                      <a id="a000232"></a>
 247                      <div class="entry" id="entry-232">
 248                         <h3 class="entry-header">Setregion/c[qc]verify</h3>
 249                         <div class="entry-content">
 250                            <div class="entry-body">
 251                               <ul>
 252
 253 <li>Implemented setregion.vbs. This command will set the region for the passed in region name. Or, if no region is given, it uses the users ID and the TOOLS database to determine that user's home region</li>
 254
 255 <li>Requested SQL folk to allow monitoring of SQL service</li>
 256
 257 <li>Changed cqverify to attempt connecting to Clearquest database using the user's username and password</li>
 258
 259 <li>Changed ccverify to not consider an empty CLEARCASE_PRIMARY_GROUP as an error</li>
 260
 261 </ul>
 262
 263                               <p class="entry-footer">
 264                                  <span class="post-footers">Posted by  at  1:27 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000232.html">Permalink</a>
 265
 266
 267                               </p>
 268                            </div>
 269                         </div>
 270                      </div>
 271
 272
 273
 274                      <h2 class="date-header">August 13, 2004</h2>
 275                      <a id="a000231"></a>
 276                      <div class="entry" id="entry-231">
 277                         <h3 class="entry-header">What'sUP/set region</h3>
 278                         <div class="entry-content">
 279                            <div class="entry-body">
 280                               <ul>
 281
 282 <li>Worked on setting up What's Up alarms and alerts</li>
 283
 284 <li>Created setregion.vbs. This script will set the region to the passed in region. If nothing is passed in it will attempt to find the region associated with the project for the currently logged in user through the CQ TOOLS database. If it can't find it then it will leave the registry setting alone</li>
 285
 286 </ul>
 287
 288                               <p class="entry-footer">
 289                                  <span class="post-footers">Posted by  at  6:31 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000231.html">Permalink</a>
 290
 291
 292                               </p>
 293                            </div>
 294                         </div>
 295                      </div>
 296
 297
 298
 299                      <h2 class="date-header">August 12, 2004</h2>
 300                      <a id="a000230"></a>
 301                      <div class="entry" id="entry-230">
 302                         <h3 class="entry-header">Tools Push</h3>
 303                         <div class="entry-content">
 304                            <div class="entry-body">
 305                               <ul>
 306
 307 <li>Spent most of the day investigating how best to solve the issue of supplying Desktop Support a group/region for a user. Started writing VBScript to interrogate the CQ TOOLS database. Have the code functionally working but we need to add Region to a Project in CQ TOOLS. Also need to orient all of our <group>.reg files to be <region>.reg files.</li>
 308
 309 <li>Implemented COMMENT_SQL_CODE trigger for BUCS_SRC</li>
 310
 311 </ul>
 312
 313                               <p class="entry-footer">
 314                                  <span class="post-footers">Posted by  at  8:47 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000230.html">Permalink</a>
 315
 316
 317                               </p>
 318                            </div>
 319                         </div>
 320                      </div>
 321
 322
 323
 324                      <h2 class="date-header">August 11, 2004</h2>
 325                      <a id="a000229"></a>
 326                      <div class="entry" id="entry-229">
 327                         <h3 class="entry-header">Cron problems/Server Problems/CC Groups</h3>
 328                         <div class="entry-content">
 329                            <div class="entry-body">
 330                               <ul>
 331
 332 <li>Had problems with cron not being able to find scripts</li>
 333
 334 <li>Spent much of the day researching whether or not we need to use CLEARCASE_PRIMARY_GROUP at all</li>
 335
 336 <li>View server needed rebooting</li>
 337
 338 </ul>
 339
 340                               <p class="entry-footer">
 341                                  <span class="post-footers">Posted by  at  5:48 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000229.html">Permalink</a>
 342
 343
 344                               </p>
 345                            </div>
 346                         </div>
 347                      </div>
 348
 349
 350
 351                      <h2 class="date-header">August 10, 2004</h2>
 352                      <a id="a000228"></a>
 353                      <div class="entry" id="entry-228">
 354                         <h3 class="entry-header">AD Groups/setup</h3>
 355                         <div class="entry-content">
 356                            <div class="entry-body">
 357                               <ul>
 358
 359 <li>Worked on trying to sort out the differences between AD groups/groups.dat and the .reg files. Need to investigate if all this is required in the first place.</li>
 360
 361 <li>Finished up setup_cygwin. Added links for .inputrc, .Xdefaults and .vimrc. Added stuff for verbose and debug</li>
 362
 363 </ul>
 364
 365                               <p class="entry-footer">
 366                                  <span class="post-footers">Posted by  at  5:56 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000228.html">Permalink</a>
 367
 368
 369                               </p>
 370                            </div>
 371                         </div>
 372                      </div>
 373
 374
 375
 376                      <h2 class="date-header">August  9, 2004</h2>
 377                      <a id="a000227"></a>
 378                      <div class="entry" id="entry-227">
 379                         <h3 class="entry-header">Env/CQ Down/Groups</h3>
 380                         <div class="entry-content">
 381                            <div class="entry-body">
 382                               <ul>
 383
 384 <li>Added more of an environment into CM_TOOLS</li>
 385
 386 <li>Clearquest has been down all day. Server threw a shoe. Won't be up 'til tomorrow</li>
 387
 388 <li>Seems we may not have a 1-to-1 correspondance between groups.dat/AD Groups and .reg files. Trying to work out the problems here</li>
 389
 390 </ul>
 391
 392                               <p class="entry-footer">
 393                                  <span class="post-footers">Posted by  at  7:04 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000227.html">Permalink</a>
 394
 395
 396                               </p>
 397                            </div>
 398                         </div>
 399                      </div>
 400
 401
 402
 403                      <h2 class="date-header">August  5, 2004</h2>
 404                      <a id="a000226"></a>
 405                      <div class="entry" id="entry-226">
 406                         <h3 class="entry-header">CC-TTE/CommentSQLCode/whosin</h3>
 407                         <div class="entry-content">
 408                            <div class="entry-body">
 409                               <ul>
 410
 411 <li>Had problems with the Permissions trigger. Something we forgot or didn't think about. If the user attempts to add elements to source control they should be permitted in folders that have .perms. However part of adding to source control checks out the parent directory first. At the parent directory level there is no .perms to permit the user to check out the parent directory! This causes Add to Source Control to fail. Solution was to change the algorithm to account for this</li>
 412
 413 <li>Finished up CommentSQLCode trigger. Added stuff to triggers.dat and documented things in CM_DOCS. Waiting for code review.</li>
 414
 415 <li>Got this bright idea to take GetCCGroups.vbs and make another script that will simply dump the users for the given groups. Useful command line tool called whois</li>
 416
 417 <li>Worked on trying to get PC to install the new Rational Web Server for John</li>
 418
 419 </ul>
 420
 421                               <p class="entry-footer">
 422                                  <span class="post-footers">Posted by  at  4:38 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000226.html">Permalink</a>
 423
 424
 425                               </p>
 426                            </div>
 427                         </div>
 428                      </div>
 429
 430
 431
 432                      <h2 class="date-header">August  4, 2004</h2>
 433                      <a id="a000225"></a>
 434                      <div class="entry" id="entry-225">
 435                         <h3 class="entry-header">CommentSQLCode Trigger</h3>
 436                         <div class="entry-content">
 437                            <div class="entry-body">
 438                               <ul>
 439
 440 <p><li>Implemented CommentSQLCode Trigger - need to do code review, triggers.dat, and documentation</li></p>
 441
 442 <p><li>Assisted Loren, Padma and William in getting the Permisisons working</li></p>
 443
 444 </ul>
 445
 446                               <p class="entry-footer">
 447                                  <span class="post-footers">Posted by  at  6:35 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000225.html">Permalink</a>
 448
 449
 450                               </p>
 451                            </div>
 452                         </div>
 453                      </div>
 454
 455
 456
 457                      <h2 class="date-header">August  3, 2004</h2>
 458                      <a id="a000224"></a>
 459                      <div class="entry" id="entry-224">
 460                         <h3 class="entry-header">New Trigger</h3>
 461                         <div class="entry-content">
 462                            <div class="entry-body">
 463                               <p>Here are the requirements as I understand them for the trigger that Steve Lipson wants for the SQL checkins. Basically he desires a trigger that will capture the checkin comment and other information and insert that information in the form of a comment at the top of the checked in element. This trigger will:</p>
 464
 465 <ul>
 466   <li>Be a postop trigger for the checkin action</li>
 467   <li><b>Not</b> be an all element trigger rather it will be attached to certain file elements in the vob</li>
 468   <li>Be made for the &lt;<i>fill in vob name here</i>&gt; vob</li>
 469   <li>Only work on file elements - directory elements are to be skipped</li>
 470   <li>Only work on file elements that have an extension of .sql - other elements will be skipped</li>
 471 </ul>
 472
 473 <p>Roughly the psuedo code for this trigger will be:</p>
 474
 475 <div class="code"><pre>
 476 # Get name of element and its type
 477 $pname        = $ENV{CLEARCASE_PN};
 478 $element_type = $ENV{CLEARCASE_ELTYPE};
 479
 480 # Skip directories and elements that aren't .sql
 481 exit if $element_type =~ /directory/i || $pname !~ /\.sql$/i;
 482
 483 # Get comment and user
 484 $comment   = $ENV{CLEARCASE_COMMENT};
 485 $userid    = $ENV{CLEARCASE_USER};
 486
 487 # Format timestamp
 488 $timestamp = getCurrentTime;
 489
 490 # Parse output of lsactivity -cact -long
 491 ($activity_id, $activity_title, $activity_owner) = parseLSActivity;
 492
 493 # Open up $pname for reading and $pname.trig for writting
 494 open PNAME_IN, $pname
 495   or die "Unable to open $pname for reading - $!\n";
 496
 497 open PNAME_OUT, ">$pname.trig"
 498   or dir "Unable to open $pname.trig for writing - $!\n";
 499
 500 # Add comment to top of file
 501 print $PNAME_OUT &lt;&lt;END;
 502 -- Date:            $timestamp
 503 -- Activity: $activity_id: $activity_title
 504 -- Owner:    $activity_owner ($userid)
 505 -- Comment:  $comment
 506 END
 507
 508 # Append $pname
 509 while (<PNAME_IN>) {
 510   print PNAME_OUT $_;
 511 } # while
 512
 513 close PNAME;
 514 close PNAME_OUT;
 515
 516 # Switch $pname.trig -> $pname
 517 unlink $pname;
 518 rename "$pname.trig", $pname;
 519
 520 # Allow checkin to proceed
 521 exit 0;
 522 </pre></div>
 523
 524                               <p class="entry-footer">
 525                                  <span class="post-footers">Posted by  at  6:54 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000224.html">Permalink</a>
 526
 527
 528                               </p>
 529                            </div>
 530                         </div>
 531                      </div>
 532
 533
 534
 535                      <h2 class="date-header">August  2, 2004</h2>
 536                      <a id="a000223"></a>
 537                      <div class="entry" id="entry-223">
 538                         <h3 class="entry-header">Server move (cont)</h3>
 539                         <div class="entry-content">
 540                            <div class="entry-body">
 541                               <p>OK, licenses are all OK now. BTW hostid is not a combination of IP address and MAC address - it's simply MAC address of the NIC card. Problem appears to be that during the server move the NIC card changed! I verified this with the Rational rep this morning. The current MAC address of the NIC card as shown by ipconfig /all (it's the Physical Address) is 00-0f-20-6d-09-97. I gave the old license strings to the rep and she determined our old MAC address of the NIC card was 00-0b-cd-9b-f4-27.</p>
 542
 543 <p>Looking at the Device Manager on the servers I notice that we have two Network Adapters listed:</p>
 544
 545 <ol>
 546   <li>HP NC7781 Gigabit Server Adapter</li>
 547   <li>HP NC7781 Gigabit Server Adapter #2</li>
 548 </ol>
 549
 550 <p>Why we have 2 NIC cards I don't know (perhaps merely for the ability to be multihomed). Normally I see #1 being disabled and #2 being enabled. Rtnlprod01 is like this. Rtnlprod02 has #1 enabled and #2 disabled. For the vob and view servers this does not matter. Either card will work. For rtnlprod03 however, since licenses are tied to the NIC card's MAC address, switching from #1 -> #2 (or #2 -> #1 as I suspect has happened here) will invalidate all licenses. We need to insure that the network adapter for rtnlprod03 remains nailed at either #1 or #2.</p>
 551
 552 <p>Since it appears that the network adapter has changed and since I have obtained a new set of licenses for this new network adapter and still have the old set, I have installed both sets so that in the event that the network adapter switches again we'll be covered. However, if we order additional licenses for say card #1 and somehow we get switched to card #2, those additional licenses will not be represented, hence the desire to nail the NIC card to either one or the other.</p>
 553
 554                               <p class="entry-footer">
 555                                  <span class="post-footers">Posted by  at  6:47 PM</span> <span class="separator">|</span> <a class="permalink" href="http://defaria.com/blogs/Status/archives/000223.html">Permalink</a>
 556
 557
 558                               </p>
 559                            </div>
 560                         </div>
 561                      </div>
 562
 563                   </div>
 564                </div>
 565             </div>
 566          </div>
 567       </div>
 568    </div>
 569 </body>
 570 </html>