• Winfiol 7.4 Serial Number
• Winfoil Download

1.1 Scope

We are using 'winfiol-md110 system' We are facing a problem when communicating or receiving international calls, the sound level is very lowوalmost can not hear anything. Please advise me to solve this issue. E WinFIOL 6.4 User's Guide. Syed Adnan Ahmad. Download Full PDF Package. A short summary of this paper. 3 Full PDFs related to this paper. E WinFIOL 6.4 User's Guide. E WinFIOL 6.4 User's Guide.

The Access Agent, without additional software, has the following facilities which are described in this document.

• Base System (BSYS) configuration and control
• Routing
• Telnet to V.24 communication (tncom)
• PPP communication
• SNMP management (Base SNMP)

Examples of additional functionality (applications) that can be added are (described in separate documents):

• SNMP Agent.
• Agent Call Account Buffer (ACAB).

1.2 Acronyms and terminology

1.3 Notation conventions

Example: ping [-s] <IP address> [<time-out>]

2.1 Hardware build-up

Main characteristics:

• Four V.24/V.28 ports for network element (in/out) and modem
• Two Ethernet ports (10BaseT and 10Base2)
• One Alarm input port with 6 inputs
• 4.5 MB flash memory (4.0/ in the file system)
• 4 MB DRAM, including 64 kB RAM disk (3.0/ in the file system)
• Token ring access (only sustaining)
• 5 V DC power supply

This model contains one agent and is designed to fit in an ASB 501 04 LIM magazine.

For more information on how to install it, see installation instructions for ACCESS AGENT.

1. Four V.24/V.28 (COM1-COM4): Used for connections to ASB 501 04, PC, terminal, modem or other V.24 compatibles. At the delivery the ports have configuration to be used for the following:
   • COM1: PPP or MML via tncom (Telnet to V.24)
   • COM2: MML via tncom (Telnet to V.24)
   • COM3: Not setup (when using network element specific software the port is used for

     SNMP communication)

   • COM4: Serial communication to PC or terminal (console) (no flow-check). May be used

     for local configuration. It can be set not to print the configuration parameters,

     thus being available for applications, e.g. tncom (Telnet to V.24).

2. Token ring connector (only in AAU1)
3. Alarm input, 1/4 connector: For connection of agent external alarms. Active alarm: +5 V (pulled up when not connected) Passive alarm: -60 V to 0 V
4. Ethernet 10BaseT (ETH): Connection to the local Ethernet 10BaseT network.
5. Ethernet 10Base2, BNC connection: Connection to the local Ethernet 10Base2 network.

All the connections in the front (except the alarm input and Ethernet 10Base2) are shielded RJ45. On the back there is a power inlet.

1. COM1-COM4: Indicates received traffic on the respective comports.
2. Reset/Config, Two-way-switch:

   Upwards: hardware reset.
   Downwards: forcing the configuration parameters to be printed to COM4 on reset, after having disabled it.

3. S: LED for future use (Only used during the boot sequence).
4. Alarm: Indicates that an alarm signal is received on one or more of the alarm pins (when the SNMP Agent is used).
5. ETH: Indicates received Ethernet (LAN) traffic (on both 10BaseT and 10Base2).
6. Power: Blinks (1 Hz) when the agent is powered and booted.

2.2 Software components

The Access Agent software (pre-installed) consists of a base system with the base application on top of it.
The Base system includes the following.

• Operating system with file system and command shell for configuration and control of the agent. Enables TCP/IP communication, FTP and Telnet servers and PPP.

Above the Base system, applications can be added. In the Access Agent, there is one application: the Base application, which includes two parts:

• tncom: Enables Telnet to V.24 connectivity. With this application, the agent can be used for connecting the ASB 501 04 to a TCP/IP network (no SNMP functionality for ASB 501 04). For example WINFIOL (terminal program for ASB 501 04 control) can be used for MML and patch downloading to external network elements.
• Base agent (Base SNMP): Enables SNMP functionality for the agent (not ASB 501 04), MIB-II support.

As mentioned before, this software can be completed with SNMP Agent application and/or ACAB.

The picture below explains how the software components are read during the booting.

At power on or reset, the Boot starts. Normally the Boot is then replaced by the Soft-image
(/bsys.img). The Soft-image is a more often upgraded copy of the Boot (the Boot is resided in the flash memory, the Soft-image on the file system).

If the Soft-image file is not found or is corrupt (or by choice is not to be loaded), no applications are loaded. The Boot, though, contains basic functionality such as support for FTP, Telnet, PPP and TCP/IP. If the Soft-image is started, all the applications listed in the /startup file are loaded. In the Access Agent, the application consists of tncom and Basesnmp. When installing network element specific software, more applications are added.

-

-

-

6.1 General

The Access Agent Unit, without additional software, has the following facilities (all thoroughly described below).

