|
| 1 | +--- |
| 2 | +title: Known issues for Modeling and Simulation Workbench |
| 3 | +description: "Troubleshooting guide for known issues on Azure Modeling and Simulation Workbench." |
| 4 | +author: yousefi-msft |
| 5 | +ms.author: yousefi |
| 6 | +ms.service: modeling-simulation-workbench |
| 7 | +ms.topic: troubleshooting-known-issue |
| 8 | +ms.date: 09/29-2024 |
| 9 | + |
| 10 | +#customer intent: As a user, I want to troubleshoot and understand known issues with Azure Modeling and Simulation Workbench. |
| 11 | + |
| 12 | +--- |
| 13 | + |
| 14 | +# Known issues: Azure Modeling and Simulation Workbench |
| 15 | + |
| 16 | +The Azure Modeling and Simulation Workbench is a secure, cloud-based platform for collaborative engineering, design, and simulation workloads that require security and confidentiality. The Workbench provides isolation for separate enterprises, allowing each to bring in code, data, or applications and apply them to a shared environment without exposing confidential intellectual property. |
| 17 | + |
| 18 | +This Known Issues guide provides troubleshooting and advisory information for resolving or acknowledging issues to be addressed. Where applicable, workaround or mitigation steps are provided. |
| 19 | + |
| 20 | +## EDA license upload failures on server name |
| 21 | + |
| 22 | +When uploading Electronic Design Automation (EDA) license files with server names that contain a dash ("-") symbol, the chamber license file server fails to process the file. For some license files, the `SERVER` line server name isn't being parsed correctly. The parser fails to tokenize this line in order to reformat for the chamber license server environment. |
| 23 | + |
| 24 | +### Troubleshooting steps |
| 25 | + |
| 26 | +If your license server has any dash ("-") characters in the name and fails when uploading a license file, this issue might be present for your release. Replace the server name with any single word placeholder using only alphanumeric characters (A-Z, a-z, 0-9) and no special characters or "-". For example if your `SERVER` line looks like this: |
| 27 | + |
| 28 | +```INI |
| 29 | +SERVER license-server-01 6045BDEB339C 1717 |
| 30 | +``` |
| 31 | + |
| 32 | +Replace the license server name to a name without dashes. The name is irrelevant as the license server transforms whatever is in the server position with the correctly formatted name. |
| 33 | + |
| 34 | +```INI |
| 35 | +SERVER serverplaceholder 6045BDEB339C 1717 |
| 36 | +``` |
| 37 | + |
| 38 | +## Users on public IP connector with IP on allowlist can't access workbench desktop or data pipeline |
| 39 | + |
| 40 | +A chamber with a public IP connector configured to allow users who's IP is listed after the first entry of the allowlist can't access the chamber either through the desktop or data pipeline using AzCopy. If the allowlist on a public IP connector contains overlapping networks, in some instances the preprocessor might fail to detect the overlapping networks before attempting to commit them to the active NSG. Failures aren't reported back to the user. Other NSG rules elsewhere - either before or after the interfering rule - might not be processed, defaulting to the "deny all" rule. Access to the connector might be blocked unexpectedly for users that previously had access and appear elsewhere in the list. Access is blocked for all connector interactions including desktop, data pipeline upload, and data pipeline download. The connector still responds to port queries, but doesn't allow interactions from an IP or IP range shown in the connector networking allowlist. |
| 41 | + |
| 42 | +### Prerequisites |
| 43 | + |
| 44 | +* A chamber is configured with a public IP connector (gateway appears as "None"). |
| 45 | + |
| 46 | +* The allowlist has entries with CIDR-masked IP ranges less than a single host /32 (/31 and smaller). |
| 47 | + |
| 48 | +* The IP ranges of two or more entries with subnet masking are overlapping. Overlapping ranges can sometimes be identified with leading octets being identical, but trailing octets marked with a "0". |
| 49 | + |
| 50 | +### Troubleshooting steps |
| 51 | + |
| 52 | +If a user that could previously access the workbench loses connectivity even though their IP is still on the allowlist, an overlapping but unhandled error with the allowlist might be blocking. Loss of connectivity doesn't preclude that any onsite or local firewall, VPN, or gateway might also be blocking access. |
| 53 | + |
| 54 | +Users should identify overlapping IP ranges by checking the allowlist of masked subnets less than a single host (less than /32) and ensure that those subnets have no overlap. Those overlapping subnets should be replaced with nonoverlapping subnets. An indicator of this is that the first allowlist entry is acknowledged, but other rules aren't. |
| 55 | + |
| 56 | +## Data pipeline upload file corruption or truncation |
| 57 | + |
| 58 | +Uploaded files to a chamber through the data pipeline might be truncated or otherwise corrupt. |
| 59 | + |
| 60 | +### Troubleshooting steps |
| 61 | + |
| 62 | +While uploading files into a chamber, you might see a file that isn't the expected length, corrupt, or otherwise doesn't pass a hash check. |
| 63 | + |
| 64 | +### Possible causes |
| 65 | + |
| 66 | +The file isn't corrupt or truncated, but still uploading. The data pipeline isn't a single stage and files placed in the upload pipeline don't appear instantaneously in the */mount/datapipeline/datain* directory and are likely still completing. Check back later and verify the length or hash. |
| 67 | + |
| 68 | +<!-- KEEP THIS FOR FUTURE CHANGES |
| 69 | +## [Issue] |
| 70 | +Required: Issue - H2 |
| 71 | +
|
| 72 | +Each known issue should be in its own section. |
| 73 | +Provide a title for the section so that users can |
| 74 | +easily identify the issue that they are experiencing. |
| 75 | +
|
| 76 | +[Describe the issue.] |
| 77 | +
|
| 78 | +<!-- Required: Issue description (no heading) |
| 79 | +
|
| 80 | +Describe the issue. |
| 81 | +
|
| 82 | +### Prerequisites |
| 83 | +
|
| 84 | +<!--Optional: Prerequisites - H3 |
| 85 | +
|
| 86 | +Use clear and unambiguous language, and use |
| 87 | +an unordered list format. |
| 88 | +
|
| 89 | +### Troubleshooting steps |
| 90 | +
|
| 91 | +<!-- Optional: Troubleshooting steps - H3 |
| 92 | +
|
| 93 | +Not all known issues can be corrected, but if a solution |
| 94 | +is known, describe the steps to take to correct the issue. |
| 95 | +
|
| 96 | +### Possible causes |
| 97 | +
|
| 98 | +<!-- Optional: Possible causes - H3 |
| 99 | +
|
| 100 | +In an H3 section, describe potential causes. |
| 101 | +
|
| 102 | +--> |
0 commit comments