The following defects are open in this release of Extreme Visibility Manager.
| Parent Defect ID: | XVM-562 | Issue ID: | XVM-562 |
|---|---|---|---|
| Severity: | S2 - High | ||
| Product: | XVM | Reported in Release: | XVM 0.1.0 |
| Symptom: | During the device discovery using the CSV file upload, if any of the given parameters are wrong in the input for some entries (except the ip address), No error message is shown in the GUI. | ||
| Condition: | If the major parameters like IP Address, Device Version, User Name or Password are wrong, device discovery failure is shown on the GUI | ||
| Workaround: | Making sure that all the parameters are correct before uploading the CSV file for the discovery | ||
| Recovery: | Unless the major parameters like IP Address, Device Version, User Name or Password are wrong device discovery will work fine. If these major parameters are wrong, discovery will fail and user needs to do the retry of the discovery after correcting them | ||
| Parent Defect ID: | XVM-828 | Issue ID: | XVM-828 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 0.1.0 |
| Symptom: | When user wants to delete Device Type for a specific location there is no option to do the same in Manage Device Types | ||
| Condition: | When user wants to delete Device Type for specific location | ||
| Workaround: | User needs to delete Device Type which will be deleted for all the locations. | ||
| Recovery: | User needs to delete Device Type for all locations and then add Device Type for needed location again. | ||
| Parent Defect ID: | XVM-1409 | Issue ID: | XVM-1409 |
|---|---|---|---|
| Severity: | S2 - High | ||
| Product: | XVM | Reported in Release: | XVM 0.1.0 |
| Symptom: | Sometime user notification shows a hour glass | ||
| Condition: | Observed once when portchannel is added | ||
| Workaround: | No functional loss. | ||
| Recovery: | No functional loss. | ||
| Parent Defect ID: | XVM-1738 | Issue ID: | XVM-1738 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 0.1.0 |
| Symptom: | When user choses to breakout ports, the broken parts are shown at the top of the Ports config object instead at its original order | ||
| Condition: | When port breakout option is done for a port | ||
| Workaround: | The page needs to be refreshed to see the ports in the correct order | ||
| Recovery: | usabiliy issue with no functional impact. Hence no recovery steps required. | ||
| Parent Defect ID: | XVM-1844 | Issue ID: | XVM-1844 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Device specific error message with an error code is seen while performing configuration operation due to permission issues. | ||
| Condition: | Discover a 9920 device with a user having role 'user' and perform config operation. | ||
| Workaround: | To discover a 9920 device, always use a user who has 'admin' privileges. | ||
| Parent Defect ID: | XVM-1993 | Issue ID: | XVM-1993 |
|---|---|---|---|
| Severity: | S2 - High | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Device add failure with an error "Already present" | ||
| Condition: | Happens when the device is upgraded when it is already discovered from xvm. | ||
| Workaround: | Delete all dtcv for the device | ||
| Recovery: | Delete all dtcv for the device | ||
| Parent Defect ID: | XVM-2121 | Issue ID: | XVM-2121 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Ingress policy and Egress policy charts are not getting populated | ||
| Condition: | When the device dashboard is accessed immediately after discovery, policy charts are not displayed. | ||
| Workaround: | Refresh the page or toggle the tabs. | ||
| Parent Defect ID: | XVM-2123 | Issue ID: | XVM-2123 |
|---|---|---|---|
| Severity: | S1 - Critical | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: |
While Installing qcow, the IP address doesnot recognize the format IPADDRESS/PREFIX |
||
| Workaround: |
The IP Address should be given in format "aaa.bbb.ccc.ddd" or The details containing w.r.t to vm in file xvmconf can be pushed to qcow as explained in installation document. |
||
| Parent Defect ID: | XVM-2125 | Issue ID: | XVM-2125 |
|---|---|---|---|
| Severity: | S2 - High | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Some of the services will fail to start. | ||
| Condition: | Issue was seen after multiple regional VM reboots scenario. | ||
| Workaround: |
1. Power on Leader node 2. backup old data folder on problematic regional nodes. "mv /var/lib/pgsql/12/data /var/lib/pgsql/12/data_org 3. execute below command "pg_basebackup -h <Leader regional IP> -U cmon_replication -Xs -P -R -D /var/lib/postgresql/12/data" 4 Execute below command and wait for State to change from "creating Replica" to running. [root@ ~]# patronictl -c /opt/app/patroni/etc/postgresql.yml list postgres + Cluster: postgres (6969515509939729866) -------------------- MemberHostRoleStateTLLag in MB -------------------------------------------------------+ pg_10.37.136.16210.37.136.162 running20 pg_10.37.136.16310.37.136.163Leaderrunning pg_10.37.136.16410.37.136.164 running80 |
||
| Recovery: |
1. Power on Leader node 2. backup old data folder on problematic regional nodes. "mv /var/lib/pgsql/12/data /var/lib/pgsql/12/data_org 3. execute below command "pg_basebackup -h <Leader regional IP> -U cmon_replication -Xs -P -R -D /var/lib/postgresql/12/data" 4 Execute below command and wait for State to change from "creating Replica" to running. [root@ ~]# patronictl -c /opt/app/patroni/etc/postgresql.yml list postgres + Cluster: postgres (6969515509939729866) -------------------- Member Host Role State TL Lag in MB -------------------------------------------------------+ pg_10.37.136.162 10.37.136.162 running 2 0 pg_10.37.136.163 10.37.136.163 Leader running pg_10.37.136.164 10.37.136.164 running 8 0 We can prevent this issue by monitoring patroni instances and checking for last column of "Lag in MB", if count is not coming back to 0 for long time we can follow above steps to recover. |
||
| Parent Defect ID: | XVM-2128 | Issue ID: | XVM-2128 |
|---|---|---|---|
| Severity: | S2 - High | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: |
"Region Service Message Processing Timedout" message shown on UI when user tries to delete the same ACL multiple times before receiving the notification/confirmation for the first delete operation. No impact on XVM functionality. |
||
| Condition: | When user continuously clicks on delete button of Policy Match Rule to delete the same ACL without waiting for delete notification from XVM. | ||
| Workaround: | Wait for the successful or failure notification from XVM. | ||
| Parent Defect ID: | XVM-2130 | Issue ID: | XVM-2130 |
|---|---|---|---|
| Severity: | S2 - High | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | NGNPB configuration details are not displayed on XVM UI after migrating policy, rules from MLX/SLX devices. | ||
| Condition: | When ACL rules, policy configuration of source device has syntax/semantic conflicts with NGNPB accepted configuration. | ||
| Workaround: | Refresh configuration of the NGNPB device again to display the details. | ||
| Parent Defect ID: | XVM-2135 | Issue ID: | XVM-2135 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Delay observed in processing of multiple devices discovery using CSV file, resulting in UI "Processing your request message will be appearing" | ||
| Condition: | Discover > 5 devices using CSV file. | ||
| Workaround: | Add less number of devices (< 5) from CSV file and repeat the same when we have multiple devices | ||
| Recovery: | There is no functionality issue, the add window will be present for more time and will disappear once discovery completed. | ||
| Parent Defect ID: | XVM-2141 | Issue ID: | XVM-2141 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Policy and Matches cannot have the same name in XVM across the different types even if it is allowed on the device. | ||
| Condition: | The issue is seen when the same name is provided for different type of match or different policies and configuration is not allowed to apply. | ||
| Workaround: | Provide different names for different type of policy or the matches. | ||
| Recovery: | There will be error seen if same name is provided and configuration is not allowed to apply. So no recovery is needed. | ||
| Parent Defect ID: | XVM-2142 | Issue ID: | XVM-2142 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Duplicate port entries are seen in the interface statistics dashboard. | ||
| Condition: | When the SCS service gets re-initialized, the duplicate entries are seen in the statistics dashboard. | ||
| Workaround: | Refresh the page, new stats entries will be updated correctly. | ||
| Parent Defect ID: | XVM-2148 | Issue ID: | XVM-2148 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Deleting egress object with Network Operator role displays incorrect message saying "Delete Request Failed". | ||
| Condition: | When user with Network Operator role deletes egress or any config object | ||
| Workaround: | There is no functionality loss, hence no workaround required. | ||
| Recovery: | No Recovery is required as there is no functional issue. | ||
| Parent Defect ID: | XVM-2149 | Issue ID: | XVM-2149 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Tunnel origination configuration is not reverted to previous state incase of failure notifications. | ||
| Condition: | Tunnel origination configuration rejected from device due to incorrect address. | ||
| Workaround: | Configuration can be deleted and added again with correct values. | ||
| Parent Defect ID: | XVM-2151 | Issue ID: | XVM-2151 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Adding back the same ACL match rule which was deleted using the same window fails. | ||
| Condition: | Delete and re add the same ACL match rule. | ||
| Workaround: | Close the current ACL edit window and retry. | ||
| Parent Defect ID: | XVM-2160 | Issue ID: | XVM-2160 |
|---|---|---|---|
| Severity: | S2 - High | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Some times, SFMS Service gets re-initiated while trying to fetch service chains in a scaled environment. | ||
| Condition: | In scaled environment with bulk configuration. | ||
| Workaround: | No functional impact. Re-initiated Service continues to work normally. | ||
| Parent Defect ID: | XVM-2162 | Issue ID: | XVM-2162 |
|---|---|---|---|
| Severity: | S2 - High | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Configuration is reconciled from device and old config is retained after Refresh Configuration (on-demand reconciliation). | ||
| Condition: |
1. When refresh configuration is performed after rebooting the device. 2. Applying default config on device, this reboots the device. |
||
| Workaround: | Wait for few minutes (~4-5) before executing refresh configuration. This will allow XVM to reconnect to the device services. | ||
| Parent Defect ID: | XVM-2164 | Issue ID: | XVM-2164 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Device discovery fails with an error notification | ||
| Condition: | Rediscover a device that is in the error state due to incorrect DTCV and location. | ||
| Workaround: | Delete the device in the error state and rediscover it with the correct DTCV and location information. | ||
| Parent Defect ID: | XVM-2165 | Issue ID: | XVM-2165 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Session expiry alert is shown multiple times | ||
| Condition: | When configuration page is opened with consolidated view. | ||
| Workaround: | Need to click alert multiple times to view the login page. | ||
| Recovery: | Recovery is not needed as there is no functionality loss. | ||
| Parent Defect ID: | XVM-2180 | Issue ID: | XVM-2180 |
|---|---|---|---|
| Severity: | S2 - High | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | The ingress group dashboard chart is not populated with data. | ||
| Condition: | Reconciliation of an ingress group added through CLI after device discovery. | ||
| Workaround: | Delete and rediscover the device. | ||
| Parent Defect ID: | XVM-2182 | Issue ID: | XVM-2182 |
|---|---|---|---|
| Severity: | S1 - Critical | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Techsupport cannot be done from control plane VM | ||
| Workaround: | Techsupport can be executed in machine where install files are downloaded | ||
| Parent Defect ID: | XVM-2185 | Issue ID: | XVM-2185 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | Notification is updated with a successful device discovery message even though the discovery failed. | ||
| Condition: | Rediscover a device that is in the error state with incorrect DTCV and location change. | ||
| Workaround: | Delete the device in the error state and rediscover it with the correct DTCV and location information. | ||
| Parent Defect ID: | XVM-2192 | Issue ID: | XVM-2192 |
|---|---|---|---|
| Severity: | S3 - Medium | ||
| Product: | XVM | Reported in Release: | XVM 6.0.0 |
| Symptom: | In installation tar file, controlplane.conf, region.conf and zone.conf , if NTP_CONF="0" , still configuring for NTP | ||
| Condition: | In installation tar file , controlplane.conf, region.conf and zone.conf , if NTP_CONF="0" , still configuring for NTP | ||
| Workaround: |
in controlplane.conf, region.conf and zone.conf , making NTP_CONF=0 (without double quotes) |
||