Network Management

 View Only
last person joined: 2 days ago 

Keep an informative eye on your network with IMC and AirWave network management solutions.
Expand all | Collapse all

8212ZL switch

This thread has been viewed 25 times
  • 1.  8212ZL switch

    Posted Aug 10, 2022 02:19 AM
    I need help to troubleshoot my core switch 8212ZL.

    For few days i facing switch suddenly stuck or not responsive .

    1. MM faulty light blinks.
    2. All module 24port fiber and ethernet offline.

    I restart the switch after 10 minutes running normally then again stuck.

    I troubleshoot.

    1. I disconnect all ethernet cable except 1 module.
    2. Fiber same not disconnected.

    After restart the switch running but found.

    1. Fiber port excessive broadcasts detected
    2. Around 12 to 15 ethernet port found high collision or drop rate.

    This time switch not fully stuck but within 24 hours for 2 to 5 minute switch not responsive then normal.

    Still 4 module ethernet cable disconnected, this problem happen suddenly.


  • 2.  RE: 8212ZL switch

    MVP GURU
    Posted Aug 11, 2022 06:49 AM
    Hello, very difficult to guess what's happening by reading what you wrote: other relevant details are needed (switch logs, output of some - diagnostic related - show commands, software version and sanitized running configuration of your HP ProCurve 8212zl...network topology if you believe STP is kicking in for some reason). It could also be an Hardware related issue...but, again, no details means very difficult to guess what is causing the effects you're observing.





  • 3.  RE: 8212ZL switch

    Posted Aug 11, 2022 06:56 AM
    Currently all core switch ethernet port I relocated to separate 48 port switch, and fiber connectivity from core switch , I found no stuck, running normal, but when I revert back ethernet cable to core switch again stuck. Its a chance of load issue ? Because its running good , but for few days malfunction.

    Log high collision or drop rate I found.







  • 4.  RE: 8212ZL switch

    Posted Aug 11, 2022 01:46 PM
    I 01/03/90 18:21:44 00331 FFI: AM2: port J1-High collision or drop rate. See
    help.
    I 01/03/90 18:21:44 00331 FFI: AM2: port J2-High collision or drop rate. See
    help.
    I 01/03/90 18:21:44 00331 FFI: AM2: port J3-High collision or drop rate. See
    help.
    I 01/03/90 18:21:44 00331 FFI: AM2: port J4-High collision or drop rate. See
    help.
    I 01/03/90 18:21:44 00331 FFI: AM2: port J5-High collision or drop rate. See
    help.
    I 01/03/90 18:21:44 00331 FFI: AM2: port J6-High collision or drop rate. See
    help.
    I 01/03/90 18:21:44 00331 FFI: AM2: port J7-High collision or drop rate. See
    help.


    I 01/03/90 19:31:51 00828 lldp: AM2: PVID mismatch on port G1(VID unknown)with
    peer device port 23(VID 1)(8090)
    I 01/03/90 09:35:57 00828 lldp: AM2: PVID mismatch on port H4(VID unknown)with
    peer device port 24(VID 1)(6894)
    I 01/03/90 09:36:00 00828 lldp: AM2: PVID mismatch on port I22(VID unknown)with
    peer device port 27(VID 1)(6901)
    I 01/03/90 09:36:14 00828 lldp: AM2: PVID mismatch on port G2(VID unknown)with
    peer device port 23(VID 1)(6900)

    Software revision : K.15.02.0005
    ROM Version : K.15.13

    After switch full stuck not operational.  Restart then ok.

    I disconnect all ethernet port then switch not going to stuck.



  • 5.  RE: 8212ZL switch

    MVP GURU
    Posted Aug 11, 2022 09:39 PM
    Interesting to see an almost 12 Years old software version still running on a HP ProCurve 8200zl Switch Series (I  believe neither HPE has that software archived publicly available...), not to speak that latest K.15.18.0024 was released on February 2021...so just less than 11 Years after the one you're using.

    By the way...PVID mismatch log entries are basically saying that involved ports on your HP 8212zl have a Native VLAN ID (untagged) different from the one of peer ports.

    If we look at just one (Informational) log line, as example this one:

    I 01/03/90 09:36:00 00828 lldp: AM2: PVID mismatch on port I22(VID unknown)with peer device port 27(VID 1)(6901)

    we discover first that your 8212's port I22 (Module I Port 22) has unknown VID (so its Native VLAN ID is unknown): generally it could mean that port I22 is not untagged on a particular VLAN (default is VLAN ID 1) but it's probably only tagged on one or more VLAN IDs. The second thing is that the corresponding peer port at the other end is instead an untagged member of VLAN 1 (so its Native VLAN ID or PVID - referenced as VID - is just 1, default), that explains the mismatch and the informative log.

    Both peer ports - Port I22 on 8212zl's end and Port 27 on the other end - should have the very same VLAN memberships, it's advisable/recommended.

    Informative High collision or Drop rate log entries could be the effects of various reasons, difficult to say what's happening on those ports (Module J).

    I believe there is a configuration/network topology issue BUT without a clear view of who-is-who and configurations of involved peers it is (and it will remain) just a personal guess.



  • 6.  RE: 8212ZL switch

    Posted Aug 11, 2022 09:53 PM
    Thanks for details.

    1. If I direct upgrade firmware to latest, I read chance of stuck or hang , it's main core if stuck network full down.

    2. This pvid or high collision once of a everyday I see on almost every port. I already read on HPE community regarding bad cables I already replaced.

    we have j9550a module.

    What I done already I disconnect and connect, this all ethernet port to new 48 port switch after I check the log of 48port switch nothing.

    3. Configuration nothing we changed its suddenly before 3 to 5 days facing malfunction. If I add any ethernet ports, after few hours stuck.