User talk:Karthick.gopi.eljay

In response to your feedback
Great! I hope you provide lots of interesting additions to our articles!

I, Jethrobot drop me a line (note: not a bot!) 06:34, 5 October 2012 (UTC)

&#160;

NOC Services and Applications
What is Network Management To operate a reliable service, the network must be managed according to a determined discipline, using a coherent structure of information management. What is a NOC Network Operations Centre (NOC) Monitors and manages a service provider’s network •	Information about current, historical and planned availability of systems •	Network status and operational statistics •	Fault monitoring and management Engineers can coordinate their work through the NOC Network Management – Components

Parts of Network Management •	Configuration/Change management •	Performance/Accounting management •	Fault management •	Security management •	Configuration Management Maintaining information relating to the design of the network and its current configuration n 	 Network State •	Record of network topology –	Static Õ	what is deployed Õ	where it is deployed Õ	how it is attached Õ	Who is responsible for it Õ	How do I contact them –	Dynamic Õ	operational status of the network elements n	inventory management •	database of network elements •	history of changes & problems n	directory maintenance •	all hosts & applications •	nameserver database n	host and service naming coordination •	"Information is not information if you can't find it" Operational Control of network 	Start/stop individual components 	Alter configuration of devices 	Load and save config versions 	Hardware/Software upgrades 	Methods of access •	SNMPGet / SNMPSet •	Out-of-Band access

•	RANCID o	RANCID - Really Awesome New Cisco confIg Differ o	Also works for IOS/CatOS/JunOS/... o	Open Source o	Runs on FreeBSD, Linux, OSX, even MS-Windows o	http://www.shrubbery.net/	(foe other useful tools) o	Collections of scripts that run from cron and automate o	logging into routers o	capturing configuration o	highlighting configuration ‘differences’ o	emailing the ‘diffs’ to a mail list o	installing ‘diffs’ into CVS o	Track config changes. o	Track hardware changes. o	Track (I)OS changes. o	Malicious changes. o	Retrieve dead router configs. o	Track router crashes. •	RANCID Sample Output 	!Slot 2/MBUS: hvers 1.1 	 !Slot 2/MBUS: software 01.36 (RAM) (ROM version is 01.33) 	 !Slot 2/MBUS: 128 Mbytes DRAM, 16384 Kbytes SDRAM 	 ! 	- !Slot 6: 1 Port Gigabit Ethernet 	- !Slot 6/PCA: part 73-3302-03 rev C0 ver 3, serial CAB031216OL 	- !Slot 6/PCA: hvers 1.1 	- !Slot 6/MBUS: part 73-2146-07 rev B0 dev 0, serial CAB031112SB 	- !Slot 6/MBUS: hvers 1.2 	- !Slot 6/MBUS: software 01.36 (RAM) (ROM version is 01.33) 	 !Slot 7: Route Processor 	 !Slot 7/PCA: part 73-2170-03 rev B0 ver 3, serial CAB024901SI 	 !Slot 7/PCA: hvers 1.4 	 !Slot 7/MBUS: part 73-2146-06 rev A0 dev 0, serial CAB02060044 •	RANCID Re-use •	More than configuration management. •	Cheap Asset Tracker/NMS •	UNIX script - easily extendible to other applications. •	Re-use login scripts •	Manage configuration changes •	Correlate syslog and RANCID using Simple Event Correlator (SEC) •	http://threebit.net/mail-archive/cisco-nsp/msg00053.html •	Looking Glass software •	See Joe Abley and Stephen Stuart NANOG presentation: •	http://www.nanog.org/mtg-0210/abley.html •	Consistency/Audit checks •	Generate DNS zone files •	Create Topographic maps •	What is SNMP 	Simple Network Management Protocol 	query - response system 	can obtain status from a device 	standard queries 	enterprise specific 	uses database defined in MIB 	management information base o	query routers for: o	in and out bytes per second o	CPU load o	uptime o	BGP peer session status o	query hosts for: o	network status o	Message queues o	Web traffic o	Squid proxy load

•	Performance Management 	A Consistent level of network performance 	Data collection 	interface stats 	throughput 	error rates 	usage 	percent availability 	Data analysis for performance metrics and trends 	Establishment of performance thresholds 	Capacity planning and deployment o	Importance of Network Statistics 	Accounting 	Troubleshooting 	Long-term trend analysis 	Capacity Planning 	Two different types 	active measurement 	passive measurement 	Management Tools have statistical functionality o	MRTG

Netflow 	Cisco developed - 1996 	Initially a mechanism for forwarding packets 	No longer - Now, primarily used for 	Accounting/Billing 	Network planning 	Peering arrangements 	Traffic engineering 	Security monitoring o	Netflow packet typically contains 	IP SRC+DST 	Port SRC+DST 	Protocol information 	TOS byte (DSCP) 	Input logical interface (ifIndex) 	Extendible (IOS capable) 	AS / VRF / ... •	Only works on inbound traffic •	Unidirectional flow •	Shows transit (traffic through) and to the router. •	Enabled by: •	ip route-cache flow •	ip flow ingress (new syntax) •	Output seen with: •	show ip cache [verbose] flow o	Netflow Example 	From your workstation: 	ping 196.200.220.1 	On your router: 	router# conf t 	router(config) int fa0/0 	router(config-if)# ip flow ingress 	router# show ip cache flow 	What’s missing? 	(Why are the flows only in 1 direction?) 	How do you fix it ? 	Now repeat the BCP38 packet spoofing exercise, but track the bogus packets with Netflow. Pay attention to what happens when uRPF is enabled. 	Top ten lists (or top five) •	Accounting Management o	What do you account for? o	Use of the network and the services it provides o	Types of accounting data o	RADIUS/TACACS accounting data from Access servers o	Interface statistics o	Protocol statistics o	Accounting Data affects Business Models o	Bill on usage? o	Flat-rate billing? •	Fault Management o	Identify the fault o	Regular polling of network elements o	Isolate the fault o	Diagnosis of the network components o	Respond to the fault o	Allocate resources to resolve the fault o	Priority scheduling o	Technical/management escalation o	Resolve the fault o	notification o	reporting mechanism o	link to NOC o	notify on-call personnel o	setup & control alarm procedures o	repair/recovery procedures o	ticket system

