08-10-2016 05:24 AM
08-10-2016 05:56 AM
In CLI mode, you can use:
chassisbeacon 1 (for enable this) or
chassisbeacon 0 (for disable this)
Or ou can use:
switchbeacon 1 (for enable this) or
switchbeacon 0 (for disable this)
08-10-2016 06:03 AM
Looking like that all 3 commands for beacon are independent, so try to make sure that
chassisbeacon, switchbeacon and portbecon are not enable and try again with GUI.
I'm looking if I can find something more on this.
08-10-2016 07:06 AM
Does port 0 is an ISL?
PortPeerBeacon has been initiated from peer swicth for port 0?
-1 could be the wrong representation of DID that send the portPeerBeacon.
Issue portPeerBeacon --show -all on the local and peer switch connected on port 0 to see if something is enable.
08-10-2016 07:56 AM
CLI works, and WebTools doesn't work for the same element, and you're getting obtuse messaging from the switch, I'd be investigating my Java JRE version on the management server.
08-11-2016 06:40 AM
08-11-2016 09:49 AM
What is the FOS version installed into the switches?
During the beacon process, have you first try by CLI and then by webtools or the reverse?
Does others switches installed are working fine with webtools beacon feature?
Which tab in webtools are you using?