Owner: User #71467

Powerman-1r Testing

Powerman-1r Testing

Xetron delivered ROCEM version 1.1 for 3560G.  Testing ROCEM for operational use on JQJADVERSE.  Operator was not able to provide a configuration for the 3560G - we only know that this 3560G is a core switch with a router on a stick configuration and in a VTPVLANVirtual Local Area Network Trunk Protocol enviroment.  Conop will be to first use ROCM to survey device and then subsequently use ROCEM to throw HG.  We are testing with a 3560G-24-PS, although Xetron's readme lists this ROCEM release is for 3560G-24-TS.  It is not believed that the power over ethernet feature should affect the implant.

Testing Summary

• Readme needs to be changed - show switch detail does not exist in this IOSApple operating system for small devices version
• Exit from ROCEM interactive session produces an SNMPSimple Network Management Protocol trap for connection close
• Connect/disconnect from ROCEM interactive session produces log messages in /var/log/syslog on AAASecurity Server from Cisco server - these are different than reported messages in Operational Use Notes
• While ROCEM interactive session active, credentials which normally login with privilege level 15 actually login with privilege level 1.  Attempts to enable produce error: Error in authentication
• While ROCEM interactive session active, new and existing telnet sessions are logged - AAASecurity Server from Cisco commands and start-stop messages recorded (this is not expected based on Operational Use Notes)
• With DUTDevice Under Test configured to log config changes locally, config changes made through ROCEM interactive session are logged to syslog.

Progress/Notes

1. Smoke Test - Survey 3560G with ROCEM
   1. 3560G is configured to use AAASecurity Server from Cisco server to authenticate users as well as authorize commands and log all commands entered
   2. 3560G is configured to log snmp traps and syslogs to Solarwinds
   3. Output of "who" command before ROCEM shows my console session and my vty session on line 1
      

      3560G#who
      Line User Host(s) Idle Location
      0 con 0 cisco idle 00:07:52
      * 1 vty 0 root idle 00:00:00 10.9.8.96

      Interface User Mode Idle Peer Address

      3560G#

   4. Verified that AAASecurity Server from Cisco is logging show commands when entered in 3560G through regular telnet session
   5. Followed Xetron Powerman-1R readme procedure to use ROCEM to execute show commands
      1. ./rocem_c3560-ipbase-mz.122-35.SE5.py -i -f fill.bin 192.168.111.1
      2. Entered y to proceed
      3. 3560# prompt appeared - no creds were netered
      4. Executed show commands from readme successfully - show switch detail does not exist in this IOS.  AAA does not log show commands entered through ROCEM to tac_accounting.log, no syslogs or SNMPSimple Network Management Protocol traps generated when commands entered
      5. AAA does log the ROCEM connection in /var/log/syslog:
                        tac_plus[1155]: connect from 172.20.100.14 [172.20.100.14] 
         Operational Use Notes details differences between AAASecurity Server from Cisco messages observed with ROCEM interactive session and without, however the messages seen are different on the AAASecurity Server from Cisco server during test than reported in the Operational Use Notes, likely due to AAASecurity Server from Cisco server configuration differences.
         
   6. Output of "who" command shows ROCEM vty session from ICON-CT IP and no username:
      

      3560G#who
      Line User Host(s) Idle Location
      0 con 0 root idle 00:04:10
      * 1 vty 0 root idle 00:00:00 10.9.8.96
      2 vty 1 idle 00:00:02 172.20.12.22

      
      
   7. Typed exit at ROCEM prompt - session closed, no logs generated to tac_accounting.log file, however connection close is logged in /var/log/syslog of AAASecurity Server from Cisco server (this is expected per Operational Use Notes).  Output of "who" shows vty session for ROCEM is gone.  No logs in 3560G logging buffer.  SNMP trap for the connection close is logged:
      CISCOTRAP-MIB:tcpConnectionClose 
      tsLineUser.2 =  
      loctcpConnOutBytes.192.168.111.1.XX.XXX.XX.XX (???).22.37770 = 78 
      loctcpConnInBytes.192.168.111.1.XX.XXX.XX.XX (???).22.37770 = 810 
      loctcpConnElapsed.192.168.111.1.XX.XXX.XX.XX (???).22.37770 = 0.50 second 
      tcpConnState.192.168.111.1.XX.XXX.XX.XX (???).22.37770 = synReceived(4) 
      tslineSesType.2.1 = telnet(5) 
      snmpTrapOID = CISCOTRAP-MIB:tcpConnectionClose 
      sysUpTime = 15 minutes 31.92 seconds
2. Performance Test - Survey 3560G with ROCEM
   1. Established traffic with IXIA to simulate network conditions on the device and repeated Test 1 procedure
      1. 900Mbps with 100000 max simultanoeous and per second superflows with constant data rate
      2. Breaking Point Enterprise traffic profile
      3. 11 minute test
   2. Baseline CPU without IXIA traffic or ROCEM activity - CPU utilization for five seconds: 5%/0%; one minute: 5%; five minutes: 5%
   3. With IXIA traffic, CPU levels are the same - CPU utilization for five seconds: 5%/0%; one minute: 5%; five minutes: 5%
   4. With IXIA traffic - only small increase in five second CPU spikes at the beginning of the test - 
      

          2    2 
      67955055555555

   5. Observed small spike in five second CPU to 15% during ROCEM survey in output of show proc cpu hist - this increase was also observed when entering the survey commands through regular telnet session

   6. Did not observe any log of ROCEM activity to syslog buffer, AAASecurity Server from Cisco server, or trap server with the exception of connection close trap noted in Step 1g.
