Validation!
The command show services rpm history-results will display up to 50
results of RPM probes and tests:
admin@ex9208# run show services rpm history-results
Owner, Test Probe received Round trip time
myprobe, t1 Fri Apr 18 00:31:20 2014 2802
usec
myprobe, t1 Fri Apr 18 00:31:21 2014 5441
usec
myprobe, t1 Fri Apr 18 00:31:22 2014 9909
usec
myprobe, t1 Fri Apr 18 00:31:23 2014 2754
usec
myprobe, t1 Fri Apr 18 00:31:24 2014 3334
usec
Redundant&Trunk&Group&(RTG)&
Objective!
To validate failover functionality of Juniper’s Redundant Trunk Group (RTG) feature
between Juniper and Cisco switches.
Background!
Juniper’s Redundant Trunk Group (RTG) feature allows definition of primary and
secondary paths between switches and redirects traffic across the secondary trunk if the
primary link fails. RTG provides an alternative to spanning tree bridging for
redundancy. RTG works in mixed Juniper-Cisco environments with no additional
configuration needed on Cisco switch ports. Up to 16 redundant trunk groups can be
defined on a standalone switch or Juniper Virtual Chassis Fabric.
Topology!
In this example, three devices – one from Juniper and two Cisco – form a ring topology.
The devices are the Juniper Virtual Chassis Fabric (in turn comprised of two Juniper
QFX5100 and one Juniper EX4300 switches); a Cisco Nexus 7010; and a Cisco Catalyst
3850. At test time, RTG was not supported in the Juniper EX9200, so it was not included
in this test.
In this example, the inter-switch ports are VLAN trunk ports allowing traffic from VLAN
IDs 2001-2003. However, RTG works equally well with or without VLAN trunking.
Spirent TestCenter traffic generator/analyzers offer frames to access ports on each switch.
Kommentare zu diesen Handbüchern