EIGRP Summary

EIGRP Summary

The characteristics of EIGRP follow:

 Hybrid routing protocol (distance vector that has link-state protocol characteristics).

 Use DUAL, first proposed by E. W. Dijkstra and C. S. Scholten, to perform distributed shortest-path routing while maintaining freedom from loops at every instant. Although many researchers have contributed to the development of DUAL, the most prominent work is that of J. J. Garcia-Luna-Aceves.

 Cisco Proprietary created in 1994.

 First released in IOS 9.21

 Uses IP protocol 88.

 Makes Automatic summarization on network Class boundary.

 Classless protocol (supports VLSMs).

 Have the power to shut the Auto-summarization And make a configured manual Summarization.

 Default composite metric of bandwidth and delay.

 You can factor load, MTU and reliability into the metric.

 Eigrp metric is the same as IGRP*256, It uses the smallest B.W,Reliablity,Load & MTU with the Comulative delay upon the path…..The MTU doesn’t actually used in the Metric calculations, But is included in the EIGRP Routing updates.

 Sends route updates to multicast address 224.0.0.10, and nei. Reply’s back with Unicast Address.

 Sends non-periodic, partial, and bounded updates.

 Send Hello packets every 5 sec. and Hold down timer is 15 sec.

 For Low speed Hello is every 60 sec. with hold down time 180 sec.

 By default, EIGRP uses no more than 50 percent of the bandwidth of a link.

 Support for authentication via MD5 Only.

 Uses DUAL for loop prevention, and generating Succ./Fesible Succ.

 Maximum paths for Load-balancing are 6 & default is 4 , maximum are 16 in IOS 12.3(2)T and later IOS releases

 By default, Equal-Metric load balancing. If Unequal-Metric load sharing is used the router will load share inversely proportional to the metrics of the paths.

 Administrative distance is 90 for EIGRP internal routes, 170 for EIGRP external routes, and 5 for EIGRP summary routes.

 Potential routing protocol for the core of a network; used in large networks.

 For neighbor relation to be established, both routers must send and receive Hello or Ack packets from each other, they must have the same AS #, and the same Metric K values.

 Eigrp doesn’t restrict that neighbors must have the same Hello & dead interval timers, Unlike OSPF.

 Has a Maximum hop count of 255, the default is 100 in the last IOS releases.


The composite metric for each EIGRP route is calculated as
EIGRP metric = IGRP metric * 256
IGRP metric = [k1*BWIGRP(min) + (k2* BWIGRP(min))/(256-LOAD) + k3*DLYIGRP(sum)]
x [k5/(RELIABILITY + k4)]
If k5 is set to zero, the [k5/(RELIABILITY+k4)] term is not used.
Given the default values for k1 through k5, the composite metric calculation used by IGRP reduces to the default metric:
IGRP metric = BWIGRP(min) + DLYIGRP(sum)
BWIGRP(min) = 107/BW(min)
DLYIGRP(sum) = DLY(sum) /10


EGRP uses multiple packet types, all identified by protocol number 88 in the IP header:
• Hellos are used by the neighbor discovery and recovery process. Hello packets are multicast and use unreliable delivery.
• Acknowledgments (ACKs) are Hello packets with no data in them. ACKs are always unicast and use unreliable delivery.
• Updates convey route information. Unlike RIP and IGRP updates, these packets are transmitted only when necessary, contain only necessary information, and are sent only to routers that require the information. When updates are required by a specific router, they are unicast. When updates are required by multiple routers, such as upon a metric or topology change, they are multicast. Updates always use reliable delivery.
• Queries and Replies are used by the DUAL finite state machine to manage its diffusing computations. Queries can be multicast or unicast, and replies are always unicast. Both queries and replies use reliable delivery.
• Requests were a type of packet originally intended for use in route servers. This application was never implemented, and request packets are noted here only because they are mentioned in some older EIGRP documentation.
EIGRP has four components:
Protocol-Dependent Modules (PDM): EIGRP implements modules for IP, IPX, and AppleTalk, which are responsible for the protocol-specific routing tasks. For example, the IPX EIGRP module is responsible for exchanging route information about IPX networks with other IPX EIGRP processes and for passing the information to the DUAL. Additionally, the IPX module will send and receive SAP information.
Reliable Transport Protocol (RTP): The Reliable Transport Protocol (RTP) manages the delivery and reception of EIGRP packets. Reliable delivery means that delivery is guaranteed and that packets will be delivered in order. If any packet is reliably multicast and an ACK is not received from a neighbor, the packet will be retransmitted as a unicast to that unresponding neighbor. If an ACK is not received after 16 of these unicast retransmissions, the neighbor will be declared dead. The time to wait for an ACK before switching from multicast to unicast is specified by the multicast flow timer. The time between the subsequent unicasts is specified by the retransmission timeout (RTO). Both the multicast flow timer and the RTO are calculated for each neighbor from the smooth round-trip time (SRTT). The SRTT is the average elapsed time, measured in milliseconds, between the transmission of a packet to the neighbor and the receipt of an acknowledgment. The formulas for calculating the exact values of the SRTT, the RTO, and the multicast flow timer are proprietary.
Neighbor Discovery/Recovery: Hellos are multicast every 5 sec., minus a small random time to prevent synchronization. & are unicast every 60 sec. On multipoint X.25, Frame Relay, and ATM interfaces, with access link speeds of T1 or slower also it's the default for ATM SVCs and for ISDN PRI In all cases, the Hellos are unacknowledged.
Diffusing Update Algorithm (DUAL): Used For routing calculations, loop free & convergence.


EIGRP Conversion

The steps for EIGRP convergence are as follows:

1- When the local router sees a connected route disappear, it checks
the topology table for a feasible successor.

2- If no feasible successor exists, The Route moves into active state in
the topology table.

3- The originating router queries its neighbor for alternative routes.

4- If an alternative exists, it is sent to the Originating router via an update message.
If no alternative route is found in the neighbor topology table, this neighbor
It-self Also send a query to all its own neighbors to confirm if they got an
alternative route.

5- When the router receives the alternatve routes though its neighbors, it adds the
route to its topology table and run the DUAL to insert the successor in its
Routing table.


6- If no router is able to supply an alternative route, All routers within the
domain remove the network from their Routing & topology table.

7- A flash update of the path with the higher metric is sent out.

8- Updates are acknowledged.

Convergence is very quick because it is the detection time, plus query, reply, and update time.
If there is a feasible successor, then convergence is almost instantaneous.











EIGRP SIA

Once a route goes Active and the Query sequence is initiated, the route can only come out of the Active state and move to Passive state when it receives a Reply for every generated Query. If the router does not receive a reply to all the outstanding queries within 180 seconds (the default time), the route goes to the SIA state.


When the route goes to SIA state, the querying router resets the neighbor relationship to the neighbor that fails to Reply. This setting causes the router to go Active on all routes known through the lost neighbor and to readvertise all the routes that it knows about to the lost neighbor.


SIA-Query and SIA-Reply are two new additions to the Type, Length, Value (TLV) triplets in the EIGRP packet header. These packets are generated automatically with no configuration required, from Cisco IOS Software Release 12.1(5) and later with the active process enhancement feature. This feature enables an EIGRP router to monitor the progression of the search for a successor route and ensure that the neighbor is still reachable. Improved network reliability results from reducing the unintended termination of the neighbor adjacency.

SIA-Query is sent every SIA-Retransmit timer (half the active timer, default is 90 sec.)
as long as SIA-replies are received, the Active timer & SIA-Retransmit timer will reset for maximum 3 times (270 sec).

