Some Security Cisco Commands

本文深入解析网络设备配置细节,涵盖日志同步、传输协议禁用、SSH登录设置、VLAN接口配置、服务质量策略及错误禁用恢复等关键操作,旨在帮助网络工程师优化设备性能与安全性。

line con 0
logging synchronous ##### 开启日志同步,如果不敲这条命令,自动弹出日志的时候如果你在配置设备,你就会发现日志信息会把你敲入的命令分隔开,影响输入。敲上这条命令之后日志信息不会分隔你敲到一半的命令行。
transport preferred none #### https://blog.51cto.com/xpvista/177844 , 线上不允许任何协议选择。系统通常假设不认识的命令为主机名。如果协议设置为none,则系统不再作这个假设,不认识的命令不能建立连接。
line vty 0 4
logging synchronous
transport preferred none
transport input ssh
line vty 5 15
password 7 045802150C2E
logging synchronous
transport input none
!
ip telnet source-interface Vlan10
ip ftp source-interface Vlan10
ip tftp source-interface Vlan10
ip ssh time-out 60
ip ssh source-interface Vlan10
ip ssh version 2
!

logging trap notifications ## https://zhidao.baidu.com/question/1733168285133876827.html ,logging trap debugging 指定日志级别,可选的级别有0-7共八个级别,0最高,7最低。这八个级别分别为:
logging source-interface Vlan10
logging host 10.50.51.

interface Vlan10
ip address 10.45.38. 255.255.255.0
no ip redirects ### https://blog.youkuaiyun.com/a9254778/article/details/7308484 ,
no ip unreachables
no ip proxy-arp
!

interface GigabitEthernet0/2
description Uplink
switchport trunk encapsulation dot1q
switchport mode trunk
switchport nonegotiate
srr-queue bandwidth share 1 70 25 5
priority-queue out
udld port aggressive
mls qos trust dscp
ip dhcp snooping trust

interface FastEthernet0/48
switchport access vlan 185
switchport mode access
switchport voice vlan 186
no logging event link-status
srr-queue bandwidth share 1 70 25 5
priority-queue out
no snmp trap link-status
spanning-tree portfast
service-policy input edge_edge_edge_edge_qos_marking
!

class-map match-all video_payload
match access-group name acl_video_payload
class-map match-all voice_payload
match access-group name acl_voice_payload
class-map match-all voice_control
match access-group name acl_voice_control
!
policy-map edge_edge_edge_edge_qos_marking
class voice_control
set ip dscp cs3
police 1000000 8000 exceed-action drop
class voice_payload
set ip dscp ef
police 1000000 8000 exceed-action drop
class video_payload
set dscp 63
!
vlan internal allocation policy ascending
!
errdisable recovery cause udld
errdisable recovery cause bpduguard
errdisable recovery cause security-violation
errdisable recovery cause channel-misconfig (STP)
errdisable recovery cause pagp-flap
errdisable recovery cause dtp-flap
errdisable recovery cause link-flap
errdisable recovery cause sfp-config-mismatch
errdisable recovery cause gbic-invalid
errdisable recovery cause l2ptguard
errdisable recovery cause psecure-violation
errdisable recovery cause port-mode-failure
errdisable recovery cause dhcp-rate-limit
errdisable recovery cause mac-limit
errdisable recovery cause vmps
errdisable recovery cause storm-control
errdisable recovery cause inline-power
errdisable recovery cause arp-inspection
errdisable recovery cause loopback
errdisable recovery cause small-frame
errdisable recovery interval 30
!
no dot1x logging verbose
!
mls qos queue-set output 1 threshold 1 200 200 50 400
mls qos queue-set output 1 threshold 2 400 400 50 400
mls qos queue-set output 1 buffers 10 50 20 20
no mls qos rewrite ip dscp
mls qos
epm access-control Open
!
ip dhcp snooping vlan 1,185-186
no ip dhcp snooping information option
ip dhcp snooping
ip device tracking probe use-svi
ip device tracking probe delay 10
ip device tracking
!
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug datetime msec localtime
service timestamps log datetime msec localtime
service password-encryption
!

# snmp_exporter ## Getting started To make it easy for you to get started with GitLab, here's a list of recommended next steps. Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)! ## Add your files - [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files - [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command: ``` cd existing_repo git remote add origin https://10.6.80.1/ops/snmp_exporter.git git branch -M main git push -uf origin main ``` ## Integrate with your tools - [ ] [Set up project integrations](https://10.6.80.1/ops/snmp_exporter/-/settings/integrations) ## Collaborate with your team - [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/) - [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html) - [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically) - [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/) - [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html) ## Test and Deploy Use the built-in continuous integration in GitLab. - [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html) - [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/) - [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html) - [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/) - [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html) *** # Editing this README When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template. ## Suggestions for a good README Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information. ## Name Choose a self-explaining name for your project. ## Description Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors. ## Badges On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge. ## Visuals Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method. ## Installation Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection. ## Usage Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README. ## Support Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc. ## Roadmap If you have ideas for releases in the future, it is a good idea to list them in the README. ## Contributing State if you are open to contributions and what your requirements are for accepting them. For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self. You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser. ## Authors and acknowledgment Show your appreciation to those who have contributed to the project. ## License For open source projects, say how it is licensed. ## Project status If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers. 翻译以上内容 并总结使用方法
最新发布
09-04
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符  | 博主筛选后可见
 
红包 添加红包
表情包 插入表情
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值