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 :)