So if no SIA-Reply is received from neighbor for 90 sec. the router reset the neighbor relationship.

So as long as a neighbor router responds to the SIA-Query, it won't be declared SIA and reset, for six minutes (270 sec.), assuming a default Active time of 180 seconds. This gives ample time for a large network to respond to queries.













EIGRP Configuration

config)# router eigrp (1-65535)
conf-router)# network < Net ID> (classlfull)
conf-router)# network < Net ID> < wildcard>
(To identify the exact Interfaces or connected Networks which will participate in the EIGRP process,
Also Networks will be auto summarized unless no auto-sumary cmd is used )

conf-router)# metric maximum-hop <#> (Up to 255, default =224)
conf-router)#passive-interface
conf-router)#distance (Define an administrative distance, default =90)
conf-router)#metric weight
(tos is a relic of the Cisco original intention to have IGRP do type of service routing; this plan was never adopted, and tos in this command is always set to zero.)

conf-router)#maximum –paths
(Up to 16 Links for load sharing, Over Equal/Unequal metric paths, default is 4 paths)
conf-router)#variance <#>
conf-router)#traffic-share < minimum / balanced >
(Minimum is the default, and will provide Equal-Metric load Balance,
Balanced is for UnEqual-Metric load sharing, will be done referred to each link Metric)

conf-router)# eigrp log-neighbor-changes
conf-router)# eigrp router-id < ip add > ( Set router-id for this EIGRP process)

conf-router)#no auto-summary (disable automatic summ. To the class boundary)
config-if)# ip summary-address eigrp
(Will suppress the advertisement of the more specific routes)

conf-router)# no metric holdown (Disables Hold down timer)
conf-router)#timers active-time (Default is 3 min)

config-if)# bandwidth < BW in kbps>
config-if)# delay < Delay in Micro sec> (maximum167 seconds)
config-if)# ip bandwidth-percent eigrp < % >
( To adjust Eigrp traffic over the link Bandwidth , default is 50%)

config-if)# ip hello-interval eigrp < sec >
config-if)# ip hold-time eigrp < sec >
config-if)# no ip split-horizon (Disables it from a specific interface)


Advanced EIGRP Configuration

EIGRP Stub Networks

• The EIGRP stub routing feature improves network stability, reduces resource utilization, and simplifies remote router (spoke) configuration.

• Stub routing is commonly used in a hub-and-spoke topology.

• Spokes are configured as stub routers under the global config prompt.

• A stub router sends a special peer information packet to all neighboring routers to report its status as a stub router.

• A neighbor that receives a packet informing it of the stub status does not query the stub router for any routes, instead, hub routers connected to the stub router answer the query on behalf of the stub router



conf-router)# eigrp stub
conf-router)# eigrp stub
(optional cmd , Default is connected and summary.)


Receive-only : Prevents the stub from sending any type of route, Cannot use any option with it.
This will issue to config Static routes to reach the routes on the Hub to
the Spoke-Stub router.

Redistributed : Permits stub to send redistributed routes.


Connected : Permits stub to send connected routes (may still need to redistribute If a
network command does not include the connected routes).

Static : Permits stub to send static routes (must still redistribute).

Summary : Permits stub to send summary routes.








EIGRP Authentication MD5
The router may be configured to use more than one "key chain." & also different keys at different times (key management).
The steps for setting up EIGRP authentication follow:
1-Define a key chain with a name.
2- Define the authentication key or keys on the key chain
3- Define the password of the key or keys.
4- Apply authentication on an interface and specify the key chain to be used.
5- Apply MD5 authentication on an interface.
6- Optionally configure key management.
Here is the cmds :
config)# key chain
config-keychain)# key <#>
config-keychain-key)# key-string < password>
config-keychain-key)#accept-lifetimeduration< mm- infinite >
config-keychain-key)#send-lifetime duration < mm- infinite >

config)# interface
config-if)# ip authentication key-chain eigrp
config-if)# ip authentication mode eigrp

# debug eigrp packets

Notes:

The password that is accepted from other routers and the password that is used with transmitted/sent messages are managed separately. Both the accept-lifetime and the send-lifetime cmd. must have a specified start time and may have either a specified duration or end time or the keyword infinite. The key numbers are examined from the lowest to the highest, and the first valid key is used.

If the service password-encryption command is not used when
implementing EIGRP authentication, the key string will be stored as plaintext
in the router configuration. If you configure the service password-encryption command, the key string will be stored and displayed in an encrypted form; when it is displayed, there will be an encryption type of 7 specified before the encrypted key string.
Show Commands

# sh ip route
# sh ip route eigrp
# sh ip route < Net ID >
# sh ip protocols

# sh ip eigrp traffic
# sh ip eigrp traffic


# sh ip eigrp nei
# sh ip eigrp nei detail
# sh ip eigrp topology

# sh ip eigrp topology (optional)
# sh ip eigrp topology all-links
# sh ip eigrp topology < active / pending / zero-successors>
# sh ip eigrp traffic
# sh ip eigrp events (Shows the types of packets sent and received and
statistics on routing decisions.)


#debug ip eigrp
#debug ip eigrp fsm
#debug ip eigrp nei (Shows the hello packets sent and received to the neighbors)
#debug ip eigrp route (Shows dynamic changes made on the routing table process)
#debug ip eigrp summary (Shows a summary of the EIGRP activity)
#debug ip eigrp packet (Shows the packets sent and received by the router.
The packet types to be monitored can be selected.
Up to 11 types are available)

# no debug all

RIPv2 Summary

RIPv2 Summary

The characteristics of RIPv2 follow :

 Distance-vector protocol.

 Use UDP port 520.

 Makes Automatic summarization on network Class boundary.

 Classless protocol (supports VLSMs).

 Have the power to shut the Auto-summarization And make a configured manual Summarization.

 Supports VLSMs.

 Metric is router hop count.

 Maximum hop count is 15; infinite (unreachable) routes have a metric of 16.

 Periodic route updates sent every 30 seconds to multicast address 224.0.0.9.

 25 routes per RIP message (24 if authentication is used).

 Invalid route marked after 180 sec.

 Flush timer is 280 sec.

 Hold-down timer 180 sec.

 Supports authentication.

 Implements split horizon with poison reverse.

 Implements triggered updates.

 Subnet mask included in route entry.

 Administrative distance for RIPv2 is 120.

 Used in small, flat networks or at the edge of larger networks.





RIPv2 Convergence


The steps for RIPv1 convergence are as follows:

1- When the local router sees a connected route disappear, it sends a Flash update and removes the route entry from its table. This is Called a triggered update with poison reverse.

2- The receiving routers send a Flash update and put the affected route in holddown.

3- The originating router queries (request message) its neighbor (DC) for alternative routes. If the neighbor has an alternative route, it is sent (respond); otherwise, the Poisoned route is sent.

4- The originating router installs the best alternative route that it hears because it has purged the original routes, and Send the new updates in its periodic routing update timer (30 sec).

5- Routers that are in holddown ignore only the alternative route, Unless its metric is much lower than the invalid route, it will accept it immediately and won't obey the holdown timer rule.

6- When the other routers emerge from holddown, they will accept the alternative route.

7- Convergence takes the time for detection, plus holddown, plus the number of routing updates (equal to the hop-count diameter of the network). This could take a long time.





















RIP v2 Configuration

config)# router rip
conf-router)# version 2
conf-router)# network < Net ID> (classfull)
conf-router)#passive-interface
conf-router)#maximum –paths (Up to 6 Links for load sharing on a R.B basis,
Over equal metric paths default =is 4 paths)
conf-router)#traffic-share min (How to compute traffic share over alternate paths)
conf-router)# no ip split-horizon (Disables it from a specific interface)
conf-router)#distance (Define an administrative distance, default =120)

