The IP Over NBMA (ION) Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] comments on MARS draft MIB
hi chris and maria, I have few comments on the MARS MIB draft submitted by you. 1. In ipAtmMarsTable clusterSeqNum and ServerSeqNum are added whose value keeps changing with every message. These objects don't seem to be useful from management point of view. 2. In ipAtmMarsRegClientTable (p.27), ipAtmMarsregClientCsn doesn't seem to be useful from the management point of view. Similarly, ipAtmMarsRegMcsCsn (p.30) in ipAtmMarsRegMcsTable doesn't seem to be useful and I think it should be ipAtmMarsRegMcsSsn. 3. In ipAtmMarsStatTable (p.30) lot of descriptions don't match the object names. I guess this is due to cut and paste. In ipAtmMarsStatTable (p.32), ipAtmMarsStatRxSjoin and ipAtmMarsStatRxSleave objects are not relevant since Mars does not receive sjoin and sleave messages. 4. In ipAtmMarsMcsStatTable (p.45), ipAtmMarsMcsStatTxSjoin and ipAtmMarsMcsStatTxSleave objects are not relevant since MCS does not send sjoin and sleave messages. Correct me if I am wrong. additions --------- 1. In MARS MIB, it would be useful to have a table for configuring backup MARS servers for this MARS. This table would contain : ipAtmMarsIndex, ipAtmMarsBackupAddr, ipAtmMarsBackupPriority, ipAtmMarsBackupRowStatus 2. A table for configuring multi-cast groups to be serverd by a MCS would be useful. This would contain : ipAtmMarsMcsIndex, ipAtmMarsMcsGroupAddr, ipAtmMarsMcsGroupAddrRowStatus -ramesh -------------------------------------------------------------------- Ramesh Uppuluri Direct : (301)-571-2554 Internetworking Software Group Fore Systems Inc., |
|