Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Access Agent Login 1

Status
Not open for further replies.

TeleLion

Technical User
Jan 4, 2006
326
US
Am trying to log into a Access Agent with user:root and password sysadm, after i log in i can not list with command ls or transfer file with MDtool disk:

Login: root
Password:

BaseSystem, Copyright (c) Ericsson Business Networks AB 1994, 1995
pSOSystem Copyright (c) Integrated Systems, Inc., 1992.
Welcome to BaseSystem...

$ ls
ls: .: Permission denied
$ cd /
$ ls
ls: .: Permission denied
$ pwd
4.0/
$
 
Login: root
Password:

BaseSystem, Copyright (c) Ericsson Business Networks AB 1994, 1995
pSOSystem Copyright (c) Integrated Systems, Inc., 1992.
Welcome to BaseSystem...

$ ls -l
ls: .: Permission denied
$
 
Login: root
Password:

BaseSystem, Copyright (c) Ericsson Business Networks AB 1994, 1995
pSOSystem Copyright (c) Integrated Systems, Inc., 1992.
Welcome to BaseSystem...

$ tncom mml
tncom: Command not found
$ ls -lg
ls: .: Permission denied
$
 
hi

type ver

chmod 775 / bin cnf log etc mib man

/gehl
 
Login: root
Password:

BaseSystem, Copyright (c) Ericsson Business Networks AB 1994, 1995
pSOSystem Copyright (c) Integrated Systems, Inc., 1992.
Welcome to BaseSystem...

$ tncom mml
tncom: Command not found
$ ver
Base System BOOT, RYS 109 004/1 R6A V1.4.8 Dec 23 1998
$ chmod 775 bin
chmod: bin: does not exist
$ ls -a
ls: .: Permission denied
$ chmod 775 cnf
chmod: cnf: does not exist
$ chmod 775 log
chmod: Command not found
$ chmod 775 etc
chmod: etc: does not exist
$ chmod mib
chmod: invalid file mode: mib
$ chmod 775 mib
chmod: mib: does not exist
$ chmod 775 man
chmod: man: does not exist
$
 
Hi,
I suspect you have an "empty system"
only the base sytem from prom is loaded,

can you try this ?

Login: root
Password:

BaseSystem, Copyright (c) Ericsson Business Networks AB 1994, 1995
pSOSystem Copyright (c) Integrated Systems, Inc., 1992.
Welcome to BaseSystem...

$ ver
Base System BOOT, RYS 109 004/1, R8A, Jul 6 2004
$ mount 4.0
mount: 4.0: volume already mounted, may be not initialized yet.
$ chmod 775 /
$ ls
BITMAP.SYS FLIST.SYS

/gehl
 
$ chmod 775 /
$ ls
BITMAP.SYS FLIST.SYS
$


Great, Thank you, Thank you, Thank you, can you please guide me through the rest of the process to get the agent to work, i alreday have the LZY 203 5250 R8A package.
 
Hi,

Just FTP the files to your AAU Like described in the readme file,
change the file attributes
edit startup file and comport.cnf

use config to set "run the soft image"
and to configure ip adresses

/gehl


 
I sent the files to teh AAU using MD tool disk, it seems the files were all named in upper case letters, am going to try to use FTP now, but thats what i used the first time and the link kept disconecting, thanks.
 
I FTP in to the AAU and then when i start transfering the file it takes for ever and after 15 minutes the link just disonnects:

ftp> put binary
binary: File not found
ftp> binary
200 Type set to I.
ftp> put bsys.img
200 PORT command successful.
150 Opening BINARY mode data connection for bsys.img.
> Netout :Connection reset by peer
Connection closed by remote host.

i tried both modes ASCII and Binary, whihc one am i spouse to be using?
 
AAU ftp stack is not really "standard"

try to use wsftppro or smartftp (disable all extra options)

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
Was able to transfer all of the files excpet for the bsys.img the FTP session times out and i lose the connection, i even used a cross cable and conected to the AAU directly with no luck, and i tried both wsftppro and smartftp, same problem, any ideas.
 
E/// FAQ :