conf-router)# timers basic < update - invalid –holdown –flush – sleep > (Adjust timers in sec , Sleeptime is a timer used to specify a period, in milliseconds, to delay a regular routing update after receiving a triggered update.)
conf-router)# neighbor < ip add>
(Because RIP is a broadcast protocol you may configure RIP to exchange routing information in a Point-Point non-broadcast network such as Frame Relay. In this type of network, RIP must be informed of neighbor RIP routers, Also When it is used in combination with the passive-interface cmd, routing information can be Only exchanged between the router and this nei Ex. Unix server on a LAN )

conf-router)#validate-update-source
(This command is applicable only to RIP and IGRP. The software ensures that the source IP address of incoming routing updates is on the same IP network as one of the addresses defined for the receiving interface. Disabling split horizon on the incoming interface will also cause the system to perform this validation check. For unnumbered IP interfaces (interfaces configured as IP unnumbered), no checking is performed. )

conf-router)# no auto-summary
conf-if )# ip summary-address rip < Net ID + mask>

Show Commands

# sh ip route
# sh ip route rip
# sh ip route < Net ID >
# sh ip rip database
# sh ip protocols

#debug ip rip
#debug ip rip events
# no debug all
Sending & Receiving Routing Updates
Options


By default, a RIP process configured on a Cisco router sends only RIPv1 messages but listens to both RIPv1 and RIPv2. This default is changed with the version cmd.

The network administrator can configure the router to only receive and send Version 1 packets.
Here is the cmds :

conf-router)# version <1 / 2>

config-if)# ip rip send version 1 (Send only ver 1 updates)
config-if)# ip rip send version 2 (Send only ver 2 updates)
config-if)# ip rip send version 1 2 (Send Both ver 1 and 2 updates)


config-if)# ip rip receive version 1 ( Accept only ver 1 updates)
config-if)# ip rip receive version 2 ( Accept only ver 2 updates)
config-if)# ip rip receive version 1 2 ( Accept both ver 1 and 2 updates)


Note : Use this command to override the default behavior of RIP as specified by the version command.

Great Way To Learn Subnetting

1. What is an IP Address?
An IP address is made of 4 Octets, or 32 bits. It is usually represented in dotted decimal format like this: 131.107.2.205. Each number represents an octet. An octet is a group of 8 bits. Since we have 4 octets in an IP Address, there are 8*4=32 bits in an IP Address.
Computers do not understand dotted decimal notation, as they only function in binary. All computers understand is 1 and 0. Therefore, we must find a way to transfer an IP Address from dotted decimal format to binary. We do this octet by octet.
Each bit in an octet has an associated decimal value:

Bit 1 2 3 4 5 6 7 8
Bit value 128 64 32 16 8 4 2 1
So you can follow, here is a decimal to binary calculator. However, I advise you to do the math at first to better understand the concepts...

Insert Number:

Let’s take an example. I have an IP address of 131.107.2.4. What is that in Binary?
Let’s do this octet by octet:
131:
Bit Value 128 64 32 16 8 4 2 1
Binary 1 0 0 0 0 0 1 1

Column with a “1” in binary mean that we count the corresponding bit value. If you add up all the bit values marked with a one, you get 128+2+1=131.
107:
Bit Value 128 64 32 16 8 4 2 1
Binary 0 1 1 0 1 0 1 1

Column with a “1” in binary mean that we count the corresponding bit value. If you add up all the bit values marked with a one, you get 64+32+8+2+1=107
2:
Bit Value 128 64 32 16 8 4 2 1
Binary 0 0 0 0 0 0 1 0

Column with a “1” in binary mean that we count the corresponding bit value. If you add up all the bit values marked with a one, you get 2
4:
Bit Value 128 64 32 16 8 4 2 1
Binary 0 0 0 0 0 1 0 0

Column with a “1” in binary mean that we count the corresponding bit value. If you add up all the bit values marked with a one, you get 4
Now we know that another way of writing our example IP address of 131.107.2.4 is:

10000011.01101011.00000010.00000100

IP Addresses are made of two distinct parts: the Network ID and the Host ID. When you try to ping an IP address, IP at Layer 3 needs to determine whether the target IP address is local or remote to your subnet. To explain this, I like to ask my students the following question:
“Let’s say I live on Maple Tree Lane. You say that you also live on Maple Tree Lane. Are we neighbors? Well, we may be, or we may not be. We do not have enough information to answer that question. Specifically, we do not know if we live in the same town. If we do live in the same town, and our street addresses are similar, then we are neighbors. If we do not live in the same town, it does not matter whether our street addresses are similar or not: we are not neighbors.”
The same applies to IP addressing. Before I can find out what your Host ID is – i.e. your street address – I have to worry about what your Network ID is – i.e. your town.
So how does IP know what the Host ID and Network IDs are? That is the role of the Subnet Mask.

Please note that neither the network ID, the host ID nor the subnet bit can be all 0s or all ones. More to come about this later…

2. What is a Subnet Mask?
A Subnet Mask is used to enable IP at Layer 3 to find out whether the target IP address you are trying to contact is local or remote to your network. That is all it does. It helps you determine which part of an IP Address is the Network ID, and which is the Host ID. So how does it do that?
We have all seen a Subnet Mask before. It usually looks something like this:

255.255.255.0

This subnet mask is obviously displayed in dotted decimal format. As we already know, however, computers do not understand this format. They only understand binary. So let’s apply what we know about binary to our subnet mask:

255
Bit Value 128 64 32 16 8 4 2 1
Binary 1 1 1 1 1 1 1 1

Column with a “1” in binary mean that we count the corresponding bit value. If you add up all the bit values marked with a one, you get 128+64+32+16+8+4+2+1=255
So, 255 is “all ones”, as you may have heard before.

0:
Bit Value 128 64 32 16 8 4 2 1
Binary 0 0 0 0 0 0 0 0

Column with a “1” in binary mean that we count the corresponding bit value. If you add up all the bit values marked with a one, you get 0. So, 0 is “all zeros”, as you may have heard before.
In other words, our 255.255.255.0 subnet masks in binary looks like this:
11111111.11111111.11111111.00000000
Note that a subnet mask is also a 32 bit, 4 octet entity that matches the structure of our IP addresses…
If I were to superimpose the IP address and subnet mask we have translated so far, I would get this:

131.107.2.4 10000011. 01101011. 00000010. 00000100
255.255.255.0 11111111. 11111111. 11111111. 00000000

I highlighted the Network bits in Red, and the Host bits in Blue. Notice anything? All the network bits are the bits that had a value of “1” in the subnet mask, and all the host bits are the bits that had a value of “0” in the subnet mask. Easy, isn’t it? In our example, the Network ID is 131.107.2, and the host ID is 4. If I change the subnet mask to 255.255.0.0, what happens? Well, let’s apply the same logic:

131.107.2.4 10000011. 01101011. 00000010 00000100
255.255.0.0 11111111. 11111111. 00000000 00000000

What happens now? My network ID is now 131.107 and my host ID is 2.4! That is why an IP address on its own cannot exist! That is why a host on a network needs at least an IP address AND a subnet mask!
Let’s say that I tell you that I have 2 IP addresses:
131.107.2.4 and 131.107.5.6
Are they local to each other, or remote?
You cannot answer that question, because it is incomplete! I need to give you the subnet mask as well! Let’s see why…
Let’s say that the subnet mask is 255.255.255.0. Then we have:

131.107.2.4 10000011. 01101011. 00000010. 00000100
131.107.5.6 10000011. 01101011. 00000101. 00000110
255.255.255.0 11111111. 11111111. 11111111. 00000000

Do the Network IDs match? No! Look at the third octect:
0 0 0 0 0 0 1 0
0 0 0 0 0 1 0 1
If the network IDs do not match, then the two IP addresses are remote from each other. They are on different subnets, and you will need a router to go from one to the other.

Let’s take the same example with a different subnet mask of 255.255.0.0:
131.107.2.4 10000011. 01101011. 00000010. 00000100
131.107.5.6 10000011. 01101011. 00000101. 00000110
255.255.0.0 11111111. 11111111. 00000000. 00000000

Do the Network IDs match now? Yes!
If the network IDs match, then the two IP addresses will be on the same network. You do not need a router to go from one to the other in this scenario.

Let’s sum this up: we have seen how only having an IP address is not sufficient, and how the same two IP addresses can be either remote or local to each other depending on which subnet mask you are using. This is at the basis of IP troubleshooting.

3. What are IP classes?
You may have heard of the different classes for IP addresses, namely, class A, B and C. How does that work? Let’s look at the following table:

Class A 1-127* 0xxxxxxx.
Class B 128-191 10xxxxxx.
Class C 192-223 110xxxxx.
*127 is part of the class A range, but you cannot assign any 127.x.x.x IP addresses to hosts as the entire range is reserved by InterNIC for the loop back address…

What does this mean? When talking about a Class of IP addresses, you only look at the first octet to determine what class this IP address belongs to.
For class A, InterNIC decided that the 1st octet would start with a bit value of 0. Therefore, the lowest binary of the 1st octet is 0000001, and the highest is 01111111 (in decimal, that would be from 1 to 127)
For class B, InterNIC decided that the 1st octet would start with a bit value of 10.
Therefore, the lowest binary of the 1st octet is 1000000, and the highest is 10111111 (in decimal, that would be from 128 to 191)
For class C, InterNIC decided that the 1st octet would start with a bit value of 110.
Therefore, the lowest binary of the 1st octet is 1100000, and the highest is 11011111 (in decimal, that would be from 192 to 223)
There are other classes, D and E, but they are not used right now and are illegal on the Internet.
Also, note that you can use any subnet mask classes with any IP address classes. Subnet mask classes are as follows:

Class A 255.0.0.0
Class B 255.255.0.0
Class C 255.255.255.0

In other words, it is totally possible to have a Class B IP address and a class C subnet mask… hang on… isn’t that what we have been taking as an example all along? Remember our 131.107.2.4 w/ a subnet mask of 255.255.255.0?

4. What is subnetting?
Subnetting is the action of taking an IP range where all IP addresses are local to each other and dividing it into different ranges – or subnets – where IP addresses from one range will be remote from any other IP addresses from any other range.
If you want to find out how many hosts you have in an IP range, first you need to determine how many host bits there are. Let’s take our previous example of 131.107.2.4 and 255.255.255.0. We already established previously that the Network ID was 131.107.2 and the Host ID was 4. In other words, we have 3 octets for the Network ID and one octet – or 8 bits – for the Host ID. Now that you have determined the amount of host bits you had, apply that number to the following formula:

(2^N)-2)=number of hosts, where N is your number of host bits

That gives us: ((2^8)-2)=254 hosts.

That means that in our example, we have the 131.107.2.x network, which contains 254 possible IP addresses, all local to each other.
What if I chose a class A subnet mask? I would then have:

(2^24)-2)=16,777,214 valid IP addresses in that range!

What if I do not need that many – heck, who does J -- and decided to divide that range in to several other, more manageable ranges? Well, I need to subnet.

Note: we have to subtract 2 because we lose the all ones and all zeroes values.
If I only had 2 bits to play with, in binary, I would have 2^2=4 possibilities:
00
01
10
11
However, all zeros in IP means the whole network, and all ones is the broadcast ID, neither one being valid IP addresses that can be assigned to a host. That is why we always lose 2 and have to subtract two from (2^N)…

Let’s look at the following table:

Bit Value 128 64 32 16 8 4 2 1
Subnet Mask 192 224 240 248 252 254 255
Number of Subnets 2 6 14 30 62 126 254

This table is the only table you need to learn to understand IP subnetting and IP addressing! Three little lines!
Let’s look at it line by line. The first line we are already acquainted with, so I will not spend more time on it.
The second line tells you what your subnet mask will be. How do we get those results? If you look at the bit value line, and add up the bit values, you will see that:
128+64=192
192+32=224
224+16=240
240+8=248
248+4=252
252+2=254
254+1=255
Easy? J
Now to the third line. This one tells you how many subnets will get if you use the corresponding subnet mask. In other words: if you use the 192 in your subnet mask, you will get 2 subnets. If you use 224, you will get 6 subnets, etc… So how did I get those numbers? Well, let’s take 192 as an example. How many bits did I use to get 192? Well, I added 128 and 64, so that would be two bits, right? Let’s look at our well-known formula:

((2^2)-2)= 2

That is where the values in the third line come from. Want to check another one? Let’s look at 248. How many bits did I use to get to 248? 128+64+32+16+8=248, or a total of 5 bits. ((2^5)-2)=30

So now, we know how to build that table, and we understand how it is built. We are almost done with subnetting!

Let’s say my boss shows up one morning and says:
“Dave, I have an IP range of 131.107.0.0 and a subnet mask of 255.255.0.0. I want 6 subnets out of this.” What do I do now?
I look at my chart, and I see that to get 6 subnets, I need a subnet mask of 224. I already have an existing subnet of 255.255.0.0, which in binary looks like this:

11111111.11111111.00000000.00000000

I cannot “borrow” any more bits from the first 2 octets, as they are already network bits – represented by a binary value of 1. So the only I can add this “224” to my subnet mask is to borrow from the host ID. I take the next available octec – the third in our example – and end up with a subnet mask of 255.255.224.0, which looks like this in binary:

11111111.11111111.11100000.00000000

Note that we “borrowed” 3 host bits – binary value of 0 -- in the third octet and made them network bits – binary value of 1. Note as well that 3 bits is what I need to make 224: 128+64+32=224.
Now that I have a subnet mask, I can tell that I have 13 host bits, meaning that I will have ((2^13)-2)=8190 valid IP addresses per range J

So I can go back to my boss and say “Boss, your new subnet mask for the 131.107.x.x network will be 255.255.224.0, and you will have 6 subnets with 8190 IP addresses in each range.” What’s my boss’ next question?
“Dave, what are those ranges?” Oh yeah… maybe I forgot that part J

5. Calculating IP ranges in subnetted environments

Bit Value 128 64 32 16 8 4 2 1
Subnet Mask 192 224 240 248 252 254 255
Number of Subnets 2 6 14 30 62 126 254
Here is our little subnetting chart again. In this section, we will learn how to derive the actual IP ranges from the network address and subnet mask.
In our example, we had:

Original IP range: 131.107.x.x
Original Subnet Mask: 255.255.0.0

Subnetted subnet mask: 255.255.224.0
Amount of subnets: 6

The first valid range will be 131.107.32.1 to 131.107.63.254. How did I get there? I used the above chart.
Once I determined that 224 was my subnet bit, I asked myself: what is the lowest bit value needed to make 224?” The answer is: 32 (128+64+32=224, and 32 is the lowest of all 3 bit values.) If you look at the chart, you can see this:

Bit value 32
Subnet Mask 224
Number of subnets 6

Visually, it is easy to see that to have 6 subnets, I will use 224 as a subnet bit and will start my first range at 32. I will then increment each range by that same value of 32. I love this chart!
My 6 ranges will be:

