1. Explain how trace route, ping, and tcpdump work and what they are used for?
2. What is the last major networking problem you troubleshot and solved on your own in the last
year?
3. What LAN analyzer tools are you familiar with and describe how you use them to troubleshoot
and on what media and network types.
4. Explain the contents of a routing table (default route, next hop, etc.)
5. Describe the commands to set up a route.
6. What routing problems have you troubleshot?
7. How do you display a routing table on a Cisco? On a host?
8. How do you use a routing table and for what?
9. What is a route flap?
10. Describe a routing filter and what it does
11. What is a network management system?
12. Describe what network statistics or measurement tools you are familiar with and how you have
used them.
13. How do you manage a long term demanding stressful work environment?
14. Have you worked in an assignment based environment, e.g. work request/trouble ticket system,
and if so, describe that environment.
15. How a L2 switch works with broadcast, unicast, multicast, known/unknown traffic.
16. What problems with the network you had had and how you solved it.
17. What are the ways to troubleshoot the network, techniques, commands
18. Draw the typical network diagram you have to deal with
19. explain how it works
20. What part of it you are responsible
Pls help bro …..if u know the answer pls give to me………
1. 1. traceroute –> traces the route to the destination ip/network you want to reach, uses ICMP
pings.
Ping –> does icmp request to destination and waits for response
tcpdump –> similar to snoop utility to monitor/capture packets coming in going out of interface
Routing table
From Wikipedia, the free encyclopedia
In computer networking a routing table, or Routing Information Base (RIB), is a data
structure in the form of a table-like object stored in a router or a networked computer that lists
the routes to particular network destinations, and in some cases, metrics associated with those
routes. The routing table contains information about the topology of the network immediately
around it. The construction of routing tables is the primary goal of routing protocols. Static
routes are entries made in a routing table by non-automatic means and which are fixed rather
than being the result of some network topology 'discovery' procedure.
Routing tables are generally not used directly for packet forwarding in modern router
architectures; instead, they are used to generate the information for a smaller forwarding table
which contains only the routes which are chosen by the routing algorithm as preferred routes for
packet forwarding, often in a compressed or pre-compiled format that is optimized for hardware
storage and lookup. The remainder of this article will ignore this implementation detail, and refer
to the entire routing/forwarding information subsystem as the "routing table".
Contents
[hide]
1 Basics
2 Function
3 Difficulties with routing tables
4 Contents of routing tables
5 See also
6 References
7 External links
2. outing table mainly contains the entries to destination addresses/networks, the
gateway/interface to be used to reach the destination. you could add default entry which will be
added towards the end of the routing table to be used when no specific route entry matches
Basics
A routing table utilizes the same idea that one does when using a map in package delivery.
Whenever a node needs to send data to another node on a network, it must know where to send
it, first. If the node cannot directly connect to the destination node, it has to send it via other
nodes along a proper route to the destination node. Most nodes do not try to figure out which
route(s) might work; instead, a node will send an IP packet to a gateway in the LAN, which then
decides how to route the "package" of data to the correct destination. Each gateway will need to
keep track of which way to deliver various packages of data, and for this it uses a Routing Table.
A routing table is a database which keeps track of paths, like a map, and allows the gateway to
provide this information to the node requesting the information.
With hop-by-hop routing, each routing table lists, for all reachable destinations, the address of
the next device along the path to that destination; the next hop. Assuming that the routing tables
are consistent, the simple algorithm of relaying packets to their destination's next hop thus
suffices to deliver data anywhere in a network. Hop-by-hop is the fundamental characteristic of
the IP Internetwork Layer [1] and the OSI Network Layer, in contrast to the functions of the IP
End-to-End and OSI Transport Layers. Current router architecture separates the Control Plane
function of the routing table from the Forwarding Plane function of the forwarding table [2]
Function
During the process of routing, decisions of hosts and routers are aided by a database of routes
known as the routing table. The routing table is not exclusive to a router. Depending on the
routable protocol, hosts may also have a routing table that may be used to decide the best router
for the packet to be forwarded. Host-based routing tables are optional for the Internet Protocol,
as well as obsolete routable protocols such as IPX.
The types of entries in a routing table:
Network route: A route (path) to a specific Network ID in the internetwork. If it's a
gateway, the G flag will appear next to that IP address.
Host Route : A route to a specific internetwork address (Network ID and Host ID). Host
routes allow intelligent routing decisions to be made for each network address. Host
routes are used to create custom routes to control or optimize specific types of network
traffic. The H flag will appear next to IP addresses that belong to hosts.
Default route: A route that is used when no other routes for the destination are found in
the routing table. If a router or end system (such as a PC), cannot find a route for a
destination, the default route is used.
Difficulties with routing tables
The need to record routes to large numbers of devices using limited storage space represents a
major challenge in routing table construction. In the Internet, the currently dominant address
aggregation technology is a bitwise prefix matching scheme called Classless Inter-Domain
Routing (CIDR).
Since in a network each node presumably possesses a valid routing table, routing tables must be
consistent among the various nodes or routing loops can develop. This is particularly problematic
in the hop-by-hop routing model in which the net effect of inconsistent tables in several different
routers could be to forward packets in an endless loop. Routing loops have historically plagued
routing, and their avoidance is a major design goal of routing protocols.
Contents of routing tables
The routing table consists of at least three information fields:-
1. the network id: i.e. the destination network id
2. cost: i.e. the cost or metric of the path through which the packet is to be sent
3. next hop: The next hop, or gateway, is the address of the next station to which the packet
is to be sent on the way to its final destination
Depending on the application and implementation, it can also contain additional values that
refine path selection:
1. quality of service associated with the route. For example, the U flag indicates that an IP
route is up.
2. links to filtering criteria/access lists associated with the route
3. interface: such as eth0 for the first Ethernet card, eth1 for the second Ethernet card, etc.
Routing Chair also are a key aspect of certain security operations, such as unicast reverse path
forwarding (uRPF) [3]. In this technique, which has several variants, the router also looks up, in
the routing table, the source address of the packet. If there exists no route back to the source
address, the packet is assumed to be malformed or involved in a network attack, and is dropped.
Host id Cost Next hop
........ ........ ........
........ ........ ........
The routing table in simple words is the a table with routes to different destination addresses or
networks. This is important for the device to know how to send the traffic to that particular
network. This table can be populated dynamically and or add static routes thats persistent unless
manually changed. To display the Routing table in a Windows XP, Windows 2000 or Windows
2003, we can use either the "route" command or a "netstat" command. In either way, the
resulting output is the same. Using netstat: From the command prompt type "netstat -rn". The "-
r" switch displays the routing table.
C:\>netstat -rn
Route Table Interface List 0×1 ………………………
MS TCP Loopback interface 0×3 …00 13 ce 85 0e e1 ……
Intel(R) PRO/Wireless 2200BG Network Connection – Packet Scheduler Miniport 0×10005 …
00 ff 28 e3 2e 8a ……
Juniper Network Connect Virtual Adapter 0×80002 …00 14 22 fd 5b 8d ……
Broadcom NetXtreme 57xx Gigabit Controller – Packet Scheduler Miniport
=====================================================
Active Routes: Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 25
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 25
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 25
224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 25
255.255.255.255 255.255.255.255 192.168.0.2 10005 1
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1
255.255.255.255 255.255.255.255 192.168.0.2 80002 1
Default Gateway: 192.168.0.1
=====================================================
Persistent Routes: None
Using route:
Using route print command displays exactly the same output.
C:\>route print
Route Table
=====================================================
Interface List 0×1 ……………………… MS TCP Loopback interface
0×3 …00 13 ce 85 0e e1 …… Intel(R) PRO/Wireless 2200BG Network Connection – Packet
Scheduler Miniport 0×10005 …
00 ff 28 e3 2e 8a …… Juniper Network Connect Virtual Adapter 0×80002 …00 14 22 fd 5b 8d
…… Broadcom NetXtreme 57xx Gigabit Controller – Packet Scheduler Miniport
====================================================
Active Routes: Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.0.1 192.168.0.2 25
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 25
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 25
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 25
224.0.0.0 240.0.0.0 192.168.0.2 192.168.0.2 25
255.255.255.255 255.255.255.255 192.168.0.2 10005 1
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 1
255.255.255.255 255.255.255.255 192.168.0.2 80002 1
Default Gateway: 192.168.0.1
=====================================================
Persistent Routes: None
What is route flap
Route flapping
From Wikipedia, the free encyclopedia
In computer networking and telecommunications, route flapping occurs when a router
alternately advertises a destination network via one route then another (or as unavailable, and
then available again) in quick sequence. A closely related term is interface flapping where an
interface on a router has a hardware failure that will cause the router to announce it alternately as
"up" and "down".
Route flapping is caused by pathological conditions (hardware errors, software errors,
configuration errors, intermittent errors in communications links, unreliable connections, etc.)
within the network which cause certain reachability information to be repeatedly advertised and
withdrawn. In a network where a Link-state routing protocol is run, route flapping will force
frequent recalculation of the topology by all participating routers. In networks with Distance
vector routing protocols flapping routes can trigger routing updates with every state change. In
both cases, they prevent the network from converging.
Route flapping can be contained to a smaller area of the network if route aggregation is used. As
an aggregate route will not be withdrawn as long as at least one of the aggregated subnets is still
valid, a flapping route that is part of an aggregate will not disturb the routers that receive this
aggregate.[1]
If u want be a good network administrator u should under
stand all concepts clearly such as Topologies, Protocols,
Client/server technology.
Here i am giving the commands to trouble shoot the
network.
1) ipconfig - this is the command which shows your
present
Tcp/IP configuration.
2) ipconfig /all- command which shows your present Tcp/ip
configuration as well as Host name, Physical address, DNS
&
DHCP ip addresses and lease duration period.
3) ipconfig /release - if u r using dynamic ip address
this
command helps to remove the ip address.
4) ipconfig /renew - this helps to renew the ip address
from
DHCP Server.
Trouble shooting steps
1) first Ping your loop back address 127.0.0.1 with
this u can verify u r NIC status.
2)then Ping your own ip address if u r getting
reply
3) ping gateway ip address of your network
4)Using NSLOOKUP command verify the dns server ip
address and ping DNS
