I'm sorry, please ignore the last message, Type-2 consistency status was due to some testing: Heres the correct vpc status:
Legend: (*) - local vPC is down, forwarding via vPC peer-link vPC domain id : 1 Peer status : peer adjacency formed ok vPC keep-alive status : peer is alive Configuration consistency status : success Per-vlan consistency status : success Type-2 consistency status : success vPC role : secondary, operational primary Number of vPCs configured : 2 Peer Gateway : Enabled Peer gateway excluded VLANs : - Dual-active excluded VLANs : - Graceful Consistency Check : Enabled Auto-recovery status : Enabled (timeout = 240 seconds) vPC Peer-link status --------------------------------------------------------------------- id Port Status Active vlans -- ---- ------ -------------------------------------------------- 1 Po1 up 1,200-202,2810 vPC status ---------------------------------------------------------------------------- id Port Status Consistency Reason Active vlans ------ ----------- ------ ----------- -------------------------- ----------- 1 Po2 up success success 200 2 Po3 up success success 200 On Fri, Aug 9, 2013 at 5:57 PM, Christian Kildau <li...@unixhosts.org>wrote: > Yes, vlan200 goes trough vpc peer-link: > > # show vpc > Legend: > (*) - local vPC is down, forwarding via vPC peer-link > > vPC domain id : 1 > Peer status : peer adjacency formed ok > vPC keep-alive status : peer is alive > Configuration consistency status : success > Per-vlan consistency status : success > Type-2 consistency status : failed > Type-2 inconsistency reason : VTP type-2 configuration incompatible > vPC role : secondary, operational primary > Number of vPCs configured : 2 > Peer Gateway : Enabled > Peer gateway excluded VLANs : - > Dual-active excluded VLANs : - > Graceful Consistency Check : Enabled > Auto-recovery status : Enabled (timeout = 240 seconds) > > vPC Peer-link status > --------------------------------------------------------------------- > id Port Status Active vlans > -- ---- ------ -------------------------------------------------- > 1 Po1 up 1,200-202,2810 > > vPC status > > ---------------------------------------------------------------------------- > id Port Status Consistency Reason Active > vlans > ------ ----------- ------ ----------- -------------------------- > ----------- > 1 Po2 up success success 200 > 2 Po3 up success success 200 > > > On Fri, Aug 9, 2013 at 4:50 PM, Сергей Кремезной <kremezn...@gmail.com>wrote: > >> Hi! >> >> Through what links (and their config) does Vlan200 go? If its vPC >> peer-link, please show all vpc-related information: >> >> # show vpc [all possible keys] >> >> Good day. >> >> --- >> Sergey >> _______________________________________________ >> cisco-nsp mailing list cisco-nsp@puck.nether.net >> https://puck.nether.net/mailman/listinfo/cisco-nsp >> archive at >> http://puck.nether.net/pipermail/cisco-nsp/ >> >> -- >> http://www.chrisk.de/ >> >> -- >> http://www.chrisk.de/ >> _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/