| CAPWAP MIB should consider more about reuse | <– Date –> <– Thread –> |
|
From: Yang Richard (rishyang |
|
| Date: Mon, 7 Jan 2008 07:08:30 -0800 (PST) | |
I think it should consider more about Entity MIB (rfc 27370) reuse.
According to CAPWAP protocol, capwapWTPTable has MIB objects
such as capwapWTPManufacturerId, capwapWTPModelId and so on.
These objects are well defined by entity MIB. Re-defining them is not a
valid design. So it requires a way to reuse entity MIB.
The basic idea could be:
At AC side, entPhysicalTable could keep info for both AC and WTP.
Each WTP could be identified by PhysicalIndex, and set
entPhysicalClass as other(1). In entity MIB, manufacture, software
version, hardware version are available for each WTP.
Current capwapWTPTable table could remove objects such
as capwapWTPManufacturerId, while keep a PhysicalIndex
for a specific WTP.
By this way, entity MIB could be reused.
Regards
Richard
-
CAPWAP MIB should consider more about reuse Yang Richard, January 7 2008
- Re: CAPWAP MIB should consider more about reuse Romascanu, Dan (Dan), January 7 2008
Results generated by Tiger Technologies using MHonArc.