3. Ad-hoc Test - Login to console while ROCEM set
   1. Established ROCEM interactive session on 3560G
   2. At console window, hit enter to bring up username prompt
   3. Enter username, and get password prompt
   4. Enter password - expected result - logged in with privilege 15.  Actual result, logged in as privilege level 1.  Type enable, but 3560G does not accept the enable password.  Can't get into enable mode.  Error message received - Error in authentication. Login in logged to AAASecurity Server from Cisco server.
   5. Exited ROCEM interactive session - must logout from privilege 1 mode and enter username and password again, this time with expected result of privilege level 15.
4. Ad-hoc Test - Login via telnet during ROCEM interactive session
   1. same result observed as above - cannot get into enable mode with root user during ROCEM interactive session.  Logged in as privilege level 1 and cannot get authenticated to enable mode.  Exited ROCEM interactive seesion and exit and attempt to login again to restore expected result.
5. Ad-hoc Test - Local authentication of users - no AAA
   1. Disabled tacacas on Target Device and enabled local authentication
   2. Verified that cisco user authenticates with privilege level 15 using local database
   3. Attempted to telnet into Target Deivce while ROCEM session active
   4. Cisco user now is logged in as privilege level 1.  Cisco user can enable to privilege 15 by entering enable and then the enable password.
6. Ad-hoc Test - Fill up vty lines during  ROCEM interactive session
   1. Establish ROCEM interacive session
   2. Establish 15 more telnet sessions with Target Device (in priv level 1)
   3. Attempt another connection - connection is refused - expected behavior
   4. Exit ROCEM and attempt another connection again - this time connection is successful, priv level 15.
7. Ad-hoc Test - SNMPSimple Network Management Protocol traps sent during interactive session
   1. During an interactive session, bounced an interface and saved config to generate SNMPSimple Network Management Protocol traps - as per Operational Use Notes, no SNMPSimple Network Management Protocol trap generated during interactive session
8. Ad-hoc Test - Logging of logins during interactive session
   1. Established interactive session and then logged in via telnet and console - start/stop of logins were logged to AAASecurity Server from Cisco server.  This is not expected because Operational Use Notes state that "While an interactive session is active, logging is disabled for all existing and new telnet sessions."
   2. Show commands entered from a regular telnet session while interactive ROCEM session active also log to AAASecurity Server from Cisco server.
9. Test EAREnterprise Archive 4694 - Confirmed
   1. Created a user larry in tac_plus and denied show commands, assigned privilege level 1
   2. Enabled tac_plus autorization and verified that larry is not authorized to issue show ver
   3. Established interactive session.
   4. Verified that larry is now authorized to issue show commands
   5. Exited interactive session and verified that larry can no longer issue unauthorized by AAASecurity Server from Cisco commands
10. Ad-hoc Test - reload device with ROCEM session
    1. Established ROCEM interactive session
    2. Entered reload and hit enter to confirm.
    3. Switch reloaded with message:  %SYS-5-RELOAD: Reload requested by vty0 (172.20.12.22). Reload Reason: Reload Command.
11. Set / Un-Set Test - Test basic funcationality with set command
    1. CT# ./rocem.py -s 172.20.100.14
       1. Initial survey information displays and asks to type "y" to proceed
       2. "y" pressed to proceed, connection created and ends with "done"
    2. telnet to DUTDevice Under Test produces an enable prompt with priv level 15 utilizing no credentials
       1. No commands logged to AAASecurity Server from Cisco or traps sent to SNMPSimple Network Management Protocol server
       2. Commands run in the telnet session still log to the DUTDevice Under Test under "sh logging"
    3. CT# ./rocem.py -u 172.20.100.14
       1. Survey information displays again and asks to type "y" to proceed
       2. "y" pressed to proceed, connection created and ends with "done" again
    4. telnet to DUTDevice Under Test produces prompt for creds.  root/password entered which gives enable prompt
       1. Issuing several commands again logs to SNMPSimple Network Management Protocol server, AAA, and still to the DUTDevice Under Test local logging
12. Ad-hoc - Test if configuration changes made through ROCEM interactive session will be logged to local syslog
    1. Configure DUTDevice Under Test to log configuration changes to local buffer and syslog
       

       archive
       log config
       logging enable
       notify syslog
       hidekeys

    2. Establish ROCEM session and make configuration changes to test if they are added to "show log" output of local log buffer:

       1. changed interface description on g0/28 as a test through ROCEM interactive session

    3. Check local log buffer to see if commands were logged - observe commands logged to local buffer with no username

       000051: Jun 3 11:01:56.097: %PARSER-5-CFGLOG_LOGGEDCMD: User:unknown user logged command:interface GigabitEthernet0/28
       000052: Jun 3 11:01:57.565: %PARSER-5-CFGLOG_LOGGEDCMD: User:unknown user logged command:description test
       000053: Jun 3 11:01:59.561: %PARSER-5-CFGLOG_LOGGEDCMD: User:unknown user logged command:no description