SYMBOL-CC-WS2000-MIB: View SNMP OID List / Download MIB

WS2000 with 1 WAN port, 6 LAN ports.

The serial number of the switch. This value is unique for each instance of the WS2000 switch.

This value is a two-character representation of the country code. Note: when changing this _CountrySelection, the current channel and power levels are NOT changed. The prior settings for these values may or may not be valid/legal for the new country selected. It is up to the network management software to ensure that channel and/or power settings are changed BEFORE changing the country selection so that no such invalid/illegal state is reached, even for a short interim. country code: Argentina: ar Australia: au Austria: at Bahrain: bh Belarus: by Belgium: be Botswana: bw Brazil: br Bulgaria: bg Canada: ca Chile: cl China: cn Colombia: co Costa Rica: cr Croatia: hr Czech Republic: cz Denmark: dk Ecuador: ec Egypt: eg Estonia: ee Finland: fi France: fr Germany: de Greece: gr Hong Kong: hk Hungary: hu Iceland: is India: in Indonesia: id Ireland: ie Israel: il Italy: it Japan: jp Jordan: jo Kazakhstan: kz Kuwait: kw Latvia: lv Liechtenstein: li Lithuania: lt Luxembourg: lu Malaysia: my Mexico: mx Morocco: ma Namibia: na Netherlands: nl New Zealand: nz Norway: no Oman: om Peru: pe Philippines: ph Poland: pl Portugal: pt Qatar: qa Romania: ro Russia: ru Saudi Arabia: sa Singapore: sg Slovak Republic: sk Slovenia: si South Africa: za South Korea: kr Spain: es Sri Lanka: lk Sweden: se Switzerland: ch Taiwan: tw Thailand: th Turkey: tr Ukraine: ua United Arab Emirates: ae United Kingdom: uk United States: us Uruguay: uy Venezuela: ve Vietnam: vn

The same text that follows 'HW=' in sysDescr, EXCLUDING the 'HW='.

The same text that follows 'FW=' in sysDescr, EXCLUDING the 'FW='. (The bootcode version).

The same text that follows 'SW=' in sysDescr, EXCLUDING the 'SW='.

The same text that follows 'MIB=' in sysDescr, EXCLUDING the 'MIB='. The MIB version is identified by a two-digit major version number (with a leading zero if needed), followed by a lower-case letter minor version and 0 or more character info number. The major MIB version is changed whenever it becomes incompatible to its previous version; i.e., some variables have been deleted or the behavior/meaning has been changed. Minor version number is changed when new features have been added, but existing behavior is completely unchanged.

The same text that follows 'CLI=' in sysDescr, EXCLUDING the 'CLI='.

Version of XML template implemented on this switch. (Much like MIB version - read details there).

The serial number of the switch. This value is unique for each instance of a given switch type.

Enable/Disable DNS Relay Mode

Enable/Disable SSLV2 Support

Enable/Disable SSHV1 Support

Enable/Disable SSL Weak Cipher Support

Writing this value causes the switch to reset to factory conditions. NOTHING is retained, NOT the static IP address assignments (if any), NOR any non-factory-default SNMP settings, nor any other non-factory-default settings. Given this, be warned that setting this value may very well cause all communication paths to the WS2000 to be lost. (However, if DHCP is used to obtain an IP addr on the WAN port, and only default SNMP settings are used, communications may be possible after the factory reset).

Writing this value causes the switch to reset in the same fashion as a common, (non-factory) reset.

Writing this value resets all counters in the ccRf > ccMus sub-tree. Obsolete in WS2000 v1.5

Performs a factory reset, EXCEPT that Wan IP and SNMP access settings are retained across the reset. Specifically: Wan Ip + related settings Pppoe settings WS2000 wan access SNMP setting SNMP v1/v2/v3 access settings

Writing this value resets all counters in the ccRf sub-tree except for the ccPortalSystemStatsTable and ccPortalTable

Specifies if the firmware is to be loaded to the switch via FTP or TFTP or SFTP or CF Card. Enumeration: 'sftpFirmwareServerToSwitch': 5, 'cfFirmwareToSwitch': 4, 'ftpFirmwareServerToSwitch': 2, 'tftpFirmwareServerToSwitch': 3, 'unspecified': 1.

The interface to use in contacting the FTP or TFTP or SFTP server. This is required since the actual firmware load is accomplished via boot code that does not contain routing logic. Enumeration: 'subnet2': 12, 'wan': 2, 'subnet1': 11, 'subnet4': 14, 'subnet3': 13, 'unspecified': 1.

The path to the firmware on the SFTP/TFTP/FTP server. Remember that the type of separator varies depending on the operating system of the server. For Windows, use '\', for Unix use '/'. No path need be specified, (in which case the default directory for the TFTP/FTP/SFTP server will be used); if a path is specified, remember to terminate it with a trailing '/' or '\'.

The name, (on the server), of the firmware file to load. If operation is set to cfFirmwareToSwitch, this variable is the file name on the compact flash card.

Set this value to start the firmware load operation. Note that the actual SFTP/TFTP/FTP does not begin immediately, as first the 'operational' firmware shuts-down, and returns to low-level boot code, which actually starts the transfer.

This value reflects the result of the most-recent firmware load since reboot, (if any).

The success/failure status of the most recent firmware load.

Specifies the type and direction of the transfer to perform involving the configuration file. Enumeration: 'ftpConfigSwitchToServer': 3, 'tftpConfigServerToSwitch': 4, 'unspecified': 1, 'sftpConfigServerToSwitch': 6, 'tftpConfigSwitchToServer': 5, 'sftpConfigSwitchToServer': 7, 'ftpConfigServerToSwitch': 2.

The path to the firmware on the SFTP/TFTP/FTP server. Remember that the type of separator varies depending on the operating system of the server. For Windows, use '\', for Unix use '/'. No path need be specified, (in which case the default directory for the SFTP/TFTP/FTP server will be used); if a path is specified, remember to terminate it with a trailing '/' or '\'.

The name, (on the server), of the configuration file to load/store from/to the server.

Set this value to start the configuration file operation. Note that unlike a firmware load, the actual FTP/TFTP/SFTP transfer does begin virtually immediately.

This value counts the total number of configuration file transfers completed, (whether they succeed or fail). The SNMP manager should save the value of this counter just before starting a LoadCfg operation, and then wait for this value to increment before checking the Result and/or Success values.

This value reflects the result of the most-recent configuration file load/store.

The success/failure status of the most recent configuration file load/store.

This value will increment by 1 or more for each config change. It persists across reboots. This variable can only be SET with the same value that it currently contains. Any other value will cause a SET-FAILED. Note that this is NOT a TEST-AND-INCREMENT semaphore, as this value does not immediately increment after a config change, but only after a short, though non-zero, delay. Because of this non-zero delay, it is not suitable as a semaphore. Note also that this value counts the number of times that Flash memory has been written, which may be greater than the number of config changes.

A snapshot of sysUpTime as of the last config change.

Can be used to solve the multiple-manager problem. Before performing any SETs, the manager reads this value. As a VAR-BIND of the only/last SET PDU, this value is written with that value read. If some other manager had made changes, this value would have incremented, and the SET to it will fail. Note that this only guards against other managers that use this semaphore. Changes made without using this value will NOT be protected against. For this reason, it is suggested that ccCfgHistChangeCount also be SET - though that is not a perfectly fail-safe semaphore, it will in most cases protect even against this latter case.

IP address of the server used for a firmware load, or configuration file load/store operation.

Username for FTP LoadFw or LoadCfg operations.

Password for FTP LoadFw or LoadCfg operations.

Counts the total number of SNMP requests rejected due to ACL violations since boot.

The IP address of the last SNMP request to be denied due to ACL violation.

SNMPv3 Engine ID

Table of SNMP v1/v2 access entries.

Description.

Simple Index.

Community Name of the SNMP manager.

Starting OID.

OID Limit whether the entire MIB tree or a specific OID set. Enumeration: 'all': 1, 'custom': 2.

Access type whether RO or RW. Enumeration: 'readWrite': 2, 'readOnly': 1.

Row Status.

Table of SNMP v3 access entries.

Description.

Simple Index.

v3 User Name.

Security Level. Enumeration: 'noAuth': 1, 'authNoPriv': 2, 'authPriv': 3.

Starting OID.

OID Limit whether the entire MIB tree or a specific OID set. Enumeration: 'all': 1, 'custom': 2.

Access type whether RO or RW. Enumeration: 'readWrite': 2, 'readOnly': 1.

Authentication Algorithm used. Enumeration: 'sha': 2, 'md5': 1.

Authentication Password.

Privacy Algorithm used. Enumeration: 'aes128': 2, 'des': 1.

