NCSU OIT Integration Services

We haven't had a chance to migrate the content off of this site, so I don't think we'll be docommissoning it on the first of January.    It's good to set specific goals, but it's also good to let them slide when the project isn't on any criticial paths.

 We'll figure out in the new year how we'd like to prioritize integrate.oit's demise. :-)

Folks,

Our newest, hopefully permenant home has been established at http://xteams.oit.ncsu.edu/iso

We haven't been know as "Integration Services" for at least two re-orgs now, and it was either time to move, or allocate some more attention to this site's backend and disaster recovery.

I'm proud that this was the first drupal site in OIT, and I think our successful example paved the way for all the Drupal projects that are now moving forward or on the drawing board.

Sigh. Novell has releasd Service Pack #5 for Client-32 4.91

http://download.novell.com/Download?buildid=qmMAWSRy5q4~

We'll need to test this against our NDPS stuff to see if it fixes anything.

If you read way far down in the list of things addressed, it does mention

Ndppnt.dll from 4.91 SP4 breaks NDPS printer installs

Last week nds02ps crashed a bit, and had trouble crashing on automatic restart.  I think the issue was that when the ndps broker and manager were loading too soon after startup, we ran out of memory or cpu or karma and the box would crash.

 I've added the command DELAY 120 just before loading the broker/manager, so we should wait 2 full minutes after a reboot to actually start the print system.  Hopefully, this delay will help the box survive a reboot.

Boo hoo.

I was hoping that we could join a Dell Remote Access Card (DRAC) to an AD domain using the existing credentials and the web interface.  Alas!  It looks like we'll need to reboot the hosts in order to configure the DRACs during POST.

Folks,

 integrate.oit went off the air for a bit when it got a kernel update.  Just so I'm not the only one who knows the details, here's what I did to bring it back.  I'll print a hardcopy and stick it to my door, and we'll call it DRP. :-)

The integrate site it hosted on a virtual machine, named "drupal" running on wpdev.unity.ad.ncsu.edu .  Yes, the 'dev' means test box that isn't monitored.

You gain access to it with  PuTTY or ssh (regular Unity credentials).  

It's not the most popular method of navigating around in ACSAD, but there is a DFS root at

\\acsad.ncsu.edu\dfs

Most folks go in through CFS directly, but the DFS root has been there all along, nonetheless.

I've made a link here, "Unity" which will link back to \\unity.ad.ncsu.edu\dfs .  The plan is that whatever AD you usually log in to, you should be able to get to everything with only a single drive letter mapped.  So far, it's worked for Jamie and I, but not Wade.  Please post your own experiences! 

So as suspected, the issue with folks getting spurious pages about "unix-y" hosts was a mistake of different cultures.

Pager copies cccadm@help.ncsu.edu to get a Remedy call cut for any pages sent for the cccadm on-call group.  The *page* is sent through arch wireless or some other alpha paging system, the e-mail is just a cc so the incident will get a tracking number for later reporting/management.

Remedy is configured to copy the oit-iso-shs@lists.ncsu.edu mailing list.  This is where the unwanted pages at 3am are coming from.

Debbie and I spent some time this afternoon trying to quantify what was broken between ACSAD and UNITY.AD.

What we tested was creating a domain local group, and then adding members to that group from the other domain.  In all cases, we could browse and add from either domain without difficulties, but when we tried to view the members of the group, we got a "the other domain may be down" error after a long delay.

Hi gang,

 Joe and Will seem to have access controls assigned to groups rather then individual people in QIP.  Yay, go team, and woot!

For our monday meeting, I'd like to ask each of you to make a printout of all the VLANS that you have rights to in QIP, and mark up which ones you think the whole group needs, if they are to be responsible even in part for the job you're doing now.  I'd like to compile a map of VLANS, past and present.