106 3Com VCX V7111 VoIP SIP Gateways User ManualThe act of compiling the MIB allows the manager to know about the special objectssupported by the agent and access these objects as part of the standard object set.VCX V7111 Gateway Supported MIBsThe VCX V7111 Gateway contains an embedded SNMP Agent supporting the followingMIBs: The Standard MIB (MIB-II) – The various SNMP values in the standard MIB are definedin RFC 1213. The standard MIB includes various objects to measure and monitor IPactivity, TCP activity, UDP activity, IP routes, TCP connections, interfaces, and generalsystem description. RTP MIB – The RTP MIB is supported per the RFC 2959. It contains objects relevant tothe RTP streams generated and terminated by the Gateway and to the RTCP informationrelated to these streams. AcBoard MIB – This proprietary MIB contains objects related both to the configuration ofthe Gateway and channels as well as to run-time information. Through this MIB, you canset up the Gateway configuration parameters, reset the Gateway, and monitor theGateway’s operational robustness and quality of service during run-time.Web ManagementOverviewThe VCX V7111 Gateway contains an Embedded Web Server to be used both for Gatewayconfiguration, including downloading of configuration files, and for run-time monitoring. TheWeb server can be accessed from any standard web browser, such as Microsoft InternetExplorer or Netscape Navigator. Specifically, you can employ this facility to set up theGateway configuration parameters needed to configure the Gateway. You also have theoption to reset the Gateway to apply the new set of parameters.Access to the Embedded Web Server is controlled by protection and security mechanismsdescribed in the following sections.The 8FXS, 8FXO, 4FXS, 4FXO, and 2FXS Gateways have identical functionality(the 2FXS supports FXS only), except for the number of channels, and are referredto collectively in this manual as the VCX V7111.Password ControlThe Embedded Web Server is protected by a unique username-password combination. Thefirst time a browser request is made, you are requested to provide its username-password sothat you can obtain access. Subsequent requests are negotiated by the browser on behalf ofthe User, so that you do not have to re-enter the username-password for each request, butthe request is still authenticated.