02-04-2013
Determining how long device has been in defined state
All,
Hoping you can help. I'm wondering how I can determine how long a device (network interface) has been in a defined state. Know there's a way, just can't figure it out.
Thanks in advance!
5 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
Occasionally I am getting the port state in CLOSE_WAIT for long time in the solaris server. I am not sure is it application problem or not. Because we are using port 9009 for Tomcat process in our web application, some time when I start the application, the port 9009 is in CLOSE_WAIT... (0 Replies)
Discussion started by: mgmk.84
0 Replies
2. AIX
Hi,
I would like to know wheather it is possible to make device in availabe state?
if for same reason os is not able to make it in available state. and it is in define state. (2 Replies)
Discussion started by: manoj.solaris
2 Replies
3. Red Hat
Hi All,
Could anyone please help to resolve the below problem.
I installed RHEL5.5 in my desktop.But when i try to activate the ethernet connection then it gives me the error.
I spent 2 days for the above and go through with several suggestion found by googling. But no luck.
... (0 Replies)
Discussion started by: Tanmoy
0 Replies
4. AIX
Hi Admins,
I am having a whole system lpar in open firmware state on HMC.
How can I bring it to running state ?
Let me know. Thanks. (2 Replies)
Discussion started by: snchaudhari2
2 Replies
5. HP-UX
Hi,
Unable to make tape backup, please help.
/opt/ignite/bin/make_tape_recovery -a /dev/rmt/?mn -I -v -m tar -x inc_entire=vg00
* Creating local directories for configuration files and archive.
======= 04/25/16 16:28:08 IST Started /opt/ignite/bin/make_tape_recovery.
(Mon... (4 Replies)
Discussion started by: anuragr
4 Replies
veth(4) Linux Programmer's Manual veth(4)
NAME
veth - Virtual Ethernet Device
DESCRIPTION
The veth devices are virtual Ethernet devices. They can act as tunnels between network namespaces to create a bridge to a physical network
device in another namespace, but can also be used as standalone network devices.
veth devices are always created in interconnected pairs. A pair can be created using the command:
# ip link add <p1-name> type veth peer name <p2-name>
In the above, p1-name and p2-name are the names assigned to the two connected end points.
Packets transmitted on one device in the pair are immediately received on the other device. When either devices is down the link state of
the pair is down.
veth device pairs are useful for combining the network facilities of the kernel together in interesting ways. A particularly interesting
use case is to place one end of a veth pair in one network namespace and the other end in another network namespace, thus allowing communi-
cation between network namespaces. To do this, one first creates the veth device as above and then moves one side of the pair to the other
namespace:
# ip link set <p2-name> netns <p2-namespace>
ethtool(8) can be used to find the peer of a veth network interface, using commands something like:
# ip link add ve_A type veth peer name ve_B # Create veth pair
# ethtool -S ve_A # Discover interface index of peer
NIC statistics:
peer_ifindex: 16
# ip link | grep '^16:' # Look up interface
16: ve_B@ve_A: <BROADCAST,MULTICAST,M-DOWN> mtu 1500 qdisc ...
SEE ALSO
clone(2), network_namespaces(7), ip(8), ip-link(8), ip-netns(8)
Linux 2018-02-02 veth(4)