Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About Manish Kumar
02-14-2019
Stats
Member since
03-29-2010
9
Posts
20
Helpful
1
Solution
Created by
Manish Kumar
in Networking Documents
in Networking Documents
12-18-2015
12:21 PM
12-18-2015
12:21 PM
For Out Of Band Management (Dial-in):
This Config allows one to dial-in to the router for out of band mgmt when the main line is down. This cannot be used as a link for internet access.
this sample is from 891-F
use show platform and identify modem port. You can use show line as well.
------------------ show platform ------------------
Interrupts:
===========
Assigned Handlers...
Vect Handler # of Ints Name
0 05521278 1 CPLD Interrupt
1 0564BAD4 0 PEB3081 ISDN S/T Transceiver Interrupt
2 05A7D69C 10 DX MRVL Address Update interrupt
3 05F8680C 0 V92 Modem Interrupt <<=======modem port
sample config:
interface Async3
no ip address
encapsulation slip
keepalive 10
line 3
exec-timeout 0 0
login local
modem InOut
transport input all
transport output all
stopbits 1
speed 115200
flowcontrol hardware
Special note: Please note at times you have to use "modem always-on" instead of "modem inout" and "autohangup" in addition to above.
use clear line <#> to clear the session.
following debugs can be used for troubleshooting:
debug modem
debug confmodem
show commands:
show modem version
show modem
show modem summary
show modem call-stats
Perform following to ensure line is good and modem is working fine
clear line 3
telnet 10.243.48.46 2003 -- any ip address that is showing up/up
atz - hit enter -this will reset modem config
ats0=1 - hit enter-this will tell modem to answer automatically after one ring
atd - enter -if you are local to the router you should hear dialtone
atdt <tel #> -it should dial out.. try to dial ur cell phone
upon reverse telnet into the modem if you get "no carrier" "no dialtone" then that is L1 issue.
Dial-Out (When using V.92 as a back-up interface for internet access):
Configuring a V.92 Modem Interface
The Cisco 891 ISR has a V.92 modem backup interface. To configure this interface, perform these steps, beginning in global configuration mode:
SUMMARY STEPS
1. interface type number
2. ip address ip-address mask
3. encapsulation ppp
4. dialer in-band
5. dialer string dial-string
6. dialer-group group-number
7. async mode dedicated
8. exit
... View more
Labels:
Created by
Manish Kumar
in Small Business Routers
in Small Business Routers
11-30-2015
09:16 AM
11-30-2015
09:16 AM
there was this bug CSCut07168 that was resolved in 1.2.1.13 here is text on it
Problem Description:
- When DHCP Server is disabled for all VLAN except one, DHCP doesn't work
- VLAN 1 is the only one that works when it is the only one with DHCP Server enabled
- If DHCP Server is enabled on any other VLAN, then DHCP works for those VLANs
- Ex. VLANs 1,2 and 3 have DHCP disabled and VLAN 4 has it enabled. DHCP doesn't work for VLAN 4
<B>Symptom:</B>
- When DHCP Server is disabled for all VLAN except one, DHCP doesn't work
- VLAN 1 is the only one that works when it is the only one with DHCP Server enabled
<B>Conditions:</B>
- DHCP Server is disabled on all VLANs except one (other than VLAN 1)
<B>Workaround:</B>
- Enable DHCP Server on any other VLAN
- Can create a dummy VLAN that is not assigned to a port
Steps to Reproduce:
1. Create VLAN 4 so that VLANS 1,25,100 and 4 exist on the router
2. Disable DHCP Server on VLANs 1, 25 and 100
3. Enable DHCP Server on VLAN 4
4. Put a port in VLAN 4 untagged
5. Connect a PC to port in VLAN 4
It will not get an ip address via DHCP
Workaround:
6. Create VLAN 5 and enable DHCP Server
7. Don't put any ports in VLAN 5 untagged
8. Connect PC to port in VLAN 4
It will now get an ip address via DHCP
What if you you assign a static IPv6 address to host in Vlan 10, does it work okay?
could you provide me
show ipv6 interface vlan 10
are you using following utility to configure it?
https://www.cisco.com/assets/sol/sb/RV320_Emulators/RV320_Emulator_v1.1.0.09/default.htm --> I used it to test what you have
config doc:
http://www.cisco.com/c/dam/en/us/td/docs/routers/csbr/rv320/administration/guide/en/rv32x_ag_en.pdf
Manish
... View more
11-12-2015
01:47 PM
Hello,
On RSP2-128, TDM support came in from XE3.14 release. Kindly move to XE3.14 release and above to verify. have you tried removing and reinserting the card? I don't see anything under Insert time so may be its not seated correctly.
Please provide me
sh ver
sh run
show log
dir bootflash or dir flash:
sh hw-module all fpd
check these:
http://www.cisco.com/c/en/us/products/collateral/routers/asr-903-series-aggr
egation-services-routers/data_sheet_c78-715295.html
http://www.cisco.com/c/en/us/products/collateral/routers/asr-903-series-aggr
egation-services-routers/data_sheet_c78-715296.html Are there any core files generated for the T1E1 IM ? Can you please pass on the core file if there is one ? Also iomd and MRT logs would help here. Adding the TDM dev alias here.
Router#request platform software system shell Activity within this shell can jeopardize the functioning of the system. Are you sure you want to continue? [y/n] y
[Router_RP_1:/]$ cd /bootflash/core [Router_RP_1:/bootflash/core]$ ls -ltr
[rudy1_RP_1:/bootflash/core]$ cd /tmp/cc/trace/ [rudy1_RP_1:/tmp/cc/trace]$ ls -ltr
Copy the iomd logs for the T1E1 IM [ slot 0 in your case ]
... View more
11-12-2015
01:25 PM
Hello,
The most common reason why we see output drops on tunnel interface is when it received large packets with DF bit set while end hosts doing PMTUD. These packets are registered as outout drops on the tunnel interface. Other option is when the router receives packets but not have the destination in its CEF table. This CEF drops could very well be contributing the output on tunnel interface. A thrid option is when router has high CPU, which doesn't seem to be the case. Finally if the tunnel destination cannot be reach is I believe also generating drops.
http://www.cisco.com/c/en/us/support/docs/ip/generic-routing-encapsulation-gre/25885-pmtud-ipfrag.html#fifth
Another thing to try is “no ip route-cache” under tunnel interface.
We can also use “debug ip cef drop”
Do you see drops with ipsec removed?
thanks
Manish
... View more
05-08-2015
12:03 PM
thank you sir, this is exactly what I was looking for. Great work.
... View more
05-08-2015
11:41 AM
Hi Vinit, Could you share an example where EEM can be used to troubleshoot high cpu caused by IGP (for example ospf) flapping? It's catch 22 where IGP can flap due to high cpu and if IGP is constantly flapping it can cause cpu to go high, and generally your remote connection session could be very slow/unresponsive during those times. Thanks Manish
... View more
Created by
Manish Kumar
in Service Providers Blogs
in Service Providers Blogs
11-17-2013
03:39 PM
11-17-2013
03:39 PM
This is very good article, thanks for sharing.. Manish
... View more
Created by
Manish Kumar
in Networking Blogs
in Networking Blogs
05-06-2013
10:42 PM
05-06-2013
10:42 PM
great Video Ruchir, very useful.. thanks
... View more
Created by
Manish Kumar
in Switching
in Switching
07-27-2012
07:10 PM
07-27-2012
07:10 PM
Hi team, We have 2 3945/15.0(1)M7 connected via gig interface to upstream routers (4 routers running MPLS BGP in core, dedicated for IP SLA probes) and we can ping physical interface IP just fine no delay but when ping loopback interface ping response time latency varies any where from 1 ms to 22 ms and we are looking for ways to find out if something in control plane of 3900 is causing this delay, any help is much appreciated. Topology and config is like this FRFRPARP301NSR01: sho ip int brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 unassigned YES NVRAM administratively down down
GigabitEthernet0/1 10.251.63.117 YES NVRAM up up
GigabitEthernet0/2 10.251.63.9 YES NVRAM up up
Loopback0 10.250.230.207 YES manual up up
Loopback1 10.250.230.206 YES manual up up
Loopback2 10.250.230.205 YES manual up up
Loopback3 10.250.230.204 YES manual up up nterface Loopback0
description Router Integrity Enterprise Template rollout for BOA AUDIT Feb 2005
ip address 10.250.230.207 255.255.255.255
!
interface Loopback1
description Tier 1 poller source
ip address 10.250.230.206 255.255.255.255
!
interface Loopback2
description Tier 2 poller source
ip address 10.250.230.205 255.255.255.255
!
interface Loopback3
description Reserved
ip address 10.250.230.204 255.255.255.255
interface GigabitEthernet0/2
description FRFRPARP301GER01B_GE0/0/1/1
mtu 9000
ip address 10.251.63.9 255.255.255.254
no ip redirects
no ip proxy-arp
duplex full
speed auto
GigabitEthernet0/2 is up, line protocol is up
Hardware is PQ3_TSEC, address is c464.1326.b982 (bia c464.1326.b982)
Description: FRFRPARP301GER01B_GE0/0/1/1
Internet address is 10.251.63.9/31
MTU 9000 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive set (10 sec)
Full-duplex, 1000Mb/s, media type is SX
output flow-control is XON, input flow-control is XON
ARP type: ARPA, ARP Timeout 04:00:00
Last input 00:00:00, output 00:00:00, output hang never
Last clearing of "show interface" counters 04:53:18
Input queue: 1/75/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 257000 bits/sec, 165 packets/sec
5 minute output rate 255000 bits/sec, 163 packets/sec
3170656 packets input, 604643921 bytes, 0 no buffer
Received 448 broadcasts, 0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 448 multicast, 0 pause input
0 input packets with dribble condition detected
3173300 packets output, 605343966 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out FRFRPARP301NSR01#ping 10.250.230.223
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.250.230.223, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
FRFRPARP301NSR01#ping 10.250.230.222
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.250.230.222, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/22/24 ms
FRFRPARP301NSR01#ping 10.250.230.223
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.250.230.223, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/4 ms
FRFRPARP301NSR01#ping 10.250.230.221
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.250.230.221, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms
FRFRPARP301NSR01#ping 10.250.230.220
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.250.230.220, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms
FRFRPARP301NSR01#
2nd NSR rtr:
FRFRPART301NSR01#sho ip int brief
Interface IP-Address OK? Method Status Protocol
GigabitEthernet0/0 unassigned YES manual administratively down down
GigabitEthernet0/1 10.251.63.245 YES NVRAM up up
GigabitEthernet0/2 10.251.63.137 YES manual up up
Loopback0 10.250.230.223 YES manual up up
Loopback1 10.250.230.222 YES manual up up
Loopback2 10.250.230.221 YES manual up up
Loopback3 10.250.230.220 YES manual up up
(I'm pinging the 1st NSR's loopbacks way above)
FRFRPART301NSR01#ping 10.250.230.207
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.250.230.207, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 20/22/24 ms
FRFRPART301NSR01#ping 10.250.230.206
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.250.230.206, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
FRFRPART301NSR01#ping 10.250.230.205
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.250.230.205, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms
FRFRPART301NSR01#ping 10.250.230.204
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.250.230.204, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 12/12/12 ms
FRFRPART301NSR1# - no interface errors - cpu is less than 5% - no controller level errors Please let me know if any information is required from devices. thanks Manish
... View more
Labels:
03-29-2010
04:00 PM
Hi, Sample config for your quick reference: PPPoEoA Sample Configuration: --------------------------------- vpdn enable no vpdn logging ! vpdn-group 1 request-dialin protocol pppoe ! interface Ethernet0 ip address 192.168.100.1 255.255.255.0 ip tcp adjust-mss 1452 ip nat inside ! interface ATM0 no ip address no atm ilmi-keepalive pvc 8/35 pppoe-client dial-pool-number 1 ! dsl operating-mode auto ! interface Dialer1 ip address negotiated ip mtu 1492 ip nat outside encapsulation ppp dialer pool 1 ppp authentication chap callin ppp chap hostname <> ppp chap password 0 <> ppp pap sent-username <> password 0 <> ! ip nat inside source list 101 interface Dialer1 overload ip route 0.0.0.0.0.0.0.0 Dialer1 access-list 101 permit ip 192.168.100.0.0.0.0.255 any
... View more
12-18-2015
For Out Of Band Management (Dial-in): This Config allows one to dial-in
to the router for out of ban...
11-30-2015
there was this bug CSCut07168 that was resolved in 1.2.1.13 here is text
on it Problem Description: ...
11-12-2015
Hello, On RSP2-128, TDM support came in from XE3.14 release. Kindly move
to XE3.14release and above ...
11-12-2015
Hello, The most common reason why we see output drops on tunnel
interfaceis when it received large p...
05-08-2015
Hi Vinit,Could you share an example where EEM can be used to
troubleshoot high cpu caused by IGP (fo...
Created by
Manish Kumar
in Service Providers Blogs
11-17-2013
11-17-2013
This is very good article, thanks for sharing..Manish
Created by
Manish Kumar
in Networking Blogs
05-06-2013
05-06-2013
great Video Ruchir, very useful.. thanks
07-27-2012
Hi team,We have 2 3945/15.0(1)M7 connected via gig interface to upstream
routers (4 routers running ...
Public Statistics
| Date Registered | 03-29-2010 03:47 PM |
| Date Last Visited | 02-14-2019 11:03 AM |
| Total Messages Posted | 9 |
| Total Helpful Votes Received | 20 |
Helpful Votes From
