CSM 4.2(1) e CIsco7609 s72033-pk9sv-mz.122-18.SXD5.bin

WE have idle=1 under vserver for traffic UDP, but the real change after 4seconds and not after 1 second. It is possible?Thanks
Ira

The minimum idle timeout is 4.
0 means infinite and all values below 4 are swaped with a value of 4.
You can see the current value with the following command:
gdufour-cat6k-2(config-module-csm)#vser test
gdufour-cat6k-2(config-slb-vserver)#idle ?
<0-13500000> idle timer value in seconds (0 is infinite(!!) default is 3600)
gdufour-cat6k-2(config-slb-vserver)#idle 1
gdufour-cat6k-2#sho mod csm 3 vser name test det
TEST, type = SLB, state = OUTOFSERVICE, v_index = 15
virtual = 1.1.1.1/32:0 unidir, UDP, service = NONE, advertise = FALSE
idle = 4, replicate csrp = none, vlan = ALL,
^^^^^^^^^
However, I have to admit this is strange to allow the configuration of a value of 1 and then silently change the value to 4.
I'll check what we can do.
Regards,
Gilles.

Similar Messages

Can I upgrade FWSM 4.0.3 to 4.0.17 with Chassis IOS s72033-adventerprisek9_wan-mz.122-33.SXH4.bin ?

Hi,
Can I upgrade FWSM 4.0.3 to 4.0.17 with Chassis IOS s72033-adventerprisek9_wan-mz.122-33.SXH4.bin ?
In chassis's slot we have ACE and FWSM slot also. if I will upgrade chassis it will reboot ACE too.
I do not want to reload Chassis.
Thanks,
Shain Bharati

Hi Shain
I upgraded my client's Cisco FWSM from 4.0.3 to 4.1.7 few months ago, and everything was good. I didn't have to do incremental upgrade as proposed by Cisco (best practise). This saves time because in the real world, we don't normally have the luxury of long maintenance window (in a non-HA environment).
However, if you choose to upgarde to 4.0.17, that's fine too. The upgrade has no bearing to the IOS version currently running in your C6509 chassis. This is because the FWSM runs on its' own operating system.
For further details on this, you could refer to http://www.cisco.com/en/US/docs/security/fwsm/fwsm41/release/notes/fwsmrn41.html
If you ask me personally, go for 4.1.9 as your FWSM will then be covered with the latest bug fixes.
P/S: If you think this comment is helpful, please do rate them accordingly.

IPV6 Migration on s72033-adventerprisek9_wan-mz.122-18.SXE6b.bin ios image

Hi,
Can Cisco 7600-7609 model router support ipv6 and NAT64. and in my router ios is s72033-adventerprisek9_wan-mz.122-18.SXE6b.bin".whether i have to upgrade the ios version?

Hi there,
You platform does support IPv6, but the NAt64 feature is currently only available on IOS-XE (ISR, CSR and ASR).
http://tools.cisco.com/ITDIT/CFN/jsp/by-feature-technology.jsp
cheers,
Seb.

Dot1q tunnel VPLS support

Hello Guys,
I am configuring a dot1q tunnel VPLS since it suited our need for the client's requirements. To my surprise the 48 port tx we are using on our 7600 doesn't support this
7609-PPE1(config-if)#switchport mode dot1q-tunnel
Command rejected: Gi2/4 doesn't support 802.1q tunneling.
IOS is s72033-pk9sv-mz.122-18.SXD5.bin
Hardware is 48 SFM-capable 48 port 10/100/1000mb RJ45 WS-X6548-GE-TX
For me to establish a good VPLS in dot1q (dot1q in dot1q) multipoint connection, what hardware with port density is available for this one?
I didn't have any problem with OSM modules, but we have to be practical with the port density.
Your insights will be greatly appreciated.
Thanks.

For vpls to work the core facing should be a osm module.Configure IP routing in the core so that the PE routers can reach each other via IP. Configure MPLS in the core so that a label switched path (LSP) exists between the PE routers.For more info refer
http://www.cisco.com/en/US/products/hw/routers/ps368/products_configuration_guide_chapter09186a00801e5c06.html#wp1338115.

