Fixed Problems
The following problems reported in previous releases have been fixed:
Workaround: After starting a Config Sync Service for the first time, and before performing a device discovery, execute the following command:
chmod -R 777 <local FTP root directory>/<FTP subdirectory>Note that <local FTP root directory> and <ftp subdirectory> are the directories set during installation.
- If you edit the Integrated Local Management Interface (ILMI) settings (virtual path identifier [VPI] and virtual circuit identifier [VCI]) of an ATM interface while the ILMI Settings Admin Status is set to "Up," an SMNP error occurs.
Workaround: Before changing VPI and VCI settings, change the ILMI Settings Admin Status to "Down," and click Save. Next, update the VPI and VCI settings, and click Save. Then, change the ILMI Settings Admin Status back to "Up," and click Save.
- You cannot create Frame Relay major interfaces for devices running JUNOSe release 6.1.0 and release 7.0.0bx. You can create Frame Relay major interfaces for devices running JUNOSe release 6.0.0 or earlier.
- When statistics are running, if an SNMP error is received on another operation (create, for instance) and you do not click the OK button on the error message dialog box within a certain number of seconds, an SNMP timeout error is returned for the SNMP statistics get request. The same result occurs if the SNMP error is on one device and the statistics polling is occurring on another.
After you click OK on the error dialog box, everything returns to normal with the next poll.
- When configuring an interface, if you display the Module Config tab (by clicking the Lower Layer button) and then close it (by clicking the X button), all other tabs are closed and the original interface remains locked.
- The OAM Loopback Enable and OAM Loopback Frequency parameters are read-only when you create and configure ATM interfaces using the NMC-RX client and NMC-RX Provisioning Service for devices that are running JUNOSe release 6.1.0 . You can configure these parameters for devices running JUNOSe release 6.0.0 or earlier.
- In previous releases, the PVS test utility was not reading the EMS name and port number from the PVS.rc file and did not work correctly if the values were changed in the file. The PVS test utility now correctly uses the EMS name and port number in the PVS.rc file.