Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Fujitsu Flashwave 4100

142 views
Skip to first unread message

Jim

unread,
Mar 12, 2004, 3:40:39 PM3/12/04
to
I am looking for anyone who may have experience with this piece of
equipment. I assigned an IP address to the NE that has made the
communications to the NE corrupt. Anytime I try to retrieve
information about the generic or SDCC or something similar, I get a
message failed. The NE is in turn-up phase and has no traffic on it. I
am wanting to crash the memory in it, but cannot recall the INIT
command for that. If someone could help, it would be appreciated.

Melon

unread,
Mar 13, 2004, 2:57:45 AM3/13/04
to

Are you sure you are actually logged into it?

act-user:(tid):root:xxx::root;
rtrv-secu-user:(tid):all:xxx;

Can you paste the exact TL1 response you are getting when you try to run
commands?

Jim

unread,
Mar 13, 2004, 8:57:25 AM3/13/04
to
Melon <nos...@screwit.lol> wrote in message news:<R9z4c.22710$m4.18745@okepread03>...

> Are you sure you are actually logged into it?
>
> act-user:(tid):root:xxx::root;
> rtrv-secu-user:(tid):all:xxx;
>
> Can you paste the exact TL1 response you are getting when you try to run
> commands?

I'm sure I have logged in all the way. The actual message I get when
trying to retrieve information is "Requested service operation failed"
Once I log in, I can even log into other NE's that have been turned up
on the ring. Everything seems to be operational, just that there is
some kind of corruption with certain information.

Melon

unread,
Mar 16, 2004, 4:06:38 PM3/16/04
to

Are you geting "Requested service operation failed" from FLEXR GT or in
the TL1 monitor window?

Jim

unread,
Mar 17, 2004, 1:15:14 AM3/17/04
to
> Are you sure you are actually logged into it?
>
> act-user:(tid):root:xxx::root;
> rtrv-secu-user:(tid):all:xxx;
>
> Can you paste the exact TL1 response you are getting when you try to run
> commands?


Thanks for your assistance. I had my problem resolved today with tech
support assistance. Ended up doing a init-sys::level=3 along with some
other things. Rebooted the system and things went back to normal.

0 new messages