Noooooooooooooooooooooooo       😕 ... View more

Hi ,   We recently upgraded from MS 14 to MS 17 and we encountered something special. Switches in a stack won't generate STP logs unless they are the active switch of a stack.   MS 14  :       MS 17 :   When I filter the Event Log with the switch name :        When I don't filter the logs , the logs are present (RSTP) :     In all 3 screenshots , the only action taken was to port cycle a client on switch -2 which is not the active/master switch of the stack. The syslog also indicates that the log seen from screenshot #3 is SENT by the active switch but displayed by the switch -2 from the dashboard. That's why it disapears when filtering with the specific switch from dashboard. .118 is switch #2 .159 is the active switch of the stack   The inital reply I got from engineering  : this is an expected behavior on the MS switches since firmware release MS15. So, the STP logs will only be generated on the active stack member switch. So, consider this as expected behavior that the non-active switch stack members will not be reporting any STP logs   Please note that these logs are being reported on the primary switch stack member switch 5 and the filter should not be applied for switch-2.      We love the extra confusion.         ... View more

General important notes MS17 introduces a change to the default login credentials for the device local status page, using "admin" as the username, and the device serial number (upper case with dashes) as the password Networks configured to run MS 17.2.1.1 will not upgrade MS22, MS42, MS220, or MS320 switches. Instead, those switches will remain on their previously configured firmware version. Ms12x important notes MS 16 introduced DAI on MS100 series platforms. If you are upgrading to a current release from MS 15 or earlier please ensure trusted ports and/or DAI-allow lists are configured prior to upgrading. New feature highlights DOM (Digital Optical Monitoring) Intelligent Capture RSPAN and VLAN Based SPAN SmartPorts New ms130x feature highlights Adaptive Policy on MS130X/R models New ms150 feature highlights Static routing on all MS150 models General fixed issues All new LAG configurations will block redundant links if the connected device is not configured for LACP. This change fixes an issue where switches would sometimes move LAG ports to an active forwarding state prior to LACP convergence, creating the potential for loops. The change does not apply to existing LAG configurations. Corrected the Local Status Page to show the 1 Gbps (forced) option, previously mislabeled as 1 Gbps (auto) Fixed a bug that caused some clients using Hybrid, 802.1X, or MAB Access Policies to fail to authenticate after a switch reboot Port-bounce CoA commands now correctly cycle PoE ports Resolved an issue that caused some clients to be incorrectly added to a configured Guest VLAN when authenticated via RADIUS immediately after a switch reboot Resolved an issue that prevented some MS210 and MS225 devices from correctly releasing MAC addresses from the MAC forwarding table Resolved an issue that sometimes caused MS350 switches to remove existing L3 SVIs when enabling Auto-stacking Ms120 fixed issues Fixed a bug that prevented MS120-48 switches from correctly forwarding multicast traffic on ports 25-48 Resolved a bug that caused Epson POS printers to fail to authenticate when using MAB hybrid auth access policies Ms12x fixed issues Fixed an issue that prevented MS120 and MS125 switches from forwarding link-local multicast (224.0.0.x) traffic when 'Flood unknown multicast traffic' was disabled Ms130 fixed issues Fixed a bug that caused some MS130-X switches to experience slow upstream when connected directly to an MX device via an mGig port Ms150 fixed issues Resolved an issue that sometimes caused floods of unknown unicast packets when client MAC addresses migrated between physical ports Ms225 fixed issues Resolved an issue that caused some MS225-48FP devices to become unresponsive and fail to forward traffic until rebooted Ms350 fixed issues Fixed a bug that prevented cable tests from correctly functioning on mGig ports Ms35x fixed issues Resolved an issue that caused some MS350-24X and MS355 switches to fail to negotiate 802.3bt UPoE LLDP connections Ms4xx fixed issues Fixed a bug that incorrectly caused STP transitions when SFP modules were inserted/removed General known issues In rare circumstances switches may experience uplink instability when IPv6 link-local addresses are enabled. If this issue is encountered it can be resolved by enabling IPv6 RA Guard to block ICMPv6 neighbor discovery messages. LACP links may take up to two minutes to come back up when the Active Member of a stack reboots On MS250 and MS350 switches, MAC addresses learned via AGGR are not removed when LAG ports are disabled. Mac addresses will be removed correctly within 5 minutes of reenabling LAG ports. RADIUS communications may not recover after an initial failure when Critical Auth is enabled Some switches may encounter an error, "incompatible configuration for attributes: allowed_vlans" when attempting to aggregate ports regardless of allowed VLANs configured in Dashboard Ms120 known issues Switches may fail to provide PoE power to legacy access points (always present) Ms150 known issues Client MAC addresses changing physical ports may cause a flood of unknown unicast packets to the source port on MS150-48 switches Ms220 known issues Client devices connected to ports 24-48 on MS220-48LP switches may have their DHCP offers and ARP replies erroneously dropped Ms225 known issues MS225 switches may infrequently stop forwarding client traffic until the switch is rebooted In rare circumstances MS225 switches may encounter a software crash that results in a reboot Ms250 known issues In rare circumstances MS250 switches using Multi-Domain Hybrid auth access policies may enter a 'port not forwarding' state, sending clients to the Guest VLAN until the switch is rebooted Ms355 known issues When reconnecting a stack cable between MS355-48X2 swithces a stack member may go offline until both switches are rebooted Ms35x known issues In rare instances, stack ports fail to initialize after an upgrade (always present) Incorrect SFP port mappings may disrupt SFP functionality Switches may experience an unexpected reboot (present since MS 15) Ms410 known issues Some MS410 switches may encounter alerts for fan failures that will eventually self-resolve Ms425 known issues In rare circumstances MS425 switches may encounter a software crash that results in a reboot MS425s in stack configurations may periodically trigger New DHCP Server alerts that include mismatched VLANs/subnets Powering off the active switch in a MS425 stack may result in up to 5 minutes of downtime while the stack reconverges ... View more

Hi ,   I have a task to determine the last activity of a 300K switchports eg: The last oper status change ( up / down ).    I don't see any endpoint to achieve that... I know some sketchy ways to do :   1- Fetch eventlogs and get RSTP / Port Status change event logs. Will take a while 2- Get Network clients , if no clients are seen on the port : the port never went up. Not 100% certain since some clients may not be detected     Any other creative painless way to achieve that ? ... View more