Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About navydivervet
08-21-2019
Stats
Member since
10-30-2007
38
Posts
0
Helpful
1
Solution
Created by
navydivervet
in Application Centric Infrastructure
in Application Centric Infrastructure
07-26-2019
08:26 AM
07-26-2019
08:26 AM
Is there existing/recommended documentation on verifying and testing, after an ACI deployment? I know this is a broad question, but was just looking for some good resources or methods...
... View more
Created by
navydivervet
in Application Centric Infrastructure
in Application Centric Infrastructure
05-31-2019
09:42 AM
05-31-2019
09:42 AM
Yes, I did register it. I believe that my issue is Layer 1 related. I'm remote, so I had to look around before identifying it. Having someone verify the Spine uplinks again...
... View more
Created by
navydivervet
in Application Centric Infrastructure
in Application Centric Infrastructure
05-27-2019
07:23 AM
05-27-2019
07:23 AM
APIC discovered only one of eight Leaf and Spine Switches. The apics do not have the CIMC port cabled, and has only one ethernet/oob mgmt port connected. On the CIMC, I've verified lldp disabled and the nic is in dedicated mode. Apics have formed cluster properly and are all fully fit. I've checked lldp bonding, wiped the switches, and tried every possible troubleshooting command imaginable. Switches do see the apics as lldp neighbors, but getting FSM-Failed message. I'm remote (so somewhat limited), but do have console connectivity. What's the effect on device discovery, of having only one ethernet port, and no CIMC connected?re both the CIMC not being connected? TAC has been silent/absent on assisting with this issue. Would appreciate any helpful advise... APIC version 14.0.2c Switch version 12.3 (future version 14.0.2c in apic repository)
... View more
Labels:
02-13-2019
09:47 AM
Appreciate your help, Jon. The 9500 stacks are in separate MDFs, with an L2 connection between them, with all vlans. The SVIs are configured in HSRP on the 9500s.
A 9300 is connected to each 9500, layer 2, with multiple vlans. The MPLS and LTE circuits are on different 9300s, in separate MDFs, on an access port to a single vlan.
I tried a major delay difference on the interfaces, which seemed to work for several days. Can't figure out why it recently jumped to the LTE path, when no changes were made.
The carrier may not be using the correct advertised networks, as they say they keep losing neighborship.
... View more
02-12-2019
10:44 AM
I have Cat 9500 as my Core/L3 device. The vendor router was not compatible with the sfp on the core switch, so it is connected to a downstream Cat 9300. The port is just an access port on vlan 82, for MPLS connectivity to a vendor router. Trying to use EIGRP to route all traffic through the MPLS circuit, but for some reason, it keeps routing to the other MDF, to the backup LTE circuit, which has the exact switch connectivity. Guess I'm questioning, or seeking an example of the proper EIGRP configs on the Core 9500, and the Cat 9300 switches
MDF 1)
Core 9500 connects to 9300 via L2 etherchannel
9300 connects to MPLS Vendor router, via access port vlan 82
MDF 2)
Core 9500 connects to 9300 via L2 etherchannel
9300 connects to LTE Vendor router, via access port vlan 82
MDFs are connected to each other via L2 etherchannel. Trying to get all traffic to route to MPLS, not LTE. Was routing properly, but changed for some unknown reason
... View more
02-12-2019
05:53 AM
Thanks for your help. No BGP. The 9300 Switch port is just configured for an access vlan 82, to the vendor router. On both the MPLS and LTE circuits.
MDF2SWI01#sh ip ei top EIGRP-IPv4 Topology Table for AS(100)/ID(10.80.70.17) Codes: P - Passive, A - Active, U - Update, Q - Query, R - Reply, r - reply Status, s - sia Status
P 10.80.52.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.80.43.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.80.38.0/24, 1 successors, FD is 2816 via Connected, Vlanx P 10.80.55.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.80.49.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.99.85.128/28, 1 successors, FD is 2816 via Connected, Vlan82 P 10.80.41.0/24, 1 successors, FD is 2816 via Connected, Vlan500 P 10.80.63.0/24, 1 successors, FD is 2816 via Connected, Vlan121 P 10.80.60.0/24, 1 successors, FD is 2816 via Connected, Vlan118 P 10.80.56.0/24, 1 successors, FD is 2816 via Connected, Vlan114 P 10.80.32.0/24, 1 successors, FD is 2816 via Connected, Vlan10 P 10.80.64.0/24, 1 successors, FD is 2816 via Connected, Vlan310 P 10.80.35.0/24, 1 successors, FD is 2816 via Connected, Vlan135 P 10.80.39.0/24, 1 successors, FD is 2816 via Connected, Vlan300 P 10.80.58.0/24, 1 successors, FD is 2816 via Connected, Vlan116 P 10.80.65.0/24, 1 successors, FD is 2816 via Connected, Vlan320 P 10.80.50.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.80.62.0/24, 1 successors, FD is 2816 via Connected, Vlan120 P 10.80.40.0/24, 1 successors, FD is 2816 via Connected, Vlan400 P 10.80.46.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.80.37.0/24, 1 successors, FD is 2816 via Connected, Vlan137 P 10.80.61.0/24, 1 successors, FD is 2816 via Connected, Vlan119 P 10.99.81.128/28, 1 successors, FD is 2816 via Connected, Vlan801 P 10.80.45.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.80.70.8/30, 1 successors, FD is 3072 via 10.80.32.130 (3072/2816), Vlan10 P 10.80.36.0/24, 1 successors, FD is 2816 via Connected, Vlan136 P 10.80.47.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.80.48.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 0.0.0.0/0, 1 successors, FD is 2562560256, tag is 65000 via 10.99.85.129 (2562560256/2562560000), Vlan82 P 10.80.42.0/24, 1 successors, FD is 2816 via Connected, Vlan200 P 10.80.33.0/24, 1 successors, FD is 2816 via Connected, Vlan20 P 10.80.57.0/24, 1 successors, FD is 2816 via Connected, Vlan115 P 10.80.54.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.50.192.218/32, 1 successors, FD is 82688, tag is 65000 via 10.99.85.130 (82688/82432), Vlan82 P 10.80.34.0/24, 1 successors, FD is 2816 via Connected, Vlan125 P 10.80.51.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.80.71.14/32, 1 successors, FD is 3328 via 10.80.32.130 (3328/3072), Vlan10 P 10.80.44.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10 P 10.80.66.0/24, 1 successors, FD is 2816 via Connected, Vlan333 P 10.80.59.0/24, 1 successors, FD is 2816 via Connected, Vlan117 P 10.80.70.0/30, 1 successors, FD is 3072 via 10.80.32.130 (3072/2816), Vlan10 P 10.80.53.0/24, 2 successors, FD is 3072 via 10.99.85.140 (3072/2816), Vlan82 via 10.80.32.252 (3072/2816), Vlan10
MDF2SWI01#sh ip route ei
Gateway of last resort is 10.99.85.129 to network 0.0.0.0
D*EX 0.0.0.0/0 [170/2562560256] via 10.99.85.129, 05:21:41, Vlan82 10.0.0.0/8 is variably subnetted, 65 subnets, 4 masks D EX 10.50.192.218/32 [170/82688] via 10.99.85.130, 05:05:33, Vlan82 D 10.80.43.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.44.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.45.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.46.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.47.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.48.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.49.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.50.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.51.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.52.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.53.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.54.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.55.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.70.0/30 [90/3072] via 10.80.32.130, 07:03:14, Vlan10 D 10.80.70.8/30 [90/3072] via 10.80.32.130, 07:03:14, Vlan10 D 10.80.71.14/32 [90/3328] via 10.80.32.130, 07:03:14, Vlan10
MDF2SWI01#sh ip route
Gateway of last resort is 10.99.85.129 to network 0.0.0.0
D*EX 0.0.0.0/0 [170/2562560256] via 10.99.85.129, 05:21:59, Vlan82 10.0.0.0/8 is variably subnetted, 65 subnets, 4 masks D EX 10.50.192.218/32 [170/82688] via 10.99.85.130, 05:05:51, Vlan82 C 10.99.81.128/28 is directly connected, Vlan801 L 10.99.81.141/32 is directly connected, Vlan801 C 10.99.85.128/28 is directly connected, Vlan82 L 10.99.85.141/32 is directly connected, Vlan82 C 10.80.32.0/24 is directly connected, Vlan10 L 10.80.32.253/32 is directly connected, Vlan10 C 10.80.33.0/24 is directly connected, Vlan20 L 10.80.33.253/32 is directly connected, Vlan20 C 10.80.34.0/24 is directly connected, Vlan125 L 10.80.34.253/32 is directly connected, Vlan125 C 10.80.35.0/24 is directly connected, Vlan135 L 10.80.35.253/32 is directly connected, Vlan135 C 10.80.36.0/24 is directly connected, Vlan136 L 10.80.36.253/32 is directly connected, Vlan136 C 10.80.37.0/24 is directly connected, Vlan137 L 10.80.37.253/32 is directly connected, Vlan137 C 10.80.38.0/24 is directly connected, Vlanx L 10.80.38.253/32 is directly connected, Vlanx C 10.80.39.0/24 is directly connected, Vlan300 L 10.80.39.253/32 is directly connected, Vlan300 C 10.80.40.0/24 is directly connected, Vlan400 L 10.80.40.253/32 is directly connected, Vlan400 C 10.80.41.0/24 is directly connected, Vlan500 L 10.80.41.253/32 is directly connected, Vlan500 C 10.80.42.0/24 is directly connected, Vlan200 L 10.80.42.253/32 is directly connected, Vlan200 D 10.80.43.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.44.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.45.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.46.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.47.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.48.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.49.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.50.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.51.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.52.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.53.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.54.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 D 10.80.55.0/24 [90/3072] via 10.80.32.252, 2w5d, Vlan10 [90/3072] via 10.99.85.140, 2w5d, Vlan82 C 10.80.56.0/24 is directly connected, Vlan114 L 10.80.56.253/32 is directly connected, Vlan114 C 10.80.57.0/24 is directly connected, Vlan115 L 10.80.57.253/32 is directly connected, Vlan115 C 10.80.58.0/24 is directly connected, Vlan116 L 10.80.58.253/32 is directly connected, Vlan116 C 10.80.59.0/24 is directly connected, Vlan117 L 10.80.59.253/32 is directly connected, Vlan117 C 10.80.60.0/24 is directly connected, Vlan118 L 10.80.60.253/32 is directly connected, Vlan118 C 10.80.61.0/24 is directly connected, Vlan119 L 10.80.61.253/32 is directly connected, Vlan119 C 10.80.62.0/24 is directly connected, Vlan120 L 10.80.62.253/32 is directly connected, Vlan120 C 10.80.63.0/24 is directly connected, Vlan121 L 10.80.63.253/32 is directly connected, Vlan121 C 10.80.64.0/24 is directly connected, Vlan310 L 10.80.64.253/32 is directly connected, Vlan310 C 10.80.65.0/24 is directly connected, Vlan320 L 10.80.65.253/32 is directly connected, Vlan320 C 10.80.66.0/24 is directly connected, Vlan333 L 10.80.66.253/32 is directly connected, Vlan333 D 10.80.70.0/30 [90/3072] via 10.80.32.130, 07:03:33, Vlan10 D 10.80.70.8/30 [90/3072] via 10.80.32.130, 07:03:33, Vlan10 D 10.80.71.14/32 [90/3328] via 10.80.32.130, 07:03:33, Vlan10
... View more
02-12-2019
05:23 AM
From Cat 9500 Cores, trying to reach MPLS circuit connected on adjacent Cat 9300. An additional pair of Cat 9500s and 9300 (in separate MDF), are connected to a backup LTE circuit. Routing keeps defaulting to LTE circuit, despite various routing and metric adjustments. Routers are vendor-managed and connectivity from switches are via access vlan. Thoughts/advice?
... View more
Labels:
11-12-2018
06:58 AM
Labels:
10-05-2018
06:42 AM
Another question... What should this 819 Router be connected to, on customer's internal network? It's managed by the ISP and the customer does not have a Router with an LTE nim. Can I just connect it to an internet switch and/or ASA? I'd like to establish a S2S vpn, but they only provided a /32 public ip
... View more
10-05-2018
06:12 AM
I'll give it a shot when I get on site. Really appreciate the help. Thanks!
... View more
10-05-2018
02:27 AM
Trying to reverse engineer installation. Customer intent was to use LTE circuit for internet and establish S2S vpn to corporate site. ISP installed Cisco 819 (see scrubbed config below). I see the Cell0 up, but unable to get Internet connectivity when connecting to router.
What's the best/proper device and method to connect to the 819? I have ISR 4331 (with no NIM for LTE), and an ASA 5500. Am I missing something more obvious?
***SCRUBBED CONFIG****
multilink bundle-name authenticated ! chat-script LTE "" "AT!CALL1" TIMEOUT 20 "OK" chat-script lte "" "AT!CALL" TIMEOUT 20 "OK" ! controller Cellular 0 lte modem link-recovery rssi onset-threshold -110 lte modem link-recovery monitor-timer 20 lte modem link-recovery wait-timer 10 lte modem link-recovery debounce-count 6 ! interface Loopback1234 description ### NEMO Router Home Address b ip address 1.2.3.4 255.255.255.255 ! interface Tunnel300 description DMNR tunnel template no ip address ip tcp adjust-mss 1390 ! interface Cellular0 ip address negotiated no ip unreachables ip flow monitor ipv4flow input ip flow monitor ipv4flow output ip mobile router-service roam ip mobile router-service collocated ccoa-only encapsulation slip load-interval 30 dialer in-band dialer idle-timeout 0 dialer enable-timeout 6 dialer string LTE dialer watch-group 1 async mode interactive ! interface FastEthernet0 switchport access vlan 200 no ip address ! interface FastEthernet1 switchport access vlan 200 no ip address ! interface Serial0 no ip address shutdown clock rate 2000000 ! interface Vlan200 ip address 10.10.10.129 255.255.255.240 ! router mobile ! ip ftp source-interface Cellular0 ip mobile secure home-agent 4.3.2.1 spi decimal 256 key ascii VzWNeMo algorithm hmac-md5 ip mobile router address 1.2.3.4 255.255.255.0 collocated single-tunnel home-agent 4.3.2.1 template Tunnel333 register extend expire 10 retry 3 interval 5 reverse-tunnel tunnel mode gre ! dialer watch-list 1 ip 5.6.7.8 0.0.0.0 dialer watch-list 1 delay route-check initial 30 dialer watch-list 1 delay connect 1 ! route-map DENY_PIP_SUBNETS deny 10 match tag 65000 ! route-map DENY_PIP_SUBNETS permit 20 ! route-map SET_TAG_65000 permit 10 set tag 65000 ! route-map clear-df permit 10 set ip df 0 ! line 3 script dialer LTE modem InOut no exec rxspeed 100000000 txspeed 50000000 ----------------------------------
#sho ip int br Interface IP-Address OK? Method Status Protocol Cellular0 222.222.222.202 YES IPCP up up FastEthernet0 unassigned YES unset up down FastEthernet1 unassigned YES unset up down FastEthernet2 unassigned YES unset administratively down down FastEthernet3 unassigned YES unset administratively down down GigabitEthernet0 unassigned YES unset administratively down down Loopback1234 1.2.3.4 YES TFTP up up Mobile0 unassigned YES unset up up Serial0 unassigned YES unset administratively down down Tunnel333 unassigned YES unset up down Vlan1 unassigned YES unset 10.10.10.129 YES TFTP down down
... View more
- Tags:
- lte
Labels:
Created by
navydivervet
in Switching
in Switching
09-16-2018
09:39 AM
09-16-2018
09:39 AM
I have two separate Cisco 9500 stacks, in different MDFs and servicing different IDFs. Each MDF will have own router, so connecting Cores via Layer 3 and have all Vlan SVIs with hsrp. When configuring stackwise, do I have to use a different domain number on each stack?
... View more
Labels:
Created by
navydivervet
in Policy and Access
in Policy and Access
03-26-2018
09:24 PM
03-26-2018
09:24 PM
Spine and Leaf Nodes accounting info is not showing up in ISE (TACACS Server). The authentication and authorization info is visible, but not the accounting
... View more
Labels:
Created by
navydivervet
in Policy and Access
in Policy and Access
03-26-2018
09:21 PM
03-26-2018
09:21 PM
ASDM access hangs at 52%, when using account with read-only access. Same account logs in fine via cli. Admin accounts also log in fine via ASDM. Using ISE TACACs for AAA
Device is Firepower 4110 / ASDM 7.8.2
... View more
Labels:
08-14-2019
Would I need to change the vpc priorities on the non-upgraded switch,
while both Sups are being chan...
08-13-2019
Understood, but with a VPC to another switch (active/active), Can I
accomplish this with Zero downti...
08-13-2019
Replacing dual Sup1s with Sup2s on Nexus 7010. Can someone provide a
brief, to the point procedure? ...
08-07-2019
Upgrading Sup1 Modules, to Sup2 on Nexus 7010 to 6.2(16) to 7.3(3)D1(1).
Can this be done via ISSU? ...
Created by
navydivervet
in Application Centric Infrastructure
07-26-2019
07-26-2019
Is there existing/recommended documentation on verifying and testing,
after an ACI deployment? I kno...
05-31-2019
Yes, I did register it. I believe that my issue is Layer 1 related. I'm
remote, so I had to look aro...
05-27-2019
APIC discovered only one of eight Leaf and Spine Switches. The apics do
not have the CIMC port cable...
02-13-2019
Appreciate your help, Jon. The 9500 stacks are in separate MDFs, with an
L2 connection between them,...
02-12-2019
I have Cat 9500 as my Core/L3 device. The vendor router was not
compatible with the sfp on the core ...
02-12-2019
Thanks for your help. No BGP. The 9300 Switch port is just configured
for an access vlan 82, to the ...
02-12-2019
From Cat 9500 Cores, trying to reach MPLS circuit connected on adjacent
Cat 9300. An additional pair...
10-05-2018
Another question... What should this 819 Router be connected to, on
customer's internal network? It'...
Public Statistics
| Date Registered | 10-30-2007 10:03 PM |
| Date Last Visited | 08-21-2019 12:28 AM |
| Total Messages Posted | 38 |
