SG-300 QoS Cisco on SNMP statistics

Similar Questions

• Cisco SG300 SNMP with cacti

  I installed Cacti on ubuntu 14.04 and I'm trying to add a Cisco sg300.

  If the switch is configured like this:
  Server SNMP My Office location
  SNMP Server contact [email protected] / * /
  SNMP community - server MyC0mmun1ty ro 192.168.10.25 view by default

  I then in the settings of the device

  SwitchName Description
  The switch ip host name

  Cisco to host model router
  number of threads 1
  disable the unchecked host

  shot detection snmp device operating time
  ping timeout 400
  try again to pin 1

  SNMP version 2
  Community SNMP MyC0mmun1ty
  SNMP port 161
  SNMP timeout 500
  OIDs maximum 10

  from the cactus Server (192.168.10.25) if I have
  Nmap - sU Pei 161 switch ip of see:
  161/udp snmp open

  also on the sg300 I had to enable snmp in the security settings where ssh/telnet etc. is and have saved the config.

  But watch the cactus
  SNMP information
  SNMP error

  OK, I suggest you enable the SNMP agent on unrestricted IP switch, IE replace command:

   snmp-server community MyC0mmun1ty ro 192.168.10.25 view Default

  with the command:

   snmp-server community MyC0mmun1ty ro view Default

  and again snmpwalk. If it will work now, your SNMP to Cacti server applications are sourcing from another IP than 192.168.10.25 (your Cacti server configured several IP?).

• Cisco ASA snmp

  Hello

  can I configure snmp specific to a server snmp traps and pitfalls different snmp for another snmp Server?

  Thank you

  To my knowledge, this is not possible, as the ASA can only send SNMP traps to a single SNMP server at any given time.

  --

  Please do not forget to select a correct answer and rate useful posts

• TMS - SNMP Traphost endpoint address

  I see the address field traphost SNTP under the view 'Settings' for a C-Series, EX, E20 end points that are managed by TMS?  Is it acceptable to leave this field blank or does it contain IP address or DNS of TMS, jointly with the SNTP parameters on the endpoint itself?

  Thanks, Patrick

  Hi Patrick, for endpoints TMS Cisco uses SNMP to communicate with, the Traphost IP address is also defined. This is done automatically on all systems if management settings apply to systems is enabled in the network settings > Service TMS Cisco component.

