Motorola 3.1 manual Network DHCP Scheme, Statically Provisioned Scheme, User Supplied Scheme

Page 24
3.3.1 Network DHCP Scheme

3.3.1 Network DHCP Scheme

Network DHCP means that the VMM device can be configured to request an address from a DHCP server and requires the inclusion of a DHCP server in the core network configuration to answer these requests. With Network DHCP selected, the VMM will send DHCP requests for its own address to the core network once it becomes associated and establishes communications with the infrastructure. Operation under the Network DHCP scheme allows users to temporarily wander outside of the network infrastructure without losing connectivity.

The server may be configured by the operator to hand out temporary or static leases. The VMM must associate and acquire an address from the network before establishing communications. Once a lease has been granted, the address will be valid out of network coverage for the remainder of the lease or, if a static lease was granted, until the next power cycle. If the lease expires or the user cycles power while outside of network coverage, the user will again lose the ability to communicate with the wireless network.

This scheme is best for a larger, closely managed network of subscribers who don't need to communicate or communicate only briefly outside of network coverage.

3.3.2 Statically Provisioned Scheme

Under the Statically Provisioned scheme, the VMM device will use provisioned DHCP-like information to establish an IP address for use in the wireless network. A DHCP server is not required on the core network because the addresses are derived from the MAC address by default. It should be noted that a DHCP server can still exist on the network to hand out addresses to other nodes using the Network DHCP Scheme as long as the server's address range does not conflict with addresses assigned to devices using the Statically Provisioned or User Supplied Schemes.

The IP addresses and options used are configurable per-device using MeshManager. The provisioned address may be freely used to communicate while associated or unassociated.

The operator must ensure that the provisioned addresses are routable and do not conflict with any other addresses in use. The operator is free to provision any option ordinarily provisioned by a DHCP server (subnet mask, DNS, etc.) through programming of the appropriate fields in each device using MeshManager.

This scheme is ideal for a managed network of users who regularly need to communicate inside and outside of network coverage or for a network lacking a DHCP server.

3.3.3 User Supplied Scheme

Operating under the User Supplied scheme, the VMM device is configured to use a fixed IP address and subnet mask. The user is responsible for configuring options that would otherwise be configured by a DHCP server.

It is also up to the user to ensure that the assigned address is routable on the core network (if core network access is needed) and that it does not conflict with other addresses in use. This is analogous to and carries the same caveats as plugging an Ethernet card into a LAN and manually assigning an address to the card.

The user is free to communicate while associated or unassociated. This scheme is ideal for small, unmanaged networks lacking a DHCP server.

16

