Switching

 View Only
last person joined: 2 days ago 

Ask questions and share experiences about EX and QFX portfolios and all switching solutions across your data center, campus, and branch locations.

jweb forces setting interface speed

  • 1.  jweb forces setting interface speed

    Posted 03-16-2021 21:19
    Hi,
    We have a fleet of EX2300 series PoE switches (12,24,48 port) running Junos 18.4R2-S5.4 (after a lot of testing to find a version which would run within the fitted flash and without bugs that impacted us).
    These are also running jweb 18.4A2 which appears to still be the latest. Ironic that the switches nag about wanting to "update" to 18.4A1 at login !

    Previously we ran 15.x stream and had all interfaces running defaults for speed / negotiation / duplex. So for copper this meant up to 1Gbe, auto, auto.

    With the new jweb, whenever we modify an interface (say to add a description) we are forced to set a port speed. There is no option to leave it set to blank (per 15.x) or auto. We have been setting to 1g. My reading of the documents led me to believe that provided the "auto-negotiate" box is still ticked (it is) that this sets the *maximum* rate advertised but allows auto-negotiate to occur with the connected device.

    Unfortunately this does not appear to be the case as 100Mb devices fail to link.

    We use the jweb primarily so that Servicedesk staff can document connections so want to reduce what they are changing - and pre-populated the template with speed of 1g on all ports with speed 1g;

    Does anyone know how we can revert to the 15.x behaviour or stop jweb from forcing us to set a speed whenever we touch an interface or have the interfaces set to 1g do auto-negotiate properly for slower devices ?

    ------------------------------
    TIA
    Ian Blackwood
    ------------------------------