Network Elements

Starting in XCO v2.5.0, in addition to fabric and tenant service configurations, the following asset service configurations are persisted and included in Drift and Reconcile (DRC).

The support is on two levels:
  • Interface level configuration: Breakout mode, MTU, admin state, speed, FEC configuration, port dampening (link-error disable), and RME
  • Global or system level configuration: NTP, SNMP v2 and v3, prefix list, and route map

Interface-level Configuration

The following table captures the various attributes of interface for which DRC and idempotency is supported.

Note

Note

Clean up explicitly any conflicting configuration which could cause reconciliation of device to fail. For example, if XCO configures a port as breakout and if that configuration is drifted by adding Layer 3 configuration to a parent interface, the reconciliation fails. It is recommended to explicitly remove the conflicting configuration from the device through the SLX CLI and retry the DRC process.
Table 1. Interface attributes supporting DRC and Idempotency
Field Identify Drift Reconcile configuration Idempotency
Admin-state Yes Yes Yes
Breakout mode Yes Yes No
Speed Yes Yes Yes
Layer-2 MTU Yes Yes Yes
IPv4 MTU Yes Yes Yes
IPv6 MTU Yes Yes Yes
FEC mode Yes Yes Yes
Link error disable Yes Yes Yes
Toggle-threshold Yes Yes Yes
Sampling time Yes Yes Yes
Wait time Yes Yes Yes
RME enable Yes Yes Yes
The following CLI commands are available:
  • efa inventory device interface redundant-management
  • efa inventory device interface set-fec
  • efa inventory device interface set-link-error-disable
  • efa inventory device interface unset-fec
  • efa inventory device interface unset-link-error-disable

For more information, see ExtremeCloud Orchestrator Command Reference, 3.2.1 .

Global or System-level Configuration

The following CLI commands are available:
  • efa inventory device setting update --prefix-independent-convergence
  • efa inventory device setting update --prefix-independent-convergence-static
  • efa inventory device setting update --maximum-load-sharing-paths
  • efa inventory device settings update --mct-bring-up-delay
  • efa inventory device settings update --maint-mode-convergence-time

For more information, see ExtremeCloud Orchestrator Command Reference, 3.2.1 .

Device Reload

The device reload command allows the user to reload a device. Users can provide IPs and fabric name separated by commas. All devices in a fabric will be reloaded for any given fabric name in the command.

The following CLI command is available for device reload:
  • efa inventory device reload
Note

Note

Drift and reconcile and idempotency configuration support is not applicable for device reload attribute.

For more information, see ExtremeCloud Orchestrator Command Reference, 3.2.1 .

Clear IP Route

The clear IP route command allows the user to clear a device's IPv4 and IPv6 routes. Users have the option to either clear an IPv4 or an IPv6 route.

The following CLI command is available for clearing IP route:
  • efa inventory device clear route-all
Note

Note

Drift and reconcile and idempotency configuration support is not applicable for clear IP route attribute.

For more information, see ExtremeCloud Orchestrator Command Reference, 3.2.1 .

SNMP Configuration

The following tables capture the various attributes of SNMP and NTP for which DRC and idempotency are supported.

Note

Note

Regarding idempotency for creating an entry which already exists in XCO, an error message is returned stating that the user already exists.
Table 2. SNMP attributes supporting DRC and Idempotency
Field Identify Drift Reconcile Configuration Idempotency Notes
Community deleted Yes Yes No A valid error message is shown when a non-existent community is deleted
Group name associated with community is modified Yes Yes Not Applicable
Group deleted Yes Yes Not Applicable
Modify group version No No Not Applicable SLX does not support editing the SNMP group version
Modify read review or write view or notify view associated with group Yes Yes Not Applicable
Modify group name associated with SNMP user Yes Yes Not Applicable
Modify authentication protocol associated with SNMP user Yes Yes Not Applicable
Modify authentication password associated with SNMP user Yes Yes Not Applicable
Modify privacy protocol associated with SNMP user Yes Yes Not Applicable
Modify privacy password associated with SNMP user Yes Yes Not Applicable
Delete SNMP user Yes Yes No A valid error message is shown when a non-existent user is deleted
Modify encrypted keyword associated with SNMP user Yes Yes Not Applicable
Modify authentication type associated with group, that is, auth, noauth, notify Yes Yes Not Applicable
Delete SNMP host entry Yes Yes No A valid error message is shown when a non-existent host is deleted
Update SNMP host severity level Yes Yes Not Applicable Any drift observed from XCO configured default severity level is reconciled
Update SNMP host source interface Yes Yes Not Applicable Any drift observed from XCO configured default source interface is reconciled
Update SNMP host UDP port Yes Yes Not Applicable Any drift observed from XCO configured default UDP port is reconciled
Update SNMP host VRF Yes Yes Not Applicable Any drift observed from XCO configured default VRF is reconciled
Update SNMP host engine id Yes Yes Not Applicable
Update of SNMP host notification type (traps, informs) Yes Yes Not Applicable
Update of SNMP view MIB OID access (included, excluded) Yes Yes Not Applicable
The following CLI commands are available for operations on SNMP interfaces:
  • efa inventory device snmp community create
  • efa inventory device snmp community delete
  • efa inventory device snmp community list
  • efa inventory device snmp user create
  • efa inventory device snmp user delete
  • efa inventory device snmp user list
  • efa inventory device snmp host create
  • efa inventory device snmp host delete
  • efa inventory device snmp host list

For more information, see the ExtremeCloud Orchestrator Command Reference, 3.2.1 .

NTP Configuration

The NTP commands let you configure NTP server configuration on the SLX device. The configuration you set is persisted in the XCO database. DRC is also supported.

The following table captures the various attributes of the NTP configuration interface for which DRC and idempotency is supported. A drift is identified if any of the following fields are modified by you through SLX CLI or other management tools. Reconcile operation pushes the intended configuration to SLX which makes the SLX configuration synchronize with XCO.

On idempotency for creating an entry which already exists in XCO, an error message is returned stating that user already exists.

Table 3. NTP attributes supporting DRC and Idempotency
Field Identify Drift Reconcile configuration Idempotency Notes
NTP auth key ID associated with NTP serer is modified Yes Yes Not Applicable
NTP auth key name associated with NTP serer is modified Yes Yes Not Applicable
NTP server deleted Yes Yes No A valid error message is shown when a non existent NTP server is deleted.
Encryption type is modified Yes Yes Not Applicable
Trusted key is modified Yes Yes Not Applicable
Encryption level is modified Yes Yes Not Applicable
NTP server disable modified Yes Yes Not Applicable
The following CLI commands are available for operations on NTP interfaces:
  • efa inventory device ntp server create
  • efa inventory device ntp server delete
  • efa inventory device ntp server list
  • efa inventory device ntp disable-server

For more information, see the ExtremeCloud Orchestrator Command Reference, 3.2.1 .

IP prefix list configuration

Note

Note

Regarding idempotency for creating an entry which already exists in XCO, an error message is returned stating that the user already exists.
Table 4. IP prefix list attributes supporting DRC and Idempotency
Field Identify Drift Reconcile configuration Idempotency Notes
IPv4 prefix list rule is deleted. Yes Yes No Deleted rule will be reconciled.
IPv4 prefix list is deleted. Yes Yes No Deleted prefix list along with all rules associated with it will be reconciled.
IPv4 prefix list rule created OOB. Different rules exist with same prefix list name in XCO. No No Not applicable Delete the OOB rule or keep it and don‘t act as part of DRC.
IPv4 prefix list rule created OOB. Different rules exist with same prefix list name and sequence number in XCO. Yes Yes Not applicable Prefix list rule will be reconciled to be in sync with XCO.
Create an IPv4 prefix OOB with a prefix list name not matching any of the XCO created entries. No No Not applicable These are treated as out of band entries and XCO will not perform DRC.
The following CLI commands are available for operations on IP prefix lists:
  • efa policy prefix-list create
  • efa policy prefix-list list
  • efa policy prefix-list delete
  • efa policy prefix-list update

For more information, see the ExtremeCloud Orchestrator Command Reference, 3.2.1 .

Route map configuration

Note

Note

Regarding idempotency for creating an entry which already exists in XCO, an error message is returned stating that the user already exists.
Table 5. Route map attributes supporting DRC and Idempotency
Field Identify Drift Reconcile configuration Idempotency Notes
Route map deleted. Yes Yes No Recreate the route map, along with the match criteria during reconcile.
Route map rule action updated. Yes Yes No Reconcile the route map action (permit/deny) for that rule.
Update IPv4 prefix list name in match criteria. Yes Yes No Reconcile the IPv4 prefix list name.
IPv4 prefix list match criteria deleted. Yes Yes NA Reconcile the match criteria for IPv4 prefix list.
A different match criteria NOT supported by XCO is added through OOB. No No NA
A set criteria NOT supported by XCO is added through OOB. No No NA
Route map is created through OOB and this is not present or created by XCO. No No NA
The following CLI commands are available for operations on route maps:
  • efa policy route-map create
  • efa policy route-map update
  • efa policy route-map delete
  • efa policy route-map list
  • efa policy route-map-match create
  • efa policy route-map-match list
  • efa policy route-map-match delete

For more information, see the ExtremeCloud Orchestrator Command Reference, 3.2.1 .

Device Settings

The following table captures the various attributes of device settings for which DRC and idempotency are supported.

Table 6. Device settings attributes supporting DRC and Idempotency
Field Identify Drift Reconcile Configuration Idempotency
BGP prefix independent convergence (PIC) Yes Yes Yes
prefix-independent-convergence-static Yes Yes Yes
ECMP routed load-sharing max path Yes Yes Yes
Maintenance mode convergence time Yes Yes Yes
Static prefix independent convergence (PIC) Yes Yes Yes
Note

Note

Drift and reconcile and idempotency configuration support is not applicable for device update and viewing device settings.

BGP Prefix Independent Convergence (PIC)

Specify Yes to enable BGP PIC and No to de-configure it.

The following CLI command is available to enable BGP PIC:
  • efa inventory device setting update --prefix-independent-convergence
Note

Note

After configuring this command, clear the routes on the device.

For more information, see ExtremeCloud Orchestrator Command Reference, 3.2.1 .

ECMP Max Path

Use the command string to view route load-sharing maximum paths. Valid values include 8, 16, 32, and 64. The default value is 64.
Note

Note

The device must be reloaded for this command to take effect.
The following CLI command is available to configure ECMP route load-sharing max path:
  • efa inventory device setting update --maximum-load-sharing-paths

For more information, see ExtremeCloud Orchestrator Command Reference, 3.2.1 .

Device Settings Update

Configure the maintenance mode and display the available device settings.

Use the device-ips parameter, separated by comma to view a range of device IP addresses.

Use the fabric-name parameter to specify the name of the fabric.

The show command displays the device settings.

The following CLI command is used to display the device settings:
  • efa inventory device setting show [ --ip device-ips ]

For more information, see ExtremeCloud Orchestrator Command Reference, 3.2.1 .

Time Zone Configuration

By default, SLX devices come up with the GMT timezone. Using the efa inventory device timezone command, you can set the timezone per device or per fabric.

The following CLI commands are available for timezone settings:
  • efa inventory device timezone set
  • efa inventory device timezone unset
  • efa inventory device timezone list
Table 7. Time zone attributes supporting DRC and Idempotency
Field Identify Drift Reconcile configuration Idempotency
Time zone is set. Yes Yes Yes
Time zone is unset. Not applicable Not applicable Yes
Note

Note

Identify drift, drift and reconcile, and idempotency support is not applicable for time zone display.

For more information, see the ExtremeCloud Orchestrator Command Reference, 3.2.1 .

9037725-01 RevAA