Hello fellow Juniperers,
I'm playing with some EX4550s as boxes for 1 and 10 Gbps breakouts. For uplinks I've installed the 2x QSFP expansion module in the front slot, and am using QSFP DACs.
In testing I noticed that whenever something is inserted into et-0/1/0, et-0/1/1 stops working for a brief moment. et-0/0/1 recovers as fast as it can, subject to whatever additional constraints. Tried with and without LAG, the interface set to disable, manipulating the other end, different firmwares on the transceivers, and tweaking config knobs. It does not seem to matter what sort of transceiver I connect into et-0/1/0, or even if it has link. I've tried "deleting" this as a VC port, and no commands show it considering the interfaces VC ports, so I don't think that's a problem. I tried a few different JUNOS releases in the 15.1R7 SR train. 12.3 is not an option for this hardware.
As far as redundancy goes this can be worked around but I'd prefer the switch to not break when optics are inserted...
Has anybody else on this list run into this before? If you haven't but you ARE running this module with both ports active, if you would mind sharing what software release you're on that would be extremely helpful!
Thanks!
Ross
--- Logs from when this happens. I think the logging on the switch is incomplete as afterwards et-0/1/1 is actually an active interface participating in ae0. The MX204 is reporting that properly ---
Sep 2 16:49:59 lab-mx204-2 kernel: lag_bundlestate_ifd_change: bundle ae0: bundle IFD minimum bandwidth or minimum links not met, Bandwidth (Current : Required) 0 : 40000000000 Number of links (Current : Required) 0 : 1
Sep 2 16:49:59 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_DOWN: ifIndex 575, ifAdminStatus up(1), ifOperStatus down(2), ifName ae0
Sep 2 16:49:59 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_DOWN: ifIndex 570, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/3
Sep 2 16:50:00 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 570, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/3
Sep 2 16:50:00 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 602, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/3.300
Sep 2 16:50:00 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 604, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/3.32767
Sep 2 16:50:02 lab-mx204-2 kernel: lag_bundlestate_ifd_change: bundle ae0 is now Up. uplinks 1 >= min_links 1
Sep 2 16:50:02 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 575, ifAdminStatus up(1), ifOperStatus up(1), ifName ae0
Sep 2 16:50:02 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 580, ifAdminStatus up(1), ifOperStatus up(1), ifName ae0.300
Sep 2 16:50:02 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 581, ifAdminStatus up(1), ifOperStatus up(1), ifName ae0.32767
Sep 2 16:50:06 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 599, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/1
Sep 2 16:50:06 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 601, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/1.300
Sep 2 16:50:06 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 603, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/1.32767
Sep 2 16:49:57 lab-ex4550-2 chassism[1279]: xcvr_is_qsfpplus DAC PASSIVE CABLE!!!!!!!
Sep 2 16:49:57 lab-ex4550-2 /kernel: drv_ge_misc_handler: ifd:155 new address:dc:38:e1:9c:69:43
Sep 2 16:49:57 lab-ex4550-2 /kernel: if_pfe_msg_send_vlan_data: peer ioctl message is NULL
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: PHY:MLD workaround passed for port:0, count:1, phy_id:0
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: PHY:MLD workaround passed for port:0, count:2, phy_id:1
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: PHY:MLD workaround passed for port:0, count:3, phy_id:2
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: PHY:MLD workaround passed for port:0, count:3, phy_id:3
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc419,for port:0, phy_id:0, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc41a,for port:0, phy_id:0, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc419,for port:0, phy_id:1, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc41a,for port:0, phy_id:1, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc419,for port:0, phy_id:2, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc41a,for port:0, phy_id:2, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc419,for port:0, phy_id:3, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc41a,for port:0, phy_id:3, value:0xc044
Sep 2 16:50:00 lab-ex4550-2 /kernel: ae_bundlestate_ifd_change: bundle ae0: bundle IFD minimum bandwidth or minimum links not met, Bandwidth (Current : Required) 0 : 1 Number of links (Current : Required) 0 : 1
Sep 2 16:50:00 lab-ex4550-2 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd et-0/1/1 - ATTACHED state - acting as standby link
Sep 2 16:50:00 lab-ex4550-2 mib2d[1355]: SNMP_TRAP_LINK_DOWN: ifIndex 507, ifAdminStatus up(1), ifOperStatus down(2), ifName ae0
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 182
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 182
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 /kernel: ae_linkstate_ifd_change: MUP received for interface et-0/1/0, member of ae0
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:02 lab-ex4550-2 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd et-0/1/1 - CD state - ready to carry traffic
Sep 2 16:50:02 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 178
Sep 2 16:50:03 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:06 lab-ex4550-2 last message repeated 2 times
Sep 2 16:50:08 lab-ex4550-2 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd et-0/1/0 - ATTACHED state - acting as standby link
Sep 2 16:50:08 lab-ex4550-2 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd et-0/1/0 - CD state - ready to carry traffic
Sep 2 16:50:08 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:08 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 178
Sep 2 16:50:08 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 178
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
I'm playing with some EX4550s as boxes for 1 and 10 Gbps breakouts. For uplinks I've installed the 2x QSFP expansion module in the front slot, and am using QSFP DACs.
In testing I noticed that whenever something is inserted into et-0/1/0, et-0/1/1 stops working for a brief moment. et-0/0/1 recovers as fast as it can, subject to whatever additional constraints. Tried with and without LAG, the interface set to disable, manipulating the other end, different firmwares on the transceivers, and tweaking config knobs. It does not seem to matter what sort of transceiver I connect into et-0/1/0, or even if it has link. I've tried "deleting" this as a VC port, and no commands show it considering the interfaces VC ports, so I don't think that's a problem. I tried a few different JUNOS releases in the 15.1R7 SR train. 12.3 is not an option for this hardware.
As far as redundancy goes this can be worked around but I'd prefer the switch to not break when optics are inserted...
Has anybody else on this list run into this before? If you haven't but you ARE running this module with both ports active, if you would mind sharing what software release you're on that would be extremely helpful!
Thanks!
Ross
--- Logs from when this happens. I think the logging on the switch is incomplete as afterwards et-0/1/1 is actually an active interface participating in ae0. The MX204 is reporting that properly ---
Sep 2 16:49:59 lab-mx204-2 kernel: lag_bundlestate_ifd_change: bundle ae0: bundle IFD minimum bandwidth or minimum links not met, Bandwidth (Current : Required) 0 : 40000000000 Number of links (Current : Required) 0 : 1
Sep 2 16:49:59 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_DOWN: ifIndex 575, ifAdminStatus up(1), ifOperStatus down(2), ifName ae0
Sep 2 16:49:59 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_DOWN: ifIndex 570, ifAdminStatus up(1), ifOperStatus down(2), ifName et-0/0/3
Sep 2 16:50:00 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 570, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/3
Sep 2 16:50:00 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 602, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/3.300
Sep 2 16:50:00 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 604, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/3.32767
Sep 2 16:50:02 lab-mx204-2 kernel: lag_bundlestate_ifd_change: bundle ae0 is now Up. uplinks 1 >= min_links 1
Sep 2 16:50:02 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 575, ifAdminStatus up(1), ifOperStatus up(1), ifName ae0
Sep 2 16:50:02 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 580, ifAdminStatus up(1), ifOperStatus up(1), ifName ae0.300
Sep 2 16:50:02 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 581, ifAdminStatus up(1), ifOperStatus up(1), ifName ae0.32767
Sep 2 16:50:06 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 599, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/1
Sep 2 16:50:06 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 601, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/1.300
Sep 2 16:50:06 lab-mx204-2 mib2d[22305]: SNMP_TRAP_LINK_UP: ifIndex 603, ifAdminStatus up(1), ifOperStatus up(1), ifName et-0/0/1.32767
Sep 2 16:49:57 lab-ex4550-2 chassism[1279]: xcvr_is_qsfpplus DAC PASSIVE CABLE!!!!!!!
Sep 2 16:49:57 lab-ex4550-2 /kernel: drv_ge_misc_handler: ifd:155 new address:dc:38:e1:9c:69:43
Sep 2 16:49:57 lab-ex4550-2 /kernel: if_pfe_msg_send_vlan_data: peer ioctl message is NULL
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: PHY:MLD workaround passed for port:0, count:1, phy_id:0
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: PHY:MLD workaround passed for port:0, count:2, phy_id:1
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: PHY:MLD workaround passed for port:0, count:3, phy_id:2
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: PHY:MLD workaround passed for port:0, count:3, phy_id:3
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc419,for port:0, phy_id:0, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc41a,for port:0, phy_id:0, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc419,for port:0, phy_id:1, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc41a,for port:0, phy_id:1, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc419,for port:0, phy_id:2, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc41a,for port:0, phy_id:2, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc419,for port:0, phy_id:3, value:0xc044
Sep 2 16:49:59 lab-ex4550-2 chassism[1279]: NLP:Reg:0xc41a,for port:0, phy_id:3, value:0xc044
Sep 2 16:50:00 lab-ex4550-2 /kernel: ae_bundlestate_ifd_change: bundle ae0: bundle IFD minimum bandwidth or minimum links not met, Bandwidth (Current : Required) 0 : 1 Number of links (Current : Required) 0 : 1
Sep 2 16:50:00 lab-ex4550-2 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd et-0/1/1 - ATTACHED state - acting as standby link
Sep 2 16:50:00 lab-ex4550-2 mib2d[1355]: SNMP_TRAP_LINK_DOWN: ifIndex 507, ifAdminStatus up(1), ifOperStatus down(2), ifName ae0
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 182
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 182
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 /kernel: ae_linkstate_ifd_change: MUP received for interface et-0/1/0, member of ae0
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:00 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:02 lab-ex4550-2 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd et-0/1/1 - CD state - ready to carry traffic
Sep 2 16:50:02 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 178
Sep 2 16:50:03 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:06 lab-ex4550-2 last message repeated 2 times
Sep 2 16:50:08 lab-ex4550-2 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd et-0/1/0 - ATTACHED state - acting as standby link
Sep 2 16:50:08 lab-ex4550-2 /kernel: KERN_LACP_INTF_STATE_CHANGE: lacp_update_state_userspace: cifd et-0/1/0 - CD state - ready to carry traffic
Sep 2 16:50:08 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 179
Sep 2 16:50:08 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 178
Sep 2 16:50:08 lab-ex4550-2 chassism[1279]: IFCM: no handler for command subtype 178
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp