[Alexandr N]

Подскажите как можно снять таблицу соответствия mac -> port.

Не может walk считать next oid.

 

# snmpwalk -v2c -On -c test 192.168.100.2 .1.3.6.1.2.1.17.7.1.2.2.1.2
.1.3.6.1.2.1.17.7.1.2.2.1.2.1.0.12.66.198.228.88 = INTEGER: 1
.1.3.6.1.2.1.17.7.1.2.2.1.2.1.0.12.66.198.228.54 = INTEGER: 1
Error: OID not increasing: .1.3.6.1.2.1.17.7.1.2.2.1.2.1.0.12.66.198.228.88
>= .1.3.6.1.2.1.17.7.1.2.2.1.2.1.0.12.66.198.228.54

[ShyLion]

Подскажите как можно снять таблицу соответствия mac -> port.

Не может walk считать next oid.

 

# snmpwalk -v2c -On -c test 192.168.100.2 .1.3.6.1.2.1.17.7.1.2.2.1.2
.1.3.6.1.2.1.17.7.1.2.2.1.2.1.0.12.66.198.228.88 = INTEGER: 1
.1.3.6.1.2.1.17.7.1.2.2.1.2.1.0.12.66.198.228.54 = INTEGER: 1
Error: OID not increasing: .1.3.6.1.2.1.17.7.1.2.2.1.2.1.0.12.66.198.228.88
>= .1.3.6.1.2.1.17.7.1.2.2.1.2.1.0.12.66.198.228.54

 

From the snmpwalk man page:

 

-Cc Do not check whether the returned OIDs are increasing. Some agents (LaserJets are an example) return OIDs out of order, but can complete the walk anyway. Other agents return OIDs that are out of order and can cause snmpwalk to loop indefinitely. By default, snmpwalk tries to detect this behavior and warns you when it hits an agent acting illegally. Use -Cc to turn off this behaviour.

 

Некоторые прекрасные прошивки могут бесконечно отдавать данные если не контролировать уникальность полученых OID.

[Alexandr N]

 

-Cc Do not check whether the returned OIDs are increasing. Some agents (LaserJets are an example) return OIDs out of order, but can complete the walk anyway. Other agents return OIDs that are out of order and can cause snmpwalk to loop indefinitely. By default, snmpwalk tries to detect this behavior and warns you when it hits an agent acting illegally. Use -Cc to turn off this behaviour.

 

 

Спасибо, такой вариант вполне работает