• Cannot ping inside the vpn client hosts. It's a NAT problem

  Hello everyone, I'm running into what seems to be a cause of exclusion with an IOS IPSEC VPN NAT/nat. I can connect to the VPN with cisco IPSEC VPN client, and I am able to authenticate. Once I have authenticate, I'm not able to reach one of the guests inside. Below is my relevant config. Any help would be greatly appreciated.

  AAA new-model

  !

  !

  AAA authentication login default local

  radius of group AAA authentication login userauthen

  AAA authorization exec default local

  AAA authorization groupauthor LAN

  crypto ISAKMP policy 3

  BA 3des

  preshared authentication

  Group 2

  !

  ISAKMP crypto client configuration group businessVPN

  key xxxxxx

  DNS 192.168.10.2

  business.local field

  pool vpnpool

  ACL 108

  Crypto isakmp VPNclient profile

  businessVPN group identity match

  client authentication list userauthen

  ISAKMP authorization list groupauthor

  client configuration address respond

  !

  !

  Crypto ipsec transform-set esp-3des esp-sha-hmac RIGHT

  !

  Crypto-map dynamic dynmap 10

  Set transform-set RIGHT

  Define VPNclient isakmp-profile

  market arriere-route

  !

  !

  10 ipsec-isakmp crypto map clientmap Dynamics dynmap

  interface Loopback0

  IP 10.1.10.2 255.255.255.252

  no ip redirection

  no ip unreachable

  no ip proxy-arp

  IP virtual-reassembly

  !

  Null0 interface

  no ip unreachable

  !

  interface FastEthernet0/0

  IP 111.111.111.138 255.255.255.252

  IP access-group outside_in in

  no ip redirection

  no ip unreachable

  no ip proxy-arp

  NAT outside IP

  inspect the outgoing IP outside

  IP virtual-reassembly

  automatic duplex

  automatic speed

  clientmap card crypto

  !

  the integrated-Service-Engine0/0 interface

  description Locator is initialized with default IMAP group

  IP unnumbered Loopback0

  no ip redirection

  no ip unreachable

  no ip proxy-arp

  IP virtual-reassembly

  ip address of service-module 10.1.10.1 255.255.255.252

  Service-module ip default gateway - 10.1.10.2

  interface BVI1

  IP 192.168.10.1 255.255.255.0

  no ip redirection

  no ip unreachable

  no ip proxy-arp

  IP nat inside

  IP virtual-reassembly

  IP nat inside source static tcp 192.168.10.2 25 interface FastEthernet0/0 25

  IP nat inside source static tcp 192.168.10.2 443 interface FastEthernet0/0 443

  IP nat inside source static tcp 192.168.10.2 3389 interface FastEthernet0/0 3389

  IP nat inside source map route nat interface FastEthernet0/0 overload

  nat extended IP access list

  deny ip 192.168.10.0 0.0.0.255 192.168.109.0 0.0.0.255

  refuse the 10.1.1.0 ip 0.0.0.255 192.168.109.0 0.0.0.255

  ip licensing 10.1.1.0 0.0.0.255 any

  permit ip 192.168.10.0 0.0.0.255 any

  sheep extended IP access list

  permit ip 192.168.10.0 0.0.0.255 192.168.109.0 0.0.0.255

  ip permit 10.1.10.0 0.0.0.255 192.168.109.0 0.0.0.255

  ip licensing 10.1.1.0 0.0.0.255 192.168.109.0 0.0.0.255

  outside_in extended IP access list

  permit tcp object-group Yes_SMTP host 111.111.111.138 eq smtp

  permit any any eq 443 tcp

  permit tcp 20.20.20.96 0.0.0.31 host 111.111.111.138 eq 3389

  permit tcp 20.20.20.96 0.0.0.31 host 111.111.111.138 eq 22

  allow any host 111.111.111.138 esp

  allow any host 111.111.111.138 eq isakmp udp

  allow any host 111.111.111.138 eq non500-isakmp udp

  allow any host 111.111.111.138 ahp

  allow accord any host 111.111.111.138

  access-list 108 allow ip 192.168.109.0 0.0.0.255 192.168.10.0 0.0.0.255

  access-list 108 allow ip 192.168.109.0 0.0.0.255 10.1.1.0 0.0.0.255

  access-list 108 allow ip 192.168.109.0 0.0.0.255 10.1.10.0 0.0.0.255

  !

  !

  !

  !

  route nat allowed 10 map

  match ip address nat

  1 channel ip bridge

  In my view, the acl applied to customer is back. It must allow traffic from the internal network to the pool of customers.

  To confirm, you can open the Cisco VPN client statistics (after login) then go in the route Details tab. We should see the networks you should be able to reach the customer. Make sure that the good ones are here.

  Kind regards

• Reg: Ganymede configuration

  Hi all

  I'm trying to configure the authentication of routers around 300 by Cisco GANYMEDE, AAA I installed acs4.2 on a windows Server 2003 and updated as a result of orders from AAA in the router, the RADIUS server host and the key on trialrouter

  AAA new-model

  !

  !

  AAA authentication login default group Ganymede + local

  NO_AUTHEN AAA authentication login no

  AAA authorization config-commands

  AAA authorization exec default group Ganymede + authenticated if

  NO_AUTHOR AAA authorization exec no

  AAA authorization commands 1 default group Ganymede + authenticated if

  AAA authorization commands 1 NO_AUTHOR no

  AAA authorization commands 15 default group Ganymede + authenticated if

  AAA authorization commands 15 NO_AUTHOR no

  AAA authorization network series none

  AAA accounting exec default start-stop Ganymede group.

  accounting AAA commands default 15 stop only Ganymede group.

  !

  AAA - the id of the joint session

  then I created a user and mentioned a secret key on the acs server, I added this router as an AAA client, the router no longer meets the old login name and password but did not username set to GBA, where I am a mistake? Kindly help.

  Thank you.

  ANU,

  Are you Ganymede username-password prompt?

  If you get the username-password prompt and it isn't taking Ganymede credentials, could you please connect with the local user name-password and run him debugs.

  debugging Ganymede

  Debug aaa authentication

  term Lun

  After this attempt to connect again with Ganymede username-password and send me the output.

  Fix the failure of GBA attemopts > reports and activity.

  HTH
  JK

  The rate of useful messages-

