Management Ethernet Interface; Fpc Interface - Juniper TX MATRIX PLUS Hardware Manual

Hide thumbs Also See for TX MATRIX PLUS:
Table of Contents

Advertisement

Management Ethernet Interface

FPC Interface

Copyright © 2010, Juniper Networks, Inc.
NOTE: The Routing Engines in the TX Matrix Plus router and the T1600 routers
in the routing matrix do not support the
and
internal Ethernet interfaces. Automated scripts that contain
fxp1
fxp2
commands that reference
ixgbe0
, and
ixgbe1
The router's management Ethernet interface
devices to the router through the
router or the connector interface panel (CIP) on the T1600 router. The Junos OS
automatically creates
em0
valid IP address before you can use
The Junos OS also creates the internal Ethernet interface,
Routing Engine installed into the TXP-CB in slot
If the router has redundant Routing Engines, another internal Ethernet interface,
is created on each Routing Engine in order to support fault tolerance. Two physical links
between the Routing Engines connect the independent control planes. If one of the links
fails, both Routing Engines can use the other link for IP communication.
When you enter the show interfaces command, the management Ethernet and internal
Ethernet interfaces (and logical interfaces) are displayed.
user@host> show interfaces
Interface
em0
em0.0
gre
ipip
ixgbe0
ixgbe0.0
ixgbe1
ixgbe1.0
A routing matrix can contain up to four T1600 routers, and each T1600 router can contain
up to eight FPCs (numbered 0 through 7). Therefore, the routing matrix can consist of
up to 32 FPCs (numbered 0 through 31). When you specify an FPC in an interface name
and within certain commands, the T1600 router that contains that FPC is implicit. Table
23 on page 80 shows the correspondence between the FPC hardware slot numbers in
T1600 routers and the FPC assignments recognized by a routing matrix.
Chapter 4: Junos OS in a Routing Matrix Overview
fxp0
,
, or
fxp0
fxp1
fxp2
.
is the interface for connecting network
em0
port on the TXP-CB on the TX Matrix Plus
ETHERNET
, but you must configure its logical interface,
em0
as a management port.
CB0
Admin Link Proto
Local
up
up
up
up
inet
192.168.176.3/25
up
up
up
up
up
up
up
up
inet
10.34.0.4/8
162.0.0.4/2
inet6
fe80::200:ff:fe22:4/64
fec0::a:22:0:4/64
tnp
0x22000004
up
up
up
up
inet
10.34.0.4/8
162.0.0.4/2
inet6
fe80::200:1ff:fe22:4/64
fec0::a:22:0:4/64
tnp
0x22000004
management interface, or the
must be modified to use
, with a
em0.0
, which connects the
ixgbe0
to the Packet Forwarding Engine.
Remote
,
em0
,
ixgbe1
79

Advertisement

Table of Contents
loading

Table of Contents