Trouble on a monday
Aug. 22nd, 2005 09:20 am![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
sobriqueGot rung up at 07:50 this morning. 'No one could log on' to the NAS (network attached storage - think fileservers).
Which leads to a few hundred rather miffed users.
Which is nice.
So proceeded to forget about the problem for the duration of my drive to work. (Seriously, driving in the rain, when there's a panic on, and you're feeling flustered is just _not_ a good idea).
Rolled into work, made coffee and started investigating.
Nice simple one this time - one of the GBICs (gigabit interface converter - a flashy name for a fiber optic network port) on our ED-64M fiber switch appears to have failed. Unfortunately, it's also the one that our control station for our NAS. Normally, this isn't a problem, except our control station handles a service called 'usermapper'. Which maps windows SIDs (security Ids) to Unix UIDs (user Ids).
So basically, the data was running and available (which was why I didn't notice over the weekend) but no new connections could be created, because security credentials were unavailable.
Nice easy fix. Click -> click. Control station boots, everyone happy.
Although I suspect this means another incident report will be required...
Which leads to a few hundred rather miffed users.
Which is nice.
So proceeded to forget about the problem for the duration of my drive to work. (Seriously, driving in the rain, when there's a panic on, and you're feeling flustered is just _not_ a good idea).
Rolled into work, made coffee and started investigating.
Nice simple one this time - one of the GBICs (gigabit interface converter - a flashy name for a fiber optic network port) on our ED-64M fiber switch appears to have failed. Unfortunately, it's also the one that our control station for our NAS. Normally, this isn't a problem, except our control station handles a service called 'usermapper'. Which maps windows SIDs (security Ids) to Unix UIDs (user Ids).
So basically, the data was running and available (which was why I didn't notice over the weekend) but no new connections could be created, because security credentials were unavailable.
Nice easy fix. Click -> click. Control station boots, everyone happy.
Although I suspect this means another incident report will be required...
