cisco device operation router components rom (read-only memory)

hosts the basic commands of the router and

sometimes a limited version of the ios (internet operating system). rom is non-
volatile, meaning it is hard-coded and does not change. contains power-on
diagnostics, a bootstrap program, and operating system software.
ram (random access memory)
contains the running version of the ios and the
current running configuration. this is extremely volatile; when the router is
shutdown, anything in ram is lost. stores routing tables, arp cache, fast-switching
cache, packet buffering (shared ram), and packet hold queues.
nvram (non-volatile random access memory)
as the name implies, files can be written to this memory and will not be lost when the
system is powered down.
this is where the startup version of the router configuration is stored.
flash memory (eeprom electronic erasable programmable read only
memory)
this is where the ios version for the router is stored. it is important
when determining what version of ios to load on a router, that you ascertain how
much flash is installed. different versions of ios require more flash to be loaded.
flash memory holds the operating system image and microcode.
ways to configure a new router
by connecting to the console port and using tftp to download a configuration file that has
been created ahead of time. · by connecting to the console port and running the setup
dialog.
· by connecting to the console port and directly typing in configuration commands. ·
using bootp in conjunction with slarp/rarp to download a configuration file that has been
created ahead of time.
determine hardware configuration
the exec commands that will show hardware configuration of a cisco router are
"show hardware" and "show version"

mode prompts monitor mode rommon 1 > user mode router> privileged mode router#
global configuration mode router(config)# interface configuration mode router(config-
if)# sub-interface configuration mode router(config-subif)# line configuration mode
router(config-line)# router configuration mode router(config-router)# ipx router
configuration mode router(config-ipx-router)#
really delete files from flash when you delete a file from flash, it is not removed from
flash, and you will not
regain the space - it is simply marked for deletion. once a file is marked for
deletion, issuing the "squeeze" command will perform a function similar to a hard
drive defrag and move the files on flash to reclaim the space occupied by the
"deleted" file.
passwords things to know: · the user mode password is the only one that cannot be
created in the setup dialogue. · all passwords can be encrypted.
· a password can be set for individual lines.
· if no password is set on the vty lines there is no telnet access into this router.
· router(config)# service password-encryption encrypts all passwords in the
configuration file. procedure to recover a lost password: · reboot the router
· issue the break command in the first 60 seconds (ctrl-break)
· enter the appropriate register value (0x2142)
reboot the router again
· avoid the startup script
· copy startup to running configuration
· change the passwords
· copy running to startup configuration types of passwords: · exec used to restrict access
to the exec mode, the basic console on the router. · enable used to restrict access to the
privileged exec mode where changes to the router configuration can be made. · enable
secret similar to the enable password, but they are encrypted so they cannot be read.
setting different types of passwords: · console password used with the routers console
port. router(config)# line con 0 router(config-line)# login router(config-line)# password
{password} · auxiliary password - used for the router's auxiliary port. router(config)# line
aux 0 router(config-line)# login router(config-line)# password {password}
· virtual terminal password used for telnet sessions to router. router(config)# line vty 0 4
router(config-line)# login router(config-line)# password {password} · enable password
used when enable secret is not configured or software revision is too old. router(config)#
enable password {password}
· enable secret password encrypted password that provides enable privileges.
router(config)# enable secret {password} register values · 0x2102 default mode 0x2142
- the value used to recover passwords
debug by default, all debug information goes to the console port on a cisco router only. to

view debug messages from a vty session, you must issue the "terminal monitor"
command.
router# debug serial interface - monitors keepalives on an interface.
to reduce the impact of a debug command on the cpu of the router, use the
scheduler-interval command and be sure to use the debug command as specifically
as possible.
snmp (simple network management protocol)
snmp is a standard method for network management stations (such as ciscoworks)
to gather information about networked devices. this udp-based protocol uses mibs
(management information databases) defined for each type of device to interpret
the information provided by the snmp enabled equipment

to enable snmp on a router the command is "snmp-server community" general

