Sponsored Content
Full Discussion: cannot plumb nxge on T5240
Operating Systems Solaris cannot plumb nxge on T5240 Post 302283259 by incredible on Tuesday 3rd of February 2009 01:25:15 AM
Old 02-03-2009
Hi guys, i updated the system with the latest kernel patch 138138-01 and did a re-conf boot. The network ip plumbed up successfully Smilie

Boot device: /pci@400/pci@0/pci@8/scsi@0/disk@0,0:a File and args: -r
SunOS Release 5.10 Version Generic_138888-01 64-bit
Copyright 1983-2008 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
ip_arp_done: init failed
NOTICE: nxge0: xcvr addr:0x1d - link is down
Hostname: xxxxxxx
NOTICE: nxge1: xcvr addr:0x1c - link is up 1000 Mbps full duplex
NOTICE: nxge1: xcvr addr:0x1c - link is down
NOTICE: nxge0: xcvr addr:0x1d - link is up 1000 Mbps full duplex
Configuring devices.
Loading smf(5) service descriptions: 6/37



root@xxxxx # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index
1
inet 127.0.0.1 netmask ff000000
nxge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
inet 165.114.106.70 netmask ffffff00 broadcast 165.114.106.255
ether 0:21:28:26:5c:86
root@xxxxx # bash
root@xxxxx # more /etc/defaultrouter
165.114.106.1
root@xxxxx # ping 165.114.106.1
165.114.106.1 is alive
root@xxxxx # netstat -rn

Routing Table: IPv4
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ---------- ---------
default 165.114.106.1 UG 1 0
165.114.106.0 165.114.106.70 U 1 1 nxge0
224.0.0.0 165.114.106.70 U 1 0 nxge0
127.0.0.1 127.0.0.1 UH 8 520 lo0

root@xxxxx # ifconfig nxge1 plumb
root@xxxxx # Feb 3 14:12:34 sgs1fs03 nxge: NOTICE: nxge1: xcvr addr:0x1c - l
ink is down

root@xxxxx # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index
1
inet 127.0.0.1 netmask ff000000
nxge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
inet 165.114.106.70 netmask ffffff00 broadcast 165.114.106.255
ether 0:21:28:26:5c:86
nxge1: flags=201000802<BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 3
inet 0.0.0.0 netmask 0
ether 0:21:28:26:5c:87
root@xxxxx # ifconfig nxge1 192.23.23.1 netmask 255.255.255.0 broadcast + up
root@xxxxx # ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index
1
inet 127.0.0.1 netmask ff000000
nxge0: flags=201000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,CoS> mtu 1500 index 2
inet 165.114.106.70 netmask ffffff00 broadcast 165.114.106.255
ether 0:21:28:26:5c:86
nxge1: flags=201000803<UP,BROADCAST,MULTICAST,IPv4,CoS> mtu 1500 index 3
inet 192.23.23.1 netmask ffffff00 broadcast 192.23.23.255
ether 0:21:28:26:5c:87
 

10 More Discussions You Might Find Interesting

1. Solaris

Before plumb the network interface.....

I know that I could use the #ifconfig hme0 plumb to activate the network interface. However, how can I know the name of the interface e.g. hme0 before I could use the ifconfig to plumb it up? I know there is a command (but I forgot it) to use in the Sparc version when you are in the... (7 Replies)
Discussion started by: heero
7 Replies

2. Solaris

raidctl on SUN T5240

Setting up a T5240 with two disks c1t0d0 and c1t1d0. I am trying to use raidctl but when I issue. raidctl -l I get Controller 1 Disk: 0.0.0 Disk: 0.1.0 So I try raidctl -c '0.0.0 0.1.0' -r 1 1 and I get "Array in use." I try (4 Replies)
Discussion started by: photon
4 Replies

3. Solaris

SUN T5240 vs M3000

Hi, We are planning to buy new server for our data center. Sun T5240 or M3000 which one have better performance, we are going to create many dt sessions in this server. So, i need your suggestions. RJS (4 Replies)
Discussion started by: rajasekg
4 Replies

4. Solaris

ufsrestore T5240

Hi Friends we have sun T5240 server, we have taken ufsdump of this server remotely with scsi tapedrive, If we need to do ufsrestore means what we have to do, since T5240 has not having scsi port, any procedure is there? Regards Rajasekar (5 Replies)
Discussion started by: rajasekg
5 Replies

5. Solaris

nxge tuning

Hi all, I would like to tune the nxge card as suggested by this link, but got some confusion. Can anyone advise me ? We have SunOS hsbc02 5.10 Generic_137137-09 sun4v sparc SUNW,Netra-CP3260 Do I have to install any patches ? The tunning link Networks - Siwiki In our nxge.conf, I... (0 Replies)
Discussion started by: dehetoxic
0 Replies

