Mejores practicas configuraciones Cisco - No Redistribution Metrics Defined for EIGRP

No Redistribution Metrics Defined for EIGRP

Excepción	No Redistribution Metrics Defined for EIGRP
Categoria	EIGRP
Tipo OS	IOS
Riesgo	Medio
Descripción	When configuring redistribution into EIGRP always define the metrics that EIGRP should use with the metric or default-metric keywords. Each protocol uses different metrics so it is important to define the parameters the EIGRP should use. EIGRP needs five metrics defined when redistributing other protocols: bandwidth, delay, reliability, load, and MTU. The redistribution of IGRP/EIGRP into another IGRP/EIGRP process does not require any metric conversion, so there is no need to define metrics or use the default-metric command during redistribution in these cases.
Recomendación	"For example, when configuring rip redistribution into EIGRP, add metrics in one of the following two ways: router eigrp 1 redistribute rip metric 10000 100 255 1 1500 or router eigrp 1 redistribute rip default-metric 10000 100 255 1 1500 Note: Values ""10000 100 255 1 1500"" were used as an example. Other values may be used in your environment. The general formats under EIGRP are: redistributemetric or default-metric
URL de referencia	Redistributing Routing Protocols
Acción correctiva	Define metrics when redistributing into EIGRP with the metric or default-metric keywords.
Advertencia	The redistribution of IGRP/EIGRP into another IGRP/EIGRP process does not require any metric conversion, so there is no need to define metrics or use the default-metric command during redistribution in these cases.

Más "Mejoras de practicas de configuraciones Cisco" AQUÍ

Sígueme también en:

Facebook | Twitter | Google +

Mejores practicas configuraciones Cisco - No EIGRP router-id configured

No EIGRP router-id configured

Excepción	No EIGRP router-id configured
Categoria	EIGRP
Tipo OS	IOS
Riesgo	Medio
Descripción	The router ID is set to the IP address of a loopback interface if one is configured. If no loopback interfaces are configured, the router ID is set to the highest IP address configured on a physical interface. To ensure deterministic behavior the EIGRP router-id should be configured to a chosen address. If a router id isn't set for EIGRP, it is possible that duplicate router ids will prevent external EIGRP routes from being installed in the topology table. To have deterministic behavior, an EIGRP router id should be created on all EIGRP speaking devices.
URL de Referencia	Preventing Duplicate Router Ids
Acción correctiva	Configure the router id, with the "eigrp router-id" command.

Más "Mejoras de practicas de configuraciones Cisco" AQUÍ

Mejores practicas configuraciones Cisco-EIGRP MD5 Disabled on Interface

EIGRP MD5 Disabled on Interface

Excepción	EIGRP MD5 Disabled on Interface
Categoria	EIGRP;Security
Tipo OS	IOS
Riesgo	Medio
Descripción	This rule detects if EIGRP authentication is configured on an EIGRP enabled interface.
Recomendación	It is recommended to apply MD5 authentication that will permit the receipt of EIGRP packets only from authorized hosts on each EIGRP interface.
Referencia URL	Configuring EIGRP Route Authentication
Acción correctiva	Enable EIGRP authentication.
Advertencia	In some scenarios, there may be many EIGRP-enabled interfaces that do not have EIGRP neighbors. MD5 authentication is not required in this situation but the interfaces should be passive.

Más "Mejoras de practicas de configuraciones Cisco" AQUÍ

Mejores practicas configuraciones Cisco - Default EIGRP Passive Interface not configured

Default EIGRP Passive Interface not configured

Excepción	Default EIGRP Passive Interface not configured.
Categotia	EIGRP
Tipo OS	IOS
Riesgo	Medio
Descripción	In large service provider and Enterprise networks, some distribution-layer routers often have a large number of interfaces, for example, at the WAN edge. A common practice to facilitate the configuration of a routing protocol on such routers is to enable the routing processes on a network range matching several of the interfaces. While this technique facilitates the configuration of the routing protocol, enabling routing indiscriminately on several or all interfaces may increase the chances for the insertion of unauthorized routing peers. Also, unnecessary routing protocol exchanges increase CPU overhead on the router. To prevent these problems, one can set all interfaces as passive by default with the 'passive-interface default' command. This command changes the configuration logic to a default passive; therefore, interfaces where router adjacencies are expected need to be configured with the 'no passive-interface' command. Setting an interface as passive disables the sending of routing updates on that interface; hence, adjacencies will not be formed in Open Shortest Path First (OSPF) or Enhanced Interior Gateway Routing Protocol (EIGRP). However, the particular subnet will continue to be advertised to other interfaces.
Acciones correctivas	"Under the 'router eigrp' block of configuration, configure the following. The parameters in front of the 'no passive-interface' command are those interfaces that need to participate in EIGRP and form router adjacencies.    passive-interface default    no passive-interface    no passive-interface    no passive-interface
Advertencia	In routers that have a small number of interfaces, you can choose to manually set the 'passive-interface' command on the interfaces where adjacency is not desired, instead of using the 'passive-interface default' command. Also, the rule does not apply if all layer 3 interfaces are designed to participate in the EIGRP domain.

