[SNMP4SDN-17] Result of calling rpc get-arp-table defined in misc-config.yang is false. Created: 27/Feb/16  Updated: 19/Oct/17  Resolved: 02/Mar/16

Status: Resolved
Project: snmp4sdn
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Nanfei Chen Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 5438

 Description   

Branch: stable/beryllium.

There are three switches in my experiment, and their connections are as follows.
s1(GE1/0)-----(GE1/0)s2(GE2/0)-----(GE1/0)s3

File snmp4sdn_swdb.csv is as follows, and there are only s1 and s2 in this file.
MAC,IP,SNMP_Community,CLI_Username,CLI_Password,Model
74:25:8a:e4:11:be,17.0.2.104,public,admin,admin,H3C_VSR
74:25:8a:e3:56:b4,17.0.3.105,public,admin,admin,H3C_VSR

Firstly, I use command snmp4sdn:readdb to read device information about s1 and s2. The result is as follows.
MAC_address (sid) IP_address SNMP_community CLI_username CLI_password Model_name
=======================================================================
00:00:74:25:8a:e3:56:b4 (127704592766644 ) 17.0.3.105 public admin admin H3C_VSR
00:00:74:25:8a:e4:11:be (127704592814526 ) 17.0.2.104 public admin admin H3C_VSR
MAC_address (sid) IP_address SNMP_community CLI_username CLI_password Model_name
=======================================================================
00:00:74:25:8a:e3:56:b4 (127704592766644 ) 17.0.3.105 public admin admin H3C_VSR
00:00:74:25:8a:e4:11:be (127704592814526 ) 17.0.2.104 public admin admin H3C_VSR

Arp table on switch s1 is as follows.
IP address MAC address VLAN Interface Aging Type
17.0.0.105 000c-2961-ee6b N/A GE1/0 17 D
17.0.2.107 000c-2970-f2b2 N/A GE2/0 17 D

Then, I call rpc get-arp-table defined in file misc-config.yang to get the arp table on switch s1. But the output of this rpc is null.

 Comments   
Comment by Nanfei Chen [ 29/Feb/16 ]

I have committed two changes for this bug.

https://git.opendaylight.org/gerrit/#/c/35507/

https://git.opendaylight.org/gerrit/#/c/35508/

There will be some problems if we use the oid which consists of arpTableEntryPhyAddrOID and midStuffForArpTableEntryOID to get the arp talbe.

Because the midStuffForArpTableEntryOID is not always 5121 for all devices which come from different vendors.

Furthermore, the midStuffForArpTableEntryOID is also not a constant even for a same device. For example, when I use MG-SOFT MIB Browser software to get ipNetToMediaPhysAddress(this oid is arpTableEntryPhyAddrOID, and it is 1.3.6.1.2.1.4.22.1.2) from h3c's device, the result is as follows.

          • SNMP QUERY STARTED *****
            1: ipNetToMediaPhysAddress.37.192.168.1.1 (PhysAddress) 70:F9:6D:EB:03:17 [70.F9.6D.EB.03.17 (hex)]
            2: ipNetToMediaPhysAddress.39.192.168.5.1 (PhysAddress) 70:F9:6D:EB:03:17 [70.F9.6D.EB.03.17 (hex)]
            3: ipNetToMediaPhysAddress.47.172.168.2.1 (PhysAddress) 00:50:56:60:AC:56 [Vmware_60:AC:56]
            4: ipNetToMediaPhysAddress.26446.98.0.0.1 (PhysAddress) 00:0F:E1:21:21:15 [Id_21:21:15]
            5: ipNetToMediaPhysAddress.26446.98.0.0.5 (PhysAddress) 5C:DD:70:0F:00:D0 [5C.DD.70.0F.00.D0 (hex)]

We can see that the midStuffForArpTableEntryOID is not a constant even for a same device from this example.

Generated at Wed Feb 07 20:39:19 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.