•	Fault Management - Fault Detection o	Who notices a problem with the network? o	Network Operations Center w/ 24x7 operations staff o	open trouble ticket to track problem o	preliminary troubleshooting o	Assign engineer to problem or escalate ticket status o	Customer call o	Other ISPs

	How identify if there is a problem with the network •	Network Monitoring Tools •	common utilities •	ping •	Traceroute •	Ethereal •	Snmp •	Monitoring Systems •	NOCol •	Big Brother •	Nagios •	HP Openview, etc… •	Report state or unreachability •	detect node down •	routing problems 	Fault Management - Ticket System o	Very Important! o	Need mechanism to track: o	failures o	current status of outage o	carrier tickets o	system provides for: o	short term memory & communication o	scheduling and work assignment o	referrals and dispatching o	oversight o	statistical analysis o	long term accountability 	Fault Management - Ticket Usagev •	create a ticket on ALL calls •	create a ticket on ALL problems •	create a ticket for ALL scheduled events •	copy of ticket mailed to reporter and mailing list(s) •	all milestones in resolution of problem maintain the same ticket # •	ticket stays "open" until problem resolved •	Ticket reporter determines that ticket should be closed. 	Fault Management - Ticket Example 	Exercise: Ticket System •	RT is already installed on http://e2-noc.ws.afnog.org •	Create tickets to track network occurrences as they occur - network failures will be provided o	Fault Management - typical failures 	Node unpingable 	no ip connectivity to router 	possible reasons: 	serial link down 	call telco 	router down/hardware problem 	call engineer 	routing problem 	troubleshoot with traceroute 	routeviews machine o	Security Management: Do’s & Don’t’s 	Dont’ leave things that are likely to be interesting to mice lying on the kitchen table overnight 	Plug the holes that mice are using to get into the house 	Don’t provide places within the house for mice to build nests 	Set traps along walls where you often see mice out of the corner of your eye 	Check the traps daily to rebait them and to dispose of squashed mice. Full traps don’t catch mice, and they smell 	Avoid using commercial bait-and-kill poisons. Traditional snap traps are best. 	Get a cat! o	Security Management – Tools 	security tools 	cops - host configuration checker (www.cert.org) 	swatch - email reports of activity on machine 	Tcpwrappers – log connections, restrict access 	ssh/skey – crypto authentication and communications 	Tripwire – monitor changes to system files 	Keep up to date with security information 	bug reports 	CERT advisories mailing list: 	http://www.cert.org./contact_cert/certmaillist.html 	bug fixes 	intruder alerts o	Security Management – Good Practice 	reporting procedure for security events 	e.g. break-ins 	abuse email address for customers to report complaints (abuse@your-isp.net) 	control internal and external gateways 	control firewalls (external and internal) 	security log management 	centralized logging host 	Stealth logger, so it cannot be compromised o	How to manage my network 	Which tools should I use? What do I really need? 	Keep it simple! 	Need to consider engineers working remotely 	Don’t want to spend too much time maintaining the tool (it should be helping you!) 	Different tools for NOC and engineers 	Different tools for statistics 	RELIABILITY! •	References o	http://www.merit.edu/ipma/docs/isp.html o	http://www.nanog.org o	http://www.caida.org o	http://www.nlanr.net o	http://www.cisco.com o	http://www.amazing.com/internet/ o	http://www.isp-resource.com/ o	http://www.merit.edu/ipma o	http://www.ripe.net •	Tools o	http://www.caida.org/Tools/ o	OC3Mon/Coral o	http://www.merit.edu/~ipma o	RouteTracker o	IRRj o	ASExplorer o	http://www.geektools.com/ o	http://www.merit.edu/ipma/tools/other.html •	SNMP Tool references o	MON - http://www.kernel.org/software/mon/ o	NOCol - ftp://ftp.navya.com/pub/vikas/nocol.tar.gz o	Sysmon - ftp://puck.nether.net/pub/jared o	Rover - http://www.merit.edu/~rover o	Concord - http://www.concord.com o	http://www.merit.net/~netscarf o

MTNL delhi
This is an automated message from MadmanBot. I have performed a web search with the contents of MTNL delhi, and it appears to include material copied directly from http://www.mtnl.net.in/press_310810.doc.

It is possible that the bot is confused and found similarity where none actually exists. If that is the case, you can remove the tag from the article. The article will be reviewed to determine if there are any copyright issues.

If substantial content is duplicated and it is not public domain or available under a compatible license, it will be deleted. For legal reasons, we cannot accept copyrighted text or images borrowed from other web sites or printed material. You may use such publications as a source of information, but not as a source of sentences. See our copyright policy for further details. (If you own the copyright to the previously published content and wish to donate it, see Donating copyrighted materials for the procedure.) MadmanBot (talk) 09:31, 2 January 2013 (UTC)

Speedy deletion nomination of MTNL delhi
Hello Karthick.gopi.eljay,

I wanted to let you know that I just tagged MTNL delhi for deletion, because it seems to be inappropriate for a variety of reasons.

If you feel that the article shouldn't be deleted and want more time to work on it, you can contest this deletion, but please don't remove the speedy deletion tag from the top.

You can leave a note on my talk page if you have questions. Thanks, Skrelk (talk) 10:24, 2 January 2013 (UTC)