Useful Topics
1. About analyzer traces:
- Only one port can be selected for tracing.
- The port saved in Engine's etc/trace.conf file is the default port for tracing when loading simulation.
- All frames will be traced except Read/Write SCSI commands.
- Trace can be saved to a file in Wireshark K12 text format.
- Saving FCoE/FIP frames is straight-forward because they are embedded in Ethernet frame and therefore directly supported by Wireshark viewer. Native FC frames, however, are not supported by Wireshark, so the FC frame is embedded in a fake FCoE frame (ETH Type 0x8906) using DA a0-b0-c0-d0-e0-f0, SA 0a-0b-0c-0d-0e-0f, and VLAN_ID 1. Using fake FCoE frame is purely to get native FC traces loadable in Wireshark.
2. Backup and load configurations:
- Starting from build 20110412_4016b, Engine configuration files can be backed up by a given configuration name, allowing user to setup multiple configurations and pick any one of them to run. See this picture.
- Configuration backups are located in BackupConfigs/<EngineName> folder. Each backup is associated with a dedicated folder, which holding all Engine related configuration or initialization files.
- Current configuration is the one to be used by Engine simulation, which is in SimSANs_Engines/<EngineName> folder as usual.
- To backup current configuration, simply type in a configuration name and click "Backup Current Config" button.
- To load all the available backup configurations, click "Refresh Backup Config List" button.
- To load a backup configuration, select a configuration name from the list, then click "Use Selected Backup Config". The configuration selected will become the Current Configuration.