| 733 | * Approximately 50 times a day during the period of e-mail sending, we have gotten four messages like these: |
| 734 | * 8052/Ethernet40 is down: |
| 735 | {{{ |
| 736 | From: rack_bbn@bbn-hn.exogeni.net (OMD site rack_bbn) |
| 737 | Date: Wed, 23 May 2012 16:29:52 +0000 |
| 738 | To: chaos@bbn.com |
| 739 | Subject: *** PROBLEM *** 8052.bbn.xo / Interface Ethernet40 is CRITICAL |
| 740 | |
| 741 | --SERVICE-ALERT------------------- |
| 742 | - |
| 743 | - Hostaddress: 192.168.103.2 |
| 744 | - Hostname: 8052.bbn.xo |
| 745 | - Service: Interface Ethernet40 |
| 746 | - - - - - - - - - - - - - - - - - |
| 747 | - State: CRITICAL |
| 748 | - Date: 2012-05-23 16:29:52 |
| 749 | - Output: CRIT - [168] (down)(!!) assuming 1GBit/s, in: 0.00B/s(0.0%), out: 68.91B/s(0.0%) |
| 750 | - |
| 751 | ---------------------------------- |
| 752 | }}} |
| 753 | * 8052/Ethernet30 is down: |
| 754 | {{{ |
| 755 | From: rack_bbn@bbn-hn.exogeni.net (OMD site rack_bbn) |
| 756 | Date: Wed, 23 May 2012 16:30:52 +0000 |
| 757 | To: chaos@bbn.com |
| 758 | Subject: *** PROBLEM *** 8052.bbn.xo / Interface Ethernet30 is CRITICAL |
| 759 | |
| 760 | --SERVICE-ALERT------------------- |
| 761 | - |
| 762 | - Hostaddress: 192.168.103.2 |
| 763 | - Hostname: 8052.bbn.xo |
| 764 | - Service: Interface Ethernet30 |
| 765 | - - - - - - - - - - - - - - - - - |
| 766 | - State: CRITICAL |
| 767 | - Date: 2012-05-23 16:30:52 |
| 768 | - Output: CRIT - [158] (down)(!!) assuming 1GBit/s, in: 0.00B/s(0.0%), out: 32.07B/s(0.0%) |
| 769 | - |
| 770 | ---------------------------------- |
| 771 | }}} |
| 772 | * 8052/Ethernet40 is back up: |
| 773 | {{{ |
| 774 | From: rack_bbn@bbn-hn.exogeni.net (OMD site rack_bbn) |
| 775 | Date: Wed, 23 May 2012 16:31:52 +0000 |
| 776 | To: chaos@bbn.com |
| 777 | Subject: *** RECOVERY *** 8052.bbn.xo / Interface Ethernet40 is OK |
| 778 | |
| 779 | --SERVICE-ALERT------------------- |
| 780 | - |
| 781 | - Hostaddress: 192.168.103.2 |
| 782 | - Hostname: 8052.bbn.xo |
| 783 | - Service: Interface Ethernet40 |
| 784 | - - - - - - - - - - - - - - - - - |
| 785 | - State: OK |
| 786 | - Date: 2012-05-23 16:31:52 |
| 787 | - Output: OK - [168] (up) 1GBit/s, in: 29.71B/s(0.0%), out: 73.21B/s(0.0%) |
| 788 | - |
| 789 | ---------------------------------- |
| 790 | }}} |
| 791 | * 8052/Ethernet30 is back up: |
| 792 | {{{ |
| 793 | From: rack_bbn@bbn-hn.exogeni.net (OMD site rack_bbn) |
| 794 | Date: Wed, 23 May 2012 16:31:52 +0000 |
| 795 | To: chaos@bbn.com |
| 796 | Subject: *** RECOVERY *** 8052.bbn.xo / Interface Ethernet30 is OK |
| 797 | |
| 798 | --SERVICE-ALERT------------------- |
| 799 | - |
| 800 | - Hostaddress: 192.168.103.2 |
| 801 | - Hostname: 8052.bbn.xo |
| 802 | - Service: Interface Ethernet30 |
| 803 | - - - - - - - - - - - - - - - - - |
| 804 | - State: OK |
| 805 | - Date: 2012-05-23 16:31:52 |
| 806 | - Output: OK - [158] (up) 1GBit/s, in: 0.00B/s(0.0%), out: 30.94B/s(0.0%) |
| 807 | - |
| 808 | ---------------------------------- |
| 809 | }}} |
| 810 | * Based on the information i was able to put together in our connection inventory so far doing step 4C, it appears that `Ethernet30` is `bbn-w4[eth1]`, and `Ethernet40` is `bbn-w4[eth0]`. We know that bbn-w4 is the xCAT worker, and apparently it resets every time it can't PXE boot. So that's what all of that is about. |