Can I ask for a clarification? All I need is one notification every time "receive_rate_bps" exceeds 4500000 (4,5Mbps) continuously for 180 seconds. What would be the correct command?
I've been trying out different parameters but can't seem to get it right:
event interface name Gig 0/1 parameter receive_rate_bps entry-op ge entry-val 4500000 entry-type increment poll-interval 180
Your help is much appreciated.
... View more
Just as a reference for other users, I had to change the following in the first line of the script:
Apparently the events have changed in the newer IOS version.
Also be very careful with the .TCL files - I had two identical .tcl files one would come up with the error : EEM Register event failed: Error empty reg spec, policy does not start with EEM registration commands: while the other didn't.
The problem seems to be with my editor (Notepad ++ and Windows notepad), but I'm not sure why this is happening.
The file seems to need to be clear txt without any UTF or other encoding.
... View more
Thanks for providing the script.
I've been trying to use it without any success on a 2951 router.
The problem I'm having is that I am unable to execute or register the script. I've saved the script as email.tcl and uploaded it to the router's flash.
When trying to register it using "event manager policy email.tcl type user" I receive the following error:
" EEM Register event failed: Error empty reg spec, policy does not start with EEM registration commands.
EEM Configuration: failed to retrieve intermediate registration result for policy email.tcl"
My question is how can I use the script correctly ?
When I replaced the first line of the script with the following"
"::cisco::eem::event_register_syslog pattern $_syslog_pattern", the script would register, but I couldn't trigger it even despite configuring the event manager environment _syslog_pattern
What I'm trying to do is use this script with an applet that is triggered when CPU usage is high - it creates a TXT file on the router's flash and I want it to be email to me.
Any help would be much appreciated!
... View more
Hello to all fellow engineers, I'd like to share with everyone our article that covers the installation of Cisco's popular IPSec VPN Client for the Windows 10 operating system (both 32 and 64 bit versions). Firewall.cx - Install & Fix Cisco VPN Client on Windows 10 (32 & 64 Bit). Fix Reason 442: Failed to enable Virtual Adapter Topics covered include: - How to Install Cisco IPSec VPN Client on Windows 10 - How to fix 'Reason 442: Failed to enable Virtual Adapter' error on Windows 10
Always, full instructions are provided to ensure the successful installation and operation of the VPN Client.
Feedback is always welcome. Many thanks, Chris.
... View more
G'day to everyone. I'm dealing with an issue, which I'd like to share in case anyone knows how to resolve this. I've conifgued a SIP trunk with a VoiP provider and incoming/outgoing calls are working fine. For the incoming calls, I've created a voip dial-peer and applied an incoming translation pattern, to ensure the incoming calls hit extension 16 as shown below: dial-peer voice 999 voip translation-profile incoming incoming-viva incoming called-number 001112223330 translation-profile incoming incoming-viva incoming called-number 001112223330 voice translation-profile incoming-viva translate called 8 voice translation-rule 8 rule 1 /001112223330/ /16/ rule 2 /^.*/ /16/ This works fine. The problem is what when I change the destination extension from 16 to Unity Express (ext. 70) so that it will go to the Autoattendant, I get a busy signal. So I'm here trying to figure out what I might be doing wrong or what I'm missing. Following is dial-peer 105 which is being hit and partial debug from the test: dial-peer voice 105 voip description AUTO-Attendant destination-pattern 70 session protocol sipv2 session target ipv4:192.168.100.10 dtmf-relay rtp-nte codec g711ulaw no vad Debug: Destination Pattern=70, Called Number=70, Digit Strip=FALSE 001128: Dec 15 10:34:35.103: //1811/CC12A5CE81E4/CCAPI/ccCallSetupRequest: Calling Number=001112223330(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed), Called Number=70(TON=Unknown, NPI=Unknown), Redirect Number=, Display Info=98889994 Account Number=98889994, Final Destination Flag=TRUE, Guid=CC12A5CE-837C-11E4-81E4-FC73FD6F77C7, Outgoing Dial-peer=105 001129: Dec 15 10:34:35.103: //1811/CC12A5CE81E4/CCAPI/cc_api_display_ie_subfields: ccCallSetupRequest: cisco-username=98889994 ----- ccCallInfo IE subfields ----- cisco-ani=001112223330 cisco-anitype=0 cisco-aniplan=0 cisco-anipi=0 cisco-anisi=1 dest=70 cisco-desttype=0 cisco-destplan=0 cisco-rdie=FFFFFFFF cisco-rdn= cisco-lastrdn= cisco-rdntype=0 cisco-rdnplan=0 cisco-rdnpi=-1 cisco-rdnsi=-1 cisco-redirectreason=-1 fwd_final_type =0 final_redirectNumber = hunt_group_timeout =0 001130: Dec 15 10:34:35.103: //1811/CC12A5CE81E4/CCAPI/ccIFCallSetupRequestPrivate: Interface=0x86C75FF4, Interface Type=3, Destination=, Mode=0x0, Call Params(Calling Number=001112223330,(Calling Name=98889994)(TON=Unknown, NPI=Unknown, Screening=User, Passed, Presentation=Allowed), Called Number=70(TON=Unknown, NPI=Unknown), Calling Translated=FALSE, Subscriber Type Str=Unknown, FinalDestinationFlag=TRUE, Outgoing Dial-peer=105, Call Count On=FALSE, Source Trkgrp Route Label=, Target Trkgrp Route Label=, tg_label_flag=0, Application Call Id=) 001131: Dec 15 10:34:35.103: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa: 001132: Dec 15 10:34:35.103: :cc_get_feature_vsa malloc success 001133: Dec 15 10:34:35.103: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa: 001134: Dec 15 10:34:35.103: cc_get_feature_vsa count is 4 001135: Dec 15 10:34:35.103: //-1/xxxxxxxxxxxx/CCAPI/cc_get_feature_vsa: 001136: Dec 15 10:34:35.103: :FEATURE_VSA attributes are: feature_name:0,feature_time:2313678960,feature_id:257 001137: Dec 15 10:34:35.103: //1812/CC12A5CE81E4/CCAPI/ccIFCallSetupRequestPrivate: SPI Call Setup Request Is Success; Interface Type=3, FlowMode=1 001138: Dec 15 10:34:35.103: //1812/CC12A5CE81E4/CCAPI/ccCallSetContext: Context=0x89EBF988 001139: Dec 15 10:34:35.103: //1811/CC12A5CE81E4/CCAPI/ccSaveDialpeerTag: Outgoing Dial-peer=105 001140: Dec 15 10:34:35.103: //1812/CC12A5CE81E4/CCAPI/cc_api_call_disconnected: Cause Value=65, Interface=0x86C75FF4, Call Id=1812 001141: Dec 15 10:34:35.103: //1812/CC12A5CE81E4/CCAPI/cc_api_call_disconnected: Call Entry(Responsed=TRUE, Cause Value=65, Retry Count=0) 001142: Dec 15 10:34:35.107: //1812/CC12A5CE81E4/CCAPI/cc_api_call_disconnected: Cause Value=47, Interface=0x86C75FF4, Call Id=1812 001143: Dec 15 10:34:35.107: //1812/CC12A5CE81E4/CCAPI/cc_api_call_disconnected: Call Entry(Responsed=TRUE, Cause Value=65, Retry Count=0) Any help or guidance is much appreciated. Chris.
... View more
Aman, Cisco TAC hasn't flag this is a 'bug', or at least not yet. I did ask the engineer why remove such a feature which was apparently helping customers avoid these issues, but the enginner didn;'t have an answer for me. By the looks of things, moving to H323 (if the telco provider can't do anything) is possibly the only option, unless someone else has a solution! Thanks,
... View more
Hello Carlo, Here is the output from the VG when dialing inwards through a phone with CallerID disabled. I also just spoke with Cisco TAC and they have told me there is no current work-around and that we need to change the VG to H323. Please let me know if you have any suggestions. Thanks, Chris. Nov 4 11:47:21.977: ISDN Se0/1/0:15 Q931: RX <- CONNECT pd = 8 callref = 0x9300 Date/Time i = 0x0E0B040D2F15 Date (dd-mm-yr) = 14-11-04 Time (hr:mnt:sec) = 13:47:21 Nov 4 11:47:21.985: ISDN Se0/1/0:15 Q931: TX -> CONNECT_ACK pd = 8 callref = 0x1300 VG2921# Nov 4 11:47:24.413: ISDN Se0/1/0:15 Q931: RX <- SETUP pd = 8 callref = 0x15DC Sending Complete Bearer Capability i = 0x8090A3 Standard = CCITT Transfer Capability = Speech Transfer Mode = Circuit Transfer Rate = 64 kbit/s Channel ID i = 0xA98381 Exclusive, Channel 1 Calling Party Number i = 0x0180, 'anonymous' Plan:ISDN, Type:Unknown Called Party Number i = 0x81, '4321586251' Plan:ISDN, Type:Unknown Nov 4 11:47:24.417: MGCP Packet received from 192.168.3.10:2427---> CRCX 52335 S0/SU1/DS1-0/1@VG2921.cucm.local MGCP 0.1 C: D000000001ab4c5e000000F5800015dc X: 1 L: p:20, a:PCMU, s:off, t:b8 M: recvonly R: D/[0-9ABCD*#] Q: process,loop <--- VG2921# Nov 4 11:47:24.421: MGCP Packet sent to 192.168.3.10:2427---> 200 52335 OK I: 28B9 v=0 c=IN IP4 192.168.3.9 m=audio 21444 RTP/AVP 0 100 a=rtpmap:100 X-NSE/8000 a=fmtp:100 192-194 <--- Nov 4 11:47:24.425: ISDN Se0/1/0:15 Q931: TX -> CALL_PROC pd = 8 callref = 0x95DC Channel ID i = 0xA98381 Exclusive, Channel 1 Nov 4 11:47:24.425: ISDN Se0/1/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x95DC Cause i = 0x8095 - Call rejected Nov 4 11:47:24.449: ISDN Se0/1/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x15DC Nov 4 11:47:24.449: MGCP Packet received from 192.168.3.10:2427---> VG2921#DLCX 52336 S0/SU1/DS1-0/1@VG2921.cucm.local MGCP 0.1 C: D000000001ab4c5e000000F5800015dc I: 28B9 X: 1 S: <--- Nov 4 11:47:24.469: MGCP Packet sent to 192.168.3.10:2427---> 250 52336 OK P: PS=0, OS=0, PR=0, OR=0, PL=0, JI=0, LA=0 <--- Nov 4 11:47:24.469: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x95DC VG2921# Nov 4 11:47:40.401: MGCP Packet sent to 192.168.3.10:2427---> NTFY 902475903 *@VG2921.cucm.local MGCP 0.1 X: 0 O: <--- Nov 4 11:47:40.401: MGCP Packet received from 192.168.3.10:2427---> 200 902475903 <--- VG2921# Nov 4 11:47:48.249: MGCP Packet received from 192.168.3.10:2427---> MDCX 52337 S0/SU1/DS1-0/30@VG2921.cucm.local MGCP 0.1 C: D000000001ab4c4a000000F5000012fb I: 28B3 X: 1e M: recvonly R: D/[0-9ABCD*#] Q: process,loop <--- Nov 4 11:47:48.249: MGCP Packet sent to 192.168.3.10:2427---> 200 52337 OK <--- Nov 4 11:47:48.253: ISDN Se0/1/0:15 Q931: TX -> DISCONNECT pd = 8 callref = 0x12FB Cause i = 0x8090 - Normal call clearing Nov 4 11:47:48.289: ISDN Se0/1/0:15 Q931: RX <- RELEASE pd = 8 callref = 0x92FB Cause i = 0x8190 - Normal call clearing Nov 4 11:47:48.289: MGCP Packet received from 192.168.3.10:2427---> VG2921#DLCX 52338 S0/SU1/DS1-0/30@VG2921.cucm.local MGCP 0.1 C: D000000001ab4c4a000000F5000012fb I: 28B3 X: 1e S: <--- Nov 4 11:47:48.305: MGCP Packet sent to 192.168.3.10:2427---> 250 52338 OK P: PS=5510, OS=881600, PR=5497, OR=879520, PL=0, JI=0, LA=0 <--- Nov 4 11:47:48.309: ISDN Se0/1/0:15 Q931: TX -> RELEASE_COMP pd = 8 callref = 0x12FB VG2921# Nov 4 11:47:54.449: MGCP Packet sent to 192.168.3.10:2427---> NTFY 902475904 *@VG2921.cucm.local MGCP 0.1 X: 0 O: <--- Nov 4 11:47:54.449: MGCP Packet received from 192.168.3.10:2427---> 200 902475904 <--- VG2921#
... View more
Hello to all. I currently have a CUCM 10.5 installation with a 2921 VG configured with MGCP. The problem experienced is that when someone calls with hidden caller id, the provider sends the Calling Party Number as 'anonymous'. This causes CUCM not to process the call and reject it. The odd thing is that I have another customer with CUCM 5.X with a similar setup (MGCP VG & anonymous as the caller ID ) where calls are processed without a problem. I've searched the forums and saw other experincing the same issue as we are, even with CUCM 7+, however no answer or solution was provided. Changing to H323 is not an option at this point. Any input would be highly appreciated. Many thanks, Chris.
... View more
Hello to everyone! I've just received a AIR-SAP702 Access point and begun configuring the device via CLI and am experiencing problems trying to configure the AP to work with WPA encryption. I've set the WPA parameters under the SSID section, however the AP fails to allow any client connect with it. I've setup many access points but this is the first time I am dealing with this model, so I am wondering if I am hitting a bug, or there's something additional required for the 702 access points, which I am not aware of. Below is my configuration: ! Last configuration change at 04:22:10 UTC Mon Mar 1 1993 by admin version 15.2 no service pad service timestamps debug datetime msec service timestamps log datetime msec service password-encryption ! hostname AP5 ! ! logging rate-limit console 9 no logging console enable secret 5 $1$EROA$uB8H/g8yjQQPZl8RYBHrH/ ! no aaa new-model no ip cef ! ! ! ! dot11 syslog ! dot11 ssid test authentication open authentication key-management wpa guest-mode infrastructure-ssid optional wpa-psk ascii 7 00554155500E5D5157 ! ! dot11 guest ! ! crypto pki trustpoint TP-self-signed-4052737212 enrollment selfsigned subject-name cn=IOS-Self-Signed-Certificate-4052737212 revocation-check none rsakeypair TP-self-signed-4052737212 ! ! crypto pki certificate chain TP-self-signed-4052737212 certificate self-signed 01 30820240 308201A9 A0030201 02020101 300D0609 2A864886 F70D0101 04050030 31312F30 2D060355 04031326 494F532D 53656C66 2D536967 6E65642D 43657274 69666963 6174652D 34303532 37333732 3132301E 170D3032 30333031 30303236 32305A17 0D323030 31303130 30303030 305A3031 312F302D 06035504 03132649 4F532D53 656C662D 5369676E 65642D43 65727469 66696361 74652D34 30353237 33373231 3230819F 300D0609 2A864886 F70D0101 01050003 818D0030 81890281 8100C5C8 3EAD9303 513C34C0 D0AB97FC 8E2E75AB BF5F3D07 0FED5D57 E625003D C2F9B9B7 ADB2D10C 6071BD32 C8B2F90B 23E7CF91 15F76A4B 736E6545 1673B13E 115DDA8F A1ADCBF3 66C3D46F 435411A8 1AEBC651 B66776AC 505A25ED CCAF62FA 5157B7ED 2D542E9A 37408292 7EA93D63 F4E47558 5E38205A 0047C88A B84CBA91 7F110203 010001A3 68306630 0F060355 1D130101 FF040530 030101FF 30130603 551D1104 0C300A82 084B6974 312D4150 31301F06 03551D23 04183016 8014BA0E FFFCA980 4A18FDE1 6A61E034 0BD7C4AF C24E301D 0603551D 0E041604 14BA0EFF FCA9804A 18FDE16A 61E0340B D7C4AFC2 4E300D06 092A8648 86F70D01 01040500 03818100 83E745AC 0B917643 6BF1D958 6A5DA8F4 1FE7385B B0863530 132BF892 40A137BA 1D84B2EA 3BBD1A8B 071C51F0 EDF1DDDF 89E44CDC C191543F 235E17E7 7E90B469 213E3292 35A06A42 29339FBD 9A9A9CA0 7D9A5859 F8A2A4B2 24C9BA66 422DB514 A53CB34C A4CCF522 D3E71B7A B71519B3 8279451E A783FBFE 18987DB7 24559631 quit ! username admin privilege 15 secret 5 $1$tW2Z$PBO.059FopASBBGXQMk55. ! ! bridge irb ! ! ! interface Dot11Radio0 no ip address no ip route-cache ! encryption mode ciphers tkip ! ssid test ! antenna gain 0 packet retries 64 drop-packet channel 2437 station-role root bridge-group 1 bridge-group 1 subscriber-loop-control bridge-group 1 spanning-disabled bridge-group 1 block-unknown-source no bridge-group 1 source-learning no bridge-group 1 unicast-flooding ! interface Dot11Radio1 no ip address shutdown antenna gain 0 peakdetect no dfs band block packet retries 64 drop-packet channel dfs station-role root bridge-group 1 bridge-group 1 subscriber-loop-control bridge-group 1 spanning-disabled bridge-group 1 block-unknown-source no bridge-group 1 source-learning no bridge-group 1 unicast-flooding ! interface GigabitEthernet0 no ip address duplex auto speed auto bridge-group 1 bridge-group 1 spanning-disabled no bridge-group 1 source-learning ! interface BVI1 ip address 10.0.0.122 255.255.255.0 ! ip default-gateway 10.0.0.4 ip forward-protocol nd ip http server no ip http secure-server ip http help-path http://www.cisco.com/warp/public/779/smbiz/prodconfig/help/eag ! ! bridge 1 route ip ! ! ! line con 0 password cisco login local line vty 0 4 login local transport input all line vty 5 15 access-class 115 in login local transport input all !
... View more
This technical document has been reproduced with the permission of www.Firewall.cx. Firewall.cx is world's only official Cisco Press reviewer partner and is officially recommended by the Cisco Network Academy. With over 900 articles covering general networking concepts, protocol analysis, network security, Cisco Switching, VPN networks, Routers, Firewalls, Voice over IP (CallManager, CallManager Express), Wireless and other complex Cisco technologies, it’s one of the most recognised, reliable and up-to-date sources of information on the Internet. Cisco Systems CCIE and CCNP engineers frequently contribute to Firewall.cx as expert guest writers. The Cisco Catalyst 4507R+E Switch It's no news that we here at Firewall.cx enjoy writing about our installations of Cisco equipment and especially devices that we don’t get to see and play with every day. Today we cover the installation of a new Cisco 4507R+E Catalyst switch populated with two 7L-E Supervisor engines, three WS-X4648-RJ45V+E 48 Gigabit PoE line cards and two 4200Watt power supplies with the ability to cover full future PoE requirements of the switch, when fully populated with PoE line cards. Many might be aware of our first 4507R article that covered the installation of a Cisco Catalyst 4507R-E switch. Since then, Cisco has replaced the 4507R-E with the newer 4507R+E chassis and introduced new Supervisor Engines. The difference between the two chassis is that the 4507R-E supports up to 24Gbps bandwidth per slot, whereas the newer 4507R+E supports up to 48Gbps per slot, bringing the chassis up to date with the new market trends and high-connectivity speed requirements of enterprise companies. To make things more interesting, we ensured we captured as many pictures as possible from our 4507R+E switch installation so that our readers can familiarise themselves with it as much as possible. After unpacking and looking at the back of the switch chassis we noticed that not much has changed except that its label now mentions 4500+E Series, indicating that it is the newer +E series. On the front side, the fan tray manages to give away that this is the newer series as it too is labelled Catalyst 4507R+E. Apart from these minor cosmetic changes the switch looks exactly the same as its predecessor. The picture below shows the back of the Cisco 4507R+E chassis. The dual power supplies are positioned at the top part of the switch and the specially designed grid allows adequate air to be pumped through the power supplies and out the back, with the help of the massive power supply fans. The fans used are extremely high quality with very little friction – when during our test run, we switched off the power supplies, the fans continued to spin for at least another 20 seconds before coming to a complete stop: Mounting a Catalyst 4500 into a rack can be a daunting experience, mainly due to its weight. When fully populated, the switch can weigh up to 55 Kgs and requires at least two people to safely pick up and place the switch into the rack, then you’d need one more person to tighten the necessary screws to keep it inside the rack! We also found it necessary for the rack to have adequate spacing above and below the area where the switch is to be placed, because it’s very difficult to keep the switch steady during installation because of its weight. In addition, it is imperative the rack’s side covers can be removed so the two handles on the switch (one on each side) are accessible. To overcome the problem of installing the heavy switch, we decided to remove both power supplies and all cards from the chassis. The empty chassis made things much easier. Revealing The Magnificent Cisco 4507R+E Backplane As we begun to slowly remove the switch’s power supplies, line cards and Supervisor Engines, we had a clear view of the spectacular 4507R backplane! The backplane is the switch’s ‘spine’, responsible of interconnecting all components together. Naturally, we had to capture this moment and here it is in all its glory: We should note that extreme caution must be given when removing and inserting the 4507 cards. The engineer performing the procedure must be properly grounded and the cards must be placed on antistatic mats or, even better, inside antistatic bags. This will help avoid electrostatic discharge that can possibly damage the line cards or supervisor engines. After removing all five cards we had a clear view of the 4507R+E’s backplane – something you don’t get to see every day. On the left side of the backplane the white and black sockets caught our attention – these are the connectors for the line cards and supervisor engines (marked in red). The Supervisor Engine sockets extend to the far right to a total of three sockets per Supervisor Engine: Looking to the left, the strategically placed fan tray is visible, ready to blow cool air into the chassis and directly on all cards. As shown in our picture the fan tray consists of two larger fans on the same level as the Supervisor Engines, and six smaller fans taking care of the cooling for the rest of the line cards: Obviously the most critical cards are the Supervisor Engines, generating most of the heat under intensive workload. Introducing The WS-X45-SUP7L-E Supervisor Engine The Supervisor Engine is the heart of every modular Cisco 4500 and 6500 series switch. The Supervisor Engine 7L-E provides a number of enhancements over its predecessor Supervisor Engine 6L-E, making it a primary choice for Enterprise-class networks seeking unprecedented performance. Following are key innovations offered by the Supervisor Engine 7L-E: 520Gbps system performance with 48Gpbs per slot to every line-card slot and 225mpps throughput Dual 10Gigabit Ethernet uplinks (via SFP+ optics) or four Gigabit Ethernet uplinks (via SFP optics) Application visibility through Flexible NetFlow (FNF) supporting Layer 2/3/4 information and synthetic traffic monitoring with IP SLA Cisco IOS XE Software which provides the ability to host third-party applications Support of 802.3az Energy Efficient Ethernet (EEE) capable line cards First and only modular switch with 8 bidirectional line-rate SPAN/RSPAN sessions Supports up to 244 ports 10/100/1000 in a 7-slot chassis External USB & SD card support for flexible storage options Maximum resiliency with redundant components, Nonstop Forwarding/Stateful Switchover (NSF/SSO), and In-Service Software Upgrade (ISSU) support Full backward compatibility with 6 G, 24 G, and 48 Gbps slot line cards with no performance degradation Product Datasheet for the Supervisor Engine 7L-E can be found in our Cisco Catalyst 4500-6500 Supervisor Engine download section Our users can refer to our popular Cisco Catalyst 4500 Series Zero-Downtime IOS Upgrade Process for Supervisor Engine 7-E, 7L-E, 6L-E and V-10GE Redundant Configurations article to learn how to upgrade their Supervisor Engine without network service interruption. Looking to the front left side of the Supervisor Engine, we can see the Status LED, Active SUP LED (on when the Sup. Engine is in active state) and Utilization LEDs. Visible behind the faceplate is the circuitry board and heatsinks attached to the dual-CPUs and other processors.: On the right we can see the Console port, Management port and 4 SFP/SFP+ slots providing two 10Gbps or four 1Gbps links! The LEDs below each SFP/SFP+ port will turn on according to the negotiated speed with the other end: Looking at the back of the Supervisor Engine 7L-E, we can see the three connectors that plug directly into the 4507R+E chassis backplane. The heat sinks fins, covering the dual core CPU and other processors, are placed in a direction where the air from the fan tray can provide maximum cooling and heat dissipation: The Supervisor Engine 7L-E board is indeed impressive. The picture above shows the Supervisor Engine almost fully inserted into the 4507R+E chassis. We took this picture to show how the Supervisor Engine’s connectors perfectly line up with the 4507R’s backplane sockets: Note how the Supervisor Engine’s processors carrying the large heatsinks are strategically placed next to the fan tray’s largest fans. The WS-X4648-RJ45V+E Line Card The WS-X4648-RJ45V+E line card provides a number of enhanced features designed to bring maximum flexibility and expandability some of which are: 48 ports 10/100/1000 module (RJ-45) Supported from Cisco IOS Software Release 12.2(40)SG or later IEEE 802.3af/at and Cisco prestandard PoE, IEEE 802.3x flow control Bandwidth is allocated across eight 6-port groups, providing 3 Gbps per port group (2:1) L2-4 Jumbo Frame support (up to 9216 bytes) Capable of up to 30 Watts of inline power per port on up to 24 ports simultaneously Enterprise and commercial: designed to power next-generation IP phones, wireless base stations, video cameras, and other PoE devices Campus and branch applications requiring enhanced performance for large file transfers and network backups In the photo below, we can see the WS-X4648 main board with its chipsets, two of which are equipped with large heatsinks. The white connector at the back provides the connection with the 4507R+E backplane through which the card and its PoE ports are powered, and data traffic is carried to the rest of the system: We should note that all 4500 & 6500 series line cards, including Supervisor Engines, have a metal carrier on the bottom of the board that covers almost all of the circuit board, making it safe to hold the line card without touching any circuits: Network Administrator Savvas Filippidis gets ready to install a line card After a careful inspection of the card it was time to place it into its slot and complete the physical installation of the 4507R+E switch. After ensuring the two module ejector levers (one on each side) were out and away from the faceplate, we gently lined it up with the two chassis slot guides of our slot and slowly pushed the line card inwards: As soon as the line card’s connector ‘touched’ the backplane we continued to push it inwards, with a little more strength this time, and the two module ejector levers automatically started to fold inwards until the line card was fully in place: Cisco 4507R+E 4200Watt Power Supplies The Cisco 4507R+E supports a number of different power supply configurations. Depending on how the switch is intended to be used, it can be populated fully with 48 Gigabit PoE ports, providing full PoE to all 5 line cards – a total of 240 ports where each line card can draw a maximum of 820 Watts. Of course, the switch needs the appropriate power supplies to be able to undertake the load and this is why it’s always a great idea to purchase large power supplies as you’ll never need to upgrade them in the future when the switch is fully populated with PoE line cards. The whopping 4200Watt power supplies were a considerable weight. To remove them, we had to loosen the captive installation screws (two for each power supply) and pull the power supply slowly outwards. Pulling out the power supply did not require much effort as it came out smoothly with the little force we used. The 4200Watt power supply is the second largest power supply available for the 4500 series and has two IEC60320-C20 connectors (per power supply) to ensure the power drawn from the UPS or power circuit is evenly split. We took both power supplies out and took a picture of them to show both front and back side. At the back of each power supply, as expected, we found one long connector, split into three groups, the middle group containing pins which are barely visible in the picture: Going back to the chassis, all we found was the power supply connector where the middle pin sockets are easily seen. In total we counted an impressive 46 connection points between the power supply and chassis: When we initially powered the Cisco 4507R+E switch, after it booted up we found both Supervisor Engine Status LEDs orange. After checking Cisco's site to find out more information, the explanation for the orange LEDs was that the Supervisor Engine was performing a 'System boot or a diagnostic test is in progress', however it was not true as the system was fully booted and working. A careful inspection showed that we had forgotten to switch on the second 4200Watt power supply and the system was running off only one power supply. At the time, the power requirements were only around 500Watts and the system was reporting the second power supply as "bad/off". As soon as we switched on the second power supply, the Supervisor Engine LEDs magically turned Green! While we found no documentation to explain this behavior, we thought it would be worth mentioning for our readers and engineers preparing to install a 4500 series switch! Article Conclusion Those who have had the luck to physically install and work on a Cisco Catalyst 4507R or any Catalyst 4500 series switch would surely agree that it is a wonderful experience and impressive piece of equipment. Examining the design and construction of the chassis, line cards and Supervisor Engines shows how much thought and work have gone into the product. Our next article covers the IOS upgrade of the Supervisor engine, health checkup, using the zero downtime IOS upgrade procedure – a necessary and extremely handy procedure that ensures the upgrade of the IOS Supervisor engines without any service interruption! Read it Now! For a complete list of our article, readers can visit www.Firewall.cx.
... View more
Hello to everyone, I'd like to share with the Cisco community one of our latest article covering the installation of a Cisco 4507R+E multilayer switch with redundant Supervisor Engines WS-X45-SUP7L-E, WS-X4648-RJ45V+E (48 port 1G PoE) Line Cards, dual 4300Watt power supplies and much more. We cover the installation and provide a number of tips using more than 20 high-resolution pictures to ensure the reader gets a ‘real feeling’ of our installation. Firewall.cx - Cisco 4507R+E Layer 3 Installation: Redundant WS-X45-SUP7L-E Supervisor Engines & WS-X4648-RJ45V+E Line Cards Key Topics: Introducing the Catalyst 4507R+E Switch Revealing The Magnificent Cisco 4507R+E Backplane Introducing The WS-X45-SUP7L-E Supervisor Engine The WS-X4648-RJ45V+E Line Card Installing Line Cards into the 4507R chassis Cisco 4507R+E 4200Watt Power Supplies Supervisor Engine Redundancy Any feedback or questions are always welcome. Chris.
... View more
Hello to everyone, I am considering the ISA 550 for a customer who has multiple VLANs on his network. In order to avoid purchase a layer3 switch, I was thinking that we could perhaps create a 802.1q trunk link from a switch to the ISA500 and perform Inter-VLAN routing through that. In addition, we would use access lists to prevent communications between specific VLANs. My question is if this setup model can be done on the ISA 550. I haven't used it before, so I am not sure if it can support this setup. Any information or help is much appreciated. Many thanks, Chris.
... View more