6500 ip flow top-talkers

Hi All,
i would like to enable "ip flow-top-talkers" in 6500 in native mode.
this command is not supported in current version.
is there any alernative command or it won't support.
running ios is s72033-pk9sv-mz.122-18.SXD5.bin
Thanx in advance for the response.
Regards,
Rajesh

This command was introduced only from 12.2(25)S and this feature was integrated into 12.3(11)T. So,if you are using any lower version other than this,this command will not work at all.If possible,better download any of the above 2 versions from cisco website and upgrade your IOS.

Setting Up Supervisor Redundancy in a 6500

All,
I am configuring a Cat 6500 with 2 WS-SUP720-3B engines. How do I configure these two engines for redundany? Is there a configuration for this or do you just install them and the software automatically sets the priority. I am asking because I have never set up 2 engines before. Any help would be great.

Use "show redundancy" to verify. Output will be similar to this:
sh redundancy
Redundant System Information :
Available system uptime = 7 weeks, 4 days, 17 hours, 27 minutes
Switchovers system experienced = 2
Standby failures = 0
Last switchover reason = active unit removed
Hardware Mode = Duplex
Configured Redundancy Mode = sso
Operating Redundancy Mode = sso
Maintenance Mode = Disabled
Communications = Up
Current Processor Information :
Active Location = slot 5
Current Software state = ACTIVE
Uptime in current state = 7 weeks, 3 days, 14 hours, 37 minutes
Image Version = Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-PK9SV-M), Version 12.2(18)SXD7, RELEASE S
OFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Tue 13-Dec-05 23:17 by kellythw
BOOT = sup-bootflash:s72033-pk9sv-mz.122-18.SXD7.bin,1
;disk0:s72033-pk9sv-mz.122-18.SXD7.bin,1
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102
Peer Processor Information :
Standby Location = slot 6
Current Software state = STANDBY HOT
Uptime in current state = 7 weeks, 3 days, 14 hours, 36 minutes
Image Version = Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-PK9SV-M), Version 12.2(18)SXD7, RELEASE S
OFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Tue 13-Dec-05 23:17 by kellythw
BOOT = sup-bootflash:s72033-pk9sv-mz.122-18.SXD7.bin,1
;disk0:s72033-pk9sv-mz.122-18.SXD7.bin,1
CONFIG_FILE =
BOOTLDR =
Configuration register = 0x2102

Rate limit: Police bandwidth

Hi friends
I have some questions:
equipment: 7609
IOS: s72033-pk9sv-mz.122-18.SXD7.bin
i need create one police with 4200000000, but the police only support 4000000000.
Router(config-pmap-c)# police ?
<32000-4000000000> Bits per second
aggregate Choose aggregate policer for current class
flow police each flow
how can i limit 4.2 Giga, any idea?
do you know a good reference aboute it?
thanx

Hi there,
It seems a bit trickier than I thought!
I've not got a router near me, but have a go with a 2 rate policer. Here you have CIR and PIR. You can send at the PIR rate - which is higher than the CIR rate. Have a look at this link for some config tips:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t4/ft2rtplc.htm
Next, I would have a go at marking the access-list 125 traffic on ingress with a qos value currently not in use (e.g af11) using shaping for the first 4gig. Then in the 1st map class - match the af11 traffic. Then on the second, match the rest of the traffic that was no marked using the access-list.
Let me know !
LH

Error message on Catalyst 6513 Urgent!!!

Hi the Catalyst 6513 is giving me this message:
Nov 1 21:34:09: %PFREDUN-SP-4-BOOTSTRING_INVALID: The bootfile slaveflash:s720
33-pk9sv-mz.122-17d.SXB1.bin is not present in standby
but it seems to me that everything is Ok bootflash is copy on both supervisors
#sh boot
BOOT variable = flash:s72033-pk9sv-mz.122-17d.SXB1.bin,12
CONFIG_FILE variable does not exist
BOOTLDR variable = bootflash:s72033-pk9sv-mz.122-17d.SXB1.bin
Configuration register is 0x2102
Standby is up
Standby has 458752K/65536K bytes of memory.
Standby BOOT variable = flash:s72033-pk9sv-mz.122-17d.SXB1.bin,12
Standby CONFIG_FILE variable does not exist
Standby BOOTLDR variable = bootflash:s72033-pk9sv-mz.122-17d.SXB1.bin
Standby Configuration register is 0x2102
Can somebody explain to me why it is happening?
Regards
Thanks
Lp

