Sponsored Content
Top Forums UNIX for Advanced & Expert Users DBsurvey syntax for cellular networks Post 8367 by roylevalle on Wednesday 10th of October 2001 02:34:39 PM
Old 10-10-2001
DBsurvey syntax for cellular networks

I'm trying to find the syntax for running DBsurvey scripts in UNIX. This is for a Sprint's cellular network (Lucent hardware). I can't find anything in Sprint or Lucent documents. Can anyone help me? A simple script looks like this:

DB: ecp
MATCH: field_name GE 1
OUTPUT: field_name1 field_name2 field_name3, etc ...
ENDDB

Thanks,
Roy
 

7 More Discussions You Might Find Interesting

1. AIX

AIX versus Networks

HI folks, Actually i have a network engineer having 2 and 1/2 years of experience in cisco having CCNA certification also. Now my company offering me to move to AIX field. I am new to AIX and do not know more about that field. So i want a suggestion from you peoples, that I have to join AIX or... (5 Replies)
Discussion started by: rawatmohinder
5 Replies

2. What is on Your Mind?

Networks alternative to Internet

I've read about BITNET, CompuServe... CompuServe was probably not a network but an online service. Are (were) there any other networks alternative to Internet? Does anyone have experience with them? Do they still exist, is it possible to access them over Internet? There seems not to be another way... (13 Replies)
Discussion started by: Action
13 Replies

3. Solaris

Multiple networks on same server

If I have 2 interfaces in a server on the same subnet/network does Solaris automatically choose to route packets destined for this network out the first interface. I.e if ce0 and ce1 were on same network ce0 would be chosen as it's first interface? (5 Replies)
Discussion started by: Actuator
5 Replies

4. IP Networking

solaris routing between two networks

ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2 inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255 ether 0:14:4f:55:82:9 ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3 inet 10.231.11.232 netmask... (1 Reply)
Discussion started by: busyboy
1 Replies

5. Solaris

solaris routing between two networks

ce0: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 2 inet 10.162.212.132 netmask ffffff00 broadcast 10.162.212.255 ether 0:14:4f:55:82:9 ce1: flags=1100843<UP,BROADCAST,RUNNING,MULTICAST,ROUTER,IPv4> mtu 1500 index 3 inet 10.231.11.232 netmask... (3 Replies)
Discussion started by: busyboy
3 Replies

6. What is on Your Mind?

What Social Networks Do You Use Regularly?

What Online Social Networks Do You Use Regularly? I use Facebook and LinkedIn nearly everyday.... You? If your online social network is not listed, please do a "write in" vote.. Thanks! (39 Replies)
Discussion started by: Neo
39 Replies

7. AIX

Setting up NIM for different networks

Hi, I am struggling setting up a NIM master to serve hosts on a network that is not directly accessible through the "master"-s default interface. I now that I need to set up network definitions and maybe NIM routes, but got confused. The master has 2 interfaces: * en0 holding the address... (8 Replies)
Discussion started by: trifo75
8 Replies
WI(4)							   BSD Kernel Interfaces Manual 						     WI(4)

