On Wed, Mar 24, 2010 at 12:16 PM, Roman Gelfand <[email protected]> wrote:
> I thought I did disable the other nic. > I am not sure, do you mean run just plain ifconfig or are there > special parameters I should use to verify the other nic is disabled? > > Thanks again for your help > > On Wed, Mar 24, 2010 at 12:02 PM, Tony Graziano > <[email protected]> wrote: > > Wow that sucks. Do yourself a favor and disable all but one eth interface > on > > the mb. Start the system and do an ifconfig and ensure the os knows you > have > > one active ethernet. > > > > ============================ > > Tony Graziano, Manager > > Telephone: 434.984.8430 > > Fax: 434.984.8431 > > > > Email: [email protected] > > > > LAN/Telephony/Security and Control Systems Helpdesk: > > Telephone: 434.984.8426 > > Fax: 434.984.8427 > > > > Helpdesk Contract Customers: > > http://www.myitdepartment.net/gethelp/ > > > > ----- Original Message ----- > > From: [email protected] > > <[email protected]> > > To: [email protected] <[email protected]> > > Sent: Wed Mar 24 11:59:31 2010 > > Subject: [sipx-users] Lost eth0 interface on CentOS 5.4 > > > > I had a working server on CentOS 5.4. After being disconnected from > > the network for a day, the whole network configuration got screwed up. > > So, I ran sipxecs-setup-system and configured, what turned out to be > > eth0 interface. That didn't resolve the problem. The hardware is > > fine.. FYI... there are two onboard nics on this server. > > > > BTW... every time I ran sipxecs-setup-system, the login banner is > > appended. Now, I have tons of duplicate banners. > > > > Thanks > > _______________________________________________ > > sipx-users mailing list [email protected] > > List Archive: http://list.sipfoundry.org/archive/sipx-users > > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users > > sipXecs IP PBX -- http://www.sipfoundry.org/ > > > 1. Plug in your Ethernet cable. 2. Run service network status to ensure networking is running 2. Run ifconfig ifconfig simply shows what interfaces are actives, their physical (mac) address and their ip settings. What you are having is a network config issue, an OS issue, you need to understand if the OS acknoledges the Ethernet interface is there before you try to configure sipx to use it. You should also make sure it is plugged in before running the command.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
