Greetings,
This is not a very easy message to write. After about 13+ years of running
AlphaServers, I will be decommissioning them in two weeks. As sometimes it
takes a while to find new owners for these machines, I'm sending this message
in advance to gauge interest in taking them. They are:
DEC AlphaServer 1200: (1) 533 MHz 21164A-2 CPU (until recently, it had two of
these. One is now showing a fan error. Perhaps, if you replaced the fan, it
still might work, if the board is OK), 1 GB ECC RAM, (2) 9.1 GB disks (one is
DEC OEM :]), (2) 18.2 GB disks, (3) 36.4 GB disks, (2) DEC DE500-XA 100 Mbit ethernet adapters, ARC Logic 2000PV VGA adapter (2 MB RAM?), QLogic 1020 Fast Wide SCSI HBA, Mylex RAID DAC960P/PD controller with 8 MB RAM.
DEC AlphaServer 4100: (4) 467 MHz 21164A-2 CPUs (one of these is dying, but I
have a replacement for it), 1 GB ECC RAM, (2) 9.1 GB disks (one is also DEC
OEM :]), (2) 18.2 GB disks, (3) 36.4 GB disks, (2) DEC DE500-[A,B]A 100 Mbit
ethernet adapters, S3 Trio32/64 VGA adapter (1 MB RAM?), QLogic 1020 Fast Wide
SCSI HBA, Mylex RAID DAC960P/PD controller with 8 MB RAM, (2) 9.1 GB disks
configured RAID1, (4) 9.1 GB disks configured RAID5, another (4) 9.1 GB disks
configured RAID5, (3) 9.1 GB disks configure RAID5. That makes (3)
StorageWorks arrays in the pedestal.
Pictures of the machines are available upon request. There's probably some other goodies in the box at the colo. I can't remember what's inside. Definitely, I have (3) DS 1287 TOY (time of year) chips. These are not very easy to find.
These machines are available to (in order of priority):
1) NetBSD/alpha port maintainers;
2) NetBSD/alpha developers;
3) pkgsrc developers (any platform);
4) NetBSD developers;
5) Developers of any other open source project;
6) The general public;
First person(s) in those categories showing interest gets them. You don't have
to take both; you can just take one if for some reason you don't want both.
I'm not parting them out, though. They've available for pickup in Troy, MI,
UNITED STATES, and I can coordinate with the colo for you. The colo will also
ship these machines for me, if you are willing to pay the shipping. In that
case, they're not limited to any particular geographic area.
The members of these lists have 14 days to declare interest/work out the
logistics of procuring these machines. Any other ideas for finding new owners
is also welcome.
Best regards,
rodent@
Sounds like a good idea.
Mark, please provide me with the following information:
your IP:
Is IP dynamic:
hostname:
your area number:
the source interface:
The email you want config alerts sent to:
The snmp community you want me to use:
For snmp, please protect it with an ACL:
snmp-server community <your community name here> RW 10
access-list 10 permit 199.166.5.172
-brian
On Thu, Mar 06, 2014 at 10:48:56PM -0500, Dave McGuire wrote:
The tunnel between here and Mark's network is outside of the 5x
numeric range that the autogeneration system uses, so they won't buck
heads. Let's fold him into that system when you get it all up and running.
-Dave
On 03/06/2014 10:30 PM, Brian Hechinger wrote:
Ah. I see.
I think the only person this affected was Cory. Everyone else's IPs don't change so the tunnels would have been fine.
-brian
On Mar 6, 2014, at 22:14, Mark Abene <phiber at phiber.com> wrote:
I GRE-peer directly with Dave McGuire (50.73.179.1), so any potential
hecnet hiccup would be via his net (I could be wrong, but I think he
updates from you?). I saw his router IP in your first e-mail, so I
just thought I'd ask. Things seem fine.
-Mark
On Thu, Mar 6, 2014 at 5:06 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
--
Dave McGuire, AK4HZ
New Kensington, PA
The tunnel between here and Mark's network is outside of the 5x
numeric range that the autogeneration system uses, so they won't buck
heads. Let's fold him into that system when you get it all up and running.
-Dave
On 03/06/2014 10:30 PM, Brian Hechinger wrote:
Ah. I see.
I think the only person this affected was Cory. Everyone else's IPs don't change so the tunnels would have been fine.
-brian
On Mar 6, 2014, at 22:14, Mark Abene <phiber at phiber.com> wrote:
I GRE-peer directly with Dave McGuire (50.73.179.1), so any potential
hecnet hiccup would be via his net (I could be wrong, but I think he
updates from you?). I saw his router IP in your first e-mail, so I
just thought I'd ask. Things seem fine.
-Mark
On Thu, Mar 6, 2014 at 5:06 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
--
Dave McGuire, AK4HZ
New Kensington, PA
Ah. I see.
I think the only person this affected was Cory. Everyone else's IPs don't change so the tunnels would have been fine.
-brian
On Mar 6, 2014, at 22:14, Mark Abene <phiber at phiber.com> wrote:
I GRE-peer directly with Dave McGuire (50.73.179.1), so any potential
hecnet hiccup would be via his net (I could be wrong, but I think he
updates from you?). I saw his router IP in your first e-mail, so I
just thought I'd ask. Things seem fine.
-Mark
On Thu, Mar 6, 2014 at 5:06 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
I GRE-peer directly with Dave McGuire (50.73.179.1), so any potential
hecnet hiccup would be via his net (I could be wrong, but I think he
updates from you?). I saw his router IP in your first e-mail, so I
just thought I'd ask. Things seem fine.
-Mark
On Thu, Mar 6, 2014 at 5:06 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
The ACL doesn't matter until the next time a config is pushed out. If the acl is wrong (doesn't allow me to talk to you) then I cannot initiate the tftp transfer of the config snippet.
I need to do a manual push when I get home for Cory. If you've made updates to the acl the next push to you will succeed.
-brian
On Mar 6, 2014, at 18:07, Mark Abene <phiber at phiber.com> wrote:
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
Just so I know, should I be expecting any interruptions?
That way I won't bug you if there are. :)
-Mark
On Thu, Mar 6, 2014 at 1:53 PM, Brian Hechinger <wonko at 4amlunch.net> wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
-brian
On Thu, 6 Mar 2014, Brian Hechinger wrote:
On Thu, Mar 06, 2014 at 04:03:48PM -0500, Cory Smelosky wrote:
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Yep, you got it.
Done.
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
On Thu, 6 Mar 2014, Brian Hechinger wrote:
Is working slightly better now. :)
I need to update hub.platinum.net's acl to allow the new host and I
think Cory does as well.
I think I do as well. ;)
199.166.5.172 it?
Reloading router: 50.73.179.1 xxxx 199.166.5.172 tunnel-gw.neurotica.com-ipv4.txt
running........
successful
Reloading router: 208.73.57.126 xxxxxx 199.166.5.172 tunnel-hub.platinum.net-ipv4.txt
Error reloading router: hub.platinum.net :: No SNMP response received before timeout
Reloading router: 10.42.255.33 xxxxxxxxxx 199.166.5.172 tunnel-bart.4amlunch.net-ipv4.txt
running...........................................................................................................................................................
successful
Reloading router: 75.49.17.245 xxxxxxxxxx 199.166.5.172 tunnel-dev.gimme-sympathy.org-ipv4.txt
Error reloading router: dev.gimme-sympathy.org :: No SNMP response received before timeout
-brian
--
Cory Smelosky
http://gewt.net Personal stuff
http://gimme-sympathy.org Projects