6. Solaris

nxge interfaces too sensitive ?

Hi all, I am writing this post in order to share my experience with the SUN nxge ethernet interfaces and try to see if some of you managed to solve similar issues than the ones we experienced here with T5520 running Solaris 10. First, we noticed that it was somehow difficult to have those... (5 Replies)
Discussion started by: fpraile
5 Replies

7. Solaris

ifconfig hme0 plumb not working

Hiii folks,, I am unable to configure NIC using hme0 command. I am getting an error message as "hme0: File or directory not found.." can someone help me... Bhagi... (9 Replies)
Discussion started by: bhargav90
9 Replies

8. Solaris

ifconfig ge0 plumb

Hello Folks, can anyone please help me with this ?! :wall: I'm using Solaris 10 with Sun V880 which has two Networks Interfaces, a Fiber (ge0) and a cooper (eri0). The eri0 is working great but when I try to plumb the ge0 interface ... # ifconfig ge0 plumb ifconfig: cannot open link... (18 Replies)
Discussion started by: pxb368@motorola
18 Replies

9. Solaris

Cannot configure RAID on T5240

Hi ! I've been given a T5240 with 4 disks and 2 HBA cards (but no array connected). I did a factory reset on SP and NVRAM clean on OBP because the server had been used before. I boot cdrom in single mode and try to create a hw mirror with disks from c1... but only c2 is seen by raidctl. ... (2 Replies)
Discussion started by: delavega
2 Replies

10. Solaris

Using a Modem on a T5-2 or a T5240

Hi Folks, Just a quick question - hopefully! I have an application currently running on a V890 with Solaris 9, I'd like to move this to either one of our T-5's or one of the T5240's in a Legacy container on an LDOM - but the fly in the ointment is the application still uses a standard Hayes... (3 Replies)
Discussion started by: gull04
3 Replies
GRE(4)							   BSD Kernel Interfaces Manual 						    GRE(4)

NAME
gre -- encapsulating network device SYNOPSIS
To compile the driver into the kernel, place the following line in the kernel configuration file: device gre Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5): if_gre_load="YES" DESCRIPTION
The gre network interface pseudo device encapsulates datagrams into IP. These encapsulated datagrams are routed to a destination host, where they are decapsulated and further routed to their final destination. The ``tunnel'' appears to the inner datagrams as one hop. gre interfaces are dynamically created and destroyed with the ifconfig(8) create and destroy subcommands. This driver corresponds to RFC 2784. Encapsulated datagrams are prepended an outer datagram and a GRE header. The GRE header specifies the type of the encapsulated datagram and thus allows for tunneling other protocols than IP. GRE mode is also the default tunnel mode on Cisco routers. gre also supports Cisco WCCP protocol, both version 1 and version 2. The gre interfaces support a number of additional parameters to the ifconfig(8): grekey Set the GRE key used for outgoing packets. A value of 0 disables the key option. enable_csum Enables checksum calculation for outgoing packets. enable_seq Enables use of sequence number field in the GRE header for outgoing packets. EXAMPLES
192.168.1.* --- Router A -------tunnel-------- Router B --- 192.168.2.* / / +------ the Internet ------+ Assuming router A has the (external) IP address A and the internal address 192.168.1.1, while router B has external address B and internal address 192.168.2.1, the following commands will configure the tunnel: On router A: ifconfig greN create ifconfig greN inet 192.168.1.1 192.168.2.1 ifconfig greN inet tunnel A B route add -net 192.168.2 -netmask 255.255.255.0 192.168.2.1 On router B: ifconfig greN create ifconfig greN inet 192.168.2.1 192.168.1.1 ifconfig greN inet tunnel B A route add -net 192.168.1 -netmask 255.255.255.0 192.168.1.1 NOTES
The MTU of gre interfaces is set to 1476 by default, to match the value used by Cisco routers. This may not be an optimal value, depending on the link between the two tunnel endpoints. It can be adjusted via ifconfig(8). For correct operation, the gre device needs a route to the decapsulating host that does not run over the tunnel, as this would be a loop. The kernel must be set to forward datagrams by setting the net.inet.ip.forwarding sysctl(8) variable to non-zero. SEE ALSO
gif(4), inet(4), ip(4), me(4), netintro(4), protocols(5), ifconfig(8), sysctl(8) A description of GRE encapsulation can be found in RFC 2784 and RFC 2890. AUTHORS
Andrey V. Elsukov <ae@FreeBSD.org> Heiko W.Rupp <hwr@pilhuhn.de> BUGS
The current implementation uses the key only for outgoing packets. Incoming packets with a different key or without a key will be treated as if they would belong to this interface. The sequence number field also used only for outgoing packets. BSD
November 7, 2014 BSD
All times are GMT -4. The time now is 02:53 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy