Author Archives: admin

show module fex

To verify hardware status on FEX on Cisco Nexus Operating System.

show environment fex 100                                                                                                                                                          


Temperature Fex 100:
-----------------------------------------------------------------
Module   Sensor     MajorThresh   MinorThres   CurTemp     Status
                    (Celsius)     (Celsius)    (Celsius)         
-----------------------------------------------------------------
1        Outlet-1   92            89           42          ok             
1        Outlet-2   76            68           38          ok             
1        Inlet-1    61            53           37          ok             
1        Die-1      92            85           48          ok             


Fan Fex: 100:
------------------------------------------------------
Fan             Model                Hw         Status
------------------------------------------------------
Chassis         N2K-C2232-FAN        --         ok
PS-1            N2200-PAC-400W       --         failure
PS-2            N2200-PAC-400W       --         ok


Power Supply Fex 100:
---------------------------------------------------------------------------
Voltage: 12 Volts
-----------------------------------------------------
PS  Model                Power       Power     Status
                         (Watts)     (Amp)           
-----------------------------------------------------
1   --                        --        --     fail/shutdown       
2   N2200-PAC-400W        396.00     33.00     ok                  


Mod Model                Power     Power       Power     Power       Status
                         Requested Requested   Allocated Allocated         
                         (Watts)   (Amp)       (Watts)   (Amp)               
--- -------------------  -------   ----------  --------- ----------  ----------
1    N2K-C2232TM-10GE    102.00    8.50        102.00    8.50        powered-up


Power Usage Summary:
--------------------
Power Supply redundancy mode:                 redundant

Total Power Capacity                              396.00 W

Power reserved for Supervisor(s)                  102.00 W
Power currently used by Modules                     0.00 W

                                                -------------
Total Power Available                             294.00 W
                                                -------------
Pearl-N5K-02# 


linkFlapErrDisabled error on cisco Nexus5500 Chassis

linkFlapErrDisabled error on cisco Nexus5500 Chassis

We observed linkFlapErrDisabled error on interface ethernet 2/7 on cisco Nexus5548 Chassis. We observed link flap on this interface 1week(s) 1day(s) ago.

Nexus5500# sh interface ethernet 2/7
Ethernet2/7 is down (linkFlapErrDisabled)
Dedicated Interface
Hardware: 1000/10000 Ethernet, address: 002a.6a18.ff86 (bia 002a.6a18.ff86)
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is trunk
auto-duplex, 10 Gb/s, media type is 10G
Beacon is turned off
Input flow-control is on, output flow-control is on
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped 1week(s) 1day(s)
Last clearing of "show interface" counters never
32 interface resets
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)

We did a shut and unshut on this port and we see interface 2/7 up.

Nexus5500# conf t
Enter configuration commands, one per line. End with CNTL/Z.
Nexus5500(config)# int ethernet 2/7
Nexus5500(config-if)# shu
Nexus5500(config-if)# no shut
Nexus5500(config-if)# end
Nexus5500# sh interface ethernet 2/7
Ethernet2/7 is up
Dedicated Interface
Hardware: 1000/10000 Ethernet, address: 002a.6a18.ff86 (bia 002a.6a18.ff86)
MTU 1500 bytes, BW 10000000 Kbit, DLY 10 usec
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA
Port mode is trunk
full-duplex, 10 Gb/s, media type is 10G
Beacon is turned off
Input flow-control is on, output flow-control is on
Rate mode is dedicated
Switchport monitor is off
EtherType is 0x8100
Last link flapped 00:00:04
Last clearing of "show interface" counters never
33 interface resets
30 seconds input rate 0 bits/sec, 0 packets/sec
30 seconds output rate 0 bits/sec, 0 packets/sec
Load-Interval #2: 5 minute (300 seconds)

Power supply not recognized by M-series router

Some power supplies for M7i and M10i might contain an incorrectly programmed I2C ID.
As a result the following errors appear in the show chassis alarms output:

  user@M10i-re0> show chassis alarms 
  2 alarms currently active
  Alarm time               Class  Description
  2006-11-29 16:21:22 GMT  Major  PEM 0 Unrecognized for the platform
  2006-11-29 16:21:22 GMT  Major  PEM 1 Unrecognized for the platform

A fix is provided in JUNOS  8.1R2, 8.2R1 and higher JUNOS releases.

Below there is an example with a step by step procedure:

  • Check which power supplies are not recognized properly:
        root@Junos-re0> show chassis alarms
        2 alarms currently active
        Alarm time               Class  Description
        2006-11-29 16:21:22 GMT  Major  PEM 0 Unrecognized for the platform
        2006-11-29 16:21:22 GMT  Major  PEM 1 Unrecognized for the platform
  • Go to the shell and and use command su to change to super-user:
        root@Junos-re0> start shell 
        % su
        Password:
        root@Junos-re0%
  • Use the smbc command to read out the currently (incorrectly) programmed I2C ID for PSU in slot 0:
        root@Junos-re0% smbc -g 2 -o 5 0x56 1
        Read from bus address 0x56 returns:
        0x06
  • Re-program the I2C ID for the same PSU:
        root@Junos-re0% smbc -w -g 2 -o 5 0x56 0x0E
  • Verify if the the I2C IC has been programmed correctly
        root@Junos-re0% smbc -g 2 -o 5 0x56 1
        Read from bus address 0x56 returns:
        0x0e
  • Repeat the same steps for PSU in slot 1
        root@Junos-re0% smbc -g 3 -o 5 0x56 1
        Read from bus address 0x56 returns:
        0x06
        root@Junos-re0% smbc -w -g 3 -o 5 0x56 0x0E
        root@Junos-re0% smbc -g 3 -o 5 0x56 1
        Read from bus address 0x56 returns:
        0x0e
  • Go back to the shell

root@Junos-re0% exit

Chassisd has to be restarted in order to have the alarms cleared.  Note: This is traffic affecting! :

    root@Junos-re0> restart chassis-control
    Chassis control process started, pid 3553
Verify that no PSU related alarms are active:

    root@Junos-re0> show chassis alarms
    No alarms currently active

show system snapshot media internal – To know Junos installed in both partitions of Ex

root> show system snapshot media internal 
fpc0:
--------------------------------------------------------------------------
Information for snapshot on       internal (/dev/da0s1a) (primary)
Creation date: Feb 11 23:59:41 2013
JUNOS version on snapshot:
  jbase  : ex-12.3R1.7
  jcrypto-ex: 12.3R1.7
  jdocs-ex: 12.3R1.7
  jroute-ex: 12.3R1.7
  jswitch-ex: 12.3R1.7
  jweb-ex: 12.3R1.7
Information for snapshot on       internal (/dev/da0s2a) (backup)
Creation date: Feb 6 08:38:13 2013
JUNOS version on snapshot:
  jbase  : 11.3R4.2
  jcrypto-ex: 11.3R4.2
  jdocs-ex: 11.3R4.2
  jroute-ex: 11.3R4.2
  jswitch-ex: 11.3R4.2
  jweb-ex: 11.3R4.2

{master:0}
root> 

show system storage partitions – Show active partitions information for the boot media in juniper ex

root> show system storage partitions 
fpc0:
--------------------------------------------------------------------------
Boot Media: internal (da0)
Active Partition: da0s1a         <<<< Ex is currently booted from slice da0s1a partition
Backup Partition: da0s2a
Currently booted from: active (da0s1a)

Partitions information:
  Partition  Size   Mountpoint
  s1a        183M   /         
  s2a        184M   altroot   
  s3d        369M   /var/tmp  
  s3e        123M   /var      
  s4d        62M    /config   

{master:0}
root> 

show chassis firmware – Verify jloader version

root@Ex4200VC> show chassis firmware no-forwarding

Part                     Type       Version
FPC 0                    uboot      U-Boot 1.1.6 (Mar 26 2011 - 04:42:33) 1.0.0
                         loader     FreeBSD/PowerPC U-Boot bootstrap loader 2.4
FPC 1                    uboot      U-Boot 1.1.6 (Mar 26 2011 - 04:42:33) 1.0.0
                         loader     FreeBSD/PowerPC U-Boot bootstrap loader 2.4

show chassis routing-engine

root@Ex4200VC> show chassis routing-engine 

Routing Engine status:
  Slot 0:
    Current state                  Master
    Election priority              Master (default)
    Temperature                 52 degrees C / 125 degrees F
    CPU temperature             52 degrees C / 125 degrees F
    DRAM                      1024 MB
    Memory utilization          34 percent
    CPU utilization:
      User                       3 percent
      Background                 0 percent
      Kernel                     2 percent
      Interrupt                  0 percent
      Idle                      95 percent
    Model                          EX4200-48P, 48 POE
    Serial ID                      BQ02103ABCDE
    Start time                     2011-03-19 23:36:30 GMT
    Uptime                         18 days, 12 hours, 59 minutes, 32 seconds
    Last reboot reason             Router rebooted after a normal shutdown.
    Load averages:                 1 minute   5 minute  15 minute
                                       0.43       0.18       0.11
Routing Engine status:
  Slot 1:
    Current state                  Backup
    Election priority              Backup (default)
    Temperature                 36 degrees C / 96 degrees F
    CPU temperature             36 degrees C / 96 degrees F
    DRAM                      1024 MB
    Memory utilization          26 percent
    CPU utilization:
      User                       8 percent
      Background                 0 percent
      Kernel                    11 percent
      Interrupt                  0 percent
      Idle                      81 percent       
    Model                          EX4200-48P, 48 POE
    Serial ID                      BQ02104ABCDE
    Start time                     2011-03-19 23:36:24 GMT
    Uptime                         18 days, 12 hours, 59 minutes, 38 seconds
    Last reboot reason             Router rebooted after a normal shutdown.
    Load averages:                 1 minute   5 minute  15 minute
                                       0.07       0.03       0.00

How to copy files from one location to another in a Routing Engine

How to copy files from one location to another in a Routing Engine

Copy file from one directory to another:

In order to move files from one directory to another on a local router, use the following command:

user@host> file copy
user@host> file copy /var/log/file1.txt /var/tmp/

In this example, file file1 is copied from the /var/log directory to /var/tmp.

Copy a file from one Routing Engine to another:

On Dual Routing engine routers, copy a file from one RE to another RE, use the following command:

user@host> file copy /var/tmp/jinstall-11.2R1.7-domestic-signed.tgz re1:/var/tmp/

In this example, when run in the Master RE, the Junos image on the Master RE is copied from the /var/tmp/ directory to the /var/tmp/ directory on the Backup RE.

system services

root@Ex# set ?
Possible completions:
+ apply-groups         Groups from which to inherit configuration data
+ apply-groups-except  Don't inherit configuration data from these groups
> dhcp                 Configure DHCP server
> finger               Allow finger requests from remote systems
> ftp                  Allow FTP file transfers
> netconf              Allow NETCONF connections
> outbound-ssh         Initiate outbound SSH connection
> service-deployment   Configuration for Service Deployment (SDXD) management application
> ssh                  Allow ssh access
> subscriber-management  Subscriber management configuration
> telnet               Allow telnet login
> tftp-server          Allow TFTP file transfers in default routing instance
> web-management       Web management configuration
> xnm-clear-text       Allow clear text-based JUNOScript connections
> xnm-ssl              Allow SSL-based JUNOScript connections
[edit system services]
root@Ex# set

Issues with logging into EX Virtual Chassis via SSH and HTTP

What needs to be checked if we encounter issues with SSH and HTTP in Juniper Ex?

SSH:

If you encounter issues with users not able to log into the switch using SSH, check the following:

  •     SSH is properly configured. root@EX# set system services ssh
  •     No firewall filters for TCP blocking SSH.  root@EX3# show firewall  
  •     Make sure the directory /var/empty exists.

SSH access in juniper ex

If the directory is not present, create it as shown below:

    %cd /var
    %mkdir empty

HTTP/HTTPS:

If you are not able to log in to the switch using HTTP/HTTPS, check the following.

  •     HTTP is properly configured under web management.

root@SW1# set system services web-management http   

  •     No firewall filters blocking http traffic.
  •     Clear the cache in the browser 

The directory structure for HTTP is as below:

/packages/mnt/jweb-ex-9.5R2.7/jail/var/etc