Ads 468x60px

Monday, May 9, 2011

Managed Services using SNMP



As nowadays in India Every ISP is talking about Manage services, What exactly is manage services ? Which protocol is responsible for this.  How any one do this ? In this section we will discuss about all this...

ISP are the service providers which offers many interactive services to customers, Customers stands for any enterprises or any Big companies in any domain. Every customer  has their own domain and business, as they have huge presence for own business. To manage this, they take links from service providers. But if sometime the links goes down or if they want to check the link quality / utilization. For all this information, they need to maintain own network team to do it and using any NMS. 
                           
NMS stands for Network Monitoring system. This system will monitor your whole network (Initially you need to configure and setup) as per your requirement.This will provide you interactive reports about Link availability/ Utilization/ etc   , But to maintain all this. It will some cost which is incurred by customers. Now ISP’s are offering these services along with link.
                ISP will monitor everything for customer, as per requirement and provide report to customer. Which will help customer to focus on own business and to avoid resources for this work.
Till now we had discussed, how real time market is accepting Manage services .. Let’s see technically what is manage services how this works...

SNMP is very important protocol for this service. Let’s see what is SNMP

SNMP means Simple Network Management Protocol. For better understanding we can divide it into 3 components –
Managed devices
Agents
Network Management System/Network Monitoring System (NMS)
  A managed device is a node that will have a SNMP agent installed or configured or it will support SNMP protocol, which needs to be enabled for this operations. The network devices can be Routers, Switches, etc.  An agent is software process/module with in network device. This provides SNMP information to NMS.
                Then major job of SNMP agent is collect all the required information from network device and send it to NMS in suitable format. This is only possible by SNMP. The NMS is application; It will process the received data from SNMP and provide interactive reports to Users.
But to get detailed information about any network device we should have MIB for that device.

Let’s see something about MIB:

MIB means  Management Information Base. It is a collection of information of network device organized hierarchically. MIB is used to manage a network device remotely with full flexibility. It will help you to provide more information about the device functionality and real time information.
This information is accessed using a SNMP protocol.

OIDs means Object Identifiers. It is used uniquely to identify and managed objects in a MIB hierarchy. We can say, MIB is collection of OID(information) for device, which will help SNMP protocol to get particular information in detail from concern network device. As you check the OIDs in MIB, you can see detail description of that OID in MIB. It will help you to know more about that OID. Every vendor has own MIBs to manage own products.
How this works  –
SNMP works with NMS. NMS send out a request to managed devices , in return a it will receive a response message. In this 4 steps are involved – Get, GerNext, Set and Trap. SNMP header consists of a header and PDU (protocol Dataunits). In that header it will contain – SNMP version information and community string. The community name is used for security reasons, To access data from network device community name should match.

The PDU depends on the type of message that is being sent. The Get, GetNext, and Set, as well as the response PDU, consist of PDU type, Request ID, Error status, Error index and Object/variable fields. The Trap consist of Enterprise, Agent, Agent address, Generic trap type, Specific trap code, Timestamp and Object/Value fields.

After collection of all information NMS process the received data and provide customized reports.
SNMP is very important for Managed services .

Some well known NMS –

Orion Solarwinds
Manage Engine Netflow
CA – Ehealth
IPSwitch – WhatsupGold
HP Openview
IBM – Tivoli



Hope this information is useful for you. For likes and any queries, Plz comment with your mail id...


Friday, May 6, 2011

Multicast Solution – Redundant BSR and RP


As we discussed many things about Multicast in previous posts, it will be better to see some real time solution which will help us for better understanding. How multicast is deployed in large enterprises.

Test Requirements – Large Enterprise is having 2 redundant multicast servers with same multicast group 239.1.1.1. As any of multicast servers went faulty due to any reason, other multicast server will work as backup to serve network and avoid downtime. Same time they want redundant BSR and RP for network. In any case Primary is not available, that time backup should take care.

Test Topology

Testing description:

Customer requires redundancy for Multicast servers and RP. Master multicast server goes down due to any reason, and then backup server sends the same multicast traffic 239.1.1.1. We need to check the convergence time how long time the client side can receive the 239.1.1.1 and same time If Primary RP goes down, Backup RP should work as primary and spoke location can access backup multicast server.

Test Process:

Multicast host 6.1.1.2 wants to join multicast group 239.1.1.1. MP 2816 router check the RP mapping and send the request to Primary RP. As source receive Join request from host, Now 4.1.1.2 (Multicast source) sends the multicast traffic 239.1.1.1 to Multicast host 6.1.1.2, It  can receive the multicast stream properly.



Now 4.1.1.2 (Multicast source) is down due to some issue.



OR
Primary RP is down due to any reason. That time



Backup RP will work as Master and backup multicast server 5.1.1.2 send the same 239.1.1.1 multicast stream manually.


And finally the convergence time less than 5 second, Now Multicast host can receive same multicast stream 239.1.1.1.This solution is majorly deployed to achieve redundancy in multicast network.  


Test Configurations:

MP1800-36:

ip mef
ip load-sharing per-destination
ip multicast-routing

controller e1 1/0
 channel-group 0 timeslots 1-31
 framing crc4
 exit
!end
vlan 1
 exit

interface fastethernet0
 ip address 2.1.1.1 255.255.255.0
 ip pim sparse-mode
 exit

interface fastethernet1
 ip address 4.1.1.1 255.255.255.0
 ip pim sparse-mode
 exit

interface serial1/0:0
 encapsulation hdlc
 ip address 1.1.1.2 255.255.255.0
 bandwidth 1984
 ip pim sparse-mode
 exit
                               
router ospf 1
 network 0.0.0.0 255.255.255.255 area 0
 exit

ip pim bsr-candidate fastethernet0 10    ### Primary BSR ###
ip pim rp-candidate fastethernet0 190   ### Primary RP ###

MP801E:

ip multicast-routing
controller e1 0/0
 channel-group 0 timeslots 1-31
 framing crc4
 exit

interface fastethernet0
 ip address 3.1.1.1 255.255.255.0
 ip pim sparse-mode
 exit

interface fastethernet1
 ip address 5.1.1.1 255.255.255.0
 ip pim sparse-mode
 exit

interface serial0/0:0
 encapsulation hdlc
 ip address 1.1.1.1 255.255.255.0
 bandwidth 1984
 ip pim sparse-mode
 exit
                                 
router ospf 1
 network 0.0.0.0 255.255.255.255 area 0
 exit

ip pim bsr-candidate fastethernet0
ip pim rp-candidate fastethernet0


MP2816:

ip mef
ip load-sharing per-destination
ip multicast-routing

vlan 1
 description default
 port 0-23 untagged
 exit

interface fastethernet0
 ip address 3.1.1.2 255.255.255.0
 ip pim sparse-mode
 exit

interface fastethernet1
 ip address 2.1.1.2 255.255.255.0
 ip pim sparse-mode
 exit
            
interface switchethernet1
 ip address 6.1.1.1 255.255.255.0
 vlan 1
 ip pim sparse-mode
 exit
                            
router ospf 1
 network 0.0.0.0 255.255.255.255 area 0
 exit

### MP2816 router is spoke router it will learn BSR information with PIM messages and RP information from BSR. ###

Test Results:

  1. As Primary Multicast server goes down and Primary Master RP is still live, That time backup multicast server will register with Primary RP. It will send same multicast traffic 239.1.1.1 in network.
  2. As Primary multicast server 239.1.1.1 and Primary RP (MP1800) goes down. That time Backup RP (MP 801E) will work as Primary RP and backup Multicast server will register to available RP and it will send same multicast stream(239.1.1.1) in network.
That means this multicast solution will overcome both challenges, which normally enterprises has to deal.


Hope you like this solution. This above configuration is tested on Maipu Routers, Cisco routers will have same configurations.

Your comments will help me to improve my posts. For any queries put comments with your mail id…


Related Posts Plugin for WordPress, Blogger...