network_stuff:cisco:ios
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| network_stuff:cisco:ios [2022/09/06 18:47] – external edit 127.0.0.1 | network_stuff:cisco:ios [2024/10/02 11:48] (current) – jotasandoku | ||
|---|---|---|---|
| Line 48: | Line 48: | ||
| __**COPY FILES FROM AND TO LINUX BOX**__\\ | __**COPY FILES FROM AND TO LINUX BOX**__\\ | ||
| ** scp needs to be enabled in the switch. Also in some cases this aaa needs to be in for authentication ** | ** scp needs to be enabled in the switch. Also in some cases this aaa needs to be in for authentication ** | ||
| + | \\ | ||
| + | Regarding TFTP, remember that it uses udp-69 just for the initial message but then it uses 64001 through 65000 as ports are specific per each session (both in src and dst). | ||
| + | |||
| aaa new-model | aaa new-model | ||
| aaa authentication login default local | aaa authentication login default local | ||
| Line 379: | Line 382: | ||
| Netflow status: | Netflow status: | ||
| show platform hardware capacity netflow | show platform hardware capacity netflow | ||
| + | show mls sampling | ||
| + | show ip flow export # To see see Netflow packets being exported from router | ||
| + | show mls nde # Netflow Data Export | ||
| + | show mls netflow table-contention summary # To see if there is excessive Netflow CAM Utilization (and potential buffer overflows) | ||
| + | |||
| | | ||
| \\ | \\ | ||
| Line 388: | Line 396: | ||
| show ip cef < | show ip cef < | ||
| show ip cef exact-route <src> <dst> | show ip cef exact-route <src> <dst> | ||
| + | show ip cef 10.1.93.0/ | ||
| [[http:// | [[http:// | ||
| * receive: for connected IP subnets for the base address of the IP subnet and for the local IP address in the IP subnet. | * receive: for connected IP subnets for the base address of the IP subnet and for the local IP address in the IP subnet. | ||
| Line 543: | Line 552: | ||
| + | ---- | ||
| + | ==== CISCO DNAC AND NDO ==== | ||
| + | ( CATALYST CENTER AND NEXUS DASHBOARD ORCHESTRATOR ) | ||
| + | |||
| + | * You cannot run Catalyst Centre (DNAC) and NDO on the same VM/ Appliance. | ||
| + | * Cisco have DNAC/ NDO appliances which are built on UCS platforms but sold as appliances (bundled h/w s/w). | ||
| + | === DNAC platform support=== | ||
| + | * DNAC offers flexible deployment options. It can be deployed on a hardware appliance or as a virtual appliance, on either VMware ESXi or AWS. | ||
| + | * DNAC can be run as 1 node 3 or 5 node clusters – base level is 1 node for **lifecycle and assurance** (recommend 3+nodes for fabric deployments) [[https:// | ||
| + | === NDO platform support === | ||
| + | * NDO Cisco Nexus Dashboard portfolio comprises physical, virtual, and cloud form factors also – base level is 1 to 3 nodes (up to 9 in a cluster) | ||
| + | * [[https:// | ||
| + | * [[https:// | ||
| + | * NOTE: Onboarding standalone switches is supported only on 3-node physical clusters. | ||
network_stuff/cisco/ios.1662490020.txt.gz · Last modified: (external edit)
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
