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!

Nortel NAM 4 - Cannot connect... 2

Status
Not open for further replies.

jchoponis

IS-IT--Management
Apr 28, 2007
43
US
I have a refurbished nortel applications module (NAM) v 4.1 that runs my voicemail.

I have the nortel software to interface with it via tcp/ip, but i am unable to connect. the ethernet interface does light up and have activity when plugged in.
I have been having a lot of trouble finding information about how to check the tcp/ip config on the nam - i have hooked up a monitor and keyboard to it and can tell that it runs OS/2 3.1 and that the ethernet interface is enabled in the bios.

i cannot seem to get to the command line - right after boot up, i see the c:\ prompt, but the os continues to load os2you 3.2 "limited host interface...". It says use ctrl + break to exit, but those keys do nothing....

Any ideas would be great...this older nortel stuff has been a real bear...
 
Oh - the NVM shown via F983 and option 99 is 4.1.05.
 
If it only shows 8 ports then you need to have NVM activated.....you may need to purchase a keycode for this.

4.1 came with it but I am not so sure if the upgrade to 4.1 patch came with it however somebody else or your vendor can help.

You still have an issue though if you cannot ping it.
I found some of my old notes:

To configure the TCP/IP, type
TCPCFG from the OS/2 Prompt.
2) At the main TCP/IP Configuration Screen, select the network adapter number you
have just configured in MPTS. If you added an adapter as #1 (Numbering starts at 0,
so the second card would be #1) then select LAN Interface #(card number) and
ensure the Enable Interface button is selected.
3) Enter all the information required in the IP Address, Subnet Mask, Routing and
HostNames (fully-qualified domain name) fields. . Enter the name of the NAM and its
IP address in the Host Name Configuration, as well as entries for other remote NAMs
not defined in any Domain Name Server (if any exist). Once complete, close the
TCP/IP configuration program and ensure you select to SAVE the changes if
necessary. Verify that Ultimail does not autostart.
4) Once the system is configured, attach the appropriate network cable to card and
reboot the NAM.
5) To test the TCP/IP connectivity, make a note of the TCP/IP address for the NAM you
have just configured, and from a remote station which is configured with TCP/IP run a
PING program and enter this IP address. If there is a response from the NAM, then
the configuration is valid. On the NAM, open an OS/2 window and Ping the NAM’s
own fully-qualified domain name – it should respond with its IP address. Any other
similarly-configured NAM’s on the network may be Pinged from this NAM, using their
own fully qualified domain name.

Cheers
CC

 
OK - was able to talk to an expert about this - he says I still need NAM IP Lite to connect - he says that without it, it will not connect to the network.

Where can I get this?
 
NAM IP lite was designed to do the dirty work you have done.

It ships with 4.0 NAM's or is on the Nortel Site (Dealers Only), if your vendor is authorized they can get it for you.




 
I got ahold of a floppy disk with an automated batch file to change the ip. Tried that - same result - ip is set, but no connectivity outsite the box...

After i ran the disk, the nam went back to the os2you limited user interface when "headed". the os2you log showed that ".Protocol Drive -> failed to initialize tcp/ip" was being logged 4 times per second!

I called my vendor contact again, but he still thinks that I do not know how to set an IP on the thing - I still think that the refurb was not properly set up - it seems as if there are no network card drivers and I don't know what card is in the nam. My contact would not authorize me to open the case and check the nic...

I reinstalled the monitor package and disabled the network interface.

I guess this is the end for this failed project. My hands are tied - I know that the nic is not installed right, but I can't open the nam to fix it...
 
I'm starting to think you got a NAM with the wrong hard drive installed. There are 2 different types of copper NAMs, and at least 4 different types of fiber NAMs (App Mod II, V1G, V2G V3G) The hard drives are not interchangeable between the different types of NAMs. If it's not too late try getting your NAM replaced with a later release NAM that has a built-in ethernet port with drivers already installed.

Brian Cox
 
I had a 3.0 that the IT guy at a site worked on fro months and never got it to work
 
It's a fiber NAM - and I am thinking it is too late to get it replaced - I have already configured it and have been using it for 5 months.

By the way lugerlover, that comment doesn't make me feel any better...
[neutral]



 
Even if this attempt was a failure, I am sure I will be replacing this thing in a few years...then I will know what to ask for before purchasing - this experience has taught me a great deal about the nam.

thanks to everyone who provided input and/or advice!

[thumbsup]

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top