|
We, at AdventNet take all efforts to ensure that our customers do not waste their time and resources unnecessarily. This section lists out the Known Issues available with the product at the time of the release.
When the network is successfully started, the message "Network started successfully" is displayed. Sending queries to the simulator before this will cause the simulator to crash.
In Solaris OS, the system will be restarted when the network is stopped.
In network creation, while specifying the unique values, if you choose RAMDOM simtype, more than one value must be specified. Specifying only one value, will throw exception and the network creation will be affected.
If a WALK file with mismatched datatype is used to create a device, the device will not be created properly.
The simulator allows to set both the following types of value for atTable : 1.1.127.0.0.1 and also 1.127.0.0.1
If Start Network operation fails to start the network devices for some reason, doing the Start Network operation again, will not list the network name in the "Select the Networks" dialog. As a work around, you can do Stop Network operation and then do the Start Network operation.
During bulk modification of ipaddress for a specified range of devices, if a device with new ipaddress is already present in the network, this will be ignored by the simulator and the same ip will be assigned. This will result in two devices having the same ip.
Modification of timer traps in template devices will create duplicate varbinds.
Sending traps using the "Send" button, will not send the traps with Global IP address.
While configuring a script file, if a script with the same name already exists in the configuration directory, this old script is updated without any information or warning message.
UpInterface() and DownInterface() script APIs will not work.
User codes added inside the generated script will be lost if the script is once again loaded and generated from the Behavior Simulation Wizard.
The script configured for External index node will not be executed.
While connecting to a CLI agent, no characters should be entered before the login prompt appears.
The "no" command in vlan mode may cause the network simulator to crash.
Specifying invalid values to the IOS commands, may cause the Network Simulator to crash.
When a query is made on a TL1 command code with completion code configured as 'DENY', the error codes and error messages displayed in the response are different for each query.
Deleting an accessId and message payload present in the device tree, from the network device, will not delete the same. The response will be generated.
It is not possible to connect to the TL1 agent using Telnet from Windows machine.
Unquoted message is not supported in Valid response.
Error response supports only Quoted lines.
If script files are configured to be executed after the upload/download of files in TFTP server, the script is executed even when the file is not transferred.
Performing a FTP download from Windows to Liniux OS by specifying a non-existing file, will hang the FTP client dialog.
When a device with Telnet support is copied and pasted, the pasted device will not have telnet support.
The response time for the telnet device increases when the number of telnet devices started is greater than 250.
If a switch (s1), which has one or more devices connected to it, is connected to a switch/router, the devices connected to s1 will not be displayed. To display the devices, the router to which s1 is connected must be clicked again in the router tree on the left-side.
If a switch (s2) is connected to switch (s1), and s1 is connected to a router, disconnecting s1 from the router, will not display s1 and s2 in the remaining device panel, as s1 and s2 are still inter-connected.
In the evaluation version, the first two group nodes will respond based on your query. If there are a lot of OIDs between the first group node and second group nodes, a MIB walk may time-out. This is because of the evaluation restriction on two group nodes.
When configuring Simulation type for a counter64 data type the value will rollback to the starting value when the value reaches 2 ^63 -1. Where according to the original value, it should accommodate 2^64 - 1.
Recording values from the real agent sor modification of scalar values will not invoke the Save dialog. The configuration must be saved manually.
In Default Trap Generation there is a problem with getting varbinds in case of v2 MIBS.
Modifying the instance value in a table in the SNMP agent simulator will not delete the instance in DB and it can be queried from manager.
The script API methods deleteRowWithValue, getAllTableValues will not work properly for a table with external indexes.
The Default Traps generation will have problems when loading multiple MIBs.
The script API method GetAllTableIndices() will return only the internal indices for a table having both internal and external indices.
If the product is using JDK1.3 or JDK1.3.1 in Linux OS, starting the TL1 agent in TCP port, will not free the port even if the agent is stopped.
If the Command Code have both Valid and Error Responses in the TCS, the Simulator simulates only the Valid Response lines by default.
If a new access identifier / message payload is added after configuring an autonomous message for a command code, then the autonomous message configured will not be reflected in the run-time.
While configuring unquoted response lines, the parameter values must not have any white spaces.
If the echo codes is configured for a command code, then while adding an access identifier or message payload block through scripts, the echo codes will not be reflected for the newly added access identifier / message payload.
Changing the Target ID after starting the agent, will not be reflected in the Timer Based Autonomous Messages. The new Target Id will be reflected in the Timer Based Autonomous Messages only after querying a command code,
The script API methods getLine() and deleteLine() for the Response block will get/delete the line irrespective of whether it is quoted or unquoted.
When a query is made on a TL1 command code with completion code configured as 'DENY', the error codes and error messages displayed in the response are different for each query.
The command line trap stormer will not exit by itself after completion of sending of the traps.
In SNMP Trap Recorder, even if all the traps in the dialog are deleted, clicking on the Save button will ask for a file name. If the file name is specified, the deleted traps will be saved in the file.
During Runtime for JDK version after 1.2.2
Exception occurred during event dispatching:
ava.lang.NullPointerException
at javax.swing.plaf.basic.BasicTableUI.paintCell(Unknown Source)
at javax.swing.plaf.basic.BasicTableUI.paintCells(Unknown Source)
at javax.swing.plaf.basic.BasicTableUI.paint(Unknown Source)
at javax.swing.plaf.ComponentUI.update(Unknown Source)
at javax.swing.JComponent.paintComponent(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
at javax.swing.JComponent.paintChildren(Unknown Source)
|
|
Note: It is not advisable to change the JDK version of the product. |
Exception while adding a row in the Table
java.lang.NullPointerException
at javax.swing.plaf.basic.BasicTableUI.paintCell(Unknown Source)
at javax.swing.plaf.basic.BasicTableUI.paintCells(Unknown Source)
at javax.swing.plaf.basic.BasicTableUI.paint(Unknown Source)
at javax.swing.plaf.ComponentUI.update(Unknown Source)
at javax.swing.JComponent.paintComponent(Unknown Source)
at javax.swing.JComponent.paint(Unknown Source)
|