Re: [CentOS] network interface question

2010-10-15 Thread Paras pradhan
Yes I just tested like this..

What i did was:

ifconfig -a gives me logical names such as: __tmp1035166962 , ethX

and ethtool -p __tmp1035166962 makes blinking in the network port.  My
problem is resolved.

Thanks a lot guys. Appreciate it.

Paras.

On Fri, Oct 15, 2010 at 12:12 PM, Bowie Bailey  wrote:
>  On 10/15/2010 1:10 PM, Bowie Bailey wrote:
>>  On 10/15/2010 12:44 PM, Paras pradhan wrote:
>>> On Fri, Oct 15, 2010 at 3:57 AM, Peter Kjellstrom  wrote:
 On Thursday 14 October 2010, Paras pradhan wrote:
 ...
> I have eight nics and its getting difficult to me which MAC id
> represents which physical port. Any way to find this?
 Have a look at the "-p" option to ethtool
>>> It would be useful (to me)  if I can use mac address instead of
>>> interface name in -p option.
>> Try this script (untested):
>>
>> 
>> #!/bin/bash
>> ETH=`ifconfig | grep -i $1 | cut -d ' ' -f 1`
>> echo "Blinking $ETH - $1"
>> ethtool -p $ETH 30
>> 
>>
>> Just call it with the mac address as an argument.  It will find the
>> interface with ifconfig and then call ethtool to blink the lights for 30
>> seconds.
>>
>> (Assuming your NIC supports ethtool.  The system I tried to test this on
>> was not supported...)
>
> oops...
>
> Make that "ifconfig -a" in the script to find inactive interfaces.
>
> --
> Bowie
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread Les Mikesell
On 10/15/2010 12:01 PM, m.r...@5-cent.us wrote:
> Paras pradhan wrote:
>> On Fri, Oct 15, 2010 at 3:57 AM, Peter Kjellstrom  wrote:
>>> On Thursday 14 October 2010, Paras pradhan wrote:
>>> ...
 I have eight nics and its getting difficult to me which MAC id
 represents which physical port. Any way to find this?
>>>
>>> Have a look at the "-p" option to ethtool
>>
>> It would be useful (to me)  if I can use mac address instead of
>> interface name in -p option.
>>
> After some thought, I think what I'd do is plug a cable into them in, one
> at a time, and use ethtool to find the one, and only one, that says "link
> detected", and you've got it.

mii-tool is a little handier for this since it will iterate over all the 
interfaces itself.  But, it will incorrectly call a 1Gb link 100baseT.

-- 
   Les Mikesell
lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread Bowie Bailey
 On 10/15/2010 1:10 PM, Bowie Bailey wrote:
>  On 10/15/2010 12:44 PM, Paras pradhan wrote:
>> On Fri, Oct 15, 2010 at 3:57 AM, Peter Kjellstrom  wrote:
>>> On Thursday 14 October 2010, Paras pradhan wrote:
>>> ...
 I have eight nics and its getting difficult to me which MAC id
 represents which physical port. Any way to find this?
>>> Have a look at the "-p" option to ethtool
>> It would be useful (to me)  if I can use mac address instead of
>> interface name in -p option.
> Try this script (untested):
>
> 
> #!/bin/bash
> ETH=`ifconfig | grep -i $1 | cut -d ' ' -f 1`
> echo "Blinking $ETH - $1"
> ethtool -p $ETH 30
> 
>
> Just call it with the mac address as an argument.  It will find the
> interface with ifconfig and then call ethtool to blink the lights for 30
> seconds.
>
> (Assuming your NIC supports ethtool.  The system I tried to test this on
> was not supported...)

oops...

Make that "ifconfig -a" in the script to find inactive interfaces.

-- 
Bowie
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread Bowie Bailey
 On 10/15/2010 12:44 PM, Paras pradhan wrote:
> On Fri, Oct 15, 2010 at 3:57 AM, Peter Kjellstrom  wrote:
>> On Thursday 14 October 2010, Paras pradhan wrote:
>> ...
>>> I have eight nics and its getting difficult to me which MAC id
>>> represents which physical port. Any way to find this?
>> Have a look at the "-p" option to ethtool
> It would be useful (to me)  if I can use mac address instead of
> interface name in -p option.

Try this script (untested):


#!/bin/bash
ETH=`ifconfig | grep -i $1 | cut -d ' ' -f 1`
echo "Blinking $ETH - $1"
ethtool -p $ETH 30


Just call it with the mac address as an argument.  It will find the
interface with ifconfig and then call ethtool to blink the lights for 30
seconds.

(Assuming your NIC supports ethtool.  The system I tried to test this on
was not supported...)

-- 
Bowie
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread Les Mikesell
On 10/15/2010 11:44 AM, Paras pradhan wrote:
> On Fri, Oct 15, 2010 at 3:57 AM, Peter Kjellstrom  wrote:
>> On Thursday 14 October 2010, Paras pradhan wrote:
>> ...
>>> I have eight nics and its getting difficult to me which MAC id
>>> represents which physical port. Any way to find this?
>>
>> Have a look at the "-p" option to ethtool
>
> It would be useful (to me)  if I can use mac address instead of
> interface name in -p option.
>

"ifconfig -a" should give you the interfaces and hwaddr values.

-- 
   Les Mikesell
 lesmikes...@gmail.com
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread m . roth
Paras pradhan wrote:
> On Fri, Oct 15, 2010 at 3:57 AM, Peter Kjellstrom  wrote:
>> On Thursday 14 October 2010, Paras pradhan wrote:
>> ...
>>> I have eight nics and its getting difficult to me which MAC id
>>> represents which physical port. Any way to find this?
>>
>> Have a look at the "-p" option to ethtool
>
> It would be useful (to me)  if I can use mac address instead of
> interface name in -p option.
>
After some thought, I think what I'd do is plug a cable into them in, one
at a time, and use ethtool to find the one, and only one, that says "link
detected", and you've got it.

mark

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread Paras pradhan
On Fri, Oct 15, 2010 at 3:48 AM, Giles Coochey  wrote:
> On 15/10/2010 10:36, John Doe wrote:
>
> From: Paras pradhan 
>
> I have eight nics and its getting difficult to me which MAC  id
> represents which physical port. Any way to find  this?
>
> Unless you are 100% sure the nics detection follow a sequential order that
> matches the nics physical ports order, I think you will have to test them
> one at
> a time...
>
> JD
>
> Not sure whether this is true for all operating systems, but in many systems
> I have come across the following ordering convention:
>


> * Onboard NIC's get listed first, e.g. eth0, eth1.
> * First PCI bus gets listsed next, starting at slot 1... e.g. eth1, eth2

Didn't happen

> * If there are multiple interfaces per card then they are ordered in
> increasing MAC address value.

Might be true but never tested. Planning to test this.

Paras.

>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread Paras pradhan
On Fri, Oct 15, 2010 at 3:57 AM, Peter Kjellstrom  wrote:
> On Thursday 14 October 2010, Paras pradhan wrote:
> ...
>> I have eight nics and its getting difficult to me which MAC id
>> represents which physical port. Any way to find this?
>
> Have a look at the "-p" option to ethtool

It would be useful (to me)  if I can use mac address instead of
interface name in -p option.

Paras.

>
> /Peter
>
>> Thanks!
>> Paras.
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread Peter Kjellstrom
On Thursday 14 October 2010, Paras pradhan wrote:
...
> I have eight nics and its getting difficult to me which MAC id
> represents which physical port. Any way to find this?

Have a look at the "-p" option to ethtool

/Peter

> Thanks!
> Paras.


signature.asc
Description: This is a digitally signed message part.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread Giles Coochey

 On 15/10/2010 10:36, John Doe wrote:

From: Paras pradhan


I have eight nics and its getting difficult to me which MAC  id
represents which physical port. Any way to find  this?

Unless you are 100% sure the nics detection follow a sequential order that
matches the nics physical ports order, I think you will have to test them one at
a time...

JD

Not sure whether this is true for all operating systems, but in many 
systems I have come across the following ordering convention:


* Onboard NIC's get listed first, e.g. eth0, eth1.
* First PCI bus gets listsed next, starting at slot 1... e.g. eth1, eth2
* If there are multiple interfaces per card then they are ordered in 
increasing MAC address value.


smime.p7s
Description: S/MIME Cryptographic Signature
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-15 Thread John Doe
From: Paras pradhan 

> I have eight nics and its getting difficult to me which MAC  id
> represents which physical port. Any way to find  this?

Unless you are 100% sure the nics detection follow a sequential order that 
matches the nics physical ports order, I think you will have to test them one 
at 
a time...

JD


  
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-14 Thread Paras pradhan
It looks like when there are no ifcfg-* files , then the kernel
assigns some default logical names ( don;t know how and why), but if
we create ifcfg-ethx files then it overrides it. That should be ok (?)
i think.

One more question:

I have eight nics and its getting difficult to me which MAC id
represents which physical port. Any way to find this?

Thanks!
Paras.


On Thu, Oct 14, 2010 at 3:53 AM, John Doe  wrote:
> From: Paras pradhan 
>
>> I don't have ifcfg-eth1 in my /etc/sysconfig/network-scripts.
>
> Maybe try to have one and put:
>  ONBOOT=no
>
> JD
>
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-14 Thread John Doe
From: Paras pradhan 

> I don't have ifcfg-eth1 in my /etc/sysconfig/network-scripts.

Maybe try to have one and put:
  ONBOOT=no

JD


  
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-13 Thread Paras pradhan
Nothing in the dmesg except this:

Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.0.2 (Aug 21, 2009)
eth0: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
133MHz found at mem e600, IRQ 16, node addr 0024e848f03d
eth1: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
133MHz found at mem e800, IRQ 17, node addr 0024e848f03f
eth2: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
133MHz found at mem ea00, IRQ 19, node addr 0026b9662f43
eth3: Broadcom NetXtreme II BCM5708 1000Base-T (B2) PCI-X 64-bit
133MHz found at mem ec00, IRQ 20, node addr 0026b9662f45


Paras.


On Wed, Oct 13, 2010 at 5:47 PM, Les Mikesell  wrote:
> On 10/13/2010 5:26 PM, Paras pradhan wrote:
>> Hi,
>>
>> I don't have ifcfg-eth1 in my /etc/sysconfig/network-scripts. But when
>> I do ifconfig eth1 I can see output as below. If I do ifconfig eth12 ,
>> I don't see anything which i am assume is normal.
>>
>>
>> eth1      Link encap:Ethernet  HWaddr 00:24:E8:44:DB:CC
>>            BROADCAST MULTICAST  MTU:1500  Metric:1
>>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>            collisions:0 txqueuelen:1000
>>            RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>            Interrupt:17 Memory:e800-e8012800
>>
>>
>> Don't know why and how this is happening.
>
> The output of 'dmesg' should show some details about the device detected
> as eth1.
>
> --
>   Les Mikesell
>    lesmikes...@gmail.com
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-13 Thread Les Mikesell
On 10/13/2010 5:26 PM, Paras pradhan wrote:
> Hi,
>
> I don't have ifcfg-eth1 in my /etc/sysconfig/network-scripts. But when
> I do ifconfig eth1 I can see output as below. If I do ifconfig eth12 ,
> I don't see anything which i am assume is normal.
>
>
> eth1  Link encap:Ethernet  HWaddr 00:24:E8:44:DB:CC
>BROADCAST MULTICAST  MTU:1500  Metric:1
>RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>collisions:0 txqueuelen:1000
>RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>Interrupt:17 Memory:e800-e8012800
>
>
> Don't know why and how this is happening.

The output of 'dmesg' should show some details about the device detected 
as eth1.

-- 
   Les Mikesell
lesmikes...@gmail.com

___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-13 Thread Paras pradhan
There are eight nics. But i don't get output of all of eth0 to eth7.

Paras.


On Wed, Oct 13, 2010 at 5:40 PM, John R Pierce  wrote:
>  On 10/13/10 3:26 PM, Paras pradhan wrote:
>> Hi,
>>
>> I don't have ifcfg-eth1 in my /etc/sysconfig/network-scripts. But when
>> I do ifconfig eth1 I can see output as below. If I do ifconfig eth12 ,
>> I don't see anything which i am assume is normal.
>>
>>
>> eth1      Link encap:Ethernet  HWaddr 00:24:E8:44:DB:CC
>>            BROADCAST MULTICAST  MTU:1500  Metric:1
>>            RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>            TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>            collisions:0 txqueuelen:1000
>>            RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>            Interrupt:17 Memory:e800-e8012800
>>
>>
>> Don't know why and how this is happening.
>
> Its unclear what your actual question is, but that behavior indicates
> that you have in fact an eth1 physical ethernet adapter but you haven't
> enabled or configured it (note there's no 'UP' or 'RUNNING' shown
> there).  you probably do not have an eth12 interface, hence why that
> gave no output.
>
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-13 Thread John R Pierce
  On 10/13/10 3:26 PM, Paras pradhan wrote:
> Hi,
>
> I don't have ifcfg-eth1 in my /etc/sysconfig/network-scripts. But when
> I do ifconfig eth1 I can see output as below. If I do ifconfig eth12 ,
> I don't see anything which i am assume is normal.
>
>
> eth1  Link encap:Ethernet  HWaddr 00:24:E8:44:DB:CC
>BROADCAST MULTICAST  MTU:1500  Metric:1
>RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>collisions:0 txqueuelen:1000
>RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>Interrupt:17 Memory:e800-e8012800
>
>
> Don't know why and how this is happening.

Its unclear what your actual question is, but that behavior indicates 
that you have in fact an eth1 physical ethernet adapter but you haven't 
enabled or configured it (note there's no 'UP' or 'RUNNING' shown 
there).  you probably do not have an eth12 interface, hence why that 
gave no output.


___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-13 Thread Paras pradhan
I have eight nics as below

[pprad...@cvprd1 ~]$ ./lshw -short -class network
WARNING: you should run this program as super-user.
H/W pathDevice   Class  Description
===
/0/100/4/0/0eth4 networkNetXtreme II BCM5708
Gigabit Ethernet
/0/100/5/0/0eth1 networkNetXtreme II BCM5708
Gigabit Ethernet
/0/100/9/0/0eth6 networkNetXtreme II BCM5708
Gigabit Ethernet
/0/100/a/0/0eth7 networkNetXtreme II BCM5708
Gigabit Ethernet
/0/100/c/0/2/0  __tmp1035166962  network82575GB Gigabit
Network Connection
/0/100/c/0/2/0.1eth5 network82575GB Gigabit
Network Connection
/0/100/c/0/4/0  __tmp619132850   network82575GB Gigabit
Network Connection
/0/100/c/0/4/0.1__tmp1445504961  network82575GB Gigabit
Network Connection


On that only eth4, eth6 and eth7 are configured ( or have ifcfg-eth4 ,
ifcfg-eth6 and ifcfg-eth7) . Wondering why there is eth1 and eth5 and
also _tmp*

Thanks!
Paras.




On Wed, Oct 13, 2010 at 5:33 PM, Jacob Bresciani  wrote:
> eth1 exists because the /dev device was found on boot (you have 2 or more
> network interfaces).
> eth12 does due to you not have 13+ nic's or did not map a network device to
> be eth12.
>
> On Wed, Oct 13, 2010 at 3:26 PM, Paras pradhan 
> wrote:
>>
>> Hi,
>>
>> I don't have ifcfg-eth1 in my /etc/sysconfig/network-scripts. But when
>> I do ifconfig eth1 I can see output as below. If I do ifconfig eth12 ,
>> I don't see anything which i am assume is normal.
>>
>>
>> eth1      Link encap:Ethernet  HWaddr 00:24:E8:44:DB:CC
>>          BROADCAST MULTICAST  MTU:1500  Metric:1
>>          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:1000
>>          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>>          Interrupt:17 Memory:e800-e8012800
>>
>>
>> Don't know why and how this is happening.
>>
>> Thanks!
>> Paras.
>> ___
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
>
>
>
> --
> Jacob Bresciani
> Linux Systems Administrator
> Advanced Ecommerce Research Systems / Terapeak
> Cell: 250 418-5412
>
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>
>
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


Re: [CentOS] network interface question

2010-10-13 Thread Jacob Bresciani
eth1 exists because the /dev device was found on boot (you have 2 or more
network interfaces).

eth12 does due to you not have 13+ nic's or did not map a network device to
be eth12.

On Wed, Oct 13, 2010 at 3:26 PM, Paras pradhan wrote:

> Hi,
>
> I don't have ifcfg-eth1 in my /etc/sysconfig/network-scripts. But when
> I do ifconfig eth1 I can see output as below. If I do ifconfig eth12 ,
> I don't see anything which i am assume is normal.
>
>
> eth1  Link encap:Ethernet  HWaddr 00:24:E8:44:DB:CC
>  BROADCAST MULTICAST  MTU:1500  Metric:1
>  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>  collisions:0 txqueuelen:1000
>  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>  Interrupt:17 Memory:e800-e8012800
>
>
> Don't know why and how this is happening.
>
> Thanks!
> Paras.
> ___
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>



-- 
Jacob Bresciani
Linux Systems Administrator
Advanced Ecommerce Research Systems / Terapeak
Cell: 250 418-5412
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


[CentOS] network interface question

2010-10-13 Thread Paras pradhan
Hi,

I don't have ifcfg-eth1 in my /etc/sysconfig/network-scripts. But when
I do ifconfig eth1 I can see output as below. If I do ifconfig eth12 ,
I don't see anything which i am assume is normal.


eth1  Link encap:Ethernet  HWaddr 00:24:E8:44:DB:CC
  BROADCAST MULTICAST  MTU:1500  Metric:1
  RX packets:0 errors:0 dropped:0 overruns:0 frame:0
  TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
  collisions:0 txqueuelen:1000
  RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
  Interrupt:17 Memory:e800-e8012800


Don't know why and how this is happening.

Thanks!
Paras.
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos