Procedure for capturing Show tech support on TFTP server

Show tech-support

This command is used to display technical support information which can be used in troubleshooting the router.The show tech-support command displays the output of a number of show commands at once. The output from this command varies depending on the platform and configuration.

This command can generate a very large amount of output. So the ideal way is to redirect the output to a file on the tftp which can be handy if the logs needs to be provided to the technical support representative.

Process for executing the command and redirecting it to tftp server.

Following steps needs to be followed in order to redirect the show tech-support output to the tftp folder.

1. Log on to the FTP Server(tftp server ip)

       ftp://tftp%20sever%20ip/

2. Create a file on the ftp server on which you want the logs to be taken.

• Create a file on desktop without any extension.
• Copy this file and paste on the ftp server.

3. Log on to the Router and execute the below mentioned command.

Show tech-support | redirect <disk>:<ROUTER_NAME-DD-MM-YY-Desc>

NOTE:make sure that Disk has enough space to capture the show-tech command output.

Also the filename crated on the router and the ftp server be same.

4. Once the output is saved in the disk, we need to copy the file from disk to the ftp server.

PE3-MLM-EU#copy disk0: ROUTER_NAME-DD-MM-YY-Desc tftp:

Address or name of remote host []? tftp server ip

Destination filename [ROUTER_NAME-DD-MM-YY-Desc]?

The Show tech is copied and same information can be accessed:

ftp://tftp server ip/

File Name: ROUTER-TECH-260309-desc

multicasting troubleshooting with commands list

1)      Check traffic on provider CE LAN interface using following command.

CErouter#sh int fa0/0 | in rate

 Queueing strategy: fifo

 30 second input rate 992000 bits/sec, 307 packets/sec

 30 second output rate 2000 bits/sec, 4 packets/sec

2)        Check multicast traffic on CE  router using following commands

    CErouter#sh ip mroute active

 Active IP Multicast Sources - sending >= 4 kbps

 a negative (-) Rate counts pps being fast-dropped

    Group: 233.77.100.4, (?)

     Source: 100.10.10.1 (?)

     Rate: 2 pps/8 kbps(1sec), 8 kbps(last 0 secs), 0 kbps(life avg)

     Group: 233.64.195.81, (?)

      Source: 160.1.1.17 (?)

      Rate: 20 pps/65 kbps(1sec), 65 kbps(last 0 secs), 1 kbps(life avg)

router#sh ip mroute count

IP Multicast Statistics

91 routes using 43784 bytes of memory

46 groups, 0.97 average sources per group

Forwarding Counts: Pkt Count/Pkts(neg(-) = Drops) per second/Avg Pkt Size/Kilobits per second

Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)

Group: 233.77.100.4, Source count: 1, Packets forwarded: 3231252, Packets received: 3231984

  Source: 100.10.10.1/32, Forwarding: 3231252/6/400/19, Other: 3231984/732/0

Group: 233.77.100.58, Source count: 1, Packets forwarded: 1821875, Packets received: 2639381

  RP-tree: Forwarding: 0/0/0/0, Other: 0/0/0

  Source: 140.1.1.17/32, Forwarding: 1821875/17/400/54, Other: 2639381/0/817506

3)      If you don’t see any multicast traffic check whether tunnel (from the remote PE) is     up or not on PE router using following command.   

PEROUTER#sh ip pim vrf <VRF NAME>neighbor

PIM Neighbor Table

Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority,

      S - State Refresh Capable

Neighbor          Interface                Uptime/Expires     

Ver     DR

Address                                                                                           Prio/Mode

212.60.60.66      Tunnel2                  3d21h/00:01:42    v2    1 / DR S P

PEROUTER#sh int Tunnel2

Tunnel2 is up, line protocol is up

  Hardware is Tunnel

  Interface is unnumbered. Using address of Loopback60 (212.60.60.36)

  MTU 1514 bytes, BW 9 Kbit, DLY 500000 usec,

     reliability 255/255, txload 1/255, rxload 1/255

  Encapsulation TUNNEL, loopback not set

  Keepalive not set

  Tunnel source 212.60.60.36 (Loopback60), destination 239.232.63.61, fastswitch TTL 255

  Tunnel protocol/transport GRE/IP Multicast, key disabled, sequencing disabled

If tunnel is down,

Check transport vrf configuration on both PE routers (Provider and Member)

a)       MDT should be same on both vrfs.

b)       Enable pim on all core interfaces.

c)       Also check if there are any ACLs which are denying the PIM neighborship to establish.

d)       Use following command to trace.

     Mtrace < Source add (management address) >  < Destination add >  < group add>

 Tunnel source and destination add  will be Loopback 100 for white OSPF, Loopback 60 for RED OSPF and Loopback 70 for BLUE OSPF of PE routers.

5) Use following command to check multicast traffic on PE router.

PEROUTER#sh ip mroute vrf <vrf name> active

Active IP Multicast Sources - sending >= 4 kbps

Group: 233.64.195.84, (?)

   Source: 100.10.10.1 (?)

     Rate: 28 pps/89 kbps(1sec), 91 kbps(last 40 secs), 90 kbps(life avg)

6) Use following command  to display IP multicast routing table.

Router#sh ip mroute

IP Multicast Routing Table

Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,

       L - Local, P - Pruned, R - RP-bit set, F - Register flag,

       T - SPT-bit set, J - Join SPT, M - MSDP created entry,

       X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,

       U - URD, I - Received Source Specific Host Report,

       Z - Multicast Tunnel, z - MDT-data group sender,

       Y - Joined MDT-data group, y - Sending to MDT-data group

Outgoing interface flags: H - Hardware switched, A - Assert winner

 Timers: Uptime/Expires

 Interface state: Interface, Next-Hop or VCD, State/Mode

(100.10.10.1, 233.77.100.4), 1w1d/00:02:51, flags: sTI

  Incoming interface: Serial0/0/0:0.101, RPF nbr 62.2.68.29

  Outgoing interface list:

    FastEthernet0/0, Forward/Sparse, 1w1d/00:02:58

(*, 233.77.100.58), 1d22h/stopped, RP 145.1.1.2, flags: SP

  Incoming interface: Null, RPF nbr 0.0.0.0

  Outgoing interface list: Null

(140.1.1.17, 233.77.100.58), 1d19h/00:03:20, flags: TA

  Incoming interface: FastEthernet0/0, RPF nbr 0.0.0.0

  Outgoing interface list:

    Serial0/0/0:0.101, Forward/Sparse, 01:11:14/00:03:23

Show Commands

1)      Show  ip pim neighbor

2)      Show  ip pim Interfaces

3)      Show ip pim rp mappings

4)      Show ip igmp groups

5)      Show ip  mroute active

6)      Show ip mroute count

Debug commands

1)      #debug ip pim

Use the debug ip pim command to display PIM packets received and transmitted, as well as PIM related events.

2)       # debug ip igmp

Use the debug ip igmp command to display IGMP packets received and transmitted, as well as IGMP-host related events

IOS upgradation on cisco 10K router

                   

IOS Upgradation on 10K PE  &Troubleshooting commands

Follow below steps for 10K IOS upgradation:

- Copy latest IOS on bootflash from tftp server

Commands:

router#copy tftp: bootflash:

Address or name of remote host []? <tftp server IP>

Source filename []? <New IOS>

Destination filename <New IOS>     

<press enter>

 - Now copy this image into standby processor using following command:

router#copy bootflash:<New IOS>  stby-bootflash:

- Check IOS presence with following commands:

router # Show bootflash: (for Active )

router# Show stby-bootflash:  (for standby)

- The redundancy mode has to be configured as SSO.

Commands:

Router(config)#Redundancy

Router(config-red)#mode sso

- Change the boot order using following commands and reload the router.

router#configuration terminal

router(config)#boot system flash <New IOS >

router(config)#boot system flash <Old IOS >

router(config)#end

- Router will reload with new IOS image and config sync with standby processor.

- Check current IOS version on both processors with following commands:

Router # show issu state detail

output:

Router#sh issu state detail

                          Slot = B

                      RP State = Active

                    ISSU State = Init

                 Boot Variable = bootflash:c10k3-p11-mz.122-33.SB1b.fc2,12;bootflash:c10k3-p11-mz.122-31.SB10e.bin,12;

                Operating Mode = SSO

               Primary Version = N/A

             Secondary Version = N/A

               Current Version = bootflash:c10k3-p11-mz.122-33.SB1b.fc2

                Variable Store = PrstVbl

                     ROMMON CV = [bootflash:c10k3-p11-mz.122-33.SB1b.fc2]

                          Slot = A

                      RP State = Standby

                    ISSU State = Init

                 Boot Variable = bootflash:c10k3-p11-mz.122-33.SB1b.fc2,12;bootflash:c10k3-p11-mz.122-31.SB10e.bin,12;

                Operating Mode = SSO

               Primary Version = N/A

             Secondary Version = N/A

               Current Version = bootflash:c10k3-p11-mz.122-33.SB1b.fc2

- Above command will give details of current IOS version on both processors and operating mode.

Router #sh redundancy

Redundant System Information :

------------------------------

       Available system uptime = 2 weeks, 1 day, 6 hours, 42 minutes

Switchovers system experienced = 1

              Standby failures = 0

        Last switchover reason = user initiated

                 Hardware Mode = Duplex

    Configured Redundancy Mode = SSO

     Operating Redundancy Mode = SSO

              Maintenance Mode = Disabled

                Communications = Up

Current Processor Information :

-------------------------------

               Active Location = slot B

        Current Software state = ACTIVE

       Uptime in current state = 2 weeks, 1 day, 6 hours, 29 minutes

                 Image Version = Cisco IOS Software, 10000 Software (C10K3-P11-M), Version 12.2(33)SB1b, RELEASE SOFTWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2009 by Cisco Systems, Inc.

Compiled Fri 30-Jan-09 11:37 by prod_rel_team

                          BOOT = bootflash:c10k3-p11-mz.122-33.SB1b.fc2,12;bootflash:c10k3-p11-mz.122-31.SB10e.bin,12;

                   CONFIG_FILE =

                       BOOTLDR =

        Configuration register = 0x2102

Peer Processor Information :

----------------------------

              Standby Location = slot A

        Current Software state = STANDBY HOT

       Uptime in current state = 2 weeks, 1 day, 6 hours, 24 minutes

                 Image Version = Cisco IOS Software, 10000 Software (C10K3-P11-M), Version 12.2(33)SB1b, RELEASE SOFTWARE (fc2)

Technical Support: http://www.cisco.com/techsupport

Copyright (c) 1986-2009 by Cisco Systems, Inc.

Compiled Fri 30-Jan-09 11:37 by prod_rel_team

                          BOOT = bootflash:c10k3-p11-mz.122-33.SB1b.fc2,12;bootflash:c10k3-p11-mz.122-31.SB10e.bin,12;

                   CONFIG_FILE =

                       BOOTLDR =

        Configuration register = 0x2102

- “show redundancy” command can be used to check:

1)      Available system uptime of both processors

2)      Configured Redundancy Mode

3)      Operating Redundancy Mode

4)      Standby processor current software state (STANDBY HOT/ STANDBY COLD)

- STANDBY HOT indicates standby processor is ready to be active if primary processor fails.

- If current IOS is different on both processors then standby processor  will show as STANBY COLD indicating it is not ready to become ACTIVE.

- If this issue is faced then copy new image into standby processor and reload the router.

- This will change the Current Software state to STANDBY HOT.

- Following commands can be used to switchover the processor:

router(config)#redundancy force-switchover main-cpu

router(config)#testcrash (Hidden Command)

Juniper Command list

Command-Line Interface

The JUNOS software CLI contains two main modes: operational and configuration. The

names adequately describe the functions permitted within each environment

Operational mode

In operational mode, you enter commands to monitor and diagnose the software, network connectivity, and the router

