[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.


[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.


[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.


[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.


[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.


[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.


[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.


[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.


[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.


[1] CC 03.02.001

[2] * VSP platforms only support the UNI ports for Application Telemetry

[3] * ZTP+ EXOS Stacking requires 30.3.X firmware

[4] ICX: SNMPv3 traps are supported in XMC but it requires an additional manual configuration on the XMC server for traps to work. XMC trap registration configures the switch for informs but ICX does not support informs. The customer must manually update the snmptrapd.conf file and restart the nssnmptrapd service, in order for SNMPv3 traps to be seen in XMC. In the /usr/local/Extreme_Networks/NetSight/appdata/snmptrapd.conf file it shows examples of how to add entries to this file. After the entry is made the nssnmptrapd service must be restarted

[5] 5320-EXOS is Beta support for 21.11.10.x

[6] ERS devices must be configured to be in CLI mode and not menu mode. Menu mode is not compatible with configuration archive scripts.