Nexus7010# show vrrp
Interface VR IpVersion Pri Time Pre State VR IP addr
---------------------------------------------------------------
Ethernet3/10 1 IPV4 100 1 s Y Backup 192.18.38.254
Note that both devices agree the master router is 192.18.38.1 (on the Juniper Virtual
Chassis), and both use a virtual IP address of 192.18.38.254.
If a router or link fails, the backup router should take over as the master. In this example,
the Cisco Nexus 7010 is promoted to master statement by reducing the Juniper Virtual
Chassis’ priority to 10. Since the Cisco Nexus 7010 uses a priority of 250 by default, it
will take over as master once this Juniper Virtual Chassis configuration change is
committed:
admin@EX9208> configure
admin@EX9208# set interfaces xe-5/0/5 family inet address 192.18.38.1/24
vrrp-group 1 virtual-address 192.18.38.254 priority 10
admin@EX9208# commit
After this change, the Juniper device becomes the backup router, and the master router is
now 192.18.38.254 on the Cisco device:
admin@EX9208# run show vrrp summary
Interface State Group VR state VR Mode Type Address
xe-5/0/5.0 up 1 backup Active lcl
192.18.38.1
vip
192.18.38.254
The Cisco device agrees that it is now the VRRP master:
Nexus7010# show vrrp summary
VRRP Summary
------------
Total Number of Groups Configured: 1
Init : 0 Backup : 0 Master : 1
Wi@Fi&passthrough&
Objective!
To verify the ability of a Juniper switch to forward Wi-Fi management traffic between a
Cisco Wi-Fi controller and Cisco Wi-Fi access points.
Background!
Many enterprises provision wireless LAN access using one or more centrally managed
controllers that monitor and manage RF and data networking parameters in real time. In
this model, Wi-Fi access points (APs) distributed throughout the enterprise depend on the
controllers for their configurations. Thus, reliable connectivity between controllers and
access points is essential.
Comentarios a estos manuales