networking theory osi model the osi is a common tool for conceptualizing how network
traffic is handled. in the
ccie track, we will be interested primarily in the lower three levels. just a reminder,
that you can use the old mnemonic "all people seem to need data processing" as a
way to help remember the sequence.
7. application user interface tools (such as telnet, smtp, ftp, etc.)
6. presentation encoding/decoding (such as ascii, mpeg, gif, jpeg, etc.)
5. session creating, managing and terminating presentation layer
4. transport error checking and recovery, flow control and multiplexing (tcp, spx, etc.) 3.
network routing (ip, ipx, etc.)
2. data link (llc/mac) · llc manages communications · mac manages addressing and
access to the physical layer 1. physical establish and maintain physical connectivity
cisco hierarchical internetworking model · core concentrates all traffic traversing the
network. the focus in on speed and fast switching. gigabit ethernet and a are seen here. ·
distribution control layer; aggregation of traffic, access lists, compression, encryption
and other services that provide the glue between access and core
layers. · access the point at which users join the network. vlans, wan connections, ras
services are all at this layer. connection-oriented vs. connectionless service connection-
oriented: similar to hdlc · connection establishment and termination required · sequenced,
acknowledged data delivery · built-in error recovery · sliding window flow control
connectionless: data transfer without virtual circuit · no message sequencing · no delivery
guarantee · higher layer is responsible for error recovery, flow control, and reliability
routing / switching · routing is defined as a layer-3 activity.
· bridging is defined as a layer-2 activity.
· switching is defined as a layer-2 activity. switching is often called micro- segmentation,
in that each switched port is basically its own bridged domain. routing and routed
protocols a routing protocol, such as bgp or ospf communicates between routers which
paths
to follow in order to get data delivered to desired destinations. a routed protocol, such as
ip or ipx is the method for passing data, and travels the
paths defined by the routing protocol.
reliability of protocols · tcp and llc type 2 are reliable protocols because they are layer
four protocols ip, udp, and frame relay are not reliable protocols because they are layer
three protocols 802.x protocols 802.2 link layer control (llc) 802.3 csma/cd access
method (ethernet) 802.4 token ring bus 802.5 token ring 802.6 man (metropolitan area
network) 802.7 broadband 802.8 fiber-optic lans 802.9 integrated voice & data 802.10
lan/man security 802.11 wireless 802.12 vganylan passive interface when enabled on an
interface this command allows the interface to hear routing
updates, but not repeat them. this helps to control routing updates.
example: router(config-router)# passive-interface s0 connectivity (diagram a-1)
bridged environment (refer to diagram a-1) in a bridged environment, a cisco router
will not modify the layer-2 mac address of
a frame when bridging. in other words, a packet retains the true source and
destination mac addresses when crossing a bridge.
for example, if in the diagram above devices b and c were bridges, packets sent
from host a to host b would have the source mac address of host a's ethernet
adapter and the destination mac address of host b's ethernet adapter, regardless of
what segment they were passing through.
if a packet were to be lost anywhere between host a and host d, the originator
would rebroadcast.
routed environment (refer to diagram a-1) in a routed environment, when a host sends
a packet it has the source mac address
of either the originating host (if on the first segment) or the last router port it was
processed by. it would have the destination mac address of the next hop router port
or the destination host, if on the final segment. in other words, a host sending a packet to
a router for processing to a remote
destination will have the routers local port as a destination address; a host receiving
a packet from the router will see a source address of the local router port. for example, if
in the devices in diagram a-1 were routers: · packet from host a to host d will have source
mac address of host a and destination mac address of router b's local ethernet port on
segment 1. · packet from host a to host d will have source mac address of router b's serial
port and destination mac address of router c's local serial port on
segment 2. · packet from host a to host d will have source mac address of router c's
ethernet port and a destination mac address of host d on segment 3.
13 if a packet sent from host a to host d were to be lost: · on segment 1, host a would
rebroadcast
· on segment 2, router b would rebroadcast
· on segment 3, router c would rebroadcast bridging & lan switching a view of bridging
when non-routable protocols, such as netbeui, lat or sna were developed all
devices on a network resided locally. as networks matured and bridges were
introduced to segment lans there was the need for these devices to communicate
across networks, especially wan links. because these protocols did not have the
mechanisms to allow this connectivity, bridging techniques were developed to allow
the communication between devices at the data link layer (layer 2 of the osi
model).
by default, bridging is disabled on all cisco routers. however, these services are still
an important component of the real-world networks you will be asked to deal with in
your professional life. for the purposes of the current discussion, you will also need
to know them for the ccie certification exams, both written and lab.
keep in mind that many non-routable protocols, most importantly sna, are very
time sensitive, and delays can cause loss of data or session connectivity. it is also
important to understand that bridging techniques are broadcast intensive, and that
this can flood slower wan links. bridging techniques
transparent bridging (tb) as the name implies, this type of bridging is transparent to the
end devices. the end devices are unaware that when they
communicate they are not local to one another. this functionality is not enabled by
default on cisco routers, but can be turned on when needed. when a device wishes to
communicate, it will send out a broadcast to search for the
requested destination address. when a transparent bridge sees the first broadcast
from a device, it extracts the mac address from the packet and enters it into its
forwarding table, the list of devices on each interface. this process of determining
what devices exist on each of the bridge's ports is called learning.
if the bridge receives a broadcast with a destination address that is in its forwarding
table it forwards the broadcast only to that one interface. if it is not in the table, it
repeats the broadcast out of all of its interfaces (except the one on which it was
received). this process is called flooding.
source-route bridging (srb)
source routing is called that because instead of an intermediate device determining a path,
the originating device creates
its own.
routing information fields (rif) are used to define paths for srb frames to traverse
a network. they are easy to read if you understand their function. for the current
discussion it's important that you understand how to understand how a rif works.
later we'll come back to how to rip `um up and read `um.
when an sna device needs to access a remote unit, it sends out a test frame that
attempts to find the destination. you can think of this as a broadcast in the ip
world; it isn't, but that will help you to conceptualize. if the destination is not found, the
source device sends out a single-route or all-
routes explorer frame. any bridges that the frame comes across in its travels add
their local bridge and ring numbers to the rif. eventually the frame either finds its
target or dies on the vine. ibm bridges support 8 rings and 7 bridges; ieee 802.5
bridges support 14 bridges and 13 rings.
once one of the explorer frames finds the destination, it returns to its creator to
announce its success. if multiple frames return, the source device takes the route of
the first frame to return, assuming this is the best path. think of it as a race in a
maze; the first one to grab the cheese and get home first, wins.
ripping up a rif
this will seem complicated, but once you understand how rifs are defined, simple
practice will drive home the necessary techniques the first bit of the first byte of the
source address is the routing information
indicator (rii), which is exactly what it sounds like; it indicates that what follows is a
rif. if this bit is a 1, the frame is a rif; if the bit is a 0, it is not.
here are the component parts of the first 2 bytes of a rif, called the rcf (routing
control field):
1. the first 3 bits define what kind of rif is being examined: · 0xx single route frame · 10x
all-routes explorer frame · 11x spanning explorer frame 2. the next 5 bits show the
length of the rif. this indicates how many bytes of bridge/ring numbers follow. 3. the next
single bit shows direction: · 0 read from left-to-right · 1 read from right-to-left\
15 4. the last 3 bits indicate the maximum frame length · 000 up to 512 bytes · 001 up to
1,500 bytes · 010 up to 2,052 bytes · 011 up to 4,472 bytes · 100 up to 8,144 bytes ·
101 up to 11,407 bytes · 110 up to 17,800 bytes · 111 broadcast frame
5. the last four bits are not relevant. they are reserved for future use. here's an example of
a rif: 0810.0011.0023.0040
translating the first two bytes (0810) to binary gives us: 0000.1000.0001.0000
rip it up to define: type rif length direction frame length not used 000 01000 0 000 0000
from this we know: · the rif type is: single route frame
· the rif length: 8 bytes (01000 binary = 8 decimal)
· direction to read the rif: right-to-left
· the maximum frame length: up to 512 bytes
the rest of the rif is called the rdf (route descriptor field) and reading it is easy.
the first three digits of each two-byte grouping are the ring number (in
hexadecimal). the last digit is the bridge number (again, in hex). a zero in the
bridge number designation indicates that the destination ring has been reached.
notice that since only four bits are used for the ring number, and zero is already
taken, the only bridge numbers available are hex 1 through f (1 to 15 in decimal).
looking at our example again (0810.0011.0023.0040), (remember that the 0x
indicates that the number that follows is in hex) we find that the path is: · ring 0x1 to
bridge 0x1
· ring 0x2 to bridge 0x3
· ring 0x4 to the destination
16 taking another example: 0a10.0021.00b1.0101.0020
translating the first two bytes (0a10) to binary gives us: 0000.1010.0001.0000

rip it up to define: type rif length direction frame length not used 000 01010 0 001 0000
from this we know: · the rif type is: single-route
· the rif length: 10 bytes (01010 binary = 10 decimal)
· direction to read the rif: right-to-left
· the maximum frame length: up to 512 bytes
following the rest of the rif · ring 0x2 to bridge 0x1
· ring 0xb to bridge 0x1
· ring 0x10 to bridge 0x1
· ring 0x2 to the destination tricky rif (common errors when reviewing rifs)
the apples-to-oranges rule : if you see 0x before a number, remember that what follows
is a hexadecimal. for example, what's the difference between ring
0x14 and ring 14? since decimal 14 is 0xe, they're obviously not the same ring
designation. the nice-try rule: srb only runs on token ring networks, so ethernet devices
do not use rifs. if you are looking at a network diagram and see that one of the
hosts is on an ethernet segment, remember that rifs are irrelevant. the roadblock rule: in
a dlsw environment the rif is terminated at the dlsw router (the definition of dlsw occurs
later in this document).
source-route transparent bridging (srt)
since you now have an understanding of both tb and srb, this next technique will
come easy. an srt bridge looks at each frame to see if it finds a rif (looking for the
rii). if there's an rii, the frame is processed like srb; if not, like tb. some
devices, such as windows 95 workstations do not support rifs. srt allows them to
communicate through bridges between lan segments. this all takes place on token
ring devices. the next technique will address ethernet translations.
source-route translational bridging (sr/tlb)
this cisco proprietary bridging technique allows bridging to take place between
ethernet domains and token ring domains. ethernet frames are not capable of
supporting rifs. this bridging method, when enabled on cisco routers, handles the
conversion from ethernet frames to token ring frames (bit ordering); adjusts the
mtu sizes (default for token ring is 4,464 bytes, ethernet 1.500 bytes); and adds
and removes rifs, as necessary. to the token ring devices the ethernet segment
looks like an srb domain using a pseudo ring. remote-source route bridging (rsrb) an
advanced bridging technique that allows legacy protocols, predominantly sna, to
communicate over large bridged environments using ip tunnels as a transport
mechanism.
frames from token ring networks are encapsulated and sent over the ip network.
the methods of encapsulation are: · direct encapsulation this method uses hdlc (high-
level data link control) and adds little overhead, but lacks reliability. this is usually used
over a
single network connection between two routers attached to token ring
networks. · fast-sequenced transport (fst) this method uses ip encapsulation, which adds
some overhead, but is still connectionless. · transport control protocol (tcp) this method
uses tcp connection, which adds significant overhead, but ensures reliable transport.
the ip network being traversed is considered one hop, using the concept of a virtual
ring. though rifs pass through the network, they are calculated as if the entire ip
network is one hop using this concept, and all acknowledgements are local,
conserving valuable wan bandwidth.
ethernet networks can be traversed as long as the local router is running sr/tlb.
data-link switching plus (dlsw+)
dlsw was developed as an advanced tool for the transport of sna and other non-
routable protocols over ip backbones. dlsw+ is cisco's enhanced version of dlsw,
and provides additional functionality over previous versions. dlsw+ has more
options and greater functionality then rsrb.
the methods of encapsulation include: · direct encapsulation this method uses hdlc (high-
level data link control) and adds little overhead, but lacks reliability. this is usually used
over a
single network connection between two routers attached to token ring
networks. (same as rsrb). · fast-sequenced transport (fts) this method uses ip
encapsulation, which adds some overhead, but is still connectionless. (same as rsrb). ·
transport control protocol (tcp) this method uses tcp connection, which adds significant
overhead, but ensures reliable transport. (same as rsrb). · frame relay rifs are generally
terminated at the dlsw router. dlsw+ can support ethernet
without sr/tlb being loaded. additional tools available with dlsw+ include: dynamic peers,
peers on demand,
backup peers and the ability to load balance connections.
encapsulated bridging used to bridge over an ip backbone or fddi backbone.
irb (integrated routing and bridging) a bvi (bridged virtual interface) is created that
acts as a member of a bridge-group
to allow traffic to be routed. the bvi number must match the bridge-group number. crb
(concurrent routing and bridging) concurrent routing of one group of interfaces, while
bridging another. lan switching all nodes on an ethernet network can transmit at the same
time, so the more nodes
you have the greater the possibility of collisions happening, which can slow the
network down.
lan segmentation: breaking up the collision domains by decreasing the number of
workstations per segment.
switching examines mac address. works like a massive multiport bridge. switching
types: · store-and-forward copies entire frame into buffer, checks for crc errors. higher
latency. used by catalyst 5000 switches · cut-through reads only the destination address
into buffer, and forwards immediately. low latency
spanning tree and root bridge developed to prevent routing loops. the sta (spanning-tree
algorithm) is used by
the stp (spanning tree protocol) to calculate a loop-free network topology. · there is one
root bridge for ethernet and switching environments.
· there is one root bridge per vlan, with 1 for all vlans.
· route bridge calculation is determined by lowest mac address. vlan (virtual lan)
broadcast domains defined on cisco switches. since each vlan is a separate
domain, routing must be enabled between them if data is to be passed. if multiple
vlans exist on a switch, a trunk can be setup on a fast or gigabit ethernet port to
pass the separated data between network devices. a trunk passes data from device
to device; it does not route data between vlans. trunking encapsulations include: · isl
used with ethernet, and is cisco proprietary
· 802.1q used with ethernet and is ieee standard
vtp (vlan transport protocol) vlans definitions can span switches. vtp is the method for
communicating these
definitions. switches can be defined as: · server listens to, stores and broadcasts vlan
configurations. can create and delete vlans. · client listens to configurations. can assign
ports to participating vlans.
· transparent forwards vtp traffic, but doesn't participate in the vlans.
cdp (cisco discovery protocol) a proprietary data link layer protocol used between cisco
devices to pass
information about local conditions. cdp uses a data-link, multicast address with no
protocol id or network layer field, and cannot be filtered.
the only way to prevent their being passed is to configure "no cdp enable" on those
interfaces on which you do not want to run cdp. you can configure a mac-layer filter
to deny a multicast address as an alternative method to block these packets.
internet protocol (ip) ip is a layer-3 routed protocol that provides addressing,
fragmentation and
reassembly. the minimum and maximum packet headers are 20 and 24 bytes,
respectively. an ip address is 32 bits long, and the network and host sections are defined
by the
subnet mast associate with the address.
an ip address can be bound to a host name on a router using the "ip host" command
example: router(config)# ip host my-example 10.10.10.1 10.10.10.2 binds name
to both addresses
ip routing protocols · static routes · ospf · isis · eigrp · rip · igrp common ip ports 20/21
ftp 23 telnet 25 smtp 37 time service 49 tacacs 53 dns 68 bootp client.21 67 bootp server
69 tftp 161 snmp dhcp (dynamic host configuration protocol) to get away from
statically configuring workstations addresses (which is a royal pain
in the tuchis), a dhcp server can be configured which will allocate addresses
dynamically. to configure a router to pass bootp packets (dhcp requests) you can use the
"ip helper-address x.x.x.x" command.
nat (network address translation) used to translate one set of ip network numbers to
another. the primary use for nating is to translate external valid ip addresses to internal
private addresses when connecting a network to the internet. it can also be used to
temporarily merge two networks that have different addressing schemes.
addressing issues
cidr - classless inter-domain routing, cidr used by bgp ver4. route summarization
reducing the number of networks being advertised between routers simplifies the
routing table, reduces memory and cpu requirements, and makes the network more
logical. this results in enhancing network performance and reclaiming bandwidth
that would otherwise be used to pass routes back and forth.
access lists used to permit or deny traffic based on the source network/subnet/host
address.
things to know: · the wildcard mask, which looks like a reversed subnet mask, defines
which bits of the address are used for the access list decision-making process. · lists are
processed top-down. in other words, the first matching rule preempts further processing. ·
only one access list is allowed per port/per direction/per protocol.remember that there is
an implicit deny at the end of all access lists. · the last configured line should always be a
permit statement. · standard lists will most likely be placed close to the destination. ·
extended lists will most likely be placed close to the source. · if the access-group
command is configured on an interface and there is no corresponding access-list created,
the command will be executed and permit
all traffic in and out. · an access class limits vty (telnet) access. · a distribution list filters
incoming or outgoing routing updates.
access lists numbers 1-99 ip standard 100-199 extended ip 200-299 protocol type-code
300-399 decnet 400-499 xns standard 500-599 xns extended 600-699 appletalk 700-799
48-bit mac address 800-899 ipx standard 900-999 ipx extended 1000-1099 ipx sap 1100-
1199 extended 48-bit mac
address 1200-1299 ipx summary address hsrp (hot standby routing protocol) provides
a means of having two default gateways to protect against an equipment
failure locking out a group of users from the wider internetwork.
the default priority for each router is 100, but can be change to give one priority as
the most likely default gateway (if say, one unit were faster than another).
ip routing protocols methods for avoiding routing loops
holddowns learned routes are held incommunicado for a period of time to prevent
updates advertising networks that are misbehaving. triggered updates configuring
routing updates to occur after a triggering event, such as a topology change. this allows
quicker convergence. split horizon if a router has received a route advertisement from
another router, it will not re-advertise it back to the sending router. think of this as a
sphincter - things are not sent back to where they came from (gross, but you won't
forget it, and that's the point). poison reverse similar to split horizon, but instead of
ignoring the update, the route is advertised back to the originating interface as a poisoned
reverse update.
the originating router gets its own route back, but with the time-to-live field
exceeded, so the route is removed from the table. when the routers re-converge,
the holddown timers have expired. this helps to more quickly clear bad routes from
the list being passed back and forth between the routers.
administrative distance determines the level of trust each routing protocol will be given
when a route is
advertised from more than one. the primary ad's are: directly connected 0 static 1 ebgp 20
eigrp (internal) 90 igrp 100 ospf 110 isis 115 rip 120 egp 140 eigrp (external) 170 ibgp
200
bgp local 200 unknown 255
rip there are two versions of rip - version 1 and 2. ripv2 is classless and supports a
variable subnet mask. both use hop count as the only metric and have a time to live
of 15 hops. a hop is basically one pass through a router. updates include the entire
routing table, and are sent out every 30 seconds.
rip requires neither an as or process id number.
example: router(config)# router rip configuring a default route in rip:
example: router(config)# ip route 0.0.0.0 0.0.0.0 10.10.10.1
ospf (open shortest path first)
ospf areas types: · backbone (transit area) - always labeled area "0", it accepts all lsas
and is used to connect multiple areas. all other areas must connect to this area in
order to exchange and route information. when interconnecting multiple
areas, the backbone area is the central entity to which all other areas must
connect. · standard - accepts internal and external lsas and also summary information.
· stub - refers to an area that does not accept type-5 lsas to learn of external ass. if routers
need to route to networks outside the autonomous system,
they use a default route (0.0.0.0). · totally stub - further reduces routing tables by
blocking external type-5 lsas and summary (type-3-and-4) lsas. intra-area routes and the
default of
0.0.0.0 are the only routes known to this area. cisco proprietary. peer relationships: ospf
hello packet information must be the same on all routers in an area for peering
relationships to be formed. this information includes: · hello/dead interval · area id ·
authentication password · stub area flag
router types: · internal router (lsa type 1 or 2) routers that have all their interfaces in the
same area. they have identical link-state databases and run single copies
of the routing algorithm. · backbone routers (lsa type 1 or 2) routers that have at least
one interface connected to area 0. · area border router (lsa type 3 or 4) routers that have
interfaces attached to multiple areas. they maintain separate link-state databases for each
area. · autonomous system boundary router (lsa type 5) routers that have at least one
interface into an external internetwork, such as a non-ospf
network. these routers can redistribute non-ospf network information to
and from an ospf network.
connection to area 0 - the main dictate in ospf is that multiple areas all connect directly
to the backbone area. the connection to the backbone area is via
an abr, which is resident in both areas and holds a full topological database for each
area. a remote network can connect to area 0 via a virtual link, essentially a tunnel
through the abr in the intermediate area. from the viewpoint of ospf, it has a
direct connection. packets designated to a different as (autonomous system) are
forwarded to an abr,
which sends the packet through the backbone area (area 0) to the destination
network abr, which forwards it to the appropriate host. all packets that pass
between ass must pass through the backbone area when being forwarded from one
area to another. the abrs have the responsibility for maintaining the routing
information between areas.
to set a designated router in an ospf network, you can set the priority or use the
router with the highest loopback address. setting the priority to 0 makes the router
ineligible to become the dr. to make an ospf router the designated router, set the
priority with the highest value: example: router(config)# ip ospf priority 100
recalculating the database: · calculate routes within the local as using type-1 and type-2
lsas.
· calculate routes to other ass (inter-area routes) using type-3 and type-4 summary lsas.
remember that a totally stubby area will not accept
summary lsas. · calculate routes to external networks using type-5 lsas. remember that
stub and totally stubby areas will not accept autonomous system lsas.
stub and totally stubby area similarities: · inter-area routing is based on a default route
(0.0.0.0).
· the backbone area cannot be a stub area.
· there can only be one exit point for a stub or totally stubby area - a single abr. · routers
within the area must be configured as stub routers or they will not form neighbor
adjacencies. · the area cannot be used for a transit area for virtual links to the backbone.
· an asbr cannot be internal to a stub area.
· typically used in a hub and spoke topology, with the spokes being remote offices set-up
as stub or totally stubby areas. stub and totally stubby area differences: · both reduce
the size of routing tables, although more so with totally stubby areas. · both will not
accept type-5 (autonomous system entries), and totally stubby will also not accept
summary lsas either (type-3 and type-4). · totally stubby is cisco proprietary.
· totally stubby area is preferable, since it increases stability and scalability while
reducing the routing information that must be maintained. remember
that you cannot use totally stubby areas if there is a mixture of cisco and
non-cisco routers. lsa types: · router link entry - this is a type 1 lsa. broadcast only in a
specific area. contains all the default link state information. generated by each router for
each area to which it belongs. it describes the states of the router's link to
the area. these are only flooded within a particular area. the link status and
cost are two of the descriptors provided. · network entry - this is a type 2 lsa. multicast to
all area routers in a multi- access network by the dr (designated router). contains network
specific
information. they describe the set of routers attached to a particular network
and are flooded only within the area that contains the network. · summary entry - type 3
lsas have route information for the internal networks and are sent to the backbone routers.
type 4 lsas have information about the asbrs. this information is broadcast by the abr, and
it will reach
all the backbone routers. · autonomous system entry - this is a type 5 lsa. it come from the
asbr and has information relating to the external networks.
no special commands are required to turn a router into an abr or asbr. the router
takes on this role by virtue of the areas to which it is connected. as a reminder, the
basic ospf configuration steps are as follows and you would simply add another
network statement for the abr or asbr to cover another area.
to configure ospf, do the following: 1. enable global configuration mode
2. enable ospf on the abr or asbr router 3. identify the ip networks and their areas enable
ospf on the router router(config)# router ospf process-id
remember that ospf has a process id (bgp, eigrp and igrp have as numbers; rip
requires neither)
example: router (config)# router ospf 1 identify which ip networks on the router are
part of the ospf
network router(config-router)# network address wildcard-mask area area-id
configuring stub and totally stubby areas (remember that an asbr cannot be internal
to a stub area) configure a stub network
router(config-router)# area area-id stub
configure a totally stub network router(config-router)# area area-id stub no-summary
bgp (border gateway protocol) bgp is the routing protocol of the internet. it comes in
two flavors, internal and
external.
when to use bgp: · connecting to two or more isps. · multi-homing network that connects
to more than one as. · when you're a monstrously huge isp. attributes of bgp · routers are
considered to be peers or neighbors whenever they open up a tcp session to exchange
routing information. · when routers communicate for the first time, they exchange their
entire routing table. from then on, they send only incremental updates. · uses tcp as its
transport protocol, via port 179. configuring bgp enable bgp using a local bgp as number
assigned by internic:
router(config)# router bgp <as-number>

remember that bgp, eigrp and igrp have as numbers (ospf has a process id, rip
requires neither). example: router (config)# router bgp 1

all networks you want to advertise:

router(config)# network <network-number>

specify bgp neighbors and peers (peers use the local bgp as-number):
router(config)# neighbor <address> remote-as <as-number>

clear the bgp information when you make a bgp configuration

change: router# clear ip bgp *.

path selection: bgp will select one path as the best path. this path is put into the bgp
routing table
and then propagated to its neighbors. the criteria for selecting the path for a
destination is: · if the path specifies a next hop that is not accessible the update is
dropped.
the path with the largest weight is preferred.
· if the weights are the same, the path with larger local preference is preferred.
· if the local preference is the same, then prefer the path that originated on this router. · if
no route originated on this router, then prefer the one with shortest as-path. · if they have
the same as_path, then prefer the path with the lowest origin path. · if the origin codes are
the same, then prefer the path with the lowest med.
· if the med is the same, then prefer an external path to an internal path.
· if these are the same, then prefer a path through the closest igp (interior gateway
protocol) neighbor. · lastly, prefer path with the lowest ip address, as specified by the bgp
router id. three ways to set the weight of updates · access lists
· neighbor weight command
· route map bgp peering functions
a bgp peer group is a defined group of bgp neighbors that are configured to share
the same update policies. instead of defining the same policies for each individual
neighbor, you define a peer group name and assign policies to the peer group itself.
ibgp · exchanges information within the same as between routers.
· is more flexible, scalable, and more efficient for controlling the exchange of information
within an as. · shows a consistent view of the as to external neighbors.

ebgp · used when routers belong to different ass and exchange bgp updates. · bgp
synchronization rule:
if an as provides transit service to another as, then bgp should not
advertise the route until all of the routers within this as have learned
the route through the igp. · when to disable synchronization: o your as does not transfer
traffic from one as to another. o all the transit routers on your as are running bgp. bgp
synchronization bgp must be synchronized with the igp (interior gateway protocol, such
as ospf or
eigrp). to do this it waits until the igp has propagated routing information across
the autonomous system before advertising transit routes to other ass. scalability
problems associated with internal bgp autonomous systems consisting of hundreds of
routing nodes can pose a serious
routing management problem for network administrators. there are two good
methods for dealing with this situation; confederations and route reflectors.
confederations confederations eliminate the need to fully mesh bgp communications by
splitting a
single as into what amount to sub-as's and using ebgp between them; although to
external as's the entire confederation grouping looks like a single as. route reflectors
defined central points of distribution for routers within an as. in other words, it
receives data and distributes it to other routers. this eliminates the need for a fully
meshed bgp environment. policy routing policy routing is a means of controlling routes.
it relies on the source, or source and
destination, of traffic rather than destination alone. policy routing can be used to
control traffic inside an as as well as between ass. policy routing is a glorified form
of static routing, and has many of the same types of problems. route dampening policy a
bgp feature that attempts to minimize the propagation of flapping routes (up,
down, up, down, etc.) across an internetwork. penalties are assigned for each flap
and when the accumulated penalty reaches a specified limit, bgp suppresses further
advertisement of that route, even if it is back up. the accumulated penalty is
reduced over time and eventually the route is trusted again.
eigrp (enhanced interior gateway routing protocol) eigrp is a stable and scalable cisco
proprietary protocol that combines the
advantages of link state and distance vector routing protocols. it supports automatic
route summarization and vlsm addressing. eigrp was designed to overcome scaling
limitations of igrp. this was achieved by
implementing: · the diffusing update algorithm (dual)
· loop-free networks
· incremental updates
· the holding of information about neighbors as opposed to the entire network types of
successors · successor - a route selected as the primary route to use to reach a destination.
successors are the entries kept in the routing table. · feasible successor - a backup route.
multiple feasible successors for a destination can be retained, kept in topology table.
features of eigrp · neighbor discovery/recovery: routers dynamically learn of other
routers on their directly attached networks by sending a 'hello packet'. as long as the
neighbor receives these packets the router is assumed to be 'alive'. · reliable transport:
ordered delivery of eigrp packets to neighbors is guaranteed. for better efficiency, reliable
transport is provided only when it is
needed. · dual (diffusing update algorithm): tracks all the routes advertised by all
neighbors. dual will use the metric to select an efficient path. it selects
routes to be inserted into the routing table based on feasible successors. · protocol
dependent modules: these are responsible for the network layer. the ipx eigrp module is
responsible for sending and receiving eigrp packets
that are encapsulated in ipx. tables neighbor table the current state of all the router's
immediately adjacent
neighbors.
topology table - this table is maintained by the protocol dependent modules and is
used by dual. it has all the destinations advertised by the neighbor routers.
routing table - eigrp chooses the best (successor) routes to a destination from the
topology table and places these routes in the routing table. the routing table
contains: · how the route was found
· destination network address and the subnet mask in prefix format
· administrative distance: this is the metric or cost from the neighbor advertising that
particular route · metric distance: this is the cost or the metric from the router
· the address of the next hop
· how old the route is
· outbound interface designation choosing routes dual selects primary and backup routes
based on the composite metric and ensures
that the selected routes are loop free. the primary routes are then moved to a
routing table. the rest (up to 6) are stored in the topology table.
eigrp uses the same composite metric as igrp to determine the best path. the
default criteria used are: · bandwidth - the smallest bandwidth cost between source and
destination
· delay - cumulative interface delay along the path
· reliability - worst reliability between source and destination based on keepalives · load -
load on a link between source and destination based on bits per second on its worst link ·
mtu - the smallest maximum transition unit configure enhanced igrp configure eigrp for
ip enable eigrp and define the autonomous system
router(config)# router eigrp autonomous-system-number
remember that bgp, eigrp and igrp have as numbers (ospf has a process id, rip
requires neither). example: router (config)# router eigrp 1
indicate which networks are part of the eigrp autonomous system
router(config-router)# network network-number

define bandwidth of a link router(config-if)# bandwidth kilobits

desktop protocols ipx (internet packet exchange) ipx is novell's network layer
protocol. an ipx address consists of two parts, the
network id followed by a host id taken from the mac address of the device.
the default cisco encapsulation type are: · ethernet - novell-ether, the novell-specific
version of ieee 802.2 standard
· token ring sap
· fddi snap

other ethernet encapsulation types and their cisco

equivalents. novell frame type cisco ios encapsulation name ethernet_ii arpa
ethernet_802.2 sap ethernet_802.3 novell-ether ethernet_snap snap
things to know: · the cisco router does not forward sap broadcasts, but constructs its own
sap table and broadcasts that every 60 seconds (by default). · only one encapsulation type
is allowed per network. you can have several networks running on the same wire, but
they must have different network
addresses. · the ipx address is 80 bits long; 32 for network bits, 48 for host bits.
· to load balance you must use the "ipx maximum-paths {number}" command and all
parallel paths must have the same tick count and the same hop counts
as the tick and hop counts are used by ipx as a metric.
to configure ipx routing you must: 1. enable ipx routing
2. assign ipx network numbers to interfaces
example: router(config)# ipx routing
router(config)# interface e0
router(config-if)#ipx network badbed (network name in hexadecimal) routing ipx ipx
can use these routing protocols: · static routes · ipx rip similar to ip rip · ipx eigrp the ipx
version of cisco's proprietary routing protocols (see later in this document) · ipx nlsp an
ipx link-state routing protocol · ipxwan - a protocol that negotiates end-to-end options for
new links before ipx traffic can traverse the wan link ipx split horizon is not supported in
any of the ipx feature sets ipx supports load balancing; though not default, it must be
configured
sap (service advertisement protocol) used when a server needs to advertise its
availability. sap updates can carry a
maximum default of seven services.
sap entries are dependent on having a routing table entry. if a sap entry has no
routing table reference, it will not be sent.
appletalk the proprietary protocol stack developed by apple computer. designed to be
easy
to use for the end-user, it has often been seen as the bane of the network engineer.
besides being complicated to configure, it is very chatty (a bandwidth hog).
appletalk can run over most physical media: · ethertalk = running over ethernet ·
tokentalk = running over token ring · fdditalk = running over, you guessed it, fddi
there are two versions of appletalk: · phase 1 a limit of 254 nodes on a network and non-
extended networks.
· phase 2 created in 1989, overcomes the 254-node limit and runs over extended
networks. cable ranges were added with a numbering scheme that
allows sequential network numbers acting as a single network. appletalk protocols · ddp
(datagram delivery protocol) layer 3 protocol. appletalk equivalent to ip or ipx. · aarp
(appletalk address resolution protocol) equivalent to dhcp in the ip world. · rp (routing
table maintenance protocol) a distance vector routing protocol in which routes are
exchanged only with immediate neighboring
routers. sends routing table information every 10 seconds. · aurp (appletalk update-based
routing protocol) an extension of rp that enables tunneling of appletalk traffic through ip
networks using
external routers that counts as one hop. sends routing table information
every 30 seconds. · appletalk eigrp a version of the cisco proprietary routing protocol for
appletalk. addressing appletalk addresses are made up of 16-bit network numbers, 8-bit
node numbers,
and 8-bit socket numbers.
zone a logical grouping of appletalk nodes.
multicasting pim (protocol independent multicast) used to forward multicast packets
through a
network.
other important multicast protocols: · igmp (internet group management protocol)
standard protocol to manage if multicast transmissions are passed to routed ports. one of
the problems
with this is if a vlan on a switch is set to receive, all the workstations on that
vlan will get the multicast stream. · cgmp (cisco group management protocol) cisco
proprietary protocols to control the flow of multicast streams to individual vlan port
members. solves
the problem sited above. requires igmp to be running on the router. performance
management queuing methods
weighted fair queuing (wfq) most basic queuing option that gives high- volume traffic a
lower priority than lower-volume traffic. for example, a time
sensitive sna conversation would have a higher priority then a file transfer where
latencies will probably not be noticed. wfq is enabled by default on all cisco routers
with link speeds of less than e1 (2.048mb). priority queuing provides the software tools
to define a hierarchy of need between different types of traffic. there are four types of
queues; high, medium,
normal and low. you can configure up to four of each type on a router, for a total of
16 queues. unless otherwise defined, all traffic is normal. the person who
configures that queue can determine higher or lower levels of priority for different
types of traffic based on protocol or port number and data passing through the
router. medium queue traffic will not be passed until high queue has been cleared;
the normal queue traffic will not be passed until medium queue traffic has been
cleared; etc. this can create a situation where a higher-level queue can monopolize
a link to the exclusion of lower level data and packets will be dropped.
custom queuing 16 queues are configured that operate in a round-robin fashion. each
queue is allocated 1,500 bytes by default, although this can be changed. when the
appropriate number of bytes has been sent, the next queue is
addressed. if the byte count has been reached and a packet has not been
completely sent, it will continue to be sent; a packet will not be fragmented. in this
way it is possible to allocate a percentage of the bandwidth to a specific protocol. for
example, 50% of the bandwidth is reserved for ip, 25% for ipx and the remainder
for miscellaneous traffic. because of the nature of custom queuing, no one queue
can monopolize the link to the exclusion of other queues. wan serial line conditions: ·
serial 0 line is down, line protocol is down - no cable or modem is connected. · serial 0
line is up, line protocol is up - the wan service is working fine and keepalives from the
remote site are being sent and received. · serial 0 line is up, line protocol is down - a cable
is plugged into the router, but no keepalives are being received from the remote router. ·
serial 0 is administratively down, line protocol is down - the interface has to have been
enabled by the administrator.
isdn provides digital service that runs over existing telephone networks. normally used to

support applications requiring high-speed voice, video, and data communications for
home users, remote offices, etc. protocols standards · e specifies isdn on existing
telephone technology. · i specify concepts, terminology and services. · q specifies
switching and signaling. graphic 2
te1---|---s/t-----nt1---u---lt---v---et
|
te2---r---ta--| equipment · ta terminal adapter converts from rs-232, v.35, and other
signals into bri. te1|2 - terminal equipment 1 (integrated ta, understands isdn) or 2 (needs
ta, predates isdn). · nt1 - network termination type 1 equipment that connects the
subscription 4 wires to the 2 wire local loop. · nt2 network termination type 1 equipment
that performs protocol functions of the data link and network layers. · lt local termination
portion of the local exchange that terminates the local loop. · et exchange termination
portion of the exchange that communicates with the isdn components.
reference points · r reference points define the hand-off from non-isdn equipment and
the ta.
· s reference points define hand-off from user terminals to an nt2.
· t reference points define hand-off between nt1 and nt2.
· u reference points define hand-off between nt1 and line-termination equipment in a
carrier network. (only us/japan, where nt1 not provided by
carrier). channels · b(earer) channel: used for data transfer (voice or data).
· d(ata) channel: used for control/signaling information using lapd. types of equipment ·
cpe customer premise equipment (on-site).
· dce data communications equipment. the devices and connections that make up the
network end of the user-to-network interface. · dte data terminal equipment. the devices
and connections that make up the user end of the user-to-network interface. terminals,
pcs, and routers
would be examples. flavors of isdn · bri 2b /1d (d = 16kb)
· pri (t1) 23b / 1d (d = 64kb)
· e1 (europe) 30b / 1d (d = 64kb)
things to know · encapsulation can be ppp, hdlc or lapd, with the default encapsulation
method being hdlc. chap authentication is associated with ppp. · a spid is similar to a
telephone number and is provided by telco. isdn switch types · basic-5ess at&t basic rate
switches (usa)
· basic-dms100 nt dms-100 (north america)
· basic-nil national isdn-1 (north america)
· basic-itr6 german itr6 isdn switches
· basic-nwnet3 norwegian net3 switches
· basic-nznet3 new zealand net3 switches
· basic-ts013 - australian ts013 switches
· basic-net3 switch type for net3 in uk and europe
· ntt ntt isdn switch (japan)
· vn3 french vn3 isdn switches
· none no specific switch specified frame-relay frame-relay is a simple and streamlined
layer2, connection-oriented access protocol,
meaning it only defines signaling and data formats between the dte and the frame
relay switch. it is closely related to x.25, but without the error correction and
retransmission overhead.
things to remember: · lmi - local management interface - control protocol for pvc setup
and management. frame-relay lmi types used in cisco routers are ansi, cisco and
q933a (default is cisco). · the encapsulation types for frame-relay are cisco and ietf
(default is cisco).
· data-link connection identifiers (dlci's), are assigned by the carrier.
· wide range of speeds from 56k over t1 (1.5kbps) to ds3 (45mbps)
· fcs - frame check sequence, similar to crc. appended to every frame for simple error
checking. · frame relay can use isdn/lapd, hdlc, and ppp.
these provide congestion information: · backward explicit congestion notification
(becn) bit set by a frame relay network in frames traveling in opposite direction of
frames encountering a
congested path. dte receiving frames with the becn bit set can request
higher level protocols take flow control action. · forward explicit congestion notification
(fecn) bit set by a frame relay network to inform dte receiving frame that congestion was
experienced in
the path from source to destination. · discard eligible bit (de) a bit set by either the dte or
frame-relay switch that marks this frame as a likely candidate to drop if there is
congestion on
the line.
likely problems on a frame relay config: · lmi does not have to match end to end
(default is cisco), however, it must match what the frame-relay cloud is using. this defines
the parameters of
communication between the router and the frame-relay switch. · encapsulation needs to
match end to end (default is cisco).
· frame map statement the ip address here needs to be the next hop address, and the dlci
number needs to be the local dlci. · if you are able to see remote sites from a central site,
but the remote sites cannot see each other, poison reverse should be disabled on split
horizon. a (asynchronous transfer mode) developed as a compromise between voice
and data needs, a is commonly found
either on large telecom networks or built into networks that have a strong need for
qos (quality of service) needs.
a uses cells that are uniform in size - 53 bytes; 5 bytes for a header, and 48
bytes for payload. this allows a great deal of control over traffic and allows for qos,
but is wasteful in that the header is a greater percentage of the traffic then in other
methods.
a is connection-oriented with traffic traveling from end-to-end over either: · svc (switched
virtual circuits) dynamically created on-demand circuits.
· pvc (permanent virtual circuits) permanently allocated circuits that are always
established and active.
there are two types of interfaces: · nni (network-to-network) connections within the
network cloud between two a devices. · uni (user-to-network) connects a workstation to
an a switch.
there are four major layers in the a reference model (equivalent to the osi
model) · higher layers a signaling, addressing and routing.
· aal (a adoption layer) converts from higher level to a cells.
· a defines a cell relaying and multiplexing.
· physical defines the physical network media and framing. lan token ring token ring is
an older technology that is still prevalent in modern day networking,
and should be reviewed carefully when preparing for the ccie certification track,
both written and lab.

tr is defined in both the original ibm specification and ieee 802.5 and comes in two
speeds, the original 4 mbps and later 16 mbps versions. token ring is installed as a
physical star configuration in that all stations are attached to a mau (multi-station
access unit, similar to a hub in ethernet); but a logical ring in that the token which
provides permission to speak travels from node to node.
token ring operation 1. a token frame is passed from station to station through the ring.
2. when a device has a need to transmit data, it must wait until the token can be seized. a
data frame is attached to the token and both the a and c bits are
set to 0. 3. the token continues on its path from station to station until it reaches the
destination mac address. the data frame is copied and the a and c bits are
changed to 1. 4. the token once again resumes its travels and eventually returns to the
source device, which analyzes the a and c bits, and releases the token.
to review again the function of the control bits:
· a-bit - address recognized (as a mnemonic device, think of this as the acknowledgement
bit, even though it isn't). that the destination sets this bit
to 1 tells the source device that the destination machine was found. c bit copy bit. that the
destination changed this bit to 1 tells the source device that the data frame was copied.
when the token returns, these bits will tell the sender that the destination received
the token and copied the data from the token. for example, if the a bit is set (1) and
the c bit is not (0), that would mean that the destination or receiving station is
recognized, but cannot copy the data from the frame.

collisions are impossible in a token ring network that is functioning normally. the
only time you might see them is when an error condition exists.
early token release can be enabled in the tr configuration. this allows the token to
be available as soon as the data has been delivered.
token ring error detection the most common error condition in tr is a beacon, which
indicates a major
problem such as a cable break or a defective nic.
one of the devices on the ring will be selected as the active monitor, which removes
orphaned data frames from the ring and regenerates tokens.
ethernet ethernet is the most common lan technology currently available, and provides
for
csma/cd, which will be explained later in this document. there are two flavors of
ethernet: 802.3 and ethernet version ii. both standards support multiple physical
media types. the primary differences are:
ethernet ii · specifies a type field, which contains a two-byte field to indicate protocol
type of the contents of the data (ip, ipx, dec, etc.). · supports both layer 1 and 2 of the osi
model.
· supports only 10mb.
802.3 · specifies a length field.
· does not contain any information about protocol type.
· has this information in the dsap and ssap (destination service access protocol and source
service access protocol) fields. supports all of the osi layer 1 functionality, and parts of
layer 2.
· supports 10mb, 100mb, and 1,000mb (gigabit ethernet).
csma/cd since only one device can "talk" on an individual ethernet segment, csma/cd is
used anytime two or more stations share the same segment and, by extension,
available bandwidth. csma/cd listens before transmitting. if a collision occurs it
backs off the clear line, waits a random period of time, and attempts to transmit
again. etherchannel etherchannel is a cisco proprietary method for aggregating the
bandwidth of up to
four fast ethernet channels on a switch and having them appear to be one logical
connection. the requirements are that all the ports be in the same vlan, have the
same speed and duplex settings, and if the switch is not a cat6000, that contiguous
ports be used. besides increasing the bandwidth available between devices, this also
adds a level of protection, because if one of the links within the etherchannel were
to go down, the traffic would continue to pass at the reduced rate without
interruption. fddi (fiber data distributed interface) fddi, and its copper cousin, cddi
represent an older technology that was the
standard for backbone connectivity for some years. it is still found in many legacy
networks, and is still relevant in both real-life situations and in preparation for the
ccie track. it is based on a token-passing scheme similar to token ring, but with dual
counter-
rotating rings that provide redundancy in the event of a fiber (or copper in the case
of cddi) cut. the primary ring carries traffic; the secondary is the backup link. the
rings have a speed of 100mbps, which was perfectly acceptable in the backbone until
the introduction of inexpensive fast ethernet and gigabit ethernet.
there are two types of devices on the network: · das (dual-attached station) which would
be attached directly to both rings.
· sas (single-attached station) - which would be connected to a concentrator.
security aaa (authentication, authorization and accounting) a standard feature set of
software security tools that identify when users are logged
into a router; control each user's authority level; and monitor user activity to provide
accounting information.
tacacs (terminal access controller access control system) · a centralized validation
service that accepts or rejects user name and password pairs. · tacacs+ uses tcp for
transport and the entire body of tacacs+ packets is encrypted if a there is a shared key on
the router and server. · tacacs+ can log every command that is entered at the router exec
command. · works with ppp or chap authentication.
· transmits passwords in clear text.
· tacacs+ can pass caller id or called party values from nas to the server.
· tacacs+ requires aaa, although earlier versions, tacacs and extended tacacs did not work
with aaa. radius (remote authentication dial-in user service) · a client-server based
protocol that accepts or rejects a user name and password pairs. · works with ppp or chap
authentication.
· transmits passwords encrypted by md5 algorithm when they are sent across the data
network. · server component can run on a microsoft nt or unix host.
· used with aaa to enable authentication, authorization and accounting.
· user names and passwords are encrypted.
pix (private internet exchange) firewall a cisco hardware and software platform that
prevents unauthorized connections
between two networks based on a defined security policy. it most commonly sits
between a company's internal network and the internet.
multiservice voice/video protocols
erlang b a traffic model used by telephone system designers to estimate the number of
lines required for trunks. h.323 standard for real-time multimedia communications and
conferencing over packet-based networks. ss7 (signaling system 7) international
standard for common channel signaling between pstn (public switch telephone network)
switches. this standard
provides for out-of-band signaling and is responsible for routing, link status, and
connection control. 1-800 calls, local phone number portability, in-network phone
mail and portable phone roaming all are defined by ss7. rtp (real-time transport
protocol) provides support for applications with real-time properties such as video or
voice over ip. compression the compress {predictor | stac} command can be used to
enhance service on slow
point-to-point links using hdlc, ppp, and lapb. this will cause an increase in cpu
utilization on the router.

collected by : emadido™