05-30-2013
Yes the issue was resolved, it is an SEA and bridge issue.
Thanks alot guys. You guys are the best.
Moderator's Comments:
|
|
edit by bakunin: thanks for the follow-up, but we would have been overjoyed to know the exact cause and the procedure by which you solved it. As it is we all learn from such information and this is why we come here.
|
|
Last edited by bakunin; 05-31-2013 at 08:24 PM..
10 More Discussions You Might Find Interesting
1. IP Networking
We are unable to bring one of our linux boxes into the network once it was restarted. But once we stop and start the network service. We are able to ping the gateway and get into network. After a minute or two we get the following reponse for the ping command
64 bytes from 124.168.215.40:... (6 Replies)
Discussion started by: chrisanto_2000
6 Replies
2. IP Networking
Dear friends,
Please explain the functionality of the ping command and explain the network details, and IP layers.
I want some more clarification about following things
i) switch
ii) hub
iii) routers
iv) proxy (3 Replies)
Discussion started by: thangappan
3 Replies
3. IP Networking
Hello this is my first post at this forum.
Apologize for my lack of network understanding
but Im posting to learn.
I have a problem reaching default gateway 10.18.110.1
If I use my laptop I can ping 10.18.110.1 but with our red hat multihomed server the gateway does not respond to ping.
cat... (11 Replies)
Discussion started by: vettec3
11 Replies
4. Solaris
I was install new solaris10 on m4000 model after that i "ping -s" to default gateway but it's take longtime (2 Min) to reply and if i use "ping" only it's reply to fase(2 sec). any body who can tell me about my problem and how to fix it please. i'm try to fix several days. (2 Replies)
Discussion started by: cesmk
2 Replies
5. AIX
Hello,
I am new to Unix :D and have been trying to configure an AIX server running 5.3. I used smitty or smit to configure interface 0 on the server. I am able to ping the IP I set, however I am still unable to ping the gateway. I configured the IP by navigating to Communications Applications... (6 Replies)
Discussion started by: cdub50
6 Replies
6. Red Hat
I know the subject line is very similar to: destination host unreachable
but the problem with my machine appears to be somewhat different from that thread. apologies if I missed something from there.
We recently moved a machine physically and from one subnet to another . I used... (1 Reply)
Discussion started by: mirage
1 Replies
7. UNIX for Dummies Questions & Answers
I have NCR MP-RAS unix. I have been trying for several months to get our network working since we had never used it before. I have setup all routes that I can think of. I know it has something to do with the routing table, because out of sheer luck I was able to get it working, and than like a... (4 Replies)
Discussion started by: Rutgerncas
4 Replies
8. AIX
So I have created an LPAR. I think I have configured everything properly but I can't ping the network. The LPAR is on a VLAN. Other LPARs on the same VLAN works. Here's some info on the LPAR:
# entstat -d ent1
--------------------------------------------------
ETERNET STATISTICS (en1) :... (20 Replies)
Discussion started by: PPPP
20 Replies
9. Red Hat
Hi,
Here is the issue: There are 2 identical systems in the same subnet here. They can ping and ssh each other. One can ping the default gateway and one can not with error '... icmp_seq Destination Host Unreachable'. I can't find any difference between the two systems in terms of network... (4 Replies)
Discussion started by: aixlover
4 Replies
10. UNIX for Advanced & Expert Users
I have setup a Linux machine on my server but for some reason Im unable to reach my default gateway. This is causing me to not communicate with the outside world (unable to connect to CentOS repos)
# ifconfig
enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet... (3 Replies)
Discussion started by: Junaid Subhani
3 Replies
LEARN ABOUT DEBIAN
ditrack
DITRACK(1) General Commands Manual DITRACK(1)
NAME
dt - DITrack command line client tool
SYNOPSIS
dt command [options] [args]
dt-createdb repository-url issue-db-dir local-wc
dt-upgrade-0.7-db issue-db-dir
OVERVIEW
DITrack is a free, open source, lightweight, distributed issue (bug, defect, ticket) tracking system using a Subversion repository instead
of a backend database. It is written in Python and runs in UNIX environment (*BSD, Linux, MacOS X).
The project is inspired by the idea of Subissue issue tracking system.
However, while Subissue aims in merely replacing the traditional database storage with Subversion repository, DITrack is a major rethought
of the issue tracking system paradigm. The main difference is that instead of sticking to the centralized model (one database, one web
interface, one mail integration machinery), DITrack treats underlying Subversion storage as a versioned distributed file system which
enables benefits of truly distributed operation mode.
For more information about the DITrack project, visit http://www.ditrack.org.
Documentation for DITrack and its tools, including detailed usage explanations of the dt and dt-createdb programs, can be found at
/usr/share/doc/ditrack/html/index.html.
Run `dt help' to access the built-in tool documentation.
Automatic upgrade is possible for databases created by DITrack 0.7. If you are upgrading from previous version of DITrack, use the upgrage
utility from DITrack 0.7 first.
To upgrade a database run the dt-upgrade-0.7-db script, passing the database path as the argument, like:
dt-upgrade-0.7-db /home/user/ditrack-database
The upgrade procedure merely modifies the working copy (nothing gets committed to the repository). So, when done, you should commit the
changes manually.
April 2007 DITRACK(1)