• Base System (BSYS) configuration and control: Network platform with UNIX-style shell used for configuration and control of the agent, file system operations, and so on.
• Routing. The agent is basically a simple router that can manage Ethernet, Token ring and PPP simultaneously. It provides only static routes. No routing protocols are supported.
• Telnet to V.24 communication (tncom): Application above the base system that establishes a connection in a TCP/IP network between a Telnet client and a V.24 port, via the agent. This way, the user can have a Telnet session directly to for example an ASB 501 04, without using SNMP management. This gives an opportunity to use the network element's own interface for a more detailed control, or for transferring files or other tasks.
• PPP communication which gives WAN accessibility via modem.
• SNMP management (Base SNMP): Application that enables SNMP management with the agent itself.

Examples of additional functionality (applications) that can be added are (described in separate documents):

• SNMP Agent: Enables SNMP management with ASB 501 04.
• Agent Call Account Buffer (ACAB): Enables buffering of Call Information Logging records (CIL) from ASB 501 04.

6.2 Performance and limitations

• Six Telnet sessions can be connected to the agent at a time.
• Two FTP sessions can be connected to the agent at a time.
• A routing table can contain up to 11 entries.
• Up to eight PPP units can be used.
• Eight trap destinations can be defined.
• A maximum of 10 community entries can be defined in /cnf/communit.cnf.
• A maximum of 255 users and 255 groups can be defined for the agent.
• The maximum communication speed on the comports is 38400 bit/s.
• Free flash memory space (4.0/): about 4 MB. Maximum 100 files.
• RAM: 4 MB, including a 64 kB RAM disk (3.0/) with a maximum of 25 files.

6.3 Configurations

The configurations were made at the installation, but can be changed to fit the current situation. Refer to the installation instructions for ACCESS AGENT.

The following configuration can be made:

• Network
• Routing
• Log
• tncom
• PPP
• Authentication (SNMP)
• Trap destination ( SNMP)
• MIB-II system variables (SNMP)

6.4 Security

At each log in, the agent checks if the file /etc/passwd, which contains all user and password information, is present. If it is (which should normally be the case) the agent uses that file checking for authentication of the log in. If the /etc/passwd for some reason is not present, or is corrupt, the agent has a default user name and password that can be used. At delivery the default user name and password is:

• Login: root
• Password: sysadm

Winfiol 7.4 Serial Number

This user name and password should be changed directly in the Normal network configuration mode.

The system administrator (user of the group root) can add other users (to the /etc/passwd file) using the Base system shell command adduser, see The base system shell. A system administrator can change all the users' passwords. The users can change their own passwords.

A maximum of 255 users can be defined. A user can belong to a group (stored in the /etc/group file) with the same file access rights. A maximum of 255 groups can be defined.

Different users can have different file access permission. Each file (and directory) has attributes determining the file access permission at three levels:

• the owner of the file
• the group of the owner
• others

The attributes are printed when ls -l is entered, for example:

• readme.txt rwxrwxr--

r = read
w = write
x = execute
- = the indicated permission is not granted

The leftmost three attributes are for the owner of the file, the next three are for the group of the owner, and the last three are for others.

The algorithm used when accessing a file is as follows:

1. Is the current user the owner of the file?

   Yes: check the owner file access permission.

2. If the answer is no:

   Does the user belong to the same group as the owner of the file?

   Yes: check the group file access permission.

   No: check the others file access permission.

The system administration group (root) is a special case; it is the only group that has execution rights and that can change attributes on files owned by another user.

There are Base system shell commands for handling the tasks concerning users, groups and passwords: (for more information, see the Base system shell)

• add user (adduser) (only executable for the system administration group)
• change file attributes and ownership (chmod, chown, chgrp) (only executable for the system administration group)
• change user password (passwd) (a non-system administrator can of course only change his own password)

6.5 File descriptions

6.6 The base system shell

The shell used in the base system is a UNIX-style shell used for setting up and controlling the agent. For example the shell provides commands that can modify or add files. This can be an alternative to manipulate the files in an editor and then use FTP to copy them to the agent.

The shell is a simple command interpreter. It has no wildcards (?, *, $) but it has the following notations for output redirection.

Examples:

• cat readme.txt >> myfile

Puts the contents of readme.txt last in the file myfile or, if the file does not exist, creates myfile.

• echo appl > startup

Replaces the contents of the file startup with the text appl or, if it does not exist, creates a startup file.

6.6.1 Most common commands

Only the options described here are supported by Ericsson.

Table 6-1. The most common commands

6.6.2 Other commands

These commands are mainly meant to be used for development and internal purposes. They may be changed without notice.

Table: 6-2. Other commands

6.7 tncom, transparent Telnet to V.24 communication

Application above the base system that establishes a connection in a TCP/IP network between a Telnet client and a V.24 port, via the agent. This way, the user can have a Telnet session directly to the ASB 501 04, without using SNMP management. This gives an opportunity to use the ASB 501 04's own interface for a more detailed control, or for transferring files or other tasks.

6.7.1 Initiation and configuration

For Telnet to V.24 support the files /bin/tncom and /cnf/comport.cnf have to be present on the agent's file system. /cnf/comport.cnf is a configuration file, described in installation instructions, ACCESS AGENT.

In the /startup file the line /bin/tncom has to be present to provide the Telnet to V.24 support. Normally, this is made during installation, but if it is not, add it and reset the agent.

6.7.2 Starting

1. Start a Telnet session towards the agent and log in.
2. When the prompt appears, write tncomcmd, where cmd is the name of the comport specified in the configuration file. For example:
   • tncom mml

   All the arguments of the tncom command are described in the next chapter.

3. The Telnet session will now be transparently connected to the first unused comport described as mml in /cnf/comport.cnf. With the example below it would be port COM1. If no unused comport is available or mml was not found in the file, an error message will appear.

   Example of the file /cnf/comport.cnf:

   mml COM1 9600 8 n 1 XON/XOFF

6.7.3 Syntax

The tncom command can be used with a number of arguments:

• The user can specify a logfile to which all given input from the Telnet client is logged (the input on the comport is not logged)
• If the agent does not get contact with the device, a time out specifies after how many seconds it will terminate.
• Binary mode can be used for truly bit transparent communication (including ctrl-d), for transferring files. This means that the break-sequence specified by the Telnet client, usually ctrl-], has to be used to terminate.
• The user can force an ongoing session to terminate. The user must then have the same IP address as the previous session had.
• The name of the port, as mentioned earlier, or the number of the comport (1-4).

The syntax is as follows.

tncom <cmd> € <-c comport> [-f filename] [-t timeout] [-b] [-q]

where

For example the command can look like this:

• tncom -f log.txt -t 5 mml

This specifies that all commands from the Telnet session will be stored in the logfile log.txt. The time out for the comport named mml is set to 5 seconds.

6.7.4 Downloading files with tncom

Do the following to transfer a file with tncom.
The Telnet client has to be able to transfer a file. (For example WINFIOL.)

1. Log in to the agent.
2. Start tncom.
3. Log in to ASB 501 04.
4. Prepare ASB 501 04 for receiving data.
5. Transfer the file.

6.7.5 Quitting

To close the started Telnet to V.24 session, log out from the ASB 501 04. Press ctrl-d to close the Telnet session in the agent. If binary mode is used, quit using the break-sequence specified by the Telnet client, usually ctrl-].

tncom has no inactivity time out.

6.8 Point to Point Protocol, PPP

6.8.1 Introduction

The Point-to-Point Protocol (PPP) is a data-link layer protocol that encapsulates multiple network layer packets to run over a serial connection. PPP defines a protocol for link control, various network control protocols, and authentication protocols. Additionally, the PPP communication may take place over direct (leased) lines or dial-up lines connected by modems.The PPP driver supports the following functions

• Link Control Protocol (LCP ) for PPP link establishment
• IP Control Protocol (IPCP)
• Asynchronous serial links for direct connection
• Support for operation over leased or dial-up lines connected by modems
• On-demand dialling support
• CHAP and PAP authentication support
• Multiple PPP units over the same line

6.8.2 PPP configuration

For PPP communication there are the following configuration files:

• /cnf/ppp.cnf
• /cnf/ppp-auth.cnf

They are described in installation instructions for ACCESS AGENT.

For more information on how to use PPP, see operational directions for ADVANCED HANDLING OF ACCESS AGENT.

6.9 Base SNMP, the base agent MIBs

The Base SNMP application of Access Agent provides basic SNMP management of its own SNMP agent, not any other. For SNMP support for ASB 501 04, the SNMP Agent should be used.

The MIB (Management Information Base) is the formal definition as to which data can be retrieved using SNMP commands. Before they can be accessed the management station needs to integrate (compile) the MIB into its data base. The following MIBs are supported by the Base agent SNMP configuration.

• The standard MIB II as defined by RFC 1213.
• The D.N.A. MIB, the common MIB definition for D.N.A. network elements.

The D.N.A. MIB (filename /mib/dna.mib) defined in ASN.1 format is stored on the agent. It can then be accessed and downloaded from an SNMP manager.

Before any SNMP management can be used, the following configurations have to be made.

• Authentication: Define allowed users.
• Trap destination: Define where to send trap messages.
• MIB-II system variables: Part of MIB-II, defining the basic identification data for the agent.

They are described in installation instructions for ACCESS AGENT.

Winfoil Download

6.9.1 MIB-II

The agent supports MIB II as defined in RFC 1213 extended with the ifName variable from the ifXTable in RFC 1573.

6.9.2 The D.N.A. MIB

The Ericsson position within the global registration tree is:
iso(1).org(3).dod(6).internet(1).private(4).enterprise(1).ericsson(193)

The D.N.A. MIB structure within the Ericsson tree is:

Before terminating, always key the command netstat to check that no one else is connected to the agent.