Teldat Router User Manual

Page 1
Teldat Router
PCMCIA-UMTS Interface
Doc. DM757-I Rev. 10.60
March, 2007
Page 2
Chapter 1 Introduction.....................................................................................................1
1. Description.........................................................................................................................2
Chapter 2 Configuration...................................................................................................4
1. Introduction........................................................................................................................5
1.1. Adding a PCMCIA-UMTS device..........................................................................5
1.2. DIAL Connection Profile........................................................................................6
a) 3GPP-ACCESSIBILITY-CONTROL.......................................................................6
3GPP-ACCESSIBILITY-CONTROL PING...............................................7
3GPP-ACCESSIBILITY-CONTOL TRACE.............................................. 7
3GPP-ACCESSIBILITY-CONTROL TIMER............................................7
3GPP-ACCESSIIBILITY-CONTROL TRAFF IC.......................................7
b) 3GPP-BEARER-SERVICE-TYPE...........................................................................8
1.3. Adding a PPP Interface........................................................................................ 8
2. PPP Configuration..............................................................................................................9
2.1. Base Interface..........................................................................................................9
2.2. PPP Connection Profile...........................................................................................9
3. Configuring the UMTS Interface.......................................................................................11
3.1. ? (HELP).................................................................................................................11
3.2. ADDITIONAL-CONTROL-COMMAND.............................................................12
3.3. ALWAYS-ATTACHED.........................................................................................12
3.4. DISABLE................................................................................................................12
a) DISABLE FLOW-CTRL-OPTION..........................................................................12
3.5. ENABLE.................................................................................................................13
a) ENABLE FLOW-CTRL-OPTION............................................................................13
3.6. FRAME-SIZE.........................................................................................................13
3.7. NO...........................................................................................................................13
3.8. PIN..........................................................................................................................13
3.9. SPEED....................................................................................................................14
3.10. UMTS .....................................................................................................................14
a) UMTS DOMAIN......................................................................................................14
b) UMTS MODE..........................................................................................................14
3.11. WAIT-TIME...........................................................................................................14
3.12. EXIT .......................................................................................................................15
4. Configuring IP....................................................................................................................16
4.1. Events......................................................................................................................16
4.2. Saving the configuration.........................................................................................16
4.3. Checking card detection..........................................................................................16
4.4. Checking the connection.........................................................................................17
5. Configuration Templates.................................................................................................... 20
Chapter 3 Monitoring .......................................................................................................22
1. Interface Monitoring Commands.......................................................................................23
1.1. AT-MODE..............................................................................................................23
1.2. BITRATE................................................................................................................23
1.3. COMMAND...........................................................................................................24
1.4. DISCONNECT.......................................................................................................24
1.5. GPRS ......................................................................................................................24
a) GPRS ATTACH ....................................................................................................... 24
b) GPRS CELLIFO......................................................................................................25
c) GPRS DETACH ......................................................................................................25
d) GPRS IMEI .............................................................................................................25
- ii -
Page 3
e) GPRS IMSI..............................................................................................................25
f) GPRS LIST..............................................................................................................25
g) GPRS NEIGHBOUR...............................................................................................25
h) GPRS OPERATOR..................................................................................................26
i) GPRS QUALITY......................................................................................................26
j) GPRS SIM-ID..........................................................................................................26
1.6. LIST........................................................................................................................26
1.7. RESET....................................................................................................................27
1.8. EXIT .......................................................................................................................27
2. PCMCIA Monitoring Commands...................................................................................... 28
2.1. SYSTEM PCMCIA DEBUG..................................................................................28
2.2. SYSTEM PCMCIA DUMP....................................................................................29
a) SYSTEM PCMCIA DUMP CIS-CARD...................................................................29
b) SYSTEM PCMCIA DUMP CIS-REG......................................................................31
c) SYSTEM PCMCIA DUMP SOCKET-LIST .............................................................31
d) SYSTEM PCMCIA DUMP SOCKET-STATE..........................................................31
e) SYSTEM PCMCIA DUMP PCI...............................................................................32
f) SYSTEM PCMCIA DUMP SUPPORTED...............................................................32
- iii -
Page 4
Chapter 1
Introduction
Page 5
1. Description
UMTS mobile technology
UMTS technology (Universal Mobile Telecommunications System) is the terminology used in Europe when referring to Third Generation mobile services and networks.
This permits data transmission at a maximum speed of 384 Kbps, theoretically better than ISDN and standard ADSL lines. Compared with current mobile technology, this can operate eight times faster than GPRS and forty times faster than GSM.
The main advance here is the WCDMA technology (Wide Code Division Multiple Access) inherited from military technology, in contrast to GSM and GPRS which use a mixture of FDMA (Frequency Division Multiple Access) and TDMA (Time Division Multiple Access). The principal advantage of WCDMA lies in the fact that the signal expands in frequency thanks to an expansion code only known to the transmitter and the receiver.
This form of modulation has numerous advantages:
High transmission speeds, by using the whole spectrum.
High security and confidentiality, due to the use of techniques that come nearer using the
maximum channel capacity. (E.g. convolutional encoders).
Maximum multiple access effectiveness, while hop sequences do not coincide.
High interference resistance.
Main characteristics
This technology is suitable for a wide variety of users and services, not just for advanced users, UMTS offers the following:
User friendly and economic: UMTS provides easy to use and adaptable services.
New and better services: Users can demand high quality voice services from UMTS as well as
data and information services.
Fast access: The main advantage of UMTS compared to the mobile second generation (2G) is
the capability to support high data transmission speeds, up to 144 Kbps over high speed mediums, 384 Kbps in open outlying areas and 2 Mbps where there is reduced mobility (inside buildings). This capacity added to inherited support from Internet Protocol (IP), powerfully combine to provide interactive multimedia services and new broadband applications.
Data packet transmission and data transference speed on demand: UMTS offers transmission
of data in packets and over high speed switch circuits due to the virtual connectivity in the network at all times and the alternative billing methods (e.g. pay per byte, by session, flat rate, asymmetric broadband for ascending / descending link) according to the needs of the various data transmission services which are emerging.
UMTS network structure
This is made up of two large subnets: the telecommunications network and the management network. The first aims to sustain the transfer of information between connection ends. The second network’s task is to provide the means for billing and rates for the subscribers, the registration and definition of the service profiles, management and security for data handling. It also handles network elements operation with the aim of ensuring this functions correctly and for detection and resolution of breakdown and abnormalities or recuperation of operations after periods where this is off or some of the elements have disconnected.
TELDAT ROUTER– UMTS Introduction
I - 2
Doc.DM757-I
Rev.10.60
Page 6
A UMTS network is made up of the following elements:
Core Network.
The Core Network incorporates transport and intelligence functions. The first ones support traffic and signaling information transport, including switching. The routing resides in intelligence functions consisting of features such as logical and the control of certain services offered through a series of well-defined interfaces; also including mobile management. Through the Core Network, the UMTS connects to other telecommunication networks thus allowing communication with both UMTS mobile users and for users connected to other networks.
Radio access network (UTRAN).
Radio access network provides the connection between mobile terminals and the Core Network. In UMTS this is known as UTRAN (UMTS Terrestrial Radio Access Network – UTRAN) and consists of a series of radio network systems or RNC (Radio Network Controller) and a series of B Nodes dependent on this. B Nodes are network elements that correspond to the base stations.
Mobile Terminals.
UMTS specifications use the term User Equipment (UE).
TELDAT ROUTER– UMTS Introduction
I - 3
Doc.DM757-I
Rev.10.60
Page 7
Chapter 2
Configuration
Page 8
1. Introduction
UMTS interface control is carried out through a series of AT commands internally generated by the device and others which can be modified by the user.
The rest of the particular connection parameters are programmed in the dial and PPP protocol profiles. Before carrying out configuration, you need to know the data provided by the carrier to configure the
connection. The following table provides a series of data regarding Spanish carriers “anonymous” accesses as well as an example of VPN access from a fictitious carrier. Please remember that both lower and upper case letters are sensitive i.e. they must be written as given.
MOVISTAR ORANGE VODAFONE VPN APN
movistar.es internet airtelnet.es apnname.es
PDP-Type
IP IP IP IP
Login
MOVISTAR CLIENTE vodafone OPERADOR_LOGIN
Password
MOVISTAR AMENA vodafone OPERADOR_PASS
Another piece of data that we must bear in mind is that if you require a permanent connection (from device startup), idle-time = 0, or on demand with a determined release time, idle-time = x
Additionally we need to know the SIM PIN value going to be used. For those cases where the SIM is not blocked (i.e. PIN is not required), you do not need to configure it.
The steps to execute in order to completely configure the connection are as follows:
1.1. Adding a PCMCIA-UMTS device
The UMTS interface currently available in the device is based on the use of PCMCIA-UMTS cards provided by the carriers, NOVATEL MERLIN U530 for example.
These cards are installed over the PCMCIA connectors available in the device. The device therefore needs to know where the cards are going to be installed from the device
configuration menu (p 4).
add device pcmcia umts X Y:
X value indicates the SLOT where this will be installed. Y value is an index in cases where multifunction cards are supported.
set data-link at <interface>
Indicates that an AT commands interface is used over the created interface.
Example:
We have a PCMCIA interface in SLOT 2, over which we are going to insert a UMTS card. We create the umts2/0 interface and indicate that AT commands will be used over it.
Config>add device pcmcia umts 2 0 Config>set data-link at umts2/0
TELDAT ROUTER– UMTS Configuration
II - 5
Doc.DM757-I
Rev.10.60
Page 9
1.2. DIAL Connection Profile
The following values must be programmed:
remote-address:
The remote-address value is always the same (*99***1#) and is the number providing access to the UMTS network. You do not need to program this as on programming a 3gpp-apn value, the remote address is automatically generated.
3gpp-apn:
This is the UMTS node through which the connection is carried out. This value depends on the carrier.
3gpp-pdp-type:
Programs the type of Protocol Data Packet to be used in the connection. This depends on the service provided by the carrier. Normally this is the IP which coincides with the default value.
3gpp-accessibility-control:
Permits you to enable connectivity control over the profile. This also permits different accessibility controls for different profiles. This is explained in more detail further on in this manual.
3gpp-bearer-service:
Permits programs for CSD connections (i.e. connections for a number, not connections for an APN) to have a series of characteristics, allowing you to program type of norm, speed, etc., provided the inserted module supports this. This is explained in more detail further on in this manual.
idle-time:
Indicates the time period where disconnection is carried out due to absence of data. A 0 idle time value means the device will immediately execute the UMTS connection. Any
other value programs the disconnection without data period.
Example:
Config>global-profiles dial
-- DIAL PROFILE Configuration -­DIALPROF config> DIALPROF config>profile UMTS default DIALPROF config>profile UMTS dialout DIALPROF config>profile UMTS 3gpp-apn movistar.es DIALPROF config>profile UMTS 3gpp-accessibility-control traffic 6 all DIALPROF config>profile UMTS idle-time 60 DIALPROF config> DIALPROF config>exit Config>
a) 3GPP-ACCESSIBILITY-CONTROL
One of the drawbacks to UMTS connections is verifying UMTS availability. As already mentioned, the mechanism the PPP protocol has for point-to-point connection control
(Echo-request/Echo-reply) is ineffective in these connections as it is only significant at a “local” level i.e. between the router and the connected module.
Various mechanisms have been implemented to verify the connection status. These can be grouped into two types, intrusive (originating data traffic on line and therefore billable) and non-intrusive (does not originate data traffic).
Each of the described mechanisms can be independently configured over each profile configured in the interface.
TELDAT ROUTER– UMTS Configuration
II - 6
Doc.DM757-I
Rev.10.60
Page 10
Intrusive
3GPP-ACCESSIBILITY-CONTROL PING
Once the UMTS connection has been established, pings are sent every so many seconds, indicated in the command, to the configured IP address.
If this times out without having received a response from the remote, a second ping is sent and a response is expected within 10 seconds. If no response is received, two more pings are sent every 5 seconds. If no response is received, the device disconnects.
The command is:
3gpp-accessibility-control ping <A.B.C.D> <timer>
<A.B.C.D> : IP Address where the pings are sent. <timer>: Time between pings.
Example:
Dial Profiles config>profile X 3gpp-accessibility-control ping 10.10.1.1 60 Dial Profiles config>
3GPP-ACCESSIBILITY-CONTOL TRACE
Identical to the above, but this sends an ICMP trace route. The command is
3gpp-accessibility-control trace <A.B.C.D> <timer>
<A.B.C.D>: IP address where the traces are sent <timer>: Time between them.
Ejemplo:
Dial Profiles config>profile X 3gpp-accessibility-control trace 10.10.1.1 60 Dial Profiles config>
Non-Intrusive
3GPP-ACCESSIBILITY-CONTROL TIMER
Independently to the idle-time value configured in the connection profile, disconnection is carried out when the configured timer value times out.
The command is:
3gpp-accessibility-control timer <value>
<value>: Timer value between 60 and 86399 seconds.
Ejemplo:
Dial Profiles config>profile X 3gpp-accessibility-control timer 60 Dial Profiles config>
3GPP-ACCESSIIBILITY-CONTROL TRAFFIC
This consists of monitoring the data flow in both directions at the IP layer, TCP or any. The mechanism initiates from the fact that when there is outgoing traffic, there will always be
incoming. A counter for sent frames starts (depending on the type). This value resets each time there are incoming frames, independently of the type.
The command is:
3gpp-accessibility-control traffic <counter> <type>
<counter> : represents the limit for the outgoing packets (sent to the network) for the type configured without receiving incoming packets. Once this value has been reached, the link disconnection process activates in order to try a new connection.
<type>: Type of monitored outgoing traffic.
TELDAT ROUTER– UMTS Configuration
II - 7
Doc.DM757-I
Rev.10.60
Page 11
IP: All IP traffic (TCP, UDP, etc). TCP: Only considers TCP traffic for connection control. ALL: Considers all traffic including non-IP traffic.
Ejemplo:
Dial Profiles config>profile X 3gpp-accessibility-control traffic 6 IP Dial Profiles config>
b) 3GPP-BEARER-SERVICE-TYPE
The following commands appear in this profile:
Dial Profiles config> profile X 3gpp-bearer-service speed <value> Dial Profiles config> profile X 3gpp-bearer-service name <value> Dial Profiles config> profile X 3gpp-bearer-service name <value> Dial Profiles config>
These commands allow CSD calls (i.e. those for a number, not those for an APN) to take a series of characteristics.
You can for example, and if the module supports this, execute calls to ISDN destination numbers (numbers which indicate V.110 in speed), etc.
Values that appear as value are those defined by the 3GPP TS 27.007 for CSD calls norm. Not all the values are possible; this depends on the module and the network. If this is incorrectly
programmed, the module will return an error but will try and execute the call anyway. You need to be very careful when using this command.
The following command will appear before making an ATDXXXXXXXX call when the events are enabled:
AT+CBST=speed,name,ce Default is 0,0,1 --> Automode. To find out the values which permit a determined module or card, enter the commands mode, as
explained in the section on monitoring, and enter AT+CBST=?.
1.3. Adding a PPP Interface
Add a PPP interface.
Example:
Config>add device ppp 1 Added PPP interface ppp1 Config>
TELDAT ROUTER– UMTS Configuration
II - 8
Doc.DM757-I
Rev.10.60
Page 12
2. PPP Configuration
2.1. Base Interface
Configure the PPP parameters related to the base interface going to be used.
Example:
Config>global-profiles ppp
-- PPP Profiles Configuration -­PPP Profiles config PPP Profiles config> PPP Profiles config>lcp-options umts2/0 default PPP Profiles config>lcp-options umts2/0 acfc PPP Profiles config>lcp-options umts2/0 pfc PPP Profiles config>lcp-options umts2/0 accm 0 PPP Profiles config> PPP Profiles config>exit Config>
2.2. PPP Connection Profile
Here we must indicate that the PPP interface must use the UMTS interface as the base interface (“
base-interface umts2/0 link” command) and use the UMTS profile for dialing (“base-interface
umts2/0 profile UMTS” command).
Similarly, program the appropriate parameters for the protocol. The user and password sent during authentication must be appropriate for the carrier and the service
being used to connect (“
authentication sent-user XXXXXX password YYYYY” command). These are
simply examples. The IP address is normally assigned during the negotiation phase (“
ipcp local address assigned
command). Echo functionality is not required (“
lcp echo-req off” command). The PPP is only significant locally, i.e. between the router and the connected UMTS module. The echo DOES NOT detect link drops nor loss of signal.
Similarly, the extreme remote IP address that appears during negotiation is the module internal IP address, which again makes no sense to have in the routing table. This can be ignored by using the “
no ipcp peer-route” command.
Example:
Config>network ppp1
-- Generic PPP User Configuration -­ppp1 config> base-interface
-- Base Interface Configuration -­ppp1 Base IFC config> ppp1 Base IFC config>base-interface umts2/0 link ppp1 Base IFC config>base-interface umts2/0 profile UMTS ppp1 Base IFC config> ppp1 Base IFC config> ppp
-- PPP Configuration --
TELDAT ROUTER– UMTS Configuration
II - 9
Doc.DM757-I
Rev.10.60
Page 13
ppp1 PPP config> ppp1 PPP config> authentication sent-user MOVISTAR password MOVISTAR ppp1 PPP config> ipcp local address assigned ppp1 PPP config> lcp echo-req off ppp1 PPP config> no ipcp peer-route ppp1 PPP config> ppp1 PPP config>exit ppp1 config> ppp1 config>exit Config>
TELDAT ROUTER– UMTS Configuration
II - 10
Doc.DM757-I
Rev.10.60
Page 14
3. Configuring the UMTS Interface
The UMTS interface as such is an AT commands interface
There are certain commands which are common for all the device’s interfaces. These commands are described in the manual on configuring common interfaces (Dm 772-I Common Configurations for Interfaces).
The available programming commands are as follows:
Command Functions
? (HELP) Lists the available commands or their options. ADDITIONAL-CONTROL-COMMAND Configures the connectivity control. ALWAYS-ATTACHED Controls the module attach/detach to the network. DISABLE Disables functionalities. ENABLE Enables functionalities. FRAME-SIZE Configures the base interface frame size. NO Permits you to configure default values or negate a
command. PIN Programs the PIN number for the SIM module used. SPEED Programs the interface speed. UMTS Permits you to configure UMTS connection
parameters. WAIT-TIME Configures the physical connection maximum wait
time. EXIT Returns to the configuration menu.
3.1. ? (HELP)
Displays a list of the available commands or their options.
Syntax:
umts2/0 AT config>?
Example:
umts2/0 AT config>? accessibility-control Set GPRS accessibility control always-attached In PDP context disconnection not perform detach disable Disable some features enable Enable some features frame-size Set frame size no Set default config pin Set PIN number for internal Module speed Set speed umts UMTS configuration wait-time Set maximum connection time exit Return to previous menu umts2/0 AT config>
TELDAT ROUTER– UMTS Configuration
II - 11
Doc.DM757-I
Rev.10.60
Page 15
3.2. ADDITIONAL-CONTROL-COMMAND
Configures additional AT commands for the modem configuration. This admits a string of up to 59 characters. Default is no configuration. This command is sent to the module after the last initialization command.
Syntax:
umts2/0 AT config>additional-control-command ? no-command No command for this action <word> Text
Example:
umts2/0 AT config>additional-control-command i
Example:
umts2/0 AT config>additional-control-command no-command
3.3. ALWAYS-ATTACHED
The modules when internally configured usually carry out an Attach in the network. The ATTACH process is a mechanism through which the module registers in the data network and
indicates it is available. You should not confuse registering in the data network with registering in the mobile network.
Each time a disconnection for a determined context is executed, you can opt to ‘deregister’ the module from the data network (DETACH) or allow it to always remain registered. This is achieved through the ALWAYS-ATTACHED command.
Example:
umts2/0 AT config>always-attached
3.4. DISABLE
The DISABLE command permits you to disable the modem flow control. Syntax:
gprs0/0 AT config>disable <parameter>
Example:
gprs0/0 AT config>disable ? flow-ctrl-option Enable flow control gprs0/0 AT config>
a) DISABLE FLOW-CTRL-OPTION
Disables the flow control. When this parameter is disabled, there is no flow control available in the interface. By default this parameter is disabled.
Syntax:
gprs0/0 AT config>disable flow-ctrl-option
Example:
gprs0/0 AT config>disable flow-ctrl-option gprs0/0 AT config>
TELDAT ROUTER– UMTS Configuration
II - 12
Doc.DM757-I
Rev.10.60
Page 16
3.5. ENABLE
The ENABLE command permits you to enable the modem flow control. Syntax:
gprs0/0 AT config>enable <parameter>
Example:
umts2/0 AT config>enable ? flow-ctrl-option Enable flow control umts2/0 AT config>
a) ENABLE FLOW-CTRL-OPTION
Enables flow control. When this parameter is enabled, flow control is available in the interface. By default this parameter is disabled.
Syntax:
umts2/0 AT config>enable flow-ctrl-option
Example:
umts2/0 AT config>enable flow-ctrl-option umts2/0 AT config>
3.6. FRAME-SIZE
Configures the maximum base interface frame size between 576 and 4096 bytes.
Example:
umts2/0 AT config>frame-size 2048
3.7. NO
Configures the default values.
Syntax:
umts2/0 AT config>no <command>
Example:
umts2/0 AT config>no ? always-attached In PDP context disconnection perform detach frame-size pin speed umts wait-time umts2/0 AT config>
3.8. PIN
Configures the PIN number for the SIM inserted in the module.
Example:
umts2/0 AT config>pin plain 1235
TELDAT ROUTER– UMTS Configuration
II - 13
Doc.DM757-I
Rev.10.60
Page 17
Note: On listing the interface configuration, the PIN value is displayed in encrypted mode. For the above example:
Example:
umts2/0 AT config>show conf ; Showing Menu and Submenus Configuration ... ; ATLAS Router 2 8 Version 10.5.1-Alfa
pin ciphered 0xFEC7DB8210108C93
3.9. SPEED
Permits you to configure the base interface data speed.
Example:
umts2/0 AT config>speed ? <9600..460800> Value in the specified range umts2/0 AT config>speed 460800
3.10. UMTS
Permits you to configure UMTS options in the device. The options are as follows:
Command Functions
DOMAIN Selects the type of data domain to use (Data, Packets or Both). MODE Selects the network mode going to be used (GPRS, WCDMA or AUTO).
a) UMTS DOMAIN
Permits you to select the data mode to be used. The normal mode used for UMTS and supported by the carrier is PS (Packet Service).
Example:
umts2/0 AT config>umts domain ? cs Circuit switched only ps Packet switched only cs+ps CS+PS umts2/0 AT config>umts domain ps
b) UMTS MODE
Permits you to select the type of network to connect to.
Example:
umts2/0 AT config>umts mode ? automatic Automatic gprs GPRS only wcdma UMTS only umts2/0 AT config>umts mode wcdma
3.11. WAIT-TIME
Permits you to configure the maximum connection wait time when the connection is GSM.
TELDAT ROUTER– UMTS Configuration
II - 14
Doc.DM757-I
Rev.10.60
Page 18
Example:
umts2/0 AT config>wait-time ? <0..65535> Value in the specified range umts2/0 AT config>wait-time 60
3.12. EXIT
Returns to the previous menu.
Example:
umts2/0 AT config>exit Config>
TELDAT ROUTER– UMTS Configuration
II - 15
Doc.DM757-I
Rev.10.60
Page 19
4. Configuring IP
The UMTS connection assigns an IP address (public or private) to the device for each connection. Configure the IP addresses so that the default route is towards the UMTS interface.
Example:
Config>protocol ip
-- Internet protocol user configuration -­IP config> IP config>address ethernet0/0 172.24.79.12 255.255.0.0 IP config>address ppp1 unnumbered IP config> IP config> IP config>route 0.0.0.0 0.0.0.0 ppp1 1 IP config> IP config>classless IP config> IP config> IP config>exit
4.1. Events
Optional, but useful to determine problems.
Example:
Config>event
-- ELS Config -­ELS config> ELS config>enable trace subsystem PPP ALL ELS config>enable trace subsystem AT ALL ELS config>exit Config>
4.2. Saving the configuration
The configuration should be saved and the device restarted so the new configuration activates.
Example:
Config>save Save configuration [n]? y
Performing memory requirements calculations, please wait Building system configuration, please wait Configuration built, saving ... OK on Flash Config>
4.3. Checking card detection
Once the configuration has been carried out and the device restarted, you need to check that the card is operative.
PCMCIA cards can be inserted and extracted without having to restart the device when inserting (and extracting) in order to be detected and vice versa, i.e. hot-swap.
TELDAT ROUTER– UMTS Configuration
II - 16
Doc.DM757-I
Rev.10.60
Page 20
*p 2 12/28/04 11:21:16 AT.020 Module PCMCIA detected intf umts2/0 12/28/04 11:21:19 AT.020 CTS change OFF --> ON intf umts2/0 12/28/04 11:21:19 AT.020 DSR change OFF --> ON intf umts2/0 12/28/04 11:21:21 AT.020 ATCMD-->AT intf umts2/0 12/28/04 11:21:22 AT.020 ATCMD-->AT+CPIN? intf umts2/0 12/28/04 11:21:23 AT.020 Wakeup started on intf umts2/0 12/28/04 11:21:24 AT.020 Setup module on intf umts2/0 12/28/04 11:21:24 AT.020 ATCMD-->AT&F intf umts2/0 12/28/04 11:21:24 AT.020 ATCMD-->AT&C1&D2+IFC=2,2 intf umts2/0 12/28/04 11:21:24 AT.020 ATCMD-->AT+CMEE=1 intf umts2/0 12/28/04 11:21:24 AT.020 ATCMD-->AT+CGMI intf umts2/0 12/28/04 11:21:24 AT.020 ATCMD-->AT+CGMM intf umts2/0 12/28/04 11:21:24 AT.020 ATCMD-->AT+GMR intf umts2/0 12/28/04 11:21:24 AT.020 ATCMD-->AT+CGSN intf umts2/0 12/28/04 11:21:24 AT.020 ATCMD-->AT+CIMI intf umts2/0 12/28/04 11:21:24 AT.020 ATCMD-->AT$NWRAT=0,1 intf umts2/0 12/28/04 11:21:26 AT.001 Modem initialized sucessfully intf umts2/0 12/28/04 11:21:26 PPP.001 Interface ppp1 ready
4.4. Checking the connection
Execute a ping to a known IP address and monitor the events.
*ping 216.239.37.99
PING 216.239.37.99: 56 data bytes 12/28/04 11:36:46 AT.020 Dialer UMTS command CIR_OPEN local st 1 intf umts2/0 12/28/04 11:36:46 AT.020 Connection request on intf umts2/0 12/28/04 11:36:46 AT.020 ATCMD-->AT+CGDCONT=1,"IP","movistar.es" intf umts2/0 12/28/04 11:36:46 AT.020 ATCMD-->AT+CGATT=1 intf umts2/0 12/28/04 11:36:46 AT.020 Attach successful intf umts2/0 12/28/04 11:36:46 AT.020 ATCMD-->AT+CSQ intf umts2/0 12/28/04 11:36:46 *AT.020 Dialer UMTS command CIR_FLOWCONTROL local st 5 intf umts2/0 12/28/04 11:36:46 *AT.020 Dialer UMTS command CIR_CONFIG local st 5 intf umts2/0 12/28/04 11:36:46 AT.003 Received Bad CRC, fr sz 14 intf umts2/0 12/28/04 11:36:46 PPP.011 ppp1:umts2/0 In frame, type 0xc021, size 27 12/28/04 11:36:46 PPP.051 ppp1:umts2/0 LCP In CONF-REQ [req-sent] id 0 len 25 12/28/04 11:36:46 PPP.053 ppp1:umts2/0 LCP AsyncMap 0 (0x020600000000) 12/28/04 11:36:46 PPP.054 ppp1:umts2/0 LCP AuthProt CHAP (0x0305c22305) 12/28/04 11:36:46 PPP.055 ppp1:umts2/0 LCP MagicNumber 4019eaf (0x050604019eaf) 12/28/04 11:36:46 PPP.056 ppp1:umts2/0 LCP ProtComp available (0x0702) 12/28/04 11:36:46 PPP.057 ppp1:umts2/0 LCP AddrCtrlComp available (0x0802) 12/28/04 11:36:46 PPP.051 ppp1:umts2/0 LCP Out CONF-NAK [req-sent] id 0 len 10 12/28/04 11:36:46 PPP.053 ppp1:umts2/0 LCP AsyncMap a0000 (0x0206000a0000) 12/28/04 11:36:46 PPP.011 ppp1:umts2/0 In frame, type 0xc021, size 22 12/28/04 11:36:46 PPP.051 ppp1:umts2/0 LCP In CONF-ACK [req-sent] id 3 len 20 12/28/04 11:36:46 PPP.053 ppp1:umts2/0 LCP AsyncMap a0000 (0x0206000a0000) 12/28/04 11:36:46 PPP.055 ppp1:umts2/0 LCP MagicNumber 8a026850 (0x05068a026850) 12/28/04 11:36:46 PPP.056 ppp1:umts2/0 LCP ProtComp available (0x0702) 12/28/04 11:36:46 PPP.057 ppp1:umts2/0 LCP AddrCtrlComp available (0x0802) 12/28/04 11:36:46 PPP.011 ppp1:umts2/0 In frame, type 0xc021, size 27 12/28/04 11:36:46 PPP.051 ppp1:umts2/0 LCP In CONF-REQ [ack-rcvd] id 1 len 25 12/28/04 11:36:46 PPP.053 ppp1:umts2/0 LCP AsyncMap a0000 (0x0206000a0000) 12/28/04 11:36:46 PPP.054 ppp1:umts2/0 LCP AuthProt CHAP (0x0305c22305) 12/28/04 11:36:46 PPP.055 ppp1:umts2/0 LCP MagicNumber 4019eaf (0x050604019eaf) 12/28/04 11:36:46 PPP.056 ppp1:umts2/0 LCP ProtComp available (0x0702) 12/28/04 11:36:46 PPP.057 ppp1:umts2/0 LCP AddrCtrlComp available (0x0802) 12/28/04 11:36:46 PPP.051 ppp1:umts2/0 LCP Out CONF-ACK [ack-rcvd] id 1 len 25 12/28/04 11:36:46 PPP.053 ppp1:umts2/0 LCP AsyncMap a0000 (0x0206000a0000) 12/28/04 11:36:46 PPP.054 ppp1:umts2/0 LCP AuthProt CHAP (0x0305c22305) 12/28/04 11:36:46 PPP.055 ppp1:umts2/0 LCP MagicNumber 4019eaf (0x050604019eaf) 12/28/04 11:36:46 PPP.056 ppp1:umts2/0 LCP ProtComp available (0x0702) 12/28/04 11:36:46 PPP.057 ppp1:umts2/0 LCP AddrCtrlComp available (0x0802) 12/28/04 11:36:46 PPP.087 ppp1:umts2/0 LCP Negotiation successful 12/28/04 11:36:46 AT.020 Dialer UMTS command CIR_FLOWCONTROL local st 5 intf umts2/0
TELDAT ROUTER– UMTS Configuration
II - 17
Doc.DM757-I
Rev.10.60
Page 21
12/28/04 11:36:46 AT.020 Dialer UMTS command CIR_CONFIG local st 5 intf umts2/0 12/28/04 11:36:46 PPP.085 ppp1:umts2/0 CHAP required by peer 12/28/04 11:36:46 PPP.011 ppp1:umts2/0 In frame, type 0xc021, size 10 12/28/04 11:36:46 PPP.051 ppp1:umts2/0 LCP In DISC-REQ [opened] id 2 len 8 12/28/04 11:36:46 PPP.011 ppp1:umts2/0 In frame, type 0xc223, size 37 12/28/04 11:36:46 PPP.067 ppp1:umts2/0 CHAP In CHALLENGE [ack-sent] id 1 len 35 12/28/04 11:36:46 PPP.070 ppp1:umts2/0 CHAP Challenge 06c617dd5025ca43f4c9578c26fa8bd7 12/28/04 11:36:46 PPP.068 ppp1:umts2/0 CHAP Peer-Name UMTS_CHAP_SRVR 12/28/04 11:36:46 PPP.067 ppp1:umts2/0 CHAP Out RESPONSE [ack-sent] id 1 len 29 12/28/04 11:36:46 PPP.071 ppp1:umts2/0 CHAP MD5 241abe9b7cfcb0a8a5277c6c6fb678b7 12/28/04 11:36:46 PPP.068 ppp1:umts2/0 CHAP Peer-Name MOVISTAR 12/28/04 11:36:46 PPP.011 ppp1:umts2/0 In frame, type 0xc223, size 6 12/28/04 11:36:46 PPP.067 ppp1:umts2/0 CHAP In SUCCESS [ack-sent] id 1 len 4 12/28/04 11:36:46 PPP.088 ppp1 IPCP Negotiation started 12/28/04 11:36:46 PPP.072 ppp1 IPCP Out CONF-REQ [starting] id 1 len 10 12/28/04 11:36:46 PPP.073 ppp1 IPCP Address 0.0.0.0 (0x030600000000) 12/28/04 11:36:46 PPP.001 Interface ppp1 ready 12/28/04 11:36:47 PPP.011 ppp1:umts2/0 In frame, type 0x8021, size 18 12/28/04 11:36:47 PPP.072 ppp1 IPCP In CONF-NAK [req-sent] id 1 len 16 12/28/04 11:36:47 PPP.076 ppp1 IPCP Unknown option (0x81060a0b0c0d) 12/28/04 11:36:47 PPP.076 ppp1 IPCP Unknown option (0x83060a0b0c0e) 12/28/04 11:36:47 PPP.072 ppp1 IPCP Out CONF-REQ [req-sent] id 2 len 10 12/28/04 11:36:47 PPP.073 ppp1 IPCP Address 0.0.0.0 (0x030600000000) 12/28/04 11:36:48 PPP.011 ppp1:umts2/0 In frame, type 0x8021, size 18 12/28/04 11:36:48 PPP.072 ppp1 IPCP In CONF-NAK [req-sent] id 2 len 16 12/28/04 11:36:48 PPP.076 ppp1 IPCP Unknown option (0x81060a0b0c0d) 12/28/04 11:36:48 PPP.076 ppp1 IPCP Unknown option (0x83060a0b0c0e) 12/28/04 11:36:48 PPP.072 ppp1 IPCP Out CONF-REQ [req-sent] id 3 len 10 12/28/04 11:36:48 PPP.073 ppp1 IPCP Address 0.0.0.0 (0x030600000000) 12/28/04 11:36:49 PPP.011 ppp1:umts2/0 In frame, type 0x8021, size 18 12/28/04 11:36:49 PPP.072 ppp1 IPCP In CONF-NAK [req-sent] id 3 len 16 12/28/04 11:36:49 PPP.076 ppp1 IPCP Unknown option (0x81060a0b0c0d) 64 bytes from 216.239.37.99: 12/28/04 11:36:49 PPP.076 ppp1 IPCP Unknown option (0x83060a0b0c0e) 12/28/04 11:36:49 PPP.072 ppp1 IPCP Out CONF-REQ [req-sent] id 4 len 10 icmp_seq=5. 12/28/04 11:36:49 PPP.073 ppp1 IPCP Address 0.0.0.0 (0x030600000000) 12/28/04 11:36:50 PPP.011 ppp1:umts2/0 In frame, type 0x8021, size 18 12/28/04 11:36:50 PPP.072 ppp1 IPCP In CONF-NAK [req-sent] id 4 len 16 12/28/04 11:36:50 PPP.076 ppp1 IPCP Unknown option (0x81060a0b0c0d) 12/28/04 11:36:50 PPP.076 ppp1 IPCP Unknown option (0x83060a0b0c0e) 12/28/04 11:36:50 PPP.072 ppp1 IPCP Out CONF-REQ [req-sent] id 5 len 10 time=272. ms 12/28/04 11:36:50 PPP.073 ppp1 IPCP Address 0.0.0.0 (0x030600000000) 12/28/04 11:36:50 PPP.011 ppp1:umts2/0 In frame, type 0x8021, size 6 12/28/04 11:36:50 PPP.072 ppp1 IPCP In CONF-REQ [req-sent] id 3 len 4 12/28/04 11:36:50 PPP.072 ppp1 IPCP Out CONF-ACK [req-sent] id 3 len 4 12/28/04 11:36:50 PPP.011 ppp1:umts2/0 In frame, type 0x8021, size 12 12/28/04 11:36:50 PPP.072 ppp1 IPCP In CONF-NAK [ack-sent] id 5 len 10 12/28/04 11:36:50 PPP.073 ppp1 IPCP Address 80.27.13.42 (0x0306501b0d2a) 12/28/04 11:36:50 PPP.072 ppp1 IPCP Out CONF-REQ [ack-sent] id 6 len 10 12/28/04 11:36:50 PPP.073 ppp1 IPCP Address 80.27.13.42 (0x0306501b0d2a) 12/28/04 11:36:50 PPP.011 ppp1:umts2/0 In frame, type 0x8021, size 12 12/28/04 11:36:50 PPP.072 ppp1 IPCP In CONF-ACK [ack-sent] id 6 len 10 12/28/04 11:36:50 PPP.073 ppp1 IPCP Address 80.27.13.42 (0x0306501b0d2a) 12/28/04 11:36:50 PPP.088 ppp1 IPCP Negotiation successful 12/28/04 11:36:50 PPP.011 ppp1:umts2/0 Out frame, type 0x0021, size 85 12/28/04 11:36:51 PPP.012 ppp1:umts2/0 In PFC frame, 0x21 [OK] 64 bytes from 216.239.37.99: 12/28/04 11:36:51 PPP.011 ppp1:umts2/0 In frame, type 0x0021, size 85 12/28/04 11:36:51 PPP.011 ppp1:umts2/0 Out frame, type 0x0021, size 85 12/28/04 11:36:52 PPP.012 ppp1:umts2/0 In PFC frame, 0x21 [OK] 12/28/04 11:36:52 PPP.011 ppp1:umts2/0 In frame, type 0x0021, size 85 icmp_seq=6. time=292. ms 12/28/04 11:36:53 PPP.011 ppp1:umts2/0 Out frame, type 0x0021, size 85 12/28/04 11:36:53 PPP.012 ppp1:umts2/0 In PFC frame, 0x21 [OK] 64 bytes from 216.239.37.99: 12/28/04 11:36:53 PPP.011 ppp1:umts2/0 In frame, type 0x0021, size 85
TELDAT ROUTER– UMTS Configuration
II - 18
Doc.DM757-I
Rev.10.60
Page 22
icmp_seq=7. time=281. ms
----216.239.37.99 PING Statistics---­10 packets transmitted, 4 packets received, 60% packet loss round-trip (ms) min/avg/max = 733/837/944 *hide
TELDAT ROUTER– UMTS Configuration
II - 19
Doc.DM757-I
Rev.10.60
Page 23
5. Configuration Templates
A configuration example is given below to simplify configuration for the user.
log-command-errors no configuration add device ppp 1 add device pcmcia umts 2 0 set data-link at umts2/0 set data-link sync serial0/0 set data-link sync serial0/1 set data-link sync serial0/2 set hostname ATLAS-UMTS global-profiles dial ; -- Dial Profiles Configuration -­ profile UMTS default profile UMTS dialout profile UMTS 3gpp-apn movistar.es profile UMTS idle-time 300 ; exit ; global-profiles ppp ; -- PPP Profiles Configuration -­ lcp-options umts2/0 default lcp-options umts2/0 acfc lcp-options umts2/0 pfc lcp-options umts2/0 accm 0 ; exit ; network umts2/0 ; -- Interface AT. Configuration -­ pin plain 1234 always-attached exit ; network ppp1 ; -- Generic PPP User Configuration -­ ppp ; -- PPP Configuration -­ authentication sent-user MOVISTAR password MOVISTAR ipcp local address assigned no ipcp peer-route lcp echo-req off exit ; base-interface ; -- Base Interface Configuration -­ base-interface umts2/0 link base-interface umts2/0 profile UMTS ; exit ; exit ; event ; -- ELS Config -­ enable trace subsystem AT ALL enable trace subsystem PPP ALL exit ; ; protocol ip ; -- Internet protocol user configuration -­ address ethernet0/0 172.24.79.12 255.255.0.0 address ppp1 unnumbered ;
TELDAT ROUTER– UMTS Configuration
II - 20
Doc.DM757-I
Rev.10.60
Page 24
; route 0.0.0.0 0.0.0.0 ppp1 ; rule 1 default rule 1 local-ip ppp1 rule 1 napt translation ; classless ; ; exit ; feature dns ; -- DNS resolver user configuration -­ server 195.235.113.3 server 195.235.96.90 exit ; dump-command-errors end ; --- end ---
TELDAT ROUTER– UMTS Configuration
II - 21
Doc.DM757-I
Rev.10.60
Page 25
Chapter 3
Monitoring
Page 26
1. Interface Monitoring Commands
The commands added to the generic AT commands interface to control the GPRS/UMTS connection and numerated and described in this section. The result of these commands depends on the module installed in the device.
Command Function AT-MODE Sends AT commands directly to the module.
BITRATE Real time monitoring of the connection data speed. COMMAND Sends AT commands to the module. DISCONNECT Sends disconnection command. GPRS Sends predefined AT commands to the module for information. LIST Lists the current parameters for the interface. RESET Sends a Reset command to the module. EXIT Returns to the previous menu.
1.1. AT-MODE
Sends AT commands directly over the connected device.
Example:
umts2/0 AT+at-mode You are now entering AT command mode on interface umts2/0 Please type CTRL-C to exit AT command mode ati Manufacturer: Novatel Wireless Incorporated Model: Merlin U530 (HW REV E.3) Revision: 37.0-37.0 [2004-07-05 09:34:05] IMEI: 353018000013586 +GCAP: +CGSM,+ES
OK
AT command mode finished
ATLAS-UMTS *
1.2. BITRATE
Permits you to monitor the data transmission speed for the interface.
Example:
umts2/0 AT+bit
Interface umts2/0
----------------------------------------------------------------------------­ Current trx rate (bps) = 2000 Current rcv rate (bps) = 96000 Current trx rate (bps) = 12000 Current rcv rate (bps) = 0 Current trx rate (bps) = 24000 Current rcv rate (bps) = 94000 Current trx rate (bps) = 4000 Current rcv rate (bps) = 128000 Current trx rate (bps) = 4000 Current rcv rate (bps) = 166000
TELDAT ROUTER– UMTS Monitoring
III - 23
Doc.DM757-I
Rev.10.60
Page 27
Current trx rate (bps) = 8000 Current rcv rate (bps) = 336000 Current trx rate (bps) = 8000 Current rcv rate (bps) = 356000 Current trx rate (bps) = 8000 Current rcv rate (bps) = 370000 Current trx rate (bps) = 20000 Current rcv rate (bps) = 174000 umts2/0 AT+
1.3. COMMAND
Sends AT commands to the module. Sending of AT commands to the module will be available when this is not connected.
Sending of any command or waiting for the result can be aborted by pressing any key.
Example:
umts2/0 AT+command Enter comand []? ati ati ati Manufacturer: Novatel Wireless Incorporated Model: Merlin U530 (HW REV E.3) Revision: 37.0-37.0 [2004-07-05 09:34:05] IMEI: 353018000013586 +GCAP: +CGSM,+ES
OK umts2/0 AT+
1.4. DISCONNECT
Forces the disconnection of an active context.
Example:
umts2/0 AT+disconnect umts2/0 AT+
1.5. GPRS
Sends predefined AT-GPRS commands to the module. The commands are shared for the UMTS and GPRS modules. This is available when this is not connected. The results of the informative commands depend on the
module being used. Syntax:
umts2/0 AT+gprs ? ATTACH CELLINFO DETACH IMEI IMSI LIST NEIGHBOUR OPERATOR QUALITY SIM-ID
a) GPRS ATTACH
Manually carries out an ATTACH, register, to the GPRS or UMTS network.
TELDAT ROUTER– UMTS Monitoring
III - 24
Doc.DM757-I
Rev.10.60
Page 28
Note: The device, before each call, will always try and carry out an ATTACH to the network in order to verify that it is still registered.
Example:
umts2/0 AT+gprs attach AT+CGATT=1 OK
b) GPRS CELLIFO
Dumps the information stored in the module regarding the base station it is serving. Not available for UMTS.
c) GPRS DETACH
Manually carries out a DETACH, de-register, to the GPRS or UMTS network.
Example:
umts2/0 AT+gprs detach AT+CGATT=0
OK
+CGREG: 0
d) GPRS IMEI
Provides the module IMEI (International Mobile station Equipment Identity).
Example:
umts2/0 AT+gprs imei AT+CGSN 500161111199050
OK
e) GPRS IMSI
Provides the SIM IMSI (International Mobile Subscriber Identity).
Example:
umts2/0 AT+gprs imsi AT+CIMI 214031303057905
OK
f) GPRS LIST
Provides information on the radio link state, as well as the register in the network (mode and domain).
Example:
umts2/0 AT+gprs list Last Measure: 42s UMTS preferred mode: AUTO UMTS preferred domain: PS Only UMTS radio access state: WCDMA PS RSSI when connecting: 10 (-93 dBm)
g) GPRS NEIGHBOUR
Provides information on the neighbor cells that can serve the module. Not available for UMTS.
TELDAT ROUTER– UMTS Monitoring
III - 25
Doc.DM757-I
Rev.10.60
Page 29
h) GPRS OPERATOR
Provides information on the available operators. Syntax:
gprs0/0 AT+gprs operator ? AVAILABLE REGISTERED
Example:
umts2/0 AT+gprs operator available AT+COPS=? +COPS: (2,"MOVISTAR","MSTAR","21407") +COPS: (3,"E AMENA","AMENA","21403") +COPS: (1,"vodafone ES","voda ES","21401")
OK
Example:
umts2/0 AT+gprs operator registered +COPS: 0,2,"Movistar"
OK
i) GPRS QUALITY
Information on the quality of the signal received by the module.
Example:
umts2/0 AT+gprs quality +CSQ: 10,99
OK
The module returns the detected signal level with the following format +CSQ:<rssi>,<ber> <rssi> Receive level:
0 Æ-113 dBm or less 1 Æ-111 dBm
2...30 Æ -109... -53 dBm 31 Æ -51 dBm or higher 99 not detectable
<ber> Bit error rate:
0...7 according to the values described in the GSM 05.08 section 8.2.4 specification. 99 unknown (cannot be measured or has not carried out a call).
j) GPRS SIM-ID
Displays the SIM card identifier number. Not available for UMTS.
1.6. LIST
Permits you to monitor information on the interface status.
TELDAT ROUTER– UMTS Monitoring
III - 26
Doc.DM757-I
Rev.10.60
Page 30
Example:
umts2/0 AT+list GPRS Daughter Board = Unknown board Rev 0 GPRS Manufacturer = Novatel Wireless Incorporated GPRS Module Model = Merlin U530 (HW REV E.3) GPRS Module Firmware = 37.0-37.0 [2004-07-05 09:34:05] GPRS Module IMEI = 353018000013586 GPRS Module IMSI = 214072530000440 Dialers registered = UMTS Current dialer registered = none State = (1) DISCONNECT Call request = 0 Telephone number = Total connection time = 0 seconds Current connection time = 0 seconds Time to stablish connection = 0 sec umts2/0 AT+
1.7. RESET
Sends a reset command to the module.
Example:
umts2/0 AT+reset umts2/0 AT+12/28/04 12:09:49 AT.020 Module restarted intf umts2/0 12/28/04 12:09:54 PPP.002 Interface ppp1 down 12/28/04 12:09:57 AT.020 ATCMD-->AT intf umts2/0 12/28/04 12:09:58 AT.020 ATCMD-->AT+CPIN? intf umts2/0 12/28/04 12:10:00 AT.020 Setup module on intf umts2/0 12/28/04 12:10:00 AT.020 ATCMD-->AT&F intf umts2/0 12/28/04 12:10:00 AT.020 ATCMD-->AT&C1&D2+IFC=2,2 intf umts2/0 12/28/04 12:10:00 AT.020 ATCMD-->AT+CMEE=1 intf umts2/0 12/28/04 12:10:00 AT.020 ATCMD-->AT$NWRAT=0,1 intf umts2/0 12/28/04 12:10:02 AT.001 Modem initialized sucessfully intf umts2/0 12/28/04 12:10:04 PPP.001 Interface ppp1 ready
1.8. EXIT
Returns to the previous menu. Example:
umts2/0 AT+exit +
TELDAT ROUTER– UMTS Monitoring
III - 27
Doc.DM757-I
Rev.10.60
Page 31
2. PCMCIA Monitoring Commands
This section describes the commands used to monitor the PCMCIA interface state at the physical layer (controller and card).
Normally these do not provide operating information, however they can be useful when detecting problems in the PCMCIA card installation, when the card is defective for example.
Access the commands from the p3 menu by using the system pcmcia command:
*p 3 +
Command Function DEBUG Enables or disables debugging traces (p 2) over the PCMCIA controller.
DUMP Displays information from the controller and the card.
2.1. SYSTEM PCMCIA DEBUG
Enables or disables the PCMCIA events debugging traces. Enable:
+system pcmcia debug enable PCMCIA debug enabled
Disable:
+system pcmcia debug disable PCMCIA debug disabled
Example:
Traces detected in the insertion where a PCMICA UMTS card has been correctly detected, is shown below:
12/28/04 12:26:47 i82365: socket event 0x0080 12/28/04 12:26:47 i82365: socket event 0x0080 12/28/04 12:26:48 cs: setup_socket(0): applying power 12/28/04 12:26:52 cs: resetting socket 0 12/28/04 12:26:53 cs: reset end socket 0 12/28/04 12:26:56 cs: reset done on socket 0 12/28/04 12:26:56 cdrmngr: do_insert 0 12/28/04 12:26:56 Socket 0: Novatel Wireless Merlin UMTS Modem NRM6831 PC Card 12/28/04 12:26:56 Card product info: [Novatel Wireless], [Merlin UMTS Modem], [NRM6831], [] 12/28/04 12:26:56 Card manfid: 0x00a4, 0x1aaf 12/28/04 12:26:56 Card function: 2 [serial] 12/28/04 12:26:56 serial_attach() 12/28/04 12:26:56 serial_event(0x01010810): (0x000004)-> card insertion 12/28/04 12:26:56 serial_config(0x01010810) 12/28/04 12:26:56 rscmng: register base:0x3f8 num:0x8 owner:serial_cs 12/28/04 12:26:56 serial_cs: register_serial() at 0xf20003f8,irq 34 slot 2 line 0 success 12/28/04 12:26:56 serial_attach() success on 0x01010810 12/28/04 12:26:56 cdrmngr: do_insert 0 success 12/28/04 12:26:57 uart_speed at 460800 (0x6)
TELDAT ROUTER– UMTS Monitoring
III - 28
Doc.DM757-I
Rev.10.60
Page 32
2.2. SYSTEM PCMCIA DUMP
Displays information on the status of the controller and the card. The options are as follows:
Command Function CIS-CARD Displays information contained the card CIS (Card Information Structure).
CIS-REG Displays information on how the card has been configured. SOCKET-LIST Displays information on the detected PCMCIA controllers and the installed
cards.
SOCKET-STATE Displays information on how the SLOT PCMCIA controller has been
configured.
PCI Displays information on how the controller PCI registers have been
configured.
a) SYSTEM PCMCIA DUMP CIS-CARD
Displays information contained in the card CIS (Card Information Structure).
Example:
+system pcmcia dump cis-card Slot[3-1]? 2 Socket 0: validate CIS: ok 20 tuples found Tuple #1, offset 0x02, tuple_code 0x01, link_length 0x03 00 00 ff dev_info NULL 0ns, 512b Tuple #2, offset 0x07, tuple_code 0x17, link_length 0x03 00 00 ff attr_dev_info NULL 0ns, 512b Tuple #3, offset 0x0c, tuple_code 0x06, link_length 0x0b 02 00 4f 00 00 00 00 ce 00 00 00 mfc_long_link function 0: attr 0x004f function 1: attr 0x00ce Tuple #4, offset 0x19, tuple_code 0x20, link_length 0x04 a4 00 af 1a manfid 0x00a4, 0x1aaf Tuple #5, offset 0x1f, tuple_code 0x15, link_length 0x2f 06 01 4e 6f 76 61 74 65 6c 20 57 69 72 65 6c 65 73 73 00 4d 65 72 6c 69 6e 20 55 4d 54 53 20 4d 6f 64 65 6d 00 4e 52 4d 36 38 33 31 00 00 ff vers_1 6.1, "Novatel Wireless", "Merlin UMTS Modem", "NRM6831", "" Tuple #6, offset 0x51, tuple_code 0x13, link_length 0x03 43 49 53 link_target Tuple #7, offset 0x56, tuple_code 0x21, link_length 0x02 02 01 funcid serial_port [post] Tuple #8, offset 0x5a, tuple_code 0x22, link_length 0x04 00 02 0f 7f serial_interface uart 16550 [space/mark/odd/even] [5/6/7/8] [1/1.5/2] Tuple #9, offset 0x60, tuple_code 0x1a, link_length 0x06 05 05 00 04 63 02 config base 0x0400 mask 0x0263 last_index 0x05 Tuple #10, offset 0x68, tuple_code 0x1b, link_length 0x19 c7 01 99 69 55 1d f6 32 2d a3 60 f8 03 07 50 ff ff 48 c1 05 43 4f 4d 31 00 cftable_entry 0x07 [default] [audio] Vcc Vnom 5V Istatic 15mA Ipeak 850mA Idown 25mA io 0x03f8-0x03ff [lines=3] [8bit] [range]
TELDAT ROUTER– UMTS Monitoring
III - 29
Doc.DM757-I
Rev.10.60
Page 33
irq mask 0xffff [pulse] 7 bytes in subtuples Tuple #11, offset 0x83, tuple_code 0x1b, link_length 0x12 0f 98 a3 60 f8 02 07 50 ff ff 48 c1 05 43 4f 4d 32 00 cftable_entry 0x0f [audio] io 0x02f8-0x02ff [lines=3] [8bit] [range] irq mask 0xffff [pulse] 7 bytes in subtuples Tuple #12, offset 0x97, tuple_code 0x1b, link_length 0x12 17 98 a3 60 e8 03 07 50 ff ff 48 c1 05 43 4f 4d 33 00 cftable_entry 0x17 [audio] io 0x03e8-0x03ef [lines=3] [8bit] [range] irq mask 0xffff [pulse] 7 bytes in subtuples Tuple #13, offset 0xab, tuple_code 0x1b, link_length 0x12 1f 98 a3 60 e8 02 07 50 ff ff 48 c1 05 43 4f 4d 34 00 cftable_entry 0x1f [audio] io 0x02e8-0x02ef [lines=3] [8bit] [range] irq mask 0xffff [pulse] 7 bytes in subtuples Tuple #14, offset 0xbf, tuple_code 0x1b, link_length 0x0e 27 98 23 50 ff ff 48 c1 05 43 4f 4d 78 00 cftable_entry 0x27 [audio] io 0x0000-0x0007 [lines=3] [8bit] irq mask 0xffff [pulse] 7 bytes in subtuples Tuple #15, offset 0xd0, tuple_code 0x13, link_length 0x03 43 49 53 link_target Tuple #16, offset 0xd5, tuple_code 0x21, link_length 0x02 02 01 funcid serial_port [post] Tuple #17, offset 0xd9, tuple_code 0x22, link_length 0x04 00 02 0f 7f serial_interface uart 16550 [space/mark/odd/even] [5/6/7/8] [1/1.5/2] Tuple #18, offset 0xdf, tuple_code 0x1a, link_length 0x06 05 0a 20 04 63 02 config base 0x0420 mask 0x0263 last_index 0x0a Tuple #19, offset 0xe7, tuple_code 0x1b, link_length 0x19 c7 01 99 69 55 1d f6 32 2d a3 60 f8 02 07 50 ff ff 48 c1 05 43 4f 4d 36 00 cftable_entry 0x07 [default] [audio] Vcc Vnom 5V Istatic 15mA Ipeak 850mA Idown 25mA io 0x02f8-0x02ff [lines=3] [8bit] [range] irq mask 0xffff [pulse] 7 bytes in subtuples Tuple #20, offset 0x102, tuple_code 0x1b, link_length 0x12 0f 98 a3 60 f8 03 07 50 ff ff 48 c1 05 43 4f 4d 37 00 cftable_entry 0x0f [audio] io 0x03f8-0x03ff [lines=3] [8bit] [range] irq mask 0xffff [pulse] 7 bytes in subtuples Tuple #21, offset 0x116, tuple_code 0x1b, link_length 0x12 17 98 a3 60 e8 02 07 50 ff ff 48 c1 05 43 4f 4d 38 00 cftable_entry 0x17 [audio] io 0x02e8-0x02ef [lines=3] [8bit] [range] irq mask 0xffff [pulse] 7 bytes in subtuples
TELDAT ROUTER– UMTS Monitoring
III - 30
Doc.DM757-I
Rev.10.60
Page 34
Tuple #22, offset 0x12a, tuple_code 0x1b, link_length 0x12 1f 98 a3 60 e8 03 07 50 ff ff 48 c1 05 43 4f 4d 39 00 cftable_entry 0x1f [audio] io 0x03e8-0x03ef [lines=3] [8bit] [range] irq mask 0xffff [pulse] 7 bytes in subtuples Tuple #23, offset 0x13e, tuple_code 0x1b, link_length 0x0e 27 98 23 50 ff ff 48 c1 05 43 4f 4d 79 00 cftable_entry 0x27 [audio] io 0x0000-0x0007 [lines=3] [8bit] irq mask 0xffff [pulse] 7 bytes in subtuples
+
b) SYSTEM PCMCIA DUMP CIS-REG
Displays information on how the card has been configured. Example:
+system pcmcia dump cis-reg 2 Socket 0 function 0: Config register base = 0x0400, mask = 0x0263 Configuration option register [COR] = 0x47 [level_req] [func_ena] [addr_decode] [ireq_ena] [index = 00] Card configuration and status register [CCSR] = 00
IO base = 0x03f8 IO size = 7
Socket 0 function 1: Config register base = 0x0420, mask = 0x0263 read config register error ATLAS-UMTS +
c) SYSTEM PCMCIA DUMP SOCKET-LIST
Displays information on the detected PCMCIA controllers and installed cards. Example:
+sys pcmcia dump socket-list SLOT 3: CARDBUS controller type TI 1510 socket number 0 Card type detected Novatel Wireless Merlin UMTS Modem NRM6831 PC Card product info: "Novatel Wireless", "Merlin UMTS Modem", "NRM6831", "" manfid: 0x00a4, 0x1aaf function: 2 (serial)
+
d) SYSTEM PCMCIA DUMP SOCKET-STATE
Displays information on how the SLOT PCMCIA controller has been configured. Example:
+system pcmcia dump socket-state Identification and revision= *(0x00)=0x84 Chip information = *(0x1f)=0x00
PCMCIA Socket -0/A- Controller Registers
---------------------------------------------­ Interface status = *(0x01)=0x7f: [bvd1/stschg] [bvd2/spkr] [detect] [wrprot] [ready] [poweron]
TELDAT ROUTER– UMTS Monitoring
III - 31
Doc.DM757-I
Rev.10.60
Page 35
Power control = *(0x02)=0x90: [output] [resetdrv] [Vcc=5v] [Vpp off] Interrupts and control = *(0x03)=0x70: [iocard] [intr ena] [irq=0] Card status changes = *(0x04)=0x00: Card status chng int cntrl = *(0x05)=0x09: [bvd1/stschg] [detect] [irq=0] Misc control 1 = *(0x16)=0xc0: [inpack] Misc control 2 = *(0x1e)=0x00: MemMap(0) = 0x21, 240 ns, 0xf0001000-0xf0001fff, 00000 [active] [attrib] MemMap(1) = 00, 0 ns, 00000-0x01fff, 00000 MemMap(2) = 00, 0 ns, 00000-0x01fff, 00000 MemMap(3) = 00, 0 ns, 00000-0x01fff, 00000 MemMap(4) = 00, 0 ns, 00000-0x01fff, 00000 IoMap (0) = 0x09, 0 ns, 0x03f8-0x03ff [active] [0ws] IoMap (1) = 00, 0 ns, 0000-0x0001 TmrSet(0) = setup = 0, command = 0, recovery = 0 TmrSet(1) = setup = 0, command = 0, recovery = 0 ExtRegs = mask 0 = 0x7f, mask 1 = 0x90, DMA ctl = 0x70 [dreq is inpack] [pullup]
+
e) SYSTEM PCMCIA DUMP PCI
Displays information on how the controller PCI registers have been configured. Example:
+system pcmcia dump pci CARDBUS PCI Bridge Registers Socket 0
------------------------------------­Offset 0000 --> AC56104C Offset 0004 --> 02100007 Offset 0008 --> 06070000 Offset 000c --> 0002A804 Offset 0010 --> F0000000 Offset 0014 --> 020000A0 Offset 0018 --> B0222000 Offset 001c --> 00000000 Offset 0020 --> 00000000 Offset 0024 --> 00000000 Offset 0028 --> 00000000 Offset 002c --> F2000000 Offset 0030 --> F2000000 Offset 0034 --> F2000000 Offset 0038 --> F2000000 Offset 003c --> 07400102 Offset 0040 --> 00000000 Offset 0044 --> 00000001 Offset 0080 --> 0844B060 Offset 008c --> 00001022 Offset 0090 --> 606003C0 Offset 00a0 --> FE120001 Offset 00a4 --> 00C08000 Offset 00a8 --> 0000080B Offset 00ac --> 0000000F Offset 00b0 --> 08000000 +
f) SYSTEM PCMCIA DUMP SUPPORTED
This displays information on PCMCIA cards supported by the current CIT release, as well as on the drivers internally used for installation
Example:
+system pcmcia dump system pcmcia dump supported Novatel Wireless Merlin UMTS Modem NRM6831 PC Card (0) : serial Novatel Wireless Merlin UMTS Modem U630 PC Card (0) : serial Novatel Wireless Merlin HSDPA Modem U740 PC Card (0) : usb_cb
TELDAT ROUTER– UMTS Monitoring
III - 32
Doc.DM757-I
Rev.10.60
Page 36
Novatel Wireless Merlin CDMA EV-DO V620 PC Card (0) : usb_cb Olicom GoCard Combo Eth/Modem 336 PC Card (0) : serial Option Wireless 3G WCDMA CardBus (0) : usb_cb Option GlobeTrotter Fusion GPRS/WCDMA/WLAN CardBus (0) : dummy_cb (1) : usb_cb Option GlobeTrotter Fusion+ EMEA Cardbus (0) : dummy_cb (1) : dummy_cb (2) : serial_cb Option GlobeTrotter Quad GPRS/WCDMA CardBus (0) : dummy_cb (1) : usb_cb Option GlobeTrotter GT 3G (Fusion Lite) Cardbus (0) : dummy_cb (1) : usb_cb Option GlobeTrotter GT 3G+ EMEA Cardbus (0) : serial_cb Option GlobeTrotter EDGE CardBus (0) : serial Sierra Wireless AirCard7xx/8xx (0) : serial Sierra Wireless AirCard510 (0) : serial +
TELDAT ROUTER– UMTS Monitoring
III - 33
Doc.DM757-I
Rev.10.60
Loading...