Re: [c-nsp] cisco-nsp Digest, Vol 99, Issue 67
Umair; i think it may be a configurations issue if you do not have the proper commands entered.. in order to get logs of BFD neighbors status you do need to configure log adjacency-changes. log-adjacency-changes [detail] Example: Router(config-router)# log-adjacency-changes Configures the router to send a system logging (syslog) message when a neighbor goes up or down. •Entering the log-adjacency-changes command allows you to see the BFD node down syslog message whenever a neighbor is down due to receiving a BFD failure detection notification. if that is already configured then check may be you need to increase the size of your log file. or may be u need an IOS upgrade. regards From: umair.sae...@live.com To: saidiz...@hotmail.com; cisco-nsp@puck.nether.net Subject: RE: cisco-nsp Digest, Vol 99, Issue 67 Date: Thu, 24 Feb 2011 14:51:23 + Hi Said Izawi, Thanks for email. But i dont hae any configurational issues. customer is running BFD with static route fine. problem is when one of the BFD neighbor goes down/up it router does not shows it in its log. so i m unable to know when th BFD neighbor went down/UP. is there any command to log BFD neighbor status with static routes. i am running SRE2. Thanks Best Regards, Umair SaeedAM IP Operations Core South , Pakistan Telecommunication Company Ltd, Phone # +92 333 2354591 From: saidiz...@hotmail.com To: cisco-nsp@puck.nether.net; umair.sae...@live.com Subject: RE: cisco-nsp Digest, Vol 99, Issue 67 Date: Wed, 23 Feb 2011 15:05:18 + Hello umair: CONFIGURING BFD BFD can be configured in two steps. The first step in configuring BFD is setting the baseline parameters for all BFD sessions on an interface. The configuration occurs at the interface level and the syntax is as follows: [no] bfd interval 50-999 min_rx 1-999 multiplier 3-50 interval: determines how frequently (in milliseconds) BFD packets will be sent to BFD peers. min_rx: determines how frequently (in milliseconds) BFD packets will be expected to be received from BFD peers multiplier: The number of consecutive BFD packets which must be missed from a BFD peer before declaring that peer unavailable, and informing the higher-layer protocols of the failure the second step Once the baseline parameters have been set, individual protocols must be informed that they will be using BFD for failure detection. In the first release of BFD, the supported protocols are OSPF, IS-IS, EIGRP and BGP. on the concerned interface you specify BFD. example: interface GigabitEthernet1/2 ip ospf network point-to-point ip ospf cost 1000 ip ospf hello-interval 3 ip ospf dead-interval 10 ip ospf bfd router ospf 1 log-adjacency-changes bfd interval 50 min_rx 50 multiplier 5 Kind Regards Said Izawi Senior Network Analyst From: cisco-nsp-requ...@puck.nether.net Subject: cisco-nsp Digest, Vol 99, Issue 67 To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 09:23:04 -0500 Send cisco-nsp mailing list submissions to cisco-nsp@puck.nether.net To subscribe or unsubscribe via the World Wide Web, visit https://puck.nether.net/mailman/listinfo/cisco-nsp or, via email, send a message with subject or body 'help' to cisco-nsp-requ...@puck.nether.net You can reach the person managing the list at cisco-nsp-ow...@puck.nether.net When replying, please edit your Subject line so it is more specific than Re: Contents of cisco-nsp digest... --Forwarded Message Attachment-- From: umair.sae...@live.com To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 06:26:00 + Subject: [c-nsp] BFD neighbor up/down in log with Static Dear all, I wanted to know that can any one know the command to enable logging of BFD neighbor status in routers log. I have already enables snmp traps but i need to show these in router logs. We are using BFD with static routing. Thanks Best Regards, Umair SaeedAM IP Operations Core South , Pakistan Telecommunication Company Ltd, Phone # +92 333 2354591 --Forwarded Message Attachment-- From: h...@efes.iucc.ac.il To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 08:55:17 +0200 Subject: Re: [c-nsp] flow-export to more than 2? Platforms which have implemented FNF or some subset thereof (N7K, CRS-1, ASR9K, et. al.) can support multiple exporters. What about 7600s? Any IOS train that handles more than 2 exporters? Thanks, Hank --Forwarded Message Attachment-- From: vikasshar...@gmail.com To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 13:44:47 +0530 Subject: [c-nsp] CRS-1 Policy change Hi, I have a policy which I can see currently not applied on any interface, I am trying to modify the policy (remove existing class-map and add new class-map), but when I commit I see following message !!% Policy manager does not support this feature: Platform does not support policy-map modification type qos I
Re: [c-nsp] cisco-nsp Digest, Vol 99, Issue 67
Umair; i think it may be a configurations issue if you do not have the proper commands entered.. in order to get logs of BFD neighbors status you do need to configure log adjacency-changes. log-adjacency-changes [detail] Example: Router(config-router)# log-adjacency-changes Configures the router to send a system logging (syslog) message when a neighbor goes up or down. •Entering the log-adjacency-changes command allows you to see the BFD node down syslog message whenever a neighbor is down due to receiving a BFD failure detection notification. if that is already configured then check may be you need to increase the size of your log file. regards From: umair.sae...@live.com To: saidiz...@hotmail.com; cisco-nsp@puck.nether.net Subject: RE: cisco-nsp Digest, Vol 99, Issue 67 Date: Thu, 24 Feb 2011 14:51:23 + Hi Said Izawi, Thanks for email. But i dont hae any configurational issues. customer is running BFD with static route fine. problem is when one of the BFD neighbor goes down/up it router does not shows it in its log. so i m unable to know when th BFD neighbor went down/UP. is there any command to log BFD neighbor status with static routes. i am running SRE2. Thanks Best Regards, Umair SaeedAM IP Operations Core South , Pakistan Telecommunication Company Ltd, Phone # +92 333 2354591 From: saidiz...@hotmail.com To: cisco-nsp@puck.nether.net; umair.sae...@live.com Subject: RE: cisco-nsp Digest, Vol 99, Issue 67 Date: Wed, 23 Feb 2011 15:05:18 + Hello umair: CONFIGURING BFD BFD can be configured in two steps. The first step in configuring BFD is setting the baseline parameters for all BFD sessions on an interface. The configuration occurs at the interface level and the syntax is as follows: [no] bfd interval 50-999 min_rx 1-999 multiplier 3-50 interval: determines how frequently (in milliseconds) BFD packets will be sent to BFD peers. min_rx: determines how frequently (in milliseconds) BFD packets will be expected to be received from BFD peers multiplier: The number of consecutive BFD packets which must be missed from a BFD peer before declaring that peer unavailable, and informing the higher-layer protocols of the failure the second step Once the baseline parameters have been set, individual protocols must be informed that they will be using BFD for failure detection. In the first release of BFD, the supported protocols are OSPF, IS-IS, EIGRP and BGP. on the concerned interface you specify BFD. example: interface GigabitEthernet1/2 ip ospf network point-to-point ip ospf cost 1000 ip ospf hello-interval 3 ip ospf dead-interval 10 ip ospf bfd router ospf 1 log-adjacency-changes bfd interval 50 min_rx 50 multiplier 5 Kind Regards Said Izawi Senior Network Analyst From: cisco-nsp-requ...@puck.nether.net Subject: cisco-nsp Digest, Vol 99, Issue 67 To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 09:23:04 -0500 Send cisco-nsp mailing list submissions to cisco-nsp@puck.nether.net To subscribe or unsubscribe via the World Wide Web, visit https://puck.nether.net/mailman/listinfo/cisco-nsp or, via email, send a message with subject or body 'help' to cisco-nsp-requ...@puck.nether.net You can reach the person managing the list at cisco-nsp-ow...@puck.nether.net When replying, please edit your Subject line so it is more specific than Re: Contents of cisco-nsp digest... --Forwarded Message Attachment-- From: umair.sae...@live.com To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 06:26:00 + Subject: [c-nsp] BFD neighbor up/down in log with Static Dear all, I wanted to know that can any one know the command to enable logging of BFD neighbor status in routers log. I have already enables snmp traps but i need to show these in router logs. We are using BFD with static routing. Thanks Best Regards, Umair SaeedAM IP Operations Core South , Pakistan Telecommunication Company Ltd, Phone # +92 333 2354591 --Forwarded Message Attachment-- From: h...@efes.iucc.ac.il To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 08:55:17 +0200 Subject: Re: [c-nsp] flow-export to more than 2? Platforms which have implemented FNF or some subset thereof (N7K, CRS-1, ASR9K, et. al.) can support multiple exporters. What about 7600s? Any IOS train that handles more than 2 exporters? Thanks, Hank --Forwarded Message Attachment-- From: vikasshar...@gmail.com To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 13:44:47 +0530 Subject: [c-nsp] CRS-1 Policy change Hi, I have a policy which I can see currently not applied on any interface, I am trying to modify the policy (remove existing class-map and add new class-map), but when I commit I see following message !!% Policy manager does not support this feature: Platform does not support policy-map modification type qos I am sure this policy is not anywhere
Re: [c-nsp] cisco-nsp Digest, Vol 99, Issue 67
Hello umair: CONFIGURING BFD BFD can be configured in two steps. The first step in configuring BFD is setting the baseline parameters for all BFD sessions on an interface. The configuration occurs at the interface level and the syntax is as follows: [no] bfd interval 50-999 min_rx 1-999 multiplier 3-50 interval: determines how frequently (in milliseconds) BFD packets will be sent to BFD peers. min_rx: determines how frequently (in milliseconds) BFD packets will be expected to be received from BFD peers multiplier: The number of consecutive BFD packets which must be missed from a BFD peer before declaring that peer unavailable, and informing the higher-layer protocols of the failure the second step Once the baseline parameters have been set, individual protocols must be informed that they will be using BFD for failure detection. In the first release of BFD, the supported protocols are OSPF, IS-IS, EIGRP and BGP. on the concerned interface you specify BFD. example: interface GigabitEthernet1/2 ip ospf network point-to-point ip ospf cost 1000 ip ospf hello-interval 3 ip ospf dead-interval 10 ip ospf bfd router ospf 1 log-adjacency-changes bfd interval 50 min_rx 50 multiplier 5 Kind Regards Said IzawiSenior Network Analyst From: cisco-nsp-requ...@puck.nether.net Subject: cisco-nsp Digest, Vol 99, Issue 67 To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 09:23:04 -0500 Send cisco-nsp mailing list submissions to cisco-nsp@puck.nether.net To subscribe or unsubscribe via the World Wide Web, visit https://puck.nether.net/mailman/listinfo/cisco-nsp or, via email, send a message with subject or body 'help' to cisco-nsp-requ...@puck.nether.net You can reach the person managing the list at cisco-nsp-ow...@puck.nether.net When replying, please edit your Subject line so it is more specific than Re: Contents of cisco-nsp digest... --Forwarded Message Attachment-- From: umair.sae...@live.com To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 06:26:00 + Subject: [c-nsp] BFD neighbor up/down in log with Static Dear all, I wanted to know that can any one know the command to enable logging of BFD neighbor status in routers log. I have already enables snmp traps but i need to show these in router logs. We are using BFD with static routing. Thanks Best Regards, Umair SaeedAM IP Operations Core South , Pakistan Telecommunication Company Ltd, Phone # +92 333 2354591 --Forwarded Message Attachment-- From: h...@efes.iucc.ac.il To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 08:55:17 +0200 Subject: Re: [c-nsp] flow-export to more than 2? Platforms which have implemented FNF or some subset thereof (N7K, CRS-1, ASR9K, et. al.) can support multiple exporters. What about 7600s? Any IOS train that handles more than 2 exporters? Thanks, Hank --Forwarded Message Attachment-- From: vikasshar...@gmail.com To: cisco-nsp@puck.nether.net Date: Wed, 23 Feb 2011 13:44:47 +0530 Subject: [c-nsp] CRS-1 Policy change Hi, I have a policy which I can see currently not applied on any interface, I am trying to modify the policy (remove existing class-map and add new class-map), but when I commit I see following message !!% Policy manager does not support this feature: Platform does not support policy-map modification type qos I am sure this policy is not anywhere attached as otherwise I would see following error !!% Object is in use: Class-map Default-From-CR-SAR of type qos is used bypolicy-map(s). Delete failed This is on CRS1 XR rel 3.6.2 am I missing something? Regards, Vikas --Forwarded Message Attachment-- From: bandh...@gmail.com CC: cisco-nsp@puck.nether.net To: vikasshar...@gmail.com Date: Wed, 23 Feb 2011 14:49:12 +0500 Subject: Re: [c-nsp] CRS-1 Policy change Can you please confirm the modified configuration / new class-map? We are running same version on CRS-1s with no. of policies modification on need basis. This should not be the case... -FJ On Wed, Feb 23, 2011 at 1:14 PM, Vikas Sharma vikasshar...@gmail.comwrote: Hi, I have a policy which I can see currently not applied on any interface, I am trying to modify the policy (remove existing class-map and add new class-map), but when I commit I see following message !!% Policy manager does not support this feature: Platform does not support policy-map modification type qos I am sure this policy is not anywhere attached as otherwise I would see following error !!% Object is in use: Class-map Default-From-CR-SAR of type qos is used bypolicy-map(s). Delete failed This is on CRS1 XR rel 3.6.2 am I missing something? Regards, Vikas ___ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/ --Forwarded Message Attachment--
