* * * * *
“Let me 'splain … No, there is too much. Let me sum up.”
Quick recap of the week so far.
Monday
Spent the day loading images off the camera and selecting which ones
to post out of 200+ photos taken during my recent road trip to the
Kennedy Space Center [1].
Tuesday
Spent the day dealing with email issues, and writing the monstrous
posts for Saturday [2].
I was supposed to get with Smirk to move computer equipment and
install a replacement core router, but he got swamped and rescheduled
for Wednesday.
Wednesday
Spent the day dealing with email issues, and dreading the write-up
for Sunday [3].
Also headed into the Data Center to help Smirk move a bunch of
equipment and replace our core router with something better. Things
go downhill, and we decide to call it a day and regroup on Thursday.
Thusday
Spent the day dealing with email issues, and headed back into the
Data Center to finish up what we started yesterday. Got into the Data
Center around 6:00 pm. We start moving equipment and hope that we
didn't miss anything.
Friday
I left the Data Center around 1:30 am, after having to diagnose a
customer's machine that isn't responding on the network. I tracked it
down to a possible bad port on the new (new!) replacement router
(which is why it took so long to track down—didn't expect a bad
port).
Smirk warned me that he might call me in the morning if there are any
issues, but hopefully, there aren't any.
Got a call from Smirk at 8:30 am. Turns out to be a minor glitch
that is easy to fix. I contemplate going back to bed.
But before I can contemplate too long, Smirk calls back, with yet
another email issue (it's bascially the same one that's plagued us
all week) and yet another customer is having network issues, possibly
due to all the work last night.
The networking issue is mostly resolved when I remove some agressive
spanning tree [4] filtering on the port (I thought there was no need
to run the spanning tree protocol over that port since it's router-to
router, not switch-to-switch, but due to the actual network topology,
it was switch-to-switch—sigh). The remaining issue is the severe lack
of OSPF (Open Shortest Path First) [5] communications between our
router and the customer's router.
The email issue is still on-going (more on that later [6]).
Finally buckled down and wrote the write-up for Sunday [7], and this
post.
And here we are …
[1]
gopher://gopher.conman.org/0Phlog:2008/03/14-16
[2]
gopher://gopher.conman.org/1Phlog:2008/03/15
[3]
gopher://gopher.conman.org/1Phlog:2008/03/16
[4]
http://en.wikipedia.org/wiki/Spanning_tree_protocol
[5]
http://en.wikipedia.org/wiki/OSPF
[6]
gopher://gopher.conman.org/0Phlog:2008/03/21.2
[7]
gopher://gopher.conman.org/1Phlog:2008/03/16
Email author at
[email protected]
