Specifications

Overview
ExtremeXOS 12.5.4 Release Notes
10
● Upgrading ExtremeXOS Software—The following note has been added to the “Installing a Core Image”
section of “Appendx B: Software Upgrade and Boot Options,” in the ExtremeXOS Concepts Guide.
NOTE
When updating from ExtremeXOS 12.0.x or earlier to ExtremeXOS 12.5.x or later, you must first update to
ExtremeXOS 12.3.4 and then update to ExtremeXOS 12.5.x or later.
● “Using Auto Provision of Edge Switches” Correction—Paragraph three of the“Using Auto Provision of
Edge Switches” section of the ExtremeXOS Concepts Guide, page 105, should read:
A switch enabled with auto provision can be identified as follows:
extremeVMDetectedResultIngress Indicates the result of a VM entry
into the network and indicates
whether the policy applied or not in
ingress direction policyApplied(1)
indicates that the named policy
was successfuly applied to the
port. policyNotApplied(2) indicates
that the named policy was not
applied to the port. policyInvalid(3)
indicates that the named policy
was either invalid or missing, and
could not be applied to the port.
policyNotFound(4) indicates that
the named policy was not found.
policyNotMapped(5) indicates that
the no policy was mapped to this
VM Entry.
extremeVMDetectedResultEgress Indicates the result of a VM entry
into the network. and indicates
whether the policy applied or not in
egress direction policyApplied(1)
indicates that the named policy
was successfuly applied to the
port. policyNotApplied(2) indicates
that the named policy was not
applied to the port. policyInvalid(3)
indicates that the named policy
was either invalid or missing, and
could not be applied to the port.
policyNotFound(4) indicates that
the named policy was not found.
policyNotMapped(5) indicates that
the no policy was mapped to this
VM Entry.
Table/Group Supported Variables Comments