Explore topic-wise InterviewSolutions in .

The overall BANDWIDTH of an EtherChannel interface depends on its ACTIVE member links. An EtherChannel with 8 active 100 Mbps links should indicate a bandwidth of 800 Mbps and, if one of its physical ports fails, the available bandwidth of port-channel interface will be evaluated as 700Mbps without FLAPPING the port-channel.

The overall bandwidth of an EtherChannel interface depends on its active member links. An EtherChannel with 8 active 100 Mbps links should indicate a bandwidth of 800 Mbps and, if one of its physical ports fails, the available bandwidth of port-channel interface will be evaluated as 700Mbps without flapping the port-channel.

Every switch series has its own set of recovery methods. Here you can DESCRIBE the procedure of PASSWORD recovery for the switches on which you have SHOWN your work experience. You can also refer following links to GET an idea of password recovery on well-known CISCO switches.

Every switch series has its own set of recovery methods. Here you can describe the procedure of password recovery for the switches on which you have shown your work experience. You can also refer following links to get an idea of password recovery on well-known Cisco switches.

If OSPF is CONFIGURED on low bandwidth links, IP-OSPF-Transmit-Delay is used to increase the time of the age field of a LSA update. By default it is SET to 1 second and, to make it effective, it MUST be added before transmission over a link.

If OSPF is configured on low bandwidth links, IP-OSPF-Transmit-Delay is used to increase the time of the age field of a LSA update. By default it is set to 1 second and, to make it effective, it must be added before transmission over a link.

This LOG MESSAGE pops up when an OSPF DBD exchange process USES a bad sequence number (DUE to packet loss or packet exploitation) for the synchronization of the database with its neighbors.

This log message pops up when an OSPF DBD exchange process uses a bad sequence number (due to packet loss or packet exploitation) for the synchronization of the database with its neighbors.

If BGP peer is in idle state then it could be due to PHYSICAL connectivity failure or neighbor is not defined with properly with respective AS. In CONNECT state, BGP tries to establish TCP session over port number 179 if it fails to establish TCP CONNECTION then it goes to Active state where it retries to establish TCP connection. By using debug ip bgp and debug ip tcp transactions commands, we can find out the EXACT cause of TCP connection failure. Lack of “update-source” or “ebgp-multihop” command can ALSO be a reason for neighbor active state;

If BGP peer is in idle state then it could be due to physical connectivity failure or neighbor is not defined with properly with respective AS. In connect state, BGP tries to establish TCP session over port number 179 if it fails to establish TCP connection then it goes to Active state where it retries to establish TCP connection. By using debug ip bgp and debug ip tcp transactions commands, we can find out the exact cause of TCP connection failure. Lack of “update-source” or “ebgp-multihop” command can also be a reason for neighbor active state;

It could be normal if it is less than 1% of total traffic on that interface with no packet drop

And it is recommended to resolve LINK issues in case CYCLIC redundancy check (CRC) ERRORS are more than 1% of the total interface traffic. The most COMMON reason for receiving CRC errors is the DUPLEX setting, as most of providers set their interface to “auto” mode.

It could be normal if it is less than 1% of total traffic on that interface with no packet drop

And it is recommended to resolve link issues in case cyclic redundancy check (CRC) errors are more than 1% of the total interface traffic. The most common reason for receiving CRC errors is the duplex setting, as most of providers set their interface to “auto” mode.

First we NEED to VERIFY the exact reason for failover; it could be due to physical or protocol issues. If it is a “protocol down” problem, then valid reasons could be link authentication failure, encapsulation mismatch, clock RATE not configured, improper access control, MTU or DUPLEX mismatch, ETC.

First we need to verify the exact reason for failover; it could be due to physical or protocol issues. If it is a “protocol down” problem, then valid reasons could be link authentication failure, encapsulation mismatch, clock rate not configured, improper access control, MTU or Duplex mismatch, etc.

This symptom is the sign of abnormal functionality in a router. FIRST we should know the exact reason for INCREASED CPU utilization, and we can use “show processes cpu ,” “show INTERFACE stat” COMMANDS to check the process utilizations. It could be due to high traffic FLOW (congestion), complex ACL or VPN deployments, ARP/TCP issues etc.

This symptom is the sign of abnormal functionality in a router. First we should know the exact reason for increased CPU utilization, and we can use “show processes cpu ,” “show interface stat” commands to check the process utilizations. It could be due to high traffic flow (congestion), complex ACL or VPN deployments, ARP/TCP issues etc.

PROXY FIREWALL.

Proxy firewall.

URL FILTERING.

URL Filtering.