HIPATH-WIRELESS-BRANCH-OFFICE-MIB

All MIBs › HIPATH-WIRELESS-BRANCH-OFFICE-MIB

Organization: Chantry Networks Inc.

Last Updated: 2005-07-29

Category: Domain: Wireless, Vendor: Siemens, Wireless and WLAN

Description: Siemens HiPath Wireless MIB for branch office controller configuration managing remote WLAN branch deployments.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is HIPATH-WIRELESS-BRANCH-OFFICE-MIB?

HIPATH-WIRELESS-BRANCH-OFFICE-MIB is a Siemens (later Enterasys/Extreme-lineage) HiPath Wireless MIB for configuring branch-office deployments of the HiPath wireless LAN access controller product line, targeting remote-site WLAN rollouts managed from a central controller. It exposes configuration data specific to branch-office operation, such as remote site provisioning and controller association settings for the branch deployment model. Its monitoring relevance is largely configuration-status oriented for a remote-office WLAN topology: verifying a branch site's controller association and provisioning state is intact helps confirm the remote WLAN is being properly managed rather than operating disconnected from central policy. It depends on the broader HiPath Wireless Controller (HWC) MIB and access-point management framework for core WLAN operation, radio, and client data. It is deployed at branch/remote office sites using Siemens/Enterasys HiPath wireless controllers managed from a central or regional HWC. Engineers can download the HIPATH-WIRELESS-BRANCH-OFFICE-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in HIPATH-WIRELESS-BRANCH-OFFICE-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

Siemens/Enterasys HiPath wireless branch-office controller

Monitoring Examples

No sample object names were supplied in the source for this module, so specific OIDs cannot be cited, but conceptually an administrator would check a branch site's controller-association state and provisioning status to confirm the remote WLAN deployment is correctly registered with its central HiPath Wireless Controller. A branch site reporting an unassociated or unprovisioned state would indicate a lost connection to the controlling HWC or a configuration push failure.

What Can Be Monitored

branch site controller association state
branch provisioning status

Imported Objects

From HIPATH-WIRELESS-HWC-MIB

apIndex

OBJECT-TYPE

From HIPATH-WIRELESS-SMI

hiPathWirelessMgmt	OBJECT-IDENTITY
hiPathWirelessModules	OBJECT-IDENTITY

From RFC1155-SMI

enterprises

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

RowStatus

OIDs

OID symbolic	OID numeric	Type	Access	Description
hiPathWirelessBranchOfficeMIB	1.3.6.1.4.1.4329.15.3.22
branchOfficeObjects	1.3.6.1.4.1.4329.15.3.22.1
branchOfficeTable	1.3.6.1.4.1.4329.15.3.22.1.1		not-accessible	Table of branch office configuration values for the access points.
branchOfficeEntry	1.3.6.1.4.1.4329.15.3.22.1.1.1		not-accessible	Branch office configuration values for a specific access point.
INT boConnectMode	1.3.6.1.4.1.4329.15.3.22.1.1.1.1	INTEGER	read-write	Access point connection mode - use a static definition or service discovery.
INT boIpAllocation	1.3.6.1.4.1.4329.15.3.22.1.1.1.2	INTEGER	read-write	Indicates if access point is to use DHCP to acquire an IP address or has a statically configured IP address.
IP boStaticIpAddress	1.3.6.1.4.1.4329.15.3.22.1.1.1.3	IpAddress	read-write	If access point is statically configured, contains the IP addres.
IP boStaticNetmask	1.3.6.1.4.1.4329.15.3.22.1.1.1.4	IpAddress	read-write	Netmask for the access point if statically configured.
IP boStaticGateway	1.3.6.1.4.1.4329.15.3.22.1.1.1.5	IpAddress	read-write	Default gateway for the access point if statically configured.
I32 boRebootOnPollFailure	1.3.6.1.4.1.4329.15.3.22.1.1.1.6	Integer32	read-write	Indicates if access point should reboot on a poll failure (disabling wireless access) or continue to provide limited local wireless service.
branchOfficeHWCTable	1.3.6.1.4.1.4329.15.3.22.1.2		not-accessible	Contains the list of access controller IP addressIf an access point has a static.
branchOfficeHWCEntry	1.3.6.1.4.1.4329.15.3.22.1.2.1		not-accessible	The access controller search list for an access point.
I32 boHWCConnectOrder	1.3.6.1.4.1.4329.15.3.22.1.2.1.1	Integer32	read-write	The position of the access controller in the search list.
IP boHWCIpAddress	1.3.6.1.4.1.4329.15.3.22.1.2.1.2	IpAddress	read-write	IP address of the access controller.
ROW boHWCRowStatus	1.3.6.1.4.1.4329.15.3.22.1.2.1.3	RowStatus	read-write	RowStatus attribute to control modification of branchOfficeHWCTable.
hiPathWirelessBranchOfficeConformance	1.3.6.1.4.1.4329.15.3.22.2
hiPathWirelessBranchOfficeGroup	1.3.6.1.4.1.4329.15.3.22.2.1			Conformance group definitions for the branch office MIB.
hiPathWirelessBOConformance	1.3.6.1.4.1.4329.15.3.22.2.2			Compliance group definitions for the branch office MIB.
hiPathWirelessBOObsoleteGroup	1.3.6.1.4.1.4329.15.3.22.2.3			Description.

RFC description

Branch office configuration management for Siemens/Chantry wireless LAN access controllers.

Start monitoring Siemens/Enterasys HiPath Wireless branch-office controller with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download HIPATH-WIRELESS-BRANCH-OFFICE-MIB

What Is HIPATH-WIRELESS-BRANCH-OFFICE-MIB?

Supported Devices

Monitoring Examples

What Can Be Monitored

This MIB depends on

Related MIBs

RFC description