Specifications

Patches Issued Since the CS2/MMS2 Release
Software Superseded by CS3/MMS3 Software Release Notice for 5.0rev1
5-80 CS3 and MMS3
--
The problem was ATM discovery was not resolving any connections
other than those between ForeSwitches. When ATMDISC was run
against an ATM network none of the LaneClient (9A128/9A426/
SS2200), ZX250 (6ATSM, 9A100), or Predator connections are
resolved, and an error message was produced:
*** Error: Cannot obtain ATM neighboring devices
for ATM switch 0x5700016
The resolution was in several parts:
1. Modify the ATMClientApp Model type so that a device model with
ATMClientApp should respond to two actions sent by ATM Discovery.
a. GET_ATM_PORT_LIST action : In response to this action the
device model with the ATMClientApp should respond with the
values for "port mh", "port mth", and "port oid" for the port models
with iftype value 37 or 39 ( ATM, SONET ).
b. RESOLVE_ATM_PORT_NAME action : The device model with
ATMClientApp should find the entry from MIB II Interface table
which has ifdescr that matches the value sent by ATM Discovery.
In response to this action the device should send back the instance
of that ifentry.
The ATM Discovery sends these actions to the device model. Using
the new action redirector / action responder mechanism
introduced in mdlsv.1 generic, GET_ATM_PORT_LIST &
RESOLVE_ATM_PORT_NAME actions will be redirected to
ATMClientApp.
2. Implement the RESOLVE_ATM_PORT_NAME sent by ATM
Discovery in all Model types with the ATMDiscFrag component as a
base model type (e.g. ForeSwitchApp - Fore).
3. Modify the GET_ATM_NEIGHBORS action to check whether or not
the remoteipaddress attribute for a port has a valid IP. If yes, it will
send it to ATM Discovery. This action will no longer stipulate that
portoperstatus attribute is "up" before it sends the IP to ATM
Discovery.
--