Page 23 Page 25
Image 24
Page 23 Page 25
Contents MEA 3.1 Vehicle Mounted Modem Users Guide Documentation RevisionPage Mesh Enabled Access VMM Users GuideCopyrights DisclaimerPage Table of Contents DEVICE INSTALLATIONDEVICE CONFIGURATION Mesh Enabled AccessVMM Users GuideDEVICE MAINTENANCE CUSTOMER SERVICE INFORMATIONSetting User Supplied IP Addresses Changing the Web Interface PasswordWARRANTY INFORMATION Regulatory and RF Safety ExposureREGULATORY INFORMATION Return Material RequestMEA Device Administration Home Page Super User Login MEA Device Administration Home Page Normal User LoginVMM Configuration Page Normal User Account Configuration Change Dialog1.1 Product Contents 1 Product Introduction2 Device Installation 2.1 Software Requirements2.2 Equipment Requirements 2.3 MAC Address Label Location 2.3.1 MAC Address TableMAC Address Table MAC Address 00-05-12-0A-xx-yy2.4 VMM6300 Assembly Information 2.5 Installing the VMM6300 DeviceFigure 2-1. VMM External Connection Point 2.6 Testing the Device Installation 2.5.1 Deployment Considerations2.5.1.1 Deployment Tips Figure 2-2. VMM6300 Trunk Mounting5. Right-click on the device MAC address and select the Ping option 3 Device Configuration 3.2 Accessing the MEA Device Administration Web Pages3.2.1 Administrator and Access Account Information 3.1 IP Addressing Considerations3.2.1.1 Password Information Administrator PasswordAccess User Password 3.2.2 Viewing MEA Device Administration Redirect Page Figure 3-2. MEA Device Administration Redirecting Web Page3.2.3 Viewing MEA Device Administration Home Page as an Administrator Figure 3-3. MEA Device Administration Home Page Super User Login3.2.4 Viewing MEA Device Administration Home Page as a Normal User Figure 3-4. MEA Device Administration Home Page Normal User Login3.2.5 VMM Device Administration Configuration Tab 3.2.5.1 Viewing the VMM Configuration Tab as an Administrator3.2.5.2 Viewing the VMM Configuration Tab as a Normal User Mesh Enabled AccessVehicle Mounted Modem Users GuideField Default Value Wired Interface3.2.6 VMM Device Administration Geo Position Tab Figure 3-6. VMM Configuration Page Normal User Account3.3 Device Addressing Schemes 3.3.1 Network DHCP Scheme 3.3.2 Statically Provisioned Scheme3.3.3 User Supplied Scheme 3.4 Setting User Supplied IP Addresses Figure 3-8. Configuration Change DialogFigure 3-9. System Update Save Completed Web Page 3.5 External Device Provisioning Figure 3-10. External Device Provisioning Table3.5.1 Connecting to the Ethernet Port 3.6 Working with MeshTrayselect Programs Æ mea Æ MeshTray.exe 3.6.1 MeshTray Status Information Figure 3-11. MeshTray Status Tab VMM3.6.3 MeshTray Authentication Activity 3.6.2 MeshTray Security TabFigure 3-12. MeshTray Security Tab VMM Figure 3-13. MeshTray Authentication Activity tab VMM 4 Device Maintenance 4.1 Changing the Web Interface PasswordFigure 4-1. Enter New Password Web Page Figure 4-2. Confirm Changes Window for Enter New Password Figure 4-3. Password Changed Confirmation Web PageFigure 4-4. Update Device Firmware Web Page 4.2 Upgrading the Device FirmwareFigure 4-5. Confirm Upload Window for Firmware Update Figure 4-6. Firmware Upload Progress Web PageOnce the filename has been confirmed, the web browser will transmit the file to the device, and the device will present an upgrade progress screen. This page will indicate the current stage in the upgrade process 4.3 Security Provisioning Web Page 4.3.1 Provision Username Section4.3.2 Provision Groupname Section Figure 4-7. Security Provisioning Web Page4.4 Resetting the VMM via the Device Administration Web Page Figure 4-8. Device Reset Prompt Web PageFigure 4-9. Device Reset in Progress Page 4.5 Restoring Factory Settings - User Supplied Mode Limitations 4.5.1 Recovering from VMM Reset-to-Default in User-Supplied Mode4.5.1.1 Resetting Device Addressing Mode Using Device Manager 4.5.1.2 Resetting Device Addressing Mode via Configuration Web Page4.6 Restoring Factory Settings - Normal Operations Figure 4-10. Restore Factory Settings Web PageFigure 4-11. Confirm Changes Window for Restore Factory Settings Figure 4-12. Factory Settings Restored Web PageThe Factory Settings Restored page will be displayed Click on the Finished button to complete the reset procedure5 Customer Service Information EuropeEmail essc@motorola.com Asia and Pacific Region5.2.1 Radio Products and Services Division 5.1 Obtaining Support5.2 Return Material Request 5.1.1 System Information5.2.1.1 Radio Products and Services Division Telephone Numbers 5.2.2 Returning System Components to Motorola5.2.3 Returning FREs 6 Warranty Information G Batteries they carry their own separate limited warranty P Loading of software upgrades or fixes into the devicesB Defects or damage from misuse, accident, water, or neglect F Product which has had the serial number removed or made illegibleequipment or software not furnished by Motorola which is attached to or used in connection with the Product. The foregoing states the entire liability of Motorola with respect to infringement of patents by the Product or any its parts thereof 7.3 Regulatory and RF Safety Exposure 7 Regulatory Information7.1 FCC Information 7.2 FCC RF Energy Exposure StatementRF Exposure Compliance and Guidelines Operating Instructions Ministry of Health Canada Safety Code 6. Limits of Human Exposure to
Top Page Image Contents