[tt]
Make a backup copy from the (release 1) agent of all the files in the /cnf directory the startup file and any other files that you might have modified for your particular system.
Log in to the Agent and format the file system by typing the following commands:
$ umount 4.0
$ mkfs -i 4.0 FDSK <blocks> 100
Warning: this operation will destroy all data on the specified volume.
Do you want to continue (y/n)? y
where <blocks> is 2772 for the Agent Box and the Chassis Agent and 7812 for the AAUs.

Mount the new booter device on the board. Caution: The board contains ESD sensitive devices and you should use an ESD wristband connected to ground when handling the hardware.
Power up the system and log in at the console, using the default user name and password.
Change the access permissions of the root directory:
$ chmod 775 .
Use FTP to download the files from the distribution disk to the Agent.
Also download the files you backed up from the /cnf directory. However, you should always check the contents of the same files on the distribution disk to see if any changes might affect you.
Restart the system.
Log into the agent with the user name 'root'.
Check that the soft image is running by typing the "version" command (it may look something like this):
$ version
Base System, CNA 403 02 R4B V1.4.4 Jun 17 1998
Base System BOOT, RYS 109 004/1 R4B V1.4.4 Jun 17 1998
Change the file access permissions of the files. The following attribute settings are recommended:
- All directories: 775 (rwxrwxr-x).
- All executable files (bsys.img and files in /bin directory): 750 (rwxr-x---).
- Files in /etc directory: 664 (rw-rw-r--).
- Other files: 664 (rw-rw-r--).
To achieve this, the following commands must be typed at the shell (use filenames that apply to your system):

$ cd
$ chmod 664 startup readme.txt
$ cd mib
$ chmod 664 dna.mib md110.mib
$ cd ../cnf
$ chmod 664 communit.cnf comport.cnf mib2sys.cnf trapcomm.cnf ppp.cnf ppp-auth.cnf mdconfig.cnf
$ cd ../etc
$ chmod 664 passwd group route
$ cd ../man
$ chmod 664 <all files>


NOTE! mdsnmp and basesnmp can not run at the same time. Chose one of them (in startup file).

Check the file attributes and ownership according to the following example (date, time, sizes and even filenames may vary):
$ cd
$ ls -lg
total 1091
---------- 1 root root 1024 Jan 01 1980 00:00 BITMAP.SYS
---------- 1 root root 13312 Jan 01 1980 00:00 FLIST.SYS
drwxrwxr-x 1 root root 32 Jan 01 1980 02:41 bin
-rwxr-x--- 1 root root 538079 Jan 01 1980 02:38 bsys.img
drwxrwxr-x 1 root root 64 Jan 01 1980 02:36 cnf
drwxrwxr-x 1 root root 48 Jan 01 1980 03:37 etc
drwxrwxr-x 1 root root 32 Jan 01 1980 00:34 mib
-rw-rw-r-- 1 root root 2191 Jan 01 1980 02:38 readme.txt
-rw-rw-r-- 1 root root 30 Jan 01 1980 02:38 startup
$ cd ../bin
$ ls -lg
total 152
-rwxr-x--- 1 root root 66002 Jan 01 1980 02:41 basesnmp
-rwxr-x--- 1 root root 11626 Jan 01 1980 02:33 tncom

$ cd ../cnf
$ ls -lg
total 9
-rw-rw-r-- 1 root root 928 Jan 01 1980 02:36 communit.cnf
-rw-rw-r-- 1 root root 1281 Jan 01 1980 02:36 comport.cnf
-rw-rw-r-- 1 root root 635 Jan 01 1980 02:36 mib2sys.cnf
-rw-rw-r-- 1 root root 698 Jan 01 1980 02:36 trapcomm.cnf
-rw-rw-r-- 1 root root 635 Jan 01 1980 02:36 ppp.cnf
-rw-rw-r-- 1 root root 698 Jan 01 1980 02:36 ppp-auth.cnf

$ cd ../etc
$ ls -lg
total 2
-rw-rw-r-- 1 root root 27 Jan 01 1980 02:39 group
-rw-rw-r-- 1 root root 360 Jan 01 1980 02:45 passwd
-rw-rw-r-- 1 root root 1063 Jan 01 1980 02:39 route

$ cd ../mib
$ ls -lg
total 1
-rw-rw-r-- 1 root root 9083 Jan 01 1980 02:33 dna.mib


[/tt]

-----------------------------------------------------
What You See Is What You Get
Never underestimate tha powah of tha google!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top