Hi All, if you are a current CCNP R&S and will expire before Feb 2020:   Can we take any of the CCNP exams (i.e. TSHOOT, Switch or Route or any CCNP wireless exams) to renew my current CCNP R&S and this will be migrated to the new CCNP Enterprise for the next 3 years?    Plan I'm thinking to take to renew my current CCNP R&S:  Take CCNA Wireless --> Take one of the CCNP Wireless exam   Any inputs or recommendation is really appreciated, thanks!    ... View more

Hi,        I have a network topology with 2 PPPoE dialer interface from 2 different ISP's and both are pro actively monitored by IP SLA's. Implementing Policy Based routing, LAN 1 uplink use ISP1 gateway and the latter uses ISP 2 gateway. However, I am trying to improve the set up where I want to have a dual redundancy on each LAN networks.  Example Scenario For LAN 1: - LAN 1 networks primary uplink is ISP1 gateway then will switch to ISP2 as ISP 1 gateway becomes unreachable via IP-SLA tracking. As ISP 1 goes back up, then will switch back again to its primary uplink.  - LAN 2 network uses ISP 2 gateway as its primary link and switchover to ISP 1 as the primary link goes down.  ISP1 gateway: XXX.XXX.XXX.XXX/32 ISP2 IP gateway: YYY.YYY.YYY.YYY/32 LAN1 Network: 10.4.3.0/24 (gateway: 10.4.3.253) LAN2 Network: 10.0.0.0/24 (gateway: 10.0.0.253)       My problem is that I am having trouble with NAT as I am using both dialer (dialer 1 and 2) interfaces for each networks.        Your inputs will be greatly appreciated. Thanks!  Current configuration:  multilink bundle-name authenticated ! ! ! ! redundancy ! ! ! ! ! controller VDSL 0/0/0 ! track 1 ip sla 1 reachability delay down 10 up 1 ! track 2 ip sla 2 reachability delay down 10 up 1 ! ! ! interface Embedded-Service-Engine0/0 no ip address shutdown ! interface GigabitEthernet0/0 description WAN 1 - CAT ISP no ip address ip virtual-reassembly in duplex auto speed auto pppoe enable group global pppoe-client dial-pool-number 1 no cdp enable ! interface GigabitEthernet0/1 description WAN 2 - ToT ISP no ip address ip virtual-reassembly in duplex auto speed auto pppoe enable group global pppoe-client dial-pool-number 2 no cdp enable ! ! note: for testing purposes, i change Gi0/2 interface based on LAN1 or LAN 2 testing though I have L3 switch from downstream network to cater both LAN networks. interface GigabitEthernet0/2 description LAN INTERFACE ip address 10.0.0.253 255.255.255.0  ip nat inside ip virtual-reassembly in ip policy route-map PBR-TO-INTERNET duplex auto speed auto ! interface ATM0/0/0 no ip address shutdown no atm ilmi-keepalive ! interface Ethernet0/0/0 no ip address shutdown ! interface Dialer1 mtu 1492 ip address negotiated ip nat outside ip virtual-reassembly in encapsulation ppp ip tcp adjust-mss 1452 dialer pool 1 ppp authentication chap callin ppp chap hostname <ISP1@hostname.com> ppp chap password 0 <ISP1passw0rd> no cdp enable ! interface Dialer2 mtu 1492 ip address negotiated ip nat outside ip virtual-reassembly in encapsulation ppp ip tcp adjust-mss 1452 dialer pool 2 ppp authentication chap callin ppp chap hostname <ISP2@ hostname.com> ppp chap password 0 <ISP2passw0rd> no cdp enable ! ip forward-protocol nd ! no ip http server no ip http secure-server ! ip nat inside source route-map NAT-TO-ISP1 interface Dialer1 overload ip nat inside source route-map NAT-TO-ISP2 interface Dialer2 overload ip route 0.0.0.0 0.0.0.0 XXX.XXX.XXX.XXX track 1 ip route 0.0.0.0 0.0.0.0 YYY.YYY.YYY.YYY 200 ! ip access-list extended HQ-NETWORK-TO-INTERNET permit ip 10.4.3.0 0.0.0.255 any ip access-list extended MANSION-NETWORK-TO-INTERNET permit ip 10.0.0.0 0.0.0.255 any ! ip sla auto discovery ip sla 1 icmp-echo XXX.XXX.XXX.XXX source-interface Dialer1 ip sla schedule 1 life forever start-time now ip sla 2 icmp-echo YYY.YYY.YYY.YYY source-interface Dialer2 ip sla schedule 2 life forever start-time now ! route-map NAT-TO-ISP2 permit 10 match ip address MANSION-NETWORK-TO-INTERNET set interface Dialer2 ! route-map NAT-TO-ISP2 permit 20 match ip address HQ-NETWORK-TO-INTERNET set interface Dialer2 ! route-map NAT-TO-ISP1 permit 10 match ip address HQ-NETWORK-TO-INTERNET set interface Dialer1 ! route-map NAT-TO-ISP1 permit 20 match ip address MANSION-NETWORK-TO-INTERNET set interface Dialer1 ! route-map PBR-TO-INTERNET permit 10 match ip address HQ-NETWORK-TO-INTERNET set ip next-hop verify-availability XXX.XXX.XXX.XXX 10 track 1 set interface Dialer1 Null0 ! route-map PBR-TO-INTERNET permit 20 match ip address MANSION-NETWORK-TO-INTERNET set ip next-hop verify-availability YYY.YYY.YYY.YYY 10 track 2 set interface Dialer2 Null0 ... View more

