ARCHITECTURE TECHNOLOGY CORPORATION CRR-1000 Manuel de démarrage rapide - Page 5
Parcourez en ligne ou téléchargez le pdf Manuel de démarrage rapide pour {nom_de_la_catégorie} ARCHITECTURE TECHNOLOGY CORPORATION CRR-1000. ARCHITECTURE TECHNOLOGY CORPORATION CRR-1000 18 pages.
Imprimer la pageCRR-1000 Quick Start Guide
inet 127.255.0.1/32 scope host lo
valid_lft forever preferred_lft forever
inet 10.255.255.10/32 scope global lo.master
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP group default qlen 1000
link/ether 08:00:27:b2:4a:fe brd ff:ff:ff:ff:ff:ff
inet 192.168.10.254/24 brd 192.168.10.255 scope global eth0.primary
valid_lft forever preferred_lft forever
inet 192.168.100.254/24 brd 192.168.100.255 scope global eth0
valid_lft forever preferred_lft forever
inet6 fe80::a00:27ff:feb2:4afe/64 scope link
valid_lft forever preferred_lft forever
3.2 ICMP Echo (ping)
An ICMP echo (ping) message can be generated from the CRR-1000 router with the "ping" command,
e.g.:
admin@CRR> ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1) 56(84) bytes of data.
64 bytes from 192.168.100.1: icmp_seq=1 ttl=255 time=1.48 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=255 time=0.722 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=255 time=0.667 ms
64 bytes from 192.168.100.1: icmp_seq=4 ttl=255 time=0.724 ms
--- 192.168.100.1 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3006ms
rtt min/avg/max/mdev = 0.667/0.899/1.484/0.339 ms
3.3 Logging Information
3.3.1 Security-Related Logging (show audit)
Audit logs contain information related to security events such as login attempts, service restarts, and
changes to the system that may have security implications. Audit logs are accessed with the "show audit"
command that takes as its single argument the corresponding audit log to be displayed. E.g.,
admin@CRR> show audit
auth.log
3.3.2 Platform Logging (show log)
Platform-specific log information is accessed with the "show log" command that takes as its single
argument the corresponding platform-specific log file to be displayed. E.g.,
admin@CRR> show log
kern.log
Tab
firewall.log
general.log
Tab
local.log
syslog
ipsec.log
user.log
3
remote