Configuration mode

you configure the JUNOS software by creating a hierarchy of configuration statements. You can do this using the CLI or by creating a text (ASCII) file that contains the statement hierarchy. (The statement hierarchy is identical in both the CLI and the text configuration file.) You can configure all properties of the JUNOS software, including interfaces, general routing information, routing protocols, and user access, as well as several system hardware properties. When you have finished entering the configuration statements, you commit them, which activate the configuration on the router.

1.     configure or edit

You access the router’s configuration mode hierarchy with either the configure or edit command:

juniper@ROUTER-RE0> configure

Entering configuration mode

[edit]

juniper@ROUTER-RE0#

2.     configure exclusive

Exclude others from modifying the configuration database. Attempts by other users to modify the configuration while configure exclusive is active result in a descriptive error message, giving the owner, tty, and timestamp of the exclusive lock.

juniper@ROUTER-RE0> configure exclusive

3.     configure private

The configure private command allows multiple users to edit different parts of the configuration at the same time and to commit only their own changes, or to roll back without interfering with one another's changes. When you issue the configure private command, you work in a private candidate configuration, which is a copy of the most recently committed configuration.

juniper@ROUTER-RE0> configure private

warning: uncommitted changes will be discarded on exit

Entering configuration mode

4.     Run command

One very useful command that exists in configuration mode is run. When you use this command,the router allows you access to operational mode commands from within the configuration. This flexibility enables you to easily verify information on the router

[edit protocols ospf]

juniper@ROUTER-RE0# run show route

inet.0: 23 destinations, 24 routes (23 active, 0 holddown, 0 hidden)

+ =

Active Route

, - = Last Active, * = Both

1.1.1.0/24 *[OSPF/10] 00:40:41, metric 4

> via so-0/0/0.0

5.     Configuring interface

Go to the edit mode and configure the interface which needs to be configured.Say we want to configure a serial interface s-2/0/0

set interfaces so-2/0/0 description "connected to PE15-PAR-EU so-1/0/0"

set interfaces so-2/0/0 traps

set interfaces so-2/0/0 dce

set interfaces so-2/0/0 clocking external

set interfaces so-2/0/0 encapsulation frame-relay

set interfaces so-2/0/0 lmi lmi-type ansi

6.     Creating subinterface

Here we want to create say s-2/0/0.150

set interfaces so-2/0/0 unit 150 point-to-point

set interfaces so-2/0/0 unit 150 dlci 150

set interfaces so-2/0/0 unit 150 inverse-arp

set interfaces so-2/0/0 unit 150 family inet address 212.31.229.30/30

set interfaces so-2/0/0 unit 150 family mpls

7.     Reloading the Router

request system reboot

 juniper@ROUTER-RE0> request system reboot

Reboot the system ? [yes,no] (no) no

If want to rebbot at some fixed time:

juniper@ROUTER-RE0> request system reboot at 2100 message ?

Possible completions:

  <message>            Message to display to all users

juniper@ROUTER-RE0> request system reboot at 2100 message

8.     IOS Upgrade

We can upgrade the JUNOS software by using the request system software add filename command.

This command loads a software file from some location, often the user’s home directory, onto the internal flash on the Routing Engine.

juniper@ROUTER-RE0> request system software add <file name>

We must reboot the router to use the new software using the “request system reboot command”.

We also have the option of an automatic reboot by using the reboot option in conjunction with the request system software add filename command.

The process looks like this:

juniper@ROUTER-RE0> request system software add <file-name> reboot

9.     Configuring OSPF

Below commands put interface s01/3/0.150 in the area 0 and also configures the metric and other required parameters.

set protocols ospf area 0.0.0.0 interface so-1/3/0.150 metric 10

set protocols ospf area 0.0.0.0 interface so-1/3/0.150 hello-interval 1

set protocols ospf area 0.0.0.0 interface so-1/3/0.150 dead-interval 4

set protocols ospf area 0.0.0.0 interface so-1/3/0.150 authentication md5 1 key "KEY NAME"