Looks like our peering dropped and did not re-establish about 1:30p on the 19th with all our MICE peers. Did I miss a critical configuration change that we needed to adopt in our config as a result of the switch-port migrations that have recently concluded? I am also noticing BPDUs showing up on our interface where before the migration, there were none. Thanks in advance for helping point me in the right direction here! * Dan H. Confidentiality Notice: Information contained in this e-mail is being sent to you after appropriate authorization or by legal exception. You are obligated to maintain it in a safe, secure and confidential manner. Re-disclosure without patient consent or as permitted by law is prohibited and may subject you to state and/or federal penalties. This information may also be legally privileged, the disclosure of which is governed by law. This information is intended for the use of the person or entity to which it is addressed. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any access, disclosure, copying or distribution of this information is strictly prohibited. If you have received this message by error, please notify the sender immediately to arrange for return or proof of destruction of the information contained in this message.
Daniel, I see the port is up, however we are not learning a MAC address from you: core-sw0(s1)#sh int e 4/35 Ethernet4/35 is up, line protocol is up (connected) Hardware is Ethernet, address is 444c.a8e6.5326 (bia 444c.a8e6.5326) Description: HCMC 40413 Ethernet MTU 10178 bytes, Ethernet MRU 10200 bytes, BW 10000000 kbit Full-duplex, 10Gb/s, auto negotiation: off, uni-link: disabled Up 4 days, 1 hour, 31 minutes, 8 seconds Loopback Mode : None 5 link status changes since last clear Last clearing of "show interface" counters never 5 minutes input rate 0 bps (0.0% with framing overhead), 0 packets/sec 5 minutes output rate 61.0 kbps (0.0% with framing overhead), 94 packets/sec 0 packets input, 0 bytes Received 0 broadcasts, 0 multicast 0 runts, 0 giants 0 input errors, 0 CRC, 0 alignment, 0 symbol, 0 input discards 0 PAUSE input 181316240 packets output, 44157130837 bytes Sent 18266385 broadcasts, 28825106 multicast 0 output errors, 0 collisions 0 late collision, 0 deferred, 3213 output discards 0 PAUSE output core-sw0(s1)#sh mac address-t e 4/35 % Invalid input core-sw0(s1)#sh mac address-t int e 4/35 Mac Address Table ------------------------------------------------------------------ Vlan Mac Address Type Ports Moves Last Move ---- ----------- ---- ----- ----- --------- Total Mac Addresses for this criterion: 0 Jeremy From: Huwe, Daniel <Daniel.Huwe@hcmed.org> Sent: Tuesday, March 25, 2025 8:52 AM To: mice-discuss@lists.micemn.net Subject: HCMC (AS 40413) Lost Peering on 03-19-2025 Looks like our peering dropped and did not re-establish about 1:30p on the 19th with all our MICE peers. Did I miss a critical configuration change that we needed to adopt in our config as a result of the switch-port migrations that have recently concluded? I am also noticing BPDUs showing up on our interface where before the migration, there were none. Thanks in advance for helping point me in the right direction here! * Dan H. Confidentiality Notice: Information contained in this e-mail is being sent to you after appropriate authorization or by legal exception. You are obligated to maintain it in a safe, secure and confidential manner. Re-disclosure without patient consent or as permitted by law is prohibited and may subject you to state and/or federal penalties. This information may also be legally privileged, the disclosure of which is governed by law. This information is intended for the use of the person or entity to which it is addressed. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any access, disclosure, copying or distribution of this information is strictly prohibited. If you have received this message by error, please notify the sender immediately to arrange for return or proof of destruction of the information contained in this message.
OK, I see it now, and I concur, this is a me problem. I'll need to swing out to the data center and figure this one out. Thanks! * Dan H. From: Jeremy Lumby <jlumby@mnvoip.com> Sent: Tuesday, March 25, 2025 8:56 AM To: Huwe, Daniel <Daniel.Huwe@hcmed.org>; mice-discuss@lists.micemn.net Subject: [EXTERNAL] RE: HCMC (AS 40413) Lost Peering on 03-19-2025 CAUTION: This email originated from outside of HCMC. DO NOT CLICK links or open attachments unless you recognize the sender and know the content is safe. Daniel, I see the port is up, however we are not learning a MAC address from you: core-sw0(s1)#sh int e 4/35 Ethernet4/35 is up, line protocol is up (connected) Hardware is Ethernet, address is 444c.a8e6.5326 (bia 444c.a8e6.5326) Description: HCMC 40413 Ethernet MTU 10178 bytes, Ethernet MRU 10200 bytes, BW 10000000 kbit Full-duplex, 10Gb/s, auto negotiation: off, uni-link: disabled Up 4 days, 1 hour, 31 minutes, 8 seconds Loopback Mode : None 5 link status changes since last clear Last clearing of "show interface" counters never 5 minutes input rate 0 bps (0.0% with framing overhead), 0 packets/sec 5 minutes output rate 61.0 kbps (0.0% with framing overhead), 94 packets/sec 0 packets input, 0 bytes Received 0 broadcasts, 0 multicast 0 runts, 0 giants 0 input errors, 0 CRC, 0 alignment, 0 symbol, 0 input discards 0 PAUSE input 181316240 packets output, 44157130837 bytes Sent 18266385 broadcasts, 28825106 multicast 0 output errors, 0 collisions 0 late collision, 0 deferred, 3213 output discards 0 PAUSE output core-sw0(s1)#sh mac address-t e 4/35 % Invalid input core-sw0(s1)#sh mac address-t int e 4/35 Mac Address Table ------------------------------------------------------------------ Vlan Mac Address Type Ports Moves Last Move ---- ----------- ---- ----- ----- --------- Total Mac Addresses for this criterion: 0 Jeremy From: Huwe, Daniel <Daniel.Huwe@hcmed.org<mailto:Daniel.Huwe@hcmed.org>> Sent: Tuesday, March 25, 2025 8:52 AM To: mice-discuss@lists.micemn.net<mailto:mice-discuss@lists.micemn.net> Subject: HCMC (AS 40413) Lost Peering on 03-19-2025 Looks like our peering dropped and did not re-establish about 1:30p on the 19th with all our MICE peers. Did I miss a critical configuration change that we needed to adopt in our config as a result of the switch-port migrations that have recently concluded? I am also noticing BPDUs showing up on our interface where before the migration, there were none. Thanks in advance for helping point me in the right direction here! * Dan H. Confidentiality Notice: Information contained in this e-mail is being sent to you after appropriate authorization or by legal exception. You are obligated to maintain it in a safe, secure and confidential manner. Re-disclosure without patient consent or as permitted by law is prohibited and may subject you to state and/or federal penalties. This information may also be legally privileged, the disclosure of which is governed by law. This information is intended for the use of the person or entity to which it is addressed. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any access, disclosure, copying or distribution of this information is strictly prohibited. If you have received this message by error, please notify the sender immediately to arrange for return or proof of destruction of the information contained in this message. Confidentiality Notice: Information contained in this e-mail is being sent to you after appropriate authorization or by legal exception. You are obligated to maintain it in a safe, secure and confidential manner. Re-disclosure without patient consent or as permitted by law is prohibited and may subject you to state and/or federal penalties. This information may also be legally privileged, the disclosure of which is governed by law. This information is intended for the use of the person or entity to which it is addressed. If you are not the intended recipient, or the employee or agent responsible for delivering it to the intended recipient, you are hereby notified that any access, disclosure, copying or distribution of this information is strictly prohibited. If you have received this message by error, please notify the sender immediately to arrange for return or proof of destruction of the information contained in this message.
participants (2)
-
Huwe, Daniel -
Jeremy Lumby