Hello,
here is what the error message decoder says:
1. %PFREDUN-4-BOOTSTRING_INVALID: The bootfile [chars] is not present in standby
This message indicates that the bootfile that is configured is not present on the redundant supervisor engine. If the redundant supervisor engine resets, it will not come up because it will not find the image specified in the bootstring.
Looks like you need to configure the bootfile on the redundant supervisor...
HTH,
GP

6500 IOS Upgrade

I need to upgrade the IOS on a 6500 with dual sup720/msfc3/pfc3. However I do not have enough space on sup-bootflash or slavesup-bootflash to fit the new image. If I delete the existing images on sup-bootflash and slavesup-bootflash that were used when the router booted and issue the squeeze command before I upload the new image on the sup-bootflash and slavesup-bootflash, will that cause my router to crash? Below is the procedure I plan to use. Please let me know if this is correct. Thanks.
1)Delete old image on sup-bootflash to make room for new IOS
-delete sup-bootflash: s72033-pk9sv-mz.122-17d.SXB2.bin
-squeeze bootflash:
-delete slavesup-bootflash: s72033-pk9sv-mz.122-17d.SXB2.bin
squeeze slavesup-bootflash:
2)Upload new image to sup-bootflash and slavesup-bootflash
-copy tftp sup-bootflash:
-copy tftp slavesup-bootflash:
3)Update boot statements to point to new image on sup-bootflash and slave-bootflash
-no boot system flash supbootflash:s72033-pk9sv-mz.122-17d.SXB2.bin
-boot system flash sup-bootflash: s72033-pk9sv-mz.12.2-17d.SXB11.bin
-boot system flash slavesup-bootflash: s72033-pk9sv-mz.12.2-17d.SXB11.bin
Will this procedure cause the router to fail if I delete the images that were used to boot?

Hi Friend,
No it will not result in router boot.
But you need to very cautious in uploading the new image cause if you delete the old image and you are trying to copy a new image on sup-bootflash and by any chance you router gets rebooted due to power problem or any other problem you will move to rommon.
SO just be cautious when you are upgrading new image and make sure you have UPS so that incase power goes down your switch is still up.
Also if you have compact flash it will be better to load the new image on it and keep it as backup.
HTH, if yes please rate the post.
Ankur

IOS -- Why recommended Flash is Much more than Image Size

Its Generally Observed that when we download an image the Image size is Much less than the Recommended Flash Card Size.
eg
First Image Information CURRENT
Image Name s72033-pk9sv-mz.122-18.SXD4.bin
DRAM / Min Flash 512 / 64
Size ~~ 48 Mb
Second Image Information
Image Name s72033-adventerprisek9_wan-mz.122-33.SXH3a.bin
DRAM / Min Flash 512 / 512
Size~~ 78Mb
Why So ? Bcuz other files like config / vlan.dat dont demand Much space & For a Backup Image256 Mb would be Enough. Please Elaborate Your Answer

Adesh,
Generally memory sizes are incremental ie 16,32,64,128 etc... So of course you have to have the available amount of memory to be able to store the IOS on it. Many routers now come with the SDM GUI that takes up 6-8Mb on flash memory, and I think Cisco does take things like that into consideration.
On your second image with the 512Mb recommended amount of flash I think is a typo. I see no reason why 512Mb is required for a 78Mb file. You could hold several IOS files with that amount of flash (which is nice) but not required.
I believe that the vlan.dat and the startup-config are still housed in NVRAM. Which is a completely different file system than flash.
HTH,
Mark

Idsm2 reload

