Grabbing IP and zonename from multiline 'ifconfig' output
Hi There,
I have a Solaris server that has a bunch of zones configured and I am trying to write a script that will take all interfaces other than the loopback ones (e.g. lo0:3 etc) and present them so that I can easily determine the zone that owns the IP
So in the case of the following ifconfg output
I would get something like
Im a little unsure how I would get it to treat each individual block of ifconfig output as a seperate entity as clearly the virtual IP's for the zones are laid out differently by ifconfig than the non zone/main IP's (eg. nxge3) .. youll notice that the ip address line is positioned differently.
I have to capture all valid IPs in the report whether they are linked to a zone or not ..
Any advice or guidance on what would be a good starting point for me would be greatly appreciated, as im not really sure how to tackle this one
I asked a similar question earlier and got a very good answer but a new doubt came up. This is a few lines of a '/sbin/ifconfig' command on my PC:
RX packets:3781025 errors:0 dropped:0 overruns:0 frame:0
TX packets:1941909 errors:0 dropped:0 overruns:0 carrier:0
Does the RX and TX packets... (1 Reply)
I'm trying to install the recommended patch cluster on a x86 Solaris 10 box.
I get this error:
ERROR: /sbin/zonename cannot be found. install_cluster for 10_x86 patch cluster not applied. Exiting.
I tried touching the file and it gave a different error of: expected argument..
anyone... (1 Reply)
I am executing a stored proc and sending the results in a log file. I then want to grab one result from the output parameters (bolded below, 2) so that I can store it in a variable which will then be called in another script. There are more details that get printed in the beginning of the log file,... (3 Replies)
Hi -
Trying to understand a few things from an ifconfig -a output - can't seem to find info anywhere on the net.
Specifically - looking to understand the following:
Flags=8863
Smart
Running (is this the same as UP)
Simplex
inet6
supported media: autoselect - does that imply the... (1 Reply)
Hi,
I wish to format the output of a grep command in such a way that sed will be able to handle the newline characters held in the output.
Since sed does not allow newlines to be contained in a replacement pattern, that means adding a backslash '\' character to the end of each line from... (8 Replies)
Hi all,
Very new to shell scripting so appreciate some help!
There is a process count that I need to monitor, I have the AIX command that gives this value and I've cleaned it up with grep/awk so it only spits out the value I'm interested in:
echo "psc -i 10050 -s RELOAD_SERVICE" | tmadmin... (14 Replies)
I'm trying to gather information on the interfaces on a large number of servers.
If I run ifconfig I will get: eth0 Link encap:Ethernet HWaddr 00:50:56:A2:27:C1
inet addr:10.145.xxx.xxx Bcast:10.152.45.255 Mask:255.255.254.0
-----
eth1 Link... (2 Replies)
Hi,
I have created a bonding bond1 interface with 6 Eth , mode=4. Recently i have changed my old ipv6 to new one and tried to restart as well as reload network service. Post which i can see old as well as changed ipv6 in ifconfig command output. Below are few files and command output for your... (1 Reply)
Dear all,
I have below "ldapsearch" output
$ ldapsearch -D "CN=SVC-ACCOUNT,OU=SVC,OU=VDSI,OU=Non-Human,DC=Org,DC=com" -w secretword -H ldaps://org.com:636 -b DC=Org,DC=com -s sub uid=v00000 "(filter)" "displayName" "uid" "street"
# extended LDIF
#
# LDAPv3
# base <DC=Org,DC=com> with... (7 Replies)
Discussion started by: baluchen
7 Replies
LEARN ABOUT DEBIAN
natmip
NATMIP(4) BSD Kernel Interfaces Manual NATMIP(4)NAME
natmip -- IP over ATM PVCs
SYNOPSIS
device atm
options NATM
DESCRIPTION
The NATM protocol stack includes support for IP over ATM. Without any additional signalling stacks or other modules it is possible to build
a CLIP (classical IP over ATM) network based on PVCs.
An ATM network card (en0 in this example) is configured for IP by something like:
ifconfig en0 128.252.200.1 netmask 0xffffff00 up
IP routing is done with special interface routes (routes with directly reachable destinations) with a link layer gateway address. The link
layer address specifies the ATM interface through which the destination can be reached, the virtual channel that connects to the destination
and the ATM characteristics of this channel. The address part of the link layer address (see link_addr(3)) consists of a fixed part (the
first 5 bytes) and a part that depends on the kind of the PVC (UBR, CBR, VBR, ABR). Multi-byte values are big-endian encoded: the bytes with
the lower numbers contain the higher order bits.
byte 0 Is a flag byte. Currently only flag 0x20 is used. When set, all IP frames are LLC/SNAP encapsulated before putting
them into an AAL5 frame. Setting this flag is recommended and allows interoperability with other CLIP implementations.
Note that BPF works only with LLC/SNAP encapsulation.
byte 1 This is the VPI of the channel.
bytes 2...3 VCI of the channel. Must not be zero.
byte 4 Traffic type. One of 0 (UBR), 1 (CBR), 2 (ABR), 3 (VBR).
The variable part for UBR connections may be either empty or three bytes:
bytes 5...7 Specifies the peak cell rate for UBR.
The variable part for CBR connections must be three bytes:
bytes 5...7 Specifies the peak cell rate for CBR.
The variable part for VBR connections must be 9 bytes long and specifies three values:
bytes 5...7 Specifies the peak cell rate for VBR.
bytes 8...10 This is the sustainable cell rate.
bytes 11...13 The maximum burst size.
The variable part for ABR connections must be 19 bytes long and specifies the following values:
bytes 5...7 Specifies the peak cell rate for ABR.
bytes 8...10 The minimum cell rate.
bytes 11...13 The initial cell rate.
bytes 14...16 The transient buffer exposure.
byte 17 The NRM value.
byte 18 The TRM value.
bytes 19...20 The ADTF value.
byte 21 The rate increase factor (RIF).
byte 22 The rate decrease factor (RDF).
byte 23 The cutoff decrease factor (CDF).
To add a PVC the route(8) utility can be used:
route add -iface <remote IP address> -link <iface>:<lladdr>
The iface is the ATM interface through which remote IP address can be reached and lladdr is the link layer address as a string of dot-sepa-
rated, hexadecimal bytes.
NATM also supports the old, original format. This consists of 4 byte link layer addresses (and the channels are implicit UBR):
byte 0 Flags:
0x01 use AAL5.
0x02 if using AAL5, use an LLC/SNAP header.
Thus, parameter 3 means AAL5 and LLC/SNAP encapsulation (this is the required setting for interworking with other CLIP
clients). Note that BPF works only with LLC/SNAP encapsulation.
byte 1 VPI for the channel
bytes 2...3 VCI for the channel
EXAMPLES
Suppose you have 3 hosts 128.252.200.1, 128.252.200.2 and 128.252.200.3 connected by ATM through PVCs:
between 128.252.200.1 and 128.252.200.2: 0xc9 UBR
between 128.252.200.1 and 128.252.200.3: 0xca VBR
between 128.252.200.2 and 128.252.200.3: 0xcb CBR
The parameters for the VBR channel are: PCR 50000, SCR 10000, MBS 10. The peak cell rate for the CBR channel is 100000.
To enable the links use the following commands:
on host 128.252.200.1:
ifconfig en0 128.252.200.1 netmask 0xffffff00 up
route add -iface 128.252.200.2 -link en0:3.0.0.c9.0
route add -iface 128.252.200.3 -link en0:3.0.0.ca.3.0.c3.50.0.27.10.0.0.a
on host 128.252.200.2:
ifconfig en0 128.252.200.2 netmask 0xffffff00 up
route add -iface 128.252.200.1 -link en0:3.0.0.c9.0
route add -iface 128.252.200.3 -link en0:3.0.0.cb.1.1.86.a0
on host 128.252.200.3:
ifconfig en0 128.252.200.3 netmask 0xffffff00 up
route add -iface 128.252.200.1 -link en0:3.0.0.ca.3.0.c3.50.0.27.10.0.0.a
route add -iface 128.252.200.2 -link en0:3.0.0.cb.1.1.86.a0
This can also be done in rc.conf(5):
on host 128.252.200.1:
network_interfaces="lo0 en0"
ifconfig_en0="inet 128.252.200.1 netmask 255.255.255.0"
static_routes="host2 host3"
route_host2="-iface 128.252.200.2 -link en0:3.0.0.c9.0"
route_host3="-iface 128.252.200.3 -link en0:3.0.0.ca.3.0.c3.50.0.27.10.0.0.a"
on host 128.252.200.2:
network_interfaces="lo0 en0"
ifconfig_en0="inet 128.252.200.2 netmask 255.255.255.0"
static_routes="host1 host3"
route_host1="-iface 128.252.200.1 -link en0:3.0.0.c9.0"
route_host3="-iface 128.252.200.3 -link en0:3.0.0.cb.1.1.86.a0"
on host 128.252.200.3:
network_interfaces="lo0 en0"
ifconfig_en0="inet 128.252.200.3 netmask 255.255.255.0"
static_routes="host1 host2"
route_host1="-iface 128.252.200.1 -link en0:3.0.0.ca.3.0.c3.50.0.27.10.0.0.a"
route_host2="-iface 128.252.200.2 -link en0:3.0.0.cb.1.1.86.a0"
SEE ALSO en(4), fatm(4), hatm(4), natm(4), patm(4)AUTHORS
Chuck Cranor of Washington University implemented the NATM protocol layer along with the EN ATM driver in 1996 for NetBSD.
BSD August 11, 2003 BSD