Privacy Password.

Row Status.

Table of SNMP access control entries.

Description.

Simple Index.

Starting IP range of the SNMP manager allowed to access the switch.

Ending IP range of the SNMP manager allowed to access the switch.

Row Status.

Table of SNMP v1/v2 trap configuration entries.

Description.

Simple Index.

Destination IP of Trap Manager.

Destination Port of Trap Manager.

Community Name.

SNMP protocol version. Enumeration: 'snmpV1': 1, 'snmpV2': 2.

Row Status.

Table of SNMP v3 trap configuration entries.

Description.

Simple Index.

Destination IP of Trap Manager.

Destination Port of Trap Manager.

User name of SNMP v3 user.

Security Level. Enumeration: 'authNoPriv': 2, 'auth': 1, 'authPriv': 3.

SNMP v3 Authentication Algorithm. Enumeration: 'sha': 2, 'md5': 1.

SNMP v3 Authentication Password.

SNMP v3 Privacy Algorithm. Enumeration: 'aes128': 2, 'des': 1.

SNMP v3 Privacy Password.

Row Status.

Capacity of the Compact Flash card in Kbyte.

Number of Kbyte in use on the Compact Flash card.

The number of seconds backwards from the specified timestamp that the the 'Short' window extends backwards in time.

The frequency at which the 'Short' summary stats are updated.

Same as corresponding 'Short' value, for the 'Long' window.

Same as corresponding 'Short' value, for the 'Long' window.

Types of network management access to permit. Bits: 'fromLanCliTelnet': 2, 'fromWanAppletHttps': 6, 'fromWanFtp': 10, 'fromWanSsh': 8, 'fromWanSnmp': 9, 'fromLanSsh': 3, 'fromLanAppletHttps': 1, 'fromLanAppletHttp': 0, 'fromWanCliTelnet': 7, 'fromLanSnmp': 4, 'fromWanAppletHttp': 5.

Allow Airbeam smart. (If enabled, Airbeam access is only allowed from the LAN interfaces).

Airbeam password. (username is 'airbeam').

The type of authentication used to authenticate the administrator.It can be a local database or a radius server. Enumeration: 'radius': 2, 'local': 1.

Administrator password. Can only be read, (via GET), using a community string capable of writing, (via SET), the value. If an otherwise valid community string is used, a string of length 0 is returned.

The IP address of the radius server which is used to authenticate the administrator

The port of the radius server which is used to authenticate the administrator

The shared secret the radius server which is used to authenticate the administrator

The duration within which the user can enter the password after providing the user id.

The duration within which the server should receive the keep alive responses from the client. In SSH v2, the server shall timeout if does not receive Keep alive responses from the client.

HTTP/HTTPS connection timeout.

Level of logging to perform. Enumeration: 'level2Critical': 2, 'level4Warnings': 4, 'level1Alert': 1, 'level3Errors': 3, 'level6Info': 6, 'level5Notice': 5, 'level0Emergency': 0, 'level7Debug': 7.

Send logs to external syslog.

IP addr of syslog server.

Delete the Core File.

Transfer the core file to external FTP server.

Enable NTP.

Preferred NTP server IPaddr.

Preferred NTP server port number.

1st alternate NTP server IPaddr.

1st alternate NTP server port number.

2nd alternate NTP server IPaddr.

2nd alternate NTP server port number.

GMT Hour Offset. Not implemented in WS2000 2.0

GMT Minute Offset. Not implemented in WS2000 2.0

Current date/time. If NTP is not running, or has not yet synchronized the time, this value will be 0.

Synchronization Interval (in minutes)

Enable updating of firmware using DHCP vendor options

Enable updating of configuration using DHCP vendor options

The interface to use in contacting the FTP or TFTP server. This is required since the actual firmware load is accomplished via boot code that does not contain routing logic. Enumeration: 'subnet2': 3, 'wan': 1, 'subnet1': 2, 'subnet4': 5, 'subnet3': 4.

The firmware filename most recently provided via DHCP options. The success/failure of actually fetching that file via TFTP is reported in ccLoadFwSuccess and ccLoadFwResult.

The config filename most recently provided via DHCP options. The success/failure of actually fetching that file via TFTP is reported in ccLoadCfgSuccess and ccLoadCfgResult.

The desired state of redundancy for this switch. 'standAlone' is for a switch with no redundancy. 'redundantPrimary' and 'redundantStandby' for when the switch is desired to be part of a pair of switches for redundancy. 'redundantUpgrade' is used to update the firmware of one switch of a pair configured for redundancy. This mode is just like 'standAlone' except that switch will not adopt portals. Note that when configuring two switches, both starting in 'standAlone' state, configure the primary first. (If you configure the desired standby first, it will NOT hear heartbeats from the primary, and will quickly transition to _OperState = 'redundantPrimary'). Enumeration: 'standby': 2, 'primary': 1.

The actual state of redundancy for this switch. Enumeration: 'upgrade': 2, 'redundancy': 1, 'standAlone': 3.

The interface to use in contacting the FTP or TFTP server. This is required since the actual firmware load is accomplished via boot code that does not contain routing logic. Enumeration: 'port6': 6, 'port4': 4, 'port5': 5, 'port2': 2, 'port3': 3, 'port1': 1.

The duration in seconds between consecutive heartbeats. User can control the frequency of hearbeats by tuning this parameter.

The duration which the master WS2000 shall wait before taking over from a backup WS2000.

Current Operational Mode of the switch.

This table allows the admin to create and store up to three certificate signature requests. The required fields are ccSelfCertsReqKeyId and ccSelfCertReqSubject.

Simple index.

The ID for the certificate. Use this field to distinguish between certificates. This is a required field.

The subject of the certificate. This is a required field.

The department that is making the request. Contact your CA to determine whether this field is required.

The name of the organization or company that is making the request. Contact your CA to determine whether this field is required.

The name of the city where the organization resides. Contact your CA to determine whether this field is required.

The name of the state where the organzation resides. Contact your CA to determine whether this field is required.

The postal code (zip code in US) for the organization. Contact your CA to determine whether this field is required.

The two-letter ISO code for the country where the organization resides. Contact your CA to determine whether this field is required.

The email address to be used for identification purposes. Contact your CA to determine whether this field is required.

The domain name to associate with the certificate. Contact your CA to determine whether this field is required.

The WAN IP of the WS 2000 Wireless Switch. Contact your CA to determine whether this field is required.

The signature algorithm you want used for the certificate. The options are: MD5-RSA: This option uses the Message Digest 5 algorithm in combination with RSA encryption. SHA1-RSA: This options uses the Secure Hash Algorithm 1 in combination with RSA encryption. This is a required field. Enumeration: 'cryptoMd5Rsa': 1, 'cryptoSha1Rsa': 2.

The desired length of the key. Possible values are 512, 1024, and 2048. Select a lower number to enhance performance. Select a large number to enhance security. Enumeration: 'keylen1024': 2, 'keylen2048': 3, 'keylen512': 1.

Start generating certificate request.

The generated certificate request string.

Row status.

ID Name of the signed certificate.

The signed certificate.

Start importing the signed certificate from ccCertMgntSelfCertsSignedStr to a new row in ccCertMgntSelfCertsSignedTable.

This table allows the admin to store up to three signed certificates. This table supports a max size of three rows.

Simple index.

The ID for the certificate. Use this field to distinguish between certificates.

The name of the certificate authority who signed the certificate.

The subject of the certificate.

The serial number of the certificate.

The date when the certificate expires.

Delete row.

The CA certificate to be imported.

Start import operation for the CA certificate stored in ccCACertsStr. This operation adds a row in ccCACertsTable.

This table allows the admin to store up to three CA certificates. This table supports a max size of three rows.

Simple index.

The ID for the certificate. Use this field to distinguish between certificates.

The name of the certificate authority.

The subject of the certificate.

The serial number of the certificate.

The date when the certificate expires.

Delete Row.

A Portal has been adopted by the switch. Example: Portal MAC=%s1 has been adopted.

A Portal has been un-adopted by the switch. Example: Portal MAC=%s1 has been UN-adopted for reason %s2.

A Portal has been denied adoption by the switch. Example: Portal MAC=%s1 has been denied adopted for reason %s2.

An MU has been associated to a Portal adopted by this switch. Example: MU MAC=%s1 has associated to Portal MAC=%s2.

An MU has been un-associated to a Portal adopted by this switch. Example: MU MAC=%s1 has UN-associated from Portal MAC=%s2 for reason %s3.

An MU has been denied association to a Portal adopted by this switch. Example: MU MAC=%s1 has been denied association to Portal MAC=%s2 for reason %s3.

The configuration of this switch has changed. Example: The configuration of the switch changed as of sysUpTime=%s1; the total number of config changes since reboot is now %s2.

An attempt to communicate via SNMP to the switch has been denied based on configured ACLs. Example: IP-addr %s1 has attempted, but been prohibited, from communicating with the switch via SNMP; total number of such ACL violations = %s2.

A [physical] port's state has changed from up-->down, or down-->up. Example: Port %i1 has changed state to %s1.

The compact flash is almost full; (it has crossed the threshold defined by ccTrapCtrlCfAlmostFullThreshold). Example: The compact flash is almost full; Used=%s1, Capacity=%s2, Threshold=%s3.

The firewall has detected an attack in progress. Example: The WAN firewall is being attached by method %s1.

Radar has been detected on a Portal channel. Example: Radar has been detected on Portal MAC=%s1, on channel %s2.

A summary statistic has crossed the prescribed threshold by an MU. Example: Threshold '%s1' of value %s2 (units:%s3) has been crossed by MU MAC=%s4 with IP-addr=%s5.

A summary statistic has crossed the prescribed threshold by a Portal. Example: Threshold #%s1 of value %s2 (units:%s3) has been crossed by Portal index=%s4 with MAC=%s5.

A summary statistic has crossed the prescribed threshold by a WLAN. Example: Threshold #%s1 of value %s2 (units:%s3) has been crossed by WLAN index=%s4 with name=%s5.

A summary statistic has crossed the prescribed threshold by the entire Switch. Example: Threshold %s1 of value %s2 (units:%s3) has been crossed by the entire switch.

A Vlan is activated. When ever a MU is associated with the switch, and it receives a VLAN attribute from the radius server, the specified VLAN is activated.

Trap to say that the device received DHCP options instructing it to load a new fw or cnfg file, and that it has completed the transfer. The varbinds tell if the transfer was successful. Note that this trap will NOT be issued if the DHCP options specify the same file as was most recently loaded. Example: (if FW bit set in _Requested): The switch was instructed to load firmware %s2, and success=%s3 with result=%s4. (if CFG bit set in _Requested): The switch was instructed to load config %s5, and success=%s6 with result=%s7.

The state of this switch's ccRedundancyOperState has changed. Example: The switch has changed it's redundancy state to %s1.

Table of Trap Enable entries.

Description.

Simple Index. Enumeration: 'trapCtrlSnmpAuthFailure': 7, 'trapCtrlMuUnAssociated': 5, 'trapCtrlRogueApDetected': 16, 'trapCtrlSnmpConfigChanged': 10, 'trapCtrlCfAlmostFull': 11, 'trapCtrlPortalDeniedAdoption': 3, 'trapCtrlSnmpAclViolation': 8, 'trapCtrlMuDeniedAssociation': 6, 'trapCtrlMuAssociated': 4, 'trapCtrlMuAuthDenied': 14, 'trapCtrlPortalAdopted': 1, 'trapCtrlPortalUnAdopted': 2, 'trapCtrlRadarDetected': 15, 'trapCtrlPortStatusChange': 12, 'trapCtrlDenialofService': 13, 'trapCtrlSnmpColdStart': 9.

Name of the Trap.

Enable/Disbale a particular Trap.

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

A ccCfAlmostFull trap will be sent when less than this number of bytes are remained on the Compact Flash card. The trap is currently scheduled to fire every 5 minutes when the condition is met.

Description of Firewall Under Attack.

The max rate at which ccFirewallUnderAttack traps/notifications will be sent from the switch. If the switch detects a FirewallUnderAttack condition and it has NOT been at least this many seconds since the last ccFirewallUnderAttack trap/notification, this current event will NOT result in a trap/notification. If this value is set to 0, every such event results in a trap/notification. Factory-default state is 1 [second].

MAC address of the Portal that has detected Radar. (Note that this variable is accessible-for-notify only).

Channel on which Radar has been detected. (Note that this variable is accessible-for-notify only).

This table configures thresholds that can be monitored for - all MUs and/or - all Portals and/or - all WLANs and/or - for the entire switch When a given threshold is crossed, it generates the appropriate corresponding notification, (ccSumStats_: _MU, _Portal, _WLAN, or _Switch). Some thresholds result in notifications when exceeded, and some when the current value sinks below the threshold. This is indicated by the wording of the entry in the entry's _Descr value. In all cases, the summary stat being monitored is the Short value, never the Long value. Note that for thresholds of type thresholdsAvgMuSignal & thresholdsAvgMuNoise, the values being 'watched' are actually negative. In these cases the threshold is specified as a Unsigned32. For example, if you wish to trap on Signal being worse than -75dBm, enter '70'. This works since a user would never want to trap on a threshold of Sinal worse than +10dBm. (SNR is not an issue, since that is a positive value). Any values reported as var-binds in the resultant trap(s) are likewise reported as positive values.

The rows/instances in this table occur at the exact same indices as the corresponding monitored data occurs in the _SumStats tables. For example, row #2 / instance .2 represents the threshold(s) for the _PktsPerSec values for MU, Portal, WLAN, and Switch. If a given threshold does not make sense for one of those 4 entities, its corresponding TruthValue will be false.

Index into table. Note that specific thresholds occur at specific instance values as denoted by the enumeration values assigned to this variable. Enumeration: 'thresholdsPktsPerSec': 3, 'unusedTimestamp': 1, 'thresholdsPpmTxDropped': 15, 'unusedThroughputRx': 8, 'thresholdsPpmRxUndecrypt': 17, 'thresholdsAvgMuSignal': 10, 'thresholdsTxAvgRetries': 16, 'thresholdsThroughput': 6, 'thresholdsAvgMuSnr': 12, 'thresholdsAvgMuNoise': 11, 'thresholdsTotalMus': 18, 'unusedPktsPerSecRx': 5, 'unusedPktsPerSecTx': 4, 'thresholdsPpmTxWithRetires': 14, 'thresholdsPctRfUtil': 19, 'thresholdsPctNUcastPkts': 13, 'thresholdsAvgBitSpeed': 9, 'thresholdsPctDropped': 20, 'unusedThroughputTx': 7, 'unusedNumPkts': 2.

Description of the threshold.

Units of the the threshold.

If true, the threshold can be set for MUs. If false, attempting the threshold will return a READ-ONLY.

The threshold for all MUs. If 0, no threshold checking is performed.

If true, the threshold can be set for Portals. If false, attempting the threshold will return a READ-ONLY.

The threshold for all Portals. If 0, no threshold checking is performed.

If true, the threshold can be set for Wlans. If false, attempting the threshold will return a READ-ONLY.

The threshold for all Wlans. If 0, no threshold checking is performed.

If true, the threshold can be set for the entire switch. If false, attempting the threshold will return a READ-ONLY.

The threshold for the entire Switch. If 0, no threshold checking is performed.

The minimum number of packets that must be in a window/dataset before any of the threshold traps will 'fire'.

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

(place-holder for future use and to keep the last OID of each ccTrapCtrl_ item here to match the last OID of the corresponding notification).

VLAN ID to which MU has been associated. (Note that this variable is accessible-for-notify only).

DHCP request received. (Note that this variable is accessible-for-notify only). Bits: 'dhcpRequestedFwLoad': 0, 'dhcpRequestedCfgLoad': 1.

The actual state of redundancy for this switch. Enumeration: 'redundantStandby': 3, 'redundantPrimary': 2, 'redundantUpgrade': 4, 'standAlone': 1.

This table lists all Access Ports that contain at least one Portal that has been adopted by this WS2000.

Small, arbitrary integer index.

MAC address of this Access Port.

Model number of the Access Port.

Serial Number of this Access Port.

Revision of the printed circuit board for this Access Port.

Revision of the boot loader code in this Access Port.

Version of the WISP (AP-switch) protocol implemented by this Access Port.

Version of run-time code on this Access Port.

The number of Portals implemented on this Access Port.

If bit of this value is set, this ApTable entry 'points' to entry in the Portal Table. Such a reference conveys that the Portal entry pointed-to represents a Portal contained in the Access Port represented by this entry. Note that since one Access Port can implement 1, 2, (and in the future possibly more), Portals, this 'pointer' field had to be a bit-mask.

This table lists all Portals that have been adopted or have failed adoption (by this WS2000).

Small, arbitrary integer index.

This value is the index in the ApTable for the entry representing the Access Port that contains this Portal. Since each Portal has one and only one Access Port as 'parent', this value is a simple integer, not a bit-mask.

(Reserved for future implementation).

Name of this Portal, as assigned by the Web UI or CLI.

Location string for this Portal, as assigned by the Web UI or CLI.

This value describes the presence/absence of internal and/or external primary and/or secondary antennas. Bits: 'undefined07': 7, 'undefined06': 6, 'undefined05': 5, 'undefined04': 4, 'undefined03': 3, 'undefined02': 2, 'undefined01': 1, 'undefined00': 0, 'externalSecondaryAntInstalled': 12, 'externalPrimaryAntInstalled': 14, 'undefined09': 9, 'undefined08': 8, 'internalSecondaryAntInstalled': 13, 'internalPrimaryAntInstalled': 15, 'undefined10': 10, 'undefined11': 11.

MAC address of the Portal.

The number of ESSs implemented by this Portal.

The number of BSSs implemented by this Portal.

The number of MUs currently associated to this Portal.

Radio type of the Portal.

The value describes the channel the Portal is currently operating on. Enumeration: 'ieee802dot11aChannel149': 149, 'ieee802dot11aChannel064': 64, 'ieee802dot11aChannel060': 60, 'ieee802dot11aChannel048': 48, 'ieee802dot11aChannel044': 44, 'ieee802dot11aChannel040': 40, 'ieee802dot11bChannel04': 4, 'ieee802dot11bChannel05': 5, 'ieee802dot11bChannel06': 6, 'ieee802dot11bChannel07': 7, 'ieee802dot11bChannel01': 1, 'ieee802dot11bChannel02': 2, 'ieee802dot11bChannel03': 3, 'ieee802dot11bChannel08': 8, 'ieee802dot11bChannel09': 9, 'ieee802dot11aChannel161': 161, 'ieee802dot11aChannel157': 157, 'ieee802dot11aChannel052': 52, 'ieee802dot11aChannel056': 56, 'ieee802dot11aChannel153': 153, 'ieee802dot11aChannel036': 36, 'ieee802dot11bChannel13': 13, 'ieee802dot11bChannel12': 12, 'ieee802dot11bChannel11': 11, 'ieee802dot11bChannel10': 10, 'ieee802dot11bChannel14': 14.

Output power level for the Portal.

A snapshot of the WS2000's sysUpTime when this Portal was last adopted.

This value describes the state of the Portal. A healthy Portal would power-on, and quickly advance from portalUpAndWaitingForConfig and then on to portalReceivingConfig and then on to portalUpAndAdopted. A Portal that is denied adoption due to ACLs would show: portalDeniedAdoptionDueToAcl. A Portal that does not 'handshake' with the switch properly would be found in state: portalBroken. Enumeration: 'portalDeniedAdoptionDueToAcl': 4, 'portalBroken': 5, 'portalUpAndWaitingForConfig': 1, 'portalUpAndAdopted': 3, 'portalReceivingConfig': 2.

Total packets received via the Portal included in all the other counters reported in this row.

The best Signal value seen from the Portal so far. (Remember that a -20dBm Signal is better than -60dBm). This value is initialized to 500dBm.

The worst Signal value seen from the Portal so far. (Remember that a -80dBm Signal is worse than -60dBm). This value is initialized to -500dBm.

A running sum of all Signal values calculated by the switch (using reported RSSI values), for packets received via this Portal. Note that this value is normally a negative value ranging from -10dBm to -80dBm. It is possible for this value to be positive, but that would be rare, and would signal an exceptionally strong signal. (This value divided by ccPortalRxRssiNumPkts yields the average Signal value for all packets received from this Portal).

A sum of the squares of each Signal value calculated for packets received via this Portal. Unlike _SignalSum, this value is never negative, since the square of a negative number is a positive. (This value can be used to calculate the standard deviation for Signal values calculated for packets from this Portal).

This scalar records the MAC address of the most recent Portal to be Adopted, UnAdopted, or Denied.

This value notes the reason for the most-recent Portal UnAdoption or Denial. Enumeration: 'aclViolation': 2, 'timeout': 3, 'success': 1.

Table describing which WLANs are eligible to adopt a new portal. The illegal MAC address value of 'FF:FF:FF:FF:FF:FF' is used in both _StartMac and _EndMac fields to indicate the special row used to declare 'default' behavior. That is, if no other row in the table applies, which WLANs are eligible to adopt the portal. This one special row cannot be deleted.

Table that describes which portals can be adopted by which WLANs.

Starting MAC address of range of MAC addresses.

Ending MAC address of range of MAC addresses.

Pointer to zero or more WLANs which are eligible to adopt portals whose MAC address falls within the specified range. Any WLAN selected by this value must first be removed from the 'default' row first. Note that to make an adoption rule apply to more than one WLAN, you must create multiple rows in this table. (This is due to the way the adoption rules are stored inside the switch).

Simple row status.

This table includes statistics for 802.11 system packets transmitted/received at each Portal.

The number of Beacons sent.

The number of octets sent in Beacons.

The number of Probe Request packets received.

The number of octets received in Probe Request packets.

The number of Probe Response packets sent with no retries.

The number of Probe Response packets sent with exactly 1 retry.

The number of Probe Response packets sent with exactly 2 retries.

The number of Probe Response packets sent with exactly 3 retries or more retries.

The number of Probe Response packets that were never successfully transmitted because the max retry count was reached.

The number of octets successfully transmitted in Probe Response packets. (For example, the octets in a Probe Response that is transmitted twice - one retry - only counts once in this sum).

Use ccPortalSettingsTable to view and set the properties of the Access Ports.

Name of Access Port.

Site location of Access Port.

The antenna diversity setting for the access port. Enumeration: 'secondaryOnly': 3, 'primaryOnly': 2, 'fullDiversity': 1.

Enable support for Short Preamble when MUs associate with the Access Port. Enabling Short Preamble may cause incompatibility with some older clients.

Eable the Uniform Spreading feature of the AP300. To comply with Dynamic Frequency Selection(DFS) requirements in the European Union, the 802.11a radio on AP300 Access Ports will come up on a random channel each time it is powered on.

The Request To Send(RTS) threshold(in bytes) for use by the WLAN's adopted Access Port.

Specify a beacon interval in units of 1,000 microseconds (K-us). This is a multiple of the DTIM (ccPortalCfgDefaultADtimPrd) value, for example, 100 : 10.

Specify a period for the Delivery Traffic Indication Message (DTIM). This is a divisor of the beacon interval (in milliseconds), for example, 10 : 100.

Enable the Secure Beacon checkbox to disallow the Access Port from broadcasting an ESSID in its beacons. This is a safeguard to prevent intruders from tapping into the WLAN. Consider this security measure for a private, corporate network.

Associate a primary WLAN with the Access Port for broadcast of the Extended Service Set Identification (ESSID). The purpose of such broadcasting is to allow mobile units to identify Access Ports that are associated with the WLAN.

List of basic rates for the radio.

List of supported rates for the radio.

Radio mode. Enumeration: 'modeG': 2, 'modeBandG': 1, 'modeB': 3.

Enable the bits for the WLANs you wish to associate the Access Port with.

Description.

Use ccPortalCfgRadioTable to view and set the radio properties of the Access Ports. The process can be broken down into the following steps: 1. Set ccPortalCfgRadioReset to TRUE. 2. Set ccPortalCfgRadioDesPlacement 3. Get ccPortalCfgRadioPosChannel 4. Set ccPortalCfgRadioDesChannel 5. Get ccPortalCfgRadioPosPowerLevel 6. Set ccPortalCfgRadioDesPowerLevel 7. Get ccPortalCfgRadioPowerInMW 8. Set and pull progress of ccPortalCfgRadioSet 9. Validate the configuration has been set by getting ccPortalCfgRadioPlacement ccPortalCfgRadioChannel ccPortalCfgRadioPowerLevel

The desired placement for radio. Enumeration: 'outdoor': 2, 'indoor': 1.

The possible channels that can be set when placement = ccPortalCfgRadioDesPlacement. Bits: 'achannel36': 12, 'achannel149': 20, 'null': 0, 'achannel161': 23, 'bchannel09': 9, 'bchannel08': 8, 'bchannel01': 1, 'bchannel03': 3, 'bchannel02': 2, 'bchannel05': 5, 'bchannel04': 4, 'bchannel07': 7, 'bchannel06': 6, 'achannel40': 13, 'achannel44': 14, 'achannel48': 15, 'achannel64': 19, 'achannel60': 18, 'achannel157': 22, 'achannel153': 21, 'bchannel10': 10, 'bchannel11': 11, 'achannel56': 17, 'achannel52': 16.

The desired channel for radio. Enumeration: 'achannel36': 36, 'achannel149': 149, 'null': 0, 'achannel161': 161, 'bchannel09': 9, 'bchannel08': 8, 'bchannel01': 1, 'bchannel03': 3, 'bchannel02': 2, 'bchannel05': 5, 'bchannel04': 4, 'bchannel07': 7, 'bchannel06': 6, 'achannel40': 40, 'achannel44': 44, 'achannel48': 48, 'achannel64': 64, 'achannel60': 60, 'achannel157': 157, 'achannel153': 153, 'bchannel10': 10, 'bchannel11': 11, 'achannel56': 56, 'achannel52': 52.

The max possible power level (dBm) that can be set when channel= ccPortalCfgRadioDesChannel.

The desired power level (dBm) for radio.

ccPortalCfgRadioDesPowerLevel in mW.

Validate values in ccPortalCfgRadioDes_ fields. If it is a valid combination, configure the switch with this combination and set ccPortalCfgRadio_ to these values.

Reset the following OIDs. ccPortalCfgRadioDesPlacement ccPortalCfgRadioDesChannel ccPortalCfgRadioDesPowerLevel ccPortalCfgRadioPosChannel ccPortalCfgRadioPosPowerLevel ccPortalCfgRadioPowerInMW

The placement configuration for radio. Enumeration: 'outdoor': 2, 'indoor': 1.

The channel configuration for radio. Enumeration: 'achannel36': 36, 'achannel149': 149, 'null': 0, 'achannel161': 161, 'bchannel09': 9, 'bchannel08': 8, 'bchannel01': 1, 'bchannel03': 3, 'bchannel02': 2, 'bchannel05': 5, 'bchannel04': 4, 'bchannel07': 7, 'bchannel06': 6, 'achannel40': 40, 'achannel44': 44, 'achannel48': 48, 'achannel64': 64, 'achannel60': 60, 'achannel157': 157, 'achannel153': 153, 'bchannel10': 10, 'bchannel11': 11, 'achannel56': 56, 'achannel52': 52.

The power level (dBm) configuration for radio.

ccPortalCfgRadioPowerLevel in mW.

The ccPortalSettingsDefaultsTable contains the initial settings for the Access Ports.

The type of the radio Enumeration: 'radioG': 3, 'radioA': 1, 'radioB': 2.

The antenna diversity setting for the access port. Enumeration: 'secondaryOnly': 3, 'primaryOnly': 2, 'fullDiversity': 1.

Enable support for Short Preamble when MUs associate with the Access Port. Enabling Short Preamble may cause incompatibility with some older clients.

Eable the Uniform Spreading feature of the AP300. To comply with Dynamic Frequency Selection(DFS) requirements in the European Union, the 802.11a radio on AP300 Access Ports will come up on a random channel each time it is powered on.

The Request To Send(RTS) threshold(in bytes) for use by the WLAN's adopted Access Port.

Specify a beacon interval in units of 1,000 microseconds (K-us). This is a multiple of the DTIM (ccPortalCfgDefaultADtimPrd) value, for example, 100 : 10.

Specify a period for the Delivery Traffic Indication Message (DTIM). This is a divisor of the beacon interval (in milliseconds), for example, 10 : 100.

Enable the Secure Beacon checkbox to disallow the Access Port from broadcasting an ESSID in its beacons. This is a safeguard to prevent intruders from tapping into the WLAN. Consider this security measure for a private, corporate network.

Associate a primary WLAN with the Access Port for broadcast of the Extended Service Set Identification (ESSID). The purpose of such broadcasting is to allow mobile units to identify Access Ports that are associated with the WLAN.

List of basic rates for the radio.

List of supported rates for the radio.

Radio mode. Enumeration: 'modeG': 2, 'modeBandG': 1, 'modeB': 3.

The ccPortalCfgRadioDefaultTable contains the initial settings for the radio settings of the Access Ports. Please refer to descriptions in ccPortalCfgRadioTable.

The default desired placement for radio type. Enumeration: 'outdoor': 2, 'indoor': 1.

The possible channels that can be set when placement = ccPortalCfgRadioDefaultDesPlacement. Bits: 'achannel36': 12, 'achannel149': 20, 'null': 0, 'achannel161': 23, 'bchannel09': 9, 'bchannel08': 8, 'bchannel01': 1, 'bchannel03': 3, 'bchannel02': 2, 'bchannel05': 5, 'bchannel04': 4, 'bchannel07': 7, 'bchannel06': 6, 'achannel40': 13, 'achannel44': 14, 'achannel48': 15, 'achannel64': 19, 'achannel60': 18, 'achannel157': 22, 'achannel153': 21, 'bchannel10': 10, 'bchannel11': 11, 'achannel56': 17, 'achannel52': 16.

The default desired channel for radio type. Enumeration: 'achannel36': 36, 'achannel149': 149, 'null': 0, 'achannel161': 161, 'bchannel09': 9, 'bchannel08': 8, 'bchannel01': 1, 'bchannel03': 3, 'bchannel02': 2, 'bchannel05': 5, 'bchannel04': 4, 'bchannel07': 7, 'bchannel06': 6, 'achannel40': 40, 'achannel44': 44, 'achannel48': 48, 'achannel64': 64, 'achannel60': 60, 'achannel157': 157, 'achannel153': 153, 'bchannel10': 10, 'bchannel11': 11, 'achannel56': 56, 'achannel52': 52.

The max possible power level (dBm) that can be set when channel= ccPortalCfgRadioDefaultDesChannel.

The desired power level (dBm) for radio.

ccPortalCfgRadioDefaultDesPowerLevel in mW.

Validate values in ccPortalCfgRadioDefaultDes_ fields. If it is a valid combination, configure the switch with this combination and set ccPortalCfgRadioDefault_ to these values.

Reset the following OIDs. ccPortalCfgRadioDefaultDesPlacement ccPortalCfgRadioDefaultDesChannel ccPortalCfgRadioDefaultDesPowerLevel ccPortalCfgRadioDefaultPosChannel ccPortalCfgRadioDefaultPosPowerLevel ccPortalCfgRadioDefaultPowerInMW

The default placement configuration for radio type. Enumeration: 'outdoor': 2, 'indoor': 1.

The default channel configuration for radio type. Enumeration: 'achannel36': 36, 'achannel149': 149, 'null': 0, 'achannel161': 161, 'bchannel09': 9, 'bchannel08': 8, 'bchannel01': 1, 'bchannel03': 3, 'bchannel02': 2, 'bchannel05': 5, 'bchannel04': 4, 'bchannel07': 7, 'bchannel06': 6, 'achannel40': 40, 'achannel44': 44, 'achannel48': 48, 'achannel64': 64, 'achannel60': 60, 'achannel157': 157, 'achannel153': 153, 'bchannel10': 10, 'bchannel11': 11, 'achannel56': 56, 'achannel52': 52.

The default power level (dBm) configuration for radio type.

ccPortalCfgRadioDefaultPowerLevel in mW.

802.1x Port Authentication username.

802.1x Port Authentication password.

Set the username and password stored in cc802dt1xPortAuthLogin and cc802dt1xPortAuthPass on all AP 300 Access Ports adopted by the switch.

This table describes general statistics about packets sent/recieved via each Portal on the switch.

Count of unicast packets sent via the Portal.

Count of unicast packets received via the Portal.

Count of non-unicast (broadcast & multicast) packets received via the Portal.

Count of unicast octets sent via the Portal.

Count of unicast octets received via the Portal.

Count of non-unicast (broadcast & multicast) octets received via the Portal.

Count of packets received via the Portal that could not be decrypted.

A snapshot of the switch's sysUpTime at the time of the last activity (packet sent or received) via the Portal.

For each Portal on the switch, this table describes counts of packets received at each possible speed, (1Mb, 2Mb, 5.5Mb, 6Mb...).

Number of pkts received via this Portal at 1 Mb.

Number of pkts received via this Portal at 2 Mb.

Number of pkts received via this Portal at 5.5 Mb.

Number of pkts received via this Portal at 6 Mb.

Number of pkts received via this Portal at 9 Mb.

Number of pkts received via this Portal at 11 Mb.

Number of pkts received via this Portal at 12 Mb.

Number of pkts received via this Portal at 18 Mb.

Number of pkts received via this Portal at 22 Mb.

Number of pkts received via this Portal at 24 Mb.

Number of pkts received via this Portal at 36 Mb.

Number of pkts received via this Portal at 48 Mb.

Number of pkts received via this Portal at 54 Mb.

For each Portal on the switch, this table describes counts of packets transmitted at each possible speed, (1Mb, 2Mb, 5.5Mb, 6Mb...).

Number of pkts transmitted via this Portal at 1 Mb.

Number of pkts transmitted via this Portal at 2 Mb.

Number of pkts transmitted via this Portal at 5.5 Mb.

Number of pkts transmitted via this Portal at 6 Mb.

Number of pkts transmitted via this Portal at 9 Mb.

Number of pkts transmitted via this Portal at 11 Mb.

Number of pkts transmitted via this Portal at 12 Mb.

Number of pkts transmitted via this Portal at 18 Mb.

Number of pkts transmitted via this Portal at 22 Mb.

Number of pkts transmitted via this Portal at 24 Mb.

Number of pkts transmitted via this Portal at 36 Mb.

Number of pkts transmitted via this Portal at 48 Mb.

Number of pkts transmitted via this Portal at 54 Mb.

For each Portal on this switch, this table describes counts of octets received at each possible speed, (1Mb, 2Mb, 5.5Mb, 6Mb...).

Number of octets received via this Portal at 1 Mb.

Number of octets received via this Portal at 2 Mb.

Number of octets received via this Portal at 5.5 Mb.

Number of octets received via this Portal at 6 Mb.

Number of octets received via this Portal at 9 Mb.

Number of octets received via this Portal at 11 Mb.

Number of octets received via this Portal at 12 Mb.

Number of octets received via this Portal at 18 Mb.

Number of octets received via this Portal at 22 Mb.

Number of octets received via this Portal at 24 Mb.

Number of octets received via this Portal at 36 Mb.

Number of octets received via this Portal at 48 Mb.

Number of octets received via this Portal at 54 Mb.

For each Portal on this switch, this table describes counts of octets transmitted at each possible speed, (1Mb, 2Mb, 5.5Mb, 6Mb...).

Number octets transmitted via this Portal at 1 Mb.

Number octets transmitted via this Portal at 2 Mb.

Number octets transmitted via this Portal at 5.5 Mb.

Number octets transmitted via this Portal at 6 Mb.

Number octets transmitted via this Portal at 9 Mb.

Number octets transmitted via this Portal at 11 Mb.

Number octets transmitted via this Portal at 12 Mb.

Number octets transmitted via this Portal at 18 Mb.

Number octets transmitted via this Portal at 22 Mb.

Number octets transmitted via this Portal at 24 Mb.

Number octets transmitted via this Portal at 36 Mb.

Number octets transmitted via this Portal at 48 Mb.

Number octets transmitted via this Portal at 54 Mb.

For each Portal on the switch, this table describes counts of the number of packets affected by transmit retries, (no retries, 1 retry, 2 retries,... gave-up).

Number of pkts successfully transmitted via this Portal with no retries.

Number of pkts successfully transmitted via this Portal with exactly 1 retry.

Number of pkts successfully transmitted via this Portal with exactly 2 retries.

Number of pkts successfully transmitted via this Portal with exactly 3 retries.

Number of pkts successfully transmitted via this Portal with exactly 4 retries.

Number of pkts successfully transmitted via this Portal with exactly 5 retries.

Number of pkts successfully transmitted via this Portal with exactly 6 retries.

Number of pkts successfully transmitted via this Portal with exactly 7 retries.

Number of pkts successfully transmitted via this Portal with exactly 8 retries.

Number of pkts successfully transmitted via this Portal with exactly 9 retries.

Number of pkts successfully transmitted via this Portal with exactly 10 retries.

Number of pkts successfully transmitted via this Portal with exactly 11 retries.

Number of pkts successfully transmitted via this Portal with exactly 12 retries.

Number of pkts successfully transmitted via this Portal with exactly 13 retries.

Number of pkts successfully transmitted via this Portal with exactly 14 retries.

Number of pkts successfully transmitted via this Portal with exactly 15 retries.

Number of pkts that never were successfully transmitted to via this Portal because the max retry count was exceeded.

For each Portal on the switch, this table describes counts of the number of octets affected by transmit retries, (no retries, 1 retry, 2 retries,... gave-up).

Number of octets successfully transmitted via this Portal with no retries.

Number of octets successfully transmitted via this Portal with exactly 1 retry.

Number of octets successfully transmitted via this Portal with exactly 2 retries.

Number of octets successfully transmitted via this Portal with exactly 3 retries.

Number of octets successfully transmitted via this Portal with exactly 4 retries.

Number of octets successfully transmitted via this Portal with exactly 5 retries.

Number of octets successfully transmitted via this Portal with exactly 6 retries.

Number of octets successfully transmitted via this Portal with exactly 7 retries.

Number of octets successfully transmitted via this Portal with exactly 8 retries.

Number of octets successfully transmitted via this Portal with exactly 9 retries.

Number of octets successfully transmitted via this Portal with exactly 10 retries.

Number of octets successfully transmitted via this Portal with exactly 11 retries.

Number of octets successfully transmitted via this Portal with exactly 12 retries.

Number of octets successfully transmitted via this Portal with exactly 13 retries.

Number of octets successfully transmitted via this Portal with exactly 14 retries.

Number of octets successfully transmitted via this Portal with exactly 15 retries.

Number of octets that never were successfully transmitted to via this Portal because the max retry count was exceeded.

This table describes statistics about RSSI, Signal, Noise, and SNR for packets recieved via each Portal on the switch.

Total packets received via the Portal included in all the other counters reported in this row.

The best Signal value seen from the Portal so far. (Remember that a -20dBm Signal is better than -60dBm). This value is initialized to -500dBm.

The worst Signal value seen from the Portal so far. (Remember that a -80dBm Signal is worse than -60dBm). This value is initialized to 500dBm.

A running sum of all Signal values calculated by the switch (using reported RSSI values), for packets received via this Portal. Note that this value is normally a negative value ranging from -10dBm to -80dBm. It is possible for this value to be positive, but that would be rare, and would signal an exceptionally strong signal. (This value divided by ccPortalSigStatsNumPkts yields the average Signal value for all packets received from this MU).

A sum of the squares of each Signal value calculated for packets received via this Portal. Unlike _SignalSum, this value is never negative, since the square of a negative number is a positive. (This value can be used to calculate the standard deviation for Signal values calculated for packets from this Portal).

The best Signal value seen from the Portal so far. (Remember that a -20dBm Signal is better than -60dBm). This value does not make sense when ccPortalSigStatsNumPkts equals to 0.

The best Noise value seen from the Portal so far. (Remember that -80dBm Noise is better than -70dBm). This value is initialized to 500dBm.

The worst Noise value seen from the Portal so far. (Remember that -50dBm Noise is worse than -60dBm). This value is initialized to -500dBm.

A running sum of all Noise values calculated by the switch (using reported RSSI values), for packets received via this Portal. Like _SignalSum, this value is normally a negative value. (This value divided by ccPortalSigStatsNumPkts yields the average Noise value for all packets received from this MU).

A sum of the squares of each Noise value calculated for packets received via this Portal. As with _SignalSumSquares, this value is never negative. (This value can be used to calculate the standard deviation for Noise values calculated for packets from this Portal).

The best Noise value seen from the Portal so far. (Remember that -80dBm Noise is better than -70dBm). This value does not make sense when ccPortalSigStatsNumPkts equals to 0.

The best SNR value seen from the Portal so far. (Remember that +30dBm SNR is better than +20dBm). This value is initialized to -500dB.

The worst SNR value seen from the Portal so far. (Remember that +10dBm SNR is worse than +20dBm). This value is initialized to 500dB.

A running sum of all SNR values calculated by the switch (using reported RSSI values), for packets received via this Portal. Unlike _Signal and _Noise, this value is never negative. (This value divided by ccPortalSigStatsNumPkts yields the average SNR value for all packets received from this MU).

A sum of the squares of each SNR value calculated for packets received via this Portal. This value is never negative. (This value can be used to calculate the standard deviation for SNR values calculated for packets from this Portal).

The best SNR value seen from the Portal so far. (Remember that +30dBm SNR is better than +20dBm). This value does not make sense when ccPortalSigStatsNumPkts equals to 0.

Averages and rates calculated over the SHORT window for each Portal.

Snapshot of sysUpTime as of the END of the 'window' of time that this entry of values represents.

The number of packets used to calculate the statistics in this window.

Packets per second as averaged over the 'window'. For transmitted packets, each packet sucessfully sent counts as 1, (not N, where N is the number of retries). Since SNMP does not convey decimal values, the result is multiplied by 100.

Packets per second TX as averaged over the 'window'. Each packet sucessfully sent counts as 1, (not N, where N is the number of retries). Since SNMP does not convey decimal values, the result is multiplied by 100.

Packets per second RX as averaged over the 'window'. Since SNMP does not convey decimal values, the result is multiplied by 100.

Actual number of bits sent and received over the window, divided by the number of seconds in the window. For transmitted packets, each packet sucessfully sent counts as 1, (not N, where N is the number of retries).

Actual number of bits TX over the window, divided by the number of seconds in the window. Each packet sucessfully sent counts as 1, (not N, where N is the number of retries).

Actual number of bits RX over the window, divided by the number of seconds in the window.

An octet-weighted average of the speeds of all packets sent/received. (For each possible speed, multiply the number of octets sent/received by that speed; divide the sum by the total number of octets; multiply by 8). For transmitted packets, each packet sucessfully sent counts as 1, (not N, where N is the number of retries). This can be said in more plain english as: the average bit-speed at which packets were sent/received.

The average of all signal values over the window. NOTE: dBm are normally negative. Here the NEGATIVE values are reported as POSITIVE values. PO

The average of all noise values over the window.

The average of all SNR values over the window.

Ratio of packets that were NOT unicast. Expressed as parts-per-10000.

Ratio of TX packets that experienced one or more retries. Expressed as parts-per-10000.

Ratio of TX packets that were dropped due to excessive. Expressed as parts-per-10000.

For all transmit packets (those that experienced some retries, those that were successfully transmitted with only 1 transmission, and those that attempted max times and gave-up), the average number of RE-transmission attempts. Said another (though identical) way: the sum of all tranmission attempts divided by the number of unique packets attempted to be sent. Since SNMP does not convey decimal values, the result above is multiplied by 100. If there were no RE-transmissions, this value would be 0. If every single packet required exactly two tranmissions, this value would be 100, (representing 1.00).

Ratio of RX packets that were undecryptable. Expressed as parts-per-10000.

The total number of MUs associated to the given Portal.

The approximate utilization of the Portal's RF port. Calculated as Throughput divided by AvgBitSpeed. Expressed as parts-per-10000.

Averages and rates calculated over the LONG window for each Portal. (Refer to ccPortalSumStatsShortTable for descriptions).

This table contains one entry for each Portal-MU association.

A snapshot of the switch's sysUpTime at the time of the first time this MU associated to this Portal.

A snapshot of the switch's sysUpTime at the time of the time this MU most recently associated to this Portal.

A count of the total number of times this MU has associated to this Portal.

This table describes general information about each MU serviced by the switch.

MAC address of the MU.

(Reserved for future implementation).

The name of the WLAN this MU is associated to.

This value is true if the WS2000 is ready to forward/switch packets to/from this MU, (internally called the 'data ready' state). Otherwise this value is false.

The index of the entry in the PortalTable to which this MU is associated.

The MAC address of the Portal to which this MU is associated.

If true, this MU supports Symbol's Rogue AP detection assist algorithm.

IP address of the MU.

Type of the MU. Enumeration: 'voice': 2, 'data': 1, 'accessPoint': 3.

Radio type of the MU.

A bit-mask of rates supported by this MU. Bits: 'supports22Mb': 8, 'supports11Mb': 5, 'supports48Mb': 11, 'supports24Mb': 9, 'supports54Mb': 12, 'supports9Mb': 4, 'supports6Mb': 3, 'supports5dot5Mb': 2, 'supports1Mb': 0, 'supports12Mb': 6, 'supports36Mb': 10, 'supports2Mb': 1, 'supports18Mb': 7.

Power-mode implemented by the MU. A MU's status will constantly switch between PSP and CAM mode when it is in PSP mode. Enumeration: 'powerSavePolling': 2, 'continuousAccessMode': 1.

Authentication method implemented by the MU. Enumeration: 'none': 1, 'kerberos': 3, 'eap802dot1x': 2.

Encryption method implemented by the MU. Enumeration: 'none': 1, 'wpaTKIP': 5, 'wep128': 3, 'wpa2AesCcmp': 6, 'keyGuardMCM': 4, 'wep40': 2.

The VLAN that this MU is assigned to.

This table describes general statistics about packets sent/recieved via each MU serviced by the switch.

Count of unicast packets sent.

Count of unicast packets received.

Count of non-unicast (broadcast & multicast) packets received.

Count of unicast octets sent.

Count of unicast octets received.

Count of non-unicast (broadcast & multicast) octets received.

Count of packets received that could not be decrypted.

Total RSSI packets received.

A running sum of all RSSI values calculated by the switch for packets.

A sum of the squares of each RSSI value calculated for packets received. This value is never negative.

The best RSSI value seen so far. (Remember that -80dBm Noise is better than -70dBm). This value does not make sense when ccMuRxRssiNumPkts equals to 0.

A snapshot of the switch's sysUpTime at the time of the last activity (packet sent or received).

For each MU serviced by the switch, this table describes counts of packets received at each possible speed, (1Mb, 2Mb, 5.5Mb, 6Mb...).

Number of pkts received at 1 Mb.

Number of pkts received at 2 Mb.

Number of pkts received at 5.5 Mb.

Number of pkts received at 6 Mb.

Number of pkts received at 9 Mb.

Number of pkts received at 11 Mb.

Number of pkts received at 12 Mb.

Number of pkts received at 18 Mb.

Number of pkts received at 22 Mb.

Number of pkts received at 24 Mb.

Number of pkts received at 36 Mb.

Number of pkts received at 48 Mb.

Number of pkts received at 54 Mb.

For each MU serviced by the switch, this table describes counts of packets transmitted at each possible speed, (1Mb, 2Mb, 5.5Mb, 6Mb...).

Number of pkts transmitted at 1 Mb.

Number of pkts transmitted at 2 Mb.

Number of pkts transmitted at 5.5 Mb.

Number of pkts transmitted at 6 Mb.

Number of pkts transmitted at 9 Mb.

Number of pkts transmitted at 11 Mb.

Number of pkts transmitted at 12 Mb.

Number of pkts transmitted at 18 Mb.

Number of pkts transmitted at 22 Mb.

Number of pkts transmitted at 24 Mb.

Number of pkts transmitted at 36 Mb.

Number of pkts transmitted at 48 Mb.

Number of pkts transmitted at 54 Mb.

For each MU serviced by this switch, this table describes counts of octets received at each possible speed, (1Mb, 2Mb, 5.5Mb, 6Mb...).

Number of octets received at 1 Mb.

Number of octets received at 2 Mb.

Number of octets received at 5.5 Mb.

Number of octets received at 6 Mb.

Number of octets received at 9 Mb.

Number of octets received at 11 Mb.

Number of octets received at 12 Mb.

Number of octets received at 18 Mb.

Number of octets received at 22 Mb.

Number of octets received at 24 Mb.

Number of octets received at 36 Mb.

Number of octets received at 48 Mb.

Number of octets received at 54 Mb.

For each MU serviced by this switch, this table describes counts of octets transmitted at each possible speed, (1Mb, 2Mb, 5.5Mb, 6Mb...).

Number of octets transmitted at 1 Mb.

Number of octets transmitted at 2 Mb.

Number of octets transmitted at 5.5 Mb.

Number of octets transmitted at 6 Mb.

Number of octets transmitted at 9 Mb.

Number of octets transmitted at 11 Mb.

Number of octets transmitted at 12 Mb.

Number of octets transmitted at 18 Mb.

Number of octets transmitted at 22 Mb.

Number of octets transmitted at 24 Mb.

Number of octets transmitted at 36 Mb.

Number of octets transmitted at 48 Mb.

Number of octets transmitted at 54 Mb.

For each MU serviced by the switch, this table describes counts of the number of packets affected by transmit retries, (no retries, 1 retry, 2 retries,... gave-up).

Number of pkts successfully transmitted with no retries.

Number of pkts successfully transmitted with exactly 1 retries.

Number of pkts successfully transmitted with exactly 2 retries.

Number of pkts successfully transmitted with exactly 3 retries.

Number of pkts successfully transmitted with exactly 4 retries.

Number of pkts successfully transmitted with exactly 5 retries.

Number of pkts successfully transmitted with exactly 6 retries.

Number of pkts successfully transmitted with exactly 7 retries.

Number of pkts successfully transmitted with exactly 8 retries.

Number of pkts successfully transmitted with exactly 9 retries.

Number of pkts successfully transmitted with exactly 10 retries.

Number of pkts successfully transmitted with exactly 11 retries.

Number of pkts successfully transmitted with exactly 12 retries.

Number of pkts successfully transmitted with exactly 13 retries.

Number of pkts successfully transmitted with exactly 14 retries.

Number of pkts successfully transmitted with exactly 15 retries.

Number of pkts that never were successfully transmitted to because the max retry count was exceeded.

A total sum of all retries across all packets sent to this MU. For example, if 4 packets have been sent, with the following number of retires: 2, 0, 5, gave-up, this value would be 2+0+5+16 = 23.

Most recent retry done by MU.

This scalar records the MAC address of the most recent MU to be Adopted, UnAdopted, or Denied.

This value notes the reason for the most-recent MU UnAdoption or Denial. Enum item associationFailed indicates that a key association field was missing, or a mismatch of supported rates, etc. Enumeration: 'timeout': 3, 'success': 1, 'associationFailed': 4, 'authenticationFailedOn802dot1x': 5, 'kerberosWrongUsername': 6, 'aclViolation': 2.