Hi,
We have one Catalyst 6509 with IDSM2, and the IDSM2 reboot unexpectedly. The error message is :
Nov 17 22:32:47: %OIR-SP-3-PWRCYCLE: Card in module 9, is being power-cycled off (Module not responding to Keep Alive polling)
Nov 17 22:32:48: %C6KPWR-SP-4-DISABLED: power to module in slot 9 set off (Module not responding to Keep Alive polling)
Nov 17 22:36:21: %DIAG-SP-6-RUN_MINIMUM: Module 9: Running Minimum Diagnostics...
Nov 17 22:36:22: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled.
Nov 17 22:36:22: %DIAG-SP-6-DIAG_OK: Module 9: Passed Online Diagnostics
Nov 17 22:36:23: %OIR-SP-6-INSCARD: Card inserted in slot 9, interfaces are now online
Nov 20 18:47:26: %OIR-SP-3-PWRCYCLE: Card in module 9, is being power-cycled off (Module not responding to Keep Alive polling)
Nov 20 18:47:26: %C6KPWR-SP-4-DISABLED: power to module in slot 9 set off (Module not responding to Keep Alive polling)
Nov 20 18:51:00: %DIAG-SP-6-RUN_MINIMUM: Module 9: Running Minimum Diagnostics...
Nov 20 18:51:01: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled.
Nov 20 18:51:01: %DIAG-SP-6-DIAG_OK: Module 9: Passed Online Diagnostics
Nov 20 18:51:01: %OIR-SP-6-INSCARD: Card inserted in slot 9, interfaces are now online
It occured several times before 11/17 and I have tried to reseat the module before, but the IDSM2 reboot again. The IOS version of supervisor engine is s72033-ps-mz.122-18.SXD5.bin, The IDSM2 software version is 6.0(5)E2. Please help to diagnosis this problem. Shall I upgrade IOS of supervisor engine or IDSM or need RMA?
Best Regards,
Jackson Ku

Hi,
you posted this in the Wireless Security section, please move your question to the Security section. I'm not sure you will get much replies here :-)
Nicolas

Idsm2 reboot unexpectedly

Hi,
We have one Catalyst 6509 with IDSM2, and the IDSM2 reboot unexpectedly. The error message is :
Nov 17 22:32:47: %OIR-SP-3-PWRCYCLE: Card in module 9, is being power-cycled off (Module not responding to Keep Alive polling)
Nov 17 22:32:48: %C6KPWR-SP-4-DISABLED: power to module in slot 9 set off (Module not responding to Keep Alive polling)
Nov 17 22:36:21: %DIAG-SP-6-RUN_MINIMUM: Module 9: Running Minimum Diagnostics...
Nov 17 22:36:22: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled.
Nov 17 22:36:22: %DIAG-SP-6-DIAG_OK: Module 9: Passed Online Diagnostics
Nov 17 22:36:23: %OIR-SP-6-INSCARD: Card inserted in slot 9, interfaces are now online
Nov 20 18:47:26: %OIR-SP-3-PWRCYCLE: Card in module 9, is being power-cycled off (Module not responding to Keep Alive polling)
Nov 20 18:47:26: %C6KPWR-SP-4-DISABLED: power to module in slot 9 set off (Module not responding to Keep Alive polling)
Nov 20 18:51:00: %DIAG-SP-6-RUN_MINIMUM: Module 9: Running Minimum Diagnostics...
Nov 20 18:51:01: %MLS_RATE-4-DISABLING: The Layer2 Rate Limiters have been disabled.
Nov 20 18:51:01: %DIAG-SP-6-DIAG_OK: Module 9: Passed Online Diagnostics
Nov 20 18:51:01: %OIR-SP-6-INSCARD: Card inserted in slot 9, interfaces are now online
It occured several times before 11/17 and I have tried to reseat the module before, but the IDSM2 reboot again. The IOS version of supervisor engine is s72033-ps-mz.122-18.SXD5.bin, The IDSM2 software version is 6.0(5)E2. Please help to diagnosis this problem. Shall I upgrade IOS of supervisor engine or IDSM or need RMA?
Best Regards,
Jackson Ku

