Professional Documents
Culture Documents
J6300
J4300
J2300
www.businesscontinuity.com.mx
Up to 2 Gbps+ performance
T1, E1, FE, Serial, ISDN BRI, ADSL/2/2+ G.SHDSL,
DS3,E3, GE Interfaces
4 fixed GE LAN ports, 4 PIM slots and 2
EPIM/PIM slots
Up to 1 Gbps+ performance
T1, E1, FE, Serial, ISDN BRI, ADSL/2/2+ G.SHDSL,
DS3,E3, GE Interfaces
4 fixed GE LAN ports, 4 PIM slots and 2 EPIM/PIM
slots
Up to 2XT1/E1 performance
T1,E1,Serial Wan Interfaces
Two fixed FE LAN ports and optional integrated
ISDN BRI backup
Fixed configurations / not modular
J2350
J2320
www.businesscontinuity.com.mx
Support for T1, E1, Synchronous Serial, ISDN Basic Rate Interface,
ADSL2/ADSL2+, G.SHDSL, and Gigabit Ethernet Interfaces
Support for integrated IP telephony*
4 fixed Gigabit Ethernet LAN ports, and 3 PIM slots
256 MB DRAM default, expandable to 1 GB DRAM
256 MB compact flash default, upgradeable to 1 GB
Hardware encryption acceleration (optional)
J6350
J4350
www.businesscontinuity.com.mx
Support for T1, E1, Fast Ethernet, Synchronous Serial, ISDN BRI,
ADSL2/ADSL2+, G.SHDSL, DS3, E3, Gigabit Ethernet Interfaces
Support for integrated IP telephony using the Avaya IG550
Integrated Gateway
4 fixed Gigabit Ethernet LAN ports, 2 PIM slots, and 4
EPIM/PIM slots
DC version available
1 GB DRAM default, expandable to 2 GB DRAM
256 MB compact flash default, upgradeable to 1 GB
Hardware encryption acceleration standard
Redundant AC or DC power supplies
Support for T1, E1, Fast Ethernet, Synchronous Serial, ISDN BRI,
ADSL2/ADSL2+, G.SHDSL, DS3, E3, Gigabit Ethernet Interfaces
Support for integrated IP telephony using the Avaya IG550 Integrated
Gateway
4 fixed Gigabit Ethernet LAN ports, 4 PIM slots, and 2 EPIM/PIM slots
DC version available
1 GB or 256 MB DRAM default, expandable to 2 GB DRAM
256 MB compact flash default, upgradeable to 1 GB
Hardware encryption acceleration (optional)
Console
Port
USB Port
Power
Button
Physical Interface
Module (PIM)
www.businesscontinuity.com.mx
LAN Ports
M10i
M7i
www.businesscontinuity.com.mx
Up to 2 Gbps+ performance
T1, E1, FE, Serial, ISDN BRI, ADSL/2/2+
G.SHDSL, DS3,E3, GE Interfaces
4 fixed GE LAN ports, 4 PIM slots and 2
EPIM/PIM slots
M-series Routers
www.businesscontinuity.com.mx
M7i
ESD
Point
LAN
Ports
Routing
Engine
Physical
Interface
Module (PIM)
MGMT
Port
www.businesscontinuity.com.mx
Console
Port
Flexible PIC
Concentrator
(FPC)
RE1
RE0
M10i
PICs
www.businesscontinuity.com.mx
Console
Port
FPC1
FPC0
www.businesscontinuity.com.mx
10
www.businesscontinuity.com.mx
11
The I/O Manager ASIC verifies the integrity of both the Layer 2 and Layer 3 headers.
Provided the data packet is valid, the ASIC removes the Layer 2 header and
segments the packet into 64-byte units called a J-Cell.
The I/O Manager ASIC sends these J-cells to the Distributed Buffer Manager ASIC for
storage in the shared memory pool.
www.businesscontinuity.com.mx
12
Every Juniper Networks router contains a single Internet Processor ASIC on the
control board in the Packet Forwarding Engine.
The Internet Processor ASIC is the heart of the Packet Forwarding Engine. It is the
only ASIC in the forwarding path that accesses the forwarding table, performs route
lookups, and makes forwarding decisions.
It receives notification cells from the Inbound Distributed Buffer Manager ASIC and
transforms them into result cells after performing a route lookup.
www.businesscontinuity.com.mx
13
Module 3:
JUNOS Software CLI Review
14
Configuration
in text file
Candidate
configuration
copy,
save
load
Configuration
Automatic
Rollback
Active
Configuration
www.businesscontinuity.com.mx
Commit
Configure
Confirmed
Configuration changes:
Made in candidate configuration
When you select Apply or OK using JWEB; written to Active
Configuration
Interim
Rollback up to 50 versions
Configuration Manipulation
15
www.businesscontinuity.com.mx
16
version 8.0R2.8;
system {
services {
web-management {
http;
}
}
syslog {
file messages {
any any;
}
}
}
Factory Default
www.businesscontinuity.com.mx
17
www.businesscontinuity.com.mx
CLI Overview
CLI
18
Operational Mode
www.businesscontinuity.com.mx
19
Context-Sensitive Help
Operational Mode
www.businesscontinuity.com.mx
20
www.businesscontinuity.com.mx
21
We further complete our command with the letter c followed by the Tab key:
Command Completion
www.businesscontinuity.com.mx
22
We further complete our command with the letter c followed by the Tab key:
Command Completion
www.businesscontinuity.com.mx
23
As with operational mode, the router uses the prompt to visually show you that
you are in configuration mode. The > is changed into the pound character (#),
and your current level in the hierarchy is displayed above the routers
hostname. The [edit] portion of the output on Merlot tells us that we are at the
top of the configuration hierarchy.
Configuration Mode
www.businesscontinuity.com.mx
You enter new information into the configuration with the set command.
24
www.businesscontinuity.com.mx
You can view the changes youve made to the configuration by issuing the
show command.
25
www.businesscontinuity.com.mx
The existing active configuration is saved on the router for future use.
26
www.businesscontinuity.com.mx
27
operator
read-only
super-user
unauthorized
Login Classes
www.businesscontinuity.com.mx
User Authentication
28
www.businesscontinuity.com.mx
29
www.businesscontinuity.com.mx
30
www.businesscontinuity.com.mx
31
Example
www.businesscontinuity.com.mx
You have just installed and turned on a router and are configuring the
JUNOS software for the first time.
32
Module 4:
Initial Configuration
33
www.businesscontinuity.com.mx
34
To configure configuration groups and inheritance, you can include the groups
statement at the [ edit ] hierarchy level:
www.businesscontinuity.com.mx
35
group-name is the name of a configuration group. You can configure more than one
configuration group by specifying multiple group-name statements. However, you
cannot use the prefix junos- in a group name because it is reserved for use by the
JUNOS software.
To create a configuration group, include the groups statement at the [edit] hierarchy
level:
www.businesscontinuity.com.mx
36
www.businesscontinuity.com.mx
37
Upload Package
www.businesscontinuity.com.mx
38
Installing Package
www.businesscontinuity.com.mx
39
www.businesscontinuity.com.mx
40
www.businesscontinuity.com.mx
unit - The logical portion of the interface that contains properties, such
as an IP address.
port - The location on the PIC where the interface port is located.
fpc - The physical slot in the chassis where the interface is located.
41
www.businesscontinuity.com.mx
42
www.businesscontinuity.com.mx
so-6/0/0.0
at-3/1/0.0
at-3/2/0.0
at-3/3/0.0
at-3/0/0.0
43
Interfaces Supported
www.businesscontinuity.com.mx
4-port E1 PIC
44
www.businesscontinuity.com.mx
Interfaces Properties
45
Description
Diagnostic characteristics
Encapsulation
Frame check sequence (FCS)
Interface clock source
Interface MTU size
Keepalives
Payload scrambling
Physical Properties
www.businesscontinuity.com.mx
46
inet
inet6
iso
Mpls
Protocol Families
Logical Properties
www.businesscontinuity.com.mx
47
www.businesscontinuity.com.mx
IP Version 4
Enable an Interface
48
www.businesscontinuity.com.mx
[edit interfaces]
user@Cabernet# show
inactive: fxp0 {
description " This is the Ethernet
management interface;
unit 0 {
[edit interfaces]
user@Cabernet# show
fxp0 {
description " This is the Ethernet
management interface ";
unit 0 {
[edit interfaces]
user@Cabernet# deactivate fxp0
[edit interfaces]
user@Cabernet# activate fxp0
49
www.businesscontinuity.com.mx
IP Version 4
Deleting an Interface
50
Errors
Policy discards
L3 incompletes
L2 channel errors
L2 mismatch timeouts
SRAM errors
HS link CRC errors
Carrier transitions
Errors
Drops
Aged packets
www.businesscontinuity.com.mx
51
Cabernet
Seconds
Time
Interface
Link
Current Delta
Statistics
monitor interface
www.businesscontinuity.com.mx
52
show arp
www.businesscontinuity.com.mx
53
local Loopback
Loopback Testing
www.businesscontinuity.com.mx
remote Loopback
54
BERT Testing
www.businesscontinuity.com.mx
55
www.businesscontinuity.com.mx
56
Module 5: Protocol
Independent Routing
Properties
57
www.businesscontinuity.com.mx
Static Routes
58
Static Routes
www.businesscontinuity.com.mx
59
www.businesscontinuity.com.mx
Using a static route when you have a single physical connection is a valid
consideration.
Static Routes
60
www.businesscontinuity.com.mx
next-hop Options
61
routing-options {
static {
defaults {
static-options;
}
route destination-prefix {
next-hop next-hop;
qualified-next-hop address {
metric metric;
preference preference;
}
lsp-next-hop lsp-name{
metric metric;
preference preference;
}
static-options;
}
}
}
www.businesscontinuity.com.mx
62
preference
Readvertise
retain
community
install
metric
www.businesscontinuity.com.mx
passive
as-path
no-install
no-readvertise
active
63
Some of the options available for configuration on a static route are outlined here. Not
every route requires the configuration of each attribute.
www.businesscontinuity.com.mx
64
[edit routing-options]
user@Chardonnay# show
static {
route 192.168.16.0/24 next-hop 1.1.1.1;
}
[edit routing-options]
user@Chardonnay# set static route 192.168.16/24 next-hop 1.1.1.1
Configuration Examples
www.businesscontinuity.com.mx
We configure the routes for 192.168.32.0 /24 and 192.168.48.0 /24 in a similar manner.
Once completed, the routing table looks like this:
Configuration Examples
65
www.businesscontinuity.com.mx
We check our routing table and see that our change took effect:
user@Chardonnay> show route protocol static
[edit routing-options]
user@Chardonnay# set static defaults preference 200
66
www.businesscontinuity.com.mx
Routing Tables
inet.0 - UniCast Routes *
inet.1 Multicast forwarding cache
inet.2 - MBGP RPF
inet.3 - MPLS Path
inet6.0 - IPv6 Routes
mpls.0 MPLS next hops
67
www.businesscontinuity.com.mx
Next hop information When multiple next hops exist, the routing table selects a single next hop
to be placed in the forwarding table. Multiple next-hop values can be placed in the forwarding
table.
Protocol preference Protocol preference. This preference value assists the routing table in
selecting the active route when more than one version of a route exists.
Protocol name This name tells you how the routing table learned the route. This name is also
used by routing policies to advertise and filter routes.
Table inet.0
68
Table inet.0
www.businesscontinuity.com.mx
69
www.businesscontinuity.com.mx
70
71
www.businesscontinuity.com.mx
72
www.businesscontinuity.com.mx
Routing Policy
73
www.businesscontinuity.com.mx
74
Policy Processing
accept
reject
next policy
Forming a Policy
www.businesscontinuity.com.mx
75
Forming a Policy
www.businesscontinuity.com.mx
76
Multiterm Policy
www.businesscontinuity.com.mx
77
www.businesscontinuity.com.mx
The match conditions available within the JUNOS software provide numerous
ways to identify routes of interest. All of the criteria will be defined using either
the from or the to syntax.
from and to
78
Match criteria
www.businesscontinuity.com.mx
79
www.businesscontinuity.com.mx
lets say that you wanted to accept all BGP routes from neighbor 1.1.1.1 only if the
routes have a MED value of 10. You could configure a policy that looks like the
following:
80
www.businesscontinuity.com.mx
lets say that you wanted to accept all BGP routes from neighbor 1.1.1.1 only if the
routes have a MED value of 10. You could configure a policy that looks like the
following:
Route Filters
81
www.businesscontinuity.com.mx
82
Module 7: RIP
83
RIP sends routing update messages at regular intervals (30 seconds) and when warranted by
network topology changes.
84
The metric (hop count) is a measure of the distance from the source of the update to the
destination network. Each hop in the path is assigned a value, which is typically 1. Most
implementations (including the JUNOS software) let you alter this value.
www.businesscontinuity.com.mx
RIP routers exchange packets with their neighbors; the packets contain network addresses
and an associated metric, or hop count, to reach those addresses.
RIP routers use UDP (User Datagram Protocol) port 520 to send messages to their
neighbors.
RIP Features
www.businesscontinuity.com.mx
Infinity Metric
85
www.businesscontinuity.com.mx
Infinity Metric
86
www.businesscontinuity.com.mx
Response Messages
In response to a Request message generated by the local router.
A regular (unsolicited) Response message sent by a neighbor.
A triggered update Response message sent by a neighbor.
87
Request Messages
The purpose of a Request message is to ask for all or some part of the local routers
current routing table. An optimum time to observe a Request message is when a
router first boots up or its routing process is restarted.
RIP routers can receive two types of messages from their neighbors: Request
messages and Response messages. Each of these message types performs a specific
function.
Input Processing
RIP Operations
www.businesscontinuity.com.mx
88
Output Processing
RIP Operations
www.businesscontinuity.com.mx
89
Output Processing
RIP Operations
Split Horizon
Split Horizon with Poisoned Reverce
Stability Features
www.businesscontinuity.com.mx
90
Triggered Updates
Hold-Downs
Timers
Stability Features
www.businesscontinuity.com.mx
91
www.businesscontinuity.com.mx
Nonhierarchical design
Suboptimal routing
Slow convergence
Scalability
Limitations
92
Packet Types
www.businesscontinuity.com.mx
93
Packet Types
www.businesscontinuity.com.mx
94
Route tag
Authentication
Multicast announcesments
VLSM support
RIPv2 Extensions
www.businesscontinuity.com.mx
95
www.businesscontinuity.com.mx
96
www.businesscontinuity.com.mx
97
www.businesscontinuity.com.mx
98
www.businesscontinuity.com.mx
99
www.businesscontinuity.com.mx
100
MD5 authentication
Simple authentication
www.businesscontinuity.com.mx
Configuring Authentication
101
www.businesscontinuity.com.mx
102
To have your RIP systems communicate with the rest of your network, you enable
RIP on each interface that is directly connected to a RIP neighbor. You do this by
defining a group in which you identify each RIP device by the name of the
interface that is directly connected to the RIP device. In this example, the Fast
Ethernet interface fe-0/0/0 is the connection to your RIP device.
Lab 3: RIP
Module 8: OSPF
103
Forming Adjacencies
www.businesscontinuity.com.mx
104
www.businesscontinuity.com.mx
The first step in building an OSPF network is advertising the networks connected to
the local router. This information is contained in the router LSA, type code 1, which
displays data about the local router. This includes all links connected to the router,
the metrics of those interfaces, and the OSPF capabilities of the router.
105
www.businesscontinuity.com.mx
106
Router Types
Internal router
Backbone router
Area Border Router
Autonomous System boundary router
OSPF Area
www.businesscontinuity.com.mx
107
www.businesscontinuity.com.mx
108
Once youve committed your configuration to the router and returned to the user
operational mode, you may find that the network isnt quite right. Configuration
issues often appear as problems with your OSPF interfaces and neighbors. We have
the ability to verify these issues within the software.
www.businesscontinuity.com.mx
109
Once you are certain the interfaces are properly assigned and operational, you should
check the status of the neighbors adjacency by using the show ospf neighbor
command:
www.businesscontinuity.com.mx
110
The show ospf database command is an excellent tool in troubleshooting OSPF. If the information
is not in the database, it will not appear in the routing table. The output shows summary
information about each LSA on a per-area basis:
www.businesscontinuity.com.mx
111
The show ospf database command is an excellent tool in troubleshooting OSPF. If the information
is not in the database, it will not appear in the routing table. The output shows summary
information about each LSA on a per-area basis:
www.businesscontinuity.com.mx
112
The show ospf database command is an excellent tool in troubleshooting OSPF. If the information
is not in the database, it will not appear in the routing table. The output shows summary
information about each LSA on a per-area basis:
www.businesscontinuity.com.mx
113
The show ospf database command is an excellent tool in troubleshooting OSPF. If the information
is not in the database, it will not appear in the routing table. The output shows summary
information about each LSA on a per-area basis:
www.businesscontinuity.com.mx
114
www.businesscontinuity.com.mx
115
The show ospf statistics command displays counters based on the OSPF packet type.
Boththe total number of packets and the number in the last 5 seconds is shown.
www.businesscontinuity.com.mx
116
The show ospf route command displays the results of the SPF algorithm. These are the routes that
OSPF is handing off to the routing table. Each destination route includes a type (internal versus
external), the LSA type used to find the route, a metric, and an outgoing interface name or IP
address:
www.businesscontinuity.com.mx
117
www.businesscontinuity.com.mx
118
Lab 3: OSPF
www.businesscontinuity.com.mx
119
Module 9: IS-IS
120
www.businesscontinuity.com.mx
121
Level 2
Two IS-IS routers form an adjacency and share database information when both ends of
their common link are configured for Level 2. Lets take a look at Figure.
IS-IS Levels
www.businesscontinuity.com.mx
122
Level 1
The requirements for a Level 1 adjacency are a bit different. Two IS-IS routers form an
adjacency when each end of the common network link is configured for Level 1 and the
IS-IS area value of each router is identical.
IS-IS Levels
www.businesscontinuity.com.mx
123
Reject Upon an authentication failure, an IS-IS router will transition between this state and the Down
state.
Down This represents a nonfunctioning adjacency. An IS-IS router moves to this state for one of several
reasons, including area mismatches, expiration of the hold time, and authentication failures.
Up This is a fully functioning state for IS-IS. An adjacency relationship is formed and the databases have
been exchanged.
Initializing When a local router sees itself in a neighbors hello, it transitions to this state. This state shows
that bidirectional communications are established.
One-Way Your IS-IS router transitions to this state after sending an IS-IS Hello PDU. In addition, any
received hellos do not contain the local routers address as a neighbor.
New This state is seen when the IS-IS adjacency process is just beginning. Start events could include
router boot-up or initial configuration.
www.businesscontinuity.com.mx
124
www.businesscontinuity.com.mx
125
www.businesscontinuity.com.mx
Configuration Commands
126
www.businesscontinuity.com.mx
127
Configuring Protocol
www.businesscontinuity.com.mx
128
Configuring Protocol
www.businesscontinuity.com.mx
129
Configuring Protocol
www.businesscontinuity.com.mx
130
Configuring Protocol
www.businesscontinuity.com.mx
131
Configuring Protocol
www.businesscontinuity.com.mx
132
Configuring Protocol
www.businesscontinuity.com.mx
133
Configuring Protocol
www.businesscontinuity.com.mx
134
Configuring Protocol
www.businesscontinuity.com.mx
135
Configuring Protocol
www.businesscontinuity.com.mx
136
www.businesscontinuity.com.mx
137
Lab 4: IS-IS
www.businesscontinuity.com.mx
138
139
www.businesscontinuity.com.mx
140
BGP exchanges its routing information between two routers, called peers or neighbors.
This connection is logical in nature and relies on the establishment of a TCP session
between thepeers. The session is established across a direct physical link or a number
of intermediate links.
Peers
www.businesscontinuity.com.mx
141
When two BGP routers are in different AS networks, the session between them is
considered an external BGP (EBGP) connection. By default, an EBGP connection is
formed between directly connected peers.
www.businesscontinuity.com.mx
142
The connection of two BGP routers within the same AS is called an internal BGP
(IBGP) connection. Unlike the EBGP variety, there is no requirement for physical
connectivity betweenIBGP peers.
Adjacency-RIB-in
Local-RIB
Adjacency-Out
Idle
Connect
Active
OpenSent
OpenConfirm
Estableshed
www.businesscontinuity.com.mx
Establishing Relationships
143
Assigning an AS Number
www.businesscontinuity.com.mx
144
www.businesscontinuity.com.mx
145
www.businesscontinuity.com.mx
146
www.businesscontinuity.com.mx
147
www.businesscontinuity.com.mx
148
www.businesscontinuity.com.mx
149
www.businesscontinuity.com.mx
150
Lab 4: BGP
www.businesscontinuity.com.mx
151
152
/usr/libexec/ui/recovery-mode
www.businesscontinuity.com.mx
3. Next, the system will run the normal bootup process. When prompted for "pathname" enter:
1.
2.
153
[edit]
root# commit and-quit
commit complete
Exiting configuration mode
[edit]
root# delete system root-authentication
root> configure
Entering configuration mode
www.businesscontinuity.com.mx
5. Enter configuration mode and edit or delete the root authentication password.
4. The system will finish booting up and display the "root>" prompt.
NOTE: the system
Starting CLI ...
root>
154
www.businesscontinuity.com.mx
Type '?' for a list of commands, 'help' for more detailed help.
ok boot -s
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [kernel] in 9 seconds...
155
# /usr/libexec/ui/recovery-mode
www.businesscontinuity.com.mx
4. Mount the virtual file systems (for JUNOS 5.4 and above, it is not necessary to mount the jbase
package, however the other packages still need to be mounted):
156
[edit]
root@router# exit
Exiting configuration mode
[edit]
root # commit
commit complete
[edit]
root# set system root-authentication plain-text-password
New password:
Retype new password:
root> configure
Entering configuration mode
www.businesscontinuity.com.mx
157
soporte@businesscontinuity.com.mx
eespinosa@businesscontinuity.com.mx
www.businesscontinuity.com.mx
158
www.businesscontinuity.com.mx
Additional Informaton
159
www.businesscontinuity.com.mx
160
The Release Notes describe the documentation for the routing platforms and known
problems with the software. JUNOS software runs on all Juniper Networks J-series,
M-series, MX-series, and T-series routing platforms. You can also find these release
notes on the Juniper Networks Technical Publications Web page, which is located at
http://www.juniper.net/techpubs/.
Managing Informaton