Monday, May 14, 2012

Cisco Career Certification Complete Reference

A Complete Reference to Cisco Career Certification Tracks !

Which Track are you following ?




I hope this will be informative for you !

Cheers :)

Saturday, April 28, 2012

Power Sensor of Board 1220 Failed :: Huawei NE40E

Whenever there is problem with the physical entity or it goes failed so the board cannot work normal and it may results in services interruption. You will face such problem when the power-on sensor board is faulty.

I will talk about the troubleshooting process, how we can find out, where & what is the problem, here we go:

First Step, Login in to your NE40E and issue the following command to check whether “MonitorBus Version” is older than 19 or the softeware version is older than 3.6

display version

If it so then use the following commands to upgrade both

upgrade lpu 1 startup monitorbus // to upgrade s/w version
upgrade lpu by-testbus 1 startup mbus_epld // to upgrade the logical version

Now check the problem is resolve or not. If it is not resolve then perform the following task where we will turn-off and turn-on the power modules to check the master and slave behavior:

power off slot 1 //Power off the board
power on slot 1 //Power on the board

If you see that the problem is resolved means all the trap alarms are cleared in NE40E so this indicates that there is problem with the power supply which needs to be replaced but if still the trap alarms are there in NE40E then you have to send some detail information from NE40E like “display trapbuffer”, “terminal monitor” and “terminal trapping” which will be studied in detail to find the root cause for the problem.

I Hope this will be informative for you.

Wednesday, April 25, 2012

8-Step Design Process

Link to my previous post of "Network Design" where i talk about the first 3-stpes and promise was done about the 4th-stpe where i will talk about the 8-stpe design process.

1. Recognize Customer Needs
2. Describe the Existing Network
3. Design Networking & Topology Solution
4. Plan the Network Implementation
5. Construct a Prototype Network
6. Fully Document the Design
7. Implement the Design
8. Verify, Monitor & Modify as Needed

1. Recognize Customer Needs
1.1 Scope Assessment
1.2Gathering the Necessary Data
1.3 Identifying Organizational Goals
1.4 Identifying Organizational Limits
1.5 Identifying Application & Services
1.6 Reaching Technical Goals
1.7 Identifying Technical Constraints

a) Scope
New v/s Existing
Entire or Subnet Modular
LAN, WAN, VoIP, Security
OSI, NAT, IP Addressing

b) Gathering the Necessary Data
Mostly we do from existing documents, anyhow we either ask for RFP or RFI.
RFP (Request for Proposal) – We normally request from vendor, companies etc while RFI (Request for Information) – When we want to install new product & we ask vendor for it. Meanwhile we can also use RFI and RFP to query for customer existing, draft documents.

c) Identifying Organizational Goals
Organizational long term, short term goals
Define Success
Lower expenses and more services
Gain competitive edge
Flexible & Reliable
Utilizing, Reducing, Increasing, Improve, Enhancing, Boosting and Broadening (Information for Stockholders)

d) Identifying Organizational Limits
Budget & Training, License, everything, Different Areas
People & Trained People Experts, If need additional Training – Contractor or Outsourcing
Policies – Vendor Policies used, Procedures
Time – You have good PM, Experience, time to meat, deadline etc

e) Identifying Application & Services
Application category, Application choice, Level etc
Like E-mail, Productivity, Voice, Web, DB, Customer Services, Security, QoS, IP Multicasting, Management etc

f) Reaching Technical Goals
Maximum Performance & Productivity
Enhance Security
Achieve Reliability for Critical Core Application
Reduce Downtime
Update Obsolete: Hardware &/or Software
Boost Network Scalability
Simple Network Management

g) Identifying Technical Constraints
Limitation of Existing Equipment
Availability of existing equipment
Compatibility of Application
Adequacy of Trained Personnel

2. Existing Network Topology
L-3 Topology & L-2 Topology - Check everywhere and documents this
Network Services – NAT, ACL, Protocol, Frame Relay/ATM, Backup Path, IP etc
Network Application – Web, FTP, Mail, Chat/IM, IP Telephony etc
Modular Map – Network Management, Internet Module, WAN, Internal Server Farm, Backbone etc
Collect Audit Report like Router Model, CPU Memory, Utilization, IOS Version, Router-Config, Routing Table, Module/slots, report etc. We can use below command, which will generate output of many commands almost:
Router # show tech-support

3. Designed Network & Topology Solution



4. Plan the Network Implementation
Have a step-by-step Procedure
Well documented & detailed
Include other staff and consultant
Consider Possible Pitfalls
Test at every step in the process
Break down complex procedure into chunks

5. Construct a Prototype Network
Pilot or Prototype - Pilot (From Scratch) & Prototype (Test, Verify and re-design)
Prototype is preferable
Bottom-Line: Test the Design
Two possible result: Success or Failure

6. Fully Document Outline

7. 8-Step Design Method

8. For Implementation, verify, monitor, & Modify - Further study at Routing and Switching (CCNP-CCIE) Level

I Hope this will be informative for you :)

Sunday, April 15, 2012

Bidirectional Forwarding Detection (BFD)

Bidirectional Forwarding Detection (BFD) is a network protocol used to detect link failure between two nodes. This is great features used for link detection as it even detect failure for you on Layer-1 where mostly detection is not possible like on VC, tunnels, MPLS-LSP, Ethernet etc.

When BFD session is establishes between two nodes, & if there are more than twlo links exists b/w that two nodes so BFD can be used to monitor the session for these two nodes. BFD does not have a discovery mechanism, sessions must be explicitly configured between endpoints. For example, on Huawei NE40E, we can do like:

bfd to-NameOfNode-001 bind peer-ip default-ip interface GigabitEthernet1/1/1
discriminator local 809
discriminator remote 908
min-tx-interval 60
min-rx-interval 60
process-interface-status
commit


BFD may &/or can be used on many different transport mechanisms and layers. For this it needs to be encapsulated by whatever transport it uses. For example, MPLS-LSP, OSPF, IS-IS Protocols that support some form of adjacency setup.

BFD can be used in either asynchronous mode and demand mode.

I hope this will be informative for you.

Cheers :)

Wednesday, February 8, 2012

BFD Session status Changes to Down & Up

While working on DataCom Network (composed of hundreds of NE routers, configured with MPLS, IS-IS, QoS, MPLS-VPN, MPLS-TE, BGP and list goes on and on……..!, I saw this alarm “BFD Session status Changes to down” and “BFD Session status changes to up”. After doing some research, studying and help, I came to know about the root cause and main reason for this alarm.

There can be different reason for alarm to appear:

1. The status of the interface goes down on which the BFD session is established between the two peers.

2. The BFD peer session is deleted or shutdown explicitly.

3. The link is not able to forward packets because of congestion or may be the link status is down.

In my case it was NSA (Non-Service Affecting) and I just need to confirm the status so for that we need to remember few commands which are:


display interface [interface name]


display bfd session all

There are bundle of more commands, if you need any help regarding that please feel free to reach me.

Note: If you are not familiar about BFD? Wait for my next blog on BFD

I Hope this will be informative for you :)

Multiprotocol Label Switching Fast Reroute (MPLS FRR)

In actual MPLS FRR is a feature of RSVP-TE, it is also called MPLS local restoration or MPLS local protection. MPLS FRR gives protection to the LSP path in a network where each LSP is protected by backup path. The node which redirects traffic after path failure to the backup path is known as Point of Local Failure (PLR) and the node where backup LSP merger with primary LSP is called Merge Point (MP). This protection is purely local as compare to protection which is enable at IP Layer (Layer-3) which take a bit more time then this which is not acceptable in real time application (VoIP, Video Conferencing etc). This local protection takes even less than 50 ms.

There are two types of protection approaches:

1. One-to-One Local Protection

In one-to-one approach, PLR maintain a separate path for each LSP across the path or network. This method creates a detour LSP for each protected path at the point of each local failure. For more detail, study RFC 4090

2. Many-to-One Local Protection

In this method, PLR create a single path that can be used to protect multiple LSP. In this method a same tunnel can be used for multiple LSP which acts as a protected path for all links which face failure. See RFC 4090 for more details.




Refer to the figure above, we have Node-A and Node-E as the start and end point for which the primary path (LSP) is from Node-A to Node-E through Node-B and Node-D. While the secondary path for Node-A to reach Node-E is through Node-C. We assume that for primary path FRR is enabled & once it is enable all the remaining nodes on a network came to know about this feature. Assume the link between Node-D and Node-E is down by any means, so the first node who realize this breakdown is Node-D which immediately inform Node-B and Node-A. For Node-A to get the failure message it will take some time and Node-D already know about the link failure & FRR is enable for the LSP so Node-D will use the detour path for the communication (Node-D-C-E) to avoid any loss and get rid of the link failure which will carry the traffic to final destination. This whole process will take less than 50 ms. On the other hand when the backup path (secondary LSP) comes up, traffic will be switched to the secondary LSP and detour path will turn down.

I Hope this will be informative for you :)

Ref: RFC4090

Monday, February 6, 2012

DHCP Relay

Dynamic Host Configuration Protocol (DHCP) serves to provide configuration parameters in a client/server environment where the DHCP server maintain address pool and lease information which the server used at time of requesting for IP from client side. This concept of DHCP relay is used when client and server does not reside on the same subnet. Look at the figure below; where the DHCP relay agent acts as a middle-man between host and DHCP server. When the host boots up on the network, the DHCP lease process occurs between the DHCP server and host (client).

DHCP lease process involves the following steps:

1. DHCPDISCOVER
In this step the host (client) sends a broadcast message over the network to request for IP address lease. The DHCP relay agent forwards the request to DHCP server after receiving from host.

2. DHCPOFFER
This can be a response from different server. This includes configuration parameters like IP, Lease information, MAC address, domain name etc as a unicast message to the host (client)

3. DHCPREQUEST
This is in response from the DHCP server to client who sends the initial DHCP server request, message means the client is requesting for IP address lease.

4. DHCPACK
This is sent by DHCP server to DHCP client which is the confirmation of assigning IP lease to the client.

As DHCPDISCOVER message is a broadcast over the network and you need a proper routing to route this message across the other segments where it has to be routed. For this you need to configure this on router interface so that it can forward your request to your DHCP server.

NOTE: In a routed network, you would need DHCP Relay Agents if you plan to implement only one DHCP server.



All clients on a network should be able to contact DHCP server. For this your server should be on the network topology and relied on by all TCP/IP based hosts with your environment. If your network is composed of different segments then we have to perform any of the following tasks:

a) Place a DHCP Relay agent on each segment
b) Place a DHCP server on each segment
c) Configure your router to forward a broadcast message


Configuration on Router

HUAWEI

You just need to configure a single command under the interface

[HUAWEI] interface GigabitEthernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] dhcp select {global | interface | relay}
[HUAWEI-GigabitEthernet1/0/1] dhcp select relay
[HUAWEI-GigabitEthernet1/0/1] ip relay address 192.168.20.20

Verification:

display dhcp relay statistics
display dhcp relay server {all | interface | vlan}

CISCO

Router # ip dhcp relay enable
Router # ip dhcp relay server 192.168.20.20 //Specify DHCP server address

Verification


Router# show ip dhcp relay conf
Router# show ip dhcp relay statistics

I Hope this will be informative for you :)