Agreed, this likely needs to have a TAC case opened for an RMA -- especially if a re-seat of the module has already been attempted. Any time you're seeing the switch cut off power to the module over multiple insertions, that's not a good thing.
I just had this happen to a FWSM last week, and re-seating the module didn't work for me, either.
You can read more about the error message here:
http://www.cisco.com/en/US/partner/products/hw/switches/ps700/products_tech_note09186a00801b42bf.shtml
WorkaroundA simple reseat of the module corrects this issue 90 percent of the time. If you reseat the module, it realigns the switch fabric and ensures a firm connection to the backplane.

CSM 3.3.1 and 6500

Hello,
We are facing a problem with CSM 3.3.1 and 6500 switch with FWSM. We have 2x 6500 switches with 2 supervisors in each + 2 FWSM cards one in each chassis. The problem is that we have CSM 3.3.1 that manages the switch and FWSM. The problem is that when we try to delete a VLAN in 6500 we get a deployment failure because the switch outputs this message:
% Applying VLAN changes may take few minutes. Please wait..
We are using the following IOS version.
CSR-CORE#sh ver
Cisco IOS Software, s72033_rp Software (s72033_rp-IPSERVICESK9_WAN-M), Version 12.2(33)SXI2a, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2009 by Cisco Systems, Inc.
Compiled Wed 02-Sep-09 01:00 by prod_rel_team
ROM: System Bootstrap, Version 12.2(17r)SX6, RELEASE SOFTWARE (fc1)
CSR-CORE uptime is 22 weeks, 6 days, 23 hours, 59 minutes
Uptime for this control processor is 22 weeks, 6 days, 23 hours, 55 minutes
Time since CSR-CORE switched to active is 22 weeks, 6 days, 23 hours, 55 minutes
System returned to ROM by power cycle at 06:42:16 UTC Fri Feb 12 2010 (SP by power on)
System restarted at 11:10:39 EEST Mon Jun 14 2010
System image file is "sup-bootdisk:s72033-ipservicesk9_wan-mz.122-33.SXI2a.bin"
Last reload reason: Reload Command
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco WS-C6509-E (R7000) processor (revision 1.5) with 983008K/65536K bytes of memory.
Processor board ID SMC1401000U
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from s/w reset
30 Virtual Ethernet interfaces
116 Gigabit Ethernet interfaces
12 Ten Gigabit Ethernet interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
CSR-CORE#
Note that we are NOT using VSS.
TIA,
Nicos

Hi all,
Sorry for not replying earlier. We found a workaround, as quoted below:
Changing How Security Manager Responds to Device Messages
Security Manager has built-in responses to many of the response messages that can be encountered when configuring a device. You might find that messages Security Manager treats as errors are messages that you want to ignore or treat as informational. Although you can configure your deployment jobs to ignore errors, you might instead want to update Security Manager to treat specific messages differently. To change how Security Manager treats a message, you need to update the DCS.properties file in \CSCOpx\MDC\athena\config folder in the installation directory (usually c:\Program Files).
Use a text editor such as NotePad to update the file. It is easiest to determine the message you want to ignore by looking at the transcript of a deployment job that encountered the error using these steps:
Step 1 Select the job with the error message from the Deployment Manager window.
Step 2 Click the Transcript button in the Deployment Details tab to open the transcript.
Step 3 Identify the error text that you want to ignore.
Step 4 Locate the appropriate warning expressions property in the DCS.properties file. For example, for PIX devices the property is called dev.pix.warningExpressions, whereas for IOS devices the property is called dev.ios.warningExpressions.Conversely, you can make device responses that are not tagged with the Error prefix to appear as error messages. To do this, add the message to the Error Expressions list (for example, dev.pix.ErrorExpressions).
Step 5 Add the error text to the warning expressions list. The warning message should be a generic regular expression string. Except for the last expression, you must delimit all expressions with “$\”. For example, if the message you want to ignore is “Enter a public key as a hexadecimal number,” enter the following string: .*Enter a public key as a hexidecimal number .*$
Step 6 Restart the CiscoWorks Daemon Manager
This has resolved the issue successfully

CSM Displaying incorrect information

