Your XP VM and the device you're testing shouldn't care about the IP address assigned to vmbr1. So you can leave it static or just remove the IP address from vmbr1 entirely. Might save you some time and energy when hooking 'em up!
@@clabretro you only need to set the IP in the bridge if you want to be able to manage your proxmox from the xp machine in this example. It is a greate video. I love your content btw ;)
As people have said, IP doesn't matter. Your bridge is layer 2. You're effectively physically plugging your VM into whichever network you've bridged onto.
I love how straightforward this device is. An equivalent modern device would require a cloud subscription. And an API that lets you access the data only in a way that benefits the manufacturer and not the user.
I had one of these in a small datacenter I worked at. One day I went to go check out an overtemp alert at around 9:30 PM, and had discovered that the outdoor unit on one of the minisplits lit it's self on fire. Thanks to a Weather Goose I was able to call the fire department just in time to prevent the fire from spreading!
@@RonnocbotWe’ve migrated most GPO’s. We’re working on migrating packages and trying to get the internal app devs to support Entra ID join only so we can move to Autopilot. Good luck!
That 9 month ago comment was amazing. I had no idea a weather goose existed, really enjoy these videos, not sure what you've managed to encapsulate, but they're absolutely perfect.
That's quite hilarious that you ran into one of those watch dogs. I work for an MSP and one of our clients have an older watchdog 15-PoE that has very old firmware (was like from 2011). I was having SMTP issues and contacted the company which I ultimately found they were bought by Vertiv, they were surprised on the age of the firmware and I was able to get the firmware updated. Fantastic video and look forward to see more of this!
Oh wow, once again a very interesting topic! And I did spot that Cisco device at the end, really looking forward to more videos about early 2000s networking, especially Cisco stuff ;)
When I need to find an IP range of an unknown device I connect to it with a cross-over to a system with a second Nic then tcpdump or run Wireshark. Start a capture then power on the device to see what it asks for. Like an ARP request of its default gateway or other information it will leak out.
Yep. I stopped using the vendor tool to find the IP address and have used that technique, but! Crossover cables are a thing of the past (I may have 1 or 2, 20 years old?). All Ethernet Network ports in the last 15+ years? have auto mdi-x, aka, auto crossover, so a straight patch would work as well.
I know I'm necroposting but as an aspiring network engineer I think this is the best channel on RUclips. I learn multiple seriously interesting things every video, that daughter card blew my mind for no reason. Keep this up man!
One thing you could try when looking for the IP is to use wireshark and look at any ARP requests coming from the other device. If it has a gateway defined, it will send an ARP request out looking for it.
I was just thinking that a mirrored port on the switch feeding to a wireshark session would tell you almost anything you needed to know about the existing IP configuration of a device.
That assumes it initiates unicast network traffic by itself, if by chance a device just listens passively this won't work. But even if it doesn't hit the gateway there's a decent chance it will send out _some_ traffic even if it's just a broadcast. In this case you'll need to look at all traffic, focusing on ARP alone won't do any good. On the gateway note, the web management on my D-Link switch has some weird half-baked IP implementation which IIRC managed to work even when the gateway was set incorrectly.
@@MarkD26 There's no need for a fancy switch. Since he has a graphical environment locally installed on his PVE node it's easy enough to put Wireshark on there.
The push-in connectors are normally open/closed dry contacts. We have the Geist equivalent to yours (except PoE and with the display) and we bought a module that uses a rope laying on the floor to detect water leaks that plugs into the RJ ports so I wouldn't be surprised if they have both analog and digital inputs.
Watching your channel is like taking a stroll through my career.. We had WeatherDucks and SuperGoosees (SuperGeese?) They were great.... But we sent them all off to be recycled into lawn furniture long ago. Love your channel
Oh, One more thing... The external sensors that plug into the RJ11 ports are just Dallas 1-Wire sensors of various types. Im sure the branded sensors are available on ebay, but if not you can build them yourself. Technically i think you can put up to 127 sensors on the bus, but in practice we used far less because of noise problems with the long unshielded cables ... 10-20 works pretty well though. It just uses standard old fashioned POTS telephone splitters.
Man, your expression when you found the backdoor is awesome. Same thing when I find something 'magical' on the Internet too! Great job dude! Also Phoenix Server Room! I can't imagine Port Forwarding it, and accessing the WAP page on a Nokia.
Also, you looked like a 'hacker-man' when you turned off the lights lol. Also with regards to the 'testing network'. I feel that you could probably get an OpenWRT compatible router, (perhaps the old WRT54Gs), and just run that, isolated from your network. And it should report the DHCP address (if any), that the devices plugged in is reporting as.
Nice! 2821 was actually my first real Cisco ISR. Best router to have if you don't want to worry about licensing. It's also how I got my first Cisco phone system running as those actually contain an IP PBX.
@@alexdhall I would aim just a little newer than that. Those were a bit pre standard and are genreally harder to work with. 7941/42/45, 7961/61/65, and 7970/71/75 are all way better.
@@JZB-2022 I have a Cisco 7912 which when shipped only supported a proprietary but I was able to find a SIP-compatible firmware which works with modern VoIP software. I imagine the ISR would support the proprietary protocol of the original firmware no problem.
That RUclips comment on that old video really came in clutch! Wow. This is a cool piece of remote monitoring equipment, I’ll bet there are still data centers out there with these…. Somewhere.
These things are super cool and useful. My company is a reseller for Room Alert devices and I wouldn't be surprised if these units are nearly identical on the inside.. The digital sensors are a little pricey, I have been tempted to open one up and see what the actual probe is - probably just a 3 wire DS18B20 or something like that you could wire up and terminate an RJ11 on your own. I've also found that you can use any variety of cheap NO or NC sensors for the analog ports, i.e. door entry magnetic sensors, motion sensors (with separate power source), etc...
Ah! I have a SuperGoose II in my rack which I inherited when we shut down an old server room (I also have a MicroGoose around here somewhere). I wish I'd know you had this, I also have some sensors I'd be happy to send you. I definitely have some water sensors, I think I still have a power sensor and maybe also an external airflow sensor.
Another Great video, as for finding out the IPs and ports learn NMAP its a linux and windows binary with a simple CLI and you can specify an IP range to search and it will check each one for common ports or you can scan every port from 1-25565 and at the end it will return you with a list of devices and open ports. That's really useful when you know the IP but not the management port
This reminds me of a 4chan post I came across. It was a "show us what you did" thread and this anon had mad from some a very obscure proprietary audio format to wav. I happened to need it. It helped me figure out the v2 of that format
I had a ton of those.... as the SuperGoose (WxGoose1250) which had a nice LCD display on the front, too..... still kicking, at least most of them are -- and very probe-able via SNMP too!
Oooh, I actually have a bunch of these in production at our corporate datacenter (lol, buy it once, buy it for life. :D ) For the analog ports, you have the two C connectors and then the three inputs, technically they're pulldowns and they're looking for connecting to Common in order to register a change. Otherwise they'll read 255 (undefined). We have one connected to some "water rope", it registers as a 0 if the rope is wet, 255 if dry. There were a myriad of sensors, current transformers (amp monitoring), utility power presence monitor (literally a LED with a photodiode detector), water ropes, additional temperature sensors, door contact sensors, etc... For the four telephone jacks on the front, those are indeed for additional temperature ensors (they're actually Dallas 1-Wire sensors). You can wire up your own, there's a PDF online somewhere but it only take three wires, +, -, and data. I think the - wire is duplicated but it requires a six pin RJ12 connector. I'll have to see if I can find the pinout, it's on a hard drive somewhere. For best results (or at least what I do) is I use something like LibreNMS or Observium to monitor the Weathergoose for historical measuring and recording and use Nagios to monitor for "current state" recording, both via SNMP. With Nagios, monitoring the explicit OID for a provided sensor (I have four hooked up to the one I have at home) it can alert if the temperature is too high or too low while Observium/LibreNMS will show the temperature trending of a particular sensor.
Glad to see someone using the keystone couplers! I started using them at home several years ago and sure, they can fail but that has rarely happened. Not having to spend a bunch of time punching down is nice at home. I save the real cabling for work lol
You can have internal network addresses of what you would typically find on the Internet. You just need to configure a network card to be able to talk with the device on the same network. The caveat being that you may not be able to access services on the Internet that uses that exact network.
Man this is really cool! It’s awesome to see hardware like this! It’s also funny to see that people all over the world will have similar problems and so glad you could find that RUclips video about how to reset the password!! Great video keep it up!
Again great videos! I believe they hooked a sensor to the main electric circuit and it will send an alert if they loose main power.. At that time generators will kick in and employees can monitor everything from the UPS management and probably call and ask the price and delivery time of a tank truck full of diesel just in case...
But when mayor electric work was needed and the circuit from the city needed to be cut we never used our 4 big ass generators... We called a mobile "generator-in-a-container" and hooked it to a special huge plug datacenters have near their main electric rooms.. Maybe it was more cost efective and redundancy wise.. (mobile generator+batteries+generators)
We've got two of these at work still. They're more reliable than the new fancy building management system. Different brand but the hardware is identical
I would expect the dry contacts to be straightforward on/off, between C and one of the 3 inputs. you could try a push button to test them. If you get the chance, you could probably add a leak detector (float contact) from a scrap dishwasher - a lot of them have them in the base plate.
Nearly every datacenter I've worked in over the last 10 years had either an ITWatchdogs or a Geist environmental monitor device. Still very common to see in the modern datacenter.
@@clabretrowe never had anything so fancy in our racks back in the day! thanks for this video btw, it prompted me to dig out an identical model from a uk reseller i inherited from a server room clearout during lockdown, and the reset/powerup part finally got me in. now i know for sure 24/7 that my home office is too cold :) shame the snmp and librenms don't get on.
Another blast from my IT past. Configured a lot of watchdog environment sensors when I worked for Delta Airlines in the early 2000's. I'm not sure how but would love to get a Westinghouse 1642, which was the green screened terminals you'd see at airports back in the day before we replace with OS/2 and eventually Windows NT4. Based on what I understand, its all serial and in theory could interface with the TTY console of any device with the right settings (dip switches) applied. Hmmm... off to ebay to search.
Actually, if you want to use bridges, you can also use the virtual functions (VF) of the NIC, so you can get something like 8 virtual interfaces and map a VM with a virtual nic from the card
Those dry contact sensors should be really easy to replicate... It's literally just detecting a very small current, usually something like 20mA (you'd have to find out the exact current). You should be able to find some that are compatible or play around with making your own. Oh, BTW, I bet city power was just their Mains power coming in. Dry contact sensors are often used to detect power conditions and are commonly used in UPS devices, so it might have been tied to that.
Another great video this week man. Todays bad idea, more building upon your previous videos Instead of pulling cable you have a great reason to spend time playing with some crusty ancient Cisco trunking to see if you can vlan from your bench to your VM’s. I love vlans, I have a couple WiFi routers sprinkled around my house that bridge ports between them on different vlans so I can link up some legacy Ethernet only hardware to my network or even just to each other.
Atkins changed name - they are now known as AtkinsRéalis. They had a fairly large railway design presence in northern europe which they sold to french Systra.
I upgraded my R7910 to a 2 port copper 10g + 2 port 1g nic a while ago, paid quite a bit for it on ebay. The day after I installed it - my network gets hit by lighting. Only casualty was the 10g card and the switch. Back to the quad 1g nic ever since. Guess it wasn't meant to be.
The universe is telling you to use fiber. AFAIK it's often cheaper than copper and more future resistant, I can't imagine getting over 10G on reasonable copper cables but a cheap fiber cable will be more than good enough for 400G.
that was plan b, but when pulling the preterminated fiber (over 300ft underground in a conduit) I broke the connector during the last few inches pulling it into the rack. @@eDoc2020
@@jfarre20 If you have 300ft of run between buildings then you should _definitely_ be using fiber instead of copper. Any defect in copper for at that distance will result in problems running at high bitrates, and you've already learned what can happen when outdoor runs are copper.
you're slowly accruing equipment of similar vintage and in this case exact manufacturer and model to the rack I managed at my last job. you just need a bunch of iBoot stuff and a Dell Precision rackmount server running Cacti.
that weather goose turned out to be cooler than I thought-the backdoor password would totally NOT fly in 2024 security always kind of funny to see how "security" was back in the day lol. you might be stuck replacing the riser card for your R720 to fix the intrusion switch issue. unless you can find the wires in that and basically tie it together so it thinks its always closed. Also. Pro Dell poweredge tip, Dell servers like you visiting the lifecycle controller so it can "add to inventory" that's a dell-branded card once you do that it may show up (the 10GB card) in idrac for monitoring...also that can tell the server to re-adjust its fan speed profile for that new card. not required, but a good idea Unless you have CSIOR enabled ( collect system inventory on reboot)
6:07 Hey, just wanted to note that when you're swapping PCIe devices you're supposed to totally remove power from the server (not just shut it down). Seems like in this case it wasn't an issue, but in the past I accidentally did it on one of my R720s and the Lifecycle Controller really wasn't happy with me the next time I booted it up. Just something to keep in mind for the future.
Fantastic video! I've actually deployed I guess what would be the newer version of the watchdog. Still rack mounted but it has gotten a few quality of life updates, like being POE powered if you like. Wonderful devices, I've debated about throwing one in my personal rack.
City power as in voltage? But i'm pretty sure stuff would die well before 20v. and tbh I would want to track power hz as well as voltage as that will give you a lot of info about incoming power conditions.
I used one of the yellow units you showed early in the video many years ago. Worked fine until it started locking up. 😢 Amazingly, not useful for monitoring the server room temperature when it was inaccessible. 😂
I just use an old fortigate firewall (well, a few years old, I've been running them for many years and as one lot nears eol they get cheap and that's what I run until the next gen gets cheap). A bunch of the ports are separate zones, each with a dhcp server running. Last device I needed to work out, just plugged into one of these ports, "diagnostic sniffer packet ", and thankfully it broadcast it's ip in the first packet it put out after powerup. Set the interface to that config, and ospf let every other network device on my network know how to get there. Gave it a quick nmap and all was good. It's even easier if the device itself is set to use dhcp, but unfortunately not every old piece of gear comes that way after decommission :(
14:25 this is always the story with old hardware. I mean there is gazillion memes about that: 20 year old video, 10 year old comment, 5 year old reply. Classic. The best is when you don't even need to tailor the answer to your case - it just matches exactly.
Pinging 255.255.255.255 is a quick and dirty way to get the IP address of anything on your LAN, unless the device is configured not to respond to pings to that broadcast address. The CLI will usually only show the first address that responded, so IIRC you have to look at the ARP table or have a pcap running on the interface to see the rest of the devices.
If I have a device with an unknown IP, I usually connect it to a PC with running Wireshark or tcpdump. Then reboot the device. Many devices will do at boot a: gratuitous ARP, ARP to the gateway, NTP request, SNMP trap, etc. And from all of them (and any other IP-Header) you can get the IP of the device, no router required. I’m also not sure what the Unifi does to show the IP, I assume they also only listen for a ARP requests.
Finding the correct driver is not painful by knowing the model Number, you can Match the hardware ID. That's what I did when Dell screwed up the Network ID for A Studio XPS 8100 wrong driver file was on the Dell site for that Model so I went to Broadcom site and Downloaded the correct driver no more Network drops and crashes I'm good at doing this I can always send you the driver because I know the model number
The city power monitor looks a lot like they monitored voltage from an outlet. They would want to know if the voltage went below 20 volts (probably 0 actually if there's a power outage) or above 150 volts for a power surge. I'm just assuming but it would make a bit of sense. Either that or they monitored their power consumption in amps
You dont Need to add an IP to an Bridge. The ip is only needed if you want to Access the Proxmox Webinterface from the Bridge Network. Just let it empty if you just want to pass a nic. Then you just Need to configure the ip in the vm
Great video! really enjoyed it :) will there gonna be a video on the Linksys tower of power? im really intressted in them, but dont know much/where to look.
I don't have much proxmox experience--do you even need to change the IP of the bridge interface in Proxmox, if you're giving the VM itself an IP too? Isn't the bridge just doing a physical layer 2 bridge anyway?
When I have to figure out a random IP, I'll usually use Wireshark and a USB-Nic. Should be able to use it on XP VM? It doesn't actually need an IP.. at minimum you should see the device trying to contact its default gateway or DNS or NTP or request DHCP? Also, for your XP interface you use for IP discovery, turn off the other services (like file/printer sharing. Etc...) to reduce extra distracting traffic...
funny to think that a microcontroller can do exactly that, and probably faster. imagine an esp32 and an sd card and some io. how technology moves! btw, what's inside this goose device? I wanted to see a teardown!
Your XP VM and the device you're testing shouldn't care about the IP address assigned to vmbr1.
So you can leave it static or just remove the IP address from vmbr1 entirely. Might save you some time and energy when hooking 'em up!
ah thank you! I was wondering about that
@@clabretro you only need to set the IP in the bridge if you want to be able to manage your proxmox from the xp machine in this example. It is a greate video. I love your content btw ;)
Came here to say just this. No need to tell proxmox the IP on the bridge for that network at all.
As people have said, IP doesn't matter. Your bridge is layer 2. You're effectively physically plugging your VM into whichever network you've bridged onto.
It's even better for the network security to not give pve an IP on that bridge. Then the old hardware cannot mess around with pve.
That obscure RUclips comment was awesome. Thank you random stranger from the internet!
I love how straightforward this device is. An equivalent modern device would require a cloud subscription. And an API that lets you access the data only in a way that benefits the manufacturer and not the user.
No kidding, and this thing will keep on working for another 30 years I bet.
I had one of these in a small datacenter I worked at. One day I went to go check out an overtemp alert at around 9:30 PM, and had discovered that the outdoor unit on one of the minisplits lit it's self on fire. Thanks to a Weather Goose I was able to call the fire department just in time to prevent the fire from spreading!
ha thats awesome!
That guy who left that youtube comment 9 months ago is a fucking legend
absolute hero
"I'm a bit late, but" no buddy - you're right on time
First I couldn’t get an SCCM task sequence to work, then Teams was down, but now you uploaded and have rescued my day. Thank you!
Glad I could help ya out 🫡
Teams being down was screwing with me all day 😅
Hope your migration from SCCM to Intune is well under way! We've been hard at work at this at my organization.
And all the IT Professionals converge upon the ancient server hardware XD
@@RonnocbotWe’ve migrated most GPO’s. We’re working on migrating packages and trying to get the internal app devs to support Entra ID join only so we can move to Autopilot. Good luck!
Honey wake up! New clabretro video just dropped!
That 9 month ago comment was amazing. I had no idea a weather goose existed, really enjoy these videos, not sure what you've managed to encapsulate, but they're absolutely perfect.
Thanks for watching!
Man I'm glad I found this channel, all this stuff is great
thanks!
Just hits all the right spots, doesn't it?
Great video! Thanks again for making it! Time to get mine up and running this weekend in my rack! Also appreciate the shoutout!!!
Definitely! let me know how it's goes. and thanks for the idea haha
Oh yes! Let's figure out the sensor stuff!
Time to take it appart and grap a couple pictures, I'd sure love to have a look! :)
I'll open it up if I do a follow-up with sensors!
Can't wait to see the SNMP rabbit hole.
Oh yeah that'll be a good one. I'll be sure to document.
It will be interesting. V1 and V2 are pretty simple (and very insecure). Never really used v3 though...
This channel never fails to deliver, I get to work around some old server and data centre kit and i love seeing this stuff
nice! and thanks for watching!
They had the best logo. They had good products. I bought a temp monitor based on the dog logo.
That's quite hilarious that you ran into one of those watch dogs. I work for an MSP and one of our clients have an older watchdog 15-PoE that has very old firmware (was like from 2011). I was having SMTP issues and contacted the company which I ultimately found they were bought by Vertiv, they were surprised on the age of the firmware and I was able to get the firmware updated. Fantastic video and look forward to see more of this!
nice! and thanks for watching!
Oh wow, once again a very interesting topic! And I did spot that Cisco device at the end, really looking forward to more videos about early 2000s networking, especially Cisco stuff ;)
There will definitely be more Cisco networking stuff coming!
When I need to find an IP range of an unknown device I connect to it with a cross-over to a system with a second Nic then tcpdump or run Wireshark. Start a capture then power on the device to see what it asks for. Like an ARP request of its default gateway or other information it will leak out.
Good call, I was thinking wireshark might be the way to go.
Yep. I stopped using the vendor tool to find the IP address and have used that technique, but!
Crossover cables are a thing of the past (I may have 1 or 2, 20 years old?).
All Ethernet Network ports in the last 15+ years? have auto mdi-x, aka, auto crossover, so a straight patch would work as well.
I know I'm necroposting but as an aspiring network engineer I think this is the best channel on RUclips. I learn multiple seriously interesting things every video, that daughter card blew my mind for no reason. Keep this up man!
thanks!
One thing you could try when looking for the IP is to use wireshark and look at any ARP requests coming from the other device. If it has a gateway defined, it will send an ARP request out looking for it.
I was just thinking that a mirrored port on the switch feeding to a wireshark session would tell you almost anything you needed to know about the existing IP configuration of a device.
That assumes it initiates unicast network traffic by itself, if by chance a device just listens passively this won't work. But even if it doesn't hit the gateway there's a decent chance it will send out _some_ traffic even if it's just a broadcast. In this case you'll need to look at all traffic, focusing on ARP alone won't do any good.
On the gateway note, the web management on my D-Link switch has some weird half-baked IP implementation which IIRC managed to work even when the gateway was set incorrectly.
@@MarkD26 There's no need for a fancy switch. Since he has a graphical environment locally installed on his PVE node it's easy enough to put Wireshark on there.
The push-in connectors are normally open/closed dry contacts. We have the Geist equivalent to yours (except PoE and with the display) and we bought a module that uses a rope laying on the floor to detect water leaks that plugs into the RJ ports so I wouldn't be surprised if they have both analog and digital inputs.
A sneaky fibre channel san at the end there.
don't worry about that 😎
Watching your channel is like taking a stroll through my career.. We had WeatherDucks and SuperGoosees (SuperGeese?) They were great.... But we sent them all off to be recycled into lawn furniture long ago. Love your channel
Oh, One more thing... The external sensors that plug into the RJ11 ports are just Dallas 1-Wire sensors of various types. Im sure the branded sensors are available on ebay, but if not you can build them yourself. Technically i think you can put up to 127 sensors on the bus, but in practice we used far less because of noise problems with the long unshielded cables ... 10-20 works pretty well though. It just uses standard old fashioned POTS telephone splitters.
thanks for the tip about the sensors!
Man, your expression when you found the backdoor is awesome. Same thing when I find something 'magical' on the Internet too! Great job dude! Also Phoenix Server Room! I can't imagine Port Forwarding it, and accessing the WAP page on a Nokia.
Also, you looked like a 'hacker-man' when you turned off the lights lol. Also with regards to the 'testing network'. I feel that you could probably get an OpenWRT compatible router, (perhaps the old WRT54Gs), and just run that, isolated from your network. And it should report the DHCP address (if any), that the devices plugged in is reporting as.
I love seeing this wacky stuff that I couldn't see anywhere else. Thank you.
I wish to have a cool homelab as yours once I independice
My first "homelab" was a Pentium III laptop with the screen broken off of it. Doesn't take much!
Nice! 2821 was actually my first real Cisco ISR. Best router to have if you don't want to worry about licensing. It's also how I got my first Cisco phone system running as those actually contain an IP PBX.
Very cool. Yeah I haven't dove in yet but I'm sure PBX stuff will show up down here eventually haha.
All he needs is some Cisco 7940 and 7960 phones...🤔
@@alexdhall I would aim just a little newer than that. Those were a bit pre standard and are genreally harder to work with. 7941/42/45, 7961/61/65, and 7970/71/75 are all way better.
@@JZB-2022 I have a Cisco 7912 which when shipped only supported a proprietary but I was able to find a SIP-compatible firmware which works with modern VoIP software. I imagine the ISR would support the proprietary protocol of the original firmware no problem.
That RUclips comment on that old video really came in clutch! Wow. This is a cool piece of remote monitoring equipment, I’ll bet there are still data centers out there with these…. Somewhere.
Yet another video about equipment we didn't know we wanted to know about :)
These things are super cool and useful. My company is a reseller for Room Alert devices and I wouldn't be surprised if these units are nearly identical on the inside.. The digital sensors are a little pricey, I have been tempted to open one up and see what the actual probe is - probably just a 3 wire DS18B20 or something like that you could wire up and terminate an RJ11 on your own.
I've also found that you can use any variety of cheap NO or NC sensors for the analog ports, i.e. door entry magnetic sensors, motion sensors (with separate power source), etc...
Ah! I have a SuperGoose II in my rack which I inherited when we shut down an old server room (I also have a MicroGoose around here somewhere). I wish I'd know you had this, I also have some sensors I'd be happy to send you. I definitely have some water sensors, I think I still have a power sensor and maybe also an external airflow sensor.
Oh awesome! Feel free to reach out to the email in the channel's about page (might have to be on desktop to see it).
do it!
@@clabretro Will do. I need to find the sensors then I'll shoot you an email.
I FINALLY found them! Sending an email now.
Another Great video, as for finding out the IPs and ports learn NMAP its a linux and windows binary with a simple CLI and you can specify an IP range to search and it will check each one for common ports or you can scan every port from 1-25565 and at the end it will return you with a list of devices and open ports. That's really useful when you know the IP but not the management port
Hope you keep this in the rack!! Also, looking further to see an update on the homelab tour in 2024!!
I might have to do one of those again ha
Killer device, great video
thanks! it seems rock solid to be honest.
This reminds me of a 4chan post I came across. It was a "show us what you did" thread and this anon had mad from some a very obscure proprietary audio format to wav. I happened to need it. It helped me figure out the v2 of that format
We have one of these in our rack, it’s old but it works! 😂
I can't blame you, this thing works great! haha
I had a ton of those.... as the SuperGoose (WxGoose1250) which had a nice LCD display on the front, too..... still kicking, at least most of them are -- and very probe-able via SNMP too!
Yeah I need to get an SNMP server going!
If Vertiv bought them, don't be surprised if new sensors are still compatible with the old monitor hardware..
That's good to hear. Is Vertiv a good company? I hadn't heard of them before.
@@clabretro they are / were also known as Liebert. One of the big players in the power / "physical" IT space, along with APC / Schneider.
Oooh, I actually have a bunch of these in production at our corporate datacenter (lol, buy it once, buy it for life. :D ) For the analog ports, you have the two C connectors and then the three inputs, technically they're pulldowns and they're looking for connecting to Common in order to register a change. Otherwise they'll read 255 (undefined). We have one connected to some "water rope", it registers as a 0 if the rope is wet, 255 if dry. There were a myriad of sensors, current transformers (amp monitoring), utility power presence monitor (literally a LED with a photodiode detector), water ropes, additional temperature sensors, door contact sensors, etc...
For the four telephone jacks on the front, those are indeed for additional temperature ensors (they're actually Dallas 1-Wire sensors). You can wire up your own, there's a PDF online somewhere but it only take three wires, +, -, and data. I think the - wire is duplicated but it requires a six pin RJ12 connector. I'll have to see if I can find the pinout, it's on a hard drive somewhere.
For best results (or at least what I do) is I use something like LibreNMS or Observium to monitor the Weathergoose for historical measuring and recording and use Nagios to monitor for "current state" recording, both via SNMP. With Nagios, monitoring the explicit OID for a provided sensor (I have four hooked up to the one I have at home) it can alert if the temperature is too high or too low while Observium/LibreNMS will show the temperature trending of a particular sensor.
ah, thank you for the sensor info! yeah thinking it's time to get a LibreNMS server running
I use Vertiv's gear daily and they make excellent KVM's. Their environment sensor leave much to be desired, but their KVM's are pretty nice
That was Avocent before they are acquired by Vertiv.
@@markarca6360 Doesn't change the fact I still use them too lol
Glad to see someone using the keystone couplers! I started using them at home several years ago and sure, they can fail but that has rarely happened. Not having to spend a bunch of time punching down is nice at home. I save the real cabling for work lol
only way to go! so much easier, especially when you're making changes.
another good video. Love that you explain everything as you go on.
thanks!
You can have internal network addresses of what you would typically find on the Internet. You just need to configure a network card to be able to talk with the device on the same network. The caveat being that you may not be able to access services on the Internet that uses that exact network.
Man this is really cool! It’s awesome to see hardware like this! It’s also funny to see that people all over the world will have similar problems and so glad you could find that RUclips video about how to reset the password!! Great video keep it up!
Again great videos! I believe they hooked a sensor to the main electric circuit and it will send an alert if they loose main power.. At that time generators will kick in and employees can monitor everything from the UPS management and probably call and ask the price and delivery time of a tank truck full of diesel just in case...
But when mayor electric work was needed and the circuit from the city needed to be cut we never used our 4 big ass generators... We called a mobile "generator-in-a-container" and hooked it to a special huge plug datacenters have near their main electric rooms.. Maybe it was more cost efective and redundancy wise.. (mobile generator+batteries+generators)
Loved that unit. I have a couple of sensors left over from that unit.
We've got two of these at work still. They're more reliable than the new fancy building management system.
Different brand but the hardware is identical
excellent . I love seeing you getting this stuff up and running! the Sensor device is cool as well!
thanks!
I would expect the dry contacts to be straightforward on/off, between C and one of the 3 inputs. you could try a push button to test them. If you get the chance, you could probably add a leak detector (float contact) from a scrap dishwasher - a lot of them have them in the base plate.
Nearly every datacenter I've worked in over the last 10 years had either an ITWatchdogs or a Geist environmental monitor device. Still very common to see in the modern datacenter.
that's so crazy to see a bit of atkins infra, i worked for ws atkins in frontline support and later as a consultant from '96-'01 in the uk
ha awesome!
@@clabretrowe never had anything so fancy in our racks back in the day! thanks for this video btw, it prompted me to dig out an identical model from a uk reseller i inherited from a server room clearout during lockdown, and the reset/powerup part finally got me in. now i know for sure 24/7 that my home office is too cold :) shame the snmp and librenms don't get on.
I love that you found that reset info in an old youtube comment xD
We use these in a few of the datacenters I manage.
nice!
I would personally love to see a video of you installing and setting up a SNMP server.
I'll probably get that in a future video!
What a cool little device. I loved the reset password hack, so brute-forceable 😇
Just great! I love this kind of YT videos!
thank you!
Another blast from my IT past. Configured a lot of watchdog environment sensors when I worked for Delta Airlines in the early 2000's. I'm not sure how but would love to get a Westinghouse 1642, which was the green screened terminals you'd see at airports back in the day before we replace with OS/2 and eventually Windows NT4. Based on what I understand, its all serial and in theory could interface with the TTY console of any device with the right settings (dip switches) applied. Hmmm... off to ebay to search.
ha thats cool. and yeah one of those terminals would be awesome
Actually, if you want to use bridges, you can also use the virtual functions (VF) of the NIC, so you can get something like 8 virtual interfaces and map a VM with a virtual nic from the card
Those dry contact sensors should be really easy to replicate... It's literally just detecting a very small current, usually something like 20mA (you'd have to find out the exact current).
You should be able to find some that are compatible or play around with making your own.
Oh, BTW, I bet city power was just their Mains power coming in. Dry contact sensors are often used to detect power conditions and are commonly used in UPS devices, so it might have been tied to that.
Another great video this week man.
Todays bad idea, more building upon your previous videos Instead of pulling cable you have a great reason to spend time playing with some crusty ancient Cisco trunking to see if you can vlan from your bench to your VM’s.
I love vlans, I have a couple WiFi routers sprinkled around my house that bridge ports between them on different vlans so I can link up some legacy Ethernet only hardware to my network or even just to each other.
thank you! and oh yeah we'll be bringing more Cisco relics into the mix for sure
You don't have to edit the bridge in PVE. You can remove the IP on vmbr1 and it will still work inside your vm.
The one and ONLY time that RUclips comments were helpful 😂😂
Nice OCP port usage dell.
Atkins changed name - they are now known as AtkinsRéalis.
They had a fairly large railway design presence in northern europe which they sold to french Systra.
I upgraded my R7910 to a 2 port copper 10g + 2 port 1g nic a while ago, paid quite a bit for it on ebay.
The day after I installed it - my network gets hit by lighting. Only casualty was the 10g card and the switch. Back to the quad 1g nic ever since. Guess it wasn't meant to be.
That's a sad tale haha.
The universe is telling you to use fiber. AFAIK it's often cheaper than copper and more future resistant, I can't imagine getting over 10G on reasonable copper cables but a cheap fiber cable will be more than good enough for 400G.
that was plan b, but when pulling the preterminated fiber (over 300ft underground in a conduit) I broke the connector during the last few inches pulling it into the rack. @@eDoc2020
@@jfarre20 If you have 300ft of run between buildings then you should _definitely_ be using fiber instead of copper. Any defect in copper for at that distance will result in problems running at high bitrates, and you've already learned what can happen when outdoor runs are copper.
I don't need it, I don't need it, I don't need it. But maybe after the day today was, this was such a good watch.
Haha. Thanks for watching!
digi makes a lot of things like that, serial to ip, usb to ip, etc.
you're slowly accruing equipment of similar vintage and in this case exact manufacturer and model to the rack I managed at my last job. you just need a bunch of iBoot stuff and a Dell Precision rackmount server running Cacti.
Ha nice! Cacti is on my short list of things to mess with 👀
Or a copy of Obsevium or LibreNMS....
that weather goose turned out to be cooler than I thought-the backdoor password would totally NOT fly in 2024 security always kind of funny to see how "security" was back in the day lol. you might be stuck replacing the riser card for your R720 to fix the intrusion switch issue. unless you can find the wires in that and basically tie it together so it thinks its always closed. Also. Pro Dell poweredge tip, Dell servers like you visiting the lifecycle controller so it can "add to inventory" that's a dell-branded card once you do that it may show up (the 10GB card) in idrac for monitoring...also that can tell the server to re-adjust its fan speed profile for that new card. not required, but a good idea Unless you have CSIOR enabled ( collect system inventory on reboot)
yeah I just turned it off in the bios lol. thanks for the inventory tip!
Oh, God that pearl 5 book looming in the background
gotta keep it at a safe distance
6:07 Hey, just wanted to note that when you're swapping PCIe devices you're supposed to totally remove power from the server (not just shut it down). Seems like in this case it wasn't an issue, but in the past I accidentally did it on one of my R720s and the Lifecycle Controller really wasn't happy with me the next time I booted it up. Just something to keep in mind for the future.
oh yeah really good call out! I got lucky this time, I noticed that while editing. definitely should've pulled the power.
Fantastic video!
I've actually deployed I guess what would be the newer version of the watchdog. Still rack mounted but it has gotten a few quality of life updates, like being POE powered if you like. Wonderful devices, I've debated about throwing one in my personal rack.
Don’t throw it in there, put it in gently 😅 want to keep the lid switch!
City power as in voltage? But i'm pretty sure stuff would die well before 20v. and tbh I would want to track power hz as well as voltage as that will give you a lot of info about incoming power conditions.
Christ, I'm pretty sure the APC rack monitor I'm actively running in my DC is the same age
I used one of the yellow units you showed early in the video many years ago. Worked fine until it started locking up. 😢 Amazingly, not useful for monitoring the server room temperature when it was inaccessible. 😂
I just use an old fortigate firewall (well, a few years old, I've been running them for many years and as one lot nears eol they get cheap and that's what I run until the next gen gets cheap). A bunch of the ports are separate zones, each with a dhcp server running. Last device I needed to work out, just plugged into one of these ports, "diagnostic sniffer packet ", and thankfully it broadcast it's ip in the first packet it put out after powerup. Set the interface to that config, and ospf let every other network device on my network know how to get there. Gave it a quick nmap and all was good.
It's even easier if the device itself is set to use dhcp, but unfortunately not every old piece of gear comes that way after decommission :(
That's a really nice way to go, I think I'll end up doing something really similar!
14:25 this is always the story with old hardware. I mean there is gazillion memes about that: 20 year old video, 10 year old comment, 5 year old reply. Classic. The best is when you don't even need to tailor the answer to your case - it just matches exactly.
Pinging 255.255.255.255 is a quick and dirty way to get the IP address of anything on your LAN, unless the device is configured not to respond to pings to that broadcast address. The CLI will usually only show the first address that responded, so IIRC you have to look at the ARP table or have a pcap running on the interface to see the rest of the devices.
yeah that's a good trick. didn't try it with the watchdog but had no luck on that IMM unfortunately.
I feel bad for just retiring my data centers 720s 😅
If I have a device with an unknown IP, I usually connect it to a PC with running Wireshark or tcpdump. Then reboot the device. Many devices will do at boot a: gratuitous ARP, ARP to the gateway, NTP request, SNMP trap, etc. And from all of them (and any other IP-Header) you can get the IP of the device, no router required.
I’m also not sure what the Unifi does to show the IP, I assume they also only listen for a ARP requests.
yeah think I'll brush up on my Wireshark skills
omg I totally forgot about this company- that stupid little dog logo brought back memories 😂
You can run wireshark, it will send arp
Please sell “Weather Goose” t-shirts with that goose graphic on them. 😂
😂
You can just leave the bridge config empty on proxmox besides the bridged port. Then you only need to reconfigure xp.
about 5 years ago we threw away our weather goose
we used for water as the place we rented flooded more than once and knowing early is key lol
looks like a Rukus logo
Of it wasnt for a OneNote file I have named HugeMcLarge, I also would not remember any network configurations.....
Finding the correct driver is not painful by knowing the model Number, you can Match the hardware ID. That's what I did when Dell screwed up the Network ID for A Studio XPS 8100 wrong driver file was on the Dell site for that Model so I went to Broadcom site and Downloaded the correct driver no more Network drops and crashes I'm good at doing this I can always send you the driver because I know the model number
The city power monitor looks a lot like they monitored voltage from an outlet. They would want to know if the voltage went below 20 volts (probably 0 actually if there's a power outage) or above 150 volts for a power surge. I'm just assuming but it would make a bit of sense. Either that or they monitored their power consumption in amps
yeah I bet you're right
You don't need to set the Proxmox bridge to the same network for the XP VM to talk to the device, save yourself 5 minutes :-)
Yeah I learned that via another comment after I posted haha. Good tip!
Loving your content BTW, bringing back lots of nostalgia vibes. Warm regards from the UK.
Thank you! And thanks for watching!
Dang, really much as I stood for.
You dont Need to add an IP to an Bridge. The ip is only needed if you want to Access the Proxmox Webinterface from the Bridge Network. Just let it empty if you just want to pass a nic. Then you just Need to configure the ip in the vm
yeah I figured that out later lol
Great video! really enjoyed it :)
will there gonna be a video on the Linksys tower of power? im really intressted in them, but dont know much/where to look.
I have one here! ruclips.net/video/LvLPz72IvAM/видео.html. The tower just seems to keep growing, though.
Ah! thank you i mustve missed it! something something tower of babel but networking heh
I like the geist firmware better, they made it a bit fancier
You don’t need another router, just a layer 3 switch or a layer 2switch with a router on a stick!
"the goose is loose" lol
I did that same thing on my dell. I didn’t mean to close it but bumped it and snap.
I don't have much proxmox experience--do you even need to change the IP of the bridge interface in Proxmox, if you're giving the VM itself an IP too? Isn't the bridge just doing a physical layer 2 bridge anyway?
you're 100% right, I didn't realize that when I was setting everything up haha
When I have to figure out a random IP, I'll usually use Wireshark and a USB-Nic. Should be able to use it on XP VM? It doesn't actually need an IP.. at minimum you should see the device trying to contact its default gateway or DNS or NTP or request DHCP?
Also, for your XP interface you use for IP discovery, turn off the other services (like file/printer sharing. Etc...) to reduce extra distracting traffic...
what is a 4124 SIP adapter to FSX interface for integrating 24 analog phones? and can you use one?
funny to think that a microcontroller can do exactly that, and probably faster. imagine an esp32 and an sd card and some io. how technology moves! btw, what's inside this goose device? I wanted to see a teardown!
I'll open it up next time it's in a video!
Wooohoooo 🎉🎉🎉🎉