This value notes the reason for the most-recent MU UnAdoption or Denial.

For each MU serviced by the switch, this table describes counts of the number of octets affected by transmit retries, (no retries, 1 retry, 2 retries,... gave-up).

Number of octets successfully transmitted with no retries.

Number of octets successfully transmitted with exactly 1 retries.

Number of octets successfully transmitted with exactly 2 retries.

Number of octets successfully transmitted with exactly 3 retries.

Number of octets successfully transmitted with exactly 4 retries.

Number of octets successfully transmitted with exactly 5 retries.

Number of octets successfully transmitted with exactly 6 retries.

Number of octets successfully transmitted with exactly 7 retries.

Number of octets successfully transmitted with exactly 8 retries.

Number of octets successfully transmitted with exactly 9 retries.

Number of octets successfully transmitted with exactly 10 retries.

Number of octets successfully transmitted with exactly 11 retries.

Number of octets successfully transmitted with exactly 12 retries.

Number of octets successfully transmitted with exactly 13 retries.

Number of octets successfully transmitted with exactly 14 retries.

Number of octets successfully transmitted with exactly 15 retries.

Number of octets that never were successfully transmitted to because the max retry count was exceeded.

This table describes statistics about RSSI, Signal, Noise, and SNR for packets recieved via each MU serviced by the switch.

Total packets received included in all the other counters reported in this row.

The best Signal value seen so far. (Remember that a -20dBm Signal is better than -60dBm). This value is initialized to -500dBm.

The worst Signal value seen so far. (Remember that a -80dBm Signal is worse than -60dBm). This value is initialized to 500dBm.

A running sum of all Signal values calculated by the switch (using reported RSSI values), for packets received. Note that this value is normally a negative value ranging from -10dBm to -80dBm. It is possible for this value to be positive, but that would be rare, and would signal an exceptionally strong signal.

A sum of the squares of each Signal value calculated for packets received. Unlike _SignalSum, this value is never negative, since the square of a negative number is a positive.

The best Signal value seen so far. (Remember that a -20dBm Signal is better than -60dBm). This value does not make sense when ccMuSigStatsNumPkts equals to 0.

The best Noise value seen so far. (Remember that -80dBm Noise is better than -70dBm). This value is initialized to 500dBm.

The worst Noise value seen so far. (Remember that -50dBm Noise is worse than -60dBm). This value is initialized to -500dBm.

A running sum of all Noise values calculated by the switch (using reported RSSI values), for packets. Like _SignalSum, this value is normally a negative value.

A sum of the squares of each Noise value calculated for packets received. As with _SignalSumSquares, this value is never negative.

The best Noise value seen so far. (Remember that -80dBm Noise is better than -70dBm). This value does not make sense when ccMuSigStatsNumPkts equals to 0.

The best SNR value seen so far. (Remember that +30dBm SNR is better than +20dBm). This value is initialized to -500dB.

The worst SNR value seen so far. (Remember that +10dBm SNR is worse than +20dBm). This value is initialized to 500dB.

A running sum of all SNR values calculated by the switch (using reported RSSI values), for packets received. Unlike _Signal and _Noise, this value is never negative.

A sum of the squares of each SNR value calculated for packets received. This value is never negative.

The best SNR value seen so far. (Remember that +30dBm SNR is better than +20dBm). This value does not make sense when ccMuSigStatsNumPkts equals to 0.

Averages and rates calculated over the SHORT window for each MU.

Snapshot of sysUpTime as of the END of the 'window' of time that this entry of values represents.

The number of packets used to calculate the statistics in this window.

Packets per second as averaged over the 'window'. For transmitted packets, each packet sucessfully sent counts as 1, (not N, where N is the number of retries). Since SNMP does not convey decimal values, the result is multiplied by 100.

Packets per second TX as averaged over the 'window'. Each packet sucessfully sent counts as 1, (not N, where N is the number of retries). Since SNMP does not convey decimal values, the result is multiplied by 100.

Packets per second RX as averaged over the 'window'. Since SNMP does not convey decimal values, the result is multiplied by 100.

Actual number of bits sent and received over the window, divided by the number of seconds in the window. For transmitted packets, each packet sucessfully sent counts as 1, (not N, where N is the number of retries).

Actual number of bits TX over the window, divided by the number of seconds in the window. Each packet sucessfully sent counts as 1, (not N, where N is the number of retries).

Actual number of bits RX over the window, divided by the number of seconds in the window.

An octet-weighted average of the speeds of all packets sent/received. (For each possible speed, multiply the number of octets sent/received by that speed; divide the sum by the total number of octets; multiply by 8). For transmitted packets, each packet sucessfully sent counts as 1, (not N, where N is the number of retries). This can be said in more plain english as: the average bit-speed at which packets were sent/received.

The average of all signal values over the window. NOTE: dBm are normally negative. Here the NEGATIVE values are reported as POSITIVE values. PO

The average of all noise values over the window.

The average of all SNR values over the window.

Ratio of packets that were NOT unicast. Expressed as parts-per-10000.

Ratio of TX packets that experienced one or more retries. Expressed as parts-per-10000.

Packets dropped divided by packets sent. Dropped here means dropped intentionally due to the appropriate QoS queue being full. Other reasons for dropped packets are not counted in this ratio. Calculated as an average for all WLANs implemented on this MU.

For all transmit packets (those that experienced some retries, those that were successfully transmitted with only 1 transmission, and those that attempted max times and gave-up), the average number of RE-transmission attempts. Said another (though identical) way: the sum of all tranmission attempts divided by the number of unique packets attempted to be sent. Since SNMP does not convey decimal values, the result above is multiplied by 100. If there were no RE-transmissions, this value would be 0. If every single packet required exactly two tranmissions, this value would be 100, (representing 1.00).

Ratio of RX packets that were undecryptable. Expressed as parts-per-10000.

Averages and rates calculated over the LONG window for each MU. (Refer to ccMuSumStatsShortTable for descriptions).

Table of wireless LANs configured on the switch.

Simple index. (In the ccRfSum tables, entry 1001 is used to represent the roll-up of all RF communications on this switch).

Name of the WLAN.

ESSID of the WLAN.

The subnet/LAN this WLAN is associated with. If not associated with any subnet/LAN, this value will be 0.

Pointer to portal(s) adopted by this WLAN.

Row enable.

Set to true to prohibit MU-to-MU communication.

Enable voice prioritization.

Answer broadcast ESS.

Multicast address 1.

Multicast address 2.

Describes the default behavior if none of this WLAN's ccWlanMuAclTable entries match the MAC address of an MU attempting to associate with this WLAN. Enumeration: 'allowAllMusExceptThoseMatchingAclRules': 1, 'denyAllMusExceptThoseMatchingAclRules': 2.

If auth802dot1xEap, additional EAP settings for this WLAN will be used from the matching entry in the ccWlanAuthEapTable. Likewise, if authKerberos, use the settings in the matching entry in the ccWlanAuthKerberosTable. Enumeration: 'authKerberos': 3, 'auth802dot1xEap': 2, 'authNone': 1.

If cryptoWep40 or cryptoWep128, additional WEP settings for this WLAN will be used from the matching entry in the ccWlanCryptoWepTable. Likewise, if cryptoWpaTkip, use the settings in the matching entry in the ccWlanCryptoWpaTable. Likewise, if cryptoKeyguardMcm, use the settings in the matching entry in the ccWlanCryptoKeyguardTable. Enumeration: 'cryptoWpa2Ccmp': 6, 'cryptoWep104': 3, 'cryptoWep40': 2, 'cryptoKeyguardMcm': 4, 'cryptoNone': 1, 'cryptoWpaTkip': 5.

The weight to be used when QoS for all WLANs is set to weighted-round-robin. Note that the sum of all weights across all WLANs need not total 100.

Table of EAP authentication settings for each WLAN.

Enable reauthentication.

Reauthentication period.

Reauthentication max retries.

IP address of the primary RADIUS server.

Port number of the primary RADIUS server.

Shared secret of the primary RADIUS server.

IP address of the secondary RADIUS server.

Port number of the secondary RADIUS server.

Shared secret of the secondary RADIUS server.

MU quiet period.

MU timeout.

MU Tx period.

MU max retries.

Server timeout.

Server max retries.

Radius Accounting Mode.

Radius Accounting MU Timeout.

Radius Accounting MU Retries.

Logging Mode.

Syslog Server IP Address.

Table of Kerberos authentication settings for each WLAN.

Realm name.

Username.

Password.

Primary KDC server IP addr.