• Learning Map
  • Unix Quiz Center
  • Unix Professional Network
  • Just-Unix-No-Noise FB Group

unixadminschool.com

  • Home
  • Announcements
    • Feed
    • MISC
  • Beginners zone
    • Beginners Lessons
    • Career Guidance
  • Experts Zone
    • Cloud Computing
    • Configuration Solutions
    • Migrations
    • Network Design
    • Scripting
    • Server Security
    • SUN CLUSTERS
    • SUN LDOMS
    • Tools & Applications
    • Veritas Cluster Services ( VCS ) Learning
  • Intermediate Zone
    • Linux Learning
      • Linux Booting
      • Linux Disk Management
      • Linux LVM
      • Linux Networking
      • Linux Performance
      • Linux Troubleshooting
      • Linux YUM/RPM
      • Performance Analysis
      • Redhat Linux Kernel
      • RHEL 6
        • RHEL LDAP
        • Rhel6 Storage
      • Web Servers
    • Solaris Admin
      • Blog for Unix Admin
        • Storage Administration – SAN
      • Oracle Hardware
      • Reference Docs
      • Solaris 10 Zones & LDOMs
      • Solaris 11
      • Solaris Access Control
      • Solaris Best Practices
      • Solaris Booting
      • Solaris Disk Management
      • Solaris DNS
      • Solaris How-to
      • Solaris Installation
      • Solaris Kernel
      • Solaris Networking
      • Solaris NFS
      • Solaris NIS
      • Solaris Packages & Patching
      • Solaris Performance
      • Solaris Tips
      • Solaris Troubleshooting
      • Solaris User Authentication
      • solaris X86
      • Solaris ZFS and Boot Environment
      • Storage Configurations
      • SUN Hardware
      • Troubleshooting Flow charts
    • Veritas Admin
      • Veritas Netbackup
      • VxVM Learning
      • VxVM Troubleshooting
  • QUIZ Center
  • Vlabs

Subscribe

Solaris Network Troubleshooting Flow Chart – host from remote subnet not reachable

You might be interested to read below :


  • Hands on Lab – Replacing Failed Disks from ZFS Pools ( RaidZ2 / RaidZ3 ) – Part2

  • Solaris Network Performance Tuning : know about TCP window size

  • Volume manager Migration from LVM to VxVM in Linux – Part 1

  • Solaris Troubleshooting NIS: add a user for NIS maps when passwd file is not in the /etc directory

  • ILOM ( Integrated Lights out Manager) Command line Reference

  • Linux Network Troubleshooting
  • Email
  • More
  • Print
  • Digg
Posted by Ramdev
7 Comments
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

7 Comments on “Solaris Network Troubleshooting Flow Chart – host from remote subnet not reachable”

  • Jayson
    15 September, 2011, 16:08

    good one ..

  • Ramdev
    15 September, 2011, 18:08

    @jayson – thanks for the comment.

  • Sai Pamidigantam
    13 January, 2012, 17:20

    Do think I am criticizing, but this above chart creates confusion.
    As I understand, A remote host is not reachable from your server/work station. Are we doing troubleshooting on remote host or local here ?
    If an user calls with the issue, first thing I ask is how the remote server is being accessed ? what protocol ? http, ssh, telnet, ftp or simply icmp ping
    Second, is there a firewall or proxy in between the servers ( a traceroute is better here – assuming all ethernet/IP )
    Assuming our workstation/server is okay ( and on network ), the troubleshooting has to start on remote server. The assumption here is, we have to have access to the console of that server. The above chart shows debug on our ( local/source) server.
    Few more comments later after I streamline my thoughts

  • Sai Pamidigantam
    13 January, 2012, 18:19

    Please read…”Do not think” from my previous post

  • Yogesh Raheja
    16 January, 2012, 10:16

    @Sai, thanks for your comment.
    Firstly,I totally agree with your comment that the complete communication flowchart will depends upon the utility which we are using to login into the server. However the flowchart shown here is “Generic” one and is applicable for any OS flavours in order to identify any issues from OS side if your server is un-responsive/not reachable/not pinging.
    Secondly Yes the post is based on remote host. Though the steps will be applicable to both local/remote hosts as the troubleshooting sequence will be same in either case but the network complexibilty will be more in case of remote hosts.
    Third, Firewall/proxy/network troubleshooting will come under 2nd & 3rd level as shown in the flow chart where devices have been checked and depending upon the situation necessary steps will be taken at Firewall/proxy/network/security level.
    Fourth, proceeding further yes console access would be required to proceed with the troubleshooting from OS side else one would have to connect our laptop to the serial port of the server physically to get to the server.
    Hope you have got the ans which you were expecting, thanks for your expert commnet on this.

  • Sai Pamidigantam
    18 January, 2012, 15:59

    Great. Appreciate all your efforts in educating future SAs ( and SAs refreshing on their fundamentals too )

  • Yogesh Raheja
    18 January, 2012, 17:53

    @Sai, thanks for your valuable boosters!!..

Leave a Comment

Join to our Professional Network (of 1400+ unixadmins ) to receive Unix Administration and Job Updates -

Pages1

Don't Miss Updates

 

Beginners Zone

 

Unixadmin Careers

Server Hardware

Beginners Lessons

Troubleshooting-Flowchart

 

Intermediate Zone

 

Solaris Booting

Solaris Volume Manager

Storage Configurations

Solaris Networking

Solaris X86

Solaris ZFS

Solaris NFS

Solaris NIS

Solaris Patching

Solaris Booting

Solaris Kernel

Veritas Volume Manager

Solaris NIS

Logical Volume Manager

Linux Networking

Linux Disk Management

Linux Troubleshooting

 

Experts Zone 

 

Solutions

Scripting and Automation

Server Security

Veritas Cluster Services

Sun Cluster Services

Cloud Computing

SUN LDOMS

Copyright © 2009 unixadminschool.com. All rights reserved.
loading Cancel
Post was not sent - check your email addresses!
Email check failed, please try again
Sorry, your blog cannot share posts by email.