Más "Mejoras de practicas de configuraciones Cisco" AQUÍ

Mejores practicas configuraciones Cisco - EIGRP auto summarization enabled (default enabled)

EIGRP auto summarization enabled (default enabled)

Excepción	EIGRP auto summarization enabled (default enabled)
Categoria	EIGRP
Tipo OS	IOS
Riesgo	Alto
Descripción	"EIGRP will automatically summarize on classful routing boundaries. Auto summarization can cause a routing partition under certain circumstances particularly with classful IP routing and where IP addresses are split. The default behavior of EIGRP auto-summarization changed in Cisco IOS Releases 15.0(1)M, 12.2(33)SRE, 12.2(33)XNE, 12.2(33)SXI4 and later releases to be disabled by default."
Acción correctiva	router eigrp no auto-summary URL de referencia: EIGRP auto summarization enabled

Más "Mejoras de practicas de configuraciones Cisco" AQUÍ

Mejores practicas configuraciones Cisco - BGP Consistency Check not enabled

BGP Consistency Check not enabled

Excepción	BGP Consistency Check not enabled
Categoria	BGP;IP routing
Tipo OS	IOS
Riesgo	Medio
Descripción	"A BGP route inconsistency with a peer occurs when an update or withdraw is not sent to a peer, resulting in black-hole routing. BGP Consistency checker will check for inconsistencies in a configurable interval. Once the process identifies such an inconsistency, it will report the inconsistency with a syslog message, and optionally take action if the auto-repair keyword is specified. Three options are available: Next-Hop Label Consistency Check RIB-Out Consistency Check Aggregation Consistency Check Next Hop Label Consistency Check: When two paths have the same next hop because they are advertised by the same provider edge router (PE), they should also have the same next-hop label. If the labels are different, there is an inconsistency. If the auto-repair keyword is specified, the system will send a route-refresh request. RIB-Out Consistency Check: If a network passes an outbound policy and is not sent, or if a network does not pass an outbound policy and is sent, there is an inconsistency. If the auto-repair keyword is specified, the system will send a route-refresh request. Aggregation Consistency Check: f specific routes and the aggregated route become out of sync, an inconsistency can occur. Either the error-message keyword or the auto-repair keyword will trigger aggregation reevaluation."
Acción Correctiva	! bgp consistency-checker {error-message | auto-repair} [interval minutes] ! error-message :System to generate an error message when an inconsistency is observed. auto-repair : System generates a syslog and also takes an action based on the inconsistency found. interval : Range is from 5 to 1440 minutes. Interval defaults to 1440 (One Day)
Advertencia	"This is applicable for IOS 15.1(2)S Cisco IOS XE 3.3S."

Más "Mejoras de practicas de configuraciones Cisco" AQUÍ

Análisis de las mejores prácticas en configuraciones Cisco

Introducción:

Este apartado, va referido a las recomendaciones que hace Cisco en cuanto a las mejores prácticas en cuanto a las configuraciones de equipamiento Cisco.

