Need help with Xylogics Remote Annex user account

[Andy22]

2000 Series to be specific. Here's what happened. We powered down our Cisco 5513 to add two cards. When we powered back up...for some reason...we could not hit the Xylogics box. It is on the 172 network where as our LAN is on a 10 network. The other equipment that is connected to it is also on the 172 network and you can hit those individually but you can't even ping the Xylogics. All other equipment on the LAN\WAN was ok.

We think it lost the Gateway setting to communicate between the 172 and 10 networks. We don't think the Router or Switch lost any settings since we can hit the other 172 equipment. You can connect with a serial cable but herein lies the problem.We need to connect via the superuser account to verify the network settings and even if there is a gateway setting but don't know the account information (i.e. command, username and password) as this box predates most of the staff.

I know this is a only brief description of a complicated problem and your probably confused as hell but I know from past experience that the Forums of AnandTech are loaded with smart folks and if I was gonna get an answer, this was the place to start my search.

If more infromation is needed I will try and provide it.

 

[L3Guy]

It sounds to me like it is not getting its Image. Most of the Xylogic Term servers were remote boot.
The 1994 variety had a proprietary Unix daemon as its preferred boot host. It could also be booted from tftp.
if the box does not get an image, nothing else will happen.

The same daemon that ran the remote boot ran the security. However, there could be a simple password on the box.
After you log in, issue a SU command to get the Super-user prompt (root)

Its been a really long time since I touched one of these. However, if you get in, the default gateway is stored on a file called config.annex that is accessible from the command line using the edit command.

I believe that password recovery on the 2000 was by attaching to port 1, then hitting the reset button during boot up.
This put you in a rom-monitor that was fairly usable.

To disconnect, the command Ha (hang-up) will disconnect a telnet session.

If you can get me the version of code you are running, I can do the RTFM thing. Also, if you can figure out where the image is, that may help. Have you de-commissioned any Unix boxes lately?

Sorry I haven't been more help. By the way, the networking forum has a bunch of professionals that hang there.
This is OT in HT! (too easy)

Doug

 

[L3Guy]

The daemon you are looking for is erpcd. Stands for extended remote procedure call daemon. Where in my memory I pulled that one ...
erpcd ran under NT or Unix 3 years ago, Unix only before then.

Regards;

Doug

 

[ScottMac]

Bay / Nortel bought 'em. There's a slim (well, very slim) chance you can get software and/or support through Nortel.

Check out their site and/or give 'em a call.

Good Luck

Scott

 

[Andy22]

Thanks for the info guys. L3Guy...you are exactly right. If you push Test after powering on it will put you in the ROM mode which is where we should be able to connect to it and issue the necessary commands. We found out that it did lose its gateway BTW.

Thanks again for your help.

 

[L3Guy]

Happy to help.

Feel free to drop me an e-mail if you get stuck.

By the way, most of the config is not accessable from the rom monitor.
If I remember rom monitor let you set up boot related parameters and root password.
You type in admin at the SU prompt for most of the configuration.
The rest of the config was in config.annex

I played Xylogics trivia with the Level 2 network support group today.
I won!
The image was held in /user/etc/bfs/erpcd
the security was in a file called user.annex
If you need it, one of the team still has the doc's in electronic format.


Regards;

Doug