NAME
wi -- WaveLAN/IEEE and PRISM-II 802.11 wireless network driver SYNOPSIS
wi* at pcmcia? function ? wi* at pci? dev ? function ? DESCRIPTION
The wi driver provides support for Lucent Technologies WaveLAN/IEEE PCCARD adapters (also known as WaveLAN II cards) and various PCI/MiniPCI/PCCARD adapters which use Intersil PRISM-II and PRISM-2.5 chipsets. Note that while Lucent sells both ISA and PCMCIA Wave- LAN/IEEE devices, the ISA product is actually a PCMCIA card in an ISA to PCMCIA bridge adapter. Consequently, the wi driver is required for both the ISA and PCMCIA NICs. Also note that some of the PRISM-II adapters works only at 3.3V, hence cardbus(4) support is required for those cards to set VCC correctly, even though they are 16-bit cards. The core of the WaveLAN/IEEE is the Lucent Hermes controller. All host/device interaction is via programmed I/O with the Hermes. The Hermes supports 802.11 and 802.3 frames, power management, BSS, WDS and ad-hoc operation modes. The Silver and the Gold cards of the WaveLAN/IEEE also support WEP. Unlike the other IEEE 802.11 network cards, the WaveLAN Gold cards accept 104 bits key (13 characters) for WEP encryption. The Intersil PRISM-II controller supports WEP as well. The wi driver encapsulates all traffic as 802.11 frames, however it can receive either 802.11 or 802.3 frames. Transmit speed is selectable between 1Mbps fixed, 2Mbps fixed or 2Mbps with auto fallback. For WaveLAN/IEEE Turbo adapters, speeds up to 6Mbps are available. For Wave- LAN/IEEE Turbo 11Mbps adapters and PRISM-II adapters, speeds up to 11Mbps are available. The wi driver supports configuration of Lucent cards for special ad-hoc operation. In this mode, the nwid is ignored and stations can commu- nicate among each other without the aid of an access point. Note that this mode is specific to Lucent chips, and not in the IEEE 802.11 specification. Due to changes in the implementation of this special ad-hoc mode, Lucent-based cards with different firmware revisions may not interoperate in this mode. This mode is no longer the default and must be selected using the ifconfig(8) (media option ``adhoc,flag0'') utility. Recent versions of Lucent and PRISM-II firmware support IBSS creation. IBSS is the standard IEEE 802.11 ad-hoc mode. In this mode, the nwid should be specified. At least one node must be able to create IBSS. The IBSS mode is enabled by ``adhoc'' or ``ibss'' media option. IBSS creation is automatically enabled if supported. The wi driver defaults to infrastructure mode (i.e., using an access point). Recent versions of PRISM-II firmware support operating as an 802.11 Access Point. In this mode, the Access Point station should set the nwid. This will create a standard 802.11 network, and the Access Point station will show up in an Access Point scan. This mode is enabled using the ``hostap'' media option. For more information on configuring this device, see ifconfig(8) and ifmedia(4). HARDWARE
Cards supported by the wi driver include: Alvarion BreezeNET Lucent WaveLAN/IEEE 2.0Mb Bronze Lucent WaveLAN/IEEE 2.0Mb Silver Lucent WaveLAN/IEEE Turbo Lucent WaveLAN/IEEE Turbo 11Mbps Melco AIR CONNECT WLI-PCM-L11, WLI-PCM-L11G Melco AIR CONNECT WLI-CF-S11G Compaq WL100 11Mbps Wireless Corega Wireless LAN PCC-11, PCCA_11, PCCB_11 DEC/Cabletron RoamAbout 802.11 DS High Rate D-Link DWL-520 11Mbps PCI Card, Revs. A1,A2,B1,B2 D-Link DWL-520 11Mbps PCI Card, Rev. C1 not supported, see atw(4) D-Link DWL-520 11Mbps PCI Card, Rev. D not supported, see rtw(4) D-Link DWL-650 11Mbps WLAN Card D-Link DWL-650 11Mbps WLAN Card, Rev. P not supported (Prism 3 chipset) D-Link DCF-650W CF Card ELECOM Air@Hawk LD-WL11 ELSA AirLancer MC-11 Ericsson Wireless LAN Farallon Skyline 11Mbps Wireless Intel PRO/Wireless 2011 LAN PC Card ICOM SL-1100 IO-DATA WN-B11/PCM Intersil PRISM Mini-PCI Linksys Group, Inc. Instant Wireless Network PC Card, CF Card Linksys Group, Inc. Instant Wireless Network WMP11 PCI Card Linksys Group, Inc. Instant Wireless Network WMP11v4 PCI Card not supported NCR WaveLAN/IEEE NEC Wireless Card CMZ-RT-WP, PK-WL001, PC-WL/11C PLANEX GeoWave/GW-NS110 Symbol Spectrum24 Wireless Networker PC Card, CF Card TDK LAK-CD011WL SMC EZ Connect 11M Wireless CF Card SMC2642W SMC EliteConnect Wireless Adapter PC Card SMC2531W-B Z-Com XI-626 PCI Card The original PRISM-I chipset is supported by the awi(4) driver. DIAGNOSTICS
wi%d: init failed The WaveLAN failed to come ready after an initialization command was issued. wi%d: failed to allocate %d bytes on NIC The driver was unable to allocate memory for transmit frames in the NIC's on-board RAM. wi%d: device timeout The WaveLAN failed to generate an interrupt to acknowledge a transmit command. SEE ALSO
arp(4), ifmedia(4), netintro(4), pci(4), pcmcia(4), ifconfig(8), wiconfig(8) HCF Light programming specification, http://www.wavelan.com. HISTORY
The wi device driver first appeared in NetBSD 1.5. AUTHORS
The wi driver was written by Bill Paul <wpaul@ctr.columbia.edu>. BUGS
The execution of wiconfig(8) while the interface is down can produce some error messages. BSD
July 6, 2005 BSD
All times are GMT -4. The time now is 02:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy