Mailing List Archive: bringing up a new eth interface on a pci nic card. some question s

bringing up a new eth interface on a pci nic card. some question s

Oct 10, 2002, 7:50 AM

Post #1 of 3 (1956 views)

I'm trying to bring up a new interface on a pci nic card inside my F740.
Without being at the netapp is there any way to see if the nic card is
seeing a good link status. Here's what I have:

na4m-be> ifconfig -a
e0: flags=200043<UP,BROADCAST,RUNNING> mtu 1500
inet 10.209.68.211 netmask 0xffffff00 broadcast 10.209.68.255
ether 00:a0:98:00:52:76 (100tx-fd-up)
e2a: flags=200043<UP,BROADCAST,RUNNING> mtu 1500
inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47
ether 00:20:fc:1e:20:cc (auto-100tx-up)
e2b: flags=42<BROADCAST,RUNNING> mtu 1500
ether 00:20:fc:1e:20:cd (auto-unknown-cfg_down)
e2c: flags=42<BROADCAST,RUNNING> mtu 1500
ether 00:20:fc:1e:20:ce (auto-unknown-cfg_down)
e2d: flags=42<BROADCAST,RUNNING> mtu 1500
ether 00:20:fc:1e:20:cf (auto-unknown-cfg_down)
e3a: flags=42<BROADCAST,RUNNING> mtu 1500
inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47
ether 00:c0:95:e0:f4:00 (auto--down)
e3b: flags=42<BROADCAST,RUNNING> mtu 1500
ether 00:c0:95:e0:f4:01 (auto--down)
e3c: flags=42<BROADCAST,RUNNING> mtu 1500
ether 00:c0:95:e0:f4:02 (auto--down)
e3d: flags=42<BROADCAST,RUNNING> mtu 1500
ether 00:c0:95:e0:f4:03 (auto--down)
lo: flags=200049<UP,LOOPBACK,RUNNING> mtu 1536
inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1

I was at the data center the other day and when I plugged the cat5 in the
link light lit up so I'm assuming that is all set. I believe I plugged it
into the quad card in slot two, and I no for sure I plugged it into the port
labeled "1". I cannot howerver seem to ping other servers on this network,
whithin the same subnet. Is there any type of command such as snoop for
Solaris or tcpdump for linux where I can see raw network traffic?

My other question is how can I force this link to 100FDX. It's cisco gear
on the other side and I know that cisco stuff generally has trouble
auto-negotiating.

Thanks
Dan

Re: bringing up a new eth interface on a pci nic card. some questions [ In reply to ]

courier at telica

Oct 10, 2002, 8:45 AM

Post #2 of 3 (1913 views)

Permalink

Hello Dan:

I have done this two years ago and try to look back on my note and found
this:

telnet net to filer:

do ifconfig ? it will tell you how to turn on other interface and setup
duplexing too.

Also if you have mount via solaris then goto /vol/vol0/etc and add the same
command that you try

to bring interface up in rc file. This is for nextime you reboot the filer
and setting will be there for you.

Second question: about tools. I used ethereal for both Solaris and Linux,
but you need to etheir use hub to snip

or do some work on cisco so you can snip.
Ethereal for Solaris is on disktwo or Software Companion disk Pkg call"
SUNWethrs I thinks.

Hopes that help.

V-
----- Original Message -----
From: "Daniel Finn" <DFinn@studentadvantage.com>
To: <toasters@mathworks.com>
Sent: Thursday, October 10, 2002 10:50 AM
Subject: bringing up a new eth interface on a pci nic card. some questions

> I'm trying to bring up a new interface on a pci nic card inside my F740.
> Without being at the netapp is there any way to see if the nic card is
> seeing a good link status. Here's what I have:
>
> na4m-be> ifconfig -a
> e0: flags=200043<UP,BROADCAST,RUNNING> mtu 1500
> inet 10.209.68.211 netmask 0xffffff00 broadcast 10.209.68.255
> ether 00:a0:98:00:52:76 (100tx-fd-up)
> e2a: flags=200043<UP,BROADCAST,RUNNING> mtu 1500
> inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47
> ether 00:20:fc:1e:20:cc (auto-100tx-up)
> e2b: flags=42<BROADCAST,RUNNING> mtu 1500
> ether 00:20:fc:1e:20:cd (auto-unknown-cfg_down)
> e2c: flags=42<BROADCAST,RUNNING> mtu 1500
> ether 00:20:fc:1e:20:ce (auto-unknown-cfg_down)
> e2d: flags=42<BROADCAST,RUNNING> mtu 1500
> ether 00:20:fc:1e:20:cf (auto-unknown-cfg_down)
> e3a: flags=42<BROADCAST,RUNNING> mtu 1500
> inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47
> ether 00:c0:95:e0:f4:00 (auto--down)
> e3b: flags=42<BROADCAST,RUNNING> mtu 1500
> ether 00:c0:95:e0:f4:01 (auto--down)
> e3c: flags=42<BROADCAST,RUNNING> mtu 1500
> ether 00:c0:95:e0:f4:02 (auto--down)
> e3d: flags=42<BROADCAST,RUNNING> mtu 1500
> ether 00:c0:95:e0:f4:03 (auto--down)
> lo: flags=200049<UP,LOOPBACK,RUNNING> mtu 1536
> inet 127.0.0.1 netmask 0xff000000 broadcast 127.0.0.1
>
> I was at the data center the other day and when I plugged the cat5 in the
> link light lit up so I'm assuming that is all set. I believe I plugged it
> into the quad card in slot two, and I no for sure I plugged it into the
port
> labeled "1". I cannot howerver seem to ping other servers on this
network,
> whithin the same subnet. Is there any type of command such as snoop for
> Solaris or tcpdump for linux where I can see raw network traffic?
>
> My other question is how can I force this link to 100FDX. It's cisco gear
> on the other side and I know that cisco stuff generally has trouble
> auto-negotiating.
>
> Thanks
> Dan
>

Re: bringing up a new eth interface on a pci nic card. some question s [ In reply to ]

rb at telenor

Oct 10, 2002, 9:27 AM

Post #3 of 3 (1942 views)

Permalink

Daniel Finn <DFinn@studentadvantage.com> writes:

> I'm trying to bring up a new interface on a pci nic card inside my F740.
> Without being at the netapp is there any way to see if the nic card is
> seeing a good link status. Here's what I have:
>
> na4m-be> ifconfig -a
> e0: flags=200043<UP,BROADCAST,RUNNING> mtu 1500
> inet 10.209.68.211 netmask 0xffffff00 broadcast 10.209.68.255
> ether 00:a0:98:00:52:76 (100tx-fd-up)
> e2a: flags=200043<UP,BROADCAST,RUNNING> mtu 1500
> inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47
> ether 00:20:fc:1e:20:cc (auto-100tx-up)

This port has link

> e3a: flags=42<BROADCAST,RUNNING> mtu 1500
> inet 10.221.88.41 netmask 0xfffffff0 broadcast 10.221.88.47
> ether 00:c0:95:e0:f4:00 (auto--down)

This doesn't

> Is there any type of command such as snoop for
> Solaris or tcpdump for linux where I can see raw network traffic?

pktt

> My other question is how can I force this link to 100FDX. It's cisco gear
> on the other side and I know that cisco stuff generally has trouble
> auto-negotiating.

ifconfig e2a mediatype 100tx-fd

You would want to have the cisco side set to the same

>>>>>>>>>>>>.rune
--
Rune Bakken
Senior System Administrator
Telenor Business Solutions (Nextra), Communications/IP-Services
Ph: +47 22 77 03 93