1 / 7

MIB Discussions for TGk

MIB Discussions for TGk. Byoung-Jo “J” Kim macsbug@research.att.com AT&T Labs-Research. Per-STA table. Include STA, AP under MAC branch Elementary data to enable various algorithms for deducing situations From any frame successfully decoded during normal operations

teegan-cunningham
Download Presentation

MIB Discussions for TGk

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MIB Discussions for TGk Byoung-Jo “J” Kim macsbug@research.att.com AT&T Labs-Research Byoung-Jo “J” Kim, AT&T Labs-Research

  2. Per-STA table • Include STA, AP under MAC branch • Elementary data to enable various algorithms for deducing situations • From any frame successfully decoded during normal operations • Includes STA from other BSS • Locally observed, mostly passively • Not particularly intended to be sent over the air to other STA • Maybe some parts if overlapping variables exist in action/report • Most likely only AP has it • Not useful for Clients without SNMP agent • STA will do measurement per TGk Actions and Reports, that may or may not be stored in TGk tables under SMT branch, if SNMP agents exists. Byoung-Jo “J” Kim, AT&T Labs-Research

  3. Potential Uses • Features that can be obtained via customizable SNMP tools, added by equipment manufacturers or management software vendors • Detect Rogue: MAC addresses and other info for STA/AP outside of BSS • Detect Potentially Overlapping BSS: # of STAs outside of BSS and # packets from them • Detect Potential Coverage Problems: consistently low RCPI/RSSI/PSNI from a set of STAs in BSS • Identify new AP locations • Long-term Load monitoring/balance, Coarse location tracking • Usage data for upgrade planning • System-wide Frequency Selection based on long-term stats • System-wide Power adjustment • Identify Trouble Makers: e.g., too much multicast from a STA • Supplement Accounting information • Distinguish system-wide problem from link-specific problem • Remote diagnosis of STAs and APs Byoung-Jo “J” Kim, AT&T Labs-Research

  4. Notes • Enable third-party network management software developed for various aspects of 802.11 • Proprietary implementations exist in some APs • Elementary information is better for unanticipated usage • Avoid purpose-specific parameters • Latest or Instantaneous values better than nothing • Can be statistically sampled via SNMP. 100% is not needed • Some form of tracking is even better • Mostly Passive during normal operations • Configurable aging parameters to keep the table size small and relevent • 40 bytes per STA despite the length in MIB definition text Byoung-Jo “J” Kim, AT&T Labs-Research

  5. dot11staStatsEntry Dot11staStatsEntry ::= SEQUENCE { dot11staAddress MacAddress, ifIndex Integer32, dot11staBSSID MacAddress, dot11staSSID OCTET STRING, -- >> J Kim: The below is basically a copy of dot11CountersTable except -- dot11FCSErrorCounter, dot11MulticastTransmittedFrameCounter -- that do not make sense for this table dot11staTransmittedFragmentCount Counter32, dot11staFailedCount Counter32, dot11staRetryCount Counter32, -- >> J Kim: Any use for distinguishing short and long retries? dot11staMultipleRetryCount Counter32, dot11staFrameDuplicateCount Counter32, dot11staRTSSuccessCount Counter32, dot11staRTSFailureCount Counter32, dot11staACKFailureCount Counter32, dot11staReceivedFragmentCount Counter32, dot11staMulticastReceivedFrameCount Counter32, dot11staTransmittedFrameCount Counter32, dot11staWEPUndecryptableCount Counter32, -- >> J Kim: Similarity to CountersTable ends here Byoung-Jo “J” Kim, AT&T Labs-Research

  6. continued dot11staReceivedByteCount Counter32, dot11staTransmittedByteCount Counter32, dot11staRSSI Integer32, dot11staRxSignalQuality Integer32, dot11staType INTEGER, dot11staState INTEGER, dot11staAID Unsigned32, dot11staPHYType INTEGER, dot11staCurrentChannel INTEGER, dot11staSecurityStatus INTEGER, -- >> J Kim: the RSSI histogram in this table is using the similar format as that of 11h RPI histogram. -- However, this is RSSI from dot11staAddress measured by this STA on this ifIndex, -- if measured during routine operation or requested by the dot11staAddress which may be -- also stored in the dot11ReportsTable. -- RSSI histograms measured not by this STA and reported back to this STA from other STA -- is recorded in the dot11ReportsTable under SMT branch. dot11staRSSIhistogram OCTET STRING, dot11staRSSIhistogramDuration Unsigned32, dot11staRSSIhistogramTime TimeTicks, dot11staTxRate Unsigned32, dot11staRxRate Unsigned32, dot11staRoamed INTEGER, dot11staLastSeen TimeTicks} -- >> J Kim: 11h TPC report results are kept under SMT branch -- >> J Kim: Add any Capability Information? Byoung-Jo “J” Kim, AT&T Labs-Research

  7. Addition in dot11phy branch Dot11PhyDSSSEntry ::= SEQUENCE { dot11CurrentChannel INTEGER, dot11CCAModeSupported INTEGER, dot11CurrentCCAMode INTEGER, dot11EDThreshold Integer32, -- >> J Kim: TGk addition starts dot11DSSSCCABusyFraction INTEGER, dot11DSSSCCAMeasurementDuration INTEGER, -- >> These following two are just reminders for potential variables on per interface received power stat -- dot11DSSSAverageRxPower INTEGER, -- dot11DSSSAveragePxPowerDuration Unsigned32, dot11DSSSAverageNoisePower Integer32, dot11DSSSAverageCCAPositivePower Integer32, dot11PLDUCRCError Counter32} -- >> J Kim: TGK addition ends Byoung-Jo “J” Kim, AT&T Labs-Research

More Related