Categoria	Riesgo	Excepción	OS
BGP	Medio	BGP Consistency Check not enabled	IOS
EIGRP	Alto	EIGRP auto summarization enabled (default enabled)	IOS
EIGRP	Medio	Default EIGRP Passive Interface not configured.	IOS
EIGRP	Medio	EIGRP MD5 Disabled on Interface	IOS
EIGRP	Medio	No EIGRP router-id configured	IOS
EIGRP	Medio	No Redistribution Metrics Defined for EIGRP	IOS
IP Applications	Medio	HSRP Preempt delay not configured	IOS
IP Applications	Medio	NTP not protected by ACL	IOS
IP Applications	Medio	Standby delay minimum reload not configured	IOS
IP Applications	Bajo	NTP Update Calendar Disabled	IOS
IP Applications	Bajo	NTP authentication not enabled	IOS
IP Applications	Bajo	NTP enabled without time zone	IOS
IP Applications	Bajo	NTP source interface not defined	IOS
IP Applications	Bajo	NTP summertime not enabled	IOS
IP Applications	Bajo	No redundant NTP server	IOS
IP Routing	Medio	IOS Static Route Missing Parameters	IOS
IP Routing	Medio	Recursive static routes are present	IOS
IP Routing	Bajo	IP Classless disabled	IOS
IP Routing	Bajo	Name Parameter Missing from Static Routes	IOS
IP Routing	Bajo	NetBIOS UDP broadcasts enabled	IOS
Infrastructure	Alto	Cisco IOS Image Verification	IOS
Infrastructure	Low	Exec enabled on line aux	IOS
LAN	Alto	Spanning-tree disabled on one or more VLANs	IOS
LAN	Medio	BPDU Guard Not Enabled	IOS
LAN	Medio	Loopguard not configured	IOS
LAN	Medio	MAC address move notification not enabled	IOS
LAN	Medio	Portfast not enabled on access or edge port	IOS
LAN	Medio	UDLD Globally Disabled	IOS
LAN	Medio	VLANs not cleared from trunk	IOS
LAN	Medio	VTP domain name not set	IOS
LAN	Bajo	Complete Power-on Diagnostics Disabled	IOS
LAN	Bajo	Dynamic trunking is enabled on a static access port	IOS
LAN	Bajo	StackWise SNMP Traps Not Enabled	IOS
Management	Medio	CDP disabled on an interface	IOS
Management	Medio	Logging to the console is enabled	IOS
Management	Medio	Loopback interface not used	IOS
Management	Medio	SNMP server memory traps not enabled	IOS
Management	Medio	Syslog level not set to informational	IOS
Management	Medio	WarmStart SNMP Traps Not Enabled	IOS
Management	Bajo	CPU Thresholding Notification is not enabled.	IOS
Management	Bajo	ColdStart SNMP Traps Not Enabled	IOS
Management	Bajo	Configuration Management SNMP Traps Not Enabled	IOS
Management	Bajo	Interface level syslog events not disabled	IOS
Management	Bajo	Interface traps not disabled on at least one interface	IOS
Management	Bajo	Linkup and Linkdown SNMP Traps Not Enabled	IOS
Management	Bajo	Memory Threshold Notifications (I-O) Not Enabled	IOS
Management	Bajo	Memory Threshold Notifications (Processor) Not Enabled	IOS
Management	Bajo	Nagle service disabled	IOS
Management	Bajo	No interface description	IOS
Management	Bajo	No redundant SNMP trap receiver	IOS
Management	Bajo	No redundant syslog server	IOS
Management	Bajo	SNMP Interface Index Persistence not enabled	IOS
Management	Bajo	SNMP contact not defined	IOS
Management	Bajo	SNMP location not defined	IOS
Management	Bajo	SNMP trap source not defined	IOS
Management	Bajo	SNMP traps not enabled	IOS
Management	Bajo	Syslog source interface not defined	IOS
Management	Bajo	The Call Home feature is not configured	IOS
Management	Bajo	The Enhanced Crashinfo File Collection feature is not configured.	IOS
Management	Bajo	Timestamping for debugging not set for datetime	IOS
Management	Bajo	Timestamping for logging not set for datetime	IOS
Management	Bajo	Unnecessary Syslog SNMP trap configured	IOS
Security	Alto	Enable password not adequately protected	IOS
Security	Alto	SNMP access for IPv4 is not protected with an access-list.	IOS
Security	Alto	The aaa authentication login command(s) is/are not configured optimally.	IOS
Security	Alto	Vlan 1 interface used	IOS
Security	Medio	AAA connection accounting disabled	IOS
Security	Medio	AAA system accounting disabled	IOS
Security	Medio	DHCP server enabled	IOS
Security	Medio	HSRP Updates not authenticated	IOS
Security	Medio	HSRP Virtual MAC Address not modified	IOS
Security	Medio	HTTP secure-server is enabled.	IOS
Security	Medio	HTTP server enabled	IOS
Security	Medio	ICMP redirects not disabled on an Interface	IOS
Security	Medio	IOS Software Resilient Configuration secure boot-config disabled	IOS
Security	Medio	Local user account is not protected against potential brute-force attacks	IOS
Security	Medio	PAD service enabled	IOS
Security	Medio	SNMPv3 not used	IOS
Security	Medio	SSH Not Used or Not Used Exclusively for Remote Access.	IOS
Security	Medio	SSH V2 not used for device Access	IOS
Security	Medio	Security Password Minimum Length Less Than 8	IOS
Security	Medio	Unicast reverse path disabled	IOS
Security	Medio	VTY line timeout disabled	IOS
Security	Medio	VTY line timeout is longer than 30 mins	IOS
Security	Medio	VTY lines not protected with an access list	IOS
Security	Bajo	A user account is not protected with MD5	IOS
Security	Bajo	Authentication SNMP Traps Not Enabled	IOS
Security	Bajo	BOOTP server enabled	IOS
Security	Bajo	CDP is enabled globally and active on all interfaces.	IOS
Security	Bajo	DHCP lease time low or infinite	IOS
Security	Bajo	ICMP unreachables enabled on all interfaces of this device.	IOS
Security	Bajo	IP Source Routing enabled	IOS
Security	Bajo	IP options allowed	IOS
Security	Bajo	Incorrectly entered commands will generate a DNS lookup.	IOS
Security	Bajo	Password recovery is Enabled	IOS
Security	Bajo	Proxy ARP is enabled	IOS
Security	Bajo	Redundant AAA server unavailable	IOS
Security	Bajo	Security authentication failure rate disabled	IOS
Security	Bajo	Service sequence-numbers not enabled	IOS
Security	Bajo	TACACS+ packets not being sourced from a specifically defined interface	IOS
Security	Bajo	TCP keepalives not enabled in both directions	IOS