| RE: Another Way to Think about CAPWAP | <– Date –> <– Thread –> |
|
From: Branislav Meandzija (bran |
|
| Date: Thu, 13 Nov 2003 10:28:05 -0600 (CST) | |
> So here's a possible other way to think about CAPWAP, > inspired by talking > with Bernard Abboba, that may point a way out of the "to SNMP > or not to > SNMP" discussion. > > Here at IETF 58, the NOC apparently has provisoned with "too > many" access > points, and partially as a result, the access points keep > appearing and > disappearing as the load changes and they interfere with each other, > according to some conversation we were having last night. This is a problem (I haven't noticed any service problems here at the IETF) but I do not understand what it has to do with "to SNMP or not to SNMP". Anything "to many" we can deal with using an intermediate hierarchy level, lets call it MOC. NOC to MOC is more of a network reposititory type of a problem. MOC to AP is clearly an SNMP, or whatever the chosen standard IETF management protocol is, type of a problem. Branislav
-
Another Way to Think about CAPWAP James Kempf, November 13 2003
-
Re: Another Way to Think about CAPWAP s. goswami, November 13 2003
- Re: Another Way to Think about CAPWAP James Kempf, November 13 2003
- RE: Another Way to Think about CAPWAP john.loughney, November 13 2003
- RE: Another Way to Think about CAPWAP Branislav Meandzija, November 13 2003
- Re: Another Way to Think about CAPWAP James Kempf, November 13 2003
-
Re: Another Way to Think about CAPWAP s. goswami, November 13 2003
-
RE: Another Way to Think about CAPWAP Branislav Meandzija, November 13 2003
- Re: Another Way to Think about CAPWAP James Kempf, November 13 2003
- RE: Another Way to Think about CAPWAP Pat R. Calhoun, November 13 2003
Results generated by Tiger Technologies using MHonArc.