Hi, I would like to set-up a VSS on our clients 6506-E switches. But first things first, I checked if SSO is already working. However, upon checking, it seems that SSO is not working and found some observations based on the current status of our client 6506-E switches. Appreciate your advise on this.    Stateful Switchover (SSO) is not working in Core Switches as expected.  Communication status is in “Down” state Peer Information is not available. (PEER state is disabled) ​ Core-1: SW-CORE-1#show version Cisco IOS Software, s2t54 Software (s2t54-IPSERVICESK9-M), Version 15.0(1)SY2, RELEASE SOFTWARE (fc4) System image file is "bootdisk:s2t54-ipservicesk9-mz.SPA.150-1.SY2.bin"   SW-CORE-1#show redundancy Redundant System Information : ------------------------------        Available system uptime = 3 weeks, 5 days, 3 hours, 56 minutes Switchovers system experienced = 0               Standby failures = 0         Last switchover reason = none                  Hardware Mode = Simplex     Configured Redundancy Mode = sso      Operating Redundancy Mode = sso               Maintenance Mode = Disabled                 Communications = Down      Reason: Simplex mode Current Processor Information : -------------------------------                Active Location = slot 5         Current Software state = ACTIVE        Uptime in current state = 3 weeks, 5 days, 3 hours, 56 minutes                  Image Version = Cisco IOS Software, s2t54 Software (s2t54-IPSERVICESK9-M), Version 15.0(1)SY2, RELEASE SOFTWARE (fc4) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2012 by Cisco Systems, Inc. Compiled Tue 10-Jul-12 13:35 by prod_rel_team                           BOOT =         Configuration register = 0x2102 Peer (slot: unavailable) information is not available because it is in 'DISABLED' state   redundancy  main-cpu   auto-sync running-config  mode sso   Core2: SW-CORE-2#show version Cisco IOS Software, s2t54 Software (s2t54-IPSERVICESK9-M), Version 15.0(1)SY2, RELEASE SOFTWARE (fc4) System image file is "bootdisk:s2t54-ipservicesk9-mz.SPA.150-1.SY2.bin"   SW-CORE-2#show redundancy Redundant System Information : ------------------------------        Available system uptime = 3 weeks, 5 days, 3 hours, 59 minutes Switchovers system experienced = 0               Standby failures = 0         Last switchover reason = none                  Hardware Mode = Simplex     Configured Redundancy Mode = sso      Operating Redundancy Mode = sso               Maintenance Mode = Disabled                 Communications = Down      Reason: Simplex mode Current Processor Information : -------------------------------                Active Location = slot 5         Current Software state = ACTIVE        Uptime in current state = 3 weeks, 5 days, 3 hours, 59 minutes                  Image Version = Cisco IOS Software, s2t54 Software (s2t54-IPSERVICESK9-M), Version 15.0(1)SY2, RELEASE SOFTWARE (fc4) Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2012 by Cisco Systems, Inc. Compiled Tue 10-Jul-12 13:35 by prod_rel_team                           BOOT =         Configuration register = 0x2102 Peer (slot: unavailable) information is not available because it is in 'DISABLED' state   redundancy  main-cpu   auto-sync running-config  mode sso     Module details: SW-CORE-1#show module Mod Ports Card Type                              Model              Serial No. --- ----- -------------------------------------- ------------------ -----------   1   24  CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAL160639E1   2   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6848-GE-TX     SAL1639NESE   5    5  Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G       SAL1638N0FC Mod MAC addresses                       Hw    Fw           Sw           Status --- ---------------------------------- ------ ------------ ------------ -------   1  c464.1304.8c88 to c464.1304.8c9f   5.1   12.2(18r)S1  15.0(1)SY2   Ok   2  30f7.0d7f.2b38 to 30f7.0d7f.2b67   1.0   12.2(18r)S1  15.0(1)SY2   Ok   5  e05f.b911.2e7f to e05f.b911.2e86   1.3   12.2(50r)SYS 15.0(1)SY2   Ok Mod  Sub-Module                  Model              Serial       Hw     Status ---- --------------------------- ------------------ ----------- ------- -------   1  Centralized Forwarding Card WS-F6700-CFC       SAL16095NK8  4.1    Ok   2  Distributed Forwarding Card WS-F6K-DFC4-A      SAL1638NBVJ  1.2    Ok   5  Policy Feature Card 4       VS-F6K-PFC4        SAL1638MUNU  1.2    Ok   5  CPU Daughterboard           VS-F6K-MSFC5       SAL1638MV1P  1.4    Ok Mod  Online Diag Status ---- -------------------   1  Pass   2  Pass   5  Pass   SW-CORE-2#show module Mod Ports Card Type                              Model              Serial No. --- ----- -------------------------------------- ------------------ -----------   1   24  CEF720 24 port 1000mb SFP              WS-X6724-SFP       SAL160639EE   2   48  CEF720 48 port 10/100/1000mb Ethernet  WS-X6848-GE-TX     SAL1637MPMS   5    5  Supervisor Engine 2T 10GE w/ CTS (Acti VS-SUP2T-10G       SAL1638N0EQ Mod MAC addresses                       Hw    Fw           Sw           Status --- ---------------------------------- ------ ------------ ------------ -------   1  c464.1304.8cb8 to c464.1304.8ccf   5.1   12.2(18r)S1  15.0(1)SY2   Ok   2  6073.5cd9.8a70 to 6073.5cd9.8a9f   1.0   12.2(18r)S1  15.0(1)SY2   Ok   5  c471.fe7c.ec56 to c471.fe7c.ec5d   1.3   12.2(50r)SYS 15.0(1)SY2   Ok Mod  Sub-Module                  Model              Serial       Hw     Status ---- --------------------------- ------------------ ----------- ------- -------   1  Centralized Forwarding Card WS-F6700-CFC       SAL16095VCA  4.1    Ok   2  Distributed Forwarding Card WS-F6K-DFC4-A      SAL1638NBUX  1.2    Ok   5  Policy Feature Card 4       VS-F6K-PFC4        SAL1638N3WY  1.2    Ok   5  CPU Daughterboard           VS-F6K-MSFC5       SAL1638N3BG  1.4    Ok Mod  Online Diag Status ---- -------------------   1  Pass   2  Pass   5  Pass   Interface Configuration Core 1: interface GigabitEthernet1/23  no ip address ! interface GigabitEthernet1/24  switchport  switchport trunk allowed vlan 10,20,30,101,102  switchport mode trunk interface GigabitEthernet5/1  switchport  switchport trunk allowed vlan 10,20,30,101,102  switchport mode trunk   Core 2: interface GigabitEthernet1/23  no ip address  spanning-tree guard loop ! interface GigabitEthernet1/24  switchport  spanning-tree guard root ! interface GigabitEthernet5/1  switchport  switchport trunk allowed vlan 10,20,30,101,102   Additional Questions: - Is it needed that the 2 6506-E switches are connected via supervisors uplink interfaces (slot 5 on this set-up, fa5/1-3 or tengig5/4-5) for SSO to work, or any interfaces on the modules can be used. Because, based on the curent set-up, they link the 2 6506-E switch using interfaces of module in slot 1 ( WS-X6724-SFP). - What other items I need to check in addition on above details?    TIA         ... View more