131.107.32.1 to 131.107.63.254
131.107.64.1 to 131.107.95.254
131.107.96.1 to 131.107.127.254
131.107.128.1 to 131.107.159.254
131.107.160.1 to 131.107.191.254
131.107.192.1 to 131.107.223.254

As you can see, to get the next range, I simply incremented my original value by the same value (look at the numbers in RED) I started at 32, then incremented 5 times by that same value of 32.
If you look at the values in BLUE you will see that they always are the next red value minus 1. For example, if I look at the first range x.x.32.1 to x.x.63.254, I looked at the next line’s red value, here 64, and subtracted 1 to get to 63. That is all there is to it!
By the way, note that my last octet on the start of range is always 1 – it cannot be 0, or else my host ID would be all 0s – and that the last octet is always 254 in the last IP of each range – it cannot be 255, or else it would be all 1s, which we know is the broadcast address, and is therefore not available for hosts to have.

In this example, we subnetted a Class B network into 6 subnets. Note that it is somewhat different if you subnet a Class A and a Class C. Let’s do a Class A example.
Original IP range: 10.x.x.x
Original Subnet mask: 255.0.0.0
Amount of subnets needed: 14
To get 14 subnets I need a subnet bit of 240, therefore my new subnet mask becomes 255.240.0.0. Note that my subnet bit is now the second octet, not the third as in the previous example. This will have its importance when we create our ranges.
What is the smallest bit value needed to make 240? 16. Therefore I will start my ranges at 16 and will increment by that same value of 16.
My ranges are:
10.16.0.1 to 10.31.255.254 10.128.0.1 to 10.143.255.254
10.32.0.1 to 10.47.255.254 10.144.0.1 to 10.159.255.254
10.48.0.1 to 10.63.255.254 10.160.0.1 to 10.175.255.254
10.64.0.1 to 10.79.255.254 10.176.0.1 to 10.191.255.254
10.80.0.1 to 10.95.255.254 10.192.0.1 to 10.207.255.254
10.96.0.1 to 10.111.255.254 10.208.0.1 to 10.223.255.254
10.112.0.1 to 10.127.255.254 10.224.0.1 to 10.239.255.254
Now let's do this with a class C. Remember, class C is the hardest, so follow this carefully!
Original IP range: 192.168.2.x
Original Subnet mask: 255.255.255.0
Amount of subnets needed: 6
To get 6 subnets I need a subnet bit of 224, therefore my new subnet mask becomes 255.255.255.224. Note that my subnet bit is now the 4th octet, not the third or second as in the previous examples. This will have its importance when we create our ranges.
What is the smallest bit value needed to make 224? 32. Therefore I will start my ranges at 32 and will increment by that same value of 32. (Are you getting the hang of it by now?)
My ranges are:
192.168.2.33 to 192.168.2.62 192.168.2.129 to 192.168.2.158
192.168.2.65 to 192.168.2.94 192.168.2.161 to 192.168.2.190
192.168.2.97 to 192.168.2.126 192.168.2.193 to 192.168.2.222
But, you say, I thought I was starting at 32?!? My first range is starting at 33! Well, remember the other examples? We always started at .1, didn't we? Except that here, because we are already subnetting at the fourth octet, we don't have room for a fifth to add the .1, so we have to incorporate it in the last octet. So why can we not use 192.168.2.32 w/ a subnet mask of 255.255.255.224? Let's see why:
192.168.2.32 11000000. 10101000. 00000010. 00100000
255.255.255.224 11111111. 11111111. 11111111. 11100000
Looking at it in binary, it is obvious that the Host ID is all zeroes, which we know is not possible...
That is it. If you know and understand this, you can subnet! Enjoy practicing...

Ports from 0 to 999 and their protocols!

Hi guys,
These are the ports (protocols) from 0 to 999 (actually they are not the all, there are nearly 65000 protocols)

use the CTRL + F to search for the port or the protocol:

