Please help the ATM virgin

[Kegnut]

Hello all. I have a new Sun workstation running Solaris 8. I installed an ATM interface and had the network folks hook it up. They gave me all the info that I needed, so I began to configure. I am using SUNWatm 5.0 so I was configuring with atmadmin. Comparing this system to one tha is connected, alive, and well...Everything looks the same. But for some reason, I cant get out. I called Sun, and they told me to ping the IP that I assigned. I did that and it said "I" was alive, so he tells me the ATM card is configured correctly. But I can't ping anything else on the network. Sun guy tells me that its a problem with the switch, not the config. But for some reason I am having a rough time believing him. Here is the ever scrolling alarm in /var/adm/messages:

fall laner: [ID 591094 kern.notice] NOTICE: lane0: will attempt to start ELAN in 38 sec

fall atmsnmpd: [ID 702911 daemon.warning] Can not obtain local IP address -- is "fall" in "/etc/hosts"?

# Yes it is

fall laner: [ID 696921 kern.warning] WARNING: laner config request failed for lane0 (status= Insufficient Info)


Can anyone help?

Thanks,
J

 

[PAGEME1000]

Hello Mate

Can you provide more information.....What is the manufacturer of you're network....network card....what lane services have you got running where is you're lecs les bus.....etc...

Thanxs

Page

 

[Kegnut]

Thanks for the response,

It turns out, my network engineers gave me the wrong ELAN name and default router. That was smart of them wasn't it! After that I got it all hooked up. One thing I did notice is, off of a fresh install of Solaris 8 07/01, there was a hostname.eri0 in the /etc directory. This was causing some problems when the system was booted. It seemed as though it was getting conflicts between hostname.eri0 and hostname.lane0. Sometimes it would connect to network and others it wouldn't. I removed the hostname.eri0 file and all is well.

Also, I am now getting these alarms:

Oct 15 06:28:14 hostname.host.name ip: [ID 801518 kern.notice] ip_rput_dlpi (lane0) : DL_ERROR_ACK for DL_ATTACH_REQ (11), errno 8, unix 0

" " " " " " " DL_ERROR_ACK for DL_BIND_REQ(1), errno 3, unix 71
" " " " " " " DL_ERROR_ACK for DL_PHYS_ADDR_REQ(49), errno 3, unix 71
" " " " " " " DL_ERROR_ACK for DL_UNBIND_REQ(2), errno 3, unix 71
" " " " " " " DL_ERROR_ACK for DL_DETACH_REQ(12), errno 3, unix 71

I called Sun about these, and they said that these are generated because (and forgive my networking terminology) we are on a FORE backbone and we have a Sun manufactured Fiber interface card. Supposedly (LOL) there is a patch for it, and I am working with them now. All of this is just to let someone else know if they run into the same problem. Thanks for the help!

Josh

 

[Kegnut]

Forgot I had this one...I figured out those DL_ERROR_ACK errors above. This was caused by a hostname.lane0 that I thought I needed. Apparently the SunATM 5.0 software is standalone of sorts, therefore it doesn't require the hostname.lane0.

Thanks for the help,
J

 

[rockyisin]

Does anyone know how to shut down ATMSNMPD on a SunATM card with out killing the card. If I configure the startup script to (not) start the atmsnmpd the nic doesnt pass any traffic. If I add it back everything is fine. If I kill the process the same reslut- dead nic card.

Help would be appreciated

Rocky

rocoppage@hotmail.com