• Cisco SG-300 52 QoS default DSCP to queue mapping

  I am setting up QoS (Advanced mode) switch Cisco SG - 300 52.

  I decided to go with DSCP to manage the priority of the packet. While the implementation I found a configuration page (see the attachment for screenshot) where it is possible to map DSCP values in a particular queue. I did not quite understand the default settings of this mapping.

  The assignment of the queue increases from 1 to 4 for 0 to 47 DSCP values. Well, the 48-63 DSCP values were assigned #3 queue. In this way the package with value DSCP 56 will have lower priority than package with value DSCP 40. It makes no sense to me. Should not increase the priority (and thus the queue) that the increase of DSCP values?

  Why the 48-63 DSCP values were assigned #3 as default file?

  DSCP - default.png

  

  I think that the answer to this direct request found in RFC 2475

  Here is the link to the RFC.

  https://www.ietf.org/RFC/rfc2475.txt

  I think the info you're looking for are under classifiers. I deny not that under any normal logic to increment just respectively. For some reason, it was the standard/normal values agreed.

  I don't know with the first 6 bits in binary has something to do with the decimal value (expressed in a number which is not binary DSCP).  Also, I think it has to do with how the cycle increments of 8 values.

  By RFC 791, here are the priority values.

  https://www.ietf.org/RFC/RFC791.txt

  Example:

  000 = Best Effort

  001 = priority

  010 = immediate

  011 = audio/video.

  100 = flash on Ride

• Configuration of SNMP on Cisco Small Business 300 Series managed switch

  Please can someone help me configure SNMP on Cisco Small Business 300 series switch?

  Thank you

  Hi Anton,.

  Don't forget to activate the service SNMP is first of all: Security > Services TCP/UDP.

  http://sbkb.Cisco.com/CiscoSB/UKP.aspx?VW=1&docid=3b13278d9ef9402a8fef57...

  also, you will find useful documents for configuration etc on our server community kb:

  http://sbkb.Cisco.com/CiscoSB/UKP.aspx?VW=1&docid=183cae2148d445b2a07473...

  Let us know if you have any problems.

  Aleksandra

• Cisco QoS for VoIP 300

  I have a question about best practices for packages of priority voice on the LAN side.

  We have everything configured on the firewall/edge device for the prioritization of voice, however I'm not sure of the exact to take sideways steps LAN to make sure that the LAN traffic will not affect voice quality.

  A very basic configurations: vlan 1 (the default) for data and vlan 100 (voice) - the ports are configured as general (1untagged, 10tagged).

  At this point, the phones are manually set with a vlan, but form read these forums I see that I can accomplish this by creating LLDP and automatically assigned to him the vlan instead, manual setting

  My main concern, however, as mentioned above, is QoS.

  Does anyone have a good practice or advice on how to Setup QoS specially for the voice.

  I found this pdf file, but I didn't know where they came up with the EIF and CBS values.

  https://supportforums.Cisco.com/docs/doc-13461

  This is my first post on the forums; Thanks in advance for any help provided.

  Hi Thomas, this is done automatically through the QoS of Basic. Within a bunch of tag VLAN, it is a value of CFP (3 bits). When the switch receives such framework it will honor the value based on this value of CFP.

  -Tom
  Please mark replied messages useful
  http://blogs.Cisco.com/smallbusiness/

• StorCenter px6 - 300 d SNMP SNMP problem after FW update to 4.0.2.9960

  Hello

  We have a problem in PX6 - 300 d, after the upgrade from version 3.2.3.15290 to 4.0.2.9960, FW SNMP configuration. Ishmael of application allows us to manage matrices. After updating the FW one of storage, the application can no longer collect information. Notify know if there was no change of FW which caused this problem?

  SNMP parameters in storage, are equal, the difference in this version of the FW of storage.

  Thank you for your help

  Adias

  Hi adias.

  There is a newer version of the firmware. I recommend updating to the latest version to see if the problem persists.

  Firmware Version 4.0.8.23976 for px6 - 300 d

