[BMWGUYinCO]

Originally Posted by spazzyfry123

I can answer that one

Totally different birds. Egg-producing hens vs broilers are two different industries utilizing different methods and requirements. Broilers are bred for rapid growth for maximum meat and the quickest rate - so they are “easy” to replace since they have such quick life cycles comparatively. Egg birds need to be further along in their lifecycle for egg production - not “easy” to replace.

But are they too not susceptible to the Avian bird flu? But what you say makes sense however.

[spazzyfry123]

Originally Posted by BMWGUYinCO

But are they too not susceptible to the Avian bird flu?

They are and were, but not at near the scale as egg-layers since they are slaughtered at such an early age. They won't see the long term AI effects like older birds (egg-laying). Broiler (meat birds) replacement is rapid - can be slaughtered in about five weeks. AI-impacted birds already had their replacement in the queue with demand not outweighing supply. Egg birds don't start laying until about five or six months. So even if they are able to replace the impacted birds, it could be several months before they see eggs.

[BMWGUYinCO]

Originally Posted by spazzyfry123

They are and were, but not at near the scale as egg-layers since they are slaughtered at such an early age. They won't see the long term AI effects like older birds (egg-laying). Broiler (meat birds) replacement is rapid - can be slaughtered in about five weeks. AI-impacted birds already had their replacement in the queue with demand not outweighing supply. Egg birds don't start laying until about five or six months. So even if they are able to replace the impacted birds, it could be several months before they see eggs.

Thanks again for the information Spazzy! I appreciate being informed about this.

[spazzyfry123]

Originally Posted by BMWGUYinCO

Thanks again for the information Spazzy! I appreciate being informed about this.

I'm in the animal feed biz. You don't know what you don't know!

[zx10guy]

Originally Posted by spazzyfry123

Attachment 3686165

Is it bad that I can relate to this meme and partially recognize the actual switch being pictured? It's either a Cisco Catalyst 4500 or 6500. Worked on plenty of them back in the day.

I could have created some interesting memes back in the day if I had the ability to take pics. Some of the things I saw were just mind blowing. One was when I had to locate a 6509 switch at a data center. Walked the aisle a number of times and couldn't find it. I finally did when I spread open a literal curtain of cables that blocked me being able to see the switch.

[jereze93]

I AM MUSIC

[BMWGUYinCO]

Originally Posted by zx10guy

Is it bad that I can relate to this meme and partially recognize the actual switch being pictured? It's either a Cisco Catalyst 4500 or 6500. Worked on plenty of them back in the day.

I could have created some interesting memes back in the day if I had the ability to take pics. Some of the things I saw were just mind blowing. One was when I had to locate a 6509 switch at a data center. Walked the aisle a number of times and couldn't find it. I finally did when I spread open a literal curtain of cables that blocked me being able to see the switch.

I've mentioned this before, but I'm a Chief Technology Officer in Healthcare. About 5 years ago, I was touring some hospitals that had their "data center" within the basements of the actual hospital (I won't mention the hospital system but it is VERY large). And yes - not good to have the DC in the basement.
In any case, the wiring I saw would make a network engineer's eyes bleed; it was a spaghetti fest blown up by a nuclear bomb. At the time, I was trying to migrate their tech out of the basement and into a properly hosted data center.

I could tell you some stories that would make you never want to visit a hospital. I'll share one now though. The DC was in the basement directly below the dialysis center. One day, they experienced a leak that went through the floor and fell into exposed racks containing network hardware (Cisco Catalysts in fact). Aside from the emergency downtime, we had to have a hazmat crew come in to clean and remove contaminated equipment since the leak contained toxic organics. I don't know who originally set up the compute infrastructure in these places, but they certainly didn't know or think about what they were doing.

[zx10guy]

Originally Posted by BMWGUYinCO

I've mentioned this before, but I'm a Chief Technology Officer in Healthcare. About 5 years ago, I was touring some hospitals that had their "data center" within the basements of the actual hospital (I won't mention the hospital system but it is VERY large). And yes - not good to have the DC in the basement.
In any case, the wiring I saw would make a network engineer's eyes bleed; it was a spaghetti fest blown up by a nuclear bomb. At the time, I was trying to migrate their tech out of the basement and into a properly hosted data center.

I could tell you some stories that would make you never want to visit a hospital. I'll share one now though. The DC was in the basement directly below the dialysis center. One day, they experienced a leak that went through the floor and fell into exposed racks containing network hardware (Cisco Catalysts in fact). Aside from the emergency downtime, we had to have a hazmat crew come in to clean and remove contaminated equipment since the leak contained toxic organics. I don't know who originally set up the compute infrastructure in these places, but they certainly didn't know or think about what they were doing.

Yep. Similar experiences. One where someone didn't think it was a bad idea to have an overhead chiller not be over a rack of EMC storage. Murphy came to visit one day and the entire array was literally toast.

Another situation similar to yours with the DC in the basement of the hospital. The place I was in decided to build the DC in what was formerly the parking garage for the building. Well, they didn't account for two things. One was the slope of the ground floor which caused inconsistent cooling from the pressurized raised floor from one end of the DC to the other. And the other issue which was the flooding that would occur during significant rain storms.

Another was the guys that worked under me. I had to go back and recheck their work when they ran cabling. One just ran a twisted pair copper Ethernet cable through the front of the rack to the next one and smashed the door onto the cable not caring how the door was physically crimping the cable. The other was how one of the guys didn't care about proper bend radius of the fiber cable in a rack. I happened to look over and saw light bleeding through the fiber at the bend that was too tight ran by one of my guys.

Another was someone didn't want to go through proper channels to set up a network path between two segments of the network. So they just connected a home router to bridge the networks. All heck broke loose on that one as the person created a cross contamination violation by doing an unauthorized bridging of a network at a higher classification level to one at a lower one.

And those weren't the worst of the ones I've encountered. One that comes to mind I can't speak of but would piss off any IT person that cares anything about security.

[spazzyfry123]

Originally Posted by BMWGUYinCO

I've mentioned this before, but I'm a Chief Technology Officer in Healthcare. About 5 years ago, I was touring some hospitals that had their "data center" within the basements of the actual hospital (I won't mention the hospital system but it is VERY large). And yes - not good to have the DC in the basement.
In any case, the wiring I saw would make a network engineer's eyes bleed; it was a spaghetti fest blown up by a nuclear bomb. At the time, I was trying to migrate their tech out of the basement and into a properly hosted data center.

I could tell you some stories that would make you never want to visit a hospital. I'll share one now though. The DC was in the basement directly below the dialysis center. One day, they experienced a leak that went through the floor and fell into exposed racks containing network hardware (Cisco Catalysts in fact). Aside from the emergency downtime, we had to have a hazmat crew come in to clean and remove contaminated equipment since the leak contained toxic organics. I don't know who originally set up the compute infrastructure in these places, but they certainly didn't know or think about what they were doing.

Funny enough I come from healthcare, but in engineering for "big iron" medical equipment OEM. Weird circle to be in Ag today, but here we are.

It is nuts what some facilities are using and downright spooky what gets a pass for patient use - especially with the cost of healthcare!

[3.0L]

.

[dumptruck]

This has become the pun thread lol