Test Set UP
========
A. 1 - AP (ver 8.2.4)
B. 3 - SM
B.1 SM version 9 board type p11
B.2 SM version 9 board type p9
B.3 Sm version 8 board type p9
Result:
======
1. When AP (SNMP trap enable) with SM IP configuration (SM Network Accessibility set either to public or local) there is no error encountered in SM (any version) to AP communication and we can ping/snmpwalk the rf ip of the SM via AP
2. When AP (SNMP trap disable) with SM IP configuration
2.1. SM Network Accessibility set to local.
-there is no encountered for SM(any version) to AP communication
2.2. SM Network Accessibility set to Public.
-This is the time we encountered an error only in SM version 9 with any version of board type “Unable to get SM config parameters SM_TWOX_RATE,SM_POWER_CONT,SM_HIPRIO_CHAN,SM_TIMING_PULSE,SM_SNMP_PERM. No reply from SM”.
sample error logs:
Jan 20 10:31:29 testdsc proxyd[38253]: LUID of SM on Associated AP: [3].
Jan 20 10:31:29 testdsc proxyd[38253]: Radio Interface IP of Associated AP: 172.31.1.1
Jan 20 10:31:29 testdsc proxyd[38253]: Radio Interface IP of Associated SM: 172.31.1.3
Jan 20 10:31:29 testdsc proxyd[38253]: Connecting to SM RFIP 172.31.1.3
Jan 20 10:32:29 testdsc proxyd[38253]: Unable to get SM config parameters SM_TWOX_RATE,SM_POWER_CONT,SM_HIPRIO_CHAN,SM_TIMING_PULSE,SM_SNMP_PERM. No reply from SM.
Can anyone give me some clear information what is the root cause of this error.
Thanks,
edelossantos.