• Using SNMP to monitor Cisco Nexus 5000

  Hello

  I would like to know what specific OID to use to monitor the following using SNMP on a Nexus 5000:

  -L' total CPU usage

  -Power supply status

  -Status of Fan chassis

  The Nexus is quite different from other devices Cisco - any help will be appreciated!

  CPU: oid to use is: 1.3.6.1.4.1.9.9.305.1.1.1 (cseSysCPUUtilization) is a part of the MIB:

  CISCO-SYSTEM-EXT-MIB

  It displays the value as a percentage of the processor.

  ME-TestBed-A (nxos) # display system resources

  Load average: 1 minute: 0.26 5 minutes: 0.41 15 minutes: 0.43

  Process: 393 1 total, running

  CPU States: inactive user of 1.0%, 4.0% of the kernel, 95.0%

  Memory usage: total 3634820K, 1728600K used, 1906220K free

  81256K buffers, 1037176K cache

  DHCP-171-69-89-49: ~ lulu-mbp$ snmpwalk - public - Cabarrus 2 c 172.25.180.5

  1.3.6.1.4.1.9.9.305.1.1.1

  SNMPv2-SMI::enterprises.9.9.305.1.1.1.0 = Gauge32 : 5

  As you can see, show sys resources indicates 95% idle, valuation is 5% cpu and the snmp poster value.

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

  Power and Fans, it is fairly limited

  The cisco mib envmon is not yet supported on the 5K, looks like.

  This leaves us with the FRU mib: 1.3.6.1.4.1.9.9.117 ftp://ftp.cisco.com/pub/mibs/oid/CISCO-ENTITY-FRU-CONTROL-MIB.oid

  The index values will come from oid: entPhysicalTable)

  1.3.6.1.2.1.47.1.1.1) is part of the ENTITY-MIB

  DHCP-171-69-89-49: ~ lulu-mbp$ snmpwalk - public - Cabarrus 2 c 172.25.180.5

  1.3.6.1.4.1.9.9.117

  SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.1.470 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.1.1000470 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.2.470 = STRING : « CentiAmps @ 12V »

  SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.2.1000470 = STRING : « CentiAmps @

  12V.

  SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.3.470 = INTEGER : 4538

  SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.3.1000470 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.4.470 = INTEGER : 29

  SNMPv2-SMI::enterprises.9.9.117.1.1.1.1.4.1000470 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.22 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.23 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.470 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.1000022 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.1000470 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.1.3000022 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.22 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.23 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.470 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.1000022 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.1000470 = INTEGER : 4

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.3000022 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.22 = ENTIER :-2910

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.23 = INTEGER : -83

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.470 = INTEGER : 29

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.1000022 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.1000470 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.3.3000022 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.1.3.0 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.1.22 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.1.23 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.1.1000022 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.1.3000022 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.2.22 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.2.23 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.2.1000022 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.2.3000022 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.3.22 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.3.23 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.3.1000022 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.3.3000022 = INTEGER : 0

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.4.22 = Timeticks : 0:00:10.27 (1027)

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.4.23 = Timeticks : 0:01:25.20 (8520)

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.4.1000022 = Timeticks :

  (41634711) 4 days, 19:39:07.11

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.4.3000022 = Timeticks :

  (41634712) 4 days, 19:39:07.12

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.5.22 = Timeticks : (0) 0:00:00.00

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.5.23 = Timeticks : (0) 0:00:00.00

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.5.1000022 = Timeticks : (0)

  0:00:00.00

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.5.3000022 = Timeticks : (0)

  0:00:00.00

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.6.22 = « »

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.6.23 = « »

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.6.1000022 = « »

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.6.3000022 = « »

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.22 = Gauge32 : 0

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.23 = Gauge32 : 0

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.1000022 = Gauge32 : 0

  SNMPv2-SMI::enterprises.9.9.117.1.2.1.1.8.3000022 = Gauge32 : 0

  SNMPv2-SMI::enterprises.9.9.117.1.3.1.0 = ENTIER : 1

  SNMPv2-SMI::enterprises.9.9.117.1.4.1.1.1.534 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.4.1.1.1.535 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.4.1.1.1.536 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.4.1.1.1.537 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.10 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.22 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.23 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.149 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.214 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.215 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.278 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.279 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.342 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.343 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.470 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.534 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.535 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.536 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.537 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4950 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4951 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4952 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4953 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4954 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4955 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4956 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4957 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4958 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4959 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4960 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4961 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4962 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4963 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4964 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4965 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4966 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4967 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4968 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.4969 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5206 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5207 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5208 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5209 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5210 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5211 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5212 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.5213 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21590 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21591 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21592 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21593 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21594 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21595 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21596 = INTEGER : 2

  SNMPv2-SMI::enterprises.9.9.117.1.5.1.1.1.21602 = INTEGER : 2

  You can read in:

  FTP://FTP.Cisco.com/pub/MIBs/v1/Cisco-entity-FRU-control-MIB-V1SMI.my

  that means values integer by OID.

  Take for example (look at the file

  ( ftp://ftp.cisco.com/pub/mibs/oid/CISCO-ENTITY-FRU-CONTROL-MIB.oid)

  cefcFRUPowerOperStatus: 1.3.6.1.4.1.9.9.117.1.1.2.1.2 for one of the

  index:

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.22 = INTEGER : 2

  We now need to find 22-year-old:

  SNMPv2-SMI::mib-2.47.1.1.1.1.7.22 = STRING : « 20 port 10GE SFP + / superviseur

  in the Module fixed-1"

  That means now the INTEGER 2 from:

  SNMPv2-SMI::enterprises.9.9.117.1.1.2.1.2.22 = INTEGER : 2

  Lets look at: CISCO-ENTITY-FRU-CONTROL-MIB-V1SMI.my, section

  cefcFRUPowerOperStatus, if you are looking for in this file you will find: we (2),

  That measn this controller is actually turned on and powered.

• This version of Cisco Adaptive Security Appliance Software Version 9.6 (1) 5 is affected by Cisco Adaptive Security Appliance SNMP Remote Code execution vulnerability and Cisco Adaptive Security Appliance CLI Remote Code execution vulnerability of

  This version of Cisco Adaptive Security Appliance Software Version 9.6 (1) 5 is affected by Cisco Adaptive Security Appliance SNMP Remote Code execution vulnerability and Cisco Adaptive Security Appliance CLI Remote Code execution vulnerability of

  Hi vrian_colaba,

  You can take a look at cisco's Advisory here:

  https://Tools.Cisco.com/Security/Center/content/CiscoSecurityAdvisory/CI...

  Fixed versions

  Cisco ASA Major Release	First version fixed
  7.2	Affected; migrate to 9.1.7(9) or later
  8.0	Affected; migrate to 9.1.7(9) or later
  8.1	Affected; migrate to 9.1.7(9) or later
  8.2	Affected; migrate to 9.1.7(9) or later
  8.3	Affected; migrate to 9.1.7(9) or later
  8.4	Affected; migrate to 9.1.7(9) or later
  8.5	Affected; migrate to 9.1.7(9) or later
  8.6	Affected; migrate to 9.1.7(9) or later
  8.7	Affected; migrate to 9.1.7(9) or later
  9.0	9.0.4 (40)
  9.1	9.1.7(9)
  9.2	9.2.4 (14)
  9.3	9.3.3 (10)
  9.4	9.4.3(8) ETA 26/08/2016
  9.5	9.5 (3) ETA 30/08/2016
  9.6 (DFT)	9.6.1 (11) / 6.0.1(2) FTD
  9.6 (ASA)	9.6.2

  5 9.6 (1) is not part of the fixed versions, this means that is assigned for the SNMP Remote Code execution vulnerability.

  Cisco Adaptive Security Appliance CLI Remote Code vulnerability to run you can also take a look at cisco's Advisory here:

  https://Tools.Cisco.com/Security/Center/content/CiscoSecurityAdvisory/CI...

  Fixed versions

  The following table shows the first software versions that include fixes for this vulnerability (9.6 is not affected)

  Cisco ASA Major Release	First version fixed
  7.2	Affected, migrate to 8.4 (3) or later
  8.0	Affected, migrate to 8.4 (3) or later
  8.1	Affected, migrate to 8.4 (3) or later
  8.2	Affected, migrate to 8.4 (3) or later
  8.3	Affected, migrate to 8.4 (3) or later
  8.4	8.4 (3)
  8.5	Affected, migrate to 9.0 (1) or later version
  8.6	Affected, migrate to 9.0 (1) or later version
  8.7	Affected, migrate to 9.0 (1) or later version
  9.0	9.0 (1)
  9.1	Not affected
  9.2	Not affected
  9.3	Not affected
  9.4	Not affected
  9.5	Not affected
  9.6	Not affected

  Hope this info helps!

  Note If you help!

  -JP-

• How to console Access of Cisco SG 300 - 28 P

  Hi Experts,

  We have just a cisco SG 300 - 28 P switch. We tried the initial installation according to the manual, but we are not able access the switch to configure. Suite of methods we tried:

  1. connected a lan cable from a computer to an ethernet port on the switch, statically assigned 192.168.1.100 IP address to the computer and attempted to access switch with default IP address: http://192.168.1.254

  2 connected the serial cable that was awarded with the switch on a machine a I tried to access through terminal tera. I have seen cables serial that has RS 32 port to be connected to the machine and RJ45 adapter to the switch console port. But for this switch, it is opposite, IE the RS 32 port switch and RJ 45/machine.

  It would be great if we can access the switch through the console port. Please help me on this.

  Kind regards

  Martin

  Hello

  The correct console cable type is null-modem cable DB9 R232 has "Female DB9" connectors at both ends of the cable.

  Kay Lee Yiu

  Concentrix at Cisco

  .:|:.:|:. CISCO | Kay Lee Yiu | Pre-sales SMB | [email protected] / * / | Phone + 1 (855) 354-7776

  

• Switch Cisco Nexus 6004 removes more than 300 bytes IP packets

  Hi all

  We have a circuit of wave level 3 10 G running between two switches Cisco Nexus 6004. The circuit came online between our two data centers (in the same city) without problem.

  When attempting to ping to the remote-end 10G interface, it works very well with packets of 64 bytes. CDP is enabled and that we see the CDP information remote switch. However, if we increase the size of the ping to more than 300 bytes packets, we lose 1 in every 20.

  We settings MTU verifed, type of cable of 10G and duplex settings.

  Level 3A tested clean and we will move forward with more testing.

  Any ideas on the problem? We feel the carrier out and end to test with their testers. But so far, the circuit's own test. I was not sure if it is something related to Cisco. I am at a loss at the moment.

  Thank you.

  Mike

  Hi Mike,.

  There is nothing wrong with your switches or circuit.  NEXUS devices have a default COPP on the control plan that limit the size and the amount of traffic that must be the CPU process.

  http://www.Cisco.com/en/us/docs/switches/Datacenter/SW/6_x/NX-OS/security/configuration/guide/b_Cisco_Nexus_7000_NX-OS_Security_Configuration_Guide__Release_6.x_chapter_011001.html

  HTH

• Plug-and-Play for Cisco Small Business 300 Series managed switch

  Nice day

  What are the automatic installation options available for the Managed Switch series of Cisco Small Business 300?

  It seems there are not, the operating system is not the standard IOS I used to.

  I would use with ability to bridge the Infrastructure first Cisco PnP.

  Concerning

  Stone

  First Infrastructure use and assume an agent CNS (Cisco Network Services) on the other side, when you enable the 'plug & play '. Series 300/500 do not run IOS and does not include the CNS agent, but there is a way to activate the automatic configuration. Switches supported by the automatic DHCP configuration (using DHCP options 66, 67, etc.) in which case they automatically download their config to a TFTP server at boot time. This allows an administrator to put the configs for all switches on a TFTP server and simply start a default switch factory in order to obtain config.

  Seal a document shows how this is done.

  Hope that the information would be useful.