Timeline for Fix our Cisco switch overwhelmed by console logging
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2019 at 3:01 | history | tweeted | twitter.com/StackNetworkEng/status/1081385100565192704 | ||
| Jul 26, 2018 at 19:26 | history | edited | Mike Pennington | CC BY-SA 4.0 | edited tags; edited title |
| Jul 26, 2018 at 18:47 | comment | added | Spcaeyob | @Cown: Not homework. Work-work and I just started with this setup this morning. Absolutely agree, but my instructions were clearly stated beforehand: I was not allowed to power down the device, and the only configured auth method was user/pass combo. | |
| Jul 26, 2018 at 18:43 | vote | accept | Spcaeyob | ||
| Jul 26, 2018 at 16:08 | answer | added | Mike Pennington | timeline score: 7 | |
| Jul 26, 2018 at 9:59 | comment | added | JFL | To follow up on Cown comment. If a system is redundant you should put it down from time to time to ensure the redundancy works as expected. If you don't, the day you need it, it will not work. | |
| Jul 26, 2018 at 9:15 | review | Close votes | |||
| Jul 26, 2018 at 14:03 | |||||
| Jul 26, 2018 at 9:05 | comment | added | user36472 | It's funny how it's "redundant", but you can't plan a service window to fix the problem? I've never seen a system so important, combined with the fact it's redundant, that cannot be put into maintenance. | |
| Jul 26, 2018 at 8:57 | comment | added | user36472 | Is this a homework question? | |
| Jul 26, 2018 at 8:45 | review | First posts | |||
| Jul 27, 2018 at 3:08 | |||||
| Jul 26, 2018 at 8:43 | history | asked | Spcaeyob | CC BY-SA 4.0 |