Network questions Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern) Announcing the arrival of Valued Associate #679: Cesar Manara Unicorn Meta Zoo #1: Why another podcast?How is IEEE 802.1ad (aka VLAN Tagging, QinQ) valid, when the packets are too large?VLAN ConfirmationDell N2000: switch will not respond on configured in-band IPReview of network connectivity diagramConfigure VLAN on Cisco SG-200 switch connected to a Meraki switch/networkEX3300: Voice VLAN stopped working after upgrade to 15.1R6.7Splitting network between guests and production clientsIntermittently loose communication with upstream managed switchMultiple VLAN setup questionsQuestions about VLANs
What's the difference between using dependency injection with a container and using a service locator?
Does using the Inspiration rules for character defects encourage My Guy Syndrome?
Determine the generator of an ideal of ring of integers
Continue tikz picture on next page
Marquee sign letters
Why do C and C++ allow the expression (int) + 4*5?
Is my guitar’s action too high?
Why did Israel vote against lifting the American embargo on Cuba?
Why is one lightbulb in a string illuminated?
A German immigrant ancestor has a "Registration Affidavit of Alien Enemy" on file. What does that mean exactly?
When speaking, how do you change your mind mid-sentence?
Is there a verb for listening stealthily?
Are Flameskulls resistant to magical piercing damage?
Are there any AGPL-style licences that require source code modifications to be public?
false 'Security alert' from Google - every login generates mails from 'no-reply@accounts.google.com'
How to charge percentage of transaction cost?
2 sample t test for sample sizes - 30,000 and 150,000
Is "ein Herz wie das meine" an antiquated or colloquial use of the possesive pronoun?
Pointing to problems without suggesting solutions
Weaponising the Grasp-at-a-Distance spell
Putting Ant-Man on house arrest
Can I ask an author to send me his ebook?
How to get a single big right brace?
Unix AIX passing variable and arguments to expect and spawn
Network questions
Planned maintenance scheduled April 23, 2019 at 23:30 UTC (7:30pm US/Eastern)
Announcing the arrival of Valued Associate #679: Cesar Manara
Unicorn Meta Zoo #1: Why another podcast?How is IEEE 802.1ad (aka VLAN Tagging, QinQ) valid, when the packets are too large?VLAN ConfirmationDell N2000: switch will not respond on configured in-band IPReview of network connectivity diagramConfigure VLAN on Cisco SG-200 switch connected to a Meraki switch/networkEX3300: Voice VLAN stopped working after upgrade to 15.1R6.7Splitting network between guests and production clientsIntermittently loose communication with upstream managed switchMultiple VLAN setup questionsQuestions about VLANs
I have been asked to come up with a plan for upgrading old switches to new.
vlan
add a comment |
I have been asked to come up with a plan for upgrading old switches to new.
vlan
Hello A Culver and welcome. Is this a real life hospital and ICU?
– jonathanjo
8 hours ago
2
Welcome to NE, we hope you will both contribute to and learn from this community. Please do not vandalize your own posts. It is not helpful in any way. You can always delete your own posts by using the "delete" link. This takes less effort for both you and users of the site. Deleted posts cannot be viewed unless a user has over 10k reputation on that site and if a user can view the deleted post, they can also see a history of the edits/versions of the post.
– YLearn♦
1 hour ago
I need to delete this question ASAP.
– A Culver
54 mins ago
add a comment |
I have been asked to come up with a plan for upgrading old switches to new.
vlan
I have been asked to come up with a plan for upgrading old switches to new.
vlan
vlan
edited 1 hour ago
A Culver
asked 9 hours ago
A CulverA Culver
316
316
Hello A Culver and welcome. Is this a real life hospital and ICU?
– jonathanjo
8 hours ago
2
Welcome to NE, we hope you will both contribute to and learn from this community. Please do not vandalize your own posts. It is not helpful in any way. You can always delete your own posts by using the "delete" link. This takes less effort for both you and users of the site. Deleted posts cannot be viewed unless a user has over 10k reputation on that site and if a user can view the deleted post, they can also see a history of the edits/versions of the post.
– YLearn♦
1 hour ago
I need to delete this question ASAP.
– A Culver
54 mins ago
add a comment |
Hello A Culver and welcome. Is this a real life hospital and ICU?
– jonathanjo
8 hours ago
2
Welcome to NE, we hope you will both contribute to and learn from this community. Please do not vandalize your own posts. It is not helpful in any way. You can always delete your own posts by using the "delete" link. This takes less effort for both you and users of the site. Deleted posts cannot be viewed unless a user has over 10k reputation on that site and if a user can view the deleted post, they can also see a history of the edits/versions of the post.
– YLearn♦
1 hour ago
I need to delete this question ASAP.
– A Culver
54 mins ago
Hello A Culver and welcome. Is this a real life hospital and ICU?
– jonathanjo
8 hours ago
Hello A Culver and welcome. Is this a real life hospital and ICU?
– jonathanjo
8 hours ago
2
2
Welcome to NE, we hope you will both contribute to and learn from this community. Please do not vandalize your own posts. It is not helpful in any way. You can always delete your own posts by using the "delete" link. This takes less effort for both you and users of the site. Deleted posts cannot be viewed unless a user has over 10k reputation on that site and if a user can view the deleted post, they can also see a history of the edits/versions of the post.
– YLearn♦
1 hour ago
Welcome to NE, we hope you will both contribute to and learn from this community. Please do not vandalize your own posts. It is not helpful in any way. You can always delete your own posts by using the "delete" link. This takes less effort for both you and users of the site. Deleted posts cannot be viewed unless a user has over 10k reputation on that site and if a user can view the deleted post, they can also see a history of the edits/versions of the post.
– YLearn♦
1 hour ago
I need to delete this question ASAP.
– A Culver
54 mins ago
I need to delete this question ASAP.
– A Culver
54 mins ago
add a comment |
2 Answers
2
active
oldest
votes
I will start by assuming that there is enough room and power in the IDFs to rack the new switches along with the old ones. If this is not the case, STOP RIGHT HERE. Three hours is waaaay too short a change window to remove and replace the switches. You will have to come up with a plan over multiple change windows to move one stack per window. Even then, you need to be sure you know exactly what is plugged in where.
You should configure the new switches "on the bench," meaning they should be fully configured and tested before you start moving cables.
To answer your specific questions:
What is the specific configuration on the switch so that some devices
would stay online as much as possible?
To minimize downtime, you need to have the old and new switches trunked together, so VLANs will exist on both old and new switches at the same time. Then, you can move cables one at a time from old to new.
Can I just reuse old configs from the old devices? what about the
PortChannel? can I use the same ones?
For the most part, the VLAN and interface configurations can probably stay the same, but I notice you have different number of switches in the old and new stacks, so some port numbers will change. There may be a few other things that may be hardware specific. If you post your configs, we can give you more detailed answer.
3
Just to add: if the cables aren't labeled yet you'd want to do that now.
– Zac67
7 hours ago
Another addition, one of the most important bench tests would be to power cycle and verify settings after. This should help to remember to save to flash, which has burnt me in the past.
– Ben
4 hours ago
add a comment |
In addition to the excellent answer about the switches themselves ...
Testing
Consider:
- Exactly what tests will qualify the new setup as satisfactory?
- Can you run the tests continuously?
- Can you do a practice run? (Perhaps without actually replugging anything)
- How long will it take you to reverse to the old equipment?
As examples, perhaps you can automate ping tests to your entire set of devices, and have that running continuously. Then, as each device moves from old to new, a brief failure will show, followed by recovery. If seeing that happen is just looking over to a screen, that's much quicker than having to sit and manually perform some tests.
What happens if it fails?
You've said the network is a hospital with an ICU.
Suppose it fails half-way through, for any reason whatsoever, the consequences for an ICU are very possibly life-threatening.
Things I'd consider:
- Do I have backup staff who can reverse to a known good state?
- Do I have a clear cut-off time to commit to the new equipment?
The reasons for the failure can be as unpredictable as network staff family or medical emergency, equipment theft, terrorist event -- all of which have happened to projects of mine. Never mind surprise equipment bugs or mistaken parameters and project underestimation.
Ground control
- Do I have a "ground control" person authourised to abort the cutover if they see it going wrong?
Nobody ever plans to get into the situation where the networking staff are over-tired and over-stressed and thing "just a few more minutes" will fix it. But it happens with surprising frequency. One way to avoid the threat of overwhelmed technical staff is to have a "ground control" person who knows the schedule and knows how and when to order a reverse to the known-good state. I put in measures like this on high-stress projects as mental health protection after seeing over-committed staff work until they dropped -- thankfully only large commercial and never medical projects. If they do that and fall asleep without proven project completion on mission critical projects it's awful costly. The more important the project, the more likely people will push themselves hard if it goes wrong, and many are unaware of their own endurance limits.
1
All excellent points. In addition, for critical equipment, you should verify satisfactory operation of each device as it is moved to the new switches before moving on the the next one.
– Ron Trunk
6 hours ago
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "496"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f58641%2fnetwork-questions%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
I will start by assuming that there is enough room and power in the IDFs to rack the new switches along with the old ones. If this is not the case, STOP RIGHT HERE. Three hours is waaaay too short a change window to remove and replace the switches. You will have to come up with a plan over multiple change windows to move one stack per window. Even then, you need to be sure you know exactly what is plugged in where.
You should configure the new switches "on the bench," meaning they should be fully configured and tested before you start moving cables.
To answer your specific questions:
What is the specific configuration on the switch so that some devices
would stay online as much as possible?
To minimize downtime, you need to have the old and new switches trunked together, so VLANs will exist on both old and new switches at the same time. Then, you can move cables one at a time from old to new.
Can I just reuse old configs from the old devices? what about the
PortChannel? can I use the same ones?
For the most part, the VLAN and interface configurations can probably stay the same, but I notice you have different number of switches in the old and new stacks, so some port numbers will change. There may be a few other things that may be hardware specific. If you post your configs, we can give you more detailed answer.
3
Just to add: if the cables aren't labeled yet you'd want to do that now.
– Zac67
7 hours ago
Another addition, one of the most important bench tests would be to power cycle and verify settings after. This should help to remember to save to flash, which has burnt me in the past.
– Ben
4 hours ago
add a comment |
I will start by assuming that there is enough room and power in the IDFs to rack the new switches along with the old ones. If this is not the case, STOP RIGHT HERE. Three hours is waaaay too short a change window to remove and replace the switches. You will have to come up with a plan over multiple change windows to move one stack per window. Even then, you need to be sure you know exactly what is plugged in where.
You should configure the new switches "on the bench," meaning they should be fully configured and tested before you start moving cables.
To answer your specific questions:
What is the specific configuration on the switch so that some devices
would stay online as much as possible?
To minimize downtime, you need to have the old and new switches trunked together, so VLANs will exist on both old and new switches at the same time. Then, you can move cables one at a time from old to new.
Can I just reuse old configs from the old devices? what about the
PortChannel? can I use the same ones?
For the most part, the VLAN and interface configurations can probably stay the same, but I notice you have different number of switches in the old and new stacks, so some port numbers will change. There may be a few other things that may be hardware specific. If you post your configs, we can give you more detailed answer.
3
Just to add: if the cables aren't labeled yet you'd want to do that now.
– Zac67
7 hours ago
Another addition, one of the most important bench tests would be to power cycle and verify settings after. This should help to remember to save to flash, which has burnt me in the past.
– Ben
4 hours ago
add a comment |
I will start by assuming that there is enough room and power in the IDFs to rack the new switches along with the old ones. If this is not the case, STOP RIGHT HERE. Three hours is waaaay too short a change window to remove and replace the switches. You will have to come up with a plan over multiple change windows to move one stack per window. Even then, you need to be sure you know exactly what is plugged in where.
You should configure the new switches "on the bench," meaning they should be fully configured and tested before you start moving cables.
To answer your specific questions:
What is the specific configuration on the switch so that some devices
would stay online as much as possible?
To minimize downtime, you need to have the old and new switches trunked together, so VLANs will exist on both old and new switches at the same time. Then, you can move cables one at a time from old to new.
Can I just reuse old configs from the old devices? what about the
PortChannel? can I use the same ones?
For the most part, the VLAN and interface configurations can probably stay the same, but I notice you have different number of switches in the old and new stacks, so some port numbers will change. There may be a few other things that may be hardware specific. If you post your configs, we can give you more detailed answer.
I will start by assuming that there is enough room and power in the IDFs to rack the new switches along with the old ones. If this is not the case, STOP RIGHT HERE. Three hours is waaaay too short a change window to remove and replace the switches. You will have to come up with a plan over multiple change windows to move one stack per window. Even then, you need to be sure you know exactly what is plugged in where.
You should configure the new switches "on the bench," meaning they should be fully configured and tested before you start moving cables.
To answer your specific questions:
What is the specific configuration on the switch so that some devices
would stay online as much as possible?
To minimize downtime, you need to have the old and new switches trunked together, so VLANs will exist on both old and new switches at the same time. Then, you can move cables one at a time from old to new.
Can I just reuse old configs from the old devices? what about the
PortChannel? can I use the same ones?
For the most part, the VLAN and interface configurations can probably stay the same, but I notice you have different number of switches in the old and new stacks, so some port numbers will change. There may be a few other things that may be hardware specific. If you post your configs, we can give you more detailed answer.
answered 8 hours ago
Ron TrunkRon Trunk
40.1k33781
40.1k33781
3
Just to add: if the cables aren't labeled yet you'd want to do that now.
– Zac67
7 hours ago
Another addition, one of the most important bench tests would be to power cycle and verify settings after. This should help to remember to save to flash, which has burnt me in the past.
– Ben
4 hours ago
add a comment |
3
Just to add: if the cables aren't labeled yet you'd want to do that now.
– Zac67
7 hours ago
Another addition, one of the most important bench tests would be to power cycle and verify settings after. This should help to remember to save to flash, which has burnt me in the past.
– Ben
4 hours ago
3
3
Just to add: if the cables aren't labeled yet you'd want to do that now.
– Zac67
7 hours ago
Just to add: if the cables aren't labeled yet you'd want to do that now.
– Zac67
7 hours ago
Another addition, one of the most important bench tests would be to power cycle and verify settings after. This should help to remember to save to flash, which has burnt me in the past.
– Ben
4 hours ago
Another addition, one of the most important bench tests would be to power cycle and verify settings after. This should help to remember to save to flash, which has burnt me in the past.
– Ben
4 hours ago
add a comment |
In addition to the excellent answer about the switches themselves ...
Testing
Consider:
- Exactly what tests will qualify the new setup as satisfactory?
- Can you run the tests continuously?
- Can you do a practice run? (Perhaps without actually replugging anything)
- How long will it take you to reverse to the old equipment?
As examples, perhaps you can automate ping tests to your entire set of devices, and have that running continuously. Then, as each device moves from old to new, a brief failure will show, followed by recovery. If seeing that happen is just looking over to a screen, that's much quicker than having to sit and manually perform some tests.
What happens if it fails?
You've said the network is a hospital with an ICU.
Suppose it fails half-way through, for any reason whatsoever, the consequences for an ICU are very possibly life-threatening.
Things I'd consider:
- Do I have backup staff who can reverse to a known good state?
- Do I have a clear cut-off time to commit to the new equipment?
The reasons for the failure can be as unpredictable as network staff family or medical emergency, equipment theft, terrorist event -- all of which have happened to projects of mine. Never mind surprise equipment bugs or mistaken parameters and project underestimation.
Ground control
- Do I have a "ground control" person authourised to abort the cutover if they see it going wrong?
Nobody ever plans to get into the situation where the networking staff are over-tired and over-stressed and thing "just a few more minutes" will fix it. But it happens with surprising frequency. One way to avoid the threat of overwhelmed technical staff is to have a "ground control" person who knows the schedule and knows how and when to order a reverse to the known-good state. I put in measures like this on high-stress projects as mental health protection after seeing over-committed staff work until they dropped -- thankfully only large commercial and never medical projects. If they do that and fall asleep without proven project completion on mission critical projects it's awful costly. The more important the project, the more likely people will push themselves hard if it goes wrong, and many are unaware of their own endurance limits.
1
All excellent points. In addition, for critical equipment, you should verify satisfactory operation of each device as it is moved to the new switches before moving on the the next one.
– Ron Trunk
6 hours ago
add a comment |
In addition to the excellent answer about the switches themselves ...
Testing
Consider:
- Exactly what tests will qualify the new setup as satisfactory?
- Can you run the tests continuously?
- Can you do a practice run? (Perhaps without actually replugging anything)
- How long will it take you to reverse to the old equipment?
As examples, perhaps you can automate ping tests to your entire set of devices, and have that running continuously. Then, as each device moves from old to new, a brief failure will show, followed by recovery. If seeing that happen is just looking over to a screen, that's much quicker than having to sit and manually perform some tests.
What happens if it fails?
You've said the network is a hospital with an ICU.
Suppose it fails half-way through, for any reason whatsoever, the consequences for an ICU are very possibly life-threatening.
Things I'd consider:
- Do I have backup staff who can reverse to a known good state?
- Do I have a clear cut-off time to commit to the new equipment?
The reasons for the failure can be as unpredictable as network staff family or medical emergency, equipment theft, terrorist event -- all of which have happened to projects of mine. Never mind surprise equipment bugs or mistaken parameters and project underestimation.
Ground control
- Do I have a "ground control" person authourised to abort the cutover if they see it going wrong?
Nobody ever plans to get into the situation where the networking staff are over-tired and over-stressed and thing "just a few more minutes" will fix it. But it happens with surprising frequency. One way to avoid the threat of overwhelmed technical staff is to have a "ground control" person who knows the schedule and knows how and when to order a reverse to the known-good state. I put in measures like this on high-stress projects as mental health protection after seeing over-committed staff work until they dropped -- thankfully only large commercial and never medical projects. If they do that and fall asleep without proven project completion on mission critical projects it's awful costly. The more important the project, the more likely people will push themselves hard if it goes wrong, and many are unaware of their own endurance limits.
1
All excellent points. In addition, for critical equipment, you should verify satisfactory operation of each device as it is moved to the new switches before moving on the the next one.
– Ron Trunk
6 hours ago
add a comment |
In addition to the excellent answer about the switches themselves ...
Testing
Consider:
- Exactly what tests will qualify the new setup as satisfactory?
- Can you run the tests continuously?
- Can you do a practice run? (Perhaps without actually replugging anything)
- How long will it take you to reverse to the old equipment?
As examples, perhaps you can automate ping tests to your entire set of devices, and have that running continuously. Then, as each device moves from old to new, a brief failure will show, followed by recovery. If seeing that happen is just looking over to a screen, that's much quicker than having to sit and manually perform some tests.
What happens if it fails?
You've said the network is a hospital with an ICU.
Suppose it fails half-way through, for any reason whatsoever, the consequences for an ICU are very possibly life-threatening.
Things I'd consider:
- Do I have backup staff who can reverse to a known good state?
- Do I have a clear cut-off time to commit to the new equipment?
The reasons for the failure can be as unpredictable as network staff family or medical emergency, equipment theft, terrorist event -- all of which have happened to projects of mine. Never mind surprise equipment bugs or mistaken parameters and project underestimation.
Ground control
- Do I have a "ground control" person authourised to abort the cutover if they see it going wrong?
Nobody ever plans to get into the situation where the networking staff are over-tired and over-stressed and thing "just a few more minutes" will fix it. But it happens with surprising frequency. One way to avoid the threat of overwhelmed technical staff is to have a "ground control" person who knows the schedule and knows how and when to order a reverse to the known-good state. I put in measures like this on high-stress projects as mental health protection after seeing over-committed staff work until they dropped -- thankfully only large commercial and never medical projects. If they do that and fall asleep without proven project completion on mission critical projects it's awful costly. The more important the project, the more likely people will push themselves hard if it goes wrong, and many are unaware of their own endurance limits.
In addition to the excellent answer about the switches themselves ...
Testing
Consider:
- Exactly what tests will qualify the new setup as satisfactory?
- Can you run the tests continuously?
- Can you do a practice run? (Perhaps without actually replugging anything)
- How long will it take you to reverse to the old equipment?
As examples, perhaps you can automate ping tests to your entire set of devices, and have that running continuously. Then, as each device moves from old to new, a brief failure will show, followed by recovery. If seeing that happen is just looking over to a screen, that's much quicker than having to sit and manually perform some tests.
What happens if it fails?
You've said the network is a hospital with an ICU.
Suppose it fails half-way through, for any reason whatsoever, the consequences for an ICU are very possibly life-threatening.
Things I'd consider:
- Do I have backup staff who can reverse to a known good state?
- Do I have a clear cut-off time to commit to the new equipment?
The reasons for the failure can be as unpredictable as network staff family or medical emergency, equipment theft, terrorist event -- all of which have happened to projects of mine. Never mind surprise equipment bugs or mistaken parameters and project underestimation.
Ground control
- Do I have a "ground control" person authourised to abort the cutover if they see it going wrong?
Nobody ever plans to get into the situation where the networking staff are over-tired and over-stressed and thing "just a few more minutes" will fix it. But it happens with surprising frequency. One way to avoid the threat of overwhelmed technical staff is to have a "ground control" person who knows the schedule and knows how and when to order a reverse to the known-good state. I put in measures like this on high-stress projects as mental health protection after seeing over-committed staff work until they dropped -- thankfully only large commercial and never medical projects. If they do that and fall asleep without proven project completion on mission critical projects it's awful costly. The more important the project, the more likely people will push themselves hard if it goes wrong, and many are unaware of their own endurance limits.
answered 6 hours ago
jonathanjojonathanjo
12.4k1938
12.4k1938
1
All excellent points. In addition, for critical equipment, you should verify satisfactory operation of each device as it is moved to the new switches before moving on the the next one.
– Ron Trunk
6 hours ago
add a comment |
1
All excellent points. In addition, for critical equipment, you should verify satisfactory operation of each device as it is moved to the new switches before moving on the the next one.
– Ron Trunk
6 hours ago
1
1
All excellent points. In addition, for critical equipment, you should verify satisfactory operation of each device as it is moved to the new switches before moving on the the next one.
– Ron Trunk
6 hours ago
All excellent points. In addition, for critical equipment, you should verify satisfactory operation of each device as it is moved to the new switches before moving on the the next one.
– Ron Trunk
6 hours ago
add a comment |
Thanks for contributing an answer to Network Engineering Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fnetworkengineering.stackexchange.com%2fquestions%2f58641%2fnetwork-questions%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Hello A Culver and welcome. Is this a real life hospital and ICU?
– jonathanjo
8 hours ago
2
Welcome to NE, we hope you will both contribute to and learn from this community. Please do not vandalize your own posts. It is not helpful in any way. You can always delete your own posts by using the "delete" link. This takes less effort for both you and users of the site. Deleted posts cannot be viewed unless a user has over 10k reputation on that site and if a user can view the deleted post, they can also see a history of the edits/versions of the post.
– YLearn♦
1 hour ago
I need to delete this question ASAP.
– A Culver
54 mins ago