Tcp/ip su management, Loading multiple sus into sudb using dload command, Managing ap from su side of network – Trango Broadband Access5830 User Manual

Page 46

Advertising
background image

Management

Trango Broadband Wireless — Access5830 User Manual Rev. F

page 42

TCP/IP SU Management

As noted in the “Getting Started” section, it is possible to use the telnet and HTTP interface to manage the SU from the AP side
of the wireless connection as long as switch #2 (TCP/IP for AP switch) is turned on at the SU. To turn on switch 2 (while
logged into the AP) use the following command:

su sw <su-id | all> 2 on

Example: su sw 2 all on (to turn on switch 2 for all associated SUs)

Note: Switch 2 default from factory is on.

Loading Multiple SUs into SUDB using DLOAD Command

To load a full database of SU entries into the AP SUDB, you need to create a SUDB in ASCII text file format. As shown
below, each row represents all information for one SU. Each column is an information field, which includes: SU ID, SU to SU
group, service level, CIR, MIR, and MAC address.

0001 0001 3000 9999 0001 de01 0203 --- Subscriber 1

0003 0011 5000 9999 0001 de04 0506
0004 0011 0512 9999 0001 de01 0203 --- Subscriber 4
0000 0000 0000 0000 0000 0000 0000 --- End of file indicator
---- ---- ---- ---- --------------
| || | | |
| || | | |---------- MAC Address
| || | |-------------------- MIR (Kbps)
| || |------------------------- CIR (Kbps)
| ||----------------------------- Service level
| | (5: priority user)
| | (1: regular user)
| |------------------------------ Peer-to-peer group #
| | (1 to F in hex)
|----------------------------------- SU ID (1~8192)

1. telnet into the AP, run command tftpd on to enable tftp process
2. tftp the file to the AP from your DOS prompt example: tftp <IP of AP> put mySUs.txt
3. telnet into the AP
4. Run

command

sudb dload to load and activate the database

5. Run command sudb view to verify the database entries

Run command updateflash sudb to write the database to non-volatile memory.

Managing AP from SU side of Network

The Access5830 was designed to prevent users on the SU side of the network from accessing the AP via telnet or HTTP
interface. If it is necessary for network administrators to access an AP from the SU side of the network the user must first
telnet into a router, or similar device, located behind the AP, then telnet from the router into the AP.

SNMP
The Access5830 supports Simple Network Management Protocol (SNMP) for network management. Network management
consists of the following 4 categories: configuration, accounting, alarm, and monitoring and control. These capabilities allow
the network operator to provide superior services through higher network accessibility and integrated accounting systems. For
more information on SNMP and its uses, you can visit http://www.faqs.org/faqs/snmp-faq/.

The Trango SNMP solution supports MIB-II (system only) and the Trango proprietary Management Information Base (MIB).
The SNMP agent resides on the AP ONLY. It gathers health, status, and performance statistics from all SUs locally, then
responds back to the SNMP manager upon request.

Users interested in using the SNMP functionality should review the entire Access5830 MIB for a complete understanding of its
features.

The following is an overview of a few of the more commonly used SNMP objects in the Access5830 system.

Advertising