On our current infastructure we have a number of Vservers built , utilising vserver SSO-GP-443
serverfarm SSO-GP-SY-443 backup SSO-GP-NW-443
Both server farms show up and available until we fail the primary server farm, when this happens the Vserver shows as below
SSO-GP-443 SLB TCP 172.27.117.25/32:443 ALL OUTOFSERVICE 1
Although on testing, traffic is passed to the servers and the display may be purely cosmetic, but we would like this confirmed and also if its a known bug , if this is the case when this bug will be fixed
c6slb-apc.4-2-4.bin CSM Code
s72033-advipservicesk9_wan-mz.122-18.SXF5.bin Switch Code

If the data is incorrect, the system generates error messages and displays the page on which the error occurs.
http://www.cisco.com/en/US/products/ps6498/products_user_guide_chapter09186a00806b79f3.html#wp1055751

7600 as Backbone router for MPLS core

I have 7600's and 7500's in my backbone and 7200's on the edge. My question is that when I look at the feature navigator the 7600 with Sup 720 is missing a lot of basic features required to be a core router of an MPLS Backbone. Features like Traffic engineering fast reroute, MPLS enabled Netflow are missing on this platform, is this platform not a good candidate to be a Backbone router for a service provider offering MPLS services??? 7500 on the other hand it seems 7500 seems to have support for the MPLS related features.

Not sure what version you where looking at but...
Cisco Internetwork Operating System Software
IOS (tm) s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2005 by cisco Systems, Inc.
Compiled Sat 10-Sep-05 01:18 by ccai
Image text-base: 0x40101040, data-base: 0x42D60000
ROM: System Bootstrap, Version 12.2(17r)S2, RELEASE SOFTWARE (fc1)
BOOTLDR: s72033_rp Software (s72033_rp-ADVIPSERVICESK9_WAN-M), Version 12.2(18)SXF, RELEASE SOFTWARE (fc1)
CASAN_Core1 uptime is 1 week, 4 hours, 9 minutes
Time since CASAN_Core1 switched to active is 1 week, 4 hours, 8 minutes
System returned to ROM by power cycle (SP by power on)
System image file is "disk0:s72033-advipservicesk9_wan-mz.122-18.SXF.bin"
This product contains cryptographic features and is subject to United
States and local country laws governing import, export, transfer and
use. Delivery of Cisco cryptographic products does not imply
third-party authority to import, export, distribute or use encryption.
Importers, exporters, distributors and users are responsible for
compliance with U.S. and local country laws. By using this product you
agree to comply with applicable laws and regulations. If you are unable
to comply with U.S. and local laws, return this product immediately.
A summary of U.S. laws governing Cisco cryptographic products may be found at:
http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
If you require further assistance please contact us by sending email to
[email protected].
cisco CISCO7609 (R7000) processor (revision 1.1) with 983008K/65536K bytes of memory.
Processor board ID FOX092307Q5
SR71000 CPU at 600Mhz, Implementation 0x504, Rev 1.2, 512KB L2 Cache
Last reset from power-on
SuperLAT software (copyright 1990 by Meridian Technology Corp).
X.25 software, Version 3.0.0.
Bridging software.
TN3270 Emulation software.
1 SIP-200 controller .
1 Virtual Ethernet/IEEE 802.3 interface
74 Gigabit Ethernet/IEEE 802.3 interfaces
1917K bytes of non-volatile configuration memory.
8192K bytes of packet buffer memory.
65536K bytes of Flash internal SIMM (Sector size 512K).
Configuration register is 0x2102
CASAN_Core1#
CASAN_Core1(config)#mpls traffic-eng ?
auto-bw auto-bw parameters
fast-reroute fast-reroute parameters
link-management Link Management configuration
logging Trap logging configuration
path-selection Path Selection Configuration
reoptimize Reoptimization parameters
signalling Traffic Engineering Signalling Parameters
topology Topology Database Configuration
tunnels Traffic Engineering tunnels

CSM 4.2(1) e CIsco7609 s72033-pk9sv-mz.122-18.SXD5.bin

Similar Messages

Maybe you are looking for