0 Shirt Pocket netTunes.
Shirt Pocket launchTunes.
1 TCPMUX, TCP Port Service Multiplexer.
2 Management Utility.
3 Compression Process.
4
5 Remote Job Entry.
6
7 Echo.
8
9 Discard.
10
11 SYSTAT.
12
13 Daytime.
14
15 [was netstat].
16
17 Quote, Quote of the Day.
18 RWP, Remote Write Protocol.
Send, Message Send Protocol.
19 Chargen, Character Generator Protocol.
20 FTP, File Transfer Protocol, data.
21 FTP, File Transfer Protocol, control.
22 SSH.
23 Telnet.
24 Any private mail system.
25 SMTP, Simple Mail Transfer Protocol.
26
27 NSW User System FE.
28
29 MSG ICP.
30
31 MSG Authentication.
32
33 Display Support Protocol.
34
35 Any private printer server.
36
37 Time, Time Protocol.
38 RAP, Internet Route Access Protocol.
39 RLP, Resource Location Protocol.
40
41 Graphics.
42 Internet Name Server.
43 Whois.
44 MPM FLAGS Protocol.
45 Internet Message Protocol.
46 MPM [default send].
47 NI FTP.
48 Digital Audit Daemon.
49 TACACS.
TACACS+.
50 RMCP, Remote Mail Checking Protocol.
51 IMP Logical Address Maintenance.
52 XNS Time Protocol.
53 DNS, Domain Name System.
54 XNS Clearinghouse.
55 ISI Graphics Language.
56 XNS Authentication.
57 MTP, Mail Transfer Protocol.
58 XNS Mail.
59 NFILE.
60
61 NI MAIL.
62 ACA Services.
63 Whois++.
64 Communications Integrator (CI).
65 TACACS-Database Service.
66 Oracle SQL*NET.
67 BOOTP, Bootstrap Protocol, server.
68 BOOTP, Bootstrap Protocol, client.
69 TFTP, Trivial File Transfer Protocol.
70 Gopher.
71 Remote Job Service.
72 Remote Job Service.
73 Remote Job Service.
74 Remote Job Service.
75 Any private dial out service.
76 Distributed External Object Store.
77 Any private RJE service.
78 vettcp.
79 Finger.
80 HTTP, HyperText Transfer Protocol.
81 HOSTS2 Name Server.
82 XFER Utility.
83 MIT ML Device.
84 Common Trace Facility.
85 MIT ML Device.
86 Micro Focus Cobol.
87 Any private terminal link.
88 Kerberos.
89 SU/MIT Telnet Gateway.
90 Is being used unofficially by Pointcast.
90 DNSIX Securit Attribute Token Map.
91 MIT Dover Spooler.
92 Network Printing Protocol.
93 Device Control Protocol.
94 Tivoli Object Dispatcher.
95 SUPDUP.
96 DIXIE.
97 Swift Remote Virtual File Protocol.
98 TAC News.
99 Metagram Relay.
100 [unauthorized use]
101 HOSTNAME.
102 TP0 over TCP.
103 Genesis Point-to-Point Trans Net.
104 ACR-NEMA Digital Imag. & Comm. 300.
105 Ph.
105 Mailbox Name Nameserver.
106 3COM-TSMUX.
107 Remote Telnet Service.
108 SNA Gateway Access Server.
109 POP, Post Office Protocol, version 2.
110 POP, Post Office Protocol, version 3.
111 Portmapper.
112 McIDAS Data Transmission Protocol.
113 Identification Protocol.
114
115 SFTP, Simple File Transfer Protocol.
116 ANSA REX Notify.
117 UUCP, Unix To Unix Copy.
118 SQL Services.
119 NNTP, Network News Transfer Protocol.
120 CFDP, Coherent File Distribution Protocol.
121 Encore Expedited Remote Pro.Call.
122 SMAKYNET.
123 NTP, Network Time Protocol.
124 ANSA REX Trader.
125 Locus PC-Interface Net Map Serv.
126 Unisys Unitary Login.
127 Locus PC-Interface Conn Server.
128 GSS X License Verification.
129 PWDGEN, Password Generator Protocol.
130 cisco FNATIVE.
131 cisco TNATIVE.
132 cisco SYSMAINT.
133 STATSRV, Statistics Server.
134 INGRES-NET Service.
135 DCE endpoint resolution.
136 PROFILE Naming System.
137 NETBIOS Name Service.
138 NETBIOS Datagram Service.
139 NETBIOS Session Service.
140 EMFIS Data Service.
141 EMFIS Control Service.
142 Britton-Lee IDM.
143 IMAP, Interactive Mail Access Protocol.
144 Universal Management Architecture.
145 UAAC Protocol.
146 TP0 bridge between TCP and X.25.
147 ISO-IP.
148 Jargon.
149 AED 512 Emulation Service.
150 SQL-NET.
151 HEMS.
152 BFTP, Background File Transfer Program.
153 SGMP, Simple Gateway Monitoring Protocol.
154
155 NETSC.
156 SQL Service.
157 KNET/VM Command/Message Protocol.
158 DMSP, Distributed Mail Service Protocol.
159 NSS-Routing.
160 SGMP-TRAPS.
161 SNMP, Simple Network Management Protocol.
162 SNMP, Simple Network Management Protocol traps.
163 CMIP/TCP Manager.
164 CMIP/TCP Agent.
165 Xerox.
166 Sirius Systems.
167 NAMP.
168 RSVD.
169 SEND.
170 Network PostScript.
171 Network Innovations Multiplex.
172 Network Innovations CL/1.
173 Xyplex.
174 MAILQ.
175 VMNET.
176 GENRAD-MUX.
177 XDMCP, X Display Manager Control Protocol.
178 NextStep Window Server.
179 BGP, Border Gateway Protocol.
180 Intergraph.
181 Unify.
182 Unisys Audit SITP.
183 OCBinder.
184 OCServer.
185 Knowbot Information Service.
186 KIS Protocol.
187 Application Communication Interface.
188 Plus Five's MUMPS.
189 Queued File Transport.
190 Gateway Access Control Protocol.
191 Prospero Directory Service.
192 OSU Network Monitoring System.
193 Spider Remote Monitoring Protocol.
194 Internet Relay Chat Protocol.
195 DNSIX Network Level Module Audit.
196 DNSIX Session Mgt Module Audit Redir.
197 Directory Location Service.
198 Directory Location Service Monitor.
199 SMUX.
200 IBM System Resource Controller.
201 AppleTalk Routing Maintenance.
202 AppleTalk Name Binding.
203 AppleTalk Unused.
204 AppleTalk Echo.
205 AppleTalk Unused.
206 AppleTalk Zone Information.
207 AppleTalk Unused.
208 AppleTalk Unused.
209 The Quick Mail Transfer Protocol.
210 Z39.50.
211 Texas Instruments 914C/G Terminal.
212 ATEXSSTR.
213 IPX.
214 VM PWSCS.
215 Insignia Solutions.
216 Computer Associates Int'l License Server.
217 dBASE Unix.
218 MPP, Message Posting Protocol.
219 Unisys ARPs.
220 IMAP, Interactive Mail Access Protocol, version 3.
221 Berkeley rlogind with SPX auth.
222 Berkeley rshd with SPX auth.
223 Certificate Distribution Center.
242 Direct.
243 Survey Measurement.
244 Dayna.
245 LINK.
246 Display Systems Protocol.
247 SUBNTBCST_TFTP.
248 bhfhs.
249
-
255
256 RAP.
257 Secure Electronic Transaction.
258 Yak Winsock Personal Chat.
259 ESRO, Efficient Short Remote Operations.
260 Openport.
261 IIOP Name Service over TLS/SSL.
262 Arcisdms.
263 HDAP.
264 BGMP, Border Gateway Multicast Protocol.
265 X-Bone CTL.
266 SCSI on ST.
267 Tobit David Service Layer.
268 Tobit David Replica.
269
-
279
280 http-mgmt.
281 Personal Link.
282 Cable Port A/X.
283 rescap.
284 corerjd.
285
286 FXP-1.
287 K-BLOCK.
288
-
299
300
-
307
308 Novastor Backup.
309 EntrustTime.
310 bhmds.
311 AppleShare IP WebAdmin.
312 VSLMP.
313 Magenta Logic.
314 Opalis Robot.
315 DPSI.
316 decAuth.
317 Zannet.
318 TSP, Time Stamp Protocol.
319 PTP Event.
320 PTP General.
321 PIP.
322 RTSPS.
323 IMMP, Internet Message Mapping Protocol.
324
-
332
333 Texar Security Port.
334
-
343
344 Prospero Data Access Protocol.
345 Performance Analysis Workbench.
346 Zebra server.
347 Fatmen Server.
348 Cabletron Management Protocol.
349 mftp.
350 MATIP, Mapping of Airline Traffic over Internet Protocol, Type A.
351 MATIP, Mapping of Airline Traffic over Internet Protocol, Type B.
bhoetty.
352 DTAG.
353 NDSAUTH.
354 bh611.
355 DATEX-ASN.
356 Cloanto Net 1.
357 bhevent.
358 Shrinkwrap.
359 Tenebris Network Trace Service.
360 scoi2odialog.
361 Semantix.
362 SRS Send.
363 RSVP Tunnel.
364 Aurora CMGR.
365 DTK.
366 SMTP, Simple Mail Transfer Protocol. ODMR, On-Demand Mail Relay.
367 MortgageWare.
368 QbikGDP.
369 rpc2portmap.
370 codaauth2.
371 Clearcase.
372 ListProcessor.
373 Legent Corporation.
374 Legent Corporation.
375 Hassle.
376 Amiga Envoy Network Inquiry Proto.
377 NEC Corporation.
378 NEC Corporation.
379 TIA/EIA/IS-99 modem client.
380 TIA/EIA/IS-99 modem server.
381 HP performance data collector.
382 HP performance data managed node.
383 HP performance data alarm manager.
384 A Remote Network Server System.
385 IBM Application.
386 ASA Message Router Object Def.
387 AURP, AppleTalk Update-based Routing Protocol.
388 Unidata LDM Version 4.
389 LDAP, Lightweight Directory Access Protocol.
CLDAP, Connection-less Lightweight X.500 Directory Access Protocol.
390 UIS.
391 SynOptics SNMP Relay Port.
392 SynOptics Port Broker Port.
393 Data Interpretation System.
394 EMBL Nucleic Data Transfer.
395 NETscout Control Protocol.
396 Novell Netware over IP.
397 Multi Protocol Trans. Net.
398 Kryptolan.
399 TP2 encapsulation.
400 Oracle Secure Backup.
401 Uninterruptible Power Supply.
402 Genie Protocol.
403 decap.
404 nced.
405 ncld.
406 Interactive Mail Support Protocol.
407 Timbuktu.
408 Prospero Resource Manager System Manager.
409 Prospero Resource Manager Node Manager.
410 DEC Ladebug Remote Debug Protocol.
411 Remote MT Protocol.
412 Trap Convention Port.
413 SMSP.
414 InfoSeek.
415 BNet.
416 Silverplatter.
417 Onmux.
418 Hyper-G.
419 Ariel.
420 SMPTE.
421 Ariel.
422 Ariel.
423 IBM Operations Planning and Control Start.
424 IBM Operations Planning and Control Track.
425 ICAD.
426 smartsdp
427 SLP, Service Location Protocol.
428 OCS_CMU.
429 OCS_AMU
430 UTMPSD
431 UTMPCD
432 IASD
433 NNSP
434 Mobile IP agent.
435 Mobile IP MN.
436 DNA-CML
437 comscm
438 dsfgw
439 dasp
440 sgcp
441 decvms-sysmgt
442 cvc_hostd
443 HTTPS, HTTP over SSL/TLS.
444 SNPP, Simple Network Paging Protocol.
445 Microsoft-DS.
446 DDM-RDB
447 DDM-RFM
448 DDM-SSL
449 AS Server Mapper
450 TServer
451 Cray Network Semaphore server
452 Cray SFS config server
453 CreativeServer
454 ContentServer
455 CreativePartnr
456 macon-tcp
457 scohelp
458 apple quick time
459 ampr-rcmd
460 skronk
461 DataRampSrv
462 DataRampSrvSec
463 alpes
464 Kerberos change/set password.
465 (TCP) URL Rendesvous Directory for SSM.
(UDP) IGMP over UDP for SSM.
466 digital-vrc
467 mylex-mapd
468 Photuris.
469 Radio Control Protocol.
470 scx-proxy
471 Mondex.
472 ljk-login.
473 hybrid-pop.
474 (TCP) tn-tl-w1.
(UDP) tn-tl-w2.
475 tcpnethaspsrv.
476 tn-tl-fd1.
477 ss7ns.
478 spsc.
479 iafserver.
480 iafdbase.
481 Ph service.
482 bgs-nsi.
483 ulpnet.
484 Integra Software Management Environment.
485 Air Soft Power Burst.
486 Avian.
487 SAFT, Simple Asynchronous File Transfer.
488 gss-http.
489 nest-protocol.
490 micom-pfs.
491 go-login.
492 Transport Independent Convergence for FNA.
493 Transport Independent Convergence for FNA.
494 POV-Ray.
495 intecourier.
496 PIM-RP-DISC.
497 dantz.
498 siam.
499 ISO ILL Protocol.
500 ISAKMP.
IKE, Internet Key Exchange.
501 STMF.
502 asa-appl-proto.
503 Intrinsa.
504 citadel.
505 mailbox-lm.
506 ohimsrv.
507 crs.
508 xvttp.
509 snare.
510 FirstClass Protocol.
511 mynet-as.
512 rexec, remote process execution.
Used by mail system to notify users of new mail received.
513 Rlogin.
Maintains data bases for who's logged on a local net and the average load of the machine.
514 Syslog.
cmd like exec but automatic authentication is performed for login server.
515 LPR.
516 videotex.
517 Like tenex link but across machine - doesn't use link protocol. A rendezvous port establishes a tcp connection.
518 ntalk.
519 unixtime.
520 RIP, Routing Information Protocol.
Extended file name server.
521 RIPng.
522 ULP.
523 IBM-DB2.
524 NCP.
525 timeserver.
526 newdate.
527 Stock IXChange.
528 Customer IXChange.
529 IRC-SERV.
530 rpc.
531 chat.
532 readnews.
533 emergency broadcasts.
534 MegaMedia Admin.
535 iiop.
536 opalis-rdv.
537 Networked Media Streaming Protocol.
538 gdomap.
539 Apertus Technologies Load Determination.
540 uucpd.
541 uucp-rlogin.
542 commerce.
543 klogin.
544 krcmd.
545 appleqtcsrvr.
546 DHCPv6 client.
547 DHCPv6 server.
548 AFP over TCP.
549 IDFP.
550 new-who.
551 cybercash.
552 deviceshare.
553 pirp.
554 RTSP, Real Time Streaming Protocol.
555 dsf.
556 rfs server.
557 openvms-sysipc.
558 SDNSKMP.
559 TEEDTAP.
560 rmonitord.
561 monitor.
562 chcmd.
563 NNTP over TLS.
564 plan 9 file service.
565 whoami.
566 streettalk.
567 banyan-rpc.
568 microsoft shuttle.
569 microsoft rome.
570 demon.
571 udemon.
572 sonar.
573 banyan-vip.
574 FTP Software Agent System.
575 VEMMI, VErsatile MultiMedia Interface.
576 ipcd.
577 vnas.
578 ipdd.
579 decbsrv.
580 SNTP HEARTBEAT.
581 Bundle Discovery Protocol.
582 SCC Security.
583 Philips Video-Conferencing.
584 Key Server.
585
586 Password Change.
587 ESMTP, Extended Simple Mail Transfer Protocol.
588 CAL.
589 EyeLink.
590 TNS CML.
591 FileMaker Inc. - HTTP Alternate (see Port 80).
592 Eudora Set.
593 HTTP RPC Ep Map.
594 TPIP.
595 CAB Protocol.
596 SMSD.
597 PTC Name Service.
598 SCO Web Server Manager 3.
599 Aeolon Core Protocol.
600 Sun IPC server.
601 Syslog.
602 XML-RPC over BEEP.
603 IDXP, Intrusion Detection Exchange Protocol.
604 TUNNEL.
605 SOAP over BEEP.
606 Cray Unified Resource Manager.
607 nqs.
608 SIFT/UFT, Sender-Initiated/Unsolicited File Transfer.
609 npmp-trap.
610 npmp-local.
611 npmp-gui.
612 HMMP Indication.
613 HMMP Operation.
614 SSLshell.
615 Internet Configuration Manager.
616 SCO System Administration Server.
617 SCO Desktop Administration Server.
618 DEI-ICDA.
619 Digital EVM.
620 SCO WebServer Manager.
621 ESCP.
622 Collaborator.
623 DMTF out-of-band web services management protocol.
Aux Bus Shunt.
ASF Remote Management and Control Protocol.
624 Crypto Admin.
625 DEC DLM.
626 ASIA.
627 CKS & TIVIOLI.
628 QMQP.
629 3Com AMP3.
630 RDA.
631 IPP, Internet Printing Protocol.
632 bmpp.
633 Service Status update (Sterling Software).
634 ginad.
635 RLZ DBase.
636 ldap protocol over TLS/SSL (was sldap).
637 lanserver.
638 mcns-sec.
639 MSDP, Multicast Source Discovery Protocol.
640 entrust-sps.
641 repcmd.
642 EMSD over ESRO.
643 SANity.
644 dwr.
645 PSSC.
646 LDP, Label Distribution Protocol.
647 DHCP Failover Protocol.
648 RRP, Registry Registrar Protocol.
649 Aminet.
650 OBEX.
651 IEEE MMS.
652 DTCP, Dynamic Tunnel Configuration Protocol.
653 RepCmd.
654 AODV, Ad hoc On-Demand Distance Vector.
655 TINC.
656 SPMP.
657 RMC.
658 TenFold.
659 URL Rendezvous.
660 MacOS Server Admin.
661 HAP.
662 PFTP.
663 PureNoise.
664 DMTF out-of-band secure web services management protocol.
ASF Secure Remote Management and Control Protocol.
Secure Aux Bus.
665 Sun DR.
666 Doom, Id Software.
667 Campaign contribution campaign contribution disclosures - SDR Technologies.
668 MeComm.
669 MeRegister.
670 VACDSM-SWS.
671 VACDSM-APP.
672 VPPS-QUA.
673 CIMPLEX.
674 ACAP, Application Configuration Access Protocol.
675 DCTP.
676 VPPS Via.
677 Virtual Presence Protocol.
678 GNU Gereration Foundation NCP.
679 MRM.
680 entrust-aaas.
681 entrust-aaas.
682 XFR.
683 CORBA IIOP.
684 CORBA IIOP SSL.
685 MDC Port Mapper.
686 Hardware Control Protocol Wismar.
687 asipregistry.
688 REALM-RUSD.
689 NMAP.
690 VATP.
691 MS Exchange Routing.
692 Hyperwave-ISP.
693 connendp.
694 ha-cluster.
695 IEEE-MMS-SSL.
696 RUSHD.
697 UUIDGEN.
698 OLSR, Optimized Link State Routing.
699 Access Network.
700 EPP, Extensible Provisioning Protocol.
701 LMP, Link Management Protocol.
702 IRIS over BEEP.
703
704 errlog copy/server daemon.
705 AgentX.
706 SILC, Secure Internet Live Conferencing.
707 Borland DSJ.
708
709 Entrust Key Management Service Handler.
710 Entrust Administration Service Handler.
711 TDP, Tag Distribution Protocol.
712 TBRPF, Topology Broadcast based on Reverse-Path Forwarding.
713 IRIS over XPC.
714 IRIS over XPCS.
715 IRIS-LWZ.
716 PANA messages.
717
-
719
720 DVMP, Distance Vectored Monitoring Protocol.
SMQP, Simple Message Queue Protocol.
721 XSRP, eXtensible Service Registration Protocol.
722
723 XSTP, eXtensible Service Transfer Protocol.
724
725 XSSP, eXtensible Service Subscription Protocol.
726
727 XSLP, eXtensible Service Location Protocol.
728
729 IBM NetView DM/6000 Server/Client.
730 IBM NetView DM/6000 send TCP.
731 IBM NetView DM/6000 receive TCP.
732
-
740
741 netGW.
742 Network based Rev. Cont. Sys.
743
744 Flexible License Manager.
745
746
747 Fujitsu Device Control.
748 Russell Info Sci Calendar Manager.
749 kerberos administration.
750 kerberos version iv.
751 pump.
752 qrh.
753 rrh.
754 send
755
756
757
758 nlogin.
759 con.
760 ns.
761 rxe.
762 quotad.
763 cycleserv.
764 omserv.
765 webster.
766
767 phone.
768
769 vid.
770 cadlock.
771 rtip.
772 cycleserv2.
773 submit.
774 rpasswd.
acmaint_dbd.
775 entomb.
acmaint_transd.
776 wpages.
777 Multiling HTTP.
778
779
780 wpgs.
781
-
799
800 mdbs_daemon.
801 device.
802
-
809
810 FCP.
811
-
827
828 itm-mcell-s.
829 CMP, Certificate Management Protocols.
830 NETCONF over SSH.
831 NETCONF over BEEP.
832 NETCONF for SOAP over HTTP.
833 NETCONF for SOAP over BEEP.
834
-
846
847 dhcp-failover 2.
848 GDOI, Group Domain of Interpretation.
849
-
859
860 iSCSI.
861 OWAMP, One-way Active Measurement Protocol.
862
-
872
873 rsync.
874
-
885
886 ICL coNETion locate server.
887 ICL coNETion server info.
888 AccessBuilder.
CD Database Protocol.
889
-
899
900 OMG Initial Refs.
901 SMPNAMERES.
902 IDEAFARM-CHAT.
903 IDEAFARM-CATCH.
904
-
909
910 KINK, Kerberized Internet Negotiation of Keys.
911 xact-backup.
912 APEX relay-relay service.
913 APEX endpoint-relay service.
914
-
988
989 FTP data over TLS/SSL.
990 FTP control over TLS/SSL.
991 NAS, Netnews Administration System.
992 telnet over TLS/SSL.
993 imap4 over TLS/SSL.
994 irc over TLS/SSL.
995 pop3 over TLS/SSL (was spop3).
996 vsinet.
997 maitrd.
998 busboy.
puparp.
999 Applix ac.


Hope this will help!! :)


Regards,l

New CCNP curriculum v6 - ROUTE, SWITCH + TSHOOT Official announcements from Cisco and the CLPs

I just received the official announcement from Global Knowledge - one of the Cisco Certified Learning Partners - that the new CCNP track will be officially announced today.

Beside the already known - i.e. leaked - information some of the key facts are as follows:

• The current BSCI, BCMSN, ONT and ISWC exams will be replaced by the ROUTE, SWITCH and TSHOOT exams
• The length of the new exams will be increased to 120 minutes each
• The ROUTE and SWITCH exams contain 52 questions each, the TSHOOT exam 53 questions
• The price of the new exams will be increased up to $ 200.00 each
• The last day to test for the old exams is July 31, 2010
• The new ROUTE and SWITCH exams will be available on March 10, 2010
• The new TSHOOT exam will be available on April 30, 2010
• If you do not pass ISCW and ONT by July 31, 2010 you have to pass the new TSHOOT exam

The official announcement from Global Knowledge can be found HERE.

UPDATE #1:

FastLane and ExperTeach - the other 2 Certified Learning Partners - also updated their websites this morning [GMT+1] with the same information.
So we can indeed expect the announcement from Cisco later today, i.e. once the US wakes up.

UPDATE #2:

Cisco just updated their website with the new CCNP Certification curriculum. Of course, the CCIP Certification and CCDP Certification pages got updated as well.

Cisco also released a special CCNP Exam Combination Tool which you can use to determine which exams you have to pass in case you are in the middle of the track right now.

UPDATE #3:

Cisco has now also updated The Cisco Learning Network with lots of information about the new exams. Below a selection of the ones that I found to be most interesting:

1) Special Beta Offer for CCNP TSHOOT Exam:

This exam will initially be released as a beta exam. You can register and take the beta (#643-832) from February 16 through March 26, 2010. All details can be found HERE.

2) The Blueprints aka exam topics of the new exams (login required):

642-902 ROUTE Exam Topics (Blueprint)
642-813 SWITCH Exam Topics (Blueprint)
642-832 TSHOOT Exam Topics (Blueprint)

Please note that these links require you to login to The Cisco Learning Network to access the content. Cisco does not allow to simply copy and paste this content! So please refrain from doing so! Thanks for your kind understanding.

UPDATE #4:

The study materials for the new exams are not yet listed at Cisco Press but this should be only a matter of hours. However, based on the available information you can expect to see the following official books to be released very soon:

• CCNP ROUTE Exam Certification Guide, February 2010
• CCNP SWITCH Exam Certification Guide, February 2010
• CCNP TSHOOT Exam Certification Guide, February 2010

In addition there will be so-called Cert Kits containing Video, Flash Cards and Quick Reference Preparation Packs for each exam (expected around February - April) and finally the Official Self-Study Guides for each exam (expected around April - July).

So it seems that at least the Exam Certification Guides will be ready in time to prepare you for the new exams as soon as they are available.

UPDATE #5:

There is a nice 10 minutes presentation regarding the upcoming changes at Cisco TV. Make sure to check it out. In contains a lot of additional information.

CiscoPress just started to update their site with information regarding the upcoming CCNP certification books. In addition to the above mentioned materials they also plan to publish Portable Command Guides for each exam as before. No scheduled release dates yet but those should be added pretty soon.

UPDATE #6:

Cisco has re-released the FAQ regarding the new CCNP curriculum on their Certifications & Communities Online Support website.

There you can find a whopping 27 Instant Answers regarding the updated track. Almost every question you can think of gets answered. Make sure to check it out.


This thread got pinned and will be updated as new information becomes available.

Please refrain from opening new threads for this topic. All information regarding the new CCNP curriculum must be posted here! This thread will be